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 MANAGING NETWORK ERRORS OCCURRED AT A NWDAF MODULE”
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 MANAGING NETWORK ERRORS OCCURRED AT A NWDAF MODULE
TECHNICAL FIELD
[0001] 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 managing one or more network errors occurred at a Network Data Analytics Function (NWDAF) module.
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 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] Network Data Analytics Function (NWDAF) (implemented by a server) is a 5G node which serves other node function requests for use case analytics of said other node function. While providing use case analytics for a node function, errors may occur within the NWDAF or while interfacing with other microservices, thereby disrupting the call flow. Disruption of call flow ultimately leads to the NWDAF failing to provide the required response to the node function, which had requested a use case analysis from the NWDAF. Some exemplary reasons for errors are connectivity failure, insufficient memory in database (DB), invalid request from the node function and so on.
[0004] In conventional approaches, alarms are raised, and counters are maintained to monitor errors occurring within and outside the NWDAF. In such approaches, no

automated actions are taken to troubleshoot the error. Moreover, in conventional approaches, network operations team would be required to implement corrective measures manually with the help of a developer. In conventional approaches, a network operator and/or developer is required to manually login to a deployment server and go through logs to ascertain the issue occurred. Furthermore, a determination of exact reason for the error is also done manually. Such an approach is naturally inefficient, time-consuming, resource intensive and not optimal.
[0005] Thus, there exists an imperative need in the art to provide a solution for error managing via a probing platform module, which the present disclosure aims to address.
SUMMARY
[0006] 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.
[0007] An aspect of the present disclosure may relate to a method for managing one or more network errors occurred at a Network Data Analytics Function (NWDAF) module. The method comprises receiving, by a transceiver unit at a probing module from the network data analytics function (NWDAF) module, a clear code data comprising a set of details related to the one or more network errors occurred at the NWDAF module. The method further comprises decoding, by a decoding unit at the probing platform module, the clear code data. The method further comprises analysing, by an analysis unit at the probing platform module, the decoded clear code data to identify a historical code data parameter, wherein the historical code data parameter indicates a number of occurrences of the clear code data in a historical data. The method further comprises detecting, by a detection unit at the probing platform module, a first condition based on the historical code data

parameter and a predefined threshold. The method further comprises sending, by the transceiver unit at the probing module to one of a network function (NF) module and the NWDAF module, a correction indication based on the detection of the first condition, for correcting the one or more network errors.
[0008] In an exemplary aspect of the present disclosure, the method further comprises receiving, by the NWDAF module, a request from the NF module, the request is related to managing the one or more network errors in an information received from the NF module. The method further comprises detecting, by the NWDAF module, an error related to the request received from the NF module. The method further comprises sending, by the NWDAF module, the clear code data to the probing platform module, wherein the clear code data comprises the set of details related to the one or more network errors.
[0009] In an exemplary aspect of the present disclosure, the method further comprises correcting, by the one of the NF module and the NWDAF module, the one or more network errors, based on the correction indication received from the probing platform module.
[0010] In an exemplary aspect of the present disclosure, the clear code data comprises a set of 31 digits.
[0011] In an exemplary aspect of the present disclosure, the set of 31 digits comprises one or more of a first pre-defined set of digits, a second pre-defined set of digits, a third pre-defined set of digits, a fourth pre-defined set of digits, a fifth pre-defined set of digits, a sixth pre-defined set of digits, a seventh pre-defined set of digits, an eighth pre-defined set of digits, a ninth pre-defined set of digits, and a tenth pre-defined set of digits. The first pre-defined set of digits representing a result of a call flow, wherein the result of the call flow is one of a success, an internal failure, and an external failure. The second pre-defined set of digits representing a network procedure. The third pre-defined set of digits representing an ingress

interface on which the NF module receives a service operation. The fourth pre-defined set of digits representing an ingress service operation. The fifth pre-defined set of digits representing an ingress response code for the ingress service operation. The sixth pre-defined set of digits representing an egress interface on which NWDAF module sends request to other NF modules. The seventh pre-defined set of digits representing an egress service operation. The eighth pre-defined set of digits representing egress response code for the egress service operation. The ninth pre-defined set of digits representing a call flow name related to the clear code data. The tenth pre-defined set of digits representing an error code related to an error among the one or more errors.
[0012] Another aspect of the present disclosure may relate to a system for managing one or more network errors occurred at a Network Data Analytics Function (NWDAF) module. The system comprises a transceiver unit, a decoding unit, an analysis unit, and a detection unit. Further, the transceiver unit is configured to receive, at a probing module from the network data analytics function (NWDAF) module, a clear code data comprising a set of details related to the one or more network errors occurred at the NWDAF module. Further, the decoding unit is configured to decode the clear code data at the probing platform module. Further, the analysis unit is configured to analyse the decoded clear code data at the probing module to identify a historical code data parameter, wherein the historical code data parameter indicates a number of occurrences of the clear code data in a historical data. Further, the detection unit is configured to detect a first condition at the probing module based on the historical code data parameter and a predefined threshold. Thereafter, the transceiver unit is further configured to send, at the probing platform, to one of a network function (NF) module and the NWDAF module, a correction indication based on the detection of the first condition, for correcting the one or more network errors.
[0013] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for managing one or more

network errors occurred at a Network Data Analytics Function (NWDAF) module, the instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit at a probing module to receive, from the network data analytics function (NWDAF) module, a clear code data comprising a set of details related to the one or more network errors occurred at the NWDAF module. The executable code when executed causes a decoding unit at the probing module to decode the clear code data. The executable code when executed causes an analysis unit at the probing module to analyse the decoded clear code data to identify a historical code data parameter, wherein the historical code data parameter indicates a number of occurrences of the clear code data in a historical data. The executable code when executed causes a detection unit at the probing module to detect a first condition based on the historical code data parameter and a predefined threshold. The executable code when executed causes the transceiver unit at the probing module to send to one of a network function (NF) module and the NWDAF module, a correction indication based on the detection of the first condition, for correcting the one or more network errors.
OBJECTS OF THE DISCLOSURE
[0014] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0015] It is an object of the present disclosure to provide a system and a method for managing the one or more network errors occurred at a Network Data Analytics Function (NWDAF) module.
[0016] It is an object of the present disclosure to provide a system and a method for error managing via a probing platform module.

[0017] It is another object of the present disclosure to provide a solution that obviates need for a user/developer to manually determine and troubleshoot an error by manually analysing logs of a deployment server.
[0018] It is yet another object of the present disclosure to provide a solution that determines exact reason for occurrence of an error.
[0019] It is yet another object of the present disclosure to provide a solution that enables automatic resolution of cause behind an error.
DESCRIPTION OF THE DRAWINGS
[0020] 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.
[0021] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture.
[0022] 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.

[0023] FIG. 3 illustrates an exemplary block diagram of a system for managing one or more network errors occurred at a Network Data Analytics Function (NWDAF) module, in accordance with exemplary implementations of the present disclosure.
[0024] FIG. 4 illustrates a method flow diagram for managing one or more network errors occurred at a Network Data Analytics Function (NWDAF) module in accordance with exemplary implementations of the present disclosure.
[0025] FIG. 5 illustrates an exemplary block diagram representation of a system architecture for managing one or more network errors occurred at a Network Data Analytics Function (NWDAF) module, in accordance with exemplary implementation of the present disclosure.
[0026] FIG. 6, a flow diagram an exemplary method for managing one or more network errors occurred at a Network Data Analytics Function (NWDAF) module, in accordance with exemplary implementations of the present disclosure.
[0027] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
[0028] 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.

[0029] 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.
5 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.
[0030] Specific details are given in the following description to provide a thorough
10 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. 15
[0031] 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
20 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.
[0032] The word “exemplary” and/or “demonstrative” is used herein to mean
25 serving as an example, instance, or illustration. For the avoidance of doubt, the
subject matter disclosed herein is not limited by such examples. In addition, any
aspect or design described herein as “exemplary” and/or “demonstrative” is not
necessarily to be construed as preferred or advantageous over other aspects or
designs, nor is it meant to preclude equivalent exemplary structures and techniques
30 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
9

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.
5 [0033] 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 conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a Digital
10 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 working of the system according to the present disclosure. More specifically, the processor or
15 processing unit is a hardware processor.
[0034] 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
20 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 assistant, tablet computer, wearable device or any other computing device which is capable
25 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 unit(s) which are required to implement the features of the present disclosure.
[0035] As used herein, “storage unit” or “memory unit” refers to a machine or
30 computer-readable medium including any mechanism for storing information in a
form readable by a computer or similar machine. For example, a computer-readable
10

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 of the system to perform their respective
5 functions.
[0036] 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
10 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.
[0037] All modules, units, components used herein, unless explicitly excluded
15 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 Programmable Gate Array
20 circuits (FPGA), any other type of integrated circuits, etc.
[0038] 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
25 and/or connected with the system.
[0039] As discussed in the background section, the current known solutions have
several shortcomings. The present disclosure aims to overcome the above-
mentioned and other existing problems in this field of technology by providing
30 method and system for managing one or more network errors occurred at a Network
Data Analytics Function (NWDAF) module. The present disclosure provides a
11

novel solution for monitoring network errors based on clear codes. Further, the novel solution as disclosed herein analyses a history of occurrence of network errors by analysing a decoded clear code. Furthermore, if the history of occurrence of network errors are high, then an indication for correction of such errors is sent. 5
[0040] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (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
10 (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 Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a
15 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], and a data network (DN) [130], wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing the features of the present disclosure.
20
[0041] 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 different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable
25 wireless communication.
[0042] Access and Mobility Management Function (AMF) [106] is a 5G core
network function responsible for managing access and mobility aspects, such as UE
registration, connection, and reachability. It also handles mobility management
30 procedures like handovers and paging.
12

[0043] Session Management Function (SMF) [108] is a 5G core network function responsible for managing session-related aspects, such as establishing, modifying, and releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement. 5
[0044] 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 and efficient messaging service. It acts as a mediator for service-based interfaces. 10
[0045] 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.
15 [0046] 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.
20 [0047] 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.
[0048] Network Exposure Function (NEF) [118] is a network function that exposes
25 capabilities and services of the 5G network to external applications, enabling
integration with third-party services and applications.
[0049] Network Repository Function (NRF) [120] is a network function that acts
as a central repository for information about available network functions and
30 services. It facilitates the discovery and dynamic registration of network functions.
13

[0050] 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.
5 [0051] Unified Data Management (UDM) [124] is a network function that
centralizes the management of subscriber data, including authentication, authorization, and subscription information.
[0052] Application Function (AF) [126] is a network function that represents
10 external applications interfacing with the 5G core network to access network
capabilities and services.
[0053] User Plane Function (UPF) [128] is a network function responsible for
handling user data traffic, including packet routing, forwarding, and QoS
15 enforcement.
[0054] 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.
20
[0055] FIG. 2 illustrates an exemplary block diagram of a computing device [200] 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 [200] may also implement a method for
25 managing one or more network errors occurred at a Network Data Analytics
Function (NWDAF) module [302] utilising the system [300]. In another implementation, the computing device [200] itself implements the method for managing the one or more network errors occurred at the Network Data Analytics Function (NWDAF) module [302] using one or more units configured within the
30 computing device [200], wherein said one or more units are capable of
implementing the features as disclosed in the present disclosure.
14

[0056] The computing device [200] may include a bus [202] or other
communication mechanism for communicating information, and a processor [204]
coupled with the bus [202] for processing information. The processor [204] may
5 be, for example, a general-purpose microprocessor. The computing device [200]
may also include a main memory [206], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [202] for storing information and instructions to be executed by the processor [204]. The main memory [206] also may be used for storing temporary variables or other intermediate information
10 during execution of the instructions to be executed by the processor [204]. Such
instructions, when stored in non-transitory storage media accessible to the processor [204], render the computing device [200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [200] further includes a read only memory (ROM) [208] or other static
15 storage device coupled to the bus [202] for storing static information and
instructions for the processor [204].
[0057] A storage device [210], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [202] for storing information and
20 instructions. The computing device [200] may be coupled via the bus [202] to a
display [212], 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 [214], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the
25 bus [202] for communicating information and command selections to the processor
[204]. Another type of user input device may be a cursor controller [216], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [204], and for controlling cursor movement on the display [212]. This input device typically has two degrees
30 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.
15

[0058] The computing device [200] 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 [200] causes
5 or programs the computing device [200] to be a special-purpose machine.
According to one implementation, the techniques herein are performed by the computing device [200] in response to the processor [204] executing one or more sequences of one or more instructions contained in the main memory [206]. Such instructions may be read into the main memory [206] from another storage medium,
10 such as the storage device [210]. Execution of the sequences of instructions
contained in the main memory [206] causes the processor [204] 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.
15
[0059] The computing device [200] also may include a communication interface [218] coupled to the bus [202]. The communication interface [218] provides a two-way data communication coupling to a network link [220] that is connected to a local network [222]. For example, the communication interface [218] may be an
20 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, the communication interface [218] 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
25 implementation, the communication interface [218] sends and receives electrical,
electromagnetic or optical signals that carry digital data streams representing various types of information.
[0060] The computing device [200] can send messages and receive data, including
30 program code, through the network(s), the network link [220] and the
communication interface [218]. In the Internet example, a server [230] might
16

transmit a requested code for an application program through the Internet [228], the
ISP [226], the local network [222], the host [224] and the communication interface
[218]. The received code may be executed by the processor [204] as it is received,
and/or stored in the storage device [210], or other non-volatile storage for later
5 execution.
[0061] Referring to FIG. 3, an exemplary block diagram of a system [300] for managing one or more network errors occurred at a Network Data Analytics Function (NWDAF) module [302], is shown, in accordance with the exemplary
10 implementations of the present disclosure. The system [300] may comprise at least
one transceiver unit [306], at least one decoding unit [308], at least one analysis unit [310], at least one detection unit [312], and at least one storage unit [316]. 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
15 within the system [300] 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 required to implement the features of the present disclosure. Further, in an implementation, the system [300] may be present in a user device/ user equipment
20 [102] to implement the features of the present disclosure. The system [300] may be
a part of the user device [102]/ or may be independent of but in communication with the user device [102] (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 implementation, the system [300] may reside partly in the server/ network
25 entity and partly in the user device.
[0062] The system [300] is configured for managing the one or more network errors occurred at the Network Data Analytics Function (NWDAF) module [302], with the help of the interconnection between the components/units of the system [300]. 30
17

[0063] Further, the NWDAF module [302] is a component that performs collection
of data from various other core network functions, application functions, as well as
operations, administration, and management (OAM) systems, and operational
support systems. The one or more network errors are the errors and issues caused
5 within the telecommunication network. The one or more network errors may
include connectivity failure, insufficient memory in database, invalid request from a consumer, etc.
10 [0064] Further, the transceiver unit [306], at a probing module [304], is configured
to receive, from the network data analytics function (NWDAF) module [302], a clear code data comprising a set of details related to the one or more network errors occurred at the NWDAF module [302]. The clear code data may refer to a set of digits. The clear code comprises the details regarding the exact location of the error,
15 a type of error, and an information associated with a network function that is being
used, and other various details. The clear code data comprises a set of 31 digits. The 31-digit clear code provides an extensive insight as to why the NWDAF module [302] is unable to serve the requests from consumer.
20 [0065] The set of 31 digits comprises one or more of a first pre-defined set of digits,
a second pre-defined set of digits, a third pre-defined set of digits, a fourth pre-defined set of digits, a fifth pre-defined set of digits, a sixth pre-defined set of digits, a seventh pre-defined set of digits, an eighth pre-defined set of digits, a ninth pre¬defined set of digits, and a tenth pre-defined set of digits.
25
[0066] The first pre-defined set of digits represents a result of the call flow, wherein the result of the call flow is one of a success, an internal failure, and an external failure. Further, the call flow may refer to a result of a particular network procedure such as a call setup and release procedure, a data transfer procedure, a handover
30 procedure, a location procedure, and any other such like procedure that may be
appreciated by a person skilled in the art. The result of the call flow is determined
18

as the success when there is no network error caused during the call flow. The result
of the call flow is determined as the internal failure when the network error caused
due to an internal error such as an issue with an application code or a software.
Further, the external failure of the call flow is determined when the network error
5 is caused due to hardware problems outside the software or application such as
database error.
[0067] The second pre-defined set of digits represents a network procedure such as
a registration of network functions. Further, the network procedure may be a call
10 setup and release procedure, a data transfer procedure, a handover procedure, a
location procedure, and any other such like procedure that may be appreciated by a person skilled in the art.
[0068] The third pre-defined set of digits representing an ingress interface on which
15 the NF module [314] receives a service operation. The ingress interface is the
interface which is used for receiving the data at the NWDAF module [302] associated with the service operation. The service operation is associated with the network procedure. For example, the ingress interface may be a RESTful API used for collection of data.
20
[0069] The fourth pre-defined set of digits representing an ingress service operation. For example, the fourth pre-defined set of digits “444” may represents the ingress service operation i.e., the collection of data from different network functions at the ingress interface.
25
[0070] Further, as used herein, the “ingress service operation” may refer to a process of managing and controlling incoming traffic from a user device or an application to a network and/or service. Further, the ingress service operation may include authentication and authorization of incoming requests, policy enforcement
30 and charging control, a network traffic management and prioritization, a routing
and forwarding of incoming traffic to an appropriate network and/or service.
19

[0071] The fifth pre-defined set of digits representing an ingress response code for
the ingress service operation. For example, the fifth pre-defined set of digits “5555”
5 may represent the ingress response code for the ingress service operation such as a
collection of data. Wherein the ingress response code “5555” may indicate that the collection of data was unsuccessful.
[0072] The sixth pre-defined set of digits representing an egress interface on which
10 NWDAF module [302] sends request to other NF modules [314]. The egress
interface is the interface which is used for sending the data from the NWDAF
module [302] associated with the service operation to other NF modules [314]. The
service operation is associated with the network procedure. For example, the egress
interface may be a RESTful API used for sending the analytics. Further, the sixth
15 pre-defined set of digits may represent an existence of an anomaly while sending
request from the NWDAF module [302] to other NF modules [314], such as “666” may represent that there is a failure while sending request i.e., the anomaly.
[0073] As used herein, the “RESTful API” may refer to an application
20 programming interface that uses the REST (Representational State of Resource)
architecture to manage and interact with network devices, services, and/or
resources. Further, the RESTful API may perform network management tasks, such
as configuring network devices and services, monitoring network performance and
faults, managing network security and access control, provisioning and deploying
25 network services, retrieving network topology and inventory information, and alike.
[0074] The seventh pre-defined set of digits representing an egress service
operation. For example, the seventh pre-defined set of digits may represent that the
egress service operation may be a prediction of the anomaly within the network.
30 Further, as used herein the “egress service operation” may refer to a process of
managing and controlling outgoing traffic from a network. Further, the egress
20

service operation may comprise a series of procedures and protocols that ensure the
secure, efficient, and reliable transmission of data packets from within the network.
Furthermore, the egress service operation may encompass various functions,
including traffic management, a traffic prioritization, an outgoing traffic policy
5 management, a routing and forwarding of the outgoing traffic.
[0075] The eighth pre-defined set of digits representing egress response code for
the egress service operation. For example, the eighth pre-defined set of digits
“8888” may represent that the egress response code for egress service operation,
10 wherein the egress response code 8888” may indicate that the sent request was not
delivered to other NF modules [314].
[0076] The ninth pre-defined set of digits representing a call flow name related to
the clear code data. The call flow name may be such as an uplink and a downlink,
15 or one or more events associated with registration of the network function.
[0077] Further, the ninth pre-defined set of digits may represent an uplink such as
Registration_Uplink that initiates from a corresponding network function to send a
registration request to the network, denoted as "NF_Register_Request". Upon
20 receipt, the network responds with an acknowledgement, a NF_Register_Ack that
confirms the request has been received, and any other such like requests.
[0078] Further, the ninth pre-defined set of digits may represent a downlink such
as Registration_Downlink wherein with the network function initiates a
25 deregistration request, a NF_Deregister_Request to a process to disengage from the
network, a NF_Deregister_Ack to affirm that the NF_Deregister_Request has been processed, and any other such like requests.
[0079] Furthermore, the ninth pre-defined set of digits may represent an event
30 associated with registration of the network function such as a NF_Config_Push
event wherein the network pushes essential configuration data to the network
21

function, a NF_Config_Ack event wherein the network function subsequently acknowledges the receipt of this data with the event in order to complete the uplink registration process, and any other such like events.
5 [0080] The tenth pre-defined set of digits representing an error code related to an
error among the one or more errors. For example, the error code “123” may indicate that the registration of the network function is unsuccessful.
[0081] After the clear code data is received, the decoding unit [308] is configured
10 to decode the clear code data at the probing module [304]. For example, once the
clear code data is received, the decoding unit [308] may decode the encoded
information associated with the clear code data. Further, the decoding unit [308]
may decode the clear code data at the probing module [304], by utilising a
predefined decoding technique such as rule based decoding technique, a set of digit
15 based decoding technique and any other such like technique that may be appreciated
by a person skilled in the art to implement the solution of the present disclosure.
Further, in an exemplary implementation in order to decode the clear code data the
decoding unit [308] may group the set of digits associated with the clear code data
in target sets of digits based on the predefined format as discussed above.
20 Thereafter, the decoding unit [308] may compare each target sets of digits with a
prestored code data parameter to determine the error code related to an error among
the one or more errors.
[0082] Once, the clear code is decoded, the analysis unit [310] is configured to
25 analyse the decoded clear code data at the probing module [304] to identify a
historical code data parameter, wherein the historical code data parameter indicates
a number of occurrences of the clear code data in a historical data. The historical
code parameter is a parameter showing the frequency of occurrence of the clear
code data in the historical data based on a comparison between received clear code
30 data and the historical data. The historical data refers to the data associated with the
22

clear codes that are collected in the past or the data that is previously received from the NWDAF module [302].
[0083] After, the analysis of the decoded clear code, the detection unit [312]
5 configured to detect a first condition at the probing module [304] based on the
historical code data parameter and a predefined threshold. The first condition refers
to the condition when the clear code has been received for more than a predefined
number of times i.e., predefined threshold. The predefined number of times can be
determined based on the requirements of the network entity or the service provider
10 of the telecommunication network.
[0084] Once, the first condition is detected, the transceiver unit [306] at the probing module [304] is further configured to send to one of a network function (NF) module [314] and the NWDAF module [302], a correction indication based on the
15 detection of the first condition, for correcting the one or more network errors. The
NF module [314] may performs one or more tasks associated with particular network function. The correction indication may be an indication to rectify the one or more network errors, by utilising a corrective measure associated with the one or more network errors. Further, the user may be notified to rectify the one or more
20 network errors. The correction indication may also indicate an appropriate
corrective measure associated with the one or more network errors such as a close action loop, etc.
[0085] Further, in an implementation of the present disclosure the NWDAF module
25 [302] is further configured to receive a request from the NF module [314], the
request is related to managing the one or more network errors in an information
received from the NF module [314]. Further, in said implementation, the NWDAF
module [302] is configured to detect an error related to the request received from
the NF module [314]. Furthermore, the NWDAF module [302] is configured to
30 send the clear code data to the probing module [304], wherein the clear code data
comprises the set of details related to the one or more network errors. The set of
23

details refers to the details associated with the one or more network errors. For example, the set of details may be the network functions at which the one or more network errors are occurring, the type of network errors that are occurring, and other such details as may be obvious to the person skilled in the art. 5
[0086] The present disclosure further discloses that the NF module [314] and the NWDAF module [302] are configured to correct the one or more network errors, based on the correction indication received from the probing module [304].
10 [0087] Referring to FIG. 4, an exemplary method flow diagram [400] for managing
one or more network errors occurred at a Network Data Analytics Function (NWDAF) module [302], 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
15 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].
[0088] Next, at step [404], the method [400] comprises receiving, by a transceiver unit [306] at a probing module [304] from the network data analytics function
20 (NWDAF) module [302], a clear code data comprising a set of details related to the
one or more network errors occurred at the NWDAF module [302]. The clear code data may refer to a set of digits. The clear code comprises the details regarding the exact location of the error, a type of error, and an information associated with a network function that is being used, and other various details. The clear code data
25 comprises a set of 31 digits. The 31-digit clear code provides an extensive insight
as to why the NWDAF module [302] is unable to serve the requests from consumer.
[0089] The set of 31 digits comprises one or more of a first pre-defined set of digits,
a second pre-defined set of digits, a third pre-defined set of digits, a fourth pre-
30 defined set of digits, a fifth pre-defined set of digits, a sixth pre-defined set of digits,
24

a seventh pre-defined set of digits, an eighth pre-defined set of digits, a ninth pre-defined set of digits, and a tenth pre-defined set of digits.
[0090] The first pre-defined set of digits represents a result of the call flow, wherein
5 the result of the call flow is one of a success, an internal failure, and an external
failure. The result of the call flow is determined as the success when there is no
network error caused during the call flow. The result of the call flow is determined
as the internal failure when the network error caused due to an internal error such
as an issue with an application code or a software. Further, the external failure of
10 the call flow is determined when the network error is caused due to hardware
problems outside the software or application such as database error.
[0091] The second pre-defined set of digits represents a network procedure such as a registration of network functions.
15
[0092] The third pre-defined set of digits representing an ingress interface on which the NF module [314] receives a service operation. The ingress interface is the interface which is used for receiving the data at the NWDAF module [302] associated with the service operation. The service operation is associated with the
20 network procedure. For example, the ingress interface may be a RESTful API used
for collection of data.
[0093] The fourth pre-defined set of digits representing an ingress service
operation. For example, the fourth pre-defined set of digits “444” may represents
25 the ingress service operation “the collection of data from different network
functions” at the ingress interface.
[0094] The fifth pre-defined set of digits representing an ingress response code for
the ingress service operation. For example, the fifth pre-defined set of digits “5555”
30 may represent the ingress response code for the ingress service operation such as a
25

collection of data. Wherein the ingress response code “5555” may indicate that the collection of data was unsuccessful.
[0095] The sixth pre-defined set of digits representing an egress interface on which
5 NWDAF module [302] sends request to other NF modules [314]. The egress
interface is the interface which is used for sending the data from the NWDAF
module [302] associated with the service operation to other NF modules [314]. The
service operation is associated with the network procedure. For example, the egress
interface may be a RESTful API used for sending the analytics. Further, the sixth
10 pre-defined set of digits may represent an existence of an anomaly while sending
request from the NWDAF module [302] to other NF modules [314], such as “666” may represent that there is a failure while sending request i.e., the anomaly.
[0096] The seventh pre-defined set of digits representing an egress service
15 operation. For example, the seventh pre-defined set of digits may represent that the
egress service operation may be a prediction of the anomaly within the network.
[0097] The eighth pre-defined set of digits representing egress response code for
the egress service operation. For example, the eighth pre-defined set of digits
20 “8888” may represent that the egress response code for egress service operation,
wherein the egress response code 8888” may indicate that the sent request was not delivered to other NF modules [314].
[0098] The ninth pre-defined set of digits representing a call flow name related to
25 the clear code data. The call flow name may be such as an uplink and a downlink,
or one or more events associated with registration of the network function.
[0099] The tenth pre-defined set of digits representing an error code related to an
error among the one or more errors. For example, the error code “123” may indicate
30 that the registration of the network function is unsuccessful.
26

[0100] After the clear code data is received, then at step [406], the method [400] comprises decoding, by a decoding unit [308] at the probing module [304], the clear code data.
5 [0101] Once, the clear code has been decoded, then at step [408], the method [400]
comprises analysing, by an analysis unit [310] at the probing module [304], the
decoded clear code data to identify a historical code data parameter, wherein the
historical code data parameter indicates a number of occurrences of the clear code
data in a historical data. The historical code parameter is a parameter showing the
10 frequency of occurrence of the clear code data in the historical data based on a
comparison between received clear code data and the historical data. The historical data refers to the data associated with the clear codes that are collected in the past or the data that is previously received from the NWDAF module [302].
15 [0102] After, the analysis of the decoded clear code, then at step [410], the method
[400] comprises detecting, by a detection unit [312] at the probing module [304], a first condition based on the historical code data parameter and a predefined threshold. The first condition refers to the condition when the clear code has been received for more than a predefined number of times i.e., the predefined threshold.
20 The predefined number of times can be determined based on the requirements of
the network entity or the service provider of the telecommunication network.
[0103] Once, the first condition is detected, thereafter, at step [412], the method [400] comprises sending, by the transceiver unit [306] at the probing module [304]
25 to one of a network function (NF) module [314] and the NWDAF module [302], a
correction indication based on the detection of the first condition, for correcting the one or more network errors. The NF module [314] may perform one or more tasks associated with particular network function. The correction indication may be an indication to rectify the one or more network errors, by utilising a corrective
30 measure associated with the one or more network errors. Further, the user may be
notified to rectify the one or more network errors. The correction indication may
27

also indicate an appropriate corrective measure associated with the one or more network errors such as a close action loop, etc.
[0104] The present disclosure further discloses that in an implementation, the
5 method [400] may also further comprise receiving, by the NWDAF module [302],
a request from the NF module [314], the request is related to managing the one or more network errors in an information received from the NF module [314]. Further, in said implementation, the method [400] further comprises detecting, by the NWDAF module [302], an error related to the request received from the NF module
10 [314]. Thereafter, the method [400] further comprises sending, by the NWDAF
module [302], the clear code data to the probing module [304], wherein the clear code data comprises the set of details related to the one or more network errors. The set of details refers to the details associated with the one or more network errors. For example, the set of details may be the network functions at which the one or
15 more network errors are occurring, the type of network errors that are occurring,
and other such details as may be obvious to the person skilled in the art.
[0105] The present disclosure further discloses that the method [400] may also
further comprise correcting, by the one of the NF module [314] and the NWDAF
20 module [302], the one or more network errors, based on the correction indication
received from the probing module [304].
[0106] Thereafter, at step [414], the method [400] is terminated.
25 [0107] Referring to FIG. 5, an exemplary block diagram representation of a system
architecture [500] for managing one or more network errors occurred at a Network Data Analytics Function (NWDAF) module [302], in accordance with exemplary implementation of the present disclosure is shown. As shown in FIG. 5, the system architecture [500] includes a data consumer [502], a network data analytics function
30 (NWDAF) module [302], a network function (NF) module [314], a probing module
[304], a database [508], a Network Function (NF) module [314], and a network data
28

analytics function user interface (NWDAF UI) [512], wherein all the 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.
5 [0108] As used herein, the data consumer [502] may refer to an end consumer of
the data provided by the NWDAF module [302].
[0109] As used herein, the NWDAF module [302] is a module responsible for
collecting data from user equipment, network functions, and operations,
10 administration, and maintenance (OAM) systems, etc. from telecommunication
networks that can be used for analytics.
[0110] As used herein, the NF module [314] may refer to an entity that may be
associated with a core network function of the network from which data is collected
15 for performing analysis on the collected data.
[0111] As used herein, the probing module [304] (or one or more probing units)
may refer to a component which is responsible for monitoring and analysing the
network activity and may also perform preventive actions based on the analysis and
20 monitoring of the network entity. The probing module [304] may be one or more
probing solutions. The one or more probing solutions refers to an agent which collects core network data from the network and/or radio access networks.
[0112] As used herein, the database [508] may refer to a repository or a storage
25 device used for storing data within the telecommunications network.
[0113] As used herein, the sub-system [510] may refer to a component associated
with the NWDAF module [302] used for providing analytical functions associated
with the data consumer [502]. The sub-system [510] may also be a trained machine
30 learning based model.
29

[0114] As used herein, the network data analytics function user interface (NWDAF UI) [512] may refer to an interface used for communicating with the network data analytics function (NWDAF) module [302] within the network.
5 [0115] The NWDAF module [302] communicates with the NF [504] for collecting
the information related to the data consumers [502]. The NWDAF module [302] also communicates with the probing module [304] for collecting the data associated with the core network, and for collecting the data associated with a radio access network (RAN) [104]. The NWDAF module [302] also communicates with the
10 database [508] for inserting and receiving the data. The NWDAF module [302] then
communicates with the sub-system [510] for predicting exception trends and transfers the received information. The exception trends may be associated with a trend or a pattern for exceptions from a network exposure function. This exception trends and received information is used for training and retraining of the sub-system
15 [510]. The data consumer [502] and the NWDAF module [302] communicates with
each other to provide subscribed abnormal behaviour analytics. The data consumer [502] also communicates with the NWDAF UI [512] for closed loop reporting in case of a high data traffic. The data consumer [502] also communicates with the sub-system [510] directly for closed loop forecasting to predict abnormal behaviour
20 trends and analytics. The NWDAF module [302] also communicates with the
NWDAF UI [512] for visualisation of prediction of the anomaly associated with the data consumer [502] between the communication of the data consumer [502] and the prediction of the trend. The closed loop reporting is a continuous feedback mechanism to monitor and adjust its operation based on the output or results, such
25 closed loop reporting allows to self-regulate and maintain stability or achieve a
desired outcome.
[0116] Referring to FIG. 6, illustrating a flow diagram an exemplary method [600]
for managing one or more network errors occurred at a Network Data Analytics
30 Function (NWDAF) module [302], in accordance with exemplary implementations
of the present disclosure. The method [600] starts at step [602], a data consumer
30

[502] sends a request to the NWDAF module [302]. The request may be a request for receiving an analytical data associated with the analysis performed by the NWDAF module [302].
[0117] Then at step [604], the method [600] comprises checking if the request received by the NWDAF module [302] is a valid request or not.
[0118] In an event, the request received by the NWDAF module [302] is the valid request the request is processed further at step [606]. Else, if the request is not a valid request, then at step [614], the request is processed, and a set of details are identified. In an implementation of the present disclosure, the set of details comprises a clear code data. The clear code data is a set of 31 digits. The set of details comprising the clear code data are related to the one or more network errors occurred at the NWDAF module [302].
[0119] Thereafter, at step [608], the method [600] comprises storing the processed request into a database [508].
[0120] After, the processed request is stored, then at step [610], the method [600] comprises checking if the processed request is valid, by decoding a data associated with the request.
[0121] Further, if the processed request is considered as valid request, then at step [618], the response from the NWDAF is sent to the data consumer [502].
[0122] However, if the processed request not a valid request that in that case at step [612] a clear code data due to the internal database error is transmitted to the probing module [304].
[0123] Further, in an event the clear code data from the step [614] and step [612] is received at the probing module [304]. The at step [616] the analysis of the received

clear code data is performed at the probing module [304] that leads to identification of the historical code parameter which indicates the number of occurrences of the clear code data in the historical data.
[0124] Thereafter, the method [600] terminates.
[0125] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for managing one or more network errors occurred at a Network Data Analytics Function (NWDAF) module [302], the instructions include executable code which, when executed by one or more units of a system [300], causes a transceiver unit [306] at a probing module [304] to receive, from the network data analytics function (NWDAF) module [302], a clear code data comprising a set of details related to the one or more network errors occurred at the NWDAF module [302]. The executable code when executed causes a decoding unit [308] at the probing module [304] to decode the clear code data; an analysis unit [310] at the probing module [304] to analyse the decoded clear code data to identify a historical code data parameter, wherein the historical code data parameter indicates a number of occurrences of the clear code data in a historical data. The executable code when executed causes a detection unit [312] at the probing module [304] to detect a first condition based on the historical code data parameter and a predefined threshold. The executable code when executed causes the transceiver unit [306] at the probing module [304] to send to one of a network function (NF) module [314] and the NWDAF module [302], a correction indication based on the detection of the first condition, for correcting the one or more network errors.
[0126] As is evident from the above, the present disclosure provides a technically advanced solution for managing one or more network errors that occurred at a Network Data Analytics Function (NWDAF) module. The present solution obviates the need for a user/developer to manually login to a deployment server and analyze logs to ascertain a cause behind an error, thereby reducing manual intervention. The system and the method disclosed by the present disclosure also helps in determining

exact reason as to why an error has occurred and enables automatic resolution of the cause behind the error. The method and the system disclosed by the present disclosure obviates the need of maintaining counters or monitoring alarms to track errors.
[0127] 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 those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
[0128] 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 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 considered to be encompassed within the scope of the present disclosure.

We Claim:
1. A method for managing one or more network errors occurred at a Network
Data Analytics Function (NWDAF) module [302], the method comprising:
- receiving, by a transceiver unit [306] at a probing module [304] from the network data analytics function (NWDAF) module [302], a clear code data comprising a set of details related to the one or more network errors occurred at the NWDAF module [302];
- decoding, by a decoding unit [308] at the probing module [304], the clear code data;
- analysing, by an analysis unit [310] at the probing module [304], the decoded clear code data to identify a historical code data parameter, wherein the historical code data parameter indicates a number of occurrences of the clear code data in a historical data;
- detecting, by a detection unit [312] at the probing module [304], a first condition based on the historical code data parameter and a predefined threshold; and
- sending, by the transceiver unit [306] at the probing module [304] to one of a network function (NF) module [314] and the NWDAF module [302], a correction indication based on the detection of the first condition, for correcting the one or more network errors.
2. The method as claimed in claim 1 further comprising:
- receiving, by the NWDAF module [302], a request from the NF module [314], the request is related to managing the one or more network errors in an information received from the NF module [314];
- detecting, by the NWDAF module [302], an error related to the request received from the NF module [314]; and
- sending, by the NWDAF module [302], the clear code data to the probing module [304], wherein the clear code data comprises the set of details related to the one or more network errors.

3. The method as claimed in claim 1 further comprising correcting, by the one of the NF module [314] and the NWDAF module [302], the one or more network errors, based on the correction indication received from the probing module [304].
4. The method as claimed in claim 1, wherein the clear code data comprises a set of 31 digits.
5. The method as claimed in claim 4, wherein the set of 31 digits comprises one or more of:

- a first pre-defined set of digits representing a result of a call flow, wherein the result of the call flow is one of a success, an internal failure, and an external failure;
- a second pre-defined set of digits representing a network procedure;
- a third pre-defined set of digits representing an ingress interface on which the NF module [314] receives a service operation;
- a fourth pre-defined set of digits representing an ingress service operation;
- a fifth pre-defined set of digits representing an ingress response code for the ingress service operation;
- a sixth pre-defined set of digits representing an egress interface on which NWDAF module [302] sends request to other NF modules [314];
- a seventh pre-defined set of digits representing an egress service operation;
- an eighth pre-defined set of digits representing egress response code for the egress service operation;
- a ninth pre-defined set of digits representing a call flow name related to the clear code data; and
- a tenth pre-defined set of digits representing an error code related to an error among the one or more errors.

6. A system [300] for managing one or more network errors occurred at a
Network Data Analytics Function (NWDAF) module [302], the system
comprising:
- a transceiver unit [306], at a probing module [304], configured to receive, from the network data analytics function (NWDAF) module [302], a clear code data comprising a set of details related to the one or more network errors occurred at the NWDAF module [302];
- a decoding unit [308] configured to decode the clear code data at the probing module [304];
- an analysis unit [310] configured to analyse the decoded clear code data at the probing module [304] to identify a historical code data parameter, wherein the historical code data parameter indicates a number of occurrences of the clear code data in a historical data; and
- a detection unit [312] configured to detect a first condition at the probing module [304] based on the historical code data parameter and a predefined threshold; and
wherein the transceiver unit [306] at the probing module [304] is further configured to send to one of a network function (NF) module [314] and the NWDAF module [302], a correction indication based on the detection of the first condition, for correcting the one or more network errors.
7. The system as claimed in claim 6, wherein the NWDAF module [302] is
further configured to:
- receive a request from the NF module [314], a request related to managing the one or more network errors in an information received from the NF module [314];
- detect an error related to the request received from the NF module [314]; and

- send the clear code data to the probing module [304], wherein the clear
code data comprises the set of details related to the one or more network
errors.
8. The system as claimed in claim 6, wherein the one of the NF module [314] and the NWDAF module [302], is configured to correct the one or more network errors, based on the correction indication received from the probing module [304].
9. The system as claimed in claim 6, wherein the clear code data comprises a set of 31 digits.
10. The system as claimed in claim 9, wherein the set of 31 digits comprises one or more of:

- a first pre-defined set of digits representing a result of a call flow, wherein the result of the call flow is one of a success, an internal failure, and an external failure;
- a second pre-defined set of digits representing a network procedure;
- a third pre-defined set of digits representing an ingress interface on which the NF module [314] receives a service operation;
- a fourth pre-defined set of digits representing an ingress service operation;
- a fifth pre-defined set of digits representing an ingress response code for the ingress service operation;
- a sixth pre-defined set of digits representing an egress interface on which NWDAF module [302] sends request to other NF modules [314];
- a seventh pre-defined set of digits representing an egress service operation;
- an eighth pre-defined set of digits representing egress response code for the egress service operation;

- a ninth pre-defined set of digits representing a call flow name related to the clear code data; and
- a tenth pre-defined set of digits representing an error code related to an error among the one or more errors.