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 IDENTIFICATION OF
PROBLEM CAUSING NETWORK NODES AND SESSIONS
USING LADDER DIAGRAM”
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 IDENTIFICATION OF PROBLEM CAUSING NETWORK NODES AND SESSIONS USING LADDER
DIAGRAM
FIELD OF INVENTION
[0001] Embodiments of the present disclosure generally relate to the field of wireless communication systems. More particularly, embodiments of the present disclosure relate to methods and systems for identification of problem causing network nodes and sessions using ladder diagram.
BACKGROUND
[0002] The following description of 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 be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[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. 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 generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] In order to monitor and analyze the network performance and troubleshoot the network (as and when needed), conventional systems would require physically probing the network. For continuous monitoring, analysis and troubleshooting of the network, physical probing would need to be performed multiple times. It apparent that such a large number of instances of physical probing of the network would be resource intensive, time consuming and inefficient for effective monitoring, analyzing and troubleshooting of the network. Further, for monitoring and analyzing the network performance, high volume of records received at every instance, it becomes cumbersome for end user to debug an issue where is occurring or on which node the issue is occurring.
[0005] Further, the conventional systems and methods for identification of problem causing nodes and session does not involve analysis of a ladder diagram. Generally, the volume and complexity of data is very high in conventionally constructed ladder diagrams. Such prohibitively high volume and complexity of data hinders swift identification of problem causing nodes and session therewith. As a result, the troubleshooting or any other analysis process becomes slow, computationally expensive and tedious at times. This problem is further compounded by the high volume of summary logs of communication (SLC) at every instance, and it becomes cumbersome for end user to debug an issue.
[0006] Thus, there exists an imperative need in the art to develop a method and a system for identification of at least one of one or more problem causing network nodes and one or more problem causing sessions, which the present disclosure aims to address.

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 identification of one of one or more problem causing network nodes and one or more problem causing sessions. The method includes receiving, by a transceiver unit, a summary log data of a session and one or more messages of the session, wherein the session is one of a call session and a data exchange session. Next, the method includes performing, by an analysis unit, an isolation and decode procedure to identify a first parameter and a second parameter related to the summary log data, wherein the first parameter is associated with a base station, and the second parameter is associated with a session details of the session. Next, the method includes stitching, by a stitching unit, at least the first parameter and the second parameter with at least the one or more messages of the session to generate a unique correlation on an enriched data. Next, the method includes creating, by a ladder diagram creation unit, a ladder diagram based on the unique correlation on the enriched data. Thereafter, the method includes identifying, by the analysis unit, at least one of the one or more problem-causing network nodes and the one or more problem-causing sessions based on the ladder diagram.
[0009] In an exemplary aspect of the present disclosure, the first parameter is a trace reference, and the second parameter is a trace recording session reference.

[0010] In an exemplary aspect of the present disclosure, the method further comprises receiving, by the transceiver unit from one or more base stations, the first parameter and the second parameter.
[0011] In an exemplary aspect of the present disclosure, the method is implemented in a trace collection entity (TCE).
[0012] In an exemplary aspect of the present disclosure, the method further comprises prior to the receiving, by the transceiver unit, the summary log data of the session and the one or more messages of the session, the method comprises: receiving, by the transceiver unit via a user interface, a subscriber information and a time range value for identification of at least one of the one or more problem-causing network nodes and the one or more problem-causing sessions.
[0013] Another aspect of the present disclosure may relate to a system for identification of one of one or more problem causing network nodes and one or more problem causing sessions. The system comprising a transceiver unit configured to receive a summary log data of a session and one or more messages of the session, wherein the session is one of a call session and a data exchange session; an analysis unit connected at least to the transceiver unit, the analysis unit configured to perform an isolation and decode procedure to identify a first parameter and a second parameter related to the summary log data, wherein the first parameter is associated with a base station of, and the second parameter is associated with a session details of the session; a stitching unit connected at least to the analysis unit, the stitching unit configured to stitch, at least the first parameter and the second parameter with at least the one or more messages of the session to generate a unique correlation on an enriched data; a ladder diagram creation unit connected to at least the stitching unit, the ladder diagram creation unit configured to create a ladder diagram based on the unique correlation on the enriched data; wherein the analysis unit is further configured to identify at least one of the one or

more problem causing network nodes and the one or more sessions based on the ladder diagram.
[0014] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for identification of one of one or more problem causing network nodes and one or more problem causing sessions, the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver unit of the system to receive a summary log data of a session and one or more messages of the session, wherein the session is one of a call session and a data exchange session; an analysis unit of the system to perform an isolation and decode procedure to identify a first parameter and a second parameter related to the summary log data, wherein the first parameter is associated with a base station, and the second parameter is associated with a session details of the session; a stitching unit of the system to stitch at least the first parameter and the second parameter with at least the one or more messages of the session to generate a unique correlation on an enriched data; a ladder diagram creation unit of the system to create a ladder diagram based on the unique correlation on the enriched data; and the analysis unit of the system to identify at least one of the one or more problem-causing network nodes and the one or more problem-causing sessions based on the ladder diagram.
[0015] Yet another aspect of the present disclosure may relate to a user equipment comprising a system for identification of one of one or more problem causing network nodes and one or more problem causing sessions, the system comprising a transceiver unit configured to receive a summary log data of a session and one or more messages of the session, wherein the session is one of a call session and a data exchange session; an analysis unit connected at least to the transceiver unit, the analysis unit configured to perform an isolation and decode procedure to identify a first parameter and a second parameter related to the summary log data, wherein the first parameter is associated with a base station of, and the second parameter is

associated with a session details of the session; a stitching unit connected at least to
the analysis unit, the stitching unit configured to stitch, at least the first parameter
and the second parameter with at least the one or more messages of the session to
generate a unique correlation on an enriched data; a ladder diagram creation unit
5 connected to at least the stitching unit, the ladder diagram creation unit configured
to create a ladder diagram based on the unique correlation on the enriched data; wherein the analysis unit is further configured to identify at least one of the one or more problem causing network nodes and the one or more sessions based on the ladder diagram. 10
OBJECTS OF THE INVENTION
[0016] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below. 15
[0017] It is an object of the present disclosure to provide a system and a method for quick identification for problem causing network nodes and session using ladder diagram.
20 [0018] It is another object of the present disclosure to provide a system and a
method for quick identification for problem causing nodes in a network and session therewith, which is efficient enough to analyse large volume of data and accurately identify problem causing nodes in a network and session therewith.
25 [0019] It is yet another object of the present disclosure to help the end user to debug,
troubleshoot and find the node which is causing the network issue.
DESCRIPTION OF THE DRAWINGS
7

[0020] 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,
5 emphasis instead being placed upon clearly illustrating the principles of the present
disclosure. Also, the embodiments shown in the 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
10 drawings includes disclosure of electrical components or circuitry commonly used
to implement such components.
[0021] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture. 15
[0022] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
20 [0023] FIG. 3 illustrates an exemplary block diagram of a system for identification
of one of one or more problem causing network nodes and one or more problem causing sessions, in accordance with exemplary implementations of the present disclosure.
25 [0024] FIG. 4 illustrates a method flow diagram for identification of one of one or
more problem causing network nodes and one or more problem causing sessions in accordance with exemplary implementations of the present disclosure.
8

[0025] FIG. 5 illustrates a network flow block diagram for identification of one of one or more problem causing network nodes and one or more problem causing sessions, in accordance with exemplary implementations of the present disclosure.
5 [0026] FIG. 6 illustrates a system block diagram for identification of one of one or
more problem causing network nodes and one or more problem causing sessions, in accordance with exemplary implementations of the present disclosure.
[0027] The foregoing shall be more apparent from the following more detailed
10 description of the disclosure.
DETAILED DESCRIPTION
[0028] In the following description, for the purposes of explanation, various
15 specific details are set forth in order to provide a thorough understanding of
embodiments of the present 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
20 address any of the problems discussed above or might address only some of the
problems discussed above.
[0029] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather,
25 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 spirit and scope of the disclosure as set forth.
30
9

[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
5 may be shown as components in block 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
10 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 operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.
15
[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
20 necessarily to be construed as preferred or 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
25 to the term “comprising” as an open transition word without precluding any
additional or 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
30 processing instructions. A processor may be a general-purpose processor, a special
10

purpose processor, a conventional processor, a digital signal processor, a plurality
of microprocessors, one or more 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
5 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 processing unit is a hardware processor.
10 [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 the features of the present disclosure. The
15 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
20 a transceiver unit, a 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
25 form readable by a 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 perform their respective
30 functions.
11

[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
5 communication or interaction of one or more modules or one or more units with
each other, which also includes the methods, functions, or procedures that may be called.
[0037] All modules, units, components used herein, unless explicitly excluded
10 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 controller, a microcontroller,
Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array
15 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
20 and/or connected with the system.
[0039] As used herein, the terms "first", "second", and the like, herein do not denote any order, ranking, quantity, or importance, but rather are used to distinguish one element from another. 25
[0040] As used herein, the ladder diagram refers to a graphical representation to depict the logical flow of operations or signals. The ladder diagram shows the sequence of control and the interconnections between different devices. The ladder diagram illustrates the sequence of events and message exchanges between entities
12

during a call or session, ensuring clarity in understanding the process and troubleshooting issues.
[0041] A summary log of communication (SLC) contains all information pertaining
5 to a session of data communication performed by a user equipment. Information in
a SLC is encoded in the form of one or more parameters, which are later decoded
for further analysis, as and when needed. A network node is unit which acts as a
connection point among devices that can receive and send data from one endpoint
to the other. A problem causing node is a network node which results in bad user
10 experience. A bad user experience can be either call drop, network outage or the
like. A session is initiated by a user by initiating data transfer and is ended by said user. There can be multiple sessions with a problem causing nodes. It is noted that the network node is a hardware executing a set of instructions.
15 [0042] As discussed in the background section, the volume and complexity of data
for identification of problem causing network nodes and session therewith is very high in conventionally constructed ladder diagrams. Such prohibitively high volume and complexity of data hinders swift identification of problem causing nodes and session therewith.
20
[0043] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing method and system for identification of at least one of one or more problem causing network nodes and one or more problem causing sessions.
25
[0044] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (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
30 (RAN) [104], an access and mobility management function (AMF) [106], a Session
13

Management Function (SMF) [108], a Service Communication Proxy (SCP) [110],
an Authentication Server Function (AUSF) [112], a Network Slice Specific
Authentication and Authorization Function (NSSAAF) [114], a Network Slice
Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a
5 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 a manner as obvious to the person skilled in the art for implementing features of the present disclosure.
10
[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 access technologies that enable
15 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
20 procedures like handovers and paging.
[0047] Session Management Function (SMF) [108] is a 5G core network function
responsible for managing session-related aspects, such as establishing, modifying,
and releasing sessions. It coordinates with the User Plane Function (UPF) for data
25 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 and efficient messaging service. It acts as a mediator for service-
30 based interfaces.
14

[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. 5
[0050] Network Slice Specific Authentication and Authorization Function (NSSAAF) [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. 10
[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
20 as a central repository for information about available network functions and
services. It facilitates 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
25 subscriber information and network policies.
[0055] Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information. 30
15

[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.
5 [0057] User Plane Function (UPF) [128] is a network function responsible for
handling user data traffic, including packet routing, forwarding, and QoS enforcement.
[0058] Data Network (DN) [130] refers to a network that provides data services to
10 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 computing device [200] (also referred to herein as a computer system [200]) upon which the features of the
15 present disclosure may be implemented in accordance with exemplary
implementation of the present disclosure. In an implementation, the computing device [200] may also implement a method for identification of at least one of one or more problem causing network nodes and one or more problem causing sessions utilising the system. In another implementation, the computing device [200] itself
20 implements the method for identification of at least one of one or more problem
causing network nodes and one or more problem causing sessions using one or more units configured within the computing device [200], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
25 [0060] The computing device [200] encompasses a wide range of electronic
devices capable of processing data and performing computations. Examples of computing device [200] include, but are not limited only to, personal computers, laptops, tablets, smartphones, servers, and embedded systems. The devices may operate independently or as part of a network and can perform a variety of tasks
30 such as data storage, retrieval, and analysis. Additionally, computing device [200]
16

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.
5 [0061] The computing device [200] may include a bus [202] or other
communication mechanism for communicating information, and a processor [204] coupled with bus [202] for processing information. The processor [204] may be, for example, a general-purpose microprocessor. The computing device [200] may also include a main memory [206], such as a random-access memory (RAM), or other
10 dynamic storage device, coupled to the bus [202] for storing information and
instructions to be executed by the processor [204]. The main memory [206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [204]. Such instructions, when stored in non-transitory storage media accessible to the processor
15 [204], render the computing device [200] into a special-purpose machine that is
customized to perform the operations specified in the instructions. The computing device [200] further includes a read only memory (ROM) [208] or other static storage device coupled to the bus [202] for storing static information and instructions for the processor [204].
20
[0062] A storage device [210], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [202] for storing information and instructions. The computing device [200] may be coupled via the bus [202] to a display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
25 Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
displaying information to a computer user. An input device [214], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [202] for communicating information and command selections to the processor [204]. Another type of user input device may be a cursor controller [216], such as
30 a mouse, a trackball, or cursor direction keys, for communicating direction
17

information and command selections to the processor [204], and for controlling cursor movement on the display [212]. The 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. 5
[0063] The computing device [200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [200] causes or programs the computing device [200] to be a special-purpose machine.
10 According to one implementation, the techniques herein are performed by the
computing device [200] in response to the processor [204] executing one or more sequences of one or more instructions contained in the main memory [206]. Such instructions may be read into the main memory [206] from another storage medium, such as the storage device [210]. Execution of the sequences of instructions
15 contained in the main memory [206] causes the processor [204] 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.
20 [0064] The computing device [200] also may include a communication interface
[218] coupled to the bus [202]. The communication interface [218] provides a two-way data communication coupling to a network link [220] that is connected to a local network [222]. For example, the communication interface [218] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or
25 a modem to provide a data communication connection to a corresponding type of
telephone line. As another example, the communication interface [218] 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 [218] sends and receives electrical,
18

electromagnetic or optical signals that carry digital data streams representing various types of information.
[0065] The computing device [200] can send messages and receive data, including
5 program code, through the network(s), the network link [220] and the
communication interface [218]. In the Internet example, a server [230] might
transmit a requested code for an application program through the Internet [228], the
ISP [226], the host [224], the local network [222] and the communication interface
[218]. The received code may be executed by the processor [204] as it is received,
10 and/or stored in the storage device [210], or other non-volatile storage for later
execution.
[0066] Referring to FIG. 3, an exemplary block diagram of a system [300] for identification of one of one or more problem causing network nodes and one or
15 more problem causing sessions, is shown, in accordance with the exemplary
implementations of the present disclosure. The system [300] comprises at least one transceiver unit [302], at least one analysis unit [304], at least one stitching unit [306] and at least one ladder diagram creation unit [308]. Also, all of the components/ units of the system [300] are assumed to be connected to each other
20 unless otherwise indicated below. As shown in the FIG. 3 all units shown within
the system [300] 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
25 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 [102]). In another implementation, the system [300] may reside in a server or a network entity. In yet another implementation, the system
30 [300] may reside partly in the server/ network entity and partly in the user device.
19

[0067] The system [300] is configured for identification of one or more problem causing network nodes and one or more problem causing sessions, with the help of the interconnection between the components/units of the system [300].
5 [0068] Further, a “cell traffic trace” includes subscriber and equipment trace that
provides a detailed information at call level on one or more specific mobile(s) (i.e.
UEs). The detailed information is an additional source of information to investigate
performance measurement and allows a deep investigation for monitoring and
optimisation operations. The cell traffic trace plays a major role in activities such
10 as determination of the root cause of a malfunctioning mobile, advanced
troubleshooting, optimisation of resource usage and quality, radio frequency coverage control and capacity improvement, dropped call analysis, core network and access network end-to-end procedure validation.
15 [0069] As used herein, the “TR” identifies a trace session and is a globally unique
identification (ID). The method to generate the TR unique ID is to divide the TR into Mobile country code (MCC), Mobile network code (MNC) and Trace Identification Data (ID).
20 [0070] As used herein, “Trace Session” identifies time interval started with a Trace
Session Activation and lasts until the Deactivation of that specific Trace Session.
[0071] As used herein, the “MCC” is a unique identifier used in conjunction with
a mobile network code (MNC) to identify a mobile network operator. The MNC is
25 a unique identifier used in conjunction with the MCC to identify a mobile network
operator. Also, trace ID is an identification data that is present in a hexadecimal format. The trace ID may be numeric, alphanumeric or alphabetic.
[0072] As used herein, “trace recording session” is a time interval within a trace
30 session while trace records are generated for a subscriber or user equipment (UE)
20

being traced and the trace recording session reference identifies a trace recording session within a trace session.
[0073] As used herein, the “TRSR” identifies a Trace Recording Session within a
5 Trace Session. The Trace Recording Session Reference shall be unique within a
Trace Session.
[0074] As used herein, an “International Mobile Subscriber Identity (IMSI)
information” is a number that uniquely identifies every user of a network. The IMSI
10 information may be stored as a 64-bit field and is transmitted by a user equipment
to the network. The IMEI information is a unique 15-digit serial number for identifying the user equipment.
[0075] The system [300] comprises at least one transceiver unit. The transceiver
15 unit [302] is configured to receive a summary log data of a session and one or more
messages of the session. The session is one of a call session (such as voice call) and
a data exchange session (such as multimedia exchange). In an exemplary aspect,
the summary log data may comprise at least one of subscriber information, location,
used network node(s), type of session (such as call or data), and the like. For
20 example, in a call session, the summary log data may include the call initiation time,
the duration of the call, the identities of the calling and receiving parties, and any
disconnection events. In a data exchange session, the summary log data might
consist of the session start time, the data volume transferred, the data transfer rate,
and any error occurrences during the data exchange. For the call session, the one or
25 more messages might include signalling messages exchanged between the devices
to establish and maintain the call. For the data exchange session, the one or more messages could encompass data packets transferred, acknowledgment messages, payload messages and error messages.
30 [0076] In an exemplary aspect, the transceiver unit [302] prior to the receiving of
the summary log data of the session and the one or more messages of the session
21

may receive, via a user interface, a subscriber information and a time range value
for identification of at least one of the one or more problem-causing network nodes
and the one or more problem-causing sessions. For monitoring and analysing the
network performance, the transceiver unit [302] may receive details of the
5 subscriber and time period range (such as pre-configured hour(s), day(s)) from the
network administrator for identifying one of the one or more problem-causing network nodes and the one or more problem-causing sessions. In an exemplary aspect, the network nodes may be such as, but not limited to, RAN, base station, network functions (such as Access and Mobility Management Function (AMF),
10 Session Management Function (SMF) etc.) and the like. In an exemplary aspect,
the session may be one of the call sessions and the data exchange session. In an exemplary aspect, the transceiver unit [302] may configure to receive, from one or more base stations, the first parameter and the second parameter. The first parameter is a trace reference (TR), and the second parameter is a trace recording session
15 reference (TRSR).
[0077] The system [300] comprises at least one analysis unit [304] connected at least to the transceiver unit [302]. The analysis unit [304] is configured to perform an isolation and decode procedure to identify a first parameter and a second
20 parameter related to the summary log data, wherein the first parameter is associated
with a base station, and the second parameter is associated with a session detail of the session. The isolation and decode procedures include extracting and separating relevant information from the summary log data for identifying the first parameter and the second parameter for further analysis and troubleshooting.
25
[0078] In an exemplary aspect, isolation and decode procedure is done based on a specified grammar, which tells analysis unit [304] to read certain number of bytes for the first parameter and certain number of bytes for the second parameter and so on. As used herein, specified grammar refers to technique of decoding the incoming
22

data. It specifies at least one of the data fields and its position in the incoming data, its data type and its decoding procedure.
[0079] The analysis unit [304] may perform the isolation and decode procedure to
5 identify the first parameter and the second parameter related to the summary log
data received from the transceiver unit [302]. The first parameter is associated with a base station, and the second parameter is associated with a session detail of the session. The first parameter is trace reference (TR), and the second parameter is trace recording session reference (TRSR). The TR parameter may identify the base
10 station or gNB in 5G network and TRSR parameter may identify the unique session
within base station or gNB in 5G network. By performing the isolation and decode procedure, the analysis unit [304] extracts the TR parameter and TRSR parameter from the summary log data. For example, in a scenario where multiple users are connected to the same base station, the TR helps identify which base station is
15 handling the user’s connection, the TRSR facilitates in ensuring that the specific
session of the user is correctly identified among multiple sessions.
[0080] The system [300] comprises at least one stitching unit [306] connected at least to the analysis unit [304]. The stitching unit [306] is configured to stitch, at
20 least the first parameter and the second parameter with at least the one or more
messages of the session to generate a unique correlation on an enriched data. The stitching corresponds to combining the first parameter (such as the trace reference i.e. TR parameter) and the second parameter (such as the trace recording session reference i.e. TRSR parameter) with the one or more messages of the session for
25 generating the unique correlation on enriched data. The stitching facilitates in
creating a dataset that uniquely correlates all the information related to the session to link the base station identifier and the session identifier with the one or more messages exchanged during the session, providing a coherent and enriched view of the session data. For example, in a 5G network, the first parameter (trace reference)
30 might be a unique identifier for a gNB, and the second parameter (trace recording
23

session reference) might be a unique identifier for the specific session handled by the gNB. The one or more messages of the session could include signalling messages, data packets, and control messages exchanged between the user equipment and the network. 5
[0081] By stitching the first parameter and the second parameter with the one or more messages of the session, the stitching unit [306] generates a unique correlation (such as a dataset that allows for detailed analysis of the session) for on the enriched data. The enriched data includes not only the one or more messages of the session
10 but also the context provided by the trace reference and trace recording session
reference. The context facilitates in understanding the flow of the session, identifying where issues may have occurred, and determining the specific network nodes involved. For example, if a user experiences a dropped call, the stitching unit [306] would stitch (such as combine) the trace reference, trace recording session
15 reference, and the one or more messages exchanged during the call. The stitching
(such as combination) helps in identifying whether the issue occurred at the gNB, during the handover process, or due to some signalling failure. The enriched data thus provides a clear and detailed picture of the session, enabling precise troubleshooting and problem resolution.
20
[0082] The system [300] comprises at least one ladder diagram creation unit [308] connected to at least the stitching unit [306]. The ladder diagram creation unit [308] is configured to create a ladder diagram based on the unique correlation on the enriched data, wherein the analysis unit [304] is further configured to identify at
25 least one of the one or more problem causing network nodes and the one or more
sessions based on the ladder diagram. The ladder diagram creation unit [308] generates a visual representation of the session data, which is organized in a sequential manner to illustrate the interaction between network nodes and the user equipment. In response to the generated unique co-relation, the ladder diagram
30 creation unit [308] may create the ladder diagram. The ladder diagram may capture
24

all the information related to the call or data exchange session performed by the
subscriber. The ladder diagram may represent the visual representation of network
with network elements. For example, in a call session, the ladder diagram might
show the initial call setup messages sent from the user equipment to the base station,
5 followed by authentication messages between the base station and the core network,
and finally the establishment of the call. Each message is plotted in order, with time progressing from top to bottom. This format helps in understanding the exact sequence of events and identifying any anomalies or delays that may have occurred.
10 [0083] In an example, if a call drops unexpectedly, the ladder diagram can highlight
where the call failed, whether it was during the handover between base stations or due to a signalling error. The clear visualization provided by the ladder diagram aids network engineers in pinpointing the exact location and cause of the problem. The analysis unit [304], using the ladder diagram, can then identify the specific
15 network node or session that is causing the issue, facilitating targeted
troubleshooting and resolution.
[0084] The analysis unit [304] is further configured to identify at least one of the one or more problem causing network nodes and the one or more sessions based on
20 the ladder diagram. The analysis unit [304] uses the ladder diagram created by the
ladder diagram creation unit [308] to identify at least one of the one or more problem-causing network nodes and the one or more problem-causing sessions based on the ladder diagram. The analysis unit [304] examines the visual representation of the session data to detect anomalies, errors, or delays that indicate
25 where problems are occurring. By analysing the sequence of events and the
interactions between different network nodes and the user equipment, the analysis unit [304] can identify the exact node or session responsible for the network issue.
[0085] For example, if the ladder diagram shows a delay in message exchange
30 between the user equipment and a base station, the analysis unit [304] can identify
25

the base station as a potential problem-causing node. Similarly, if the diagram highlights a failed handover between base stations, the specific session causing the failure can be identified.
5 [0086] In an exemplary aspect, the system [300] may be implemented in a trace
collection entity (TCE). The TCE is a component responsible for collecting, processing, and storing a trace data generated by one or more network elements or one or more network interfaces and providing a visual output such as ladder diagram. TCE creates a ladder diagram for a given subscriber with the use of TR
10 and TRSR. With the help of ladder diagram, user or network administrator can
analyse the subscriber summary and can see the problem causing node and problem causing session. The TCE may receive subscriber details and time period range (such as pre-configured hour(s), day(s)), summary log data of a session and one or more messages of the session. The trace collection entity may identify the TR
15 parameter associated with the base station and TRSR parameter associated with the
session details of the session. The trace collection entity may process the TR parameter and the TRSR parameter with at least the one or more messages of the session to generate a unique correlation on an enriched data. Further, the TCE may create a ladder diagram based on the unique correlation on the enriched data and
20 may identify at least one of the one or more problem causing network nodes and
the one or more sessions based on the ladder diagram. In an exemplary aspect, the TCE may generate ladder diagram or call sequence diagram for a specific session for customized implementation to receive TR and TRSR parameter from gNB for analysing to take further appropriate actions.
25
[0087] In an exemplary implementation of the present disclosure, the analysis unit [304] is configured to enable analysis of plurality of summary logs of communication by the subscriber in order to identify instances of bad subscriber’s service or user experience, as defined in paragraphs above. The analysis unit [304]
30 of the system [300] by isolating and decoding the first parameter pertaining to a
26

network mode of summary log data of communication. Therefore, with isolation
and decoding of the first parameter of summary log of communication, the problem
causing network node in network, such as 5G network, can be identified. Similarly,
the analysis unit [304] of the system [300] isolates and decodes the second
5 parameter of summary log data of communication. The second parameter of
summary log data of communication pertains to a session and details thereof.
[0088] Post isolation and identification of the first parameter and the second
parameter of the summary log data of communication, a ladder diagram of reduced
10 complexity is created. This allows easier analysis thereof and quicker identification
of problem causing nodes in the network and session therewith.
[0089] In an exemplary aspect, the present disclosure may be implemented by the other network, such as, but not limited to 4G, 6G and the like.
15
[0090] Referring to FIG. 4, an exemplary method flow diagram [400] for identification of one of one or more problem causing network nodes and one or more problem causing sessions, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [400] is
20 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 FIG. 4, the method [400] starts at step [402].
[0091] At step [404], the method [400] as disclosed by the present disclosure
25 comprises receiving, by a transceiver unit [302], a summary log data of a session
and one or more messages of the session, wherein the session is one of a call session
and a data exchange session. The session is one of a call session (such as voice call)
and a data exchange session (such as multimedia exchange). In an exemplary
aspect, the summary log data may comprise at least one of subscriber information,
30 location, used network node(s), type of session (such as call or data), and the like.
27

For example, in a call session, the summary log data may include the call initiation
time, the duration of the call, the identities of the calling and receiving parties, and
any disconnection events. In a data exchange session, the summary log data might
consist of the session start time, the data volume transferred, the data transfer rate,
5 and any error occurrences during the data exchange. For the call session, the one or
more messages might include signalling messages exchanged between the devices to establish and maintain the call. For the data exchange session, the one or more messages could encompass data packets transferred, acknowledgment messages, payload messages and error messages.
10
[0092] In an exemplary aspect, the transceiver unit [302] prior to the receiving of the summary log data of the session and the one or more messages of the session may receive, via a user interface, a subscriber information and a time range value for identification of at least one of the one or more problem-causing network nodes
15 and the one or more problem-causing sessions. For monitoring and analysing the
network performance, the transceiver unit [302] may receive details of the subscriber and time period range (such as pre-configured hour(s), day(s)) from the network administrator for identifying at least one of the one or more problem-causing network nodes and the one or more problem-causing sessions. In an
20 exemplary aspect, the network nodes may be such as, but not limited to, RAN, base
station, network functions (such as Access and Mobility Management Function (AMF), Session Management Function (SMF) etc.) and the like. In an exemplary aspect, the session may be one of the call session and the data exchange session. In an exemplary aspect, the transceiver unit [302] may configure to receive, from one
25 or more base stations, the first parameter and the second parameter. The first
parameter is a trace reference (TR), and the second parameter is a trace recording session reference (TRSR).
[0093] Next, at step [406], the method [400] as disclosed by the present disclosure
30 comprises performing, by an analysis unit [304], an isolation and decode procedure
28

to identify a first parameter and a second parameter related to the summary log data,
wherein the first parameter is associated with a base station, and the second
parameter is associated with session details of the session. The isolation and decode
procedure include extracting and separating relevant information from the summary
5 log data for identifying the first parameter and the second parameter for further
analysis and troubleshooting.
[0094] The analysis unit [304] may perform the isolation and decode procedure to identify the first parameter and the second parameter related to the summary log
10 data received from the transceiver unit [302]. The first parameter is associated with
a base station of, and the second parameter is associated with session details of the session. The first parameter is trace reference (TR), and the second parameter is trace recording session reference (TRSR). The TR parameter may identify the base station or gNB in 5G network and TRSR parameter may identify the unique session
15 within base station or gNB in 5G network. By performing the isolation and decode
procedure, the analysis unit [304] extracts the TR parameter and TRSR parameter from the summary log data. For example, in a scenario where multiple users are connected to the same base station, the TR helps identify which base station is handling the user’s connection, the TRSR facilitates in ensuring that the specific
20 session of the user is correctly identified among multiple sessions.
[0095] Next, at step [408], the method [400] as disclosed by the present disclosure comprises stitching, by a stitching unit [306], at least the first parameter and the second parameter with at least the one or more messages of the session to generate
25 a unique correlation on an enriched data. The stitching corresponds to combining
the first parameter (such as the trace reference i.e. TR parameter) and the second parameter (such as the trace recording session reference i.e. TRSR parameter) with the one or more messages of the session for generating the unique correlation on enriched data. The stitching facilitates in creating a dataset that uniquely correlates
30 all the information related to the session to link the base station identifier and the
29

session identifier with the one or more messages exchanged during the session,
providing a coherent and enriched view of the session data. For example, in a 5G
network, the first parameter (trace reference) might be a unique identifier for a gNB,
and the second parameter (trace recording session reference) might be a unique
5 identifier for the specific session handled by the gNB. The one or more messages
of the session could include signalling messages, data packets, and control messages exchanged between the user equipment and the network.
[0096] By stitching the first parameter and the second parameter with the one or
10 more messages of the session, the stitching unit [306] generates a unique correlation
(such as a dataset that allows for detailed analysis of the session) for the enriched
data. The enriched data includes not only the one or more messages of the session
but also the context provided by the trace reference and trace recording session
reference. The context facilitates in understanding the flow of the session,
15 identifying where issues may have occurred, and determining the specific network
nodes involved. For example, if a user experiences a dropped call, the stitching unit
[306] would stitch (such as combine) the trace reference, trace recording session
reference, and the one or more messages exchanged during the call. The stitching
(such as combination) helps in identifying whether the issue occurred at the gNB,
20 during the handover process, or due to some signalling failure. The enriched data
thus provides a clear and detailed picture of the session, enabling precise
troubleshooting and problem resolution.
[0097] Next, at step [410], the method [400] as disclosed by the present disclosure
25 comprises creating, by a ladder diagram creation unit [308], a ladder diagram based
on the unique correlation on the enriched data, wherein the analysis unit [304] is
further configured to identify at least one of the one or more problem causing
network nodes and the one or more sessions based on the ladder diagram. The
ladder diagram creation unit [308] generates a visual representation of the session
30 data, which is organized in a sequential manner to illustrate the interaction between
30

network nodes and the user equipment. In response to the generated unique co-
relation, the ladder diagram creation unit [308] may create the ladder diagram. The
ladder diagram may capture all the information related to the call or data exchange
session performed by the subscriber. The ladder diagram may represent the visual
5 representation of network with network elements. For example, in a call session,
the ladder diagram might show the initial call setup messages sent from the user
equipment to the base station, followed by authentication messages between the
base station and the core network, and finally the establishment of the call. Each
message is plotted in order, with time progressing from top to bottom. This format
10 helps in understanding the exact sequence of events and identifying any anomalies
or delays that may have occurred.
[0098] In an example, if a call drops unexpectedly, the ladder diagram can highlight where the call failed, whether it was during the handover between base stations or
15 due to a signalling error. The clear visualization provided by the ladder diagram
aids network engineers in pinpointing the exact location and cause of the problem. The analysis unit [304], using the ladder diagram, can then identify the specific network node or session that is causing the issue, facilitating targeted troubleshooting and resolution.
20
[0099] The analysis unit [304] is further configured to identify at least one of the one or more problem causing network nodes and the one or more sessions based on the ladder diagram.
25 [0100] Next, at step [412], the method [400] as disclosed by the present disclosure
comprises identifying, by the analysis unit [304], one of the one or more problem causing network nodes and the one or more problem-causing sessions based on the ladder diagram. The analysis unit [304] of the system [300] may identify at least one of the one or more problem causing network nodes and the one or more sessions
30 based on the ladder diagram. The analysis unit [304] uses the ladder diagram created
31

by the ladder diagram creation unit [308] to identify at least one of the one or more
problem-causing network nodes and the one or more problem-causing sessions
based on the ladder diagram. The analysis unit [304] examines the visual
representation of the session data to detect anomalies, errors, or delays that indicate
5 where problems are occurring. By analysing the sequence of events and the
interactions between different network nodes and the user equipment, the analysis
unit [304] can identify the exact node or session responsible for the network issue.
For example, if the ladder diagram shows a delay in message exchange between the
user equipment and a base station, the analysis unit [304] can identify the base
10 station as a potential problem-causing node. Similarly, if the diagram highlights a
failed handover between base stations, the specific session causing the failure can be identified.
[0101] Thereafter, the method [400] terminates at step [414].
15
[0102] FIG. 5 illustrates a network flow block diagram [500] for identification of one of one or more problem causing network nodes and one or more problem causing sessions, in accordance with exemplary implementations of the present disclosure. As shown in FIG. 5, a network flow block diagram [500] comprises a
20 set of gNBs (gNB [502], gNB [504], and gNB [506]), a Xprobe [508], a Message
brokers [510], a conductor unit [512], a Normalizer [514], a Workflow [516], a Graphical User Interface [516A], a AIDR Writer [518], a Ingestion layer[520], a database (DB) [522], a AI/ML unit [524], a Ingestion layer[526], an Inventory system/ FMS (Fulfilment management system) [528], a Computation engine [530],
25 a Distributed File System[532] and Computation layer [534].
[0103] The network flow begins with various Next Generation NodeB (gNB) units,
specifically gNB [502], gNB [504], and gNB [506]. These units are responsible for
providing summary log data, trace reference (TR) parameter and trace recording
30 session reference (TRSR) parameter for subscriber sessions within the network.
32

Each gNB is configured to gather comprehensive performance indicators and event logs for monitoring the state and efficacy of the network's 5G operations.
[0104] The data is then transmitted over a TCP connection to the Xprobe [508].
5 The Xprobe acts as the primary receiving point and is tasked with the initial
handling of the incoming data. It receives specific sets of instructions related to the decoding of summary log data to identify the trace reference (TR) parameter and trace recording session reference (TRSR) parameter.
10 [0105] Once Xprobe [508] processes the initial data, it segregates the summary log
data based on data type and message size. This segregation is crucial as it allows for a more organized and targeted approach to data parsing, which is carried out by the message brokers [510]. The message brokers parse this data byte by byte, carefully interpreting each piece according to its specific characteristics and
15 preparing it for further processing.
[0106] The parsed data is then sent to the conductor unit [512], which performs the
core decoding tasks. The conductor unit [512] is configured for transforming the
raw, parsed data into a format that is usable for diagnostics and monitoring,
20 ensuring that the decoding is successful and accurately reflects the data's intent and
content.
[0107] Post-decoding, the data undergoes several more stages of processing:
• Normalizer [514]: This unit standardizes the decoded data to ensure
25 uniformity across various data sets, making it easier to integrate and analyse 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. Artificial intelligence data record (AIDR) Writer [518] enriches
30 the data and stores the enriched data in files.
33

• 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 and analysis. Ingestion layer [520] pulls the data from AIDR writer [518] and pushes the data to Distributed file system [532]. 5
[0108] The data also passes through the workflow [516], which enhances
operational efficiency by automating and optimizing various backend processes.
The Workflow's output is then processed by the Computation Engine [530], which
is tasked with analysing large volumes of data for deep insights and strategic
10 decision-making.
[0109] Herein, the Ingestion layer [526] fetches the inventory data of subscribers
from Inventory system/ FMS (Fulfilment management system) [528] and pushes
the data to workflow unit [516]. The Inventory system/ FMS (Fulfilment
15 management system) [528] manages the inventory associated operations in the
network. The Inventory system/ FMS (Fulfilment management system) [528] handles incoming service order request in the network.
[0110] The refined data is stored in the Database (DB) [522] and subsequently
20 processed by artificial intelligence/machine learning (AI/ML) techniques within the
AI/ML unit [524]. The AI/ML techniques are configured to perform advanced analyses, such as predictive maintenance and fraud detection, contributing significantly to the network's proactive management strategies.
25 [0111] Further, the data circulates through the Computation Layer [534], where it
is further analysed and refined, ensuring that every piece of information extracted from the summary log data is utilized to its fullest potential to maintain and enhance network performance.
34

[0112] Finally, the Workflow [516] with help of Computation engine [530] provides ladder diagram with identified problem causing network nodes and problem-causing sessions to the Graphical User Interface [516A].
5 [0113] From the Graphical User Interface [516A] data associated with problem
causing network nodes and problem-causing sessions becomes accessible to end-users or network administrator 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.
10
[0114] FIG. 6 illustrates a block diagram of a system [600] for identification of one of one or more problem causing network nodes and one or more problem causing sessions, in accordance with exemplary implementations of the present disclosure. As shown in FIG. 6, the system [600] comprises at least one UI [602], at least one
15 workflow [604] and at least one database [606].
[0115] First, from UI [602] workflow [604] receives subscriber information and time range value (such as pre-configured hour(s), day(s)) via end user or network administrator.
20
[0116] Next, the workflow [604] analyses the received information from the UI with searches for data in database [606] and co-relates the data. The workflow [604] analyses the received information with user session, TR parameter and TRSR parameter and derive unique correlation for that session. The workflow [604]
25 searches for analysed data in database [606] and co-relates the data. Thereafter, the
workflow [604] creates a ladder diagram or call sequence diagram based on the unique correlation on the enriched data for identifying the problem causing nodes and problem causing sessions.
35

[0117] Thereafter, the workflow [604] may send the ladder diagram information to the UI [602]. Through UI [602], the end user or network administrator may identify the problem causing nodes and problem causing sessions and further take troubleshooting action for improving network service and user experience. 5
[0118] The present disclosure relates to a user equipment comprising a system for identification of one of one or more problem causing network nodes and one or more problem causing sessions, the system comprising: a transceiver unit [302] configured to receive a summary log data of a session and one or more messages of
10 the session, wherein the session is one of a call session and a data exchange session;
an analysis unit [304] connected at least to the transceiver unit [302], the analysis unit [304] configured to perform an isolation and decode procedure to identify a first parameter and a second parameter related to the summary log data, wherein the first parameter is associated with a base station of, and the second parameter is
15 associated with a session details of the session; a stitching unit [306] connected at
least to the analysis unit [304], the stitching unit [306] configured to stitch, at least the first parameter and the second parameter with at least the one or more messages of the session to generate a unique correlation on an enriched data; and a ladder diagram creation unit [308] connected to at least the stitching unit [306], the ladder
20 diagram creation unit [308] configured to create a ladder diagram based on the
unique correlation on the enriched data; wherein the analysis unit [304] is further configured to identify at least one of the one or more problem causing network nodes and the one or more sessions based on the ladder diagram.
25 [0119] The present disclosure further discloses a non-transitory computer readable
storage medium storing instructions for identification of one of one or more problem causing network nodes and one or more problem causing sessions, the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver unit [302] of the system to receive a summary log
30 data of a session and one or more messages of the session, wherein the session is
36

one of a call session and a data exchange session; an analysis unit [304] of the
system to perform an isolation and decode procedure to identify a first parameter
and a second parameter related to the summary log data, wherein the first parameter
is associated with a base station, and the second parameter is associated with a
5 session details of the session; a stitching unit [306] of the system to stitch at least
the first parameter and the second parameter with at least the one or more messages
of the session to generate a unique correlation on an enriched data; a ladder diagram
creation unit [308] of the system to create a ladder diagram based on the unique
correlation on the enriched data; and the analysis unit [304] of the system to identify
10 at least one of the one or more problem-causing network nodes and the one or more
problem-causing sessions based on the ladder diagram.
[0120] As is evident from the above, the present disclosure provides a technically advanced solution for identification of at least one of one or more problem causing
15 network nodes and one or more problem causing sessions. The present disclosure
provides a system and a method for quick identification for problem causing network nodes and session using ladder diagram. The present system and method quickly and easily identify the problem causing nodes in a network and session therewith, which is efficient enough to analyse large volume of data and accurately
20 identify problem causing nodes in a network and session therewith. The present
disclosure helps the end user to debug, troubleshoot and find the node which is causing the network issue.
[0121] Further, in accordance with the present disclosure, it is to be acknowledged
25 that the functionality described for the various components/units can be
implemented 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
30 construed as limiting the scope of the present disclosure. Consequently, alternative
37

arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
5 [0122] While considerable emphasis has been placed herein on the
disclosed embodiments, it will be appreciated that many embodiments can be made
and that many changes can be made to the embodiments without departing from the
principles of the present disclosure. These and other changes in the embodiments
of the present disclosure will be apparent to those skilled in the art, whereby it is to
10 be understood that the foregoing descriptive matter to be implemented is illustrative
and non-limiting.
38

We Claim:
1. A method [400] for identification of one or more problem causing network
nodes and one or more problem causing sessions, the method [400]
comprising:
- receiving, by a transceiver unit [302], a summary log data of a session and one or more messages of the session, wherein the session is one of a call session and a data exchange session;
- performing, by an analysis unit [304], an isolation and decode procedure to identify a first parameter and a second parameter related to the summary log data, wherein the first parameter is associated with a base station, and the second parameter is associated with a session details of the session;
- stitching, by a stitching unit [306], at least the first parameter and the second parameter with at least the one or more messages of the session to generate a unique correlation on an enriched data;
- creating, by a ladder diagram creation unit [308], a ladder diagram based on the unique correlation on the enriched data; and
- identifying, by the analysis unit [304], at least one of the one or more problem-causing network nodes and the one or more problem-causing sessions based on the ladder diagram.

2. The method [400] as claimed in claim 1, wherein the first parameter is a trace reference, and the second parameter is a trace recording session reference.
3. The method [400] as claimed in claim 1, wherein the method [400] comprises receiving, by the transceiver unit [302] from one or more base stations, the first parameter and the second parameter.

4. The method [400] as claimed in claim 1, wherein the method [400] is implemented in a trace collection entity (TCE).
5. The method [400] as claimed in claim 1, wherein prior to the receiving, by the transceiver unit [302], the summary log data of the session and the one or more messages of the session, the method [400] comprises:
- receiving, by the transceiver unit [302] via a user interface, a subscriber
information and a time range value for identification of at least one of
the one or more problem-causing network nodes and the one or more
problem-causing sessions.
6. A system [300] for identification of one of one or more problem causing
network nodes and one or more problem causing sessions, the system [300]
comprising:
- a transceiver unit [302] configured to receive a summary log data of a session and one or more messages of the session, wherein the session is one of a call session and a data exchange session;
- an analysis unit [304] connected at least to the transceiver unit [302], the analysis unit [304] configured to perform an isolation and decode procedure to identify a first parameter and a second parameter related to the summary log data, wherein the first parameter is associated with a base station of, and the second parameter is associated with a session details of the session;
- a stitching unit [306] connected at least to the analysis unit [304], the stitching unit [306] configured to stitch, at least the first parameter and the second parameter with at least the one or more messages of the session to generate a unique correlation on an enriched data; and
- a ladder diagram creation unit [308] connected to at least the stitching unit [306], the ladder diagram creation unit [308] configured to create a ladder diagram based on the unique correlation on the enriched data;

wherein the analysis unit [304] is further configured to identify at least one of the one or more problem causing network nodes and the one or more sessions based on the ladder diagram.
7. The system [300] as claimed in claim 6, wherein the first parameter is a trace reference, and the second parameter is a trace recording session reference.
8. The system [300] as claimed in claim 6, wherein the transceiver unit [302] is further configured to receive, from one or more base stations, the first parameter and the second parameter.
9. The system [300] as claimed in claim 6, wherein the system [300] is implemented in a trace collection entity (TCE).
10. The system [300] as claimed in claim 6, wherein the transceiver unit [302], prior to the receiving of the summary log data of the session and the one or more messages of the session, is configured to:
- receive, via a user interface, a subscriber information and a time range
value for identification of at least one of the one or more problem-
causing network nodes and the one or more problem-causing sessions.
11. A user equipment comprising a system for identification of one of one or
more problem causing network nodes and one or more problem causing
sessions, the system comprising:
- a transceiver unit [302] configured to receive a summary log data of a session and one or more messages of the session, wherein the session is one of a call session and a data exchange session;
- an analysis unit [304] connected at least to the transceiver unit [302], the analysis unit [304] configured to perform an isolation and decode

procedure to identify a first parameter and a second parameter related to the summary log data, wherein the first parameter is associated with a base station of, and the second parameter is associated with a session details of the session;
- a stitching unit [306] connected at least to the analysis unit [304], the stitching unit [306] configured to stitch, at least the first parameter and the second parameter with at least the one or more messages of the session to generate a unique correlation on an enriched data; and
- a ladder diagram creation unit [308] connected to at least the stitching unit [306], the ladder diagram creation unit [308] configured to create a ladder diagram based on the unique correlation on the enriched data;
wherein the analysis unit [304] is further configured to identify at least one of the one or more problem causing network nodes and the one or more sessions based on the ladder diagram.