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 OF NETWORK SLICE OF AT LEAST ONE CELL

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 telecommunications and network management, more particularly relates to a method and system for managing data of a network slice of at least one cell.
BACKGROUND OF THE INVENTION
[0002] Network analysis techniques are invaluable tools for identifying and resolving issues in communication networks. These techniques encompass various approaches, including performance monitoring, packet analysis, protocol analysis, and traffic flow analysis. By examining network data and traffic patterns, service providers can gain insights into network performance, identify anomalies, and pinpoint the root causes of issues.
[0003] However, in most of the conventional systems the predominant deployment strategy revolves around network slicing, where each slice can extend across multiple geographical areas and Public Land Mobile Networks (PLMNs). The deployment makes the deployment pattern in 5G networks impractical to analyze the performance of cells within a slice using traditional PLMN or location-based methods. Further, the conventional systems lack the capability to perform detailed analysis on cells belonging to specific slices or across multiple slices simultaneously.
[0004] Thus, there is a need for a solution which solves the above problem.
SUMMARY OF THE INVENTION
[0005] One or more embodiments of the present invention provides a method and a system for managing data of a network slice of at least one cell.
[0001] In one aspect of the present invention, the method for managing data of a network slice of at least one cell is disclosed. The method includes the step of receiving a request from a User Equipment (UE), the request corresponds to retrieving the data of the network slice of at least one cell. The method further includes the step of retrieving data of the network slice of the at least one cell from a database on receipt of the request. The method further includes the step of performing the network slice data analysis on the retrieved data to compute information pertaining to the network slice. The method further includes the step of transmitting information pertaining to the network slice of the at least one cell to the UE.
[0002] In one embodiment, the method for performing the network slice data analysis includes the step of debugging the retrieved data of the network slice of the at least one cell. Further the method includes the step of determining at least one of, radio and network parameters of each of the at least one cell of the network slice based on debugging and identifying a pattern/trend corresponding to the identified at least one of, the radio and the network parameters.
[0003] In one embodiment, the information corresponds to at least one of, Call Release Reason (CRR) distribution within the network slice, worst cell distribution within the network slice, and top and worst IMSI within the network slice.
[0004] In one embodiment, the at least one cell of a plurality of cells pertains to at least one of a geographical location and a Public Land Mobile Network (PLMN).
[0005] In one embodiment, the network slice encompasses the plurality of cells, sites, geographical locations, terrains, and population densities, among other variables.
[0006] In another aspect of the present invention, a system for managing data of a network slice of at least one cell is disclosed. The system includes a receiving unit configured to receive a request from a UE, the request corresponds to retrieving the data of the network slice of the at least one cell. The system further includes a retrieving unit configured to retrieve data of the network slice of the at least one cell from a database on receipt of the request. The system further includes an analysing unit configured to perform, the network slice data analysis on the retrieved data to compute information pertaining to the network slice. The system further includes a transmitting unit configured to transmit information pertaining to the network slice of the at least one cell to the UE.
[0007] In another aspect of the present invention, a User Equipment (UE) is disclosed. One or more primary processors communicatively coupled to one or more processors. The one or more primary processors are coupled with a memory. The memory stores instructions which when executed by the one or more primary processors causes the UE to transmit, a request to retrieve data of a network slice of at least one cell to the one or more processors.
[0008] In yet another aspect of the present invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions that, when executed by a processor, causes the processor to receive, a request from the UE the request corresponds to retrieving the data of the network slice of at least one cell. The processor is further configured to retrieve historic data of the network slice of the at least one cell from at least one of, a database and a distributed file system on receipt of the request. The processor is further configured to perform the network slice data analysis on the retrieved data to compute information pertaining to the network slice. The processor is further configured to transmit the retrieved information pertaining to the data of the network slice of the at least one cell to the UE for performing network slice data analysis.
[0009] 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
[0010] 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.
[0011] FIG. 1 is an exemplary block diagram of a communication system for managing data of a network slice of at least one cell, according to one or more embodiments of the present disclosure;
[0012] FIG. 2 is an exemplary block diagram of a system for managing data of a network slice of at least one cell, according to one or more embodiments of the present disclosure;
[0013] FIG. 3 is a schematic representation of a workflow of the system of FIG. 2 communicably coupled with a User equipment (UE), according to one or more embodiments of the present disclosure
[0014] FIG. 4 is an exemplary diagram of an architecture of the system of the FIG. 2, according to one or more embodiments of the present disclosure;
[0015] FIG. 5 is a signal flow diagram for managing data of a network slice of at least one cell, according to one or more embodiments of the present disclosure; and
[0016] FIG. 6 is a flow chart illustrating a method for managing data of a network slice of at least one cell, according to one or more embodiments of the present disclosure.
[0017] The foregoing shall be more apparent from the following detailed description of the invention.

DETAILED DESCRIPTION OF THE INVENTION
[0018] 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.
[0019] 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.
[0020] 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.
[0021] The present disclosure addresses the challenges faced in established technologies where the conventional techniques may be limited by geographical considerations and may not provide suitable or true sense of analytical data for network issues resolution or network insights evaluation. The solution provides slice-level debugging, performance analysis, and insights into cell performance, the invention facilitates the optimization of network performance, minimizes service disruptions, and facilitates the overall quality of service of the network. The present invention facilitates the end users to gain valuable insights and perform in-depth analysis based on network slices. By analyzing data at the network slice level, the network operators can identify the impact of slice performance on cell performance for one or more subscribers and alter their optimizations in accordance with the analysis.
[0022] Referring to FIG. 1, FIG. 1 illustrates an exemplary block diagram of a communication system 100 for managing data of a network slice of at least one cell, according to one or more embodiments of the present disclosure. The communication system 100 includes a network 105, a User Equipment (UE) 110, a server 115, and a system 120. The UE 110 aids a user to interact with the system 120. In an embodiment, the UE 110 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.
[0023] For the purpose of description and explanation, the description will be explained with respect to the UE 110, or to be more specific will be explained with respect to a first UE 110a, a second UE 110b, and a third UE 110c, and should nowhere be construed as limiting the scope of the present disclosure. Each of the first UE 110a, the second UE 110b, and the third UE 110c is configured to connect to the server 115 via the network 105. As per the illustrated embodiment, the communication system 100 includes one or more base stations 125. In alternate embodiments, the UE 110 may include a plurality of UEs as per the requirement. For ease of reference, each of the first UE 110a, the second UE 110b, and the third UE 110c, will hereinafter be collectively and individually referred to as the “User Equipment (UE) 110”.
[0024] For the purpose of description and explanation, the description will be explained with respect to one or more base stations 125, or to be more specific will be explained with respect to a first base station 125a, a second base station 125b, and a third base station 125c, and should nowhere be construed as limiting the scope of the present disclosure. For ease of reference, each of the first base station 125a, the second base station 125b, and the third base station 125c, will hereinafter be collectively and individually referred to as the “base station 125”.
[0025] The first base station 125a includes, by way of example but not limitation, a cell site, cell phone tower, or cellular base station. Each of the first base station 125a, the second base station 125b, and the third base station 125c is a cellular-enabled mobile device site where antennas and electronic communications equipment are placed (typically on a radio mast, tower, or other raised structure) to create a cell, or adjacent cells, in the communication network. The structure typically supports an antenna and one or more sets of transmitters/receivers, digital signal processors, control electronics, a GPS receiver for timing, primary and backup electrical power sources, and sheltering.
[0026] The network 105 may 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 105 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, or some combination thereof.
[0027] The network 105 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 105 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.
[0028] The network 105 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 105 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.
[0029] The communication system 100 includes the server 115 accessible via the network 105. The server 115 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.
[0030] The communication system 100 further includes the system 120 communicably coupled to the server 115 and the UE 110 via the network 105. The system 120 is adapted to be embedded within the server 115 or is embedded as the individual entity. However, for the purpose of description, the system 120 is illustrated as remotely coupled with the server 115, without deviating from the scope of the present disclosure.
[0031] Operational and construction features of the system 120 will be explained in detail with respect to the following figures.
[0032] FIG. 2 illustrates an exemplary block diagram of the system 120 for monitoring the network 105, according to one or more embodiments of the present disclosure.
[0033] As per the illustrated embodiment, the system 120 includes one or more processors 205, a memory 210, a user interface 215 and a database 220. For the purpose of description and explanation, the description will be explained with respect to one processor 205 and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the system 120 may include more than one processor 205 as per the requirement of the network 105. The one or more processors 205, hereinafter referred to as the processor 205 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.
[0034] As per the illustrated embodiment, the processor 205 is configured to fetch and execute computer-readable instructions stored in the memory 210. The memory 210 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 display the enriched data to the user via the user interface in order to perform analysis. The memory 210 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.
[0035] In an embodiment, the user interface 215 includes a variety of interfaces, for example, interfaces for data input and output devices, referred to as Input/Output (I/O) devices, storage devices, and the like. The user interface 215 facilitates communication of the system 120. In one embodiment, the user interface 215 provides a communication pathway for one or more components of the system 120.
[0036] In an embodiment, the database 220 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 220 types are non-limiting and may not be mutually exclusive e.g., the database can be both commercial and cloud-based, or both relational and open-source, etc.
[0037] In order for the system 120 to manage data of a network slice of at least one cell, the processor 205 includes one or more modules. In one embodiment, the one or more modules includes, but not limited to, a receiving unit 225, a retrieving unit 230, an analysing unit 235 and a transmitting unit 240 communicably coupled to each other.
[0038] The receiving unit 225, the retrieving unit 230, the analysing unit 235 and the transmitting unit 240 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 205. 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 205 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for processor 205 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 210 may store instructions that, when executed by the processing resource, implement the processor 205. In such examples, the system 120 may comprise the memory 210 storing the instructions and the processing resource to execute the instructions, or the memory 210 may be separate but accessible to the system 120 and the processing resource. In other examples, the processor 205 may be implemented by electronic circuitry.
[0039] In one embodiment, the receiving unit 225 is configured to receive a request from a UE 110. The request corresponds to retrieving the data of the network slice of the at least one cell. The data corresponds to at least one of, a trace record. The trace records refer to the detailed log of a network resource utilization and status within a specific timeframe. In one embodiment the trace records include, but are not limited to, session log, call detail record, resource allocation, traffic flows, radio resource management, quality of service, UE 110 information, location information, session establishment and termination. In an embodiment the at least one cell of a plurality of cells pertains to at least one of a geographical location and a Public Land Mobile Network (PLMN). The PLMN refers to integral infrastructure and framework for provisioning advanced wireless communication services to end users and UE 110 in a public mobile network domain. The public mobile network refers to the environment, where mobile network operators facilitate wireless communication services to the public. In one embodiment the public mobile network includes, but is not limited to, Radio Access Network (RAN), core network, service provisioning, security infrastructure. In an embodiment, the network slice refers to a virtualized and independent portion of the network 105. The network slice facilitates tailored network services and capabilities, which are optimized to meet the specific requirements of the distinct applications and devices such as but not limited to, Enhanced Mobile Broadband (eMBB), Ultra-Reliable Low Latency Communications (URLLC), Massive Machine Type Communications (mMTC), autonomous vehicles, industrial IoT devices. The network slice includes, but is not limited to, the plurality of cells, sites, geographical locations, terrains, and population densities, among other variables. In an embodiment, the request received corresponds to retrieving the data of the network slice of the at least one cell.
[0040] Upon receiving the request, the retrieving unit 230 is configured to retrieve data of the network slice of the at least one cell from the database 220. In one embodiment the request includes an identifier to specify which data to retrieve. The identifier is one of, but not limited to, a network slice identifier, a Network Slice ID (NSID), a Network Slice Selection Assistance Information (S-NSSAI), a network slice subnet, a network function ID, a cell identifier, a Mobile country code (MCC), a Mobile Network Code (MNC), a Location Area Code (LAC), a Tracking Area Code (TAC), a Service Area Code (SAI), and a Public Land Mobile Network Identity (PLMN ID).
[0041] Upon retrieving the data of the network slice of the at least one cell from the database 220, the analysing unit 235 is configured to perform the cell level data analysis across network slice to compute information pertaining to the network slice. In an embodiment, the information includes, but not limited to, at least one of, Call Release Reason (CRR) distribution in the network slice, worst cell distribution in the network slice, and top and worst IMSI in the network slice. The information provides insights pertaining to the network slice, which facilitates the user such as, network operators to assess CRR patterns, the worst-performing cells within the specific slice, and identify the top and worst cells exhibiting the poorest performance within the slice. In one embodiment, the CRR distribution refers to the categorization and analysis of reasons for call releases within a network slice of network 105. The reasons for call release include, but not limited to, handovers, user-initiated terminations, network errors. In an embodiment, the worst cell distribution includes, but is not limited to, the Worst International Mobile Subscriber Identity (IMSI) distribution. The worst IMSI refers to the IMSIs, which experience the poorest service quality or performance in the network slice. The IMISI refers to a unique identifier assigned to each mobile subscriber in the network 105. The top and worst IMSI within slice refers to identifying the subset of IMSIs in the network slice, which determines the poorest performance characteristics, such as high call drop rates, data session failures, and unsatisfactory user experience metrics.
[0042] In one embodiment, the analysing unit 235 performs network slice data analysis on the retrieved data by debugging the retrieved data of the network slice of the at least one cell. In an embodiment, the debugging involves the process of detecting and diagnosing the radio and network errors impacting the network slice. The radio errors of the analyzed parameters include but are not limited to, Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Interference-plus-Noise Ratio (SINR), Channel Quality Indicator (CQI). The network errors of the analyzed parameters include, but are not limited to, handover thresholds, Cell Load Balancing Parameters, Mobility Management Parameters, Quality of Service (QoS) Parameters. Further, the analyzing unit 235 determines at least one of, radio and network parameters of each of the at least one cell of the network slice based on debugging. In an embodiment, the radio parameters include but are not limited to Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Interference-plus-Noise Ratio (SINR), Channel Quality Indicator (CQI). In an embodiment the network parameters include, but are not limited to, handover thresholds, cell load balancing parameters, mobility management parameters, QoS parameters.
[0043] Upon determining the at least one of the radio and network parameters, the analyzing unit 235 is configured to identify a pattern/trend corresponding to the determined at least one of, the radio and the network errors. In an embodiment, the pattern/trend refers to recurring behaviors, anomalies, or deviations observed in the occurrence of radio and network errors within a specific network slice. Thereby, the analyzing unit 235 completes performing the network slice data analysis.
[0044] Upon performing the network slice data analysis, the transmitting unit 240 is configured to transmit information pertaining to the network slice of the at least one cell to the UE 110. Advantageously, the end user such as, network operator associated to the UE 110 may then perform the necessary data operations on the received network slice information to gain insights about data such as, for example, cell performance of the network 105.
[0045] FIG. 3 is a schematic representation of a workflow of the system of FIG. 2 communicably coupled with a User equipment (UE), according to one or more embodiments of the present disclosure. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first UE 110a and the system 120 for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
[0046] As mentioned earlier in FIG. 1, the UE 110 may include an external storage device, a bus, a main memory, a read-only memory, a mass storage device, communication port(s), and a processor. The exemplary embodiment as illustrated in FIG. 3 will be explained with respect to the first UE 110a without deviating from the scope of the present disclosure and limiting the scope of the present disclosure. The first UE 110a includes one or more primary processors 305 communicably coupled to the one or more processors 205 of the system 120.The one or more primary processors 305 are coupled with a memory 310 storing instructions which are executed by the one or more primary processors 305. Execution of the stored instructions by the one or more primary processors 305 enables the first UE 110a to transmit, a request to retrieve data of a network slice of at least one cell to the one or more processors. The request corresponds to retrieving the data of the network slice of at least one cell. In an embodiment, the end user such as, network operator is associated to the UE 110. Once the network slice information is transmitted by the transmitting unit 240 of the system 120 to the UE 110, the network operators may use this information to perform the necessary data operations on the network slice information to gain insights about data such as, for example, cell performance of the network 105.
[0047] As illustrated in FIG. 2, the system 120 includes the one or more processors 205, the memory 210, the user interface 215, and the database 220. The operations and functions of the one or more processors 205, the memory 210, the user interface 215, and the database 220 are already explained in FIG. 2. For the sake of brevity, a similar description related to the working and operation of the system 120 as illustrated in FIG. 2 has been omitted to avoid repetition.
[0048] FIG.4 is an exemplary architecture 400 which can be implemented in the system 120 of the FIG.2 for managing data of a network slice of at least one cell, according to one or more embodiments of the present invention. The exemplary embodiment as illustrated in the FIG. 4 includes one or more GnodeBs 405, a probing agent 410, a conductor 415, a message broker unit 420, a normalizer 425, an Artificial Intelligence Data Records (AIDR) writer 430, a Graphical User Interface (GUI) 435, the database 220, an ingestion layer 440, a distributed file system 445, a workflow 450, a computation engine 455, and a computation layer 460.
In an embodiment, the one or more GnodeBs 405 serves as the primary data source in the network 105. Furthermore, the one or more GnodeBs can have different software versions. The one or more GnodeBs 405 is configured to generate call summary logs. The call summary logs refer to essential information about user sessions in the network 105. In an embodiment the call summary logs contains information about the network session in the network 105 such as, but is not limited to, signal strength, network congestion, latency, and other Key Performance Indicators (KPIs). Further the GnodeBs 405 transmits the generated call summary logs to the probing agent 410 via a Transmission Control Protocol (TCP). The TCP refers to networking protocol configured to transmit the data packets between the GnodeBs 405 and the probing agent 410 over the network 105.
[0049] Once the probing agent 410 receives the call summary data generated by the one or more GnodeBs 405 of different versions via the TCP, the probing agent 410 validates and segregates the call summary data received based on the version of the GnodeBs 405. In an embodiment, the Call Release Reason (CRR) is identified in the probing agent 410 from the received call summary data. The call summary data from the one or more GnodeBs 405 is received as for example, a Hexadecimal dump stream over TCP. Further the probing agent 410 consumes the call summary data byte by byte and stores it in message broker unit 420.
[0050] Upon storing the call summary data at the message broker unit 420, further the call summary data is transmitted from the message broker unit 420 to the conductor 415. The conductor 415 ingests and decodes the call summary data of multiple versions related to the one or more GnodeBs 405 received from the probing agent 410 before feeding it to the message broker unit 420. The conductor 415 is configured as the customized decoder component in the architecture. In an embodiment the conductor 415 operates on byte indices to decode the call summary data. The conductor 415 features configurable versions that facilitates adjustments to accommodate changes in the length and position of fields within the decoded data. The configurations are illustrated by the user via the GUI 435, facilitating the accessibility for the user. The user herein is the network operator. Further by handling the different data versions, the conductor 415 facilitates seamless processing and compatibility across the architecture of the system 120.The collected call summary data from the probing agent 410 and the decoded data from the conductor 415 are securely stored in the message broker unit 420. The message broker unit 420 is configured as the publisher subscriber service to store the data. The message broker unit 420 act as an intermediary for data transmission and storage.
[0051] The normalizer 425 receives the decoded data from the message broker unit 420. The normalizer 425 performs real time enrichment, stitching, and data correlation operations on the collected data. Further the operations performed by the normalizer 425 facilitates the data by adding additional context, linking related information, and aligning the data for further analysis. Further the normalizer 425 optimizes the data for insights extraction and subsequent processing. In one embodiment, further the normalizer 425 is configured to receive rules from the user via the GUI 435. The rules may include, but are not limited to, data processing, data formatting and data transformation, data alignment based on the user request.
[0052] In one embodiment, the architecture which further includes AIDR writer 430, continuously retrieves the data from the message broker unit 420 and stores it in the file system.
[0053] In an embodiment, the end user such as the network operator requests the GUI 435 for the network slice insights data for a one or more subscriber from the collected call summary data. The request includes performance analysis and identifier of at least one cell from the one or more cells. The GUI 435 serves as the interface for the users to interact with the system 120. Further the GUI 435 inputs the user request for network slice data to workflow 450.
[0054] The database 220 is configured to store data. The data includes, but is not limited to meta data, session logs, subscriber level data, cell level data, policy related data, enriched and raw data from the one more processor of the system 120.
[0055] In an embodiment, the ingestion layer 440 is configured to fetch the data from the AIDR writer 430 and push it to the distributed file system 445. In one embodiment, further the ingestion layer 440 fetches data such as but not limited to, SIM details from Fulfilment Management System (FMS) 465 and transmits it to the workflow 450.
[0056] In one embodiment, the architecture 400 further includes distributed file system 445. The distributed file system 445 is configured to store the data from the ingestion layer 440. The computation layer 460 utilizes this data for the computation process.
[0057] In an embodiment, architecture 400 includes the workflow 450. Upon receiving the user request for network slice data from the collected call summary data via the GUI 435, the workflow 450 directs the request to the computation engine 455. The workflow 450 functions as the intermediary component between the GUI 435 and the computation engine 455. The workflow serves as the the orchestrator of the architecture 400.
[0058] The computation engine 455 receives requests from the workflow 450 for the computation of the network slice data. Based on the received request, the computation engine 455 assigns task to the computation layer 460 for the computation of the network slice data. The computation engine 455 facilitates efficient resource allocation and manages the execution of computations.
[0059] Upon the assignment of the computation task for the requested network slice data, the computation layer 460 operates on the cell level data across network slices available in the database 220 and the distributed file system 445 generates the computed network slice data. In one embodiment the computed network slice data includes, but not limited to, CRR distribution within slice, worst IMSI distribution by slice, TOP N worst IMSI in the network slice.
[0060] In one embodiment, the process for generating the computed network slice data includes, but not limited to monitoring and analyzing slice-level performance in the core network, which involves collecting data from network functions (NFs) and the Radio Access Network (RAN) to gain insights into slice loading, performance, and other key performance indicators (KPIs) which impact network slice performance.
[0061] Upon completion of the computation of the network slice data, the computation layer 460 provides the computed network slice data to the computation engine 455. Further the computation engine 455 transmits the computed network slice data to the workflow 450. The workflow 450 serving as the medium between the computation engine 455 and the GUI 435, transmits the response containing the requested data to the GUI 435. Further the end user such as the network operator accesses the computed network slice data via the GUI 435 to gain insights about cell performance.
[0062] In one embodiment, architecture 400 includes the FMS 465. The FMS 470 is configured as the inventory system, designed to capture and store subscriber level details.
[0063] FIG. 5 is a signal flow diagram for managing data of a network slice of at least one cell, according to one or more embodiments of the present invention. For the purpose of description, the signal flow diagram is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0064] At step 505, the user requests for the network slice data for cell performance analysis through the GUI 435. In one embodiment, the cell performance analysis request includes, but is not limited to, request to analyze a particular cell or more than one cell. Further, the user is a network operator, a technician or an administrator.
[0065] At step 510, upon receiving the user request for network slice data, the GUI 435 inputs to the workflow 450 the user request. The GUI 435 serves as the interface for the users to interact with the system 120.
[0066] At step 515, upon receiving the request for network slice data from the workflow 450, the workflow 450 directs the request to the computation engine 455. The workflow 450 functions as the intermediary component between the GUI 435 and the computation engine 455.
[0067] At step 520, the computation engine 455 receives requests from the workflow 450 for the computation of the network slice data. Based on the received request, the computation engine 455 assigns task to the computation Layer 460 for the computation of the network slice data.
[0068] At step 525, upon the assignment of the computation task, the computation layer 460 fetches and operates on the data available in the database 220 and the distributed file system 445. Based on the data available in the database 220 and distributed file system 445, the computation layer 460 computes the information pertaining to the network slice. In an embodiment, the information includes, but not limited to, at least one of, Call Release Reason (CRR) distribution in the network slice, worst cell distribution in the network slice, and top and worst IMSI in the network slice. In one embodiment, the CRR distribution refers to the categorization and analysis of reasons for call releases within a network slice of network 105. The reasons for call release include, but not limited to, handovers, user-initiated terminations, network errors. The worst IMSI distribution within the network slice refers to identifying the IMSIs, which experiencing the poorest service quality or performance in the network slice. The IMISI refers to a unique identifier assigned to each mobile subscriber in the network 105. The top and worst IMSI within slice refers to identifying the subset of IMSIs in the network slice, which determines the poorest performance characteristics, such as high call drop rates, data session failures, and unsatisfactory user experience metrics.
[0069] At step 530, the computation layer 460 provides the generated computed network slice data to the computation engine 455.
[0070] At step 535, upon receiving the computed network slice data, the computation engine 455 transmits the computed network slice data to the workflow 450.
[0071] At step 540, the workflow 450 serving as the medium between the computation engine 455 and the GUI 435, transmits the response containing the requested data to the GUI 435.
[0072] At step 545, the end user accesses the computed network slice data via the GUI 435 to gain insights about cell performance.
[0073] FIG. 6 is a flow diagram illustrating a method for managing data of a network slice of the at least one cell.
[0074] At step 605, the method 600 includes the step of receiving a request from the UE 110, The request corresponds to retrieving the data of the network slice of the at least one cell. The data corresponds to at least one of, a trace record. The trace records refer to the detailed log of a network resource utilization and status within a specific timeframe. In one embodiment the trace records include, but are not limited to, session log, resource allocation, traffic flows, radio resource management, quality of service, UE 110 information, location information, session establishment and termination. In an embodiment the at least one cell of a plurality of cells pertains to at least one of a geographical location and a Public Land Mobile Network (PLMN). The PLMN refers to integral infrastructure and framework for provisioning advanced wireless communication services to end users and UE 110 in a public mobile network domain. The public mobile network refers to the environment, where mobile network operators facilitate wireless communication services to the public. In one embodiment the public mobile network includes, but is not limited to, Radio Access Network (RAN), core network, service provisioning, security infrastructure. In an embodiment, the network slice includes, but is not limited to the plurality of cells, sites, geographical locations, terrains, and population densities, among other variables. In an embodiment, the request received corresponds to retrieving the data of the network slice of the at least one cell.
[0075] At step 610, the method 600 includes the step of retrieving data of the network slice of the at least one cell from the database on receipt of the request.
[0076] At step 615, the method 600 includes the step of performing the network slice data analysis on the retrieved data to compute information pertaining to the network slice. The network slice data analysis on the retrieved data includes debugging the retrieved data of the network slice of the at least one cell, determining at least one of, radio and network parameters of each of the at least one cell of the network slice based on debugging, identify a pattern/trend corresponding to the determined at least one of, the radio and the network parameters. In an embodiment, the pattern/trend refers to recurring behaviors, anomalies, or deviations observed in the occurrence of radio and network errors within a specific network slice. In an embodiment the radio parameters include but are not limited to Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Interference-plus-Noise Ratio (SINR), Channel Quality Indicator (CQI). In an embodiment the network parameters include, but are not limited to, handover thresholds, cell load balancing parameters, mobility management parameters, QoS parameters.
[0077] At step 620, the method 600 includes the step of transmitting information pertaining to the network slice of the at least one cell to the UE 110. The end user such as, network operator may then perform the necessary data operations on the received network slice data to gain insights about cell performance of the network 105.
[0078] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-6) 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.
[0079] The present disclosure incorporates technical advancement that facilitates the end users to gain valuable insights and perform in-depth analysis based on network slices. By analyzing data at the network slice level, the network operators can understand the impact of slice performance on the cell performance and alter their optimizations. The solution facilitates debugging the network slice data of the at least one cell, determining at least one of radio and network parameters of each of the at least one cell of the network slice based on debugging and identifying, a pattern/trend corresponding to the identified at least one of, the radio and the network parameters within specific network slices. This facilitates comprehensive end-to-end management and network surveillance. Further the comprehensive approach facilitates network operator to address issues efficiently, optimize network performance, and align their business objectives with network environment analysis.
[0080] The present invention provides various advantages, including optimal resource utilization and reduced execution time. By eliminating the limited geographical considerations, further the system facilitates suitable or true sense of analytical data for the network issues resolution. The solution performs network slice data analysis on to compute information pertaining to the network slice, which facilitates identifying a pattern/trend corresponding to the at least one of, the radio and the network parameters. The solution provides slice-level debugging, performance analysis, and provide the user to have insights into cell performance. Further the invention facilitates the optimization of network performance, minimizes service disruptions, and facilitates the overall quality of service of the network.
[0081] 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
[0082] Communication system – 100
[0083] Network – 105
[0084] User Equipment – 110
[0085] Server – 115
[0086] System – 120
[0087] Processor -205
[0088] Memory – 210
[0089] User Interface– 215
[0090] Database- 220
[0091] Receiving unit - 225
[0092] Retrieving unit - 230
[0093] Analysing unit - 235
[0094] Transmitting unit - 240
[0095] GUI - 435
[0096] Workflow - 450
[0097] Computation engine - 455
[0098] Computation layer - 460
[0099] Distributed file system – 445
[00100] Fulfilment Management system - 465

,CLAIMS:
CLAIMS
We Claim:
1. A method (600) for managing data of a network slice of at least one cell, the method comprising the steps of:
receiving (605), by one or more processors (205), a request from a User Equipment (UE), the request corresponds to retrieving the data of the network slice of at least one cell;
retrieving (610), by the one or more processors (205), data of the network slice of the at least one cell from a database on receipt of the request;
performing (615), by the one or more processors (205), the network slice data analysis on the retrieved data to compute information pertaining to the network slice; and
transmitting (620), by the one or more processors (205), information pertaining to the network slice of the at least one cell to the UE.

2. The method (600) as claimed in claim 1, wherein the data is one of trace records such as session logs.

3. The method (600) as claimed in claim 1, c
debugging, by the one or more processors (205), the retrieved data of the network slice of the at least one cell;
determining, by the one or more processors (205), at least one of, radio and network parameters of each of the at least one cell of the network slice based on debugging; and
identifying, by the one or more processors (205), a pattern/trend corresponding to the identified at least one of, the radio and the network parameters.

4. The method (600) as claimed in claim 1, wherein the information corresponds to at least one of, Call Release Reason (CRR) distribution within the network slice, worst cell distribution within the network slice, and top and worst IMSI within the network slice.

5. The method (600) as claimed in claim 1, wherein the at least one cell of a plurality of cells pertains to at least one of a geographical location and a Public Land Mobile Network (PLMN).

6. The method (600) as claimed in claim 1, wherein the network slice encompasses the plurality of cells, sites, geographical locations, terrains, and population densities, among other variables.

7. The method as claimed in claim 1, wherein for performing, by the one or more processors (205), the network slice data analysis, the method comprises the step of:
analysing, by the one or more processors (205), the cell level data across the network slices.

8. A system (120) for managing data of a network slice of at least one cell, the system (120) comprises:
a receiving unit (225) is configured to receive a request from a User Equipment (UE) (110), the request corresponds to retrieving the data of the network slice of the at least one cell;
a retrieving unit (230) is configured to retrieve data of the network slice of the at least one cell from a database on receipt of the request;
an analysing unit (235) configured to perform, the network slice data analysis on the retrieved data to compute information pertaining to the network slice and
a transmitting unit (240) configured to transmit, information pertaining to the network slice of the at least one cell to the UE.

9. The system (120) as claimed in claim 7, wherein the analysing unit is configured to:
debug the retrieved data of the network slice of the at least one cell;
determine at least one of, radio and network parameters of each of the at least one cell of the network slice based on the debugging; and
identify a pattern/trend corresponding to the determined at least one of, the radio and the network parameters.

10. The system (120)as claimed in claim 6, wherein the information corresponds to at least one of Call Release Reason (CRR) distribution within the network slice, worst cell distribution within the network slice, and top and worst IMSI within the network slice.

11. The system (120) as claimed in claim 6, wherein the at least one cell of a plurality of cells pertains to at least one of a geographical location and a Public Land Mobile Network (PLMN).

12. The system (120) as claimed in claim 6, wherein the network slice encompasses the plurality of cells, sites, geographical locations, terrains, and population densities, among other variables.

13. A User Equipment (UE) (110), comprising:
one or more primary processors (305) communicatively coupled to one or more processors (205), the one or more primary processors (305) coupled with a memory (310), wherein said memory stores instructions which when executed by the one or more primary processors (305) causes the consumer unit to:
transmit, a request to retrieve data of a network slice of at least one cell to the one or more processors (205).
wherein the one or more processors (205)is configured to perform the steps as claimed in claim 1.