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

METHOD AND SYSTEM FOR OPTIMISING A NETWORK MANAGEMENT
PROCESS
TECHNICAL FIELD
[001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to methods and systems for optimising a network management process.
BACKGROUND
[002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. The fourth-generation (4G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth-generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[004] Further, traditional network monitoring and network structure probing methods have long faced challenges due to the limitations imposed by one or more physical taps, one or more aggregators, and one or more packet capturing tools. The one or more physical taps involve physically accessing and tapping into network cables, often require significant effort and
2

resources. The one or more physical taps may disrupt network connectivity and pose risks of damage or interference to the network infrastructure. Similarly, the one or more aggregators, are used to collect network traffic from multiple sources, however the one or more aggregators face limitations in terms of scalability and flexibility. The one or more aggregators may struggle to handle large volumes of network data, which ultimately leads to potential data loss or delays in capturing critical information. Additionally, the one or more aggregators may not provide granular visibility into specific network segments or devices, which limits the effectiveness in complex network environments. Further, the one or more packet capturing tools are commonly used for network monitoring, however also present challenges. The one or more packets typically require deep packet inspection and analysis, which may be time-consuming and resource intensive. Furthermore, an encrypted traffic poses a significant hurdle for the conventional packet capturing tools, as the conventional packet capturing tools are unable to decipher encrypted content, which limits the ability to provide comprehensive insights.
[005] The aforementioned challenges have led to the development of multiple alternative approaches and technologies in network monitoring and structure probing. For instance, software-defined networking (SDN) and network functions virtualization (NFV) have emerged as solutions that offer greater flexibility, scalability, and visibility, which enable centralized management and control of network resources, thereby allowing for efficient monitoring and probing without the need for physical access, which further causes multiple challenges to provide a smooth interface between the Network Function (NF) and the error detection and elimination system.
[006] Thus, there exists an imperative need in the art to provide a system and a method for optimising a network management process.
SUMMARY
[007] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

[008] An aspect of the present disclosure may relate to a method for optimising a network management process. The method comprises receiving, at an aggregation unit, a streaming data record (SDR) associated with a network procedure of a network function. The method comprises validating, by a validation unit, the received SDR based on a predefined target format associated with the SDR, to generate one of a successful validation result and an unsuccessful validation result. The method comprises ingesting, by the aggregation unit, the SDR associated with the network procedure based on the generation of the successful validation result. The method comprises enriching, by a data analytics engine, the received SDR based on the ingestion of the received SDR. The method comprises -generating, by the data analytics engine, an analysis report associated with the network procedure based on at least one of the received SDR and the enriched SDR.
[009] In an exemplary aspect of the present disclosure, the enriching, the received SDR further comprises adding, by a processing unit, one or more new values to the received SDR to generate an enriched SDR and storing, at a storage unit, the enriched SDR.
[010] In an exemplary aspect of the present disclosure, the received SDR is validated based on one or more predefined SDR validation policies.
[011] In an exemplary aspect of the present disclosure, the successful validation result is generated in an event the received SDR successfully matches with the predefined target format associated with the SDR, and the unsuccessful validation result is generated in an event the received SDR does not match with the predefined target format associated with the SDR.
[012] In an exemplary aspect of the present disclosure, the received SDR associated with the network procedure is generated based on a predefined SDR format associated with said network procedure wherein the predefined SDR format further comprises a SDR header, a SDR payload and a delimiter.
[013] In an exemplary aspect of the present disclosure, the SDR header comprises one or more values associated with at least one of a network function name, a network procedure name, a version associated the network procedure, and a relation identifier in a pre-stored format associated with the network function.

[014] In an exemplary aspect of the present disclosure, the SDR payload comprises plurality of fields, wherein each field is associated with one of: a SDR type field identifier in a predetermined format, an incoming Request associated with the network function, an Outgoing Response associated with the network function, an Outgoing Request associated with the network function, an Incoming Response associated with the network function, an Originating Call Flow associated with the network function, and a Terminating Call Flow associated with the network function.
[015] In an exemplary aspect of the present disclosure, the predefined SDR format is a delimiter separated record format.
[016] In an exemplary aspect of the present disclosure, the analysis report is generated in at least one of a predefined format and a dynamically generated format.
[017] In an exemplary aspect of the present disclosure, the method further comprises displaying, via a user interface, the analysis report associated with the network procedure.
[018] Another aspect of the present disclosure may relate to a system for optimising a network management process. The system comprises an aggregation unit configured to receive a streaming data record (SDR) associated with a network procedure. The system further comprises a validation unit connected to at least the aggregation unit, the validation unit configured to validate the received SDR based on a predefined target format associated with the SDR, to generate one of a successful validation result and an unsuccessful validation result, wherein the aggregation unit is further configured to ingest the SDR associated with the network procedure based on the generation of the successful validation result. The system further comprises a data analytics engine connected to at least the validation unit, the data analytics engine configured to enrich the received SDR based on the ingestion of the received SDR. The data analytics engine further configured to generate an analysis report associated with the network procedure based on at least one of the received SDR and the enriched SDR.
[019] Yet another object of the disclosure relates to a user equipment (UE) for optimising a network management process, the UE comprising: a memory; and a processor coupled to the memory, wherein the processor is configured to: transmit, to a system, a streaming data record (SDR) associated with a network procedure of a network function, and receive, from the

system, an analysis report associated with the network procedure based on at least one of the received SDR and the enriched SDR, wherein the analysis report is received based on: validating, by the system, the received SDR based on a predefined target format associated with the SDR, to generate one of a successful validation result and an unsuccessful validation result, ingesting, by the system, the SDR associated with the network procedure based on the generation of the successful validation result, and enriching, by the system, the received SDR based on the ingestion of the received SDR.
[020] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for optimising a network management process, the instructions include executable code which, when executed by a one or more units of a system, causes: an aggregation unit to receive, a streaming data record (SDR) associated with a network procedure of a network function, a validation unit to validate, the received SDR based on a predefined target format associated with the SDR, to generate one of a successful validation result and an unsuccessful validation result, the aggregation unit to ingest, the SDR associated with the network procedure based on the generation of the successful validation result, data analytics engine to enrich a the received SDR based on the ingestion of the received SDR, and data analytics engine to generate, an analysis report associated with the network procedure based on at least one of the received SDR and the enriched SDR.
OBJECTS OF THE INVENTION
[021] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[022] It is an object of the present disclosure to provide a method for optimising a network management process.
[023] It is another object of the present disclosure to provide a system for optimising a network management process.
[024] It is another object of the present disclosure to provide a solution to deliver a defined and finalized structure of streaming data record (SDR) that is easy to implement in the network.

[025] It is another object of the present disclosure to provide a lightweight structure of SDR which include only one or more values and reduced a bandwidth requirement.
[026] It is yet another object of the present disclosure to provide a flexible structure of SDR which may be adopted as per one or more network requirements.
DESCRIPTION OF THE DRAWINGS
[027] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
[028] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core(5GC) network architecture.
[029] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
[030] FIG. 3 illustrates an exemplary block diagram of a system for optimising a network management process, in accordance with exemplary implementations of the present disclosure.
[031] FIG. 4 illustrates a method flow diagram for optimising a network management process in accordance with exemplary implementations of the present disclosure.
[032] FIG. 5 illustrates an exemplary sequence flow diagram for requesting a streaming data record (SDR) in accordance with exemplary implementations of the present disclosure.

[033] FIG. 6 illustrates exemplary sequence flow diagram of a response of a streaming data record (SDR) in accordance with exemplary implementations of the present disclosure.
[034] FIG. 7 illustrates exemplary a sequence flow diagram of a call flow of a streaming data record (SDR) in accordance with exemplary implementations of the present disclosure.
[035] FIG. 8 illustrates exemplary flow diagram of optimising a network management process in accordance with exemplary implementations of the present disclosure.
[036] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
[037] 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 may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.
[038] 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.
[039] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example,

circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
[040] Also, it is noted that individual embodiments may be described as a process which is
5 depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block
diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.
10
[041] 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
15 advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary
structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or
20 other elements.
[042] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a
25 conventional processor, a digital signal processor, a plurality of microprocessors, one or more
microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the
30 working of the system according to the present disclosure. More specifically, the processor or
processing unit is a hardware processor.
[043] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless
9

communication device”, “a mobile communication device”, “a communication device” may
be any electrical, electronic and/or computing device or equipment, capable of implementing
the features of the present disclosure. The user equipment/device may include, but is not limited
to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital
5 assistant, tablet computer, wearable device or any other computing device which is capable of
implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
10
[044] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical
15 storage media, flash memory devices or other types of machine-accessible storage media. The
storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
[045] As used herein “interface” or “user interface refers to a shared boundary across which
20 two or more separate components of a system exchange information or data. The interface may
also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
25 [046] All modules, units, components used herein, unless explicitly excluded herein, may be
software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field
30 Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[047] As used herein the transceiver unit include at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or
10

a combination thereof between units/components within the system and/or connected with the system.
[048] As discussed in the background section, the conventional network monitoring and
5 network structure probing methods have several issues due to multiple limitation imposed by
one or more physical taps, one or more aggregators, and one or more packet capturing tools such as additional requirement of effort and resources, risks of damage to a network infrastructure, scalability and flexibility issues, potential data loss or delays in capturing critical information, lack of granular visibility. Hence, the currently known solutions have several
10 shortcomings. The present disclosure aims to overcome the above-mentioned and other
existing problems in this field of technology by providing method and system for optimising a network management process. The network management process is optimized via validating a received streaming data record (SDR) based on a predefined target format that is associated with the SDR for generating one of a successful validation result and an unsuccessful validation
15 result. Further, the SDR associated with a network procedure is ingested based on the
generation of the successful validation result. Thereafter, the received SDR is enriched and an analysis report is generated based on at least one of the received SDR and the enriched SDR.
[049] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core
20 (5GC) network architecture, in accordance with exemplary implementation of the present
disclosure. As shown in FIG. 1, the 5GC network architecture [100] includes a user equipment
(UE) [102], a radio access network (RAN) [104], an access and mobility management function
(AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy
(SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific
25 Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection
Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository
Function (NRF) [120], a Policy Control Function (PCF) [122], a Unified Data Management
(UDM) [124], an application function (AF) [126], a User Plane Function (UPF) [128], a data
network (DN) [130], wherein all the components are assumed to be connected to each other in
30 a manner as obvious to the person skilled in the art for implementing features of the present
disclosure.
[050] Radio Access Network (RAN) [104] is the part of a mobile telecommunications system that connects user equipment (UE) [102] to the core network (CN) and provides access to
11

different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.
[051] Access and Mobility Management Function (AMF) [106] is a 5G core network function
5 responsible for managing access and mobility aspects, such as UE registration, connection, and
reachability. It also handles mobility management procedures like handovers and paging.
[052] Session Management Function (SMF) [108] is a 5G core network function responsible
for managing session-related aspects, such as establishing, modifying, and releasing sessions.
10 It coordinates with the User Plane Function (UPF) [128] for data forwarding and handles IP
address allocation and QoS enforcement.
[053] Service Communication Proxy (SCP) [110] is a network function in the 5G core
network that facilitates communication between other network functions by providing a secure
15 and efficient messaging service. It acts as a mediator for service-based interfaces.
[054] Authentication Server Function (AUSF) [112] is a network function in the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens. 20
[055] Network Slice Specific Authentication and Authorization Function (NSSAAF) [114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized.
25 [056] Network Slice Selection Function (NSSF) [116] is a network function responsible for
selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.
[057] Network Exposure Function (NEF) [118] is a network function that exposes capabilities
30 and services of the 5G network to external applications, enabling integration with third-party
services and applications.
12

[058] Network Repository Function (NRF) [120] is a network function that acts as a central repository for information about available network functions and services. It facilitates the discovery and dynamic registration of network functions.
5 [059] Policy Control Function (PCF) [122] is a network function responsible for policy
control decisions, such as QoS, charging, and access control, based on subscriber information and network policies.
[060] Unified Data Management (UDM) [124] is a network function that centralizes the
10 management of subscriber data, including authentication, authorization, and subscription
information.
[061] Application Function (AF) [126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services. 15
[062] User Plane Function (UPF) [128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.
[063] Data Network (DN) [130] refers to a network that provides data services to user
20 equipment (UE) in a telecommunications system. The data services may include but are not
limited to Internet services, private data network related services.
[064] FIG. 2 illustrates an exemplary block diagram of a computing device [1000] (also referred herein as computing system [1000]) upon which the features of the present disclosure
25 may be implemented in accordance with exemplary implementation of the present disclosure.
In an implementation, the computing device [1000] may also implement a method for optimising a network management process utilising the system. In another implementation, the computing device [1000] itself implements the method for optimising the network management process using one or more units configured within the computing device [1000], wherein said
30 one or more units are capable of implementing the features as disclosed in the present
disclosure.
[065] The computing device [1000] may include a bus [1002] or other communication mechanism for communicating information, and a hardware processor [1004] coupled with the
13

bus [1002] for processing information. The hardware processor [1004] may be, for example, a
general purpose microprocessor. The computing device [1000] may also include a main
memory [1006], such as a random access memory (RAM), or other dynamic storage device,
coupled to the bus [1002] for storing information and instructions to be executed by the
5 processor [1004]. The main memory [1006] also may be used for storing temporary variables
or other intermediate information during execution of the instructions to be executed by the
processor [1004]. Such instructions, when stored in non-transitory storage media accessible to
the processor [1004], render the computing device [1000] into a special-purpose machine that
is customized to perform the operations specified in the instructions. The computing device
10 [1000] further includes a read only memory (ROM) [1008] or other static storage device
coupled to the bus [1002] for storing static information and instructions for the processor [1004].
[066] A storage device [1010], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [1002] for storing information and instructions. The computing device [1000] may be coupled via the bus [1002] to a display [1012], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [1014], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [1002] for communicating information and command selections to the processor [1004]. Another type of user input device may be a cursor controller [1016], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [1004], and for controlling cursor movement on the display [1012]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
[067] The computing device [1000] may implement the techniques described herein using
customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic
which in combination with the computing device [1000] causes or programs the computing
30 device [1000] to be a special-purpose machine. According to one implementation, the
techniques herein are performed by the computing device [1000] in response to the processor [1004] executing one or more sequences of one or more instructions contained in the main memory [1006]. Such instructions may be read into the main memory [1006] from another storage medium, such as the storage device [1010]. Execution of the sequences of instructions
14

contained in the main memory [1006] causes the processor [1004] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
5 [068] The computing device [1000] also may include a communication interface [1018]
coupled to the bus [1002]. The communication interface [1018] provides a two-way data communication coupling to a network link [1020] that is connected to a local network [1022]. The local network [1022] is further connected to a host [1024]. For example, the communication interface [1018] may be an integrated services digital network (ISDN) card,
10 cable modem, satellite modem, or a modem to provide a data communication connection to a
corresponding type of telephone line. As another example, the communication interface [1018] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [1018] sends and receives electrical, electromagnetic or optical
15 signals that carry digital data streams representing various types of information.
[069] The computing device [1000] can send messages and receive data, including program
code, through the network(s), the network link [1020] and the communication interface [1018].
In the Internet example, a server [1030] might transmit a requested code for an application
20 program through the Internet [1028], the ISP [1026], the Host [1024], the local network [1022]
and the communication interface [1018]. The received code may be executed by the processor [1004] as it is received, and/or stored in the storage device [1010], or other non-volatile storage for later execution.
25 [070] Referring to FIG. 3, an exemplary block diagram of a system [300] for optimising a
network management process, is shown, in accordance with the exemplary implementations of the present disclosure. The system [300] comprises at least one aggregation unit [302], at least one validation unit [304], at least one data analytics engine [306], and at least one storage unit [308]. Also, all of the components/ units of the system [300] are assumed to be connected to
30 each other unless otherwise indicated below. As shown in the figures all units shown within
the system should also be assumed to be connected to each other.
[071] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be implemented interchangeably.
15

While specific embodiments may disclose a particular functionality of these units for clarity, it
is recognized that various configurations and combinations thereof are within the scope of the
disclosure. The functionality of specific units as disclosed in the disclosure should not be
construed as limiting the scope of the present disclosure. Consequently, alternative
5 arrangements and substitutions of units, provided they achieve the intended functionality
described herein, are considered to be encompassed within the scope of the present disclosure.
[072] The system [300] is configured for optimising the network management process with the help of the interconnection between the components/units of the system [300].
10
[073] In order to optimize the network management process, the aggregation unit [302] is configured to receive a streaming data record (SDR) associated with a network procedure. The SDR refers a summary of a procedure or a call flow in a network such as 5G network. Also, the SDR may also refer to a data which is continuously flowing from a source system to a target
15 node or target system associated with the network. The SDR may be generated simultaneously,
at a high speed by plurality of data sources such as a set of servers, a set of sensors, a set of input devices, a set of processors associated with the network and/or a user device. Further, the network procedure may include one or more rules and/or one or more operations for managing a lifecycle of a network infrastructure. Further, the network procedure as used herein refers to
20 a set of steps or actions that are carried out to manage or facilitate communication between
devices or systems within the network. The network procedure can include tasks like establishing connections, transferring data, managing resources, and troubleshooting issues.
[074] The present disclosure encompasses that the received SDR associated with the network
25 procedure is generated based on a predefined SDR format associated with said network
procedure. The predefined SDR format further comprises a SDR header, a SDR payload and a delimiter.
[075] The present disclosure encompasses that the SDR header comprises one or more values
30 associated with at least one of a network function name, a network procedure name, a version
associated the network procedure, and a relation identifier in a pre-stored format associated with the network function [802].
16

[076] The SDR header is section at the beginning of the predefined SDR format which may indicate about a data type i.e., a network function (nf) name as depicted in table 1 below, a call flow name, a version data, a destination i.e., a relation identifier . The SDR payload is a section which is an actual intended message. 5
[077] The present disclosure encompasses that the SDR payload comprises plurality of fields,
wherein each field is associated with one of: a SDR type field identifier in a predetermined
format, an incoming Request associated with the network function [802], an Outgoing
Response associated with the network function [802], an Outgoing Request associated with the
10 network function [802], an Incoming Response associated with the network function [802], an
Originating Call Flow associated with the network function [802], and a Terminating Call Flow associated with the network function [802].
[078] The SDR type field identifier as used herein refers to a label or marker within one or
15 field of the SDR payload i.e., a SDR field position. The SDR type field identifier indicates a
type information that is contained in the SDR field position. Such as a SDR field position 1 may indicate the type of SDR, a SDR field position 2 may indicate a subclassification of the type of SDR and so on.
20 [079] Further, the subclassification of the type of SDR may be an integer value such as 1.
Further, said an integer value may indicates that the SDR is associated with at least one of an Incoming Request, an Outgoing Response, an Outgoing Request, an Incoming Response, an Originating Procedure or a Terminating Procedure. Ex- For procedure SDR, it can be, either NF is originating the procedure (Request initiator) or the NF is terminating the procedure
25 (Request Receiver).
[080] The present disclosure encompasses that the predefined SDR format is a delimiter
separated record format. The delimiter may be character or symbol which separates one piece
of data from another piece of data of the SDR i.e., an identifier that separates the SDR header
30 and the SDR payload. Further, the delimiter may be a specific character, sequence of bits, or
signal used to separate or delineate the SDR header and the SDR payload within the SDR. The delimiters as disclosed in the present disclosure is utilised to identify the boundaries between the SDR header and the SDR payload such as a specific delimiter may be associated with a particular SDR and SDR payload set.
17

[081] Thereafter, the aggregation unit [302] transmits the received SDR to the validation unit
[304]. The validation unit [304] is connected to at least the aggregation unit [302]. The
validation unit [304] receives the SDR transmitted by the aggregation unit [302]. Further, the
5 validation unit [304] configured to validate the received SDR based on a predefined target
format associated with the SDR, to generate one of a successful validation result and an unsuccessful validation result.
The present disclosure encompasses that the received SDR is validated based on one or more
10 predefined SDR validation policies. The one or more predefined SDR validation policies may
include one or more processes for verifying the received SDR with the pre-defined target format. Further, the one or more processes may include data type check, format check, ranges pattern check, dependencies check and constraint check, implementation of validation logic, monitoring of a validation result. The one or more predefined SDR validation policies may also
15 include a schematic validation policy, a data quality validation policy and a data security
validation policy. The schema validation policy includes checking of the SDR to a predefined structure or schema which helps to ensure that the SDR include correct fields, types and values. The data quality validation policy includes an assessment of the SDR i.e. whether the SDR meets a standard of accuracy, completeness, consistency, timeliness and uniqueness. The data
20 quality validation policy helps to identify and correct one or more error, one or more duplicates,
one or more outliers and one or more missing values. The data security validation policy includes checking of the SDR, whether the SDR is protected from an unauthorized access, modification. The data security validation policy helps to ensure that the SDR complies with one or more regulation policies. Further, the one or more predefined SDR validation policies
25 defined herein are not intended to limit the scope, applicability, or configuration of the
disclosure and the one or more predefined SDR policies may include other known policies. The one or more predefined SDR validation policies may be stored in the storage unit [308].
[082] The present disclosure encompasses that the predefined target format is a predefined
30 format which may be set by a network operator and stored in the storage unit [308].Further, the
predefined target format may refer to a standard structure which include one or more defined values, one or more defined data type and alike. Further, in an implementation each SDR field of the SDR may be associated with predefined target format.
18

[083] The present disclosure encompasses that the successful validation result is generated in an event the received SDR successfully matches with the predefined target format associated with the SDR. Further the unsuccessful validation result is generated in an event the received SDR does not match with the predefined target format associated with the SDR. 5
[084] The present disclosure encompasses that the successful validation result indicates that
the received SDR matches or align with the predefined target format and the unsuccessful
validation result indicates that the received SDR does not matches or align with the predefined
target format. Further, in an implementation the successful validation result indicates that each
10 SDR field of the received SDR matches or align with the predefined target format associated
with said that each SDR field. Further, in another implementation the unsuccessful validation result indicates that at least one SDR field of the received SDR does not matches or align with the predefined target format associated with said that each SDR field.
15 [085] The present disclosure encompasses that the received SDR is validated by matching a
content or one or more attributes of the received SDR with a content or one or more attributes present in the predefined target format. For example, the SDR includes a data format such as “XXYYZZ00” and the predefined target format is “00YYXXZZ”, the data format of received SDR is matched the predefined target format and in case the received SDR does not align with
20 the predefined target format, then the result is unsuccessful validation result, or else if the data
format of the received SDR aligns with the predefined target format, then the result is successful validation result.
[086] Thereafter, the aggregation unit [302] is further configured to ingest the SDR associated
25 with the network procedure based on the generation of the successful validation result. The
present disclosure encompasses that the SDR is ingested based on one or more ingestion
protocols that may be known to person skilled in the art. Further the ingestion is a process of
importing one or more large files, assorted data files from plurality of sources into a single
storage medium or a data warehouse or data mart or database. The present disclosure as
30 disclosed herein, the SDR associated with the network procedure may be transmitted to the
data analytics engine [306] i.e., ingested at the data analytics engine [306] based on the generation of the successful validation result associated with the said SDR.
19

[087] Further, the data analytics engine [306] connected to at least the validation unit [304],
the data analytics engine [306] configured to enrich the received SDR based on the ingestion
of the received SDR, and generate an analysis report associated with the network procedure
based on at least one of the received SDR and the enriched SDR. The received SDR is the SDR
5 which was received by the aggregation unit [302] and the enriched SDR is the SDR which
received from the data analytics engine [306].
[088] The present disclosure encompasses that the received SDR is enriched via utilizing one
or more data enrichment protocols which refers to a process of enhancing the SDR by
10 supplementing a missing information. Further, the missing information is extracted or
identified from a data stored in the storage unit [308]. Also, the extraction or identification may be done via one or more data extraction protocols.
[089] The present disclosure encompasses that the data analytics engine [306] is configured
15 to enrich the received SDR by adding one or more new values to the received SDR to generate
an enriched SDR and by storing the enriched SDR. For instance, the received SDR may be
enriched in an event at least one missing SDR field is detected, wherein to enrich the said
received SDR a historic or a prestored SDR information associated with the network procedure
may be fetched from storage unit [308] in order to replace said one missing SDR field with a
20 historic SDR or a prestored SDR field based on the historic SDR information or the prestored
SDR information.
[090] The present disclosure encompasses the data analytics engine [306] is configured to
generate the analysis report in at least one of a predefined format and a dynamically generated
25 format.
[091] The present disclosure encompasses that the data analytic engine generates the analysis
report via using one or more report generation protocols that automatically generated the
analysis report according to the predefined format or the dynamically generated format. The
30 predefined format may have information associated with the analysis report in a structured
format having a template where certain sections, styles, or layouts are predetermined. Whereas the dynamically generated format associated with the analysis report refers to a format that is created or adjusted automatically based on certain conditions or inputs. Instead of being fixed
20

like a template, the dynamically generated format adapts or changes depending on the SDR data or the network procedure.
[092] The present disclosure encompasses that the system [300] further comprising a user
5 interface configured to display the analysis report associated with the network procedure.
[093] Further, an exemplary format of SDR header is depicted in below Table 1. Also, an exemplary format of the remaining SDR is depicted in Table 2.
Table 1: Exemplary Format of SDR Header

Description Mandatory /Optional
Network Function Identifier M
Call Flow Identifier M
Category Identifier M
Relation Identifier M
10
Table 2: Exemplary Format of SDR

Field Position SDR Field Description Required Data Type
1 Type of SDR

[094]

Integer

2 Sub classification of SDR based on Field #1

Integer

21


3 Timestamp of Request Date
Field Position SDR Field Description
4 Timestamp of Response Date
5 Correlation ID String
6 ClearCode String
7 NETWORK PROTOCOL Verb
8 URL String
9 context String
10 Reserved for Query String String
11 Reserved for Query String String
12 Reserved for Query String String
13 Reserved for Query String String
14 Reserved for Query String String
15 Reserved for NETWORK PROTOCOL header String
16 Reserved for NETWORK PROTOCOL header String
17 Reserved for NETWORK PROTOCOL header String
22

18 Reserved for NETWORK PROTOCOL header String
19 Reserved for NETWORK PROTOCOL header String
20 Reserved for NETWORK PROTOCOL header String
21 Reserved for NETWORK PROTOCOL header String
22 Reserved for NETWORK PROTOCOL header String
23 Reserved for NETWORK PROTOCOL header String
24 Reserved for NETWORK PROTOCOL header String
Field Position SDR Field Description
25 Reserved for NETWORK PROTOCOL Body String
26 Reserved for NETWORK PROTOCOL Body String
27 Reserved for NETWORK PROTOCOL Body String
28 Reserved for NETWORK PROTOCOL Body String
29 Reserved for NETWORK PROTOCOL Body String
30 Reserved for NETWORK PROTOCOL Body String
31 Reserved for NETWORK PROTOCOL Body String
32 Reserved for NETWORK PROTOCOL Body String
33 Reserved for NETWORK PROTOCOL Body String
34 Reserved for NETWORK PROTOCOL Body String
35 Reserved for NETWORK PROTOCOL Body String
36 Reserved for NETWORK PROTOCOL Body String
37 Reserved for NETWORK PROTOCOL Body String
38 Reserved for NETWORK PROTOCOL Body String
39 Reserved for NETWORK PROTOCOL Response Code Integer
40 Reserved for NETWORK PROTOCOL Response Description String
41 Reserved for NETWORK PROTOCOL Response Body String
42 Reserved for NETWORK PROTOCOL Response Body String
23

43 Reserved for NETWORK PROTOCOL Response Body String
44 Reserved for NETWORK PROTOCOL Response Body String
45 Reserved for NETWORK PROTOCOL Response Body String
46 Reserved for NETWORK PROTOCOL Response Body String
47 Reserved for NETWORK PROTOCOL Response Body String
48 Reserved for NETWORK PROTOCOL Response Body String
49 Reserved for NETWORK PROTOCOL Response Body String
50 Reserved for NETWORK PROTOCOL Response Body String
[095] Additionally, the Table 1 and Table 2 explains the SDR format which a Network
Function (NF) [802] adheres to push the data from the NR to a network probing module [804]
for maintaining sanity and allow a cross correlation across different NFs for stitching one or
5 more call flows across NFs and allowing multiple analytics as depicted in FIG. 8. The network
probing module [804] is remote solution for enabling one or more network operators for optimizing and troubleshooting the network.
[096] In addition to this, one or more enumerated values (depicted in Table 2) against the
10 Field description specifies the one or more values which may appear against that field in SDR.
Further, the SDR comprises with both headers and message body which is send by the network functions (NFs) [802].
[097] Referring to FIG. 4, an exemplary method flow diagram [400] for optimising a network
15 management process, in accordance with exemplary implementations of the present disclosure
is shown. In an implementation the method [400] is performed by the system [300]. Also, as shown in FIG. 4, the method [400] starts at step [402].
24

[098] At step [404], the method comprises receiving, at an aggregation unit [302], a streaming
data record (SDR) associated with a network procedure of a network function [802]. The SDR
refers a summary of a procedure or a call flow in a network such as 5G network. Also, the SDR
5 may also refer to a data which is continuously flowing from a source system to a target node
or target system associated with the network. The SDR may be generated simultaneously, at a
high speed by plurality of data sources such as a set of servers, a set of sensors, a set of input
devices, a set of processors associated with the network and/or a user device. Further, the
network procedure may include one or more rules and/or one or more operations for managing
10 a lifecycle of a network infrastructure. Further, the network procedure as used herein refers to
a set of steps or actions that are carried out to manage or facilitate communication between devices or systems within the network. The network procedure can include tasks like establishing connections, transferring data, managing resources, and troubleshooting issues.
15 [099] The present disclosure encompasses that the received SDR associated with the network
procedure is generated based on a predefined SDR format associated with said network procedure wherein the predefined SDR format further comprises a SDR header, a SDR payload and a delimiter.
20 [100] The present disclosure encompasses that the SDR header comprises one or more values
associated with at least one of a network function name, a network procedure name, a version or category identifier associated the network procedure, and a relation identifier in a pre-stored format associated with the network function [802].
25 [101] The SDR header is section at the beginning of the predefined SDR format which may
indicate about a data type i.e., a network function (NF) name as depicted in table 1 below, a call flow name, a version data or category identifier, a destination i.e., a relation identifiers . The SDR payload is a section which is an actual intended message.
30 [102] The present disclosure encompasses that the SDR payload comprises plurality of fields,
wherein each field is associated with one of: a SDR type field identifier in a predetermined format, an incoming Request associated with the network function [802], an Outgoing Response associated with the network function [802], an Outgoing Request associated with the network function [802], an Incoming Response associated with the network function [802], an
25

Originating Call Flow associated with the network function [802], and a Terminating Call Flow associated with the network function [802].
[103] The SDR type field identifier as used herein refers to a label or marker within one or
5 field of the SDR payload i.e., a SDR field position. The SDR type field identifier indicates a
type information that is contained in the SDR field position. Such as a SDR field position 1 may indicate the type of SDR, a SDR field position 2 may indicate a subclassification of the type of SDR and so on.
10 [104] Further, the subclassification of the type of SDR may be an integer value such as 1.
Further, said an integer value may indicates that the SDR is associated with at least one of an Incoming Request, an Outgoing Response, an Outgoing Request, an Incoming Response, an Originating Procedure or a Terminating Procedure. Ex- For procedure SDR, it can be, either NF is originating the procedure (Request initiator) or the NF is terminating the procedure
15 (Request Receiver).
[105] The present disclosure encompasses that the predefined SDR format is a delimiter separated record format. The delimiter may be character or symbol which separates one piece of data from another piece of data of the SDR i.e., an identifier that separates the SDR header
20 and the SDR payload. Further, the delimiter may be a specific character, sequence of bits, or
signal used to separate or delineate the SDR header and the SDR payload within the SDR. The delimiters as disclosed in the present disclosure is utilised to identify the boundaries between the SDR header and the SDR payload such as a specific delimiter may be associated with a particular SDR and SDR payload set.
25
[106] At step [406], the method comprises validating, by a validation unit [304], the received SDR based on a predefined target format associated with the SDR, to generate one of a successful validation result and an unsuccessful validation result.
30 [107] The present disclosure encompasses that the received SDR is validated based on one or
more predefined SDR validation policies. The one or more predefined SDR validation policies may include one or more processes for verifying the received SDR with the pre-defined target format. Further the one or more predefined SDR validation policies may be stored in a storage unit [308].
26

[108] The present disclosure encompasses that the predefined target format is a predefined format which may be set by a network operator and stored in the storage unit [308]. Further, in an implementation each SDR field of the SDR may be associated with predefined target format. 5
[109] The present disclosure encompasses that the successful validation result is generated in an event the received SDR successfully matches with the predefined target format associated with the SDR. Further, the unsuccessful validation result is generated in an event the received SDR does not match with the predefined target format associated with the SDR.
10
[110] The present disclosure encompasses that the successful validation result indicates that the received SDR matches or align with the predefined target format and the unsuccessful validation result indicates that the received SDR does not matches or align with the predefined target format. Further, in an implementation the successful validation result indicates that each
15 SDR field of the received SDR matches or align with the predefined target format associated
with said that each SDR field. Further, in another implementation the unsuccessful validation result indicates that at least one SDR field of the received SDR does not matches or align with the predefined target format associated with said that each SDR field.
20 [111] The present disclosure encompasses that the received SDR is validated by matching a
content or one or more attributes of the received SDR with a content or one or more attributes present in the predefined target format.
[112] At step [408], the method comprises ingesting, by the aggregation unit [302], the SDR
25 associated with the network procedure based on the generation of the successful validation
result.
[113] At step [410], the method comprises enriching, by a data analytics engine [306], the
received SDR based on the ingestion of the received SDR. The present disclosure encompasses
30 that the SDR is ingested based on one or more ingestion protocols that may be known to person
skilled in the art. Further the ingestion is a process of importing one or more large files, assorted data files from plurality of sources into a single storage medium or a data warehouse or data mart or database. The present disclosure as disclosed herein, the SDR associated with the network procedure may be transmitted to the data analytics engine [306] i.e., ingested at the
27

data analytics engine [306] based on the generation of the successful validation result associated with the said SDR.
[114] The present disclosure encompasses that enriching, the received SDR further comprises
5 adding, by a processing unit, one or more new values to the received SDR to generate an
enriched SDR; and storing, at a storage unit [308], the enriched SDR. The received SDR is the SDR which was received by the aggregation unit [302] and the enriched SDR is the SDR which received from the data analytics engine [306].
10 [115] The present disclosure encompasses that the received SDR is enriched via utilizing one
or more data enrichment protocols which refers to a process of enhancing the SDR by supplementing a missing information. Further, the missing information is extracted or identified from a data stored in the storage unit [308]. Also, the extraction or identification may be done via one or more data extraction protocols.
15
[116] The present disclosure encompasses that the data analytics engine [306] is configured to enrich the received SDR by adding one or more new values to the received SDR to generate an enriched SDR and by storing the enriched SDR. The present disclosure as disclosed herein, the SDR associated with the network procedure may be transmitted to the data analytics engine
20 [306] i.e., ingested at the data analytics engine [306] based on the generation of the successful
validation result associated with the said SDR.
[117] At step [412], the method comprises generating, by the data analytics engine [306], an
analysis report associated with the network procedure based on at least one of the received
25 SDR and the enriched SDR.
[118] The present disclosure encompasses that the analysis report is generated in at least one of a predefined format and a dynamically generated format.
30 [119] The present disclosure encompasses that the data analytic engine generates the analysis
report via using one or more report generation protocols that automatically generated the analysis report according to the predefined format or the dynamically generated format. The predefined format may have information associated with the analysis report in a structured format having a template where certain sections, styles, or layouts are predetermined. Whereas
28

the dynamically generated format associated with the analysis report refers to a format that is created or adjusted automatically based on certain conditions or inputs. Instead of being fixed like a template, the dynamically generated format adapts or changes depending on the SDR data or the network procedure. 5
[120] The present disclosure encompasses that the method further comprises displaying, via a user interface, the analysis report associated with the network procedure.
[121] The method [400] terminates at step [414].
10
[122] Referring to FIG. 5, an exemplary a sequence flow diagram [500] for requesting a streaming data record (SDR) in accordance with exemplary implementations of the present disclosure is shown. At step S1, a network protocol request is transmitted from a first Network Function (NF1) to a second Network Function (NF2), wherein the NF1 send Field 1 value 1
15 and Field 2 value 1 in the network protocol request to the NF2.
[123] At step S2, a network protocol response is received from NF2 and the network protocol
response is transmitted to the NF1. At step S2, a network protocol response is transmitted from
NF2 to NF1. Further, according to the predefined SDR format, the value 1 of the field 1
20 corresponds to a request and the value 1 of the field 2 corresponds to the outgoing requests i.e.
the protocol request from the NF1 to the NF2.
[124] At step S3, a network protocol request is transmitted from NF2 to NF1.
25 [125] At step S4, another network protocol response is transmitted from NF1 to NF2. Further,
according to the predefined SDR format associated with the NF1 SDR, the value 1 of the field 1 corresponds to a request and the value 3 of the field 2 corresponds to the incoming requests i.e., the network protocol request from the NF2 received at the NF1.
30 [126] Referring to FIG. 6, an exemplary a sequence flow diagram [600] of a response of a
streaming data record (SDR) in accordance with exemplary implementations of the present disclosure is shown. At step S1, as depicted in FIG. 6 in an event a network protocol request is transferred from a first Network Function (NF1) to a second Network Function (NF2). Then, at step S2, a network protocol response associated with the network protocol request is
29

transmitted from NF2 to NF1 should have a field 1 value as 2 indicating the response from the NF2 to the NF1, and a field 2 as 2 indicating outgoing responses from the NF2 to the NF1.
[127] Whereas as in an event the network protocol request is transmitted from the NF1 to
5 NF2 as depicted in step S3, in that event at step S4, a network protocol response associated
with the request at step S3 should have a field 1 have value 2 indicating a response to the request at step S3 and a field 2 have value 2 indicating it as an incoming response from the NF1 at the NF2.
[128] Referring to FIG. 7, an exemplary a sequence flow diagram [700] of a call flow of a streaming data record (SDR) in accordance with exemplary implementations of the present disclosure is shown. At step S1, in an event a network protocol request is transmitted from a first Network Function (NF1) to a second Network Function (NF2). At step S2, a network protocol response is transmitted from NF2 to NF1. Then, a network protocol response associated with the network protocol request of the step S1, if comprises the field 1 value as 3 and the field 2 value as 6 in a SDR as indicated in figure 7 signifies that it is the SDR associated with a call flow and Sub classification of the call flow SDR is a termination call flow i.e., the call flow terminating at the NF2.
[129] Further, as depicted in FIG. 7 in an event a network protocol request is transmitted from to first Network Function (NF1) from a second Network Function (NF2). At step S3, a network protocol response is transmitted from NF1 to NF2. Then, a network protocol response associated with the network protocol request of the step S3, comprises the field 1 value as 3 and the field 2 value as 5 in a SDR as indicated in figure 7 signifies that it is the SDR associated with a call flow and Sub classification of the call flow SDR is a originating call flow i.e., the call flow originating from the NF1.
[130] Referring to FIG. 8, an exemplary a flow diagram [800] of optimising a network
management process in accordance with exemplary implementations of the present disclosure
30 is shown. As depicted in FIG. 8, a Streaming Data Records (SDR) is transmitted from a
plurality of Network Functions (NFs) [802] to a network probing module [804] over a network protocol. The network probing module [804] may include plurality of probing solutions. The Network Function (NFs) [802] adheres to push the data from the NFs) [802] to the network probing module [804] for maintaining sanity and allow a cross correlation across different NFs
30

[802] for stitching one or more call flows across NFs [802] and allowing multiple analytics. The network probing module [804] is remote solution for enabling one or more network operators for optimizing and troubleshooting the network.
5 [131] The present disclosure further discloses a non-transitory computer readable storage
medium storing instructions for optimising a network management process, the instructions include executable code which, when executed by a one or more units of a system, causes: an aggregation unit [302] to receive, a streaming data record (SDR) associated with a network procedure of a network function [802], a validation unit [304] to validate, the received SDR
10 based on a predefined target format associated with the SDR, to generate one of a successful
validation result and an unsuccessful validation result, the aggregation unit [302] to ingest, the SDR associated with the network procedure based on the generation of the successful validation result, data analytics engine [306] to enrich a the received SDR based on the ingestion of the received SDR, and data analytics engine [306] to generate, an analysis report
15 associated with the network procedure based on at least one of the received SDR and the
enriched SDR.
[132] The present disclosure further discloses a user equipment (UE) for optimising a network management process, the UE comprising: a memory; and a processor coupled to the memory, wherein the processor is configured to: transmit, to a system [300], a streaming data record (SDR) associated with a network procedure of a network function [802], and receive, from the system [300], an analysis report associated with the network procedure based on at least one of the received SDR and the enriched SDR, wherein the analysis report is received based on: validating, by the system [300], the received SDR based on a predefined target format associated with the SDR, to generate one of a successful validation result and an unsuccessful validation result, ingesting, by the system [300], the SDR associated with the network procedure based on the generation of the successful validation result, and enriching, by the system [300], the received SDR based on the ingestion of the received SDR.
30 [133] As is evident from the above, the present disclosure provides a technically advanced
solution for optimising a network management process. The present disclosure provides a solution optimising a network management process by introducing a defined structure of streaming data record (SDR) that is easy to implement in the network. The defined structure of SDR is a lightweight structure which include only one or more values and reduce a bandwidth
31

requirement. Also, the defined structure of the SDR is a flexible structure that may be adopted
as per one or more network requirements. In addition to this, the present solution solves the
issues (such as additional requirement of effort and resources, risks of damage to a network
infrastructure, scalability and flexibility issues, potential data loss or delays in capturing critical
5 information, lack of granular visibility) that are faced by conventional solutions such as one or
more physical taps, one or more aggregators, and one or more packet capturing tools. In addition to this the present solution overcome the above-mentioned and other existing problems in this field of technology by validating a received streaming data record (SDR) based on a predefined target format that is associated with the SDR for generating one of a successful
10 validation result and an unsuccessful validation result. Further, the SDR associated with a
network procedure is ingested based on the generation of the successful validation result. Thereafter, the received SDR is enriched, and an analysis report is generated based on at least one of the received SDR and the enriched SDR. Hence, the present solution optimizes the network management process efficiently.
15
[134] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to
20 those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to
be implemented is illustrative and non-limiting.
32

We Claim:
1. A method [400] for optimising a network management process, the method [400]
comprising:
- receiving, at an aggregation unit [302], a streaming data record (SDR) associated with a network procedure of a network function [802];
- validating, by a validation unit [304], the received SDR based on a predefined target format associated with the SDR, to generate one of a successful validation result and an unsuccessful validation result;
- ingesting, by the aggregation unit [302], the SDR associated with the network procedure based on the generation of the successful validation result;
- enriching, by a data analytics engine [306], the received SDR based on the ingestion of the received SDR; and
- generating, by the data analytics engine [306], an analysis report associated with the network procedure based on at least one of the received SDR and the enriched SDR.
2. The method [400] as claimed in claim 1, wherein the enriching, the received SDR further
comprises:
- adding, by a processing unit, one or more new values to the received SDR to generate an enriched SDR; and
- storing, at a storage unit [308], the enriched SDR.

3. The method [400] as claimed in claim 1, wherein the received SDR is validated based on one or more predefined SDR validation policies.
4. The method [400] as claimed in claim 1, wherein the successful validation result is generated in an event the received SDR successfully matches with the predefined target format associated with the SDR, and the unsuccessful validation result is generated in an event the received SDR does not match with the predefined target format associated with the SDR.
5. The method [400] as claimed in claim 1, wherein the received SDR associated with the network procedure is generated based on a predefined SDR format associated with said
33

network procedure wherein the predefined SDR format further comprises a SDR header, a SDR payload and a delimiter.
6. The method [400] as claimed in claim 5, wherein the SDR header comprises one or more values associated with at least one of a network function name, a network procedure name, a version associated the network procedure, and a relation identifier in a pre-stored format associated with the network function [802].
7. The method [400] as claimed in claim 5, wherein the SDR payload comprises plurality of fields, wherein each field is associated with one of: a SDR type field identifier in a predetermined format, an incoming Request associated with the network function [802], an Outgoing Response associated with the network function [802], an Outgoing Request associated with the network function [802], an Incoming Response associated with the network function [802], an Originating Call Flow associated with the network function [802], and a Terminating Call Flow associated with the network function [802].
8. The method [400] as claimed in claim 5, wherein the predefined SDR format is a delimiter separated record format.
9. The method [400] as claimed in claim 1, wherein the analysis report is generated in at least one of a predefined format and a dynamically generated format.
10. The method [400] as claimed in claim 1, the method further comprises displaying, via a user interface, the analysis report associated with the network procedure.
11. A system [300] for optimising a network management process, the system [300] comprising:

- an aggregation unit [302] configured to receive a streaming data record (SDR) associated with a network procedure;
- a validation unit [304] connected to at least the aggregation unit [302], the validation unit [304] configured to validate the received SDR based on a predefined target format associated with the SDR, to generate one of a successful validation result and an unsuccessful validation result,

wherein the aggregation unit [302] is further configured to ingest the SDR associated with the network procedure based on the generation of the successful validation result; and
- a data analytics engine [306] connected to at least the validation unit [304], the data
analytics engine [306] configured to:
enrich the received SDR based on the ingestion of the received SDR, and generate an analysis report associated with the network procedure based on at least one of the received SDR and the enriched SDR.
12. The system [300] as claimed in claim 11, wherein the data analytics engine [306] is
configured to enrich the received SDR by:
- adding one or more new values to the received SDR to generate an enriched SDR; and
- storing the enriched SDR.

13. The system [300] as claimed in claim 11, wherein the received SDR is validated based on one or more predefined SDR validation policies.
14. The system [300] as claimed in claim 11, wherein the successful validation result is generated in an event the received SDR successfully matches with the predefined target format associated with the SDR, and the unsuccessful validation result is generated in an event the received SDR does not match with the predefined target format associated with the SDR.
15. The system [300] as claimed in claim 11, wherein the received SDR associated with the network procedure is generated based on a predefined SDR format associated with said network procedure wherein the predefined SDR format further comprises a SDR header, a SDR payload and a delimiter.
16. The system [300] as claimed in claim 15, wherein the SDR header comprises one or more values associated with at least one of a network function name, a network procedure name, a version associated the network procedure, and a relation identifier in a pre-stored format associated with the network function.

17. The system [300] as claimed in claim 15, wherein the SDR payload comprises plurality of fields, wherein each field is associated with one of: a SDR type field identifier in a predetermined format, an incoming Request associated with the network function [802], an Outgoing Response associated with the network function [802], an Outgoing Request associated with the network function [802], an Incoming Response associated with the network function [802], an Originating Call Flow associated with the network function [802], and a Terminating Call Flow associated with the network function [802].
18. The system [300] as claimed in claim 15, wherein the predefined SDR format is a delimiter separated record format.
19. The system [300] as claimed in claim 11, wherein the data analytics engine [306] is configured to generate the analysis report in at least one of a predefined format and a dynamically generated format.
20. The system [300] as claimed in claim 11, the system further comprising a user interface configured to display the analysis report associated with the network procedure.
21. A user equipment (UE) for optimising a network management process, the UE comprising:
- a memory; and
- a processor coupled to the memory, wherein the processor is configured to:
o transmit, to a system [300], a streaming data record (SDR) associated with a
network procedure of a network function [802], and o receive, from the system [300], an analysis report associated with the network
procedure based on at least one of the received SDR and the enriched SDR,
wherein the analysis report is received based on:
validating, by the system [300], the received SDR based on a predefined target format associated with the SDR, to generate one of a successful validation result and an unsuccessful validation result,
ingesting, by the system [300], the SDR associated with the network procedure based on the generation of the successful validation result, and
enriching, by the system [300], the received SDR based on the ingestion of the received SDR.