System and method for managing sequence of trace records in a network

Abstract

A system (108) and a method (500) for managing a sequence of trace records in a network (106) are described A trace record generating unit (210) in a network function (208) generates trace records associated with a trace reference and assigns a sequence number in a header of each trace record. The trace records, along with the assigned sequence number, are transmitted to a consumer (212), which tracks the sequence of the trace records. Based on the sequence number, the consumer (212) determines whether the trace records are received out of order or one or more trace records are missing. Upon determination, the consumer (212) arranges the trace records in a sequential order and triggers an alert for missing trace records. The system (108) enables accurate tracking, reordering, and detection of missing trace records without requiring payload inspection, thereby improving data integrity, processing efficiency, and reliability of network monitoring.

Description

SYSTEM AND METHOD FOR MANAGING SEQUENCE OF TRACE RECORDS IN A NETWORK 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. All rights to such intellectual property are fully reserved by the owner.TECHNICAL FIELD

[0002] The present disclosure generally relates to the field of telecommunication networks. More particularly, the present disclosure relates to a system and method for managing a sequence of trace records in a 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 term “network function”, as used herein, refers to a functional entity within a communication network, including but not limited to Radio Access Network (RAN) nodes and core network functions, configured to perform one or more network operations. Examples of core network functions may include, but are not limited to, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a User Plane Function (UPF), a Policy Control Function (PCF), and a Network Repository Function (NRF).

[0005] The term “Trace Record Generator (TRG) (interchangeably referred to as trace record generating unit)”, as used herein, refers to a functional component within the network function, configured to generate trace records based on monitoring and diagnostic activities within the communication network.

[0006] The term “Trace Collection Entity (TCE) (interchangeably referred to as a consumer)”, as used herein, refers to a network component or entity configured toreceive, collect, and process a plurality of trace records generated by a trace record generating unit.

[0007] The term “trace record”, as used herein, refers to a structured data set generated by the TRG to capture information associated with one or more network events, including, but not limited to, signaling messages, session states, and performance metrics. Such trace records are utilized for network monitoring, troubleshooting, performance optimization, and analysis of network behavior.

[0008] The term “sequence number”, as used herein, refers to a unique identifier (e.g., Information Element (IE)) assigned to a header of each trace record by the TRG to maintain an order of the plurality of trace records associated with a trace reference. The sequence number is initialized to 0, incremented for each subsequent trace record, and reassigned upon reaching an upper limit (e.g., 65535) or upon reinitialization of a trace session.

[0009] The term “trace reference”, as used herein, refers to an identifier used in network tracing to correlate trace sessions across different network elements. It is a unique value assigned when a trace session is initiated for a subscriber or a network entity by a management system.

[0010] The term “trace session”, as used herein, refers to a period during which trace records are generated and associated with a trace reference for monitoring a specific subscriber, network entity, or network event.

[0011] The term “management system”, as used herein, refers to a network management component that initiates and triggers a generation of trace records by the TRG based on network monitoring requirements, or diagnostic requests.BACKGROUND

[0012] 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.

[0013] In modem telecommunication networks, trace records are extensively used to monitor, analyze, and troubleshoot network activities, including signaling events, session management, and traffic flow. These trace records are critical for network operators to understand network behavior, detect anomalies, and resolve issuesaffecting service quality. Typically, the trace records are generated by network functions (NFs) within a Radio Access Network (RAN) and core network components, and the generated trace records are collected and analyzed by a consumer (e.g., Trace Collection Entity (TCE)). However, in the existing system architecture, there is no mechanism to track the sequence of these trace records, resulting in challenges such as identifying missing records due to transmission losses or processing failures at the TCE.

[0014] A major challenge arises when packet loss occurs during the transmission of trace records. As there is no acknowledgment on an application layer for received trace records, optimizing signaling and avoiding excessive error / response handling at NFs becomes essential. Consequently, detecting lost trace records becomes difficult, impacting the reliability and accuracy of the trace record. Missing trace records may lead to incomplete analysis, delayed troubleshooting, and potential misinterpretation of network events.

[0015] Additionally, in scenarios where a significant volume of trace records are generated simultaneously, it becomes challenging to detect lost trace records accurately. The absence of a systematic mechanism to track the sequence and completeness of trace records may result in misinterpretations during network analysis, leading to suboptimal diagnostics and ineffective troubleshooting.

[0016] There is, therefore, a need in the art to overcome the deficiencies of the prior arts.SUMMARY OF THE DISCLOSURE

[0017] In an exemplary embodiment, a method for managing a sequence of a plurality of trace records in a network is disclosed. The method includes generating, by a trace record generating unit in a network function, the plurality of trace records associated with a trace reference. In response to generating, the method includes assigning, by the trace record generating unit, a sequence number in each header of the plurality of trace records. The method further includes transmitting, by the network function, the plurality of trace records and the assigned sequence number to a consumer. The method includes tracking, by the consumer, the sequence of each of the plurality of trace records received from the trace record generating unit. The method further includes determining, by the consumer, at least one of: the plurality of trace records are received out of order, and one or more missing trace records from the plurality of trace records based on the assigned sequence number in the header. Upon determining that the plurality of trace records are received out of order, the method includes arranging, by the consumer, the plurality of trace records in a sequential orderbased on the assigned sequence number. The method further includes triggering, by the consumer, an alert upon detecting the one or more missing trace records.

[0018] In some embodiments, triggering the alert includes transmitting, by the consumer, a notification to the trace record generating unit indicating detection of the one or more missing trace records.

[0019] In some embodiments, payload information and timestamp information associated with the plurality of trace records remain unchanged during the arranging of the plurality of trace records in the sequential order.

[0020] In some embodiments, the method further includes performing, by the consumer, one or more operations on the plurality of trace records arranged in the sequential order for analysis of network performance.

[0021] In some embodiments, tracking the sequence of each of the plurality of trace records includes maintaining, by the consumer, a sequence tracking log, wherein the sequence tracking log stores an expected sequence number associated with the plurality of trace records to verify whether the plurality of trace records are received in the sequential order based on the assigned sequence number.

[0022] In some embodiments, determining the one or more missing trace records includes extracting, by the consumer, the sequence number from each header of the plurality of trace records; comparing, by the consumer, the sequence number of each of the plurality of trace records received from the trace record generator with the expected sequence number stored in the sequence tracking log; and upon comparing, identifying, by the consumer, the one or more missing trace records based on detecting a mismatch between the received sequence number and the expected sequence number.

[0023] In some embodiments, assigning the sequence number includes assigning, by the trace record generating unit, the sequence number for each of the plurality of trace records when the trace reference associated with the plurality of trace records are assigned to the network function.

[0024] In some embodiments, assigning the sequence number includes initializing, by the trace record generating unit, the sequence number to zero when a first trace record from the plurality of trace records is generated; and incrementing, by the trace record generating unit, the sequence number by one for each subsequently generated trace record associated with the trace reference.

[0025] In some embodiments, the method further includes determining, by the trace record generating unit, whether the sequence number has reached a predefinedthreshold; and upon determining that the sequence number has reached the predefined threshold, reassign, by the trace record generating unit, the sequence number to zero for a subsequent trace record generated by the trace record generating unit.

[0026] In some embodiments, the method further includes determining, by the trace record generating unit, whether a trace session associated with the trace reference is reactivated with a new trace reference; and upon determining that the trace session is reactivated with the new trace reference, reassigning, by the trace record generating unit, the sequence number to zero for the subsequent trace record generated by the trace record generating unit.

[0027] In another exemplary embodiment, a network function for managing a sequence of a plurality of trace records in a network is disclosed. The network function includes a trace record generating unit configured to generate a plurality of trace records associated with a trace reference; assign a sequence number in each header of the plurality of trace records; and transmit the plurality of trace records and the assigned sequence number to a consumer.

[0028] In another exemplary embodiment, a consumer for managing a sequence of a plurality of trace records in a network is disclosed. The consumer is configured to receive the plurality of trace records and an associated sequence number assigned in each header of the plurality of trace records from a network function; track a sequence of the plurality of trace records; determine at least one of: the plurality of trace records are received out of order, and one or more missing trace records from the plurality of trace records based on the assigned sequence number in the header; arrange the plurality of trace records in sequential order based on the assigned sequence number; and trigger an alert upon detecting the one or more missing trace records.

[0029] In yet another exemplary embodiment, a computer program product including a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or more processors to perform a method for managing a sequence of a plurality of trace records in a network. The method includes generating, by a trace record generating unit in a network function, the plurality of trace records associated with a trace reference; in response to generating, assigning, by the trace record generating unit, a sequence number in each header of the plurality of trace records; transmitting, by the network function, the plurality of trace records and the assigned sequence number to a consumer; tracking, by the consumer, the sequence of each of the plurality of trace records received from the trace record generating unit; determining, by the consumer, at least one of: the plurality of trace records are received out of order, and one or more missing trace records from the plurality of trace records based on the assigned sequencenumber in the header; upon determining that the plurality of trace records are received out of order, arranging, by the consumer, the plurality of trace records in a sequential order based on the assigned sequence number; and triggering, by the consumer, an alert upon detecting the one or more missing trace records.

[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.OBJECTIVE OF THE DISCLOSURE

[0031] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies, are as follows:

[0032] An objective of the present disclosure is to provide a system and method for managing a sequence of trace records in a network by detecting missing trace records through sequence number analysis. This enables the identification of gaps in trace records and ensures data reliability.

[0033] Another objective of the present disclosure is to assign a sequence number field in the header of trace records with minimal overhead, thereby providing an effective approach for managing trace records while maintaining network efficiency.

[0034] Another objective of the present disclosure is to improve data integrity by accurately tracking and verifying the completeness of trace records, facilitating precise network monitoring and troubleshooting.

[0035] Another objective of the present disclosure is to provide a system and method for reordering trace records based on sequence numbers without relying on payload parsing or timestamp analysis, thereby minimizing processing overhead while supporting procedural and call flow analysis.

[0036] Another objective of the present disclosure is to enhance network performance by enabling network operators to promptly detect and address transmission losses, resulting in better diagnostics, faster issue resolution, and optimized network operations.

[0037] Yet another objective of the present disclosure is to enhance existing trace mechanisms by introducing a sequence-based tracking approach that overcomes limitations associated with absence of sequencing information, thereby improving reliability, ordering, and completeness of trace records.

[0038] Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

[0039] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0040] FIG. 1 illustrates an exemplary network architecture implementing a system for managing a sequence of trace records in a network, in accordance with an embodiment of the present disclosure.

[0041] FIG. 2 illustrates an exemplary block diagram of the system for managing the sequence of trace records in the network, in accordance with an embodiment of the present disclosure.

[0042] FIG. 3 illustrates an exemplary system architecture for managing the sequence of trace records in the network, in accordance with an embodiment of the present disclosure.

[0043] FIG. 4 illustrates an exemplary process flow for managing the sequence of trace records in the network, in accordance with an embodiment of the present disclosure.

[0044] FIG. 5 illustrates an exemplary flow diagram of a method for managing the sequence of trace records in the network, in accordance with an embodiment of the present disclosure.

[0045] FIG. 6 illustrates an exemplary block diagram of a computer system in which or with which embodiments of the present disclosure may be implemented.

[0046] The foregoing shall be more apparent from the following more detailed description of the disclosure.List of reference numerals100 - Network Architecture102 -User(s)104 - User Equipments (UEs)106 - Network108 - System200 - Block diagram202 - Processor(s)204 - Memory206 -Interface(s)208 - Network function210 - Trace record generating unit212 - Consumer214 -Database300 - System Architecture302 - Management System304 - Fourth Generation / Fifth Generation / Sixth Generation Radio Access Network (4G / 5G / 6GRAN)306 - 4G / 5G / 6G Core Network308, 404 - Trace Collection Entity (TCE)400 - Process Flow402 - Radio Access Network / Core Network Functions (RAN / Core NFs) Trace Record Generator (TRG)500 - Method flow diagram600 - Computer System610 - External Storage Device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port(s)670 - ProcessorDETAILED DESCRIPTION

[0047] 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 any 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. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.

[0048] 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.

[0049] 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.

[0050] Also, it is noted that individual embodiments may be described as a process that 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 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.

[0051] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and / or “demonstrative” is not necessarily to be construed as preferred or 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 like the term “comprising” as an open transition word without precluding any additional or other elements.

[0052] 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 this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0053] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context 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 or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes anycombinations of one or more of the associated listed items. It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.

[0054] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog, offering only voice services. Further, text messaging and data services became possible when the second-generation (2G) technology was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized the wireless communication with faster data speeds, improved network coverage, and security. Currently, fifth generation (5G) technology is being deployed, offering significantly faster data speeds, lower latency, and the ability to connect many devices simultaneously. Further, Sixth Generation (6G) successor to 5G is expected to provide significantly high data speed with reduced latency, which may offer improved connectivity for a vast number of devices concurrently. The capabilities of 6G enable new types of applications and services, such as advanced augmented reality (AR) and virtual reality (VR), holographic communications, and more immersive digital experiences. These advancements represent a significant leap forward from previous generations, enabling enhanced mobile broadband, improved Internet of Things (loT) connectivity, and more efficient use of network resources. The 6G technology promises to build upon these advancements, pushing the boundaries of wireless communication even further. While the 5G technology is still being rolled out globally, research and development into the 6G are rapidly progressing, with the aim of revolutionizing the way of connecting and interacting with technology.

[0055] While considerable emphasis has been placed herein on the components and component parts of 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 embodiment, as well as other 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 is to be interpreted merely as illustrative of the disclosure and not as a limitation.

[0056] Trace records are critical in monitoring, troubleshooting, and analyzing network behavior. The trace records are typically generated by a network function and transmitted to a consumer (e.g., Trace Collection Entity (TCE)) for further analysis. The trace records help the network operators detect issues, optimize network performance, and implement proactive maintenance strategies. The trace records are transmitted in a streaming manner from the network function to the consumer, with trace records continuously delivered over network interfaces without guaranteed ordering or delivery. Due to this streaming-based transmission, trace records may arrive out of order, be delayed, or be lost during transmission because of network conditions or processing limitations. A major challenge arises when packet loss occurs during the transmission of trace records. As there is no acknowledgment on an application layer for received trace records, optimizing signaling and avoiding excessive error or response handling at network functions becomes essential. Consequently, detecting lost trace records becomes difficult, impacting the reliability and accuracy of trace records. Missing trace records may lead to incomplete analysis, delayed troubleshooting, and potential misinterpretation of network events.

[0057] In existing implementations, trace records associated with a trace session are correlated using identifiers, such as a trace reference and a trace recording session reference, which enable associating multiple trace records with a particular call or session. However, such identifiers do not provide any mechanism to determine the sequence or ordering of individual trace records within the trace session. As a result, although trace records may be correlated with a session, the lack of sequence tracking leads to challenges in identifying missing records and maintaining correct ordering during analysis.

[0058] The present disclosure addresses the problem of detecting and handling packet loss in trace records transmitted to the consumer by assigning a sequence number in each header of the trace records. The introduced sequence number enables tracking of the order of trace records within a trace session, thereby overcoming the limitation of the absence of sequencing information in existing trace mechanisms. By assigning the sequence number in the header of trace records, the present disclosure enables the consumer (e.g., TCE) to identify missing trace records by detecting gaps in the sequence number, ensuring completeness and accuracy of the collected trace records. The present disclosure further facilitates efficient reordering of trace records based on sequence numbers without requiring inspection of payload data or timestamp information, thereby reducing processing overhead while maintaining data integrity. This enhancement improves the reliability and accuracy of trace record collection in telecommunication networks, leading to faster issue resolution, improved customer experience, predictive maintenance, and more informed business strategies. Asnetworks continue to evolve with increased complexity, accurate and reliable trace record management becomes critical for ensuring seamless connectivity and efficient network operations.

[0059] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0060] FIG. 1 illustrates an exemplary network architecture (100) implementing a system (108) for managing a sequence of trace records in a network (106), in accordance with an embodiment of the present disclosure.

[0061] As illustrated in FIG. 1, the network architecture (100) may include one or more user equipments (UEs) (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 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 UEs (104-1, 104-2, ....104-N) may be individually referred to as the UE (104) and collectively referred to as the UEs (104). Although three UEs (104) are depicted in FIG. 1, however, any number of the user equipments (104) may be included without departing from the scope of the ongoing description. In an embodiment, each UE (104) may have a unique identifier attribute associated therewith. In an embodiment, the unique identifier attribute may be indicative of at least one of a Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Equipment Identity (IMEI) number, an International Mobile Subscriber Identity (IMSI), a Subscriber Permanent Identifier (SUPI), and the like.

[0062] In an embodiment, the UE (104) may include smart devices operating in a smart environment, such as an Internet of Things (loT) system. In such an embodiment, the UE (104) may include, but is not limited to, smartphones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, a smart security system, a smart home system, other devices for monitoring or interacting with or for the users (102) and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE (104) may include, but is not limited to, intelligent, multi-sensing, network-connected devices that can integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network-connected.

[0063] In an embodiment, the UE (104) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, 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 device, a portable gaming system, and / or any other type of computer device with a wireless communication capabilities, and the like. In an embodiment, the UE (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, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device. In addition, the UE (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 an entity such as touch pad, a touch enabled screen, an electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE (104) may not be restricted to the mentioned devices and various other devices may be used.

[0064] In FIG. 1, the UE (104) may communicate with the system (108) via a network (106). In an embodiment, the network (106) may include at least one of a Fourth Generation (4G) network, Fifth Generation (5G) network, a Sixth Generation (6G) network, or the like. The network (106) may be a Radio Access Network (RAN). The RAN may include one or more network functions configured to process signaling messages and data sessions corresponding to the UE (104). Such signaling interactions and session events form a basis for generation of a plurality of trace records within the network. The network (106) may enable the UEs (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 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. In an embodiment, the network (106) may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth.

[0065] In an embodiment, the UE (104) may be communicatively coupled with the network (106) to initiate and maintain communication sessions. During such sessions, the UE (104) may transmit and receive signaling messages and data packets via the RAN. These interactions may include session establishment, mobility management, handover procedures, and data transmission events. The network function within the RAN may monitor such events and generate a plurality of trace records corresponding to the communication activities associated with the UE (104). The generated trace records may be associated with a trace reference for a trace session.

[0066] In an embodiment, the system (108) may be configured to manage the sequence of the plurality of trace records generated within the network (106). The system (108) may include a network function within the RAN comprising a trace record generating unit, and a consumer configured to process the plurality of trace records. The trace record generating unit configured to generate a plurality of trace records associated with a trace reference, assign a sequence number in each header of the plurality of trace records, and transmit the plurality of trace records and the assigned sequence number to a consumer. The system (108) may include the consumer configured to receive the plurality of trace records and an associated sequence number assigned in each header of the plurality of trace records from a network function, track a sequence of the plurality of trace records, determine at least one of: the plurality of trace records are received out of order, and one or more missing trace records from the plurality of trace records based on the assigned sequence number in the header, arrange the plurality of trace records in sequential order based on the assigned sequence number, and trigger an alert upon detecting the one or more missing trace records. A process for managing the sequence of trace records is explained in greater detail in conjunction with FIGS. 2-6.

[0067] 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 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).

[0068] FIG. 2 illustrates an exemplary block diagram (200) of the system (108) for managing the sequence of trace records in the network (106), in accordance with an embodiment of the present disclosure.

[0069] FIG. 2 with reference to FIG. 1, illustrating the system (108) that may include one or more processor(s) (202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers,digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the 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 configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may comprise 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.

[0070] In an embodiment, the system (108) may include an interface(s) (206). The interface(s) (206) may comprise a variety of interfaces, for example, interfaces for data input and output devices (I / O), storage devices, and the like. The interface(s) (206) may facilitate communication through the system (108). The interface(s) (206) may also provide a communication pathway for one or more components of the system (108). Examples of such components include, but are not limited to, a network function (208), a consumer (210) and a database (212).

[0071] In an embodiment, the network function (208) and the consumer (210) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the network function (208) and the consumer (210). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the network function (208) and the consumer (210) may be processor-executable instructions stored on a non-transitory machine-readable storage medium, and the hardware for the network function (208) and the consumer (210) may comprise a processing resource (for 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 network function (208) and the consumer (210). In such examples, the system (108) may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system (108) and the processing resource. In other examples, the network function (208) and the consumer (210) may be implemented by electronic circuitry.

[0072] In an embodiment, the network function (208) (also referred to as a producer) and the consumer (210) may be implemented within the system (108), such that both entities operate as part of an integrated architecture and communicate with each other over the network (106) to manage the sequence of a plurality of tracerecords. In an embodiment, managing the sequence of the plurality of trace records refers to ensuring orderly handling, continuity, and integrity of the plurality of trace records during transmission and reception, including maintaining consistency in the sequencing of trace records, enabling identification of anomalies, and supporting reliable reconstruction of trace records for subsequent processing. Examples of the network function may include, but is not limited to, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a User Plane Function (UPF), a Policy Control Function (PCF), and a Network Repository Function (NRF), each of which may be configured to generate trace records based on signaling procedures, session management events, or data transmission activities within the network.

[0073] The network function (208) includes a trace record generating unit (210) (also referred to as a trace record generator (TRG)). In order to manage the sequence of the plurality of trace records in the network (106), the trace record generating unit (210) may be configured to generate the plurality of trace records associated with a trace reference. The trace reference is an identifier used to associate the plurality of trace records with a particular trace session corresponding to a subscriber, device, or network activity. In an embodiment, the trace reference may be provided to the network function (208) by a management system based on monitoring requirements, diagnostic requests, or predefined conditions, thereby enabling activation of a trace session at the network function (208).

[0074] In an embodiment, the management system may be configured to control and configure tracing operations within the network (106). The management system may initiate the trace session by transmitting trace configuration information, including the trace reference, to one or more network functions. The management system may further define parameters associated with the trace session, such as scope of tracing, duration, and triggering conditions, thereby enabling selective and controlled generation of the plurality of trace records.

[0075] In an embodiment, the trace record generating unit (210) (e.g., TRG) is a network function component, such as a Radio Access Network (RAN) node or a core network function, responsible for generating trace records based on monitoring and diagnostic activities within the communication network (106). In an embodiment, the trace records are data records that capture detailed information about specific network events or transactions. In an embodiment, the trace records are data records that capture detailed information about specific network events or transactions. The trace records contain monitoring information, including, but not limited to, signaling messages, session states, and performance metrics. In some embodiments, the plurality of trace records may be generated in response to the occurrence of predefined events,procedural triggers, or signaling interactions within the network (106), and may be continuously generated during an active trace session.

[0076] In response to generating the plurality of trace records, the trace record generating unit (210) may assign a sequence number in each header of the plurality of trace records. The sequence number may be implemented as an Information Element (IE) embedded within the header of each trace record and may uniquely represent a relative position of each trace record within a sequence corresponding to a trace reference. The assignment of the sequence number enables tracking of the order in which the plurality of trace records are generated.

[0077] In an embodiment, the trace record generating unit (210) may assign the sequence number for each of the plurality of trace records when the trace reference associated with the plurality of trace records is assigned to the network function (208). In particular, upon receiving the trace reference from the management system, the trace record generating unit (210) may initiate sequence number assignment for the plurality of trace records corresponding to the trace reference, thereby ensuring that all trace records generated under the same trace reference are associated with a continuous sequence.

[0078] In an embodiment, the sequence number may be initialized to zero when a first trace record associated with a trace reference is generated and may be incremented by one for each subsequently generated trace record associated with the same trace reference. For example, if a trace session is initiated for a subscriber session, a first trace record generated for a signaling event may be assigned sequence number “0”, a subsequent trace record for a session update may be assigned sequence number “1”, and so on.

[0079] In an embodiment, the trace record generating unit (210) may determine whether the sequence number has reached a predefined threshold. The predefined threshold may correspond to a maximum permissible value of the sequence number, such as 65535. Upon determining that the sequence number has reached the predefined threshold, the trace record generating unit (210) may reassign the sequence number to zero for a subsequent trace record generated by the trace record generating unit (210). For example, when the sequence number reaches “65535” for a trace record, the next generated trace record may be assigned a sequence number “0”, thereby enabling cyclic reuse of the sequence number range.

[0080] In another embodiment, the trace record generating unit (210) may also determine whether a trace session associated with the trace reference is reactivated with a new trace reference. The new trace reference may be assigned by the managementsystem to indicate initiation of a new trace session or reactivation of a previously terminated trace session. Upon determining that the trace session is reactivated with the new trace reference, the trace record generating unit (210) may reassign the sequence number to zero for the subsequent trace record generated by the trace record generating unit (210), thereby ensuring that sequence numbering is reinitialized for the new trace session and remains consistent within each trace reference.

[0081] Once the sequence number is assigned in the header of the plurality of trace records, the network function (208) may further transmit the plurality of trace records along with the assigned sequence number to the consumer (212) (also referred to as a trace collection entity (TCE)). Each trace record may include the assigned sequence number in its header, thereby enabling the consumer (212) to track the sequence of the plurality of trace records as generated by the trace record generating unit (210).

[0082] In an embodiment, the plurality of trace records may be transmitted to the consumer (212) in a streaming manner over the network (106), where the trace records are delivered continuously as they are generated. For example, during an ongoing call session or data session, multiple trace records corresponding to signaling exchanges may be generated and transmitted in real time. Due to such streaming transmission, variations in network conditions may result in out-of-order delivery or loss of one or more trace records. The inclusion of the sequence number in each header ensures that the consumer (212) is able to maintain visibility of the intended order of the plurality of trace records irrespective of such transmission anomalies.

[0083] In an embodiment, each of the plurality of trace records transmitted in the streaming manner may include a header portion and a payload portion. The header portion of the streaming trace record may include a plurality of fields associated with identification, correlation, and characterization of the trace record. In particular, the header may include a timestamp field indicative of a time at which the trace record is generated, an identifier corresponding to a network function instance that generated the trace record, and a type of the network function associated with the trace record. The header may further include a trace reference field configured to associate the trace record with a trace session, and a trace recording session reference field configured to identify a recording instance corresponding to the trace session.

[0084] The header may further include a trace record type identifier indicative of a type of the trace record, including but not limited to normal trace records, trace session start, trace session stop, trace recording session start, trace recording session stop, heartbeat records, trace recording session not started, trace recording session dropped events, trace file open, trace file close, trace file abnormal closed, and trace recording session throttled start and stop. In an embodiment, such trace record types maycorrespond to administrative messages that indicate lifecycle events of a trace session, such as initiation, termination, heartbeat signaling, or abnormal conditions during trace recording. These administrative messages enable the consumer (212) to understand the state and progression of the trace session without relying solely on payload data. In an embodiment, the trace record type identifier with value “normal” may correspond to trace records that do not carry administrative messages.

[0085] In some embodiments, the header may optionally include a radio access network user equipment identifier (ranUeld) associated with traced signaling information, a pay load schema identifier configured to indicate a format of the pay load, and a global base station identifier (globalGnbld) applicable for trace records reported by network nodes such as gNB-CU-CP, gNB-CU-UP, or gNB-DU. Further, the header may include one or more vendor-specific extension fields represented as a set of keyvalue pairs to support extensibility.

[0086] In an embodiment, the header may further include a sequence number field configured to maintain sequence integrity of the plurality of trace records. The sequence number may be set (assigned) when a trace reference is assigned to the trace record generating unit, such that the sequence number is associated with each trace record corresponding to the trace reference. The sequence number may be represented as a two-byte octet value within a predefined range, such as 0 to 65535. The sequence number may be initialized at a beginning of a trace session and incremented for each subsequent trace record. In an embodiment, the sequence number may be reassign when the sequence number reaches an upper limit or when a trace session is reactivated with a new trace reference, thereby ensuring consistent sequencing within each trace session.

[0087] In an embodiment, the trace recording session reference may be present in trace records associated with a trace recording session, including trace records carrying non-zero payload or administrative messages corresponding to session start or stop events. Further, the ranUeld field may be included when such identifier is captured in traced signaling messages and supported by the radio access network. In some embodiments, the payload schema identifier may not be required for trace records having zero-size payload or for trace records carrying administrative messages. Additionally, vendor-specific extensions may be implemented as generic key-value pairs.

[0088] In an embodiment, the payload portion of the streaming trace record may include trace data corresponding to captured network events or signaling information. However, in accordance with the present disclosure, processing of the plurality of trace records, including ordering and detection of missing trace records, is performed basedon the sequence number included in the header, without requiring inspection or modification of the payload portion of the trace record. This approach provides multiple advantages, including a reduction in computational overhead by eliminating the need for payload parsing, faster processing of large volumes of trace records in high-throughput environments, and improved scalability of the consumer (212). Further, since payload data may include complex encoded structures or sensitive information, avoiding payload inspection enhances data security and preserves confidentiality. Additionally, reliance on the sequence number enables consistent and deterministic ordering of trace records independent of payload format variations or timestamp inconsistencies.

[0089] In an embodiment, upon receiving the plurality of trace records, the consumer (212) may track the sequence of each of the plurality of trace records based on the assigned sequence number. The tracking may include maintaining a sequence tracking log that stores an expected sequence number corresponding to the plurality of trace records. The expected sequence number may represent a next anticipated sequence value for a subsequently received trace record.

[0090] For example, if the consumer (212) receives trace records with sequence numbers “0”, “1”, and “2”, the sequence tracking log may store an expected sequence number “3”. If a subsequent trace record with sequence number “4” is received, the consumer (212) may detect a deviation from the expected sequence. Such tracking enables the consumer (212) to continuously monitor the integrity and ordering of incoming trace records.

[0091] In an embodiment, based on the tracking, the consumer (212) may determine at least one of: whether the plurality of trace records are received out of order, and whether one or more trace records are missing from the plurality of trace records. In order to determine the one or more missing trace records, the consumer (212) may process the plurality of trace records based on the sequence number associated with each header of the plurality of trace records. In particular, the consumer (212) may extract the sequence number from each header of the plurality of trace records, compare the received sequence number with the expected sequence number stored in the sequence tracking log, and identify a mismatch indicative of a gap in sequence.

[0092] In an embodiment, the extraction may include reading the sequence number field embedded in the header without accessing or decoding the payload portion of the trace record. The comparison may be performed to determine whether the received trace record follows the expected sequence progression. In an embodiment, if the extracted sequence number matches the expected sequence number, the consumer (212) may update the sequence tracking log to reflect the next expected sequencenumber by incrementing the expected sequence number. For example, upon receiving a trace record with sequence number “3”, the expected sequence number may be updated to “4”. In an embodiment, if the extracted sequence number does not match the expected sequence number, the consumer (212) may identify a mismatch indicative of the gap in the sequence. Such a mismatch may correspond to the one or more missing trace records or out-of-order reception of trace records.

[0093] For example, if the expected sequence number is “3” and the consumer (212) receives a trace record with sequence number “5”, the consumer (212) may determine that trace record(s) corresponding to sequence number “3” and / or “4” are missing. Similarly, if a trace record with sequence number “2” is received after receiving sequence number “4”, the consumer (212) may determine that the plurality of trace records are received out of order.

[0094] In an embodiment, upon determining that the plurality of trace records are received out of order, the consumer (212) may arrange the plurality of trace records in a sequential order based on the assigned sequence number. The arrangement may be performed without modifying payload information or timestamp information associated with the plurality of trace records, thereby preserving the integrity of the trace data.

[0095] For example, if trace records are received in an order such as “0”, “2”, “1”, “3”, the consumer (212) may rearrange the trace records into a correct sequential order “0”, “1”, “2”, “3” based on the sequence numbers. This approach eliminates the need for inspecting payload contents or relying on timestamp-based ordering, thereby reducing processing overhead and enabling efficient handling of large volumes of trace records in high-throughput network environments.

[0096] In an embodiment, upon detecting one or more missing trace records, the consumer (212) may trigger an alert indicating the detection of the one or more missing trace records. The alert may include transmitting a notification to the trace record generating unit (210) to determine a root cause for the missing or incorrect order of the trace records. In an example, the consumer (212) may generate an alert when a sequence gap is detected, such as missing sequence number “3” in a sequence “0, 1, 2, 4”. The alert may include information indicative of the missing sequence number, trace reference, and time of occurrence.

[0097] In an embodiment, the consumer (212) may perform one or more operations on the plurality of trace records arranged in the sequential order for analysis of network performance. Such operations may include processing and analyzing the plurality of trace records to identify network issues, evaluate signaling behavior, detect anomalies,and support troubleshooting activities. For example, the ordered trace records may be analyzed to determine latency patterns, call drops, or signaling failures, thereby enabling efficient network monitoring and optimization.

[0098] In an embodiment, the database (214) may store data generated as a result of functionalities implemented by one or more components of the network function (208) and the consumer (210). The stored data may include, but is not limited to, the plurality of trace records, sequence numbers associated with each trace record, sequence tracking logs, expected sequence number values, alert information corresponding to detected missing trace records, and analysis results derived from processing the plurality of trace records. In an embodiment, the database (214) may be implemented as a relational database, a distributed database, a cloud-based database, or any combination thereof, depending on deployment requirements and scalability considerations. The database (214) may further support storage and retrieval of large volumes of streaming trace data in real time.

[0099] By addressing the challenges of the absence of sequence tracking, out-of-order reception, and undetected loss of trace records in streaming -based transmission, the system (108) provides an efficient and reliable mechanism for managing the sequence of the plurality of trace records in the network (106). The introduction of a sequence number in the header of each trace record enables accurate identification of missing trace records, facilitates deterministic reordering of trace records received out of order, and ensures the integrity and completeness of trace data. Further, the system (108) provides enhanced processing efficiency by eliminating dependency on payload inspection or timestamp-based ordering, thereby reducing computational overhead and enabling faster handling of large volumes of trace records in high-throughput network environments. The disclosed system (108) also improves the scalability and reliability of trace data collection and analysis, supporting real-time or near real-time network monitoring, efficient troubleshooting, and optimized network performance. Accordingly, the present disclosure provides a robust, low-overhead, and scalable solution for sequence management of trace records in communication networks.

[0100] Although FIG. 2 shows exemplary components of the system (108), in other embodiments, the system (108) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 2. Additionally, or alternatively, one or more components of the system (108) may perform functions described as being performed by one or more other components of the system (108).

[0101] FIG. 3 illustrates an exemplary system architecture (300) for managing the sequence of trace records in the network (106), in accordance with an embodiment of the present disclosure. FIG. 3 is explained in conjunction with the FIGs. 1 and 2.

[0102] The system architecture (300) includes a management system (302). The system architecture (300) further includes a Radio Access Network (RAN) (304), a core network (306), and a Trace Collection Entity (TCE) (308) (analogous to the consumer (212)). The RAN (304) may be a Fourth Generation / Fifth Generation / Sixth Generation (4G / 5G / 6GRAN). Similarly, the core network (306) may be a 4G / 5G / 6G core network. The 4G / 5G / 6G RAN (304) and the 4G / 5G / 6G core network (306) may include one or more network functions configured to generate trace records and are collectively referred to as trace record generating entities.

[0103] The management system (302) may be configured to control and configure tracing operations within the network (106). In an embodiment, the management system (302) may transmit trace configuration information to the RAN (304) and the core network (306). The trace configuration may include one or more parameters, such as a trace reference, the scope of tracing, triggering conditions, and the duration of a trace session. Based on the received trace configuration, the RAN (304) and the core network (306) may initiate the generation of a plurality of trace records corresponding to the trace reference.

[0104] In an embodiment, the RAN (304) and the core network (306), acting as trace record generating units, may generate the plurality of trace records in response to monitoring events, signaling procedures, or diagnostic triggers occurring within the network (106). The plurality of trace records may correspond to activities such as session establishment, session modification, handover procedures, or data transmission events. The generated trace records may be associated with a trace reference received from the management system (302), thereby enabling correlation of the plurality of trace records with a specific trace session.

[0105] The present disclosure assigns a sequence number as an Information Element (IE) within a header of each trace record to enhance traceability and sequence management. The sequence number IE may be implemented as a two-byte octet field configured to maintain sequence integrity of the plurality of trace records. In an embodiment, the sequence number may range from 0 to 65535 and may be incremented for each subsequent trace record associated with a trace reference.

[0106] In an embodiment, the trace record generating entities (RAN 304, core network 306) may determine whether the sequence number has reached a predefined threshold corresponding to an upper limit of the sequence number range. Upondetermining that the sequence number has reached the predefined threshold, the sequence number may be reassigned to zero for a subsequent trace record.

[0107] In an embodiment, when a trace reference is assigned to the trace record generating entities (304, 306) by the management system (302), the trace record generating entities may assign the sequence number to each of the plurality of trace records associated with the trace reference. The sequence number may be initialized at the beginning of a trace session and incremented for each subsequently generated trace record.

[0108] In another embodiment, the trace record generating entities may determine whether a trace session associated with the trace reference is reactivated with a new trace reference. Upon determining that the trace session is reactivated with the new trace reference, the trace record generating entities may reassign the sequence number to zero for subsequent trace records, thereby ensuring that sequence numbering remains consistent within each trace session.

[0109] Further, the RAN (304) and the core network (306) may transmit the plurality of trace records, including the assigned sequence number in the header, to the TCE (308) in a streaming manner over the network (106).

[0110] In an embodiment, the TCE (308) may be configured to receive the plurality of trace records from the RAN (304) and the core network (306) and track a sequence of the plurality of trace records based on the sequence number included in the header. The TCE (308) may determine whether the plurality of trace records are received out of order and whether one or more trace records are missing based on the assigned sequence number.

[0111] In an embodiment, the TCE (308) may identify missing trace records by detecting gaps in the sequence number. For example, if a sequence number expected to be received is absent in a received sequence of trace records, the TCE (308) may determine that one or more trace records corresponding to the missing sequence number are not received.

[0112] In an embodiment, upon determining that the plurality of trace records are received out of order, the TCE (308) may arrange the plurality of trace records in a sequential order based on the assigned sequence number. The arrangement of the plurality of trace records may be performed without requiring inspection of payload information or timestamp information associated with the plurality of trace records, thereby reducing processing overhead and improving efficiency.

[0113] Further, upon detecting one or more missing trace records, the TCE (308) may trigger an alert to indicate potential data loss. The use of the sequence number for detecting missing trace records and reordering out-of-order trace records enhances data integrity, improves traceability, and supports accurate network monitoring and analysis.

[0114] FIG. 4 illustrates an exemplary process flow (400) for managing the sequence of trace records in the network (106), in accordance with an embodiment of the present disclosure. FIG. 4 is explained in conjunction with the FIGs. 1, 2 and 3. The present FIG. 4 depicts the interaction between the RAN / core network Functions (NFs) (containing TRG) (analogous to the trace record generating unit 210) (402) and the TCE (404) (analogous to the consumer (212)) for managing the sequence of trace records.

[0115] In operation, to manage the sequence of trace records, the TRG (402) may be triggered to generate a plurality of trace records (e.g., trace record 1, trace record 2, trace record 3, ... trace record N) associated with a trace reference. In response to generating the plurality of trace records, the TRG (402) may assign a sequence number in each header of the plurality of trace records. The sequence number may be assigned to indicate an order in which the plurality of trace records are generated. For example, the generated trace record 1 may be assigned a sequence number 1, the generated trace record 2 may be assigned a sequence number 2 and so on.

[0116] To further elaborate, the TRG within the RAN / core NFs (402) is configured to generate trace records and assign a sequence number in each header of the generated trace records. The sequence number follows a defined algorithm to ensure unique identification and proper ordering. When the TRG (e.g., the RAN / core NFs) (402) is triggered to create a new trace record, it initializes the sequence number. If it is the first trace record in the trace session, the sequence number is set to 0. For each subsequent trace record, the sequence number increments by 1. If the sequence number reaches its upper limit of 65535, it reassigned to 0 to maintain continuity. The assigned sequence number is inserted in the trace record header, ensuring seamless tracking. The RAN / core NFs (TRG) (404) then transmit the trace record with its corresponding sequence number and wait for the next trace request, repeating the process.

[0117] Ideally, the RAN / core NFs (TRG) (402) sends multiple trace records sequentially, starting from trace record 1 with sequence number 1, at step (406), followed by trace record 2 with sequence number 2, at step (408), and trace record 3 with sequence number 3, at step (410), and so on until trace record N with sequence number N, at step (412). In an embodiment, these sequences of trace records arereceived by the TCE (404), which is responsible for ensuring proper sequencing of the trace records.

[0118] However, during transmission of trace records from the TRG (402) to the TCE (404), some of the trace records may be lost or arrive out of order due to varying network conditions such as congestion, packet loss, or latency. This requires a mechanism at the TCE (404) to verify sequence integrity and ensure complete data reconstruction. To identify the missing trace records, the TCE (404) receives incoming trace records and extracts their sequence numbers from the header. The TCE (404) maintains a sequence tracking log to verify whether all records have arrived in the expected order. The sequence handling logic at the TCE (404) involves receiving and evaluating incremental sequence numbers to verify continuity and handling trace session restart: if sequence number 0 is received in a new trace session (with a new trace reference), the TCE (404) considers it the first trace record of that session; and if sequence number 0 is received in an existing trace session (with the same trace reference), the TCE (404) treats it as a continuation of an ongoing session, accounting for sequence number wraparound.

[0119] To ensure data integrity, the TCE (404) compares the received sequence numbers with expected values. If a gap is detected (for example, if the expected sequence number is 105, but the next received record is 106), the TCE (404) identifies the missing trace record (for example, 105 is lost). The missing records alert may be triggered to determine the root cause.

[0120] In some embodiments, if trace records arrive out of order, the TCE (404) arranges them in sequential order before processing. The sequence number allows TCE (404) to reorder records efficiently without inspecting the payload or the timestamps, reducing the significant processing overhead of payload inspection or timestamp parsing.

[0121] In some embodiments, once all trace records are ordered correctly or received in a correct order, the TCE (404) processes and analyzes the trace data for network monitoring and troubleshooting. If missing records are identified, additional corrective actions, such as the TCE (404), may trigger an alert for the missing trace records and analyze a root cause to avoid further replication of a similar network / TRG state. The approach to trace record handling ensures robust data integrity, minimizing the risk of missing critical diagnostic information.

[0122] FIG. 5 illustrates an exemplary flow diagram of a method (500) implemented by the system (108) for managing the sequence of trace records in the network, inaccordance with an embodiment of the present disclosure. FIG. 5 is explained in conjunction with the FIGs. 1, 2, 3 and 4.

[0123] At step (502), the method (500) includes generating, by a trace record generating unit (210) in a network function (208), the plurality of trace records associated with a trace reference. The plurality of trace records may be generated based on monitoring events, signaling interactions, or diagnostic triggers corresponding to a trace session associated with the trace reference.

[0124] At step (504), in response to generating, the method (500) includes assigning, by the trace record generating unit (210), a sequence number in each header of the plurality of trace records. In an embodiment, assigning the sequence number may include assigning the sequence number when the trace reference associated with the plurality of trace records is assigned to the network function. Further, assigning the sequence number may include initializing the sequence number to zero when a first trace record from the plurality of trace records is generated and incrementing the sequence number by one for each subsequently generated trace record associated with the trace reference.

[0125] In an embodiment, the method (500) may further include determining whether the sequence number has reached a predefined threshold, and upon determining that the sequence number has reached the predefined threshold, reassigning the sequence number to zero for a subsequent trace record. In another embodiment, the method (500) may include determining whether a trace session associated with the trace reference is reactivated with a new trace reference, and upon determining that the trace session is reactivated with the new trace reference, reassigning the sequence number to zero for subsequent trace records.

[0126] At step (506), the method (500) includes transmitting, by the network function (208), the plurality of trace records and the assigned sequence number to a consumer. In an embodiment, the plurality of trace records may be transmitted in a streaming manner over the network (106), such that the trace records are delivered continuously as they are generated.

[0127] At step (508), the method (500) includes tracking, by the consumer (212), the sequence of each of the plurality of trace records received from the trace record generating unit. In an embodiment, tracking may include maintaining a sequence tracking log, wherein the sequence tracking log stores an expected sequence number associated with the plurality of trace records to verify whether the plurality of trace records are received in a sequential order based on the assigned sequence number.

[0128] At step (510), the method (500) includes determining, by the consumer (212), at least one of: whether the plurality of trace records are received out of order, and whether one or more trace records are missing from the plurality of trace records based on the assigned sequence number in the header. In an embodiment, determining the one or more missing trace records may include extracting the sequence number from each header of the plurality of trace records, comparing the sequence number of each of the plurality of trace records received from the trace record generating unit with the expected sequence number stored in the sequence tracking log, and upon comparing, identifying the one or more missing trace records based on detecting a mismatch between the received sequence number and the expected sequence number.

[0129] At step (512), upon determining that the plurality of trace records are received out of order, the method (500) includes arranging, by the consumer (212), the plurality of trace records in a sequential order based on the assigned sequence number. In an embodiment, payload information and timestamp information associated with the plurality of trace records remain unchanged during the arranging of the plurality of trace records in the sequential order.

[0130] In particular, since the arranging is performed solely based on the sequence number present in the header, the consumer (212) is not required to parse, decode, or modify the payload portion of the trace records. This reduces computational complexity and processing overhead, especially in high-throughput environments where a large volume of trace records is processed in real time. Further, preserving the payload ensures that the original trace data remains intact, thereby maintaining data integrity and preventing unintended alteration of diagnostic information. Additionally, avoiding reliance on timestamp information eliminates issues arising from clock synchronization discrepancies across different network functions, which may otherwise lead to incorrect ordering if timestamps are used.

[0131] At step (514), the method (500) includes triggering, by the consumer (212), an alert upon detecting the one or more missing trace records. In an embodiment, triggering the alert may include transmitting, by the consumer, a notification to the trace record generating unit indicating detection of the one or more missing trace records.

[0132] In an embodiment, the method (500) may further include performing one or more operations on the plurality of trace records arranged in the sequential order for analysis of network performance. The one or more operations may include processing the plurality of trace records to identify network anomalies, analyze signaling behavior, and support troubleshooting of network events.

[0133] FIG. 6 illustrates an exemplary computer system (600) in which or with which embodiments of the present disclosure may be implemented.

[0134] As shown in FIG. 6, the computer system (600) may include an external storage device (610), a bus (620), a main memory (630), a read-only memory (640), a mass storage device (650), communication port(s) (660), and a processor (670). A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. The processor (670) may include various modules associated with embodiments of the present disclosure.

[0135] The communication port(s) (660) 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 port(s) (660) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system connects.

[0136] The main memory (630) may be random access memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (640) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor (670).

[0137] The mass storage device (650) may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage device (650) includes, but is not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks.

[0138] The bus (620) communicatively couples the processor (670) with the other memory, storage, and communication blocks. The bus (620) may be, e.g., a Peripheral Component Interconnect (PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (670) to the computer system.

[0139] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus (620) to support direct operator interaction with the computer system. Other operator and administrativeinterfaces can be provided through network connections connected through the communication port(s) (660). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.

[0140] In an exemplary embodiment, a network function for managing a sequence of a plurality of trace records in a network is disclosed. The network function includes a trace record generating unit configured to generate a plurality of trace records associated with a trace reference; assign a sequence number in each header of the plurality of trace records; and transmit the plurality of trace records and the assigned sequence number to a consumer.

[0141] In an exemplary embodiment, a consumer for managing a sequence of a plurality of trace records in a network is disclosed. The consumer is configured to receive the plurality of trace records and an associated sequence number assigned in each header of the plurality of trace records from a network function; track a sequence of the plurality of trace records; determine at least one of: the plurality of trace records are received out of order, and one or more missing trace records from the plurality of trace records based on the assigned sequence number in the header; arrange the plurality of trace records in sequential order based on the assigned sequence number; and trigger an alert upon detecting the one or more missing trace records.

[0142] In an exemplary embodiment, a computer program product including a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or more processors to perform a method for managing a sequence of a plurality of trace records in a network. The method includes generating, by a trace record generating unit in a network function, the plurality of trace records associated with a trace reference; in response to generating, assigning, by the trace record generating unit, a sequence number in each header of the plurality of trace records; transmitting, by the network function, the plurality of trace records and the assigned sequence number to a consumer; tracking, by the consumer, the sequence of each of the plurality of trace records received from the trace record generating unit; determining, by the consumer, at least one of: the plurality of trace records are received out of order, and one or more missing trace records from the plurality of trace records based on the assigned sequence number in the header; upon determining that the plurality of trace records are received out of order, arranging, by the consumer, the plurality of trace records in a sequential order based on the assigned sequence number; and triggering, by the consumer, an alert upon detecting the one or more missing trace records.

[0143] The present disclosure provides a technical advancement by introducing a sequence number-based mechanism within a header of each trace record for managing a sequence of a plurality of trace records in a communication network. In existing trace mechanisms, trace records are transmitted without inherent support for maintaining sequence integrity or detecting loss of trace records at an application layer, thereby resulting in challenges such as out-of-order reception and undetected missing trace records. The present disclosure addresses these limitations by enabling assignment of a sequence number to each trace record, thereby facilitating accurate tracking, detection of missing trace records through identification of sequence gaps, and deterministic reordering of trace records at a consumer.

[0144] Further, the present disclosure enables processing of the plurality of trace records based on the sequence number without requiring inspection of payload information or reliance on timestamp-based ordering, thereby reducing computational overhead, improving processing efficiency, and enhancing scalability in high-throughput network environments. Additionally, the disclosed mechanism ensures data integrity and completeness of trace records, supports real-time or near real-time network monitoring, and improves reliability of troubleshooting and analysis. Accordingly, the present disclosure provides a robust, low-overhead, and scalable solution for sequence management of trace records, thereby enhancing overall network performance and operational efficiency.

[0145] The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

[0146] 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 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 is to be implemented merely as illustrative of the disclosure and not as a limitation.TECHNICAL ADVANCEMENTS

[0147] The present disclosure provides a system and a method for managing a sequence of trace records in a network by identifying missing trace records based on a sequence number analysis. This enables the detection of data loss or gaps in the trace records and ensures data reliability.

[0148] The present disclosure maintains data integrity (data reconciliation) by ensuring the completeness of trace records, which is essential for accurate monitoring, diagnosing network issues, and analyzing network performance.

[0149] The present disclosure introduces an efficient reordering mechanism that allows a Trace Collection Entity (TCE) to reassemble trace records in the correct sequence without parsing the payload or relying on timestamps. This capability minimizes processing overhead and enables precise procedural or call flow-level analysis, thereby improving the accuracy and speed of network troubleshooting.

[0150] The present disclosure contributes to enhanced network performance by allowing network operators to promptly detect and address trace record losses, leading to faster issue resolution and proactive network optimization.

[0151] The present disclosure provides significant benefits with minimal overhead by adding a sequence number field to the header of the trace records. This enhancement significantly improves trace record management without imposing substantial data or processing burdens on the network functions.

[0152] The present disclosure strengthens compliance with existing trace mechanisms by addressing a critical limitation in managing trace records. The proposed solution extends the robustness of current practices, making the trace mechanism more effective in handling complex network environments (such as Fifth Generation (5G), Internet of Things (loT), and cloud computing), ensuring seamless connectivity and efficient telecom operations.

Claims

CLAIMSWe Claim:

1. A method (500) for managing a sequence of a plurality of trace records in a network (106), the method (500) comprising:generating (502), by a trace record generating unit (210) in a network function (208), the plurality of trace records associated with a trace reference;in response to generating, assigning (504), by the trace record generating unit (210), a sequence number in each header of the plurality of trace records;transmitting (506), by the network function (208), the plurality of trace records and the assigned sequence number to a consumer (212);tracking (508), by the consumer (212), the sequence of each of the plurality of trace records received from the trace record generating unit (210);determining (510), by the consumer (212), at least one of: the plurality of trace records are received out of order, and one or more missing trace records from the plurality of trace records based on the assigned sequence number in the header;upon determining that the plurality of trace records are received out of order, arranging (512), by the consumer (212), the plurality of trace records in a sequential order based on the assigned sequence number; andtriggering (514), by the consumer (212), an alert upon detecting the one or more missing trace records.

2. The method (500) as claimed in claim 1, wherein triggering the alert comprises: transmitting, by the consumer (212), a notification to the trace record generating unit (210) indicating detection of the one or more missing trace records.

3. The method (500) as claimed in claim 1, wherein payload information and timestamp information associated with the plurality of trace records remain unchanged during the arranging of the plurality of trace records in the sequential order.

4. The method (500) as claimed in claim 1, further comprises:performing, by the consumer (212), one or more operations on the plurality of trace records arranged in the sequential order for analysis of network performance.

5. The method (500) as claimed in claim 1, wherein tracking the sequence of each of the plurality of trace records comprises:maintaining, by the consumer (212), a sequence tracking log, wherein the sequence tracking log stores an expected sequence number associated with the plurality of trace records to verify whether the plurality of trace records are received in the sequential order based on the assigned sequence number.

6. The method (500) as claimed in claim 1, wherein determining the one or more missing trace records comprises:extracting, by the consumer (212), the sequence number from each header of the plurality of trace records;comparing, by the consumer (212), the sequence number of each of the plurality of trace records received from the trace record generator with the expected sequence number stored in the sequence tracking log; andupon comparing, identifying, by the consumer (212), the one or more missing trace records based on detecting a mismatch between the received sequence number and the expected sequence number.

7. The method (500) as claimed in claim 1, wherein assigning the sequence number comprises:assigning, by the trace record generating unit (210), the sequence number for each of the plurality of trace records when the trace reference associated with the plurality of trace records are assigned to the network function (208).

8. The method (500) as claimed in claim 1, wherein assigning the sequence number comprises:initializing, by the trace record generating unit (210), the sequence number to zero when a first trace record from the plurality of trace records is generated; and incrementing, by the trace record generating unit (210), the sequence number by one for each subsequently generated trace record associated with the trace reference.

9. The method (500) as claimed in claim 7, further comprising:determining, by the trace record generating unit (210), whether the sequence number has reached a predefined threshold; andupon determining that the sequence number has reached the predefined threshold, reassigning by the trace record generating unit (210), the sequence number to zero for a subsequent trace record generated by the trace record generating unit (210).

10. The method (500) as claimed in claim 7, further comprising:determining, by the trace record generating unit (210), whether a trace session associated with the trace reference is reactivated with a new trace reference; and upon determining that the trace session is reactivated with the new trace reference, reassigning, by the trace record generating unit (210), the sequence number to zero for the subsequent trace record generated by the trace record generating unit (210).

11. A network function (208) for managing a sequence of a plurality of trace records in a network (106), the network function (208) comprising:a trace record generating unit (210) configured to:generate a plurality of trace records associated with a trace reference; assign a sequence number in each header of the plurality of trace records; andtransmit the plurality of trace records and the assigned sequence number to a consumer (212).

12. The network function (208) as claimed in claim 11, wherein payload information and timestamp information associated with the plurality of trace records remain unchanged during the arranging of the plurality of trace records in the sequential order.

13. The network function (208) as claimed in claim 11, wherein the trace record generating unit (210) is configured to assign the sequence number for each of the plurality of trace records when the trace reference associated with the plurality of trace records is assigned to the network function (208); wherein to assign the sequence number, the trace record generating unit (210) is configured to:initialize the sequence number to zero when a first trace record from the plurality of trace records is generated; andincrement the sequence number by one for each subsequently generated trace record associated with the trace reference.

14. The network function (208) as claimed in claim 13, wherein the trace record generating unit (210) is configured to:determine whether the sequence number has reached a predefined threshold; andupon determining that the sequence number has reached the predefined threshold, reassign the sequence number to zero for a subsequent trace record generated by the trace record generating unit (210).

15. The network function (208) as claimed in claim 13, wherein the trace record generating unit (210) is configured to:determine whether a trace session associated with the trace reference is reactivated with a new trace reference; andupon determining that the trace session is reactivated with the new trace reference, reassign the sequence number to zero for the subsequent trace record generated by the trace record generating unit (210).

16. A consumer (212) for managing a sequence of a plurality of trace records in a network (106), wherein the consumer (212) is configured to:receive the plurality of trace records and an associated sequence number assigned in each header of the plurality of trace records from a network function (208);track a sequence of the plurality of trace records;determine at least one of: the plurality of trace records are received out of order, and one or more missing trace records from the plurality of trace records based on the assigned sequence number in the header;arrange the plurality of trace records in sequential order based on the assigned sequence number; andtrigger an alert upon detecting the one or more missing trace records.

17. The consumer (212) as claimed in claim 16, wherein to trigger the alert, the consumer (212) is configured to:transmit a notification to the network function (208) indicating detection of the one or more missing trace records.

18. The consumer (212) as claimed in claim 16, wherein the consumer (212) is configured to:perform one or more operations on the plurality of trace records arranged in the sequential order for analysis of network performance.

19. The consumer (212) as claimed in claim 16, wherein to track the sequence of each of the plurality of trace records, the consumer (212) is configured to:maintain a sequence tracking log, wherein the sequence tracking log stores an expected sequence number associated with the plurality of trace records to verify whether the plurality of trace records are received in the sequential order based on the assigned sequence number; andwherein to determine the one or more missing trace records, the consumer (212) is configured to:extract the sequence number from each header of the plurality of trace records; compare the sequence number of each of the plurality of trace records received from the trace record generator with the expected sequence number stored in the sequence tracking log; andupon comparing, identify the one or more missing trace records based on detecting a mismatch between the received sequence number and the expected sequence number.

20. A computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, causethe one or more processors to perform a method (500) for managing a sequence of a plurality of trace records in a network (106), the method (500) comprising:generating (502), by a trace record generating unit (210) in a network function (208), the plurality of trace records associated with a trace reference;in response to generating, assigning (504), by the trace record generating unit (210), a sequence number in each header of the plurality of trace records;transmitting (506), by the network function (208), the plurality of trace records and the assigned sequence number to a consumer (212);tracking (508), by the consumer (212), the sequence of each of the plurality of trace records received from the trace record generating unit (210);determining (510), by the consumer (212), at least one of: the plurality of trace records are received out of order, and one or more missing trace records from the plurality of trace records based on the assigned sequence number in the header;upon determining that the plurality of trace records are received out of order, arranging (512), by the consumer (212), the plurality of trace records in a sequential order based on the assigned sequence number; andtriggering (514), by the consumer (212), an alert upon detecting the one or more missing trace records.

Images