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 DYNAMICALLY PROVISIONING STREAMING DATA RECORDS (SDR) INFORMATION”
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 DYNAMICALLY PROVISIONING STREAMING DATA RECORDS (SDR) INFORMATION
TECHNICAL FIELD
5
[0001] Embodiments of the present disclosure generally relate to field of wireless communication system. More particularly, embodiments of the present disclosure relate to system and method for dynamically provisioning streaming data records (SDR) information. 10
BACKGROUND
[0002] 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
15 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.
[0003] Wireless communication technology has rapidly evolved over the past few
20 decades, with each generation bringing significant improvements and advancements. The
first generation of wireless communication technology was based on analog technology
and offered only voice services. However, with the advent of the second-generation (2G)
technology, digital communication and data services became possible, and text messaging
was introduced. 3G technology marked the introduction of high-speed internet access,
25 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
30 more advanced, sophisticated, and capable of delivering more services to its users. Further,
reducing call drops and latency is of paramount importance in the telecommunications industry. Call drops can be frustrating for users, and they can also result in lost revenue for service providers. Latency, on the other hand, refers to the time it takes for data to travel from one device to another and can cause delays and disruptions in communication. The
2

introduction of 5G technology promises to address these issues by delivering ultra-low
latency and high-speed data transmission. With 5G, call drops are going to be minimized,
and users are going to experience seamless, uninterrupted communication. Additionally,
5G technology may enable the development of new applications and services that require
5 high-speed, low-latency communication, such as remote surgeries, autonomous vehicles,
and virtual reality. The reduction of call drops, and latency is crucial in ensuring that users have access to reliable and efficient communication services, and the 5G technology is a significant step towards achieving this goal.
10 [0004] In the 5G communication system, a number of functional modules are provided,
for example an Access and Mobility Management Function (AMF), a network exposure function (NEF), a Unified data management (UDM), a Network Slice Selection Function (NSSF), and/or a Network Repository Function (NRF), etc., one or more of which interacts with each other to implement multiple operations of the 5G communication system. One
15 such function, i.e. NRF is provided for facilitating communication of a third-party
application function, also termed as outside application functions (AF), with a network function (NF) in home-PLMN (h-PLMN). For example, in certain situation, a service for obtaining tracking data of a connected car, the AF is required to retrieve tracking information of the connected car from the UDM. In case of such service requests, the AF
20 communicate with the UDM through the NEF. For ease in reference and understanding,
the concepts of the present disclosure will be discussed focussing on the communication of the AF with the UDM through the NEF, however it may be obvious to a person skilled in the art that similar concepts may be applied for communication of the AF with other NFs through the NEF.
25
[0005] Service Operation: Furthermore, it may be noted that NEF forms an essential network function (NF) for communication of the AF with other NFs. NEF essentially locally stores thereon an SDR data that contains a plurality of streaming data records (SDR) information (also termed as SDR attributes). During a service operation, for example
30 retrieval of tracking information by the AF, the NEF receives a service request from the
AF containing one or more SDR information (or SDR attributes); authenticates the SDR information in the service request; and transmits the service request to the UDM in case of positive authentication of the SDR information. Thereafter, in the same service operation, the NEF receives a service request approval, containing one or more SDR information,
3

from the UDM; and transmits the service request approval, containing one or more SDR information, to the AF. In such service operations, there may be situation of failure of such execution of the service process. Accordingly, the v-probe is provided in the network system, to perform failure analysis. 5
[0006] Failure Analysis: v-Probe is provided in the wireless communication system to perform analysis of the cause of failure of any service operation. For example, in case of failure of service operation at the NEF, the v-Probe receives the plurality of SDR information provisioned in the SDR data stored on the NEF; performs analytics on the
10 plurality of SDR information to identify the cause of failure; and display a report of the
analytics on a dashboard. It may be noted that the analytics performed by the v-Probe is periodically required to be changed. For such purposes, the NEF is periodically required to be provisioned, by an API interface, with one or more new SDR information. However, such provisioning of the SDR information in the SDR data stored on the NEF, may require
15 a downtime of the NEF. Such downtime of the NEF can further cause disconnection of the
AF from the h-PLMN, which is an unadvisable technique.
[0007] Thus, there exists an imperative need in the art to provide a system and method
of provisioning the new SDR information to the SDR data stored in the NEF, without
20 causing downtime of the NEF thereof, which the present disclosure aims to address.
SUMMARY
[0008] This section is provided to introduce certain aspects of the present disclosure in
25 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.
[0009] An aspect of the present disclosure may relate to a method for dynamically
provisioning Streaming Data Records (SDR) information. The method includes providing,
30 by a display unit, at least one template associated with a network exposure function (NEF)
to a user to receive a user input corresponding to the at least one template. Next, the method includes modifying, by a modifying unit, a set of attributes associated with the at least one template in real-time based on the received user input corresponding to at least one network failure event. Next, the method includes storing, by a storing unit via a secured Application
4

Programming Interface (API), the modified template at a database. Next, the method includes generating, by a generating unit, an SDR based on the stored template. Thereafter, the method includes transmitting, by a transmitting unit, the generated SDR to a probing engine for failure analysis. 5
[0010] In an exemplary aspect of the present disclosure, modifying the at least one template further comprises at least one of adding and removing at least one attribute of the set of attributes from the at least one template.
10 [0011] In an exemplary aspect of the present disclosure, the method further comprises
enabling, by a processing unit, storing of the modified template without interrupting NEF's ongoing operations.
[0012] In an exemplary aspect of the present disclosure, the set of attributes comprises
15 subscriber identifiers and monitoring types associated with one or more network call flows.
[0013] In an exemplary aspect of the present disclosure, the NEF operates as part of an
overall 5G network architecture interfacing with User Data Management (UDM), Access
and Mobility Management Function (AMF), Session Management Function (SMF), and
20 Network Repository Function (NRF) components.
[0014] In an exemplary aspect of the present disclosure, the at least one template comprises a plurality of attributes corresponding to a set of network failures.
25 [0015] Another aspect of the present disclosure may relate to a system for dynamically
provisioning Streaming Data Records (SDR) information. The system comprising a display unit configured to provide at least one template associated with a network exposure function (NEF) to a user to receive a user input corresponding to the at least one template; a modifying unit configured to modify a set of attributes associated with the at least one
30 template in real-time based on the received user input corresponding to at least one network
failure event; a storing unit configured to store via a secured Application Programming Interface (API), the modified template at a database; a generating unit configured to generate an SDR based on the stored template; and a transmitting configured to transmit the generated SDR to a probing engine for failure analysis.
5

[0016] Another aspect of the present disclosure may relate to a user equipment (UE)
comprising: a processor configured to: display at least one template associated with a
network exposure function (NEF) to a user to receive a user input corresponding to the at
5 least one template; modify a set of attributes associated with the at least one template in
real-time based on the received user input corresponding to at least one network failure event, wherein a Streaming Data Record (SDR) is generated based on the modified set of attributes associated with the at least one template, and wherein the generated SDR is transmitted to a probing engine for failure analysis.
10
[0017] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for dynamically provisioning Streaming Data Records (SDR) information, the storage medium include executable code which, when executed by one or more units of a system, causes: a display unit configured
15 to provide at least one template associated with a network exposure function (NEF) to a
user to receive a user input corresponding to the at least one template; a modifying unit configured to modify a set of attributes associated with the at least one template in real¬time based on the received user input corresponding to at least one network failure event; a storing unit configured to store via a secured Application Programming Interface (API),
20 the modified template at a database; a generating unit configured to generate an SDR based
on the stored template; and a transmitting unit configured to transmit the generated SDR to a probing engine for failure analysis.
OBJECTS OF THE INVENTION
25
[0018] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0019] It is an object of the present disclosure to provide a system and a method for
30 runtime provisioning of the new streaming data record (SDR) information to the SDR data
stored in the network exposure function (NEF), without causing downtime of the NEF.
[0020] It is another object of the present disclosure to provide a system and a method for runtime provisioning of the new SDR information to the SDR data stored in the NEF. The
6

system and method provides for: receiving, by the NEF, a provisioning request from an
API interface; sending, by the NEF, a provisioning approval to the API interface; receiving,
by the NEF a provisioning file containing one or more new SDR information from the API
interface; storing the new SDR information contained in the provisioning file in a NEF
5 database of the NEF.
DESCRIPTION OF THE DRAWINGS
[0021] The accompanying drawings, which are incorporated herein, and constitute a part
10 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
15 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.
20 [0022] FIG. 1 illustrates an exemplary block diagram representation of 5th generation
core (5GC) network architecture.
[0023] 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
25 implementation of the present disclosure.
[0024] FIG. 3 illustrates an exemplary block diagram of a system for dynamically provisioning Streaming Data Records (SDR) information, in accordance with exemplary implementations of the present disclosure. 30
[0025] FIG. 4 illustrates a method flow diagram for dynamically provisioning Streaming Data Records (SDR) information in accordance with exemplary implementations of the present disclosure.
7

[0026] FIG. 5 illustrates an exemplary network architecture block diagram of a system for dynamically provisioning Streaming Data Records (SDR) information, in accordance with exemplary implementations of the present disclosure.
5 [0027] FIG. 6 illustrates a sequence flow diagram for dynamically provisioning
Streaming Data Records (SDR) information, in accordance with exemplary implementations of the present disclosure.
[0028] The foregoing shall be more apparent from the following more detailed
10 description of the disclosure.
DETAILED DESCRIPTION
[0029] In the following description, for the purposes of explanation, various specific
15 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
20 only some of the problems discussed above.
[0030] 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
25 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.
[0031] Specific details are given in the following description to provide a thorough
30 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.
8

[0032] Also, it is noted that individual embodiments may be described as a process which
is depicted as a flowchart, a flow diagram, a data flow diagram, a structure 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
5 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.
[0033] 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
10 disclosed herein is not limited by such examples. In addition, any aspect or design described
herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar
15 words are used in either the detailed description or the claims, such terms are intended to
be inclusive—in a manner similar to the term “comprising” as an open transition word— without precluding any additional or other elements.
[0034] As used herein, a “processing unit” or “processor” or “operating processor”
20 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 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
25 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 working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
30 [0035] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a
smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment/device may
9

include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose
computer, desktop, personal digital assistant, tablet computer, wearable device or any other
computing device which is capable of implementing the features of the present disclosure.
Also, the user device may contain at least one input means configured to receive an input
5 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.
[0036] As used herein, “storage unit” or “memory unit” refers to a machine or computer-
10 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 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
15 of the system to perform their respective functions.
[0037] As used herein “interface” or “user interface refers to a shared boundary across
which two or more separate components of a system exchange information or data. The
interface may also be referred to a set of rules or protocols that define communication or
20 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.
[0038] All modules, units, components used herein, unless explicitly excluded herein,
may be software modules or hardware processors, the processors being a general-purpose
25 processor, a special purpose processor, a conventional processor, a digital signal processor
(DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
30 [0039] As used herein the transceiver unit include at least one receiver and at least one
transmitter configured respectively for receiving and transmitting data, signals, information, or a combination thereof between units/components within the system and/or connected with the system.
10

[0040] As used herein, the secured application programming interface (API) refers to a
set of protocols and tools that include specific security measures to protect data integrity,
confidentiality, and authentication. Security features integrated within the API may include
token-based authentication, encryption, secure sockets layer (SSL) or transport layer
5 security (TLS) protocols, and regular security audits.
[0041] As used herein, Subscription Permanent Identifier (SUPI) is a globally unique
identifier that is assigned to each subscriber in network such as 5G network. The SUPI may
have a string of 15 decimal digits. The SUPI may have digits representing Mobile Country
10 Code (MCC), Mobile Network Code (MNC) identifying the network operator and Mobile
Subscriber Identification Number (MSIN) representing the individual user of that particular network operator.
[0042] As used herein, the templates refer to predefined configurations and guidelines
15 that facilitate the integration and implementation of new services, parameters,
functionalities within the network. The templates provide a standardized framework to
ensure consistency, compatibility, and efficiency when adding new functionalities or
modifications in parameters for performing any changes in the network service based on
the requirement. The templates include detailed instructions on service behavior,
20 interaction protocols, and integration points with existing network elements. Further, the
templates may facilitate modification or changes in the parameters or attributes of a network service, or a call flow based on authorisation of a user.
[0043] As discussed in the background section, the current known solutions have several
25 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 dynamically provisioning Streaming Data Records (SDR) information.
[0044] ‘Service operation’ are referred to as various service requested by a third-party
30 or outside Application Function (AF) from one or more network functions (NFs) in the
home-PLMN (h-PLMN). For example, in order to retrieve a tracking information of a connected car, the AF is required to perform tracking service operation at the home PLMN. A process to execute such service operation includes: receiving, by a network exposure function (NEF), a service request containing one or more SDR information (or SDR
11

attributes) from the AF; authenticating, by the NEF, the SDR information in the service
request; and transmitting, by the NEF, the service request to a Unified data management
(UDM) in case of positive authentication of the SDR information; receiving, by the NEF,
a service request approval, containing one or more SDR information, from the UDM; and
5 transmitting the service request approval, containing the one or more SDR information, to
the AF. Furthermore, in such service operations, there may be situation of failure of such execution of the service operation. Accordingly, the v-probe is provided in the network system, to perform failure analysis.
10 [0045] ‘Failure analyses refer to an analysis of various SDR information stored on the
NEF, to identify the cause of failure of any service operation. A process of facilitating such failure analysis includes: receiving, by the v-Probe, the plurality of SDR information provisioned in the SDR data stored on the NEF database of the NEF; performing, by the v-probe, an analytics on the plurality of SDR information to identify the cause of failure; and
15 displaying, by the v-probe, a report of the analytics on a dashboard. It may be noted that
the analytics performed by the v-Probe is periodically required to be changed. For such purposes, the NEF is periodically required to be provisioned, by an API interface, with one or more new SDR information. However, such provisioning of the SDR information in the SDR data stored on the NEF, may require a downtime of the NEF. Such downtime of the
20 NEF can further cause disconnection of the AF from the h-PLMN, which is unadvisable
technique.
[0046] ‘Provisioning’ herein refers to addition/deletion/updating of the SDR information in the SDR data stored on the NEF database of the NEF. In the present disclosure, the
25 system and method provide for runtime provisioning of the new streaming data record
(SDR) information to the SDR data stored in the network exposure function (NEF). The method includes: receiving, by the NEF, a provisioning request from an API interface; sending, by the NEF, a provisioning approval to the API interface; receiving, by the NEF a provisioning file containing one or more new SDR information from the API interface;
30 storing the new SDR information contained in the provisioning file in a NEF database of
the NEF.
[0047] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture, in accordance with exemplary implementation of the
12

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)
5 [112], a Network Slice Specific Authentication and Authorization Function (NSSAAF)
[114], a Network Slice Selection Function (NSSF) [116], a Network Exposure Function
(NEF) [118], a 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
10 components are assumed to be connected to each other in a manner as obvious to the person
skilled in the art for implementing features of the present disclosure.
[0048] 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
15 access to different types of networks (e.g., 5G network). It consists of radio base stations
and the radio access technologies that enable wireless communication.
[0049] Access and Mobility Management Function (AMF) [106] is a 5G core network
function responsible for managing access and mobility aspects, such as UE registration,
20 connection, and reachability. It also handles mobility management procedures like
handovers and paging.
[0050] Session Management Function (SMF) [108] is a 5G core network function
responsible for managing session-related aspects, such as establishing, modifying, and
25 releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding
and handles IP address allocation and QoS enforcement.
[0051] Service Communication Proxy (SCP) [110] is a network function in the 5G core
network that facilitates communication between other network functions by providing a
30 secure and efficient messaging service. It acts as a mediator for service-based interfaces.
[0052] 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.
13

[0053] 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
5 authorized.
[0054] 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. 10
[0055] Network Exposure Function (NEF) [118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
15 [0056] 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.
[0057] Policy Control Function (PCF) [122] is a network function responsible for policy
20 control decisions, such as QoS, charging, and access control, based on subscriber
information and network policies.
[0058] Unified Data Management (UDM) [124] is a network function that centralizes
the management of subscriber data, including authentication, authorization, and
25 subscription information.
[0059] Application Function (AF) [126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services. 30
[0060] User Plane Function (UPF) [128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.
14

[0061] Data Network (DN) [130] refers to a network that provides data services to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.
5 [0062] FIG. 2 illustrates an exemplary block diagram of a computing device [1000] (also
referred to herein as a computer system [1000]) upon which the features of the present disclosure 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 dynamically provisioning Streaming Data Records (SDR) information
10 utilizing the system. In another implementation, the computing device [1000] itself
implements the method for dynamically provisioning Streaming Data Records (SDR) information using one or more units configured within the computing device [1000], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
15
[0063] The computing device [1000] may include a bus [1002] or other communication mechanism for communicating information, and a processor [1004] coupled with the bus [1002] for processing information. The processor [1004] may be, for example, a general-purpose microprocessor. The computing device [1000] may also include a main memory
20 [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 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
25 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 [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].
30
[0064] 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)
15

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
5 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.
10
[0065] 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 device [1000] to be a special-purpose machine. According to one
15 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 contained in the main memory [1006] causes
20 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.
[0066] The computing device [1000] also may include a communication interface [1018]
25 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]. For example, the communication interface [1018] may be an integrated services
digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data
communication connection to a corresponding type of telephone line. As another example,
30 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 signals that carry digital data streams representing various types of information.
16

[0067] 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
5 for an application program through the Internet [1028], the host [1024], the ISP [1026], 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.
10 [0068] The computing device [1000] encompasses a wide range of electronic devices
capable of processing data and performing computations. Examples of computing device [1000] include, but are not limited only to, personal computers, laptops, tablets, smartphones, servers, and embedded systems. The devices may operate independently or as part of a network and can perform a variety of tasks such as data storage, retrieval, and
15 analysis. Additionally, computing device [1000] may include peripheral devices, such as
monitors, keyboards, and printers, as well as integrated components within larger electronic systems, showcasing their versatility in various technological applications.
[0069] Referring to FIG. 3, an exemplary block diagram of a system [300] for
20 dynamically provisioning Streaming Data Records (SDR) information, is shown, in
accordance with the exemplary implementations of the present disclosure. The system
[300] comprises at least one display unit [302], at least one modifying unit [304], at least
one storing unit [306], at least one generating unit [308], at least one transmitting unit [310],
at least one processing unit [312], at least one database [314] and at least one Network
25 Exposure Function (NEF) [118]. Also, all of the components/ units of the system [300] are
assumed to be connected to 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. Also, in FIG. 3 only a few units are shown, however, the system [300] may comprise
multiple such units or the system [300] may comprise any such numbers of said units, as
30 required to implement the features of the present disclosure. Further, in an implementation,
the system [300] may be present in a user device to implement the features of the present disclosure. The system [300] may be a part of the user device / or may be independent of but in communication with the user device (may also referred herein as a UE). In another implementation, the system [300] may reside in a server or a network entity. In yet another
17

implementation, the system [300] may reside partly in the server/ network entity and partly in the user device.
[0070] The system [300] is configured for dynamically provisioning Streaming Data
5 Records (SDR) information, with the help of the interconnection between the
components/units of the system [300].
[0071] The system [300] comprises a display unit [302] configured to provide at least one template associated with a network exposure function (NEF) [118] to a user to receive
10 a user input corresponding to the at least one template. The display unit [302] of the system
[300] may provide at least one template associated with the NEF [118] to the user for receiving one or more input corresponding to the at least one template. In an exemplary aspect, the NEF [118] operates as part of an overall 5G network architecture interfacing with User Data Management (UDM) [124], Access and Mobility Management Function
15 (AMF) [106], Session Management Function (SMF) [108], and Network Repository
Function (NRF) [120] components. In an exemplary aspect, the user may be such as, but not limited to network administrator, service provider, or authorized person. The NEF [118] is a network function that securely exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and internal application
20 functions (AFs) over a secure application programming interface (API). In an exemplary
aspect, the NEF [118] may be a single entity or a group of NEFs or a NEF cluster. In an implementation, the user may access the at least one template associated with the NEF [118] for providing the input. The at least one template may comprise a plurality of attributes corresponding to the set of network failures. The template may have information
25 for network functions (NFs), monitoring attributes/parameters (for e.g. Subscription
Permanent Identifier (SUPI)), monitoring type based on call flows and the like. The display unit [302] may communicatively attached with such as user device, human machine interface (HMI) and computing device. The user may access the template associated with the NEF [118] for providing one or more input(s) for such as, but not limited to, adding
30 attributes, adding network functions call flows for monitoring network performance and
failures. In an exemplary aspect, the user may provide input in form of a file via secured application programming interface (API) as provisioning request.
18

[0072] The system [300] comprises a modifying unit [304] configured to modify a set of
attributes associated with the at least one template in real-time based on the received user
input corresponding to at least one network failure event. The modifying unit [304] of the
system [300] may modify the set of attributes associated with the at least one template in
5 real-time based on the received user input corresponding to at least one network failure
event. In an exemplary aspect, the modifying unit [304] may communicatively attached with the displaying unit [302]. After receiving the user input from the displaying unit [302], the modifying unit [304] may modify the set of attributes in real-time or run time corresponding to the network failure event. The set of attributes may comprise at least one
10 of subscriber identifiers and monitoring types associated with one or more network call
flows. In an exemplary aspect, the modification of the at least one template further comprises at least one of adding and removing at least one attribute of the set of attributes from the at least one template. In an implementation, the user may provide input (such as attributes and for NFs details) via the display unit [302] for modifying the template
15 depending upon call flow in real-time or run-time, which needs to debug. Based on the
received input(s), the modifying unit [304] may modify the template in real-time based on the received user input corresponding to at least one network failure event.
[0073] In an exemplary aspect, network call flows may be a sequence or steps of a
20 service (such as voice or data transmission) implementation in the network. In an
exemplary aspect, the network call flow may be associated with steps or service operations
procedure of the network functions (NF) in network such as, but not limited to, 5G network.
In an exemplary aspect, network call flow may comprise registration, subscription, and/or
notification etc. For example, subscription flow for which Application Function (AF) [126]
25 is subscribing to NEF [118] to have monitoring events information against SUPI from the
deployed network.
[0074] The system [300] comprises a storing unit [306] configured to store via a secured
Application Programming Interface (API), the modified template at a database [314]. The
30 storing unit [306] of the system [300] may store the modified template at the database [314]
via the secured API. In an exemplary aspect, the storing unit [306] of the system [300] may communicatively attached with the modifying unit [304]. The modified template with the set of attributes in real time by the modifying unit [304] may store by the storing unit [306] via the secured API at the database [314]. The stored modified template at the database
19

[314] may access for further processing and analyzing failure events in the network. In an exemplary aspect, the modified template may store with at least one of timestamp, template ID, so that latest/ new/ older modified template can be identified and may further process based on the requirements. 5
[0075] In an exemplary aspect, the system [300] further comprises a processing unit [312] configured to enable storing of the modified template without interrupting NEF's [118] ongoing operations. The processing unit [312] of the system [300] may enable storing of the modified template into database [314] without interrupting NEF's [118] ongoing
10 operations. In an exemplary aspect, the processing unit [312] may receive the modified
template from the modifying unit [304] for debugging one or more network service or operation issues based on user input provided at run-time. The processing unit [312] is configured to enable storing of the modified template without interrupting NEF's [118] ongoing operations. The NEF [118] operation may be one or more call flow associated with
15 User Data Management (UDM) [124], Access and Mobility Management Function (AMF)
[106], Session Management Function (SMF) [108], and Network Repository Function (NRF) [120] components. In an exemplary aspect, the NEF [118] operation may be associated with third party application service request.
20 [0076] The system [300] comprises a generating unit [308] configured to generate an
SDR based on the stored template. The generating unit [308] of the system [300] may
generate the Streaming Data Records (SDRs) based on the stored template. In an exemplary
aspect, the generating unit [308] may communicatively attached with the database [314].
The generating unit [308] may access the stored modified template for generating the
25 Streaming Data Records (SDRs). The generating unit [308] may store the generated SDR
into the database [314]. The SDR may represent transactions or logs as debugging records
data for such as, but not limited to, 5G network call flow service operation. The generated
SDR may have timestamp information and involved network functions (NFs) operation. In
an exemplary aspect, when user modifies the template with the set of the attributes in run-
30 time or real-time for any debugging or identify any required network issues, the generating
unit [308] may generate the SDR records with latest modified template. In an exemplary
aspect, the generating unit [308] may generate the SDR records based on user provided
template ID or timestamp and the like.
20

[0077] The system [300] comprises a transmitting unit [310] configured to transmit the
generated SDR to a probing engine for failure analysis. The transmitting unit [310] of the
system [300] may transmit the generated SDR to the probing engine for failure analysis.
The probing engine or v-probe engine or virtual probing engine may perform failure
5 analysis of the service operation, by performing failure analysis of the generated SDR
information stored in the database [314]. The generated failure analysis performed by the
probing engine may be send to the display unit [302] for taking further necessary corrective
action(s) by the user/network administrator. The failure analysis may comprise information
at least one of such as, but not limited to, root causing issues, parameters, network function
10 nodes and errors in call flow executions. In an exemplary aspect, after receiving the failure
analysis, the user/network administrator may run further new modified template for specified call flow for identifying service issues.
[0078] Further, in accordance with the present disclosure, it is to be acknowledged that
15 the functionality described for the various the components/units can be implemented
interchangeably. While specific embodiments may disclose a particular functionality of
these units for clarity, it is recognized that various configurations and combinations thereof
are within the scope of the disclosure. The functionality of specific units as disclosed in the
disclosure should not be construed as limiting the scope of the present disclosure.
20 Consequently, alternative 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.
[0079] Referring to FIG. 4, an exemplary method flow diagram [400] for dynamically
25 provisioning Streaming Data Records (SDR) information, in accordance with exemplary
implementations of the present disclosure is shown. In an implementation the method [400] is performed by the system [300]. Further, in an implementation, the system [300] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 4, the method [400] starts at step [402]. 30
[0080] At step [404], the method [400] as disclosed by the present disclosure comprises providing, by a display unit [302], at least one template associated with a network exposure function (NEF) [118] to a user to receive a user input corresponding to the at least one template. The method [400] implemented by the display unit [302] of the system [300] may
21

provide at least one template associated with the NEF [118] to the user to for receiving one
or more input corresponding to the at least one template. In an exemplary aspect, the NEF
[118] operates as part of an overall 5G network architecture interfacing with User Data
Management (UDM) [124], Access and Mobility Management Function (AMF) [106],
5 Session Management Function (SMF) [108], and Network Repository Function (NRF)
[120] components. In an exemplary aspect, the user may be such as, but not limited to network administrator, service provider, or authorized person. The NEF [118] is a network function that securely exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and internal application
10 functions (AFs) over a secure application programming interface (API). In an exemplary
aspect, the NEF [118] may be a single entity or a group of NEFs or a NEF cluster. In an implementation, the user may access the at least one template associated with the NEF [118] for providing the input. The at least one template may comprise a plurality of attributes corresponding to the set of network failures. The template may have information
15 for network functions (NFs), monitoring attributes/parameters (for e.g. Subscription
Permanent Identifier (SUPI)), monitoring type based on call flows and the like. The display unit [302] may communicatively attached with such as user device, human machine interface (HMI) and computing device. The user may access the template associated with the NEF [118] for providing one or more input(s) for such as, but not limited to, adding
20 attributes, adding network functions call flows for monitoring network performance and
failures. In an exemplary aspect, the user may provide input in form of a file via secured application programming interface (API) as provisioning request.
[0081] Next, at step [406], the method [400] as disclosed by the present disclosure
25 comprises modifying, by a modifying unit [304], a set of attributes associated with the at
least one template in real-time based on the received user input corresponding to at least
one network failure event. The method [400] implemented by the modifying unit [304] of
the system [300] may modify the set of attributes associated with the at least one template
in real-time based on the received user input corresponding to at least one network failure
30 event. In an exemplary aspect, the modifying unit [304] may communicatively attached
with the displaying unit [302]. After receiving the user input from the displaying unit [302], the modifying unit [304] may modify the set of attributes in real-time or run time corresponding to the network failure event. The set of attributes may comprise at least one of subscriber identifiers and monitoring types associated with one or more network call
22

flows. In an exemplary aspect, the modification of the at least one template further
comprises at least one of adding and removing at least one attribute of the set of attributes
from the at least one template. In an implementation, the user may provide input (such as
attributes and for NFs details) via the display unit [302] for modifying the template
5 depending upon call flow in real-time or run-time, which needs to debug. Based on the
received input(s), the modifying unit [304] may modify the template in real-time based on the received user input corresponding to at least one network failure event.
[0082] In an exemplary aspect, network call flows may be a sequence or steps of a
10 service (such as voice or data transmission) implementation in the network. In an
exemplary aspect, the network call flow may associate with steps or service operations
procedure of the network functions (NF) in network such as, but not limited to, 5G network.
In an exemplary aspect, network call flow may comprise registration, subscription, and/or
notification etc. For example, subscription flow for which Application Function (AF) [126]
15 is subscribing to NEF [118] to have monitoring events information against SUPI from the
deployed network.
[0083] Next, at step [408], the method [400] as disclosed by the present disclosure comprises storing, by a storing unit [306] via a secured Application Programming Interface
20 (API), the modified template at a database [314]. The method [400] implemented by the
storing unit [306] of the system [300] may store the modified template at a database [314] via the secured API. In an exemplary aspect, the storing unit [306] of the system [300] may communicatively attached with the modifying unit [304]. The modified template with the set of attributes in real time by the modifying unit [304] may store by the storing unit [306]
25 via the secured API at the database [314]. The stored modified template at the database
[314] may access for further processing and analyzing failure events in the network. In an exemplary aspect, the modified template may store with at least one of timestamp, template ID, so that latest/ new/ older modified template can be identified and may further process based on the requirements.
30
[0084] In an exemplary aspect, the method further comprises enabling, by a processing unit [312], storing of the modified template without interrupting NEF's [118] ongoing operations. The processing unit [312] of the system [300] may enable storing of the modified template into the database [314] without interrupting NEF's [118] ongoing
23

operations. In an exemplary aspect, the processing unit [312] may receive the modified
template from the modifying unit [304] for debugging one or more network service or
operation issues based on user input provided at run-time. The processing unit [312] is
configured to enable storing of the modified template without interrupting NEF's [118]
5 ongoing operations. The NEF [118] operation may be one or more call flow associated with
User Data Management (UDM) [124], Access and Mobility Management Function (AMF) [106], Session Management Function (SMF) [108], and Network Repository Function (NRF) [120] components. In an exemplary aspect, the NEF [118] operation may be associated with third party application service request.
10
[0085] Next, at step [410], the method [400] as disclosed by the present disclosure comprises generating, by a generating unit [308], an SDR based on the stored template. The method [400] implemented by the generating unit [308] of the system [300] may generate the SDR based on the stored template. In an exemplary aspect, the generating unit
15 [308] may communicatively attached with the database [314]. The generating unit [308]
may access the stored modified template for generating the Streaming Data Records (SDRs). The generating unit [308] may store the generated SDR into the database [314]. The SDR may represent transactions or logs as debugging records data for such as, but not limited to, 5G network call flow service operation. The generated SDR may have
20 timestamp information and involved network functions (NFs) operation. In an exemplary
aspect, when user modifies the template with the set of the attributes in run-time or real¬time for any debugging or identify any required network issues, the generating unit [308] may generate the SDR records with latest modified template. In an exemplary aspect, the generating unit [308] may generate the SDR records based on user provided template ID
25 or timestamp and the like.
[0086] Next, at step [412], the method [400] as disclosed by the present disclosure
comprises transmitting, by a transmitting unit [310], the generated SDR to a probing engine
for failure analysis. The method [400] implemented by the transmitting unit [310] of the
30 system [300] may transmit the generated SDR to the probing engine for failure analysis.
The probing engine or v-probe engine or virtual probing engine may perform failure analysis of the service operation, by performing failure analysis of the generated SDR information stored in the database [314]. The generated failure analysis performed by the probing engine may be send to the display unit [302] for taking further necessary corrective
24

action(s) by the user/network administrator. The failure analysis may comprise information
at least one of such as, but not limited to, root causing issues, parameters, network function
nodes and errors in call flow executions. In an exemplary aspect, after receiving the failure
analysis, the user/network administrator may run further new modified template for
5 specified call flow for identifying service issues.
[0087] Thereafter, the method [400] terminates at step [414].
[0088] FIG. 5 illustrates an exemplary network architecture [500] block diagram of a
10 system for dynamically provisioning Streaming Data Records (SDR) information, in
accordance with exemplary implementations of the present disclosure. The network
architecture [500] comprises at least one a secured application program interface (API)
[502], at least one network exposure function (NEF)/ NEF Cluster [118] having one or
more NEFs [118a-1184n] (collectively referred to as NEF [118] or individually referred to
15 as NEF [118] herein), at least one v-Probe engine [506], and one or more network functions
including a unified data management function (UDM) [124], an Access and Mobility
Management Function (AMF) [106], a session management function (SMF) [108], and a
network repository function (NRF) [120]. Furthermore, a third-party application function
(AF) [126] is shown that communicates with one or more network functions (NFs) through
20 the network exposure function (NEF) [118], for enabling execution of one or more service
operations. It may be noted that the NFs are shown only as exemplary and may include
other NFs as well.
[0089] It may be noted that the NEF [118] is provided to facilitate the service operations
25 from the network functions (NFs), when requested by the AF [126]. In the present
disclosure, the NEF [118] includes a NEF database [514]. A system architecture and arrangement of the NEF [118] is commonly known to a person skilled in the art and is not repeated herein for the sake of brevity.
30 [0090] The v-Probe engine [506] is provided to perform failure analysis of the service
operation, by performing failure analysis of the SDR information in the SDR data stored on the NEF database [514] of the NEF [118].
25

[0091] In an operation, the AF [126] may provide set of attributes for the call flow
execution for the NFs in a template in real-time or run-time. The NEF/NEF cluster [118]
comprises one or more NEFs (NEF1 [118a] ...NEFn [118n]). In an exemplary aspect, each
of NEF [118] may store the template and process for the specific call flow and store
5 associated information into the database [514]. The specific NEF may receive the provided
input by the AF [126], modify the template base on the input and execute the modified
template. Further, the NEF [118] generate SDR log data based on the latest modified
template and send the SDR data information to the v-Probe engine [506] for failure
analysis. The v-Probe engine [506] may perform the failure analysis and may provide root
10 cause issues, call flow issues and NF’s performance issues for taking further any corrective
action(s). In an exemplary aspect, after receiving the failure analysis, a new modified template may further run for specified call flow for identifying service issues.
[0092] FIG. 6 illustrates a sequence flow [600] diagram for dynamically provisioning
15 Streaming Data Records (SDR) information, in accordance with exemplary
implementations of the present disclosure. In an exemplary aspect, the sequence flow [600] may performed by the system [300].
[0093] At step S2, access the template may be performed. The user may access the
20 template associated with a network exposure function (NEF) [118] via a display unit [302].
The user may provide one or more input such as attributes/parameters for e.g. Subscription Permanent Identifier (SUPI), NFs information and information for call flow execution for debugging the network issues.
25 [0094] At step S4, upload and save the template may be performed. The display unit
[302] may communicatively attached with the modifying unit [304], which modify the template based on the user input. The modified template with the set of attributes may upload and save in the database [314]. The modified template may store with timestamp and template ID for further processing or usage in the database [314].
30
[0095] At step S6, execute the call flow may be performed. In an exemplary aspect, the generating unit [308] may execute the call flow for performing the debugging and resolving network issues.
26

[0096] At step S8, analyze the template for respective scenario may be performed. The
generating unit [308] may analyze the modified template for the respective scenario based
on the provided user input. In an exemplary aspect, the generating unit [308] may analyze
the call flow for 5G network scenario with the provided set of the attributes by the user and
5 may generate streaming data records (SDR) or records log data for further processing. The
generating unit [308] may also store SDR data information into the database [314] associated with the template.
[0097] At step S10, forward generated SDR to v-Probe may be performed. The
10 generating unit [308] may share the generated SDR data information with the transmitting
unit [310], which may forward the generated SDRs data to the v-Probe engine. The v-Probe
engine may perform failure analysis to identify the call flow issue or network service issues
and provide insights to the user on display unit [302] for taking further actions. The actions
may be such as, modifying/adding/ removing attributes in the template, modifying NFs,
15 estimating service maintenance/replacement requirement and the like.
[0098] The present disclosure further discloses a user equipment (UE) comprising: a processor configured to: display at least one template associated with a network exposure function (NEF) [118] to a user to receive a user input corresponding to the at least one
20 template; modify a set of attributes associated with the at least one template in real-time
based on the received user input corresponding to at least one network failure event, wherein a Streaming Data Record (SDR) is generated based on the modified set of attributes associated with the at least one template, and wherein the generated SDR is transmitted to a probing engine for failure analysis.
25
[0099] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for dynamically provisioning Streaming Data Records (SDR) information, the instructions include executable code which, when executed by one or more units of a system, causes: a display unit [302] configured to provide at least one
30 template associated with a network exposure function (NEF) [118] to a user to receive a
user input corresponding to the at least one template; a modifying unit [304] configured to modify a set of attributes associated with the at least one template in real-time based on the received user input corresponding to at least one network failure event; a storing unit [306] configured to store via a secured Application Programming Interface (API), the modified
27

template at a database [314]; a generating unit [308] configured to generate an SDR based on the stored template; and a transmitting unit [310] configured to transmit the generated SDR to a probing engine for failure analysis.
5 [0100] As is evident from the above, the present disclosure provides a technically
advanced solution for provisioning the new SDR information to the SDR data stored in the
NEF database [514] of the NEF [118], in accordance with exemplary embodiments of the
present invention is shown. As is explained in the flowchart above, the disclosed system
[300] and method [400] comprises runtime provisioning of the SDR information to the
10 NEF database [514] of the NEF [118], and thus it avoids a downtime of the NEF [118]. At
any moment SDR fields can be modified by adding or removing required attribute which need to be captured while call failure. Accordingly, the v-Probe is capable of effectively performing failure analysis of the service operation.
15 [0101] 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. 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
20 the disclosure, should not be construed as limiting the scope of the present disclosure.
Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are encompassed within the scope of the present disclosure.
25 [0102] While considerable emphasis has been placed herein on the disclosed
embodiments, it will be appreciated that many embodiments can be made and that many changes can be made to the embodiments without departing from the principles of the present disclosure. These and other changes in the embodiments of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing
30 descriptive matter to be implemented is illustrative and non-limiting.
28

We Claim:
1. A method for dynamically provisioning Streaming Data Records (SDR) information,
the method comprising:
providing, by a display unit [302], at least one template associated with a
5 network exposure function (NEF) [118] to a user to receive a user input
corresponding to the at least one template;
modifying, by a modifying unit [304], a set of attributes associated with the at
least one template in real-time based on the received user input corresponding to at
least one network failure event;
10 storing, by a storing unit [306] via a secured Application Programming
Interface (API), the modified template at a database [314];
generating, by a generating unit [308], an SDR based on the stored template; and
transmitting, by a transmitting unit [310], the generated SDR to a probing
15 engine for failure analysis.
2. The method as claimed in claim 1, wherein modifying the at least one template
further comprises at least one of adding and removing at least one attribute of the set
of attributes from the at least one template.
3. The method as claimed in claim 1, wherein the method comprises enabling, by a
20 processing unit [312], storing of the modified template without interrupting NEF's
[118] ongoing operations.
4. The method as claimed in claim 1, wherein the set of attributes comprises subscriber
identifiers and monitoring types associated with one or more network call flows.
5. The method as claimed in claim 1, wherein the NEF [118] operates as part of an
25 overall 5G network architecture interfacing with User Data Management (UDM),
Access and Mobility Management Function (AMF), Session Management Function (SMF), and Network Repository Function (NRF) components.
6. The method as claimed in claim 1, wherein the at least one template comprises a
plurality of attributes corresponding to a set of network failures.
30 7. A system for dynamically provisioning Streaming Data Record (SDR) information,
the system comprising:
29

a display Unit [302] configured to provide at least one template associated with a network exposure function (NEF) [118] to a user to receive a user input corresponding to the at least one template;
a modifying unit [304] configured to modify a set of attributes associated with
5 the at least one template in real-time based on the received user input corresponding
to at least one network failure event;
a storing unit [306] configured to store via a secured Application Programming Interface (API), the modified template at a database [314];
a generating unit [308] configured to generate an SDR based on the stored
10 template; and
a transmitting unit [310] configured to transmit the generated SDR to a probing engine for failure analysis.
8. The system as claimed in claim 7, wherein the modification of the at least one
template further comprises at least one of adding and removing at least one attribute
15 of the set of attributes from the at least one template.
9. The system as claimed in claim 7, wherein the system further comprises a processing
unit [312] configured to enable storing of the modified template without interrupting
NEF's [118] ongoing operations.
10. The system as claimed in claim 7, wherein the set of attributes comprises subscriber
20 identifiers and monitoring types associated with one or more network call flows.
11. The system as claimed in claim 7, wherein the NEF [118] operates as part of an
overall 5G network architecture interfacing with User Data Management (UDM),
Access and Mobility Management Function (AMF), Session Management Function
(SMF), and Network Repository Function (NRF) components.
25 12. The system as claimed in claim 7, wherein the at least one template comprises a
plurality of attributes corresponding to a set of network failures.
13. A user equipment (UE) comprising:
a processor configured to:
display at least one template associated with a network exposure
30 function (NEF) [118] to a user to receive a user input corresponding to the at
least one template; and
30

modify a set of attributes associated with the at least one template in
real-time based on the received user input corresponding to at least one
network failure event, wherein a Streaming Data Record (SDR) is generated
based on the modified set of attributes associated with the at least one
5 template, and wherein the generated SDR is transmitted to a probing engine
for failure analysis.
14. The UE as claimed in claim 13, wherein the SDR is generated based on performing
of steps of method claim 1. 10