DESC:
FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
METHOD AND SYSTEM FOR CREATING PROCEDURE DATA RECORDS (PDR)
2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN OFFICE-101, SAFFRON, NR. CENTRE POINT, PANCHWATI 5 RASTA, AMBAWADI, AHMEDABAD 380006, GUJARAT, INDIA
3.PREAMBLE TO THE DESCRIPTION

THE FOLLOWING SPECIFICATION PARTICULARLY DESCRIBES THE NATURE OF THIS INVENTION AND THE MANNER IN WHICH IT IS TO BE PERFORMED.

FIELD OF THE INVENTION
[0001] The present invention relates to wireless communication network, more particularly relates to a method and system for creating Procedure Data Records (PDR).
BACKGROUND OF THE INVENTION
[0002] In a wireless communication network such as a 5G network, there are many Network Functions (NFs). Further, there are hundreds of network instances for each NF. For soft probe-based solutions, structure and format of the records sent by 10 network nodes basis network events is not available and is not standardized. Also, the exact RCA (which NF or procedure or interface is contributing for the error) is also not available directly from the summary logs.
[0003] Therefore, there is a need for a method to efficiently define or standardize a record structure for user data.
SUMMARY OF THE INVENTION
[0004] One or more embodiments of the present disclosure provide a method and system for creating Procedure Data Records (PDR).
[0005] In one aspect of the present invention, the system for creating PDR is disclosed. The system includes a transceiver configured to receive a plurality of Streaming Data Records (SDRs) from a plurality of Network Functions (NFs). The system further includes a data stitching module configured to stitch the plurality of SDRs in order to create a single end-to-end (E2E) Procedure Data Record (PDR). Further, each of the plurality of SDRs are stitched in order to create a single PDR using a unique identifier related to a subscriber. The system further includes a storage module configured to store a created PDR in a database subsequent to creation of the PDR.
[0006] In an embodiment, the plurality of Network Functions (NFs) includes at least one of, but not limited to, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), and a Policy Control Function (PCF).
[0007] In an embodiment, a display unit subsequent to creating the PDR, displays the created PDR. The display of the created PDR depicts information related to at least one of the one or more NFs, one or more procedures, one or more interfaces, or modules causing the error which affects a subscriber session.
[0008] In an embodiment, the unique identifier includes at least one of, a Subscription Permanent Identifier (SUPI), a Subscription Concealed Identifier (SUCI), and a Permanent Equipment Identifier (PEI).
[0009] In an embodiment, the transceiver transmits the created PDR to an automatic Root Cause Analysis (RCA) unit. An Artificial Intelligence/Machine Learning (AI/ML) engine of the system facilitates a user to identify the errors with at least one of, the one or more NFs of the plurality of NFs.
[0010] In an embodiment, the created PDR represents the error originating from the one or more NFs when the at least one of the plurality of SDRs received from the respective NF includes an error clear code.
[0011] In an embodiment, the plurality of SDRs is correlated by stitching the plurality of SDRs.
[0012] In an embodiment, the created PDR pertains to aggregated data record for a procedure, wherein the aggregated data includes details of the error and error generating NF.
[0013] In another aspect of the present invention, the method for creating PDR is disclosed. The method includes the step of receiving a plurality of Streaming Data Records (SDRs) from a plurality of Network Functions (NFs). The method further includes the step of stitching the plurality of SDRs in order to create a single end-to-end (E2E) Procedure Data Record (PDR). Further, each of the plurality of SDRs are stitched in order to create a single PDR using a unique identifier related to a subscriber. The method further includes the step of storing a created PDR in a database subsequent to creation of the PDR.
[0014] In another aspect of the invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions is disclosed. The computer-readable instructions are executed by a processor. The processor is configured to receive a plurality of Streaming Data Records (SDRs) from a plurality of Network Functions (NFs). The processor is configured to stitch the plurality of SDRs in order to create a single end-to-end (E2E) Procedure Data Record (PDR). Further, each of the plurality of SDRs are stitched in order to create a single PDR using a unique identifier related to a subscriber. The processor is configured to store a created PDR in a database subsequent to creation of the PDR.
[0015] In another aspect of invention, User Equipment (UE) is disclosed. The UE includes one or more primary processors communicatively coupled to one or more processors, the one or more primary processors coupled with a memory. The processor causes the UE to display, to a user, the created PDR which depicts information related to the error which affects the subscriber session.
[0016] Other features and aspects of this invention will be apparent from the following description and the accompanying drawings. The features and advantages described in this summary and in the following detailed description are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art, in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.
BRIEF DESCRIPTION OF THE DRAWINGS
[0017] 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.
[0018] FIG. 1 is an exemplary block diagram of an environment for creating Procedure Data Records (PDR), according to one or more embodiments of the present invention;
[0019] FIG. 2 is an exemplary block diagram of a system for creating PDR according to one or more embodiments of the present invention;
[0020] FIG. 3 is a schematic representation of a workflow of the system of FIG. 1, according to the one or more embodiments of the present invention;
[0021] FIG. 4 is a signal flow diagram for creating PDR, according to one or more embodiments of the present invention; and
[0022] FIG. 5 is a schematic representation of a method for creating PDR, according to one or more embodiments of the present invention.
[0023] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0024] Some embodiments of the present disclosure, illustrating all its features, will now be discussed in detail. It must also be noted that as used herein and in the appended claims, the singular forms "a", "an" and "the" include plural references unless the context clearly dictates otherwise.
[0025] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. However, one of ordinary skill in the art will readily recognize that the present disclosure including the definitions listed here below are not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
[0026] A person of ordinary skill in the art will readily ascertain that the illustrated steps detailed in the figures and here below are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0027] The present disclosure provides creation of procedure data records. In the present disclosure, multiple Streaming Data Records (SDRs) from different Network Functions (NFs) or for different procedures, are stitched together, correlated and then single summary record Procedure Data Record (PDR) is created which captures information of the NF, procedure, interface, or module causing the issue and affecting the subscriber session. That is, the present disclosure correlates subscriber level records and creates a single summary record.
[0028] FIG. 1 illustrates an exemplary block diagram of an environment 100 for creating Procedure Data Records (PDR), according to one or more embodiments of the present disclosure. In this regard, the environment 100 includes a User Equipment (UE) 102, a server 104, a network 106 and a system 108 communicably coupled to each other for creating the PDR. The PDR is a type of data record that captures detailed information about the procedures or actions taken within the network 106, typically related to subscriber activity and network function interactions. The subscriber activity includes, but is not limited to, data usage, voice calls, messaging, mobility, service requests. The network functions include, but are not limited to, baseband processing, Radio Resource Management (RRM), packet core functions, session management, authentication and authorization.
[0029] As per the illustrated embodiment and for the purpose of description and illustration, the UE 102 includes, but not limited to, a first UE 102a, a second UE 102b, and a third UE 102c, and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the UE 102 may include a plurality of UEs as per the requirement. For ease of reference, each of the first UE 102a, the second UE 102b, and the third UE 102c, will hereinafter be collectively and individually referred to as the “User Equipment (UE) 102”.
[0030] In an embodiment, the UE 102 is one of, but not limited to, any electrical, electronic, electro-mechanical or an equipment and a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device. In an embodiment, the UE 102 is one of, but not limited to, an admin, a subscriber.
[0031] The environment 100 includes the server 104 accessible via the network 106. The server 104 may include, by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof. In an embodiment, the entity may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business enterprise side, a defense facility side, or any other facility that provides service.
[0032] The network 106 includes, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. The network 106 may include, but is not limited to, a Third Generation (3G), a Fourth Generation (4G), a Fifth Generation (5G), a Sixth Generation (6G), a New Radio (NR), a Narrow Band Internet of Things (NB-IoT), an Open Radio Access Network (O-RAN), and the like.
[0033] The network 106 may also include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network 106 may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, a VOIP or some combination thereof.
[0034] The environment 100 further includes the system 108 communicably coupled to the server 104 and the UE 102 via the network 106. The system 108 is configured for creating PDR. As per one or more embodiments, the system 108 is adapted to be embedded within the server 104 or embedded as an individual entity.
[0035] Operational and construction features of the system 108 will be explained in detail with respect to the following figures.
[0036] FIG. 2 is an exemplary block diagram of the system 108 for creating the PDR, according to one or more embodiments of the present invention.
[0037] As per the illustrated embodiment, the system 108 includes one or more processors 202, a memory 204, a user interface 206, and a database 208. For the purpose of description and explanation, the description will be explained with respect to one processor 202 and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the system 108 may include more than one processors 202 as per the requirement of the network 106. The one or more processors 202, hereinafter referred to as the processor 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, single board computers, and/or any devices that manipulate signals based on operational instructions.
[0038] As per the illustrated embodiment, the processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 204. 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 include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as disk memory, EPROMs, FLASH memory, unalterable memory, and the like.
[0039] In an embodiment, the user interface 206 includes a variety of interfaces, for example, interfaces for a graphical user interface, a web user interface, a Command Line Interface (CLI), and the like. The user interface 206 facilitates communication of the system 108. In one embodiment, the user interface 206 provides a communication pathway for one or more components of the system 108. Examples of such components include, but are not limited to, the UE 102 and the database 208.
[0040] The database 208 is one of, but not limited to, a centralized database, a cloud-based database, a commercial database, an open-source database, a distributed database, an end-user database, a graphical database, a No-Structured Query Language (NoSQL) database, an object-oriented database, a personal database, an in-memory database, a document-based database, a time series database, a wide column database, a key value database, a search database, a cache databases, and so forth. The foregoing examples of database 208 types are non-limiting and may not be mutually exclusive e.g., a database can be both commercial and cloud-based, or both relational and open-source, etc.
[0041] In order for the system 108 to create the PDR, the processor 202 includes one or more modules. In one embodiment, the one or more modules includes, but not limited to, a transceiver 210, a data stitching module 212, a storage module 214 and a display unit 216 communicably coupled to each other for creating PDR.
[0042] In one embodiment, the one or more modules includes, but not limited to, the transceiver 210, the data stitching module 212, the storage module 214 and the display unit 216 can be used in combination or interchangeably for creating PDR.
[0043] The transceiver 210, the data stitching module 212, the storage module 214 and the display unit 216 in an embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 202. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor 202 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 204 may store instructions that, when executed by the processing resource, implement the processor. In such examples, the system 108 may comprise the memory 204 storing the instructions and the processing resource to execute the instructions, or the memory 204 may be separate but accessible to the system 108 and the processing resource. In other examples, the processor 202 may be implemented by electronic circuitry.
[0044] In an embodiment, the transceiver 210 is configured to receive a plurality of Streaming Data Record (SDRs) from a plurality of Network Functions (NFs).The SDR is a probing agent which collects probing data (Streaming Data Record- SDR) from 4th generation/ 5th generation (4G/5G) network nodes. The SDR can be a transaction or procedure in 5G core network or a call flow in 4G network. The SDR can also be a Call Detail Records (CDR) written in network nodes or a debugging record (can be logs as well). Further, the SDR includes but not limited to, NF, NF instance identifier (ID), NF type, timestamp, session ID, trace ID, trace type, cause codes (error codes), message name, interface, subscriber data (International Mobile Subscriber Identity (IMSI), International Mobile Equipment Identity (IMEI). In an embodiment, the above mentioned one or more parameters of the SDR is used for stitching SDRs. The NFs refer to the various modular and virtualized components that perform specific tasks within the network 106. The plurality of NFs includes at least one of, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a Policy Control Function (PCF), Unified Data Management (UDM), User Data Repository (UDR), Authentication Server Function (AUSF), Network Exposure Function (NEF), Network Slice Selection Function (NSSF), Application Function (AF), and Radio Access Network (RAN).
[0045] Upon receiving the plurality of SDRs, the data stitching module 212 is configured to stitch the plurality of SDRs in order to create a single end-to-end (E2E) Procedure Data Record (PDR). The stitching of the plurality of SDRs refers to integrating and managing various types of subscriber data spread across different NFs to provide a cohesive and seamless service experience. The E2E PDR is a unified record that encapsulates all aspects of a subscriber’s interaction with the network 106 from registration and authentication to session management and service usage. In an embodiment, the plurality of SDRs is correlated by stitching the plurality of SDRs. Further, each of the plurality of SDRs are stitched in order to create a single PDR using a unique identifier related to the subscriber. The unique identifier includes at least one of, a Subscription Permanent Identifier (SUPI), a Subscription Concealed Identifier (SUCI), and a Permanent Equipment Identifier (PEI).
[0046] In an embodiment, the transceiver 210 transmits the created PDR to an automatic Root Cause Analysis (RCA). The RCA is a process used to identify the underlying reasons for network issues or faults. Further, an Artificial Intelligence/Machine Learning (AI/ML) engine of the system facilitates a user to identify the errors with at least one of, the one or more NFs of the plurality of NFs. In an embodiment, the stitched PDR will lead to the automatic RCA using the AI/ML engine and helps the user to identify the problem easily and quickly. The AI/ML engine utilizes advanced algorithms to analyze the PDR and identify patterns, anomalies, and potential errors in the NFs. The AI/ML engine processes the PDR using at least one of techniques such an anomaly detection, a pattern recognition, a correlation analysis. The anomaly detection identifies deviations from normal network 106 behavior by comparing current data against historical patterns. The pattern recognition recognizes patterns that are indicative of specific types of networks issues. The correlation analysis correlates the data points across different NFs to identify common factors. In particular, the correlation analysis helps in pinpointing whether an issue in one NF is affecting another.
[0047] In an embodiment, the "Clear Code" fields capture the internal/external clear codes that the NF will log against the network procedure. The clear code is a specific code used within network functions to log information about the status of the network procedure, particularly errors or completion status. These clear codes will be captured as part of the PDRs (Procedure Data Records) generated by the correlation of SDRs of multiple NFs. The probing agent 402 will then consume these records along with the clear codes.
[0048] To detect the root cause analysis (RCA), the AI/ML engine uses a decision tree model to train the PDR data based on the digits of the clear codes (PDRs contains clear codes), as each digit of a clear code signifies particular information, for example, first set of digits the clear code is used to identify the result, whether it is a success or an error (internal/external), second set of digits depict the network procedure, third set of digits depict the type of interface, e.g., ingress/egress, respective of response codes, fourth set of set digits depict error codes.
Based on the above mentioned error codes, the probing agent 402 determines the automatic root cause analysis (RCA). Additionally, the probing agent 402 finds the RCA for network functions based on errors (external), interfaces(egress), and procedures(network).
[0049] In an embodiment, the created PDR represents the error originating from the one or more NFs when the at least one of the plurality of SDRs received from the respective NF includes an error clear code. The error clear code is a unique identifier included in the plurality of SDRs that represents a specific error or issue detected by the NF. Further, the created PDR pertains to aggregated data record for a procedure. The aggregated data includes details of the error and error generating NF.
[0050] Upon creating the PDR, the storage module 214 is configured to store a created PDR in the database 208. In an embodiment, subsequent to creating the PDR, the display unit 216 is configured to display the created PDR. The display of the created PDR depicts information related to at least one of, the one or more NFs, one or more procedures, one or more interfaces, or modules causing the error which affects a subscriber session. The subscriber session is a process that includes the initial attachment, session establishment, ongoing data transfer, mobility management, policy enforcement, session modification and detachment.
[0051] Therefore, the system 108 provides the user an exact information of the error and also the root cause of the error by stitching all SDRs into a single PDR.
[0052] FIG. 3 describes a preferred embodiment of the system 108 of FIG. 2, according to various embodiments of the present invention. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first UE 112a and the system 108 for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
[0053] As mentioned earlier in FIG. 1, each of the first UE 112a, the second UE 112b, and the third UE 112c may include an external storage device, a bus, a main memory, a read-only memory, a mass storage device, communication port(s), and a processor. The exemplary embodiment as illustrated in FIG. 3 will be explained with respect to the first UE 112a without deviating from the scope of the present disclosure and the limiting the scope of the present disclosure. The first UE 112a includes one or more primary processors 302 communicably coupled to the one or more processors 202 of the system 108.
[0054] The one or more primary processors 302 are coupled with a memory 304 storing instructions which are executed by the one or more primary processors 302. Execution of the stored instructions by the one or more primary processors 302 enables the first UE 112a to display, to a user, the created PDR which depicts information related to the error which affects the subscriber session.
[0055] As mentioned earlier in FIG. 2, the one or more processors 202 of the system 108 is configured for creating PDR. As per the illustrated embodiment, the system 108 includes the one or more processors 202, the memory 204, the user interface 206, and the database 208. The operations and functions of the one or more processors 202, the memory 204, the user interface 206, and the database 208 are already explained in FIG. 2. For the sake of brevity, a similar description related to the working and operation of the system 108 as illustrated in FIG. 2 has been omitted to avoid repetition.
[0056] Further, the processor 202 includes the transceiver 210, the data stitching module 212, the storage module 214 and the display unit 216. The operations and functions of the transceiver 210, the data stitching module 212, the storage module 214 and the display unit 216 are already explained in FIG. 2. Hence, for the sake of brevity, a similar description related to the working and operation of the system 108 as illustrated in FIG. 2 has been omitted to avoid repetition. The limited description provided for the system 108 in FIG. 3, should be read with the description as provided for the system 108 in the FIG. 2 above, and should not be construed as limiting the scope of the present disclosure.
[0057] FIG. 4 is a signal flow diagram for creating PDR, according to one or more embodiments of the present invention. For the purpose of description, the signal flow diagram is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0058] At step 402, the plurality of SDRs is received from the plurality of NFs. The plurality of NFs includes at least one of, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a Policy Control Function (PCF), Unified Data Management (UDM), User Data Repository (UDR), Authentication Server Function (AUSF), Network Exposure Function (NEF), Network Slice Selection Function (NSSF), Application Function (AF), and Radio Access Network (RAN).
[0059] At step 404, upon receiving the plurality of SDRs, a probing agent 402 stiches the plurality of SDRs in order to create the single E2E PDR. Further, each of the plurality of SDRs are stitched in order to create the single PDR using the unique identifier related to the subscriber. In an embodiment, the probing agent 402 is the system 108.The unique identifier includes at least one of, the Subscription Permanent Identifier (SUPI), the Subscription Concealed Identifier (SUCI), and the Permanent Equipment Identifier (PEI). In an embodiment, the plurality of SDRs is correlated by stitching the plurality of SDRs.
[0060] At step 406, the created PDR is transmitted to the RCA at the probing agent 402. The AI/ML engine is used to facilitate the user to identify the errors with at least one of, the one or more NFs of the plurality of NFs. Further, the created PDR represents the error originating from the one or more NFs when the at least one of the plurality of SDRs received from the respective NF includes the error clear code. The created PDR pertains to aggregated data record for the procedure. The aggregated data includes details of the error and error generating NF.
[0061] At step 408, subsequent to creating the PDR, the created PDR is stored in the database 208.
[0062] At step 410, subsequent to creating the PDR, the created PDR is displayed on the display unit 216. The display of the created PDR depicts information related to at least one of, the one or more NFs, one or more procedures, one or more interfaces, or modules causing the error which affects the subscriber session.
[0063] FIG. 5 is a flow diagram of a method 500 for creating PDR, according to one or more embodiments of the present invention. For the purpose of description, the method 500 is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0064] At step 502, the method 500 includes the step of receiving the plurality of SDRs from the plurality of NFs by the transceiver 210. The plurality of NFs includes at least one of, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a Policy Control Function (PCF), Unified Data Management (UDM), User Data Repository (UDR), Authentication Server Function (AUSF), Network Exposure Function (NEF), Network Slice Selection Function (NSSF), Application Function (AF), and Radio Access Network (RAN).
[0065] At step 504, the method 500 includes the step of stitching the plurality of SDRs in order to create the single E2E PDR by the data stitching module 212. Further, each of the plurality of SDRs are stitched in order to create the single PDR using the unique identifier related to the subscriber. The unique identifier includes at least one of, the Subscription Permanent Identifier (SUPI), the Subscription Concealed Identifier (SUCI), and the Permanent Equipment Identifier (PEI). In an embodiment, the plurality of SDRs is correlated by stitching the plurality of SDRs.
[0066] In an embodiment, the transceiver 210 transmits the created PDR to the RCA. The AI/ML engine is used to facilitate the user to identify the errors with at least one of, the one or more NFs of the plurality of NFs. Further, the created PDR represents the error originating from the one or more NFs when the at least one of the plurality of SDRs received from the respective NF includes the error clear code. The created PDR pertains to aggregated data record for the procedure. The aggregated data includes details of the error and error generating NF.
[0067] At step 506, the method 500 includes the step of storing the created PDR in the database 208 by the storage module 214. Further, subsequent to creating the PDR, the created PDR is displayed on the display unit 216. The display of the created PDR depicts information related to at least one of, the one or more NFs, one or more procedures, one or more interfaces, or modules causing the error which affects the subscriber session
[0068] The present invention further discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by the processor 202. The processor 202 is configured to receive the plurality of SDRs from the plurality of NFs. The processor 202 is further configured to stitch the plurality of SDRs in order to create the single E2E PDR. Further, each of the plurality of SDRs are stitched in order to create the single PDR using the unique identifier related to the subscriber. The processor 202 is further configured to store the created PDR in the database subsequent to creation of the PDR.
[0069] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-5) are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0070] The present disclosure incorporates technical advancement providing the accurate information of the error and also the root cause of the error to the user. More specifically by stitching all SDRs into a single record (PDR), the end user can exact information of the error and also the root cause of the error.
[0071] The present invention offers multiple advantages over the prior art and the above listed are a few examples to emphasize on some of the advantageous features. The listed advantages are to be read in a non-limiting manner.

REFERENCE NUMERALS

[0072] Environment- 100
[0073] User Equipment (UE)- 102
[0074] Server- 104
[0075] Network- 106
[0076] System -108
[0077] Processor- 202
[0078] Memory- 204
[0079] User Interface- 206
[0080] Database- 208
[0081] Transceiver- 210
[0082] Data Stitching Module - 212
[0083] Storage Module- 214
[0084] Display Unit- 216
[0085] One or more primary processor- 302
[0086] Memory – 304
,CLAIMS:CLAIMS:
We Claim:
1. A method (500) for creating Procedure Data Records (PDR), the method (500) comprises the steps of:
receiving, by one or more processors (202), a plurality of Streaming Data Records (SDRs) from a plurality of Network Functions (NFs);
stitching, by the one or more processors (202), the plurality of SDRs in order to create a single end-to-end (E2E) Procedure Data Record (PDR), wherein each of the plurality of SDRs are stitched in order to create a single PDR using a unique identifier related to a subscriber; and
storing, by the one or more processors (202), a created PDR in a database (208) subsequent to creation of the PDR.

2. The method (500) as claimed in claim 1, wherein the plurality of Network Functions (NFs) includes at least one of, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), and a Policy Control Function (PCF).

3. The method (500) as claimed in claim 1, wherein the one or more processors (202) subsequent to creating the PDR, displays the created PDR on a display unit (216), wherein the display of the created PDR depicts information related to at least one of, the one or more NFs, one or more procedures, one or more interfaces, or modules causing the error which affects a subscriber session.

4. The method (500) as claimed in claim 1, wherein the unique identifier includes at least one of, a Subscription Permanent Identifier (SUPI), a Subscription Concealed Identifier (SUCI), and a Permanent Equipment Identifier (PEI).

5. The method (500) as claimed in claim 1, wherein the created PDR is transmitted by the one or more processors to an automatic Root Cause Analysis (RCA) unit, wherein the one or more processors (202) using an Artificial Intelligence/Machine Learning (AI/ML) engine facilitates a user to identify the errors with at least one of, the one or more NFs of the plurality of NFs.

6. The method (500) as claimed in claim 1, wherein the created PDR represents the error originating from the one or more NFs when the at least one of the plurality of SDRs received from the respective NF includes an error clear code.

7. The method (500) as claimed in claim 1, wherein the plurality of SDRs are correlated by stitching the plurality of SDRs.

8. The method (500) as claimed in claim 1, wherein the created PDR pertains to aggregated data record for a procedure, wherein the aggregated data includes details of the error and error generating NF.

9. A system (108) for creating Procedure Data Records (PDR), the system (108) comprising:
a transceiver (210) configured to, receive, a plurality of Streaming Data Records (SDRs) from a plurality of Network Functions (NFs);
a data stitching module (212) configured to, stitch, the plurality of SDRs in order to create a single end-to-end (E2E) Procedure Data Record (PDR), wherein each of the plurality of SDRs are stitched in order to create a single PDR using a unique identifier related to a subscriber; and
a storage module (214) configured to, store, a created PDR in a database (208) subsequent to creation of the PDR.

10. The system (108) as claimed in claim 9, wherein the plurality of Network Functions (NFs) includes at least one of, but not limited to, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), and a Policy Control Function (PCF).

11. The system (108) as claimed in claim 9, a display unit subsequent to creating the PDR, displays the created PDR, wherein the display of the created PDR depicts information related to at least one of, the one or more NFs, one or more procedures, one or more interfaces, or modules causing the error which affects a subscriber session.

12. The system (108) as claimed in claim 9, wherein the unique identifier includes at least one of, a Subscription Permanent Identifier (SUPI), a Subscription Concealed Identifier (SUCI), and a Permanent Equipment Identifier (PEI).

13. The system (108) as claimed in claim 9, wherein the transceiver (210) transmits the created PDR to an automatic Root Cause Analysis (RCA) unit, wherein an Artificial Intelligence/Machine Learning (AI/ML) engine of the system facilitates a user to identify the errors with at least one of, the one or more NFs of the plurality of NFs.

14. The system (108) as claimed in claim 9, wherein the created PDR represents the error originating from the one or more NFs when the at least one of the plurality of SDRs received from the respective NF includes an error clear code.

15. The system (108) as claimed in claim 9, wherein the plurality of SDRs is correlated by stitching the plurality of SDRs.

16. The system (108) as claimed in claim 9, wherein the created PDR pertains to aggregated data record for a procedure, wherein the aggregated data includes details of the error and error generating NF.

17. A User Equipment (UE) (102), comprising:
one or more primary processors (302) communicatively coupled to one or more processors (202), the one or more primary processors (302) coupled with a memory (304), wherein said memory (304) stores instructions which when executed by the one or more primary processors (302) causes the UE (102) to:
display, to a user, the created PDR which depicts information related to the error which affects the subscriber session;
wherein the one or more processors (202) is configured to perform the steps as claimed in claim 1.