DESC:
FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
METHOD AND SYSTEM FOR MANAGING DATA IN A NETWORK
2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN OFFICE-101, SAFFRON, NR. CENTRE POINT, PANCHWATI 5 RASTA, AMBAWADI, AHMEDABAD 380006, GUJARAT, INDIA
3.PREAMBLE TO THE DESCRIPTION

THE FOLLOWING SPECIFICATION PARTICULARLY DESCRIBES THE NATURE OF THIS INVENTION AND THE MANNER IN WHICH IT IS TO BE PERFORMED.

FIELD OF THE INVENTION
[0001] The present invention relates to the field of cellular and wireless communication, more particularly relates to method and system for managing data in a network.
BACKGROUND OF THE INVENTION
[0002] For analysis and troubleshooting of any issue in the network, knowledge of the geographical location of the network node is an indispensable requirement.
[0003] The NRSL call summary logs received from Next Generation NodeB (gNodeB) contains only the node id, network cell id and circle related geo-information. However, these are not self-sufficient for the end user to dig down to the exact point of breakdown.
[0004] So, to enable the end user gain insights of the complete network geographical visualization and data extraction, Solution incorporates multiple levels of pre-defined network geographies and multiple sub geographies in addition to Circle.
[0005] The current invention addresses this gap, by providing a method for identifying the geographical location of a network node.
SUMMARY OF THE INVENTION
[0006] One or more embodiments of the present disclosure provide a method and a system for managing data in a network.
[0007] In one aspect of the present invention, the system for managing the data in the network is disclosed. The system includes a receiving unit configured to receive the data from a plurality of Next Generation Node B (gNodeB) via a plurality of message brokers. The system further includes a correlating unit configured to correlate the received data with a set of predefined network geographical data. The system further includes an aggregation unit configured to aggregate the received data at multiple levels based on the correlation. The system further includes a transmittal unit configured to transmit the aggregated data to a user interface based on receipt of a request via the user interface.
[0008] In an embodiment, the data pertains to at least New Radio Session Log (NRSL) summary.
[0009] In an embodiment, the set of predefined network geographical data is at least one of a zone, supercore, R4GState, maintenance zone, a geographical location, and a product type.
[0010] In an embodiment, the multiple levels is at least one of a node level and a network level.
[0011] In an embodiment, the system comprises a filtering unit configured to filter, the aggregated data on receipt of the request based on one or more filtering options, wherein the one or more filtering options is at least success or failure events, and the geographical location.
[0012] In an embodiment, the correlating unit is configured to stitch, the corelated received data with the set of network geographical data and store, subsequent to stitching, the corelated received data in a database.
[0013] In another aspect of the present invention, the method for managing the data in the network is disclosed. The method includes the step of receiving the data from a plurality of Next Generation Node B (gNodeB) via a plurality of message brokers. The method further includes the step of correlating the received data with a set of predefined network geographical data. The method further includes the step of aggregating the received data at multiple levels based on the correlation. The method further includes the step of transmitting the aggregated data to a user interface based on receipt of a request via the user interface.
[0014] In another aspect of the invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions is disclosed. The computer-readable instructions are executed by a processor. The processor is configured to receive the data from a plurality of Next Generation Node B (gNodeB) via a plurality of message brokers. The processor is further configured to correlate the received data with a set of predefined network geographical data. The processor is further configured to aggregate the received data at multiple levels based on the correlation. The processor is further configured to transmit the aggregated data to a user interface based on receipt of a request via the user interface.
[0015] Other features and aspects of this invention will be apparent from the following description and the accompanying drawings. The features and advantages described in this summary and in the following detailed description are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art, in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.
BRIEF DESCRIPTION OF THE DRAWINGS
[0016] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0017] FIG. 1 is an exemplary block diagram of an environment for managing data in a network, according to one or more embodiments of the present invention;
[0018] FIG. 2 an exemplary block diagram of a system for managing the data in the network, according to one or more embodiments of the present invention;
[0019] FIG. 3 is an exemplary block diagram of an architecture implemented in the system of the FIG. 2, according to one or more embodiments of the present invention;
[0020] FIG. 4 is a signal flow diagram for managing the data in the network, according to one or more embodiments of the present invention; and
[0021] FIG. 5 is a schematic representation of a method for managing the data in the network, according to one or more embodiments of the present invention.
[0022] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0023] Some embodiments of the present disclosure, illustrating all its features, will now be discussed in detail. It must also be noted that as used herein and in the appended claims, the singular forms "a", "an" and "the" include plural references unless the context clearly dictates otherwise.
[0024] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. However, one of ordinary skill in the art will readily recognize that the present disclosure including the definitions listed here below are not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
[0025] A person of ordinary skill in the art will readily ascertain that the illustrated steps detailed in the figures and here below are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0026] The present invention discloses a system and method for managing data in a network. The system enables an end user to easily monitor and debug the network across multiple geographies via a user interface. Debugging a network failure and identification of reason for the same upto the ground level is fastened. By applying Artificial Intelligence / Machine Learning (AI/ML) algorithms to a Network Geography analysis near real-time grabbing of an upcoming failure helps identify problems at the lowest geographical level of the network node, and thereby help prevent failures.
[0027] FIG. 1 illustrates an exemplary block diagram of an environment 100 for managing data in a network, according to one or more embodiments of the present disclosure. In this regard, the environment 100 includes a User Equipment (UE) 102, a server 104, a network 106 and a system 108 communicably coupled to each other for managing the data in the network 106.
[0028] As per the illustrated embodiment and for the purpose of description and illustration, the UE 102 includes, but not limited to, a first UE 102a, a second UE 102b, and a third UE 102c, and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the UE 102 may include a plurality of UEs as per the requirement. For ease of reference, each of the first UE 102a, the second UE 102b, and the third UE 102c, will hereinafter be collectively and individually referred to as the “User Equipment (UE) 102”.
[0029] In an embodiment, the UE 102 is one of, but not limited to, any electrical, electronic, electro-mechanical or an equipment and a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device.
[0030] The environment 100 includes the server 104 accessible via the network 106. The server 104 may include, by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof. In an embodiment, the entity may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business enterprise side, a defense facility side, or any other facility that provides service.
[0031] The network 106 includes, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. The network 106 may include, but is not limited to, a Third Generation (3G), a Fourth Generation (4G), a Fifth Generation (5G), a Sixth Generation (6G), a New Radio (NR), a Narrow Band Internet of Things (NB-IoT), an Open Radio Access Network (O-RAN), and the like.
[0032] The network 106 may also include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network 106 may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, a VOIP or some combination thereof.
[0033] The environment 100 further includes the system 108 communicably coupled to the server 104 and the UE 102 via the network 106. The system 108 is configured to manage the data in the network 106. As per one or more embodiments, the system 108 is adapted to be embedded within the server 104 or embedded as an individual entity.
[0034] Operational and construction features of the system 108 will be explained in detail with respect to the following figures.
[0035] FIG. 2 is an exemplary block diagram of the system 108 for managing the data in the network 106, according to one or more embodiments of the present invention.
[0036] As per the illustrated embodiment, the system 108 includes one or more processors 202, a memory 204, a user interface 206, and a database 208. For the purpose of description and explanation, the description will be explained with respect to one processor 202 and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the system 108 may include more than one processors 202 as per the requirement of the network 106. The one or more processors 202, hereinafter referred to as the processor 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, single board computers, and/or any devices that manipulate signals based on operational instructions.
[0037] As per the illustrated embodiment, the processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 204. The memory 204 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory 204 may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as disk memory, EPROMs, FLASH memory, unalterable memory, and the like.
[0038] In an embodiment, the user interface 206 includes a variety of interfaces, for example, interfaces for a graphical user interface, a web user interface, a Command Line Interface (CLI), and the like. The user interface 206 facilitates communication of the system 108. In one embodiment, the user interface 206 provides a communication pathway for one or more components of the system 108. Examples of such components include, but are not limited to, the UE 102 and the database 208.
[0039] The database 208 is one of, but not limited to, a centralized database, a cloud-based database, a commercial database, an open-source database, a distributed database, an end-user database, a graphical database, a No-Structured Query Language (NoSQL) database, an object-oriented database, a personal database, an in-memory database, a document-based database, a time series database, a wide column database, a key value database, a search database, a cache databases, and so forth. The foregoing examples of database 208 types are non-limiting and may not be mutually exclusive e.g., a database can be both commercial and cloud-based, or both relational and open-source, etc.
[0040] In order for the system 108 for managing the data in the network 106, the processor 202 includes one or more modules. In one embodiment, the one or more modules includes, but not limited to, a receiving unit 210, a correlating unit 212, an aggregation unit 214, a transmittal unit 216 and a filtering unit 218 communicably coupled to each other for managing the data in the network 106.
[0041] In one embodiment, the one or more modules includes, but not limited to, the receiving unit 210, the correlating unit 212, the aggregation unit 214, the transmittal unit 216 and the filtering unit 218 and can be used in combination or interchangeably for managing the data in the network 106.
[0042] The receiving unit 210, the correlating unit 212, the aggregation unit 214, d the transmittal unit 216, and the filtering unit 218 in an embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 202. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor 202 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 204 may store instructions that, when executed by the processing resource, implement the processor. In such examples, the system 108 may comprise the memory 204 storing the instructions and the processing resource to execute the instructions, or the memory 204 may be separate but accessible to the system 108 and the processing resource. In other examples, the processor 202 may be implemented by electronic circuitry.
[0043] In one embodiment, the receiving unit 210 is configured to receive the data from a plurality of Next Generation Node B (gNodeB) via a plurality of message brokers. The data is at least one of session identification data, timing data, Quality of Service (QoS) metrics, User Equipment (UE) data, resource utilization data, error and event data, throughput data, mobility data. The data includes, but not limited to, session Identifier (ID), gNodeB ID, cell ID, session start time, session end time, duration, latency, packet loss, jitter, UE ID, device type location, CPU usage, memory usage, bandwidth utilization, error codes, event logs, uplink throughput, downlink throughput handover count, cell transitions. The gNodeB is a base station in 5th Generation (5G) networks responsible for facilitating wireless communication between user devices (such as smartphones) and the 5G core network 106. The message broker is an intermediary system that facilitate the exchange of messages between different applications, systems, or services. The data pertains to at least NR Session Log (NRSL) summary. The NR Session Log (NRSL) is typically used to record and summarize the activities, observations, and outcomes of network resource (NR) sessions in telecommunications. The NRSL summary includes, but not limited to, session identification, timing information, network details, quality metrics, events and procedures, errors and issues, user experience metrics, traffic statistics, additional contextual information.
[0044] Upon receiving the data from the plurality of gNodeB, the correlating unit 212 is configured to correlate the received data with a set of predefined network geographical data. The predefined network geographical data refers to the specific information related to the geographical locations, terrain and other spatial details that are used to optimize the deployment, management and performance of the network 106. The set of predefined network geographical data is at least a zone, supercore, R4GState, maintenance zone, a geographical location, and a product type. The zone refers to a specific are within the network 106 that is managed and optimized as a unit. The zone includes, but not limited to, coverage zones and service zones. The supercore handles a significant portion of the data traffic and connects various network components. The supercore includes, but not limited to, core network nodes, high-capacity links. The R4GState is the state of the 4th Generation (4G) network that interwork with the 5th Generation (5G) network. The R4GState includes, but not limited to, legacy network integration and transition plans. The maintenance zones are specific areas designated for regular maintenance and upgrades. The maintenance zone includes, but not limited to, scheduled maintenance areas, emergency repair zones. The geographical location includes information about the physical locations relevant to the network 106. The geographical locations include, but are not limited to, latitude and longitude, topographical data. The product type categorizes the different types of equipment and services deployed in the network 106. The product types include, but not limited to equipment types, service types.
[0045] The correlating of the received data with the set of predefined network geographical data involves matching and integrating the key attributes such as gNodeB ID, cell ID, latitude, longitude etc, of the received data with geographical information to analyze and optimize network performance. Further, the correlating unit 212 is configured to stitch the correlated received data with the set of network geographical data. The stitching refers to the process of combining or integrating the correlated received data with the set of network geographical data. The stitching enables network operators to visualize and analyze how the network 106 is performing across different areas and to identify and address potential issues. Subsequent to stitching the correlated received data, the correlated received data is stored in the database 208.
[0046] Upon correlating the received data, the aggregation unit 214 is configured to aggregate the received data at multiple levels based on the correlation. The multiple levels is at least one of a node level and a network level. The aggregation of the received data at the node level includes collection of data specific to each node, calculating key performance metrics for each node, such as average signal strength (RSRP), average signal quality (SINR), data throughput, and error rates and creating node-specific reports or dashboards showing performance metrics and any anomalies. The aggregation of the received data at the network level includes collecting the data from all cell towers in the network 106, calculating overall network metrics such as average RSRP, data throughput and error rates, identifying network-wide trends such as peak usage time or regions with consistent performance issues and developing network-level dashboards and heatmaps to visualize overall network performance and identify areas needing attention.
[0047] Upon aggregating the received data, the aggregated data is transmitted by the transmittal unit 216 to the user interface 206 based on receipt of a request via the user interface 206. The request is a message or signal sent to the system 108, requesting specific information or action The request is at least one of data query request, data visualization request, configuration request, system status request, and alert or notification request. The request is for at least one of customized data access, efficient resource utilization, real-time monitoring and response, support for decision making, enhanced user experience and scalability and flexibility.
[0048] In an embodiment, the filtering unit 218 is configured to filter the aggregated data on receipt of the request based on or more filtering options. The one or more filtering options is at least success or failure events and the geographical location. On receipt of the request from the user interface 206, the aggregated data is filtered based on the success or failure event filtering by identifying the data that meets the success or failure criteria specified in the request. For example, filter the data where latency exceeds 100ms or where packet loss exceeds 5% as failure events otherwise as success event. On receipt of the request from the user interface 206, the aggregated data is filtered based on geographical location filtering by applying filter to include data points only with the specified geographical zone or region. For example, filtering the data within a specific city or operational area defined by its latitude 34.0522 to 34.0422 and longitude -118.2437 to -118.2537coordinates.
[0049] Therefore, the system 108 is configured to easily identify and rectify the network failure. Further, the system 108 enables early detection and prevention of upcoming failure or issue at the lowest geographical level of a network node.
[0050] FIG. 3 is an exemplary block diagram of an architecture 300 implemented in the system 108 for managing the data in the network 106, according to one or more embodiments of the present invention.
[0051] The architecture 300 includes a message broker unit 302, a normalizer 304, a workflow 306, a graphical user interface 308, an Application Identifier Repository (AIDR) writer 310, a distributed file system 312, a computation engine 314 and the database 208 communicably coupled to each other for monitoring the data in the network 106.
[0052] In an embodiment the decoded raw NRSL call summary data is stored in the message broker unit 302. Thereafter, the decoded data is fetched by the normalizer 304. Further, at the normalizer 304, the pre-defined network geographical data consisting of zone, supercore, R4GState, maintenance zone, product type etc. is stitched together with the decoded data and stored in the database 208.
[0053] Simultaneously, the decoded data is also fetched by the AIDR writer 310. The AIDR writer 310 is a tool used to manage and write identifiers for various applications within the network 106. The AIDR writer 310 plays a crucial role in ensuring that applications and services can be uniquely identified, tracked, and managed Further, at the AIDR writer, the pre-defined network geographical data consisting of zone, supercore, R4GState, maintenance zone, product type etc. is stitched together with the decoded data and stored in the distributed file system 312.
[0054] In an embodiment, when a user requests for network geography-based data from the graphical user interface 308, the graphical user interface 308 forwards the request to the workflow 306. The workflow 306 fetches the data from the database 208 and also forwards the request to the computation engine 314 in case the request requires reckoning over historical data. Upon receiving the request from the workflow 306, the computation engine 314 calculates and fetches the data from the distributed file system 312 and sends the response with computed data to the workflow 306.
[0055] Upon receiving the response with the computed data from the computation engine 314, the workflow 306 forwards the response in the form of report for visualization to the user via dashboard on graphical user interface 308.
[0056] FIG. 4 is a signal flow diagram for managing the data in the network 106, according to one or more embodiments of the present invention.
[0057] At step 402, receiving the data from the plurality of gNodeB via the plurality of message brokers. The data pertains to at least New Radio Session Log (NRSL) summary.
[0058] At step 404, upon receiving the data from the plurality of gNodeB, the received data is correlated with the set of predefined network geographical data. The set of predefined network geographical data is at least one of the zone, supercore, maintenance zone, the geographical location, and the product type. Further, on correlation of the received data with the set of network geographical data, the correlated received data is stitched with the set of network geographical data. Subsequent to stitching, the correlated received data is stored in the database 208.
[0059] At step 406, upon correlating the received data, the received data is aggregated at the multiple levels based on the correlation. The multiple levels is at least one of the node level and the network level.
[0060] At step 408, upon aggregating the received data, the aggregated data is transmitted the user interface 206, based on receipt of the request via the user interface 206.
[0061] At step 410, in an embodiment, the aggregated data is filtered based on one or more filtering options. The one or more filtering options is at least success or failure events and the geographical location.
[0062] FIG. 5 is a flow diagram of a method 500 for managing the data in the network 106, according to one or more embodiments of the present invention. For the purpose of description, the method 500 is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0063] At step 502, the method 500 includes the step of receiving the data from the plurality of gNodeB via the plurality of message brokers by the receiving unit 210. The data pertains to at least New Radio Session Log (NRSL) summary.
[0064] At step 504, the method 500 includes the step of correlating the received data with the set of predefined network geographical data by the correlating unit 212. The set of predefined network geographical data is at least one of the zone, supercore, R4GState, maintenance zone, the geographical location, and the product type.
[0065] At step 506, the method 500 includes the step of aggregating the received data by the aggregation unit 214 at multiple levels based on the correlation. The multiple levels is at least one of the node level and the network level.
[0066] At step 508, the method 500 includes the step of transmitting the aggregated data to the user interface 206 by the transmittal unit 216 based on receipt of the request via the user interface 206. In an embodiment, the filtering unit 218 is configured to filter the aggregated data on receipt of the request based one or more filtering options. The one or more filtering options is at least success or failure events and the geographical conditions.
[0067] The present invention further discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by the processor 202. The processor 202 is configured to receive the data from a plurality of Next Generation Node B (gNodeB) via a plurality of message brokers. The processor 202 is further configured to correlate the received data with a set of predefined network geographical data. The processor 202 is further configured to aggregate the received data at multiple levels based on the correlation. The processor 202 is further configured to transmit the aggregated data to a user interface 206 based on receipt of a request via the user interface 206.
[0068] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-5) are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0069] The present disclosure incorporates technical advancement of monitoring and debugging the network across multiple geographies not only in reports but also visually on user interface. Further, the present disclosure enables early detection and prevention of an upcoming failure or issue at the lowest geographical level of a network node.
[0070] The present invention offers multiple advantages over the prior art and the above listed are a few examples to emphasize on some of the advantageous features. The listed advantages are to be read in a non-limiting manner.
REFERENCE NUMERALS

[0071] Environment- 100
[0072] User Equipment (UE)- 102
[0073] Server- 104
[0074] Network- 106
[0075] System -108
[0076] Processor- 202
[0077] Memory- 204
[0078] User Interface- 206
[0079] Database- 208
[0080] Receiving Unit- 210
[0081] Correlating Unit- 212
[0082] Aggregation Unit- 214
[0083] Transmittal Unit- 216
[0084] Filtering Unit- 218
[0085] Message Broker Unit- 302
[0086] Normalizer- 304
[0087] Workflow- 306
[0088] Graphical User Interface -308
[0089] AIDR Writer- 310
[0090] Distributed File System- 312
[0091] Computing Engine - 314
,CLAIMS:CLAIMS:

We Claim:

1. A method (500) of managing data in a network (106), the method (500) comprising the steps of:
receiving, by one or more processors (202), the data from a plurality of Next Generation Node B (gNodeB) via a plurality of message brokers;
correlating, by the one or more processors (202), the received data with a set of predefined network geographical data;
aggregating, by the one or more processors (202), the received data at multiple levels based on the correlation; and
transmitting, by the one or more processors (202), the aggregated data to a user interface (206) based on receipt of a request via the user interface (206).

2. The method (500) as claimed in claim 1, wherein the data pertains to at least New Radio Session Log (NRSL) summary.

3. The method (500) as claimed in claim 1, wherein the set of predefined network geographical data is at least one of a zone, supercore, R4GState, maintenance zone, a geographical location, and a product type.

4. The method (500) as claimed in claim 1, wherein the multiple levels is at least one of a node level and a network level.

5. The method (500) as claimed in claim 1, wherein based on the request, the method comprises the step of, filtering, by the one or more processors (202), the aggregated data based on one or more filtering options, wherein the one or more filtering options is at least success or failure events, and the geographical location.

6. The method (500) as claimed in claim 1, wherein on correlation of the received data with the set of network geographical data, the method comprises the step of
stitching, by the one or more processors (202), the corelated received data with the set of network geographical data; and
storing, by the one or more processors (202), subsequent to stitching, the corelated received data in a database (208).

7. A system (108) for managing data in a network (106), the system (108) comprising:
a receiving unit (210) configured to receive, the data from a plurality of Next Generation Node B (gNodeB) via a plurality of message brokers;
a correlating unit (212) configured to correlate, the received data with a set of predefined network geographical data;
an aggregation unit (214) configured to aggregate, the received data at multiple levels based on the correlation; and
a transmittal unit (216) configured to transmit, the aggregated data to a user interface (206) based on receipt of a request via the user interface (206).

8. The system (108) as claimed in claim 7, wherein the data pertains to at least New Radio Session Log (NRSL) summary.

9. The system (108) as claimed in claim 7, wherein the set of predefined network geographical data is at least one of a zone, supercore, R4GState, maintenance zone, a geographical location, and a product type.

10. The system (108) as claimed in claim 7, wherein the multiple levels is at least one of a node level and a network level.

11. The system (108) as claimed in claim 7, the system (108) comprises a filtering unit (218) configured to filter, the aggregated data on receipt of the request based on one or more filtering options, wherein the one or more filtering options is at least success or failure events, and the geographical location.

12. The system (108) as claimed in claim 7, wherein the correlating unit (212) is configured to:
stitch, the corelated received data with the set of network geographical data; and
store, subsequent to stitching, the corelated received data in a database (208).