FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR REAL-TIME CUSTOMIZED DECODING OF CALL SUMMARY LOGS”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR REAL-TIME CUSTOMIZED DECODING OF CALL
SUMMARY LOGS
FIELD OF THE INVENTION
5 [0001] Embodiments of the present disclosure generally relate to network performance
management systems. More particularly, embodiments of the present disclosure relate to real-time customized decoding of call summary logs.
BACKGROUND
10 [0002] The following description of the related art is intended to provide background
information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
15 [0003] Wireless communication technology has rapidly evolved over the past few
decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced.
20 3G technology marked the introduction of high-speed internet access, mobile video calling,
and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth-generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each
25 generation, wireless communication technology has become more advanced, sophisticated, and
capable of delivering more services to its users.
[0004] In the field of radio network communications, the management and analysis of call
summary logs are critical for maintaining and optimizing network performance. Traditionally,
radio networks have generated call summary logs that are standardized and relatively static in
30 format. These logs often provide basic information about the subscriber sessions but lack depth
and flexibility, which can hinder detailed troubleshooting and analysis. Moreover, these logs
2

are usually transmitted in formats that are not readily adaptable to dynamic network conditions or varied troubleshooting needs, leading to inefficiencies in data handling and interpretation.
[0005] A significant problem with the prior art is that traditional systems for decoding call
summary logs are not equipped to handle customized or proprietary log formats efficiently.
5 This limitation becomes particularly evident when dealing with New Radio Summary Log
(NRSL), a proprietary log format designed to provide detailed session information. Existing
systems often require manual adjustments or bespoke software updates to interpret these logs
correctly, which can be time-consuming and prone to errors. Furthermore, the inability to
automatically adapt to changes in log formats or to enrich the logs with additional context-
10 specific data (like device or subscriber information) further complicates the effective
monitoring and troubleshooting of radio access network (RAN) issues. Another issue with
conventional systems is their limited proactive monitoring capabilities. Most systems perform
basic parsing and decoding tasks but do not proactively monitor the quality or integrity of the
decoding process itself. This lack of proactive monitoring means that repeated errors or
15 anomalies in log decoding might not be detected promptly, leading to potential delays in
addressing network issues or inaccuracies in log data analysis.
[0006] Thus, there exists an imperative need in the art to develop a method and a system
for real-time customized decoding of call summary logs.
20 SUMMARY
[0007] This section is provided to introduce certain aspects of the present disclosure in a
simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0008] An aspect of the present disclosure may relate to a method for real-time customized
25 decoding of call summary logs. The method includes receiving a set of instructions, the
instructions related to customized decoding of a call summary log data received from a network
node, wherein the call summary log data comprises headers and payloads of one or more
messages, and wherein the headers and payloads of the data vary based on a version and a
message type of the messages in the data. Furthermore, the method encompasses identifying a
30 probe manager unit for communicating the instructions to a conductor unit. The method further
includes parsing the call summary log data, wherein the call summary log data is parsed byte by byte based on the message type and a size of the one or more messages in the data. Further,
3

the method includes sending to the conductor unit, the parsed data. The method further includes performing the customized decoding of the data related to call summary logs.
[0009] In an exemplary aspect of the present disclosure, post the identifying the probe
manager unit for communicating the instructions to the conductor unit, the method further
5 includes transferring to the probe manager unit, the set of instructions and transferring, by the
probe manager unit to the conductor unit, the set of instructions.
[0010] In an exemplary aspect of the present disclosure, prior to the receiving, by the
interface unit via the processing unit, the set of instructions, the method further comprises detecting a change in signature of the data received from the network node.
10 [0011] In an exemplary aspect of the present disclosure, for detecting the change in the
signature of the data received from the network node, the method further includes monitoring the data received from the network node, wherein the monitoring can be one of a continuous monitoring of the data, and a periodic monitoring of the data.
[0012] In an exemplary aspect of the present disclosure, the performing, by the conductor
15 unit, the customized decoding of the data related to call summary logs, further comprises
receiving an issue in at least one of the customized decoding of the data, and the parsing of the data and further, notifying the issue.
[0013] In an exemplary aspect of the present disclosure, the issue is received in an event
the at least one of the customized decoding of the data, and the parsing of the data fails for a
20 predefined threshold number of times.
[0014] Another aspect of the present disclosure may relate to a system for real-time
customized decoding of call summary logs. The system includes an interface unit configured to receive a set of instructions, the instructions related to customized decoding of a call summary log data received from the network node, wherein the call summary log data
25 comprises headers and payloads of one or more messages, and wherein the headers and
payloads of the data vary based on a version and a message type of the messages in the data. The system further includes a processing unit connected to the interface unit. The processing unit is configured to identify a probe manager unit for communicating the instructions to a conductor unit. The probe manager unit is configured to parse the call summary log data,
30 wherein the call summary log data is parsed byte by byte based on the message type and a size
of the one or more messages in the data and send, to the conductor unit, the parsed data. The
4

system further includes the conductor unit configured to perform the customized decoding of the data related to call summary logs.
[0015] Another aspect of the present disclosure relates to a user equipment comprising a
system for real-time customized decoding of call summary logs. The system further includes
5 an interface unit. The interface unit is configured to receive a set of instructions, the instructions
related to customized decoding of a call summary log data received from the network node, wherein the call summary log data comprises headers and payloads of one or more messages, and wherein the headers and payloads of the data vary based on a version and a message type of the messages in the data. The system further includes a processing unit connected to the
10 interface unit, the processing unit is configured to identify a probe manager unit for
communicating the instructions to a conductor unit. The probe manager unit is configured to parse the call summary log data, wherein the call summary log data is parsed byte by byte based on the message type and a size of the one or more messages in the data and send, to the conductor unit, the parsed data. The system further includes the conductor unit configured to
15 perform the customized decoding of the data related to call summary logs.
[0016] Yet another aspect of the present disclosure may relate to a non-transitory computer
readable storage medium storing instructions for real-time customized decoding of call summary logs, the storage medium comprising executable code which, when executed by one or more units of a system, causes: an interface unit to: receive a set of instructions, the
20 instructions related to customized decoding of a call summary log data received from the
network node, wherein the call summary log data comprises headers and payloads of one or more messages, and wherein the headers and payloads of the data vary based on a version and a message type of the messages in the data; a processing unit connected to the interface unit, the processing unit to: identify a probe manager unit for communicating the instructions to a
25 conductor unit; the probe manager unit to: parse the call summary log data, wherein the call
summary log data is parsed byte by byte based on the message type and a size of the one or more messages in the data; and send, to the conductor unit, the parsed data; and the conductor unit to: perform the customized decoding of the data related to call summary logs.
30 OBJECTS OF THE INVENTION
[0017] Some of the objects of the present disclosure, which at least one embodiment
disclosed herein satisfies are listed herein below.
5

[0018] It is an object of the present disclosure to provide a system and a method for real-
time customization and decoding of call summary logs.
[0019] It is another object of the present disclosure to provide a solution that can adapt to
a change in data signature received by the probe without needing to again develop, test and
5 deploy a probing software.
[0020] It is yet another object of the present disclosure to provide a solution that adapts to
a change in data signature without needing to stop probing a network.
DESCRIPTION OF THE DRAWINGS
10 [0021] 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. Also, the embodiments shown in the
15 figures are not to be construed as limiting the disclosure, but the possible variants of the method
and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
20 [0022] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core
(5GC) network architecture.
[0023] FIG. 2 illustrates an exemplary block diagram of a computer system upon which
the features of the present disclosure may be implemented in accordance with the exemplary implementation of the present disclosure.
25 [0024] FIG. 3 illustrates an exemplary block diagram of a system for real-time customized
decoding of call summary logs, in accordance with exemplary implementations of the present disclosure.
[0025] FIG. 4 illustrates a method flow diagram for real-time customized decoding of call
summary logs in accordance with exemplary implementations of the present disclosure.
6

[0026] FIG. 5 illustrates an exemplary signalling flow diagram indicating an exemplary
process for real-time customized decoding of call summary logs, in accordance with exemplary embodiments of the present disclosure.
[0027] The foregoing shall be more apparent from the following more detailed description
5 of the disclosure.
DETAILED DESCRIPTION
[0028] In the following description, for the purposes of explanation, various specific
details are set forth in order to provide a thorough understanding of embodiments of the present
10 disclosure. It will be apparent, however, that embodiments of the present disclosure may be
practiced without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.
15 [0029] The ensuing description provides exemplary embodiments only, and is not
intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the
20 spirit and scope of the disclosure as set forth.
[0030] Specific details are given in the following description to provide a thorough
understanding of the embodiments. However, it will be understood by one of ordinary skill in
the art that the embodiments may be practiced without these specific details. For example,
circuits, systems, processes, and other components may be shown as components in block
25 diagram form in order not to obscure the embodiments in unnecessary detail.
[0031] Also, it is noted that individual embodiments may be described as a process which
is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block
diagram. Although a flowchart may describe the operations as a sequential process, many of
the operations may be performed in parallel or concurrently. In addition, the order of the
30 operations may be re-arranged. A process is terminated when its operations are completed but
could have additional steps not included in a figure.
7

[0032] The word “exemplary” and/or “demonstrative” is used herein to mean serving as
an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed
herein is not limited by such examples. In addition, any aspect or design described herein as
“exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or
5 advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary
structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent
that the terms “includes,” “has,” “contains,” and other similar words are used in either the
detailed description or the claims, such terms are intended to be inclusive—in a manner similar
to the term “comprising” as an open transition word—without precluding any additional or
10 other elements.
[0033] As used herein, a “processing unit” or “processor” or “operating processor”
includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more
15 microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a
microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or
20 processing unit is a hardware processor.
[0034] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a
smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing
25 the features of the present disclosure. The user equipment/device may include, but is not limited
to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a
30 processing unit, a storage unit, a detection unit and any other such unit(s) which are required
to implement the features of the present disclosure.
[0035] As used herein, “storage unit” or “memory unit” refers to a machine or computer-
readable medium including any mechanism for storing information in a form readable by a
8

computer or similar machine. For example, a computer-readable medium includes read-only
memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical
storage media, flash memory devices or other types of machine-accessible storage media. The
storage unit stores at least the data that may be required by one or more units of the system to
5 perform their respective functions.
[0036] As used herein “interface” or “user interface refers to a shared boundary across
which two or more separate components of a system exchange information or data. The
interface may also be referred to a set of rules or protocols that define communication or
interaction of one or more modules or one or more units with each other, which also includes
10 the methods, functions, or procedures that may be called.
[0037] All modules, units, components used herein, unless explicitly excluded herein, may
be software modules or hardware processors, the processors being a general-purpose processor,
a special purpose processor, a conventional processor, a digital signal processor (DSP), a
plurality of microprocessors, one or more microprocessors in association with a DSP core, a
15 controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field
Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[0038] As used herein the transceiver unit include at least one receiver and at least one
transmitter configured respectively for receiving and transmitting data, signals, information or
a combination thereof between units/components within the system and/or connected with the
20 system.
[0039] In the 5th Generation core network, during probing of the network, the probe
receives data of a predefined signature (information is organized in a predefined manner). In conventional probing systems (physically probing the network), a probing unit is developed specifically for the predefined signature of the data to be received by a probe from a network
25 node. As a result, when the signature of the data to be received by the probe changes, the
probing unit needs to be again developed, tested and deployed in the field. Therefore, the conventional probing system is less flexible and is inefficient in adapting to the change in data signatures. Thus, there exists an imperative need in the art to develop a method and a system for real-time customization and decoding of call summary logs, which the present disclosure
30 aims to address.
[0040] As discussed in the background section, a significant problem with the prior art is
that traditional systems for decoding call summary logs are not equipped to handle customized
9

or proprietary log formats efficiently. The limitation becomes particularly evident when
dealing with New Radio Summary Log (NRSL), a proprietary log format designed to provide
detailed session information. Existing systems often require manual adjustments or bespoke
software updates to interpret these logs correctly, which can be time-consuming and prone to
5 errors. Furthermore, the inability to automatically adapt to changes in log formats or to enrich
the logs with additional context-specific data (like device or subscriber information) further
complicates the effective monitoring and troubleshooting of radio access network (RAN)
issues. Another issue with conventional systems is their limited proactive monitoring
capabilities. Most systems perform basic parsing and decoding tasks but do not proactively
10 monitor the quality or integrity of the decoding process itself. The lack of proactive monitoring
means that repeated errors or anomalies in log decoding might not be detected promptly, leading to potential delays in addressing network issues or inaccuracies in log data analysis.
[0041] The present disclosure aims to overcome the above-mentioned and other existing
problems in the field of radio access network (RAN) monitoring and diagnostics by introducing
15 a method for real-time customized decoding of call summary logs, specifically tailored for
handling proprietary log formats like the New Radio Summary Log (NRSL). The proposed method enhances efficiency and accuracy by adapting to various log formats without the need for manual adjustments or bespoke software updates, thus addressing a significant limitation of traditional systems. Firstly, the proposed system employs a dynamic decoding process that
20 automatically adjusts to changes in log formats. This is achieved through the reception of
customizable decoding instructions tailored to the specific requirements of the log data being processed. The instructions can be updated in response to changes in log signatures detected by the system, ensuring continuous adaptation to evolving log formats and content without requiring manual intervention. Moreover, the disclosure enhances the monitoring capabilities
25 of traditional systems by implementing proactive monitoring of the quality and integrity of the
decoding process. The proposed system not only parses and decodes the data but also monitors for errors or anomalies in the process. If the system detects issues beyond a predefined threshold, it proactively notifies the end user. The proposed solution allows for timely detection and resolution of potential problems, significantly reducing the delay in addressing network
30 issues and improving the accuracy of log data analysis. The proposed system enriches the
decoded data with device-level and subscriber-level information, providing a more comprehensive view of network events and enhancing the ability to troubleshoot and analyse
10

network performance effectively. This enriched data supports a more detailed and informed analysis, facilitating better business decisions and operational strategies.
[0042] It would be appreciated by the person skilled in the art that the present disclosure
offers a robust solution to the challenges posed by the limited flexibility and reactive nature of
5 traditional call log decoding systems, significantly advancing the field of network diagnostics
and monitoring.
[0043] Hereinafter, exemplary embodiments of the present disclosure will be described
with reference to the accompanying drawings.
[0044] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core
10 (5GC) network architecture, in accordance with exemplary implementation of the present
disclosure. As shown in FIG. 1, the 5GC network architecture [100] includes a user equipment
(UE) [102], a radio access network (RAN) [104], an access and mobility management function
(AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy
(SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific
15 Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection
Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository
Function (NRF) [120], a Policy Control Function (PCF) [122], a Unified Data Management
(UDM) [124], an application function (AF) [126], a User Plane Function (UPF) [128], a data
network (DN) [130], wherein all the components are assumed to be connected to each other in
20 a manner as obvious to the person skilled in the art for implementing features of the present
disclosure.
[0045] Radio Access Network (RAN) [104] is the part of a mobile telecommunications
system that connects user equipment (UE) [102] to the core network (CN) and provides access
to different types of networks (e.g., 5G network). It consists of radio base stations and the radio
25 access technologies that enable wireless communication.
[0046] Access and Mobility Management Function (AMF) [106] is a 5G core network
function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.
30 [0047] Session Management Function (SMF) [108] is a 5G core network function
responsible for managing session-related aspects, such as establishing, modifying, and
11

releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement.
[0048] Service Communication Proxy (SCP) [110] is a network function in the 5G core
network that facilitates communication between other network functions by providing a secure
5 and efficient messaging service. It acts as a mediator for service-based interfaces.
[0049] Authentication Server Function (AUSF) [112] is a network function in the 5G core
responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.
[0050] Network Slice Specific Authentication and Authorization Function (NSSAAF)
10 [114] is a network function that provides authentication and authorization services specific to
network slices. It ensures that UEs can access only the slices for which they are authorized.
[0051] Network Slice Selection Function (NSSF) [116] is a network function responsible
for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.
15 [0052] Network Exposure Function (NEF) [118] is a network function that exposes
capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
[0053] Network Repository Function (NRF) [120] is a network function that acts as a
central repository for information about available network functions and services. It facilitates
20 the discovery and dynamic registration of network functions.
[0054] Policy Control Function (PCF) [122] is a network function responsible for policy
control decisions, such as QoS, charging, and access control, based on subscriber information and network policies.
[0055] Unified Data Management (UDM) [124] is a network function that centralizes the
25 management of subscriber data, including authentication, authorization, and subscription
information.
[0056] Application Function (AF) [126] is a network function that represents external
applications interfacing with the 5G core network to access network capabilities and services.
[0057] User Plane Function (UPF) [128] is a network function responsible for handling
30 user data traffic, including packet routing, forwarding, and QoS enforcement.
12

[0058] Data Network (DN) [130] refers to a network that provides data services to user
equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.
[0059] FIG. 2 illustrates an exemplary block diagram of a computer system [1000] upon
5 which the features of the present disclosure may be implemented in accordance with exemplary
implementation of the present disclosure. In an implementation, the computer system [1000]
may also implement a method for real-time customized decoding of call summary logs utilising
the system. In another implementation, the computer system [1000] itself implements the
method for real-time customized decoding of call summary logs using one or more units
10 configured within the computer system [1000], wherein said one or more units are capable of
implementing the features as disclosed in the present disclosure.
[0060] The computer system [1000] encompasses a wide range of electronic devices
capable of processing data and performing computations. Examples of computer system [1000]
include, but are not limited only to, personal computers, laptops, tablets, smartphones, user
15 equipment (UE), servers, and embedded systems. The devices may operate independently or
as part of a network and can perform a variety of tasks such as data storage, retrieval, and analysis. Additionally, computer system [1000] may include peripheral devices, such as monitors, keyboards, and printers, as well as integrated components within larger electronic systems, showcasing their versatility in various technological applications.
20 [0061] The computer system [1000] may include a bus [1002] or other communication
mechanism for communicating information, and a processor [1004] coupled with bus [1002] for processing information. The processor [1004] may be, for example, a general purpose microprocessor. The computer system [1000] may also include a main memory [1006], such as a random access memory (RAM), or other dynamic storage device, coupled to the bus [1002]
25 for storing information and instructions to be executed by the processor [1004]. The main
memory [1006] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [1004]. Such instructions, when stored in non-transitory storage media accessible to the processor [1004], render the computer system [1000] into a special-purpose machine that is customized to
30 perform the operations specified in the instructions. The computer system [1000] further
includes a read only memory (ROM) [1008] or other static storage device coupled to the bus [1002] for storing static information and instructions for the processor [1004].
13

[0062] A storage device [1010], such as a magnetic disk, optical disk, or solid-state drive
is provided and coupled to the bus [1002] for storing information and instructions. The
computer system [1000] may be coupled via the bus [1002] to a display [1012], such as a
cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display,
5 Organic LED (OLED) display, etc. for displaying information to a computer user. An input
device [1014], including alphanumeric and other keys, touch screen input means, etc. may be
coupled to the bus [1002] for communicating information and command selections to the
processor [1004]. Another type of user input device may be a cursor control [1016], such as a
mouse, a trackball, or cursor direction keys, for communicating direction information and
10 command selections to the processor [1004], and for controlling cursor movement on the
display [1012]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
[0063] The computer system [1000] may implement the techniques described herein using
customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic
15 which in combination with the computer system [1000] causes or programs the computer
system [1000] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computer system [1000] in response to the processor [1004] executing one or more sequences of one or more instructions contained in the main memory [1006]. Such instructions may be read into the main memory [1006] from another
20 storage medium, such as the storage device [1010]. Execution of the sequences of instructions
contained in the main memory [1006] causes the processor [1004] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
[0064] The computer system [1000] also may include a communication interface [1018]
25 coupled to the bus [1002]. The communication interface [1018] provides a two-way data
communication coupling to a network link [1020] that is connected to a local network [1022].
For example, the communication interface [1018] may be an integrated services digital network
(ISDN) card, cable modem, satellite modem, or a modem to provide a data communication
connection to a corresponding type of telephone line. As another example, the communication
30 interface [1018] may be a local area network (LAN) card to provide a data communication
connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [1018] sends and receives electrical,
14

electromagnetic or optical signals that carry digital data streams representing various types of information.
[0065] The computer system [1000] can send messages and receive data, including
program code, through the network(s), the network link [1020] and the communication
5 interface [1018]. In the Internet example, a server [1030] might transmit a requested code for
an application program through the Internet [1028], the ISP [1026], the local network [1022] and the communication interface [1018]. The received code may be executed by the processor [1004] as it is received, and/or stored in the storage device [1010], or other non-volatile storage for later execution.
10 [0066] Referring to FIG. 3, an exemplary block diagram of a system [300] for real-time
customized decoding of call summary logs, is shown, in accordance with the exemplary implementations of the present disclosure. The system [300] comprises at least one network node [302], at least one interface unit [304], at least one processing unit [306], at least one probe manager unit [308], and at least one conductor unit [310]. Also, all of the components/
15 units of the system [300] are assumed to be connected to each other unless otherwise indicated
below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however, the system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an
20 implementation, the system [300] may be present in a user device to implement the features of
the present disclosure. The system [300] may be a part of the user device / or may be independent of but in communication with the user device (may also referred herein as a UE). In another implementation, the system [300] may reside in a server or a network entity. In yet another implementation, the system [300] may reside partly in the server/ network entity and
25 partly in the user device.
[0067] The system [300] is configured for real-time customized decoding of call summary
logs, with the help of the interconnection between the components/units of the system [300].
[0068] The system [300] includes an interface unit [304] configured to receive a set of
instructions, the instructions related to customized decoding of a call summary log data
30 received from the network node [302], wherein the call summary log data comprises headers
and payloads of one or more messages, and wherein the headers and payloads of the data vary based on a version and a message type of the messages in the data. The instructions are received
15

by the interface unit [304] via a manual input of one or more users. For example, in a scenario
where the network node [302] transmits call summary logs in a new version that includes
additional or altered message types. The network node [302] used herein may include one or a
combination of a Next Generation NodeB (gNB), Network Data Analytics Function
5 (NWDAF), an Access and Mobility Management Function (AMF), a Session Management
Function (SMF), Policy Control Function (PCF), an Authentication Server Function (AuSF), and an Application Function (AF).
[0069] Further, the interface unit [304] at least connected with the network node [302] is
responsible for receiving updates or new decoding instructions from a system administrator or
10 an automated update system. The instructions specify how the different headers and payloads
should be processed based on their message types and versions, which may include handling variations in data types such as integers, bytes, or shorts, and adjusting to changes in message structures. In an implementation of the present disclosure, in the 5th Generation core network, the New Radio summary log (NRSL) may be been deployed by the network node [302] (such
15 as Next Generation NodeB (gNB)) to provide a summary of key performance indicators (KPIs)
and events related to operation of 5G New Radio (NR) technology. The NRSL are generated for every subscriber Radio Resource Control (RRC) session in the network and have pre-defined format with set of fields. In the 5th generation core network, an RRC session refers to a communication between a user equipment (UE), such as a smartphone or a mobile device,
20 and the Radio Access Network (RAN) node (such as gNB). For example, the set of instructions
may relate to decoding one or more NRSL data flows. The interface unit [304] is configured to receive the set of instructions from network node [302] (such as gNB) over a Transmission Control Protocol (TCP). A single NRSL message includes headers and payload, whereas multiple NRSL message includes a Call summary log data. The Call summary log data includes
25 headers and payloads. A header contains information of the packet and is attached at the
beginning of the data. The header includes source address, destination address, protocol version, packet length, and the like.
[0070] The system [300] comprises the processing unit [306] connected to the interface
unit [304]. The processing unit [306] configured to identify a probe manager unit [308] for
30 communicating the instructions to a conductor unit [310]. In an implementation of the present
disclosure, the processing unit [306] is connected to the interface unit [304]. Once, the set of instructions for decoding are received by the processing unit [306], the processing unit [306] may identify a probe manager unit [308] to allow the instructions to be sent to the conductor
16

unit [310]. For example, upon receiving a new set of decoding instructions from the interface
unit [304], the processing unit [306] evaluates the instructions to determine their applicability
and compatibility with the existing system configuration. Once validated, the instructions are
then forwarded to the probe manager unit [308]. The probe manager unit [308] serves as the
5 intermediary that ensures these instructions are accurately communicated to the conductor unit
[310], which is responsible for the decoding of the call summary logs. The effective identification and communication process managed by the processing unit [306] facilitates in maintaining the integrity and accuracy of the data decoding process.
[0071] Prior to the interface unit [304] receiving the set of instructions, the processing unit
10 [306] is configured to detect a change in the signature of data received from the network node
[302]. For detecting the change in the signature of data received from the network node [302], the processing unit [306] is configured to monitor the call summary log data received from the network node [302], wherein the monitoring can be one of a continuous monitoring of the data, and a periodic monitoring of the data. For example, continuous monitoring allows the system
15 to detect any change in real-time, ensuring immediate response to modifications in log data
structures or formats. It would be beneficial in scenarios where rapid adjustments are needed, such as during the rollout of new network technologies or standards, where log formats can frequently change. On the other hand, periodic monitoring might be scheduled at specific intervals, suitable for less dynamic environments where changes are less frequent, and
20 predictability is higher. This method conserves system resources while still maintaining a
reasonable level of alertness to changes. Once a change in the data signature is detected, the processing unit [306] initiates protocols to adapt the decoding processes to accommodate the new data format. This might involve dynamically updating the decoding instructions in the interface unit [304] to match the new signature. The detection and adaptation process ensures
25 that the system remains effective in decoding the logs accurately, regardless of changes in the
data structure sent by the network node [302].
[0072] Post the identifying the probe manager unit [308] for communicating the
instructions to the conductor unit [310], the processing unit is configured to transfer the set of
instructions from the interface unit [304] to the probe manager unit [308]; and the probe
30 manager unit [308] is configured to transfer the set of instructions to the conductor unit
[310].Initially, the processing unit [306] receives the set of instructions from the interface unit [304], which acts as the initial recipient of these directives, typically entered by users or generated by automated systems.
17

[0073] Once the processing unit [306] has received these instructions, it is configured to
transfer them directly to the probe manager unit [308]. This step is crucial for maintaining the integrity and fidelity of the instructions, ensuring that no data is lost or altered during transmission.
5 [0074] It would be appreciated by the person skilled in the art that the system ensures that
the data decoding aligns perfectly with the requirements and expectations set out by the network operators or system administrators, allowing for precise and effective analysis of network traffic and events.
[0075] In an implementation of the present disclosure, the processing unit [306] may
10 continuously monitor the call summary log data to detect a change in the signature from the set
of instructions received through the network node [302]. In another implementation of the
present disclosure, the processing unit [306] may monitor the call summary log data at pre¬
determined time intervals to detect a change in the signature from the set of instructions
received through the network node [302]. Once a change in the signature is detected, the
15 changes signature data is segregated from the data and sent to the message broker. For example,
a telecommunications network updates its data formats or protocols as part of an upgrade or
maintenance activity. In such cases, the call summary log data transmitted from the network
node [302] might begin to exhibit new patterns or structures not previously encoded in the
existing set of decoding instructions. By monitoring the data at scheduled intervals, say, every
20 few minutes, the processing unit [306] can promptly detect these deviations from the expected
data signature. Upon detecting a change, the processing unit [306] isolates the altered sections of the data. The segregation allows the system to handle the changed data separately, ensuring that the standard processing of the remaining data continues uninterrupted and without error. The segregated data reflecting the new signature is then forwarded to the message broker.
25 [0076] The probe manager unit [308] is configured to parse the call summary log data,
wherein the call summary log data is parsed byte by byte based on the message type and a size of the one or more messages in the data and send, to the conductor unit [310], the parsed data. In an implementation of the present disclosure, the message broker [510] may parse the NRSL data on the basis of their respective message types, sizes, and data and sent to the designated
30 destination, which in this case is a message queue. The message type may be any key
performance indicator (KPI) including but not limited to performance summary, call summary, and the like. The NRSL message may be parsed in separate bytes. The NRSL message parsed is further sent to the conductor unit [310]. For example, the NRSL data includes various
18

message types such as initial setup requests, handover commands, and status updates, each
with distinct headers and payload structures. The probe manager unit [308] would first identify
the type of each message and then proceed to dissect the data byte by byte, ensuring each
component is correctly interpreted according to its data type, whether it's an integer, byte, short,
5 etc., and the predefined rules for that specific message type. Once the data is parsed, the probe
manager unit [308] packages the formatted data into a structured format suitable for further
processing and analysis. The structured data is then transmitted to the conductor unit [310],
which is responsible for the actual decoding of the data. The conductor unit [310] uses the
information provided by the probe manager to apply the appropriate decoding algorithms,
10 transforming the raw, parsed data into a format that can be easily analyzed and acted upon by
other systems within the network or by network personnel.
[0077] The conductor unit [310] configured to perform the customized decoding of the
data related to call summary logs. For example, once the conductor unit [310] receives the parsed byte-by-byte data from the probe manager unit [308], it applies a series of decoding
15 techniques to handle the unique characteristics of each message type and data structure. This
could include decoding complex encoded fields like IMSI, IMEI, or RSRP levels, or interpreting event codes related to network activities like handovers or call setups and releases. The customization aspect of the decoding process is particularly significant because it allows the conductor unit [310] to adapt to various proprietary formats and updates in NRSL data,
20 ensuring that the system remains flexible and up-to-date with the latest network technologies
and standards. If the unit encounters anomalies or errors during decoding, such as inconsistencies in the expected data formats or repeated failures in decoding certain data types, it triggers alerts or notifications. These notifications inform system administrators or automated response systems about potential issues, allowing for timely interventions and adjustments. The
25 system thus facilitates in maintaining the reliability and accuracy of the data decoding, which
in turn supports effective network management and troubleshooting. In an implementation of the present disclosure, the conductor unit [310] is configured to perform the customized decoding of the parsed NRSL message.
[0078] The processing unit [306] is configured to receive the issue in an event the at least
30 one of the customized decoding of the data, and the parsing of the data fails for a predefined
threshold number of times. While the conductor unit [310] performs the customized decoding of the data related to call summary logs, the processing unit [306] is further configured to receive an issue in at least one of the customized decoding of the data, and the parsing of the
19

data and notify the issue via the interface unit [304]. For example, if during the decoding
process, the conductor unit [310] encounters malformed data or a data format that does not
conform to expected patterns more than a certain number of times, this issue is flagged and
communicated to the processing unit [306]. The predefined threshold might be set based on
5 historical data, operational requirements, or the criticality of the data being processed. The
threshold acts as a trigger point beyond which the system acknowledges a persistent or
significant problem that could impact the quality or reliability of the data processing. Upon
receiving notification of such an issue, the processing unit [306] takes action to document the
error and notify relevant personnel or systems. The notification may be conducted through the
10 interface unit [304], which might, for instance, display an alert on a monitoring dashboard or
send a notification message to system administrators or automated response systems. The notification includes details about the nature of the issue, the specific data involved, and potentially recommended actions to resolve the problem.
[0079] In an implementation of the present disclosure, if the message broker [510] fails to
15 parse the NRSL message for a predetermined period, the unsuccessful parsing message is sent
to the processing unit [306]. While the conductor unit [310] decodes the NRSL message, the conductor unit [310] detects a problem in customized decoding of NRSL and the processing unit [306] receives the problem associated with the decoding. The processing unit [306] sends a notification to the network node [302] (such as gNB).
20 [0080] Referring to FIG. 4, an exemplary method flow diagram [400] for real-time
customized decoding of call summary logs, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [400] is performed by the system [300]. Further, in an implementation, the system [300] may be present in a server device to implement the features of the present disclosure. Also, as shown in Figure 4, the method
25 [400] starts at step [402].
[0081] At step [404], the method comprises receiving a set of instructions, the instructions
related to customized decoding of a call summary log data received from a network node [302],
wherein the call summary log data comprises headers and payloads of one or more messages,
and wherein the headers and payloads of the data vary based on a version and a message type
30 of the messages in the data. The instructions are received via a manual input of one or more
users. For example, in a scenario where the network node [302] transmits call summary logs in a new version that includes additional or altered message types. The network node [302] used herein may include one or a combination of a Next Generation NodeB (gNB), a Network Data
20

Analytics Function (NWDAF), an Access and Mobility Management Function (AMF), a
Session Management Function (SMF), Policy Control Function (PCF), an Authentication
Server Function (AuSF), and an Application Function (AF). The interface unit [304] at least
connected with the network node [302] is responsible for receiving updates or new decoding
5 instructions from a system administrator or an automated update system. The instructions
specify how the different headers and payloads should be processed based on their message types and versions, which may include handling variations in data types such as integers, bytes, or shorts, and adjusting to changes in message structures. In an implementation of the present disclosure, in the 5th Generation core network, the New Radio summary log (NRSL) may be
10 been deployed by the network node [302] (such as Next Generation NodeB (gNB)) to provide
a summary of key performance indicators (KPIs) and events related to operation of 5G New Radio (NR) technology. The NRSL are generated for every subscriber Radio Resource Control (RRC) session in the network and have pre-defined format with set of fields. In the 5th generation core network, an RRC session refers to a communication between a user equipment
15 (UE), such as a smartphone or a mobile device, and the Radio Access Network (RAN) node
(such as gNB). For example, the set of instructions may relate to decoding one or more NRSL data flows. The interface unit [304] is configured to receive the set of instructions from network node [302] (such as gNB) over a Transmission Control Protocol (TCP). A single NRSL message includes headers and payload, whereas multiple NRSL message includes a Call
20 summary log data. The Call summary log data includes headers and payloads. A header
contains information of the packet and is attached at the beginning of the data. The header includes source address, destination address, protocol version, packet length, and the like.
[0082] Prior to the receiving, by the interface unit [304] via the processing unit [306], the
set of instructions, the method comprises detecting a change in signature of the data received
25 from the network node [302]. For detecting the change in the signature of the data received
from the network node [302], the method comprises monitoring the data received from the network node [302], wherein the monitoring can be one of a continuous monitoring of the data, and a periodic monitoring of the data. For example, continuous monitoring allows the system to detect any change in real-time, ensuring immediate response to modifications in log data
30 structures or formats. It would be beneficial in scenarios where rapid adjustments are needed,
such as during the rollout of new network technologies or standards, where log formats can frequently change. On the other hand, periodic monitoring might be scheduled at specific intervals, suitable for less dynamic environments where changes are less frequent, and
21

predictability is higher. This method conserves system resources while still maintaining a
reasonable level of alertness to changes. Once a change in the data signature is detected, the
processing unit [306] initiates protocols to adapt the decoding processes to accommodate the
new data format. This might involve dynamically updating the decoding instructions in the
5 interface unit [304] to match the new signature. The detection and adaptation process ensures
that the system remains effective in decoding the logs accurately, regardless of changes in the data structure sent by the network node [302].
[0083] Next at step [406], the method includes identifying a probe manager unit [308] for
communicating the instructions to a conductor unit [310]. Post the identifying of the probe
10 manager unit [308] for communicating the instructions to the conductor unit [310], the method
comprises transferring to the probe manager unit [308], the set of instructions and transferring, by the probe manager unit [308] to the conductor unit [310], the set of instructions. In an implementation of the present disclosure, the processing unit [306] is connected to the interface unit [304]. Once, the set of instructions for decoding are received by the processing unit [306],
15 the processing unit [306] may identify a probe manager unit [308] to allow the instructions to
be sent to a conductor unit [310]. For example, upon receiving a new set of decoding instructions from the interface unit [304], the processing unit [306] evaluates the instructions to determine their applicability and compatibility with the existing system configuration. Once validated, the instructions are then forwarded to the probe manager unit [308]. The probe
20 manager unit [308] serves as the intermediary that ensures these instructions are accurately
communicated to the conductor unit [310], which is responsible for the decoding of the call summary logs. The effective identification and communication process managed by the processing unit [306] facilitates in maintaining the integrity and accuracy of the data decoding process. In an implementation of the present disclosure, continuous monitoring by the
25 processing unit [306] of the call summary log data to detect a change in the signature from the
set of instructions received through the network node [302]. In another implementation of the present disclosure, monitoring of the call summary log data at pre-determined time intervals to detect a change in the signature from the set of instructions received through the network node [302] by the processing unit [306]. Once a change in the signature is detected, the changes
30 signature data is segregated from the data and sent to the message broker.
[0084] Further at step [408], the method encompasses parsing the call summary log data,
wherein the call summary log data is parsed byte by byte based on the message type and a size of the one or more messages in the data. In an implementation of the present disclosure, the
22

message broker [510] may parse the NRSL data on the basis of their respective message types,
sizes, and data and sent to the designated destination, which in this case is a message queue.
The message type may be any key performance indicator (KPI) including but not limited to
performance summary, call summary, and the like. The NRSL message may be parsed in
5 separate bytes. The NRSL message parsed is further sent to the conductor unit [310]. For
example, the NRSL data includes various message types such as initial setup requests, handover commands, and status updates, each with distinct headers and payload structures. The probe manager unit [308] would first identify the type of each message and then proceed to dissect the data byte by byte, ensuring each component is correctly interpreted according to its
10 data type, whether it's an integer, byte, short, etc., and the predefined rules for that specific
message type. Once the data is parsed, the probe manager unit [308] packages the formatted data into a structured format suitable for further processing and analysis. The structured data is then transmitted to the conductor unit [310], which is responsible for the actual decoding of the data. The conductor unit [310] uses the information provided by the probe manager to apply
15 the appropriate decoding algorithms, transforming the raw, parsed data into a format that can
be easily analysed and acted upon by other systems within the network or by network personnel.
[0085] Next at step [410], the method includes sending to the conductor unit [310], the
parsed data. The performing, by the conductor unit [310], the customized decoding of the data
20 related to call summary logs, further comprises receiving an issue in at least one of the
customized decoding of the data, and the parsing of the data and notifying the issue. The issue is received in an event the at least one of the customized decoding of the data, and the parsing of the data fails for a predefined threshold number of times. In an implementation of the present disclosure, the message broker [510] may parse the NRSL data on the basis of their respective
25 message types, sizes, and data and sent to the designated destination, which in this case is a
message queue. The message type may be any key performance indicator (KPI) including but not limited to performance summary, call summary, and the like. The NRSL message may be parsed in separate bytes. The NRSL message parsed is further sent to the conductor unit [310]. For example, the NRSL data includes various message types such as initial setup requests,
30 handover commands, and status updates, each with distinct headers and payload structures. The
probe manager unit [308] would first identify the type of each message and then proceed to dissect the data byte by byte, ensuring each component is correctly interpreted according to its data type, whether it's an integer, byte, short, etc., and the predefined rules for that specific
23

message type. Once the data is parsed, the probe manager unit [308] packages the formatted
data into a structured format suitable for further processing and analysis. The structured data is
then transmitted to the conductor unit [310], which is responsible for the actual decoding of the
data. The conductor unit [310] uses the information provided by the probe manager to apply
5 the appropriate decoding algorithms, transforming the raw, parsed data into a format that can
be easily analysed and acted upon by other systems within the network or by network personnel.
[0086] Next at step [412], the method includes performing the customized decoding of the
data related to call summary logs. For example, once the conductor unit [310] receives the
10 parsed byte-by-byte data from the probe manager unit [308], it applies a series of decoding
techniques to handle the unique characteristics of each message type and data structure. This could include decoding complex encoded fields like IMSI, IMEI, or RSRP levels, or interpreting event codes related to network activities like handovers or call setups and releases. The customization aspect of the decoding process is particularly significant because it allows
15 the conductor unit [310] to adapt to various proprietary formats and updates in NRSL data,
ensuring that the system remains flexible and up-to-date with the latest network technologies and standards. If the unit encounters anomalies or errors during decoding, such as inconsistencies in the expected data formats or repeated failures in decoding certain data types, it triggers alerts or notifications. These notifications inform system administrators or automated
20 response systems about potential issues, allowing for timely interventions and adjustments. The
system thus facilitates in maintaining the reliability and accuracy of the data decoding, which in turn supports effective network management and troubleshooting. In an implementation of the present disclosure, the conductor unit [310] is configured to perform the customized decoding of the parsed NRSL message.
25 [0087] Thereafter, the method terminates at step [414].
[0088] Referring to FIG. 5, it illustrates an exemplary signalling flow diagram indicating
an exemplary process for real-time customized decoding of call summary log data, in accordance with exemplary embodiments of the present disclosure.
[0089] The flow begins with various Next Generation NodeB (gNB) units, including gNB
30 [502], gNB [504], and gNB [506]. The gNB units [502], [504], [506] are responsible for
collecting NRSL data directly from subscriber sessions within the network. Each gNB is
24

configured to gather comprehensive performance indicators and event logs for monitoring the state and efficacy of the network's 5G operations.
[0090] The data is then transmitted over a TCP connection to the probe manager unit (such
as Xprobe [508]). The probe manager unit (such as Xprobe [508]) acts as the primary receiving
5 point and is configured to handle the incoming data. It receives specific sets of instructions
related to the decoding of NRSL data, which may include headers and payloads of messages. These messages vary based on version and data type, necessitating a flexible and dynamic approach to their decoding.
[0091] Once probe manager unit (such as Xprobe [508]) processes the initial data, it
10 segregates the NRSL data based on data type and message size. This segregation allows for a
more organized and targeted approach to data parsing, which is carried out by the message brokers [510]. The message broker [510] parse the data byte by byte, carefully interpreting each piece according to its specific characteristics and preparing it for further processing.
[0092] The parsed data is then sent to the conductor unit [310], which performs the
15 decoding tasks. The conductor unit [310] transforms the raw, parsed data into a format that is
usable for diagnostics and monitoring, ensuring that the decoding is successful and accurately reflects the data's intent and content.
[0093] Post-decoding, the data undergoes several more stages of processing that includes:
• Normalizer [514]: The unit standardizes the decoded data to ensure uniformity across
20 various data sets, making it easier to integrate and analyze on a broader scale.
• AIDR Writer [518]: It automatically detects and responds to network incidents or anomalies in real-time, enhancing the system’s responsiveness to potential issues.
• Ingestion Layer [520]: Here, the data is prepared for storage and further processing, funnelling it into systems like the Distributed File System [532] for eventual retrieval
25 and analysis.
[0094] Further, the data reaches the Graphical User Interface [516A], where it becomes
accessible to end-users for monitoring and management purposes. The GUI [516A] is essential for providing a user-friendly visualization of the data, supporting efficient configuration and oversight of network operations.
30 [0095] The data also passes through the workflow [516], which enhances operational
efficiency by automating and optimizing various backend processes. The Workflow's output is
25

then processed by the Computation Engine [530], which is tasked with analysing large volumes of data for deep insights and strategic decision-making.
[0096] The refined data is stored in the Database [522] and subsequently processed by
artificial intelligence/machine learning (AI/ML) techniques within the AI/ML unit [524]. The
5 AI/ML techniques are configured to perform advanced analysis, such as predictive
maintenance and fraud detection, contributing significantly to the network's proactive management strategies.
[0097] Finally, the data circulates through the Computation Layer [534], where it is further
analysed and refined, ensuring that every piece of information extracted from the NRSL data
10 is utilized to its fullest potential to maintain and enhance network performance.
[0098] The present disclosure further discloses a user equipment comprising a system for
real-time customized decoding of call summary logs. The system further comprising an interface unit [304]. The interface unit [304] is configured to receive a set of instructions, the instructions related to customized decoding of a call summary log data received from the
15 network node [302], wherein the call summary log data comprises headers and payloads of one
or more messages, and wherein the headers and payloads of the data vary based on a version and a message type of the messages in the data. The system further includes a processing unit [306] connected to the interface unit [304]. The processing unit [306] is configured to identify a probe manager unit [308] for communicating the instructions to a conductor unit [310]. The
20 probe manager unit [308] is configured to parse the call summary log data, wherein the call
summary log data is parsed byte by byte based on the message type and a size of the one or more messages in the data and send, to the conductor unit [310], the parsed data. The system further includes the conductor unit [310] configured to perform the customized decoding of the data related to call summary logs.
25 [0099] The present disclosure further discloses a non-transitory computer readable storage
medium storing instructions for real-time customized decoding of call summary logs, the storage medium comprising executable code which, when executed by one or more units of a system, causes: an interface unit [304] to: receive a set of instructions, the instructions related to customized decoding of a call summary log data received from the network node [302],
30 wherein the call summary log data comprises headers and payloads of one or more messages,
and wherein the headers and payloads of the data vary based on a version and a message type of the messages in the data; a processing unit [306] connected to the interface unit [304], the

processing unit [306] to: identify a probe manager unit [308] for communicating the
instructions to a conductor unit [310]; the probe manager unit [308] to: parse the call summary
log data, wherein the call summary log data is parsed byte by byte based on the message type
and a size of the one or more messages in the data; and send, to the conductor unit [310], the
5 parsed data; and the conductor unit [310] to: perform the customized decoding of the data
related to call summary logs.
[00100] As is evident from the above, the present disclosure provides a technically
advanced solution for real-time customized decoding of call summary logs. The present
solution provides a system and a method for real-time customization and decoding of call
10 summary logs that can adapt to a change in data signature received by the probe without
needing to again develop, test and deploy a probing software. The present solution provides a solution that adapts to a change in data signature without needing to stop probing a network.
[00101] Further, in accordance with the present disclosure, it is to be acknowledged that the
functionality described for the various the components/units can be implemented
15 interchangeably. While specific embodiments may disclose a particular functionality of these
units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the
20 intended functionality described herein, are considered to be encompassed within the scope of
the present disclosure.
[00102] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and that many
changes can be made to the implementations without departing from the principles of the
25 present disclosure. These and other changes in the implementations of the present disclosure
will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

5
We Claim:
1. A method for real-time customized decoding of call summary logs, the method
comprising:
receiving a set of instructions, the instructions related to customized decoding of a
10 call summary log data received from a network node [302], wherein the call summary
log data comprises headers and payloads of one or more messages, and wherein the
headers and payloads of the data vary based on a version and a message type of the
messages in the data;
identifying a probe manager unit [308] for communicating the instructions to a
15 conductor unit [310];
parsing the call summary log data, wherein the call summary log data is parsed byte by byte based on the message type and a size of the one or more messages in the data;
sending to the conductor unit [310], the parsed data; and
performing the customized decoding of the data related to call summary logs.
20
2. The method as claimed in claim 1, wherein post the identifying the probe manager unit
[308] for communicating the instructions to the conductor unit [310], the method
comprises:
transferring to the probe manager unit [308], the set of instructions; and
25 transferring, by the probe manager unit [308] to the conductor unit [310], the set of
instructions.
3. The method as claimed in claim 1, wherein prior to the receiving, by the interface unit
[304] via the processing unit [306], the set of instructions, the method comprises:
30 detecting a change in signature of the data received from the network node [302].
4. The method as claimed in claim 1, wherein for detecting the change in the signature of
the data received from the network node [302], the method comprises:
28

5 monitoring the data received from the network node [302], wherein the monitoring
can be one of a continuous monitoring of the data, and a periodic monitoring of the data.
5. The method as claimed in claim 1, wherein the performing, by the conductor unit [310],
the customized decoding of the data related to call summary logs, further comprises:
10 receiving an issue in at least one of the customized decoding of the data, and the
parsing of the data; and
notifying the issue.
6. The method as claimed in claim 5, wherein the issue is received in an event the at least
15 one of the customized decoding of the data, and the parsing of the data fails for a
predefined threshold number of times.
7. A system [300] for real-time customized decoding of call summary logs, the system
comprising:
20 an interface unit [304] configured to:
receive a set of instructions, the instructions related to customized decoding
of a call summary log data received from the network node [302], wherein the call
summary log data comprises headers and payloads of one or more messages, and
wherein the headers and payloads of the data vary based on a version and a message
25 type of the messages in the data;
a processing unit [306] connected to the interface unit [304], the processing unit [306] configured to:
identify a probe manager unit [308] for communicating the instructions to a conductor unit [310];
30 the probe manager unit [308] configured to:
parse the call summary log data, wherein the call summary log data is parsed byte by byte based on the message type and a size of the one or more messages in the data; and

5 send, to the conductor unit [310], the parsed data; and
the conductor unit [310] configured to:
perform the customized decoding of the data related to call summary logs.
8. The system as claimed in claim 7, wherein post the identifying the probe manager unit
10 [308] for communicating the instructions to the conductor unit [310], the processing unit
is configured to transfer the set of instructions from the interface unit [304] to the probe
manager unit [308]; and the probe manager unit [308] is configured to transfer the set of
instructions to the conductor unit [310].
15 9. The system [300] as claimed in claim 7, wherein prior to the interface unit [304] receiving
the set of instructions, the processing unit [306] is configured to:
detect a change in the signature of data received from the network node [].
10. The system [300] as claimed in claim 7, wherein for detecting the change in the signature
20 of data received from the network node [302], the processing unit [306] is configured to:
monitor the call summary log data received from the network node [302], wherein the monitoring can be one of a continuous monitoring of the data, and a periodic monitoring of the data.
25 11. The system [300] as claimed in claim 7, wherein while the conductor unit [310] performs
the customized decoding of the data related to call summary logs, the processing unit [306] is further configured to:
receive an issue in at least one of the customized decoding of the data, and the parsing of the data; and
30 notify the issue via the interface unit [304].

5 12. The system [300] as claimed in claim 11, wherein the processing unit [306] is configured
to receive the issue in an event the at least one of the customized decoding of the data, and the parsing of the data fails for a predefined threshold number of times.
13. A user equipment (UE) [102] comprising a system for real-time customized decoding of
10 call summary logs, the system further comprising:
an interface unit [304] configured to:
receive a set of instructions, the instructions related to customized decoding
of a call summary log data received from the network node [302], wherein the call
summary log data comprises headers and payloads of one or more messages, and
15 wherein the headers and payloads of the data vary based on a version and a message
type of the messages in the data;
a processing unit [306] connected to the interface unit [304], the processing unit [306] configured to:
identify a probe manager unit [308] for communicating the instructions to a
20 conductor unit [310];
the probe manager unit [308] configured to:
parse the call summary log data, wherein the call summary log data is parsed byte by byte based on the message type and a size of the one or more messages in the data; and
25 send, to the conductor unit [310], the parsed data; and
the conductor unit [310] configured to:
perform the customized decoding of the data related to call summary logs.
Dated this 11th day of July 2023
30 (GARIMA SAHNEY)
IN/PA-1826 AGENT FOR THE APPLICANT(S)
OF SAIKRISHNA & ASSOCIATES
31