FORM 2
THE PATENTS ACT, 1970
THE PATENTS RULE 0) 003
COMPLETE SPECIFICATION
APPLICANT
JIO PLATFORMS LIMITED
of Office-101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India; Nationality: India
The following specification particularly describes
the invention and the manner in which
it is to be performed

RESERVATION OF RIGHTS
[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and/or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.
TECHNICAL FIELD
[0002] The present disclosure generally relates to a means to trace a logger of a request in a communication network. In particular, the present disclosure relates to implementing a trace logging mechanism in a communication network.
DEFINITION
[0003] As used in the present disclosure, the following terms are generally
intended to have the meaning as set forth below, except to the extent that the context
in which they are used to indicate otherwise.
[0004] The network functions (NFs) are the logical entities or software-based
functionalities that define how the network operates and processes data.
[0005] A policy control function (PCF) determines the mobile network
resources and services needed to support connected devices. The PCF is vital for
ensuring the customer experience of modern voice and data services.
[0006] A network repository function (NRF) is responsible for maintaining
information about network functions (NFs) and the services they provide. It serves
as a central repository of NF instances and their respective services.
[0007] A binding support function (BSF) allows PCFs to register, update and
remove the binding information from it, and allows NF consumers to discover the
selected PCF.

[0008] A charging function (CHF) is for accurately calculating and allocating
charges for various services and resources used by subscribers.
[0009] A command-line interface (CLI) is a text-based user interface (UI) used
to run programs, manage computer files, and interact with the computer.
[0010] A subscription permanent identifier (SUPI) is a globally unique
subscription permanent identifier allocated to each subscriber.
[0011] Error codes are generated by the event-log analysis and system
configuration code. The error codes are used to identify the cause of a problem, a
failing component, and the service actions that might be needed to solve the
problem. Further, the error codes are numeric or alphanumeric codes that indicate
the nature of an error and, when possible, why it occurred. The error codes can be
reported to end users of software, returned from communication protocols, or used
within programs as a method of representing anomalous conditions.
BACKGROUND
[0012] The following description of related art may be 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.
[0013] In a communication network, such as a 5G or 6G network, network functions, such as binding support function (BSF), policy control function (PCF), charging function (CHF), network repository function (NRF), etc. may receive a plurality of requests. As a result, a challenge may arise to track the plurality of requests as well as to track subscribers making the requests. This challenge may lead to inefficient operation of identification and/or rectification of issues that cause the raising of the requests. Furthermore, there may be limitations in monitoring particular parameters of the network that are required to be traced in order to diagnose faults in the network.

[0014] There may, therefore, be a requirement in the art for a means to accurately trace or track subscribers and their requests to diagnose faults in the network.
SUMMARY
[0015] In an exemplary embodiment, a method for performing trace logging of a plurality of events in a communication network is described. The method comprises receiving, by a network function (NF), an event with a unique identification (ID) from a network function-client (NF-C). The plurality of events includes receiving a request or transmitting a response in response to the received request. The method comprises checking, by the NF, whether a trace logger functionality for the event is enabled and on detecting that the trace logger functionality is enabled, detecting, by the NF, whether the unique ID of the event is present in a trace logger. The trace logger is configured to store a plurality of unique IDs corresponding to parameters of the plurality of events. The method comprises on detecting that the unique ID of the event is present in the trace logger, initiating, by the NF, trace logging of the event. The method comprises checking, by the NF, a log mode from a plurality of log modes for the event in the trace logger and collecting, by the NF, logs of the event into a trace log file of the trace logger based on the log mode.
[0016] In some embodiments, the method comprises checking, by the NF, whether a live tracing is enabled and on detecting that the live tracing is enabled, displaying the event. For the live tracing, generating a plurality of templates of unique IDs corresponding to the plurality of parameters and adding the plurality of templates of the unique IDs corresponding to the plurality of parameters in the trace logger.
[0017] In some embodiments, on detecting that the unique ID of the event is not present in the trace logger, ignoring, by the NF, the event. [0018] In some embodiments, the unique IDs of the plurality of parameters includes a subscription permanent identifier (SUPI) or error codes.

[0019] In some embodiments, the NF includes a network repository function (NRF), a binding support function (BSF), a policy control function (PCF), and a charging function (CHF).
[0020] In some embodiments, the NF is configured to keep dumping logs into the trace log file upto a point when the trace log is not removed for a defined parameter from the plurality of parameters, or the trace logging is disabled. [0021] In some embodiments, the trace logging is enabled/disabled through a runtime configurable flag.
[0022] In another exemplary embodiment, a system for performing trace logging of a plurality of events in a communication network is described. The system comprises a network function (NF) and a network function-client (NF-C). The NF comprises a receiving unit configured to receive an event with a unique identification (ID) from the network function-client (NF-C). The plurality of events includes receiving a request or transmitting a response in response to the received request. A checking unit is configured to check whether a trace logging for the event is enabled. On detecting that the trace logging is enabled, the checking unit is configured to check whether the unique ID of the event is present in a trace logger. The trace logger is configured to store a plurality of unique IDs corresponding to parameters of the plurality of events. On detecting that the unique ID of the event is present in the trace logger, a processing unit is configured to initiate trace logging of the event. The checking unit is configured to check a log mode from a plurality of log modes for the event in the trace logger. A collecting unit is configured to collect logs of the event into a trace log file of the trace logger based on the log mode.
[0023] In some embodiments, the checking unit configured to check whether a live tracing is enabled. On detecting that the live tracing is enabled, the processing unit configured to display the event. For the live tracing, generating a plurality of templates of unique IDs corresponding to the plurality of parameters and adding the plurality of templates of the unique IDs corresponding to the plurality of parameters in the trace logger.

[0024] In some embodiments, on detecting that the unique ID of the event is not present in the trace logger, the processing unit configured to ignore the event. [0025] In some embodiments, the unique IDs of the plurality of parameters includes a subscription permanent identifier (SUPI) or error codes. [0026] In some embodiments, the NF include a network repository function (NRF), a binding support function (BSF), a policy control function (PCF), and a charging function (CHF).
[0027] In some embodiments, the NF is configured to keep dumping logs into the trace log file upto a point when the trace log is not removed for a defined parameter from the plurality of parameters, or the trace logging is disabled. [0028] In some embodiments, the trace logging is enabled/disabled through a runtime configurable flag.
[0029] In some embodiments, a user equipment is communicatively coupled with a system. The system may receive a connection request from the UE. The system may send an acknowledgment of the connection request to the UE. The UE may transmit a plurality of signals in response to the connection request. The system is configured for performing trace logging of a plurality of events in a network. [0030] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure, and are not restrictive.
OBJECTS OF THE INVENTION
[0031] An object of the present invention is to provide a system and a method
for trace logging in a communication network.
[0032] Another object of the present invention is to provide a system and a
method that facilitates identification and troubleshooting of issues in an application.
[0033] Another object of the present invention is to provide a system and a
method that facilitates monitoring of network functions in real-time.
[0034] Another object of the present invention is to provide a system and a
method that facilitates optimization of trace logging to gather pertinent information,
thus reducing the quantum of data to be received, stored and/or analyzed.

[0035] Another object of the present invention is to provide a system and a method that facilitates correlation of traces associated with user requests with other events in the communication network.
[0036] Another object of the present invention is to provide a system and a method that improves reliability in storing and retrieving log data without adversely affecting the network functions.
BRIEF DESCRIPTION OF DRAWINGS
[0037] The accompanying drawings, which are incorporated herein, and
constitute a part of this disclosure, illustrate exemplary embodiments of the
disclosed methods and systems in which like reference numerals refer to the same
parts throughout the different drawings. Components in the drawings are not
necessarily to scale, emphasis instead being placed upon clearly illustrating the
principles of the present disclosure. Some drawings may indicate the components
using block diagrams and may not represent the internal circuitry of each
component. It will be appreciated by those skilled in the art that disclosure of such
drawings includes the disclosure of electrical components, electronic components
or circuitry commonly used to implement such components.
[0038] FIG. 1 illustrates an exemplary network architecture 100 in which or
with which embodiments of the present disclosure may be implemented.
[0039] FIG. 2A illustrates an exemplary block diagram 200A of a system for
trace logging in a communication network, in accordance with an embodiment of
the present disclosure.
[0040] FIG. 2B illustrates an exemplary block diagram 200B of a network
function (NF) for trace logging in the communication network, in accordance with
an embodiment of the present disclosure.
[0041] FIG. 3 illustrates an exemplary schematic diagram 300 of the system
for trace logging in the communication network, in accordance with an embodiment
of the present disclosure.

[0042] FIG. 4A illustrates a schematic flow diagram 400A depicting an
operation of the system for trace logging in the communication network, in
accordance with an embodiment of the present disclosure.
[0043] FIG. 4B illustrates an exemplary schematic flow diagram 400B
depicting trace logging of events in the communication network, in accordance with
an embodiment of the present disclosure.
[0044] FIG. 5 illustrates an exemplary computer system 500 in which or with
which embodiments of the present disclosure may be implemented.
DETAILED DESCRIPTION
[0045] 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 disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.
[0046] 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 spirit and scope of the disclosure as set forth.
[0047] 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, networks, processes, and other components may be shown as components in block diagram form in order not to

obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments. [0048] Also, it is noted that individual embodiments may be described as a 5 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 can 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
10 steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function. [0049] The word “exemplary” and/or “demonstrative” is used herein to mean
15 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 advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques
20 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 other elements.
25 [0050] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout
30 this specification are not necessarily all referring to the same embodiment.
9

Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[0051] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used 5 herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one
10 or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.
[0052] The various embodiments of the present disclosure will be explained in detail with reference to FIGs. 1 – 5.
15 [0053] FIG. 1 illustrates an exemplary network architecture 100 in which or with which embodiments of the present disclosure may be implemented. [0054] Referring to FIG. 1, the network architecture 100 may include one or more computing devices or user equipment (104-1, 104-2…104-N) associated with one or more users (102-1, 102-2…102-N) in an environment. A person of ordinary
20 skill in the art will understand that one or more users (102-1, 102-2…102-N) may be individually referred to as the user 102 and collectively referred to as the users 102. Similarly, a person of ordinary skill in the art will understand that one or more user equipment (104-1, 104-2…104-N) may be individually referred to as the user equipment 104 and collectively referred to as the user equipment 104. A person of
25 ordinary skill in the art will appreciate that the terms “computing device(s)” and “user equipment” may be used interchangeably throughout the disclosure. Although three user equipment 104 are depicted in FIG. 1, however any number of the user equipment 104 may be included without departing from the scope of the ongoing description.
30 [0055] In an embodiment, the user equipment 104 may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a
10

smartphone, a phablet device, and so on), a wearable computer device(e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing 5 device, a portable gaming system, and/or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the user equipment 104 may include, but is not limited to, any electrical, electronic, electro¬mechanical, or an equipment, or a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a
10 general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device, wherein the user equipment 104 may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user 102 or the entity
15 such as touchpad, touch enabled screen, electronic pen, and the like. A person of ordinary skill in the art will appreciate that the user equipment 104 may not be restricted to the mentioned devices and various other devices may be used. [0056] Referring to FIG. 1, the user equipment 104 may communicate with a system 108, for example, a system for trace logging in a communication network,
20 through a network 106. In an embodiment, the network 106 may include at least one of a Fifth Generation (5G) network, 6G network, or the like. The network 106 may enable the user equipment 104 to communicate with other devices in the network architecture 100 and/or with the system 108. The network 106 may include a wireless card or some other transceiver connection to facilitate this
25 communication. In another embodiment, the network 106 may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.
30 [0057] In another exemplary embodiment, the centralized server 112 may include or comprise, by way of example but not limitation, one or more of a stand-
11

alone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at 5 least a portion of any of the above, some combination thereof.
[0058] In an embodiment, the user equipment (UE) 104 is communicatively coupled with the system 108. The system 108 may receive a connection request from the UE 104. The system 108 may send an acknowledgment of the connection request to the UE 104. The UE 104 may transmit a plurality of signals in response
10 to the connection request. The system 108 is configured for performing trace logging of a plurality of events in the network 106.
[0059] Although FIG. 1 shows exemplary components of the network architecture 100, in other embodiments, the network architecture 100 may include fewer components, different components, differently arranged components, or
15 additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture 100 may perform functions described as being performed by one or more other components of the network architecture 100. [0060] FIG. 2A illustrates an exemplary block diagram 200A of the system 108
20 for trace logging in the communication network 106, in accordance with an embodiment of the present disclosure.
[0061] The system 108 may include one or more processors 202 and a memory 204 communicably coupled to the one or more processors 202. The one or more processor(s) 202 may be implemented as one or more microprocessors,
25 microcomputers, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, one or more processor(s) 202 may be configured to fetch and execute computer-readable instructions stored in a memory 204 of the system 108. The memory 204 may be
30 configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed
12

to create or share data packets over a network service. The memory 204 may include any non-transitory storage device including, for example, volatile memory such as Random-Access Memory (RAM), or non-volatile memory such as Erasable Programmable Read-Only Memory (EPROM), flash memory, and the like. 5 [0062] In an embodiment, the system 108 may include an interface(s) 206. The interface(s) 206 may include a variety of interfaces, for example, interfaces for data input and output devices, referred to as I/O devices, storage devices, and the like. The interface(s) 206 may facilitate communication of the system 108. The interface(s) 206 may also provide a communication pathway for one or more
10 components of the system 108. Examples of such components include, but are not limited to, processing unit/engine(s) 210 and a database 220. [0063] The processing unit/engine(s) 210 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s)
15 210. In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) 210 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine(s) 210 may comprise a processing resource (for
20 example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) 210. In such examples, the system 108 may include the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or
25 the machine-readable storage medium may be separate but accessible to the system 108 and the processing resource. In other examples, the processing engine(s) 210 may be implemented by an electronic circuitry.
[0064] In an embodiment, the system 108 may perform trace logging to record events (e.g., requests received, or responses sent for requests containing parameters
30 like SUPI or response containing response codes, error codes, etc.) in a log file for later analysis. The system 108 may perform a live tracing to monitor the execution
13

of a particular request in real-time without affecting the overall logger mode of the
network functions (e.g., CHF/PCF/NRF/BSF). This significantly improves the
stability during the monitoring and debugging phases.
[0065] The system 108 may include a network function (NF) 222. The network 5 function 222 may configure to perform trace logging in the communication network
106 as explained in FIG. 2B.
[0066] In an aspect, the network functions (e.g., CHF/PCF/NRF/BSF), a
command line interface and a NF-client may be part of the system 108 to perform
trace logging to record events. 10 [0067] FIG. 2B illustrates an exemplary block diagram 200B of the network
function (NF) 222 for trace logging in the communication network 106, in
accordance with an embodiment of the present disclosure.
[0068] The network function 222 may be a network repository function (NRF),
a binding support function (BSF), a policy control function (PCF), and a charging 15 function (CHF).
[0069] The network function 222 comprises a receiving unit 224, a checking
unit 226, a processing unit 228, and a collection unit 230.
[0070] The receiving unit 224 is configured to receive an event with a unique
identification (ID) from the network function-client (NF-C). The plurality of events 20 includes receiving a request or transmitting a response in response to the received
request. For example, events may be an update request, a connection request, a
service request, a call request, a data request, a positive response (e.g., ACK), a
negative response (e.g., NACK), etc.
[0071] The checking unit 226 is configured to check whether a trace logging 25 for the event is enabled. The trace logging may be enabled or disabled by a runtime
configurable flag. For example, if the runtime configurable flag is set, the trace
logging is enabled. If the runtime configurable flag is reset, the trace logging is
disabled.
[0072] On detecting that the trace logging is enabled, the checking unit 226 is 30 configured to check whether the unique ID of the event is present in a trace logger.
14

The trace logger is configured to store a plurality of unique IDs corresponding to a
plurality of parameters of the plurality of events.
[0073] On detecting that the unique ID of the event is present in the trace
logger, the processing unit 228 is configured to initiate trace logging of the event. 5 [0074] The checking unit 226 is configured to check a log mode from a
plurality of log modes for the event in the trace logger. The log mode may comprise
a debug log mode, an error log mode, an information log mode, and a pattern log
mode.
[0075] The collection unit 230 is configured to collect logs of the event into a 10 trace log file of the trace logger based on the log mode.
[0076] The checking unit 226 is configured to check whether a live tracing is
enabled.
[0077] On detecting that the live tracing is enabled, the processing unit 228 is
configured to display the event. 15 [0078] In an aspect, the trace logging may allow developers to identify issues
in the application by providing detailed information about events (e.g., the request
and response) for traced parameters. This information can be used to troubleshoot
issues and improve the application's performance.
[0079] FIG. 3 illustrates an exemplary schematic diagram 300 of the system 20 108 for trace logging in the communication network 106, in accordance with an
embodiment of the present disclosure.
[0080] To implement functionalities of the system 108, the system 108 may
include a network function client (NF-C) 302, a network function (NF) 304, and a
command line interface (CLI) 306. In some embodiments, the NF 304 may include, 25 without limitations, binding support function (BSF), policy control function (PCF),
charging function (CHF), network repository function (NRF), etc.
[0081] The system 108 for trace logging may be enabled for requests from the
NF-C 302 through the CLI 306. The system 108 may be capable of tracing a request
generated in any log mode. In some embodiments, the system 108 may be 30 implementable irrespective of the log mode in which the NF 304 may be running.
Thus, live tracing of requests and responses for a particular parameter (e.g.,
15

subscription permanent identifier (SUPI) or error code) may be enabled using the system 108. The live tracing may require pre-made templates for the parameters. The templates may be generated through the CLI 306. Live tracking of the events (e.g., requests or responses) enables real-time monitoring of the network functions 5 NFs by providing a continuous view of the application's flow and data progression. This may help the developers to identify issues occur in the application's flow and take immediate action to resolve them.
[0082] FIG. 4A illustrates an exemplary schematic flow diagram 400A depicting an operation of the system 108 for trace logging in the communication
10 network 106, in accordance with an embodiment of the present disclosure.
[0083] Referring to FIGs. 3 and 4, the system 108 may be implemented to record events, such as requests received, or responses transmitted in response to the received requests containing particular parameters. In some examples, the parameters may include SUPI. In some other examples, there may be other
15 parameters. In some cases, the parameters may also include particular response codes in a log file that may be stored for analysis at a later stage. Further, the system 108 may provide a live tracing technique to allow monitoring execution of a particular request from a subscriber in real-time. Furthermore, the performing the live tracing technique may not affect a logger mode of the NF 304 in a production
20 environment. As a result, there may be significant improvements in stability of the system 108 during monitoring and debugging phases.
[0084] At step 402, adding unique ID to a trace logger set through the CLI 306. In an aspect, the CLI 306 is configured to generate templates for a plurality of parameters of unique IDs and add templates of the plurality of the parameters of the
25 unique IDs in the trace logger.
[0085] At step 404, the request from the NF-C 302 may be transmitted to and
received by the NF 304. The NF 304 may check if the trace logging functionality is
enabled.
[0086] At step 406, the NF 304 may check if a unique identification (ID)
30 provided in the trace logger is the same as that of the request. If the unique ID is the same as that of the request, the NF 304 may enable trace logging for that request
16

received. Otherwise, if the unique ID is not the same as that of the request, the NF 304 in step 414 may ignore the event.
[0087] At step 408, the NF 304 may be further configured to check the log mode of the trace logger and collect the logs into a trace log file. Thus, irrespective 5 of the log mode of the NF 304, the trace log file may include logs for requests and responses based on the log mode of the trace logger. The NF 304 may be configured to continuously dump logs into the trace file. In some embodiments, the dumping of log files may continue up until an instance that the trace log is not removed for the particular parameter associated with the trace file (e.g., SUPI, error code, etc.).
10 In some embodiments, the trace logging functionality may be enabled/disabled through a runtime configurable flag. For example, if the runtime configurable flag is set, then the trace logging functionality is enabled. If the runtime configurable flag is reset, then the trace logging functionality is disabled. [0088] At step 410, the NF 304 may be configured to check whether a live
15 tracing is enabled.
[0089] At step 412, further, if live tracing is enabled, the CLI 306 may be configured to display the request and response of the traced parameter in the CLI. If the live tracing is not enabled, the CLI 306 may display the collected logs of the trace log file.
20 [0090] The system 108 provides a means to identify issues in an application by providing detailed information pertaining to requests and responses for traced parameters (e.g., SUPI). By providing such information, the system 108 may facilitate quicker troubleshooting of the issues, and potentially shorter downtimes before the issues get resolved. The system 108 may further facilitate real-time
25 monitoring of NF by providing a continuous view of flow and data progression in an application. This way, the system 108 may further facilitate early detection of issues in the network 106.
[0091] The system 108 may provide an optimized means to gather relevant or pertinent information from logs. As a result, an amount of data that is to be analyzed
30 may be minimized, leading to better efficiency of analyzing resources. The system
17

108 may further allow for better correlation of traces associated with each user request with other events and exception reports.
[0092] Lastly, the system 108 provides for a reliable and an efficient way to store and retrieve log data for traced parameters without significantly impacting the 5 NF.
[0093] FIG. 4B illustrates an exemplary schematic flow diagram 400B depicting trace logging of events in the communication network 106, in accordance with an embodiment of the present disclosure. [0094] As illustrated in FIG. 4B, at step 422, receiving, by the network function
10 (NF) 304, an event with a unique identification (ID) from the network function-client (NF-C) 302. The unique IDs of the plurality of parameters includes a subscription permanent identifier (SUPI) or error codes. The NF 304 includes a network repository function (NRF), a binding support function (BSF), a policy control function (PCF), and a charging function (CHF).
15 [0095] At step 424, checking, by the NF 304, whether a trace logging for the event is enabled. The trace logging is enabled/disabled through a runtime configurable flag.
[0096] At step 426, on detecting that the trace logging is enabled, checking, by the NF 304, whether the unique ID of the event is present in a trace logger.
20 [0097] At step 428, on detecting that the unique ID of the event is present in the trace logger, initiating, by the NF 304, trace logging of the event. On detecting that the unique ID of the event is not present in the trace logger, the NF 304 may ignore the event. [0098] At step 430, checking, by the NF 304, a log mode from a plurality of
25 log modes for the event in the trace logger.
[0099] At step 432, collecting, by the NF 304, logs of the event into a trace log file of the trace logger based on the log mode. The NF 304 is configured to keep dumping logs into the trace log file upto a point when the trace log is not removed for a defined parameter (e.g., SUPI, error code) from the plurality of parameters, or
30 the trace logging is disabled.
18

[0100] In an aspect, the NF 304 is configured to check whether a live tracing is enabled. On detecting that the live tracing is enabled, displaying the event. For the live tracing, a plurality of templates of unique IDs corresponding to a plurality of parameters is generated. The plurality of templates of the unique IDs 5 corresponding to the plurality of parameters is added in the trace logger. If the live tracing is not enabled, the CLI may display the collected logs of the trace log file. [0101] FIG. 5 illustrates an exemplary computer system 500 in which or with which embodiments of the present disclosure may be implemented. [0102] The computer system 500 may include an external storage device 510,
10 a bus 520, a main memory 530, a read-only memory 540, a mass storage device 550, a communication port(s) 560, and a processor 570. A person skilled in the art will appreciate that the computer system 500 may include more than one processor and communication ports. The processor 570 may include various modules associated with embodiments of the present disclosure. The communication port(s)
15 560 may be any of an RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication ports(s) 560 may be chosen depending on a network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system 500
20 connects.
[0103] In an embodiment, the main memory 530 may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory 540 may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chip for storing static information
25 e.g., start-up or basic input/output system (BIOS) instructions for the processor 570. The mass storage device 550 may be any current or future mass storage solution, which can be used to store information and/or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or
30 solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and/or Firewire interfaces).
19

[0104] In an embodiment, the bus 520 may communicatively couple the processor(s) 570 with the other memory, storage, and communication blocks. The bus 520 may be, e.g. a Peripheral Component Interconnect PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), USB, or the like, for 5 connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor 570 to the computer system 500.
[0105] In another embodiment, operator and administrative interfaces, e.g., a display, keyboard, and cursor control device may also be coupled to the bus 520 to
10 support direct operator interaction with the computer system 500. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) 560. Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system 500 limit the scope of the present
15 disclosure.
[0106] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred
20 embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter to be implemented merely as illustrative of the disclosure and not as limitation. [0107] The present disclosure provides technical advancement related to trace
25 logging. This advancement addresses the limitations of existing solutions by tracing the request and the response for the traced parameters. The disclosure involves providing detailed information pertaining to the request and the responses for the traced parameters, which offer significant improvements in identifying issues in the application. By implementing real-time monitoring of NF by providing a
30 continuous view of flow and data progression in the application, the disclosed invention facilitates early detection of the issues in the network.
20

ADVANTAGES OF INVENTION
[0108] The present invention provides a system and a method for trace logging
in a communication network.
[0109] The present invention provides a system and a method that facilitates
identification and troubleshooting of issues in an application.
[0110] The present invention provides a system and a method that facilitates
monitoring of network functions in real-time.
[0111] The present invention provides a system and a method that facilitates
optimization of trace logging to gather pertinent information, thus reducing the
quantum of data to be received, stored and/or analyzed.
[0112] The present invention provides a system and a method that facilitates
correlation of traces associated with user requests with other events in the
communication network.
[0113] The present invention provides a system and a method that improves
reliability in storing and retrieving log data without adversely affecting the network
functions.

We Claim:
1. A method (400B) for performing trace logging of a plurality of events in a
communication network, the method comprising:
receiving (422), by a network function (NF) (222, 304), an event with a unique identification (ID) from a network function-client (NF-C) (302), wherein the plurality of events includes receiving a request or transmitting a response in response to the received request;
checking (424), by the NF (222, 304), whether a trace logging for the event is enabled;
on detecting that the trace logging is enabled, checking (426), by the NF (222, 304), whether the unique ID of the event is present in a trace logger, wherein the trace logger is configured to store a plurality of unique IDs corresponding to a plurality of parameters of the plurality of events;
on detecting that the unique ID of the event is present in the trace logger, initiating (428), by the NF (222, 304), trace logging of the event;
checking (430), by the NF (222, 304), a log mode from a plurality of log modes for the event in the trace logger; and
collecting (432), by the NF (222, 304), logs of the event into a trace log file of the trace logger based on the log mode.
2. The method as claimed in claim 1, wherein:
checking (434), by the NF (222, 304), whether a live tracing is enabled; and
on detecting that the live tracing is enabled, displaying (436) the event, wherein for the live tracing, generating a plurality of templates of unique IDs corresponding to the plurality of parameters; and
adding the plurality of templates of the unique IDs corresponding to the plurality of parameters in the trace logger.

3. The method as claimed in claim 1, wherein on detecting that the unique ID of the event is not present in the trace logger, ignoring, by the NF (222, 304), the event.
4. The method as claimed in claim 1, wherein the unique IDs of the plurality of parameters includes a subscription permanent identifier (SUPI) or error codes.
5. The method as claimed in claim 1, wherein the NF (222, 304) includes a network repository function (NRF), a binding support function (BSF), a policy control function (PCF), and a charging function (CHF).
6. The method as claimed in claim 1, wherein the NF (222,304) is configured to keep dumping logs into the trace log file upto a point when the trace log is not removed for a defined parameter from the plurality of parameters, or the trace logging is disabled.
7. The method as claimed in claim 6, wherein the trace logging is enabled/disabled through a runtime configurable flag.
8. A system (108) for performing trace logging of a plurality of events in a communication network, the system comprising a network function (NF) (222, 304), and a network function-client (NF-C) (302), the NF (222, 304) comprising:
a receiving unit (224) configured to receive an event with a unique identification (ID) from the network function-client (NF-C) (302), wherein the plurality of events includes receiving a request or transmitting a response in response to the received request;
a checking unit (226) configured to check whether a trace logging for the event is enabled;

on detecting that the trace logging is enabled, the checking unit (226) configured to check whether the unique ID of the event is present in a trace logger, wherein the trace logger is configured to store a plurality of unique IDs corresponding to parameters of the plurality of events;
on detecting that the unique ID of the event is present in the trace logger, a processing unit (228) configured to initiate trace logging of the event;
the checking unit (226) configured to check a log mode from a plurality of log modes for the event in the trace logger; and
a collection unit (230) configured to collect logs of the event into a trace log file of the trace logger based on the log mode.
9. The system (108) as claimed in claim 8, wherein:
the checking unit (226) configured to check whether a live tracing is enabled; and
on detecting that the live tracing is enabled, the processing unit (228) configured to display the event, wherein for the live tracing, generating a plurality of templates of unique IDs corresponding to the plurality of parameters; and
adding the plurality of templates of the unique IDs corresponding to the plurality of parameters in the trace logger.
10. The system as claimed in claim 8, wherein on detecting that the unique ID of the event is not present in the trace logger, the processing unit configured to ignore the event.
11. The system as claimed in claim 8, wherein the unique IDs of the plurality of parameters includes a subscription permanent identifier (SUPI) or error codes.

12. The system as claimed in claim 8, wherein the NF (222, 304) include a network repository function (NRF), a binding support function (BSF), a policy control function (PCF), and a charging function (CHF).
13. The system as claimed in claim 8, wherein the NF (222, 304) is configured to keep dumping logs into the trace log file upto a point when the trace log is not removed for a defined parameter from the plurality of parameters, or the trace logging is disabled.
14. The system as claimed in claim 13, wherein the trace logging is enabled/disabled through a runtime configurable flag.
15. A user equipment (UE) (104) communicatively coupled with a system (108), the coupling comprises steps of:
receiving, by the system (108), a connection request;
sending an acknowledgment of the connection request to the UE (104); and
transmitting a plurality of signals in response to the connection request, wherein the system (108) configured for performing trace logging of a plurality of events in a network (106) as claimed in claim 8.