FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
THE PATENTS RULES, 2003
COMPLETE
SPECIFICATION
(See section 10; rule 13)
TITLE OF THE INVENTION
SYSTEM AND METHOD FOR REPORTING LOAD INFORMATION TO NETWORK
FUNCTION
APPLICANT
JIO PLATFORMS LIMITED
of Office-101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad -
380006, Gujarat, India; Nationality : India
The following specification particularly describes
the invention and the manner in which
it is to be performed
2
RESERVATION OF RIGHTS
[0001] A portion of the disclosure of this patent document contains material,
which is subject to intellectual property rights such as but are not limited to,
copyright, design, trademark, integrated circuit (IC) layout design, and/or trade
5 dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates
(hereinafter referred as owner). The owner has no objection to the facsimile
reproduction by anyone of the patent document or the patent disclosure, as it
appears in the Patent and Trademark Office patent files or records, but otherwise
reserves all rights whatsoever. All rights to such intellectual property are fully
10 reserved by the owner.
FIELD OF INVENTION
[0002] The present disclosure generally relates to a wireless
telecommunications network. More particularly, the present disclosure relates to a
15 system and a method for reporting load information to a Network Function (NF).
DEFINITIONS
[0003] As used in the present disclosure, the following terms are generally
intended to have the meaning as set forth below, except to the extent that the context
20 in which they are used to indicate otherwise.
[0004] The term “network functions” as used herein, refers to the logical
entities or software-based functionalities that define how the network operates and
processes data. The network functions are used in the operation and management
of the network, ensuring that subscribers can reliably communicate and access
25 services while maintaining network efficiency and security.
[0005] The term “consumer network function” as used herein, refers to any
network function within the network environment that consumes services or
interacts with other network functions to provide end-to-end services to subscribers.
[0006] The term “Network Data Analytics Function (NWDAF)” as used
30 herein, refers to a functional entity responsible for collecting and analyzing network
data in real-time to provide insights and support various network management

functions. The NWDAF leverages data analytics to drive operational efficiencies,
enhance service quality, and enable dynamic network management capabilities. The
NWDAF helps in collecting and analyzing the network data to support the
deployment and enhancement of advanced network services and applications.
5 [0007] The term “Network Repository Function (NRF)” as used herein,
refers to a central repository and directory for managing and discovering network
functions and services within a 5G network. It plays a critical role in facilitating
service discovery, registration, and routing of network services across various
network slices and domains.
10 [0008] The term “Service Communication Proxy (SCP)” as used herein,
refers to an intermediary that manages and controls communication between
various components within the network.
[0009] The term “SCP instance” as used herein, refers to an instance that
serves the purpose of handling and enhancing communication between various
15 network elements. This includes managing traffic between user devices (e.g., user
equipments, smartphones, tablets, IoT devices) and backend network services (like
application servers, databases, billing systems, etc.).
[0010] The term “nfservicelist” as used herein, refers to a list of network
functions or services provided by a network. These services could include things
20 like voice calls, messaging, internet access, multimedia services, etc. Each service
would have associated network functions responsible for its delivery and
management.
[0011] The term “Subscription request for load data” as used herein, refers
to requesting ongoing access to real-time or historical data related to the
25 performance, usage, or metrics of network functions within a telecommunications
or network services environment.
[0012] The term “Public land mobile network (PLMN)” as used herein,
refers to a combination of wireless communication services offered by an operator
in a country. The PLMN is identified by a globally unique PLMN code, which
30 consists of a MCC (Mobile Country Code) and MNC (Mobile Network Code).
[0013] The term “Configured time interval/predefined time interval” as
4
used herein, refers to a predetermined time period for a purpose within a network
or a system.
[0014] The term “Subscription request” for load data as used herein, refers
to a process where a system or application requests ongoing updates or notifications
5 regarding changes in load or usage data.
[0015] The term “Discovery request” in networking as used herein, refers
to a message sent by a device or application on a network to discover and identify
other devices, services, or resources available within the network.
[0016] The term “Discovery response” in networking as used herein, refers
10 to a message sent by a network device or service in response to a discovery request.
The purpose of a discovery response is to provide information about the device or
service's capabilities, status, or presence on the network.
[0017] The term “Public Land Mobile Network (PLMN) identifier” as used
herein, refers to a unique code used to identify a mobile network operator (MNO)
15 within a country or region. It consists of two main components: the Mobile Country
Code (MCC) and the Mobile Network Code (MNC).
[0018] The term “NF instances endpoints" as used herein, refer to the
interfaces or access points through which these virtualized network functions
interact with other components of the network.
20 [0019] The term “NF instance IDs” refer to unique identifiers assigned to
individual instances of network functions deployed within the network.
[0020] The term “Load values" as used herein, refer to metrics or parameters
that indicate the current utilization, performance, or resource consumption of
individual NF instances deployed within the network.
25 [0021] The term “service status of a network function as used herein, refers
to its operational state and availability within the network.
[0022] The term “NF instance name" as used herein, refers to a name
assigned to an individual instance of the network function deployed within the
network.
30 [0023] The term “Network function type” as used herein, refers to types of
the network functions categorized based on their roles, responsibilities, and the

services they provide within the network.
BACKGROUND OF THE INVENTION
[0024] The following description of the related art is intended to provide
5 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 admission of the prior art.
10 [0025] Network Function (NF) load reporting may be performed by
Network Repository Function (NRF) which may then be used for NF load analytics
by a Network data analytics function (NWDAF). Each Service Communication
Proxy (SCP) instance may have to register with the NRF and send load information
in a request to the NRF. NWDAF may discover each instance of the registered SCP
15 and subscribe to the NRF for load information for all instances of SCP.
Consequently, the NWDAF may receive notification from the NRF for each
subscribed SCP instance. As a result, there is a significant increase in signalling
traffic between NRF-SCP and NWDAF-NRF, which may cause congestion.
[0026] There is, therefore, a need in the art to provide a system and method
20 to reduce huge traffic caused due to increased signalling between multiple network
nodes by mitigating the problems associated with the prior arts.
OBJECTS OF THE INVENTION
[0027] It is an object of the present disclosure to provide a system and a
25 method for reporting load information of one network function to another Network
Function (NF).
[0028] It is an object of the present disclosure to provide a system and a
method that includes a Network Repository Function (NRF) to provide load
information for Service Communication Proxy (SCP) instances in a single
30 notification to Network data analytics function (NWDAF) for a particular Public
Land Mobile Network (PLMN).
6
[0029] It is an object of the present disclosure to provide a system and a
method that includes NWDAF to discover multiple SCP instances, in a single
request, as a list from the NRF, and to subscribe the NRF for the discovered SCP
for load analytics.
5 [0030] It is an object of the present disclosure to provide a system and a
method that reduces notification traffic towards the NWDAF and consequently
towards a consumer NF. Therefore, resource utilization at NF end may be enhanced.
SUMMARY
10 [0031] In an exemplary embodiment, method for reporting load data in a
network is described. The method comprises receiving, by a network data analytics
function (NWDAF), a subscription request for load data of at least one network
function (NF) from a consumer network function (NF). The method further
comprises on receiving the subscription request, sending, by the NWDAF, a
15 discovery request for the at least one NF to a network repository function (NRF).
The method comprises in response to the discovery request, receiving, by the
NWDAF, a discovery response from the NRF. The discovery response comprises
comprising a list of a plurality of NF instances corresponding to the at least one NF.
The method comprises performing, by the NWDAF, a mapping for the received
20 plurality of NF instances corresponding to the at least one NF in the list. The method
further comprises subscribing, by the NWDAF, for load values corresponding to
the plurality of NF instances of the at least one NF in the mapping, to the NRF. The
method comprises receiving, by the NWDAF, a response from the NRF after a
predefined time period. The response comprises load values corresponding to the
25 plurality of NF instances of the at least one NF. The method comprises sending, by
the NWDAF, the response towards the consumer NF.
[0032] In some embodiments, the subscription request and the discovery
request comprise at least one public land mobile network (PLMN) identifier (ID)
corresponding to the at least one NF and a network function type.
30 [0033] In some embodiments, the at least one NF is a service
communication proxy (SCP).

[0034] In some embodiments, the list comprises NF instances endpoints, NF
instance IDs, NF instance names, NF service names, and NF service statuses.
[0035] In some embodiments, the NWDAF is configured to fetch the
plurality of NF instances of the at least one NF from the mapping.
5 [0036] In some embodiments, the load values are values corresponding to
load of the plurality of NF instances corresponding to the at least one PLMN ID of
the at least one NF.
[0037] In another exemplary embodiments, a system for reporting load data
in a network is described. The system comprises a network data analytics function
10 (NWDAF), a network function repository (NRF), a consumer network function
(NF), and a plurality of NFs. The NWDAF comprises a receiving unit configured
to receive a subscription request for load data of at least one network function (NF)
from the consumer NF. On receiving the subscription request, a sending unit is
configured to send a discovery request for the at least one NF to the NRF. In
15 response to the discovery request, the receiving unit is configured to receive a
discovery response from the NRF. The discovery response comprises comprising a
list of a plurality of NF instances corresponding to the at least one NF. A processing
unit is configured to perform a mapping for the received plurality of NF instances
corresponding to the at least one NF in the list. The processing unit is configured to
20 subscribe for load values corresponding to the plurality of NF instances of the at
least one NF in the mapping, to the NRF. The receiving unit is configured to receive
a response from the NRF after a predefined time period. The response comprises
load values corresponding to the plurality of NF instances of the at least one NF.
The sending unit is configured to send the response towards the consumer NF.
25 [0038] In some embodiments, the subscription request and the discovery
request comprise at least one public land mobile network (PLMN) identifier (ID)
corresponding to the at least one NF and a network function type.
[0039] In some embodiments, the at least one NF is a service
communication proxy (SCP).
30 [0040] In some embodiments, the list comprises NF instances endpoints, NF
instance IDs, NF instance names, NF service names, and NF service statuses.
8
[0041] In some embodiments, the processing unit is configured to fetch the
plurality of NF instances of the at least one NF from the mapping.
[0042] In some embodiments, the load values are values corresponding to
load of the plurality of NF instances corresponding to the at least one PLMN ID of
5 the at least one NF.
[0043] In some embodiments, a user equipment is communicatively
coupled with a system. The coupling comprises steps of receiving, by the system, a
connection request and sending, by the system, an acknowledgment of the
connection request to the UE. The coupling further comprises transmitting a
10 plurality of signals in response to the connection request. The system is configured
for performing load data reporting in a network.
[0044] The foregoing general description of the illustrative embodiments
and the following detailed description thereof are merely exemplary aspects of the
teachings of this disclosure, and are not restrictive.
15
BRIEF DESCRIPTION OF DRAWINGS
[0045] The accompanying drawings, which are incorporated herein, and
constitute a part of this disclosure, illustrate exemplary embodiments of the
disclosed methods and systems which like reference numerals refer to the same
20 parts throughout the different drawings. Components in the drawings are not
necessarily to scale, emphasis instead being placed upon clearly illustrating the
principles of the present disclosure. Some drawings may indicate the components
using block diagrams and may not represent the internal circuitry of each
component. It will be appreciated by those skilled in the art that disclosure of such
25 drawings includes the disclosure of electrical components, electronic components,
or circuitry commonly used to implement such components.
[0046] FIG. 1 illustrates an exemplary network architecture for
implementing a system, in accordance with an embodiment of the present
disclosure.
30 [0047] FIG. 2A illustrates an exemplary block diagram of the system, in
accordance with an embodiment of the present disclosure.

[0048] FIG. 2B illustrates an exemplary block diagram of a Network Data
Analytics Function (NWDAF), in accordance with an embodiment of the present
disclosure.
[0049] FIG. 3 illustrates an exemplary block diagram of a system
5 architecture of the system, in accordance with an embodiment of the present
disclosure.
[0050] FIG. 4A illustrates an exemplary flow diagram implementing a
method for performing load data reporting in a network, in accordance with an
embodiment of the present disclosure.
10 [0051] FIG. 4B illustrates an exemplary flow diagram implementing a
method for performing load data reporting in a network, in accordance with an
embodiment of the present disclosure.
[0052] FIG. 5 illustrates an exemplary computer system in which or with
which the embodiments of the present disclosure may be implemented.
15 [0053] The foregoing shall be more apparent from the following more
detailed description of the disclosure.
DETAILED DESCRIPTION
[0054] In the following description, for explanation, various specific details
20 are outlined in order to provide a thorough understanding of embodiments of the
present disclosure. It will be apparent, however, that embodiments of the present
disclosure may be practiced without these specific details. Several features
described hereafter can each be used independently of one another or with any
combination of other features. An individual feature may not address all of the
25 problems discussed above or might address only some of the problems discussed
above. Some of the problems discussed above might not be fully addressed by any
of the features described herein.
[0055] The ensuing description provides exemplary embodiments only and
is not intended to limit the scope, applicability, or configuration of the disclosure.
30 Rather, the ensuing description of the exemplary embodiments will provide those
skilled in the art with an enabling description for implementing an exemplary
10
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.
[0056] Specific details are given in the following description to provide a
5 thorough understanding of the embodiments. However, it will be understood by one
of ordinary skill in the art that the embodiments may be practiced without these
specific details. For example, circuits, systems, networks, processes, and other
components may be shown as components in block diagram form in order not to
obscure the embodiments in unnecessary detail. In other instances, well-known
10 circuits, processes, algorithms, structures, and techniques may be shown without
unnecessary detail to avoid obscuring the embodiments.
[0057] Also, it is noted that individual embodiments may be described as a
process that is depicted as a flowchart, a flow diagram, a data flow diagram, a
structure diagram, or a block diagram. Although a flowchart may describe the
15 operations as a sequential process, many of the operations can be performed in
parallel or concurrently. In addition, the order of the operations may be re-arranged.
A process is terminated when its operations are completed but could have additional
steps not included in a figure. A process may correspond to a method, a function, a
procedure, a subroutine, a subprogram, etc. When a process corresponds to a
20 function, its termination can correspond to a return of the function to the calling
function or the main function.
[0058] The word “exemplary” and/or “demonstrative” is used herein to
mean serving as an example, instance, or illustration. For the avoidance of doubt,
the subject matter disclosed herein is not limited by such examples. In addition, any
25 aspect or design described herein as “exemplary” and/or “demonstrative” is not
necessarily to be construed as preferred or advantageous over other aspects or
designs, nor is it meant to preclude equivalent exemplary structures and techniques
known to those of ordinary skill in the art. Furthermore, to the extent that the terms
“includes,” “has,” “contains,” and other similar words are used in either the detailed
30 description or the claims, such terms are intended to be inclusive like the term
“comprising” as an open transition word without precluding any additional or other

elements.
[0059] Reference throughout this specification to “one embodiment” or “an
embodiment” or “an instance” or “one instance” means that a particular feature,
structure, or characteristic described in connection with the embodiment is included
5 in at least one embodiment of the present disclosure. Thus, the appearances of the
phrases “in one embodiment” or “in an embodiment” in various places throughout
this specification are not necessarily all referring to the same embodiment.
Furthermore, the particular features, structures, or characteristics may be combined
in any suitable manner in one or more embodiments.
10 [0060] The terminology used herein is to describe particular embodiments
only and is not intended to be limiting the disclosure. As used herein, the singular
forms “a”, “an”, and “the” are intended to include the plural forms as well, unless
the context indicates otherwise. It will be further understood that the terms
“comprises” and/or “comprising,” when used in this specification, specify the
15 presence of stated features, integers, steps, operations, elements, and/or
components, but do not preclude the presence or addition of one or more other
features, integers, steps, operations, elements, components, and/or groups thereof.
As used herein, the term “and/or” includes any combinations of one or more of the
associated listed items.
20 [0061] The various embodiments throughout the disclosure will be
explained in more detail with reference to FIGs. 1-5.
[0062] FIG. 1 illustrates an exemplary network architecture (100) for
implementing a system (108), in accordance with an embodiment of the present
disclosure.
25 [0063] As illustrated in FIG. 1, one or more computing devices (104-1, 104-
2…104-N) may be connected to the system (108) through a network (106). A
person of ordinary skill in the art will understand that the one or more computing
devices (104-1, 104-2…104-N) may be collectively referred as computing devices
(104) and individually referred as a computing device (104). One or more users
30 (102-1, 102-2…102-N) may provide one or more requests to the system (108). A
person of ordinary skill in the art will understand that the one or more users (102-
12
1, 102-2…102-N) may be collectively referred as users (102) and individually
referred as a user (102). Further, the computing devices (104) may also be referred
as a user equipment (UE) (104) or as UEs (104) throughout the disclosure.
[0064] In an embodiment, the computing device (104) may include, but not
5 be limited to, a mobile, a laptop, etc. Further, the computing device (104) may
include one or more in-built or externally coupled accessories including, but not
limited to, a visual aid device such as a camera, audio aid, microphone, or keyboard.
Furthermore, the computing device (104) may include a mobile phone, smartphone,
virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general10 purpose computer, a desktop, a personal digital assistant, a tablet computer, and a
mainframe computer. Additionally, input devices for receiving input from the user
(102) such as a touchpad, touch-enabled screen, electronic pen, and the like may be
used. A person of ordinary skill in the art will appreciate that the user equipment
(104) may not be restricted to the mentioned devices and various other devices may
15 be used.
[0065] Referring to FIG. 1, the user equipment (104) is configured to
communicate with the system (108) via the network (106). In an embodiment, the
network (106) may include at least one of a Fifth Generation (4G) network, 6G
network, or the like. The network (106) may enable the user equipment (104) to
20 communicate with other devices in the network architecture (100) and/or with the
system (108). The network (106) may include a wireless card or some other
transceiver connection to facilitate this communication. In another embodiment, the
network (106) may be implemented as, or include any of a variety of different
communication technologies such as a wide area network (WAN), a local area
25 network (LAN), a wireless network, a mobile network, a Virtual Private Network
(VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.
[0066] In an embodiment, the network (106) may include at least one of a
Fifth Generation (5G) network, Sixth Generation (6G) network, or the like. The
network (106) may enable the user equipment (104) to communicate with other
30 devices in the network architecture (100) and/or with the system (108). The network
(106) may include a wireless card or some other transceiver connection to facilitate

this communication. In another embodiment, the network (106) may be
implemented as, or include any of a variety of different communication
technologies such as a wide area network (WAN), a local area network (LAN), a
wireless network, a mobile network, a Virtual Private Network (VPN), the Internet,
5 the Public Switched Telephone Network (PSTN), or the like.
[0067] In an embodiment, the network (106) may include, by way of
example but not limitation, at least a portion of one or more networks having one
or more nodes that transmit, receive, forward, generate, buffer, store, route, switch,
process, or a combination thereof, etc. one or more messages, packets, signals,
10 waves, voltage or current levels, some combination thereof, or so forth. The
network (106) may also include, by way of example but not limitation, one or more
of a wireless network, a wired network, an internet, an intranet, a public network, a
private network, a packet-switched network, a circuit-switched network, an ad hoc
network, an infrastructure network, a Public Switched Telephone Network (PSTN),
15 a cable network, a cellular network, a satellite network, a fiber optic network, or
some combination thereof.
[0068] In an embodiment, the user equipment (104) is communicatively
coupled with the system (108). The system (108) may receive a connection request
from the UE (104). The system (108) may send an acknowledgment of the
20 connection request to the UE (104). The UE (104) may transmit a plurality of
signals in response to the connection request. The system (108) may be configured
for performing load data reporting in the network (106).
[0069] In an embodiment, the system (108) may include a consumer NF
(110), a network data analytics function (NWDAF) (114), a network repository
25 function (NRF) (112) and a plurality of network functions (NFs) (116-1, 116-
2…116-N). In an aspect, at least one network function (NF) from the plurality of
network function may be a service communication proxy (SCP). In an aspect, a
person of ordinary skill in the art will understand that the one or more network
functions (116-1, 116-2…116-N) may be collectively referred as network functions
30 (NFs) (116) and individually referred as a Network function (NF) (116).
[0070] The consumer NF (110) may subscribe to the NWDAF (114) for
14
load analytics of at least one NF (e.g., Service communication proxy (SCP)), by
sending a subscription request to the NWDAF (114). The subscription request
comprises at least one public land mobile network (PLMN) identifier (ID)
corresponding to the at least one NF (116) and a network function type.
5 [0071] In an aspect, the network function type may include whether the
network function is a consumer network function or a producer network function.
For example, during the course of network operations, such as registering a User
Equipment (“UE”) with the network, forming communication pathways between
various NFs, one NF (referred to as a “consumer” NF) may request, from the NRF,
10 an identifier of one or more other NFs (referred to as “producer” NFs) from which
the consumer NF may obtain services, information, or the like. For example,
consumer NF may be Access and Mobility Management Function (AMF), Serving
Gateway (SGW). As another example, the producer NF is a Policy Control Function
(PCF), Unified Data Management function (UDM), Charging Function (CHF),
15 Subscription Locator Function (SLF).
[0072] In an aspect, the network functions may further include, but not
limited to, Service Communication Proxy (SCP), Session Management Function
(SMF), User Plane Function (UPF), Network Repository Function (NRF),
Application Function (AF), Network Exposure Function (NEF), Network Data
20 Analytics Function, Customer Network Function (CNF), Provider Network
Function (PNF), etc.
[0073] The Service Communication Proxy (SCP) is a network function of
service-oriented architecture (SOA) and distributed systems. Its primary function is
to facilitate communication between services, often providing additional
25 capabilities beyond basic message routing.
[0074] The Access and Mobility Management Function (AMF) is network
function to manage user access and mobility in the network. The AMF handles
initial registration, authentication, and mobility management for devices moving
between different cells or networks.
30 [0075] The policy control function (PCF) is network function that defines
and enforces policies related to network resource allocation, quality of service

(QoS), and service differentiation. The PCF supports dynamic policy adjustments
based on network conditions and user requirements.
[0076] The Session Management Function (SMF) is network function that
establishes, manages, and terminates user sessions in the network. The SMF is
5 responsible for session anchoring and mobility management across different
network slices.
[0077] The User Plane Function (UPF) is network function that Handles the
forwarding of user data packets in the network. The UPF provides data processing,
routing, and traffic management capabilities.
10 [0078] The Network Repository Function (NRF) is network function to
stores information about available network functions and capabilities within the
network. The NRF facilitates the discovery and selection of network functions by
other network entities.
[0079] The Network Data Analytics Function (NWDAF) is a network
15 function to support advanced analytics and data-driven decision-making processes.
The NWDAF collects and analyzes network data, including traffic patterns, user
behavior, service usage, and performance metrics.
[0080] Upon receiving the subscription request, the NWDAF (114) may
discover the at least one NF (e.g., SCP) from the NRF (112), by sending a discovery
20 request to the NRF (112). The discovery request comprises the received PLMN ID
corresponding to the at least one NF and the network function type. On receiving
the discovery request, the NRF (112) may send a discovery response to the NWDAF
(114) based on the PLMN ID and the network function type. The discovery
response comprises a list (e.g., nfservicelist) of requested NF instances (e.g., SCP
25 instances). After receiving the discovery response from the NRF (112), the
NWDAF (114) may perform a mapping of the received NF instances in the list. The
mapping stores the NF instances (e.g., SCP instances) corresponding to the at least
one NF (e.g., SCP). In an aspect, while performing the mapping, the NWDAF may
perform mapping of data of the subscription request (e.g., network function type
30 and the PLMN ID) to the network functions in the list. The mapping of NF instances
in the list is process of associating instances of network functions with their
16
corresponding entries in the list. The list provides an overview of all network
functions and their instances, facilitating efficient management and monitoring of
the network functions. Then, the NWDAF may stores the received NF instances to
the corresponding network function in the list. In an aspect, the network function
5 instances (NF instances) refer to instances of network functions that are deployed
and operated within the network. The NF instances represent the operational
components of network functions that manage and control the network's operations.
In an aspect, NF instances may include, but not limited to, resource management
instances, session management instances, policy control instances, authentication
10 instances, slice management instances, management and orchestration instances,
etc.
[0081] The NWDAF (114) may send subscription to the NRF (112) for load
value changes and NF service status updates. The NWDAF may fetches the NF
instances from the mapping while sending the subscription to the NRF. In an aspect,
15 the load values of the NF instances may refer to current utilization or workload of
the NF instances. For example, a SCP Instance 1 is for routing and managing service
communications and a SCP Instance 2 is for redundancy and load balancing to
handle peak traffic. The SCP Instance 1 load value is 70%. This indicates that the
SCP Instance 1 is operating at 70% of its maximum capacity, handling a substantial
20 volume of service requests and message routing tasks. The SCP Instance 2 load
value is 50%. The SCP Instance 2 is actively performing load balancing of the
network traffic. If the load value of the SCP Instance 1 is increased to 80% from
70%, so there is load value change for the SCP instance 1. If load value of the SCP
Instance 2 is 50%, then there is no load value change for the SCP instance 2.
25 [0082] In an aspect, NF service status refers to the operational state and
condition of a Network Function (NF) within a network infrastructure. It
encompasses various metrics and indicators that provide insights into the health,
availability, performance, and operational status of the NF. For example, the SCP
instance handles service communication and messaging. The service status of the
30 SCP instances comprises active, standby, or undergoing maintenance. The SCP
instance updates its service status may comprise active-active or active-standby.

[0083] In response to the subscription, the NRF (112) may send a response
to the NWDAF (114) after a configured time interval. The response comprises load
values for the NF instances (e.g., SCP instances) in the list. In an aspect, the load
values are values of load corresponding to the at one PLMN ID corresponding to
5 the at least one NF (116). Upon receiving the notification from the NRF (112), the
NWDAF (114) may send the received response towards the consumer NF (110).
The PLMN ID may be used to signify the SCP instances load. In an aspect, NF
instance within the network may be associated with PLMN IDs to denote the
network operator it belongs to. This helps in distinguishing between different
10 operators' network elements within the network. For example, the SCP instance
within the network may be associated with PLMN IDs to identify and differentiate
between different network operators. This differentiation helps in managing and
enhancing service communication between different operators' networks. For
example, the subscriber roams onto the operator’s network from another network
15 domain. The SCP instance uses the subscriber’s home PLMN ID to route and
process service requests according to agreed-upon roaming agreements and
policies.
[0084] The NWDAF may displays real-time, historical, and predictive
values of the NF load status for all subscribed NF instances (e.g., SCP instances).
20 This information may be utilized to estimate future resource allocations based on
load patterns and utilization trends. In an aspect, the load patterns in the network
refer to the fluctuations and variations in the usage of resources (e.g., bandwidth,
CPU, memory, and storage) over time. The load patterns are used to determine their
impact on network performance, capacity planning, resource allocation, and overall
25 user experience. The load patterns comprise regular or periodic load (e.g., daily
peak, weekly peak, seasonal peak in traffic), unexpected spikes, etc. Further, the
utilization trends in the network refer to the patterns and variations in the usage of
network resources over time. The utilization trends are used in resource allocation,
planning capacity upgrades, and ensuring improved network performance. The
30 utilization trends may be resource usage metrics (e.g., bandwidth, storage), patterns
and variations (e.g., peak usage, off-peak usage, seasonal variations, etc.). For
18
example, the internet service provider (ISP) monitors bandwidth utilization trends
across its network. By analyzing historical data, identifying peak usage times and
plan capacity upgrades to ensure consistent service delivery during high-demand
periods.
5 [0085] Although FIG. 1 shows exemplary components of the network
architecture (100), in other embodiments, the network architecture (100) may
include fewer components, different components, differently arranged components,
or additional functional components than depicted in FIG. 1. Additionally, or
alternatively, one or more components of the network architecture (100) may
10 perform functions described as being performed by one or more other components
of the network architecture (100).
[0086] FIG. 2A illustrates an exemplary block diagram (200) of the system
(108), in accordance with an embodiment of the present disclosure.
[0087] Referring to FIG. 2A, in an embodiment, the system (108) may
15 include one or more processor(s) (202). The one or more processor(s) (202) may be
implemented as one or more microprocessors, microcomputers, microcontrollers,
digital signal processors, central processing units, logic circuitries, and/or any
devices that process data based on operational instructions. Among other
capabilities, the one or more processor(s) (202) may be configured to fetch and
20 execute computer-readable instructions stored in a memory (204) of the system
(108). The memory (204) may be configured to store one or more computerreadable instructions or routines in a non-transitory computer readable storage
medium, which may be fetched and executed to create or share data packets over a
network service. The memory (204) may comprise any non-transitory storage
25 device including, for example, volatile memory such as random-access memory
(RAM), or non-volatile memory such as erasable programmable read only memory
(EPROM), flash memory, and the like.
[0088] In an embodiment, the system (108) may include an interface(s)
(206). The interface(s) (206) may comprise a variety of interfaces, for example,
30 interfaces for data input and output devices (I/O), storage devices, and the like. The
interface(s) (206) may facilitate communication through the system (108). The

interface(s) (206) may also provide a communication pathway for one or more
components of the system (108). Examples of such components include, but are not
limited to, processing engine(s) (208) and a database (210).
[0089] In an embodiment, the processing engine(s) (208) may be
5 implemented as a combination of hardware and programming (for example,
programmable instructions) to implement one or more functionalities of the
processing engine(s) (208). In examples described herein, such combinations of
hardware and programming may be implemented in several different ways. For
example, the programming for the processing engine(s) (208) may be processor10 executable instructions stored on a non-transitory machine-readable storage
medium and the hardware for the processing engine(s) (208) may comprise a
processing resource (for example, one or more processors), to execute such
instructions. In the present examples, the machine-readable storage medium may
store instructions that, when executed by the processing resource, implement the
15 processing engine(s) (208). In such examples, the system may comprise the
machine-readable storage medium storing the instructions and the processing
resource to execute the instructions, or the machine-readable storage medium may
be separate but accessible to the system and the processing resource. In other
examples, the processing engine(s) (208) may be implemented by electronic
20 circuitry.
[0090] In an aspect, the system may use the processing engine(s) to perform
load data reporting between the NRF (112), the NWDAF (114), and the consumer
NF (110). In an aspect, the load data or the load information refers to the
information and metrics that describe the utilization and performance of network
25 resources. The load data is used to find out how network resources are being used,
manage network performance, and make decisions for network optimization and
scaling. For example, traffic load (e.g., total throughput, traffic load, peak traffic,
etc.), resource utilization (e.g., bandwidth usage, storage utilization, memory
utilization, etc.), subscriber load (e.g., no of active users, device connections,
30 session counts, etc.), signal quality (e.g., signal-to-noise ratio (SNR), signal strength
(RSRP)), call and session load (e.g., no of active calls, call drop rate, session
20
establishment success rate), handover load (e.g., no of handovers, handover success
rate, handover failures, etc.)
[0091] In an aspect, the processing engine may be a part of the NWDAF
(114). The processing engine(s) (208) may include a discovery unit, a reporting
5 unit, and other unit(s). In an embodiment, the other unit(s) may include, but not
limited to, a data ingestion unit, an input/output unit, and a notification unit. The
discovery unit may receive a subscription request for SCP load analytics from the
consumer NF (110). The discovery unit may discover the SCP from the NRF (112).
The reporting unit may receive requested SCP instances in a list (e.g., nfservicelist),
10 in response to discovery of SCP from the NRF (112). After receiving the discovery
response, the reporting unit may perform a mapping of the received NF instances
and subscribe to the NRF (112) for requesting load values (e.g., load value changes
and NF service status updates) corresponding to the NF instances. In response to
subscription, the reporting unit may receive a response from the NRF (112) after a
15 configured time interval. The response comprises the load values for SCP instances
in the list. The reporting unit may send the received update from the NRF (112)
towards the consumer NF (110).
[0092] The NF load status for all subscribed SCP instances, which may be
used to estimate resource allocations based on load patterns and utilization trends.
20 [0093] Although FIG. 2A shows exemplary components of the system
(108), in other embodiments, the system (108) may include fewer components,
different components, differently arranged components, or additional functional
components than depicted in FIG. 2A. Additionally, or alternatively, one or more
components of the system (108) may perform functions described as being
25 performed by one or more other components of the system (108).
[0094] FIG. 2B illustrates an exemplary block diagram (200B) of the
Network Data Analytics Function (NWDAF) (114), in accordance with an
embodiment of the present disclosure.
[0095] The NWDAF (114) comprises a receiving unit (212), a sending unit
30 (214), a processing unit (216) and a database (218).
[0096] The receiving unit (212) is configured to receive a subscription

request for load data of at least one network function (NF) from the consumer NF
(110). The at least one NF (116) may be a service communication proxy. The
consumer NF (110) may request load data corresponding to a plurality of SCP
instances by sending the subscription request to the NWDAF (114). The
5 subscription request comprises at least one public land mobile network (PLMN)
identifier (ID) corresponding to the at least one NF (116) and a network function
type. For example, PLMN ID corresponding to the SCP. The network function type
is the SCP.
[0097] On receiving the subscription request, the sending unit (214) is
10 configured to send a discovery request for the at least one NF (116) to the NRF
(112). The discovery request comprises the received PLMN ID corresponding to
the NF (116) and the network function type. The NWDAF (114) may use the
discovery request to find out details of the NF (116) corresponding to the
subscription request from the NRF (112) based on the PLMN ID and network
15 function type. The details may comprise NF type, instances corresponding to the
NF, etc.
[0098] Based on the discovery request, the receiving unit (212) is
configured to receive a discovery response comprising a list of a plurality of NF
instances corresponding to the at least one NF (116) from the NRF (112). In an
20 aspect, on receiving the discovery request, the NRF (112) may find out the list of
the NF instances corresponding to the NF based on the received PLMN ID
corresponding to the NF and the NF type. The NRF (112) may send the list of the
NF instances corresponding to the NF to the NWDAF (114). In an aspect, the list
comprises NF instances endpoints, NF instance IDs, a NF instance name, a NF
25 service name, and a NF service status.
[0099] The processing unit (216) of the NWDAF (114) may perform a
mapping for the received plurality of NF instances corresponding to the at least one
NF (116) in the list. The plurality of NF instances corresponding to the at least one
NF (116) may be fetched by the NWDAF (114) from the mapping in the list at time
30 of the subscription. In an aspect, fetching of the plurality of NF instances
corresponding to the at least one NF includes retrieving data of the NF instances of
22
the NF based on mapping in the list. For example, consider two AMF instances:
AMF1_instance_1 and AMF2_instance_2. These instances are mapped to their
corresponding network functions, where AMF1_instance_1 is associated with
AMF 1, and AMF2_instance_2 is associated with AMF 2. During subscription, the
5 NWDAF retrieves AMF1_instance_1 corresponding to AMF 1 and
AMF2_instance_2 corresponding to AMF 2 using this mapping.
[00100] The processing unit (216) is configured to subscribe for load values
corresponding to the plurality of NF instances of the at least one NF in the mapping,
to the NRF. The NWDAF may subscribe to the NRF to receive the load values
10 corresponding to the plurality of NF instances of the at least one NF in the mapping.
[00101] The receiving unit (212) is configured to receive a response from the
NRF (112) after a predefined time period. The response comprises load values
corresponding to the at least one NF. In an aspect, the predefined time interval may
be a predetermined time period for process within the network. The predefined time
15 period may be used to synchronize the flow of the requests, the responses and the
data between the network functions. This ensures that data transmission and
reception occur at predefined time period and also reducing the likelihood of
conflicts or errors due to timing discrepancies. For example, the NRF provides the
response (e.g., load data) to the NWDAF within predefined time period (e.g., 200
20 milliseconds) to ensure timely analytics and decision-making.
[00102] In an aspect, in response to the subscription, the NRF (112) may
send the load values corresponding to the plurality of NF instances of the at least
one NF (116). The NWDAF (114) may receive the response from the NRF (112)
corresponding to the updates or changes in the load values corresponding to the NF
25 (116). Further, the response may comprise NF service status updates. In an aspect,
the NRF (112) is configured to store information corresponding to the NFs (116).
The information includes, but not limited to, NF instances endpoints, NF instance
IDs, NF instance names, NF service names, and NF service status, etc.
[00103] In an aspect, the NF instances endpoints may refer as endpoints or
30 access points where instances of network functions are deployed or instantiated. In
an aspect, the NF instance IDs may refer as identifiers assigned to instances of

network functions (NFs) deployed within the network. The NF IDs are used for
management and operation of network functions within the network. In an aspect,
the NF instance names may refer as names assigned to instances of network
functions (NFs) deployed within the network. The NF instance names may help
5 operators and administrators to easily identify and distinguish between different
instances of network functions. This is useful where multiple instances of the same
NF type may be deployed. For example, a SCP-East-Prod indicates a Service
Communication Proxy deployed in the Eastern region for production services, a
SCP-West-Test indicates a Service Communication Proxy deployed in the Western
10 region for testing or development purposes, a SCP-Internal indicates a Service
Communication Proxy deployed specifically for internal communication within the
network, etc. In an aspect, the NF service names may refer to names assigned to
network function (NF) services offered within the network. For example, the
service communication proxy (SCP) services such as authentication, messaging,
15 load balancing, content delivery, traffic management, database management, etc. In
an aspect, NF service status may refer as current operational state or condition of a
Network Function (NF) service. For example, SCP service status may comprise
registered, running or operational, stopped, error, etc.
[00104] The sending unit (214) may send the response towards the consumer
20 NF (110). On receiving the response from the NRF (112), the NWDAF (114) may
send the response towards the consumer NF (110). In this way, the consumer NF
(110) may receive the load data corresponding to the NF instances of the NF (116)
from the NWDAF (114). In an aspect, the NWDAF (114) may store the received
load data corresponding to the NF instances of the NF in the database (218).
25 [00105] In an aspect, the NRF (112) may provide the load information for
the NF instances of the NF (110) in single notification towards the NWDAF (114).
This reduces notification traffic towards the NWDAF (114) and consequently
towards the consumer NF (110). With reduction in the signaling traffic, the resource
utilization at network function is enhanced.
30 [00106] FIG. 3 illustrates an exemplary architecture (300) of the system
(108), in accordance with an embodiment of the present disclosure.
24
[00107] As illustrated in FIG. 3, in an embodiment, the system (108) may
include the consumer NF (110), the NWDAF (114), and the NRF (112). The
consumer NF (110) may communicate with the NWDAF (114) and the NRF (112)
via a Nnf interface. The NWDAF (114) may communicate with the consumer NF
5 (110) and the NRF (112) via a Nnwdaf interface. The NRF (112) may communicate
with the NWDAF (114) and the consumer NF (110) via a Nnrf interface.
[00108] In an aspect, the Nnf interface is an interface used by the consumer
NF to request subscription to data delivery for a particular context, to cancel
subscription to data delivery and to request a report of data for a particular context
10 from the NWDAF.
[00109] In an aspect, the Nnwdaf interface is an interface used by the
NWDAF to request subscription to network analytics delivery for a particular
context, to cancel subscription to network analytics delivery and to request a report
of network analytics for a particular context from the NFs and the NRF.
15 [00110] In an aspect, the Nnrf interface is an interface used by the NRF to
communicate with the other NFs.
[00111] FIG. 4A illustrates an exemplary flow diagram implementing a
method (400A) for performing load data reporting in the network (106), in
accordance with an embodiment of the present disclosure.
20 [00112] As illustrated in FIG. 4A, at step 402, the method (400A) may
include sending a subscription request to a NWDAF (114) for SCP load analytics
by a consumer NF (110). The subscription request for load data of the SCP may
refer to a request made to the NWDAF (114) to provide data related to the
utilization, performance, or operational load of the SCP within the network. In an
25 aspect, the subscription request comprises PLMN ID corresponding to the SCP.
[00113] At step 404, the method (400A) may include discovering, by the
NWDAF (114), the SCP from the NRF (112), upon receiving the request. The
discovering of the SCP from the NRF (112) is performed using the PLMN ID
received in the subscription request. The NRF (112) may use the PLMN ID to find
30 out the SCP instances corresponding to the subscription request.
[00114] At step 406, the method (400A) may include sending, by the NRF

(112), requested SCP instances in a list (e.g. nfservicelist). In an aspect, the
nfservicelist may refer to the list or repository maintained by the NRF that contains
information about available NF services. The list may include details such as, but
not limited to, NF Service ID (e.g., identifier for each NF service), NF Service
5 Name (e.g., name or label for the NF service), NF Service Type (e.g., types or
categories of the NF service (e.g., firewall, load balancer, etc.)), NF Service
Capabilities (e.g., functional capabilities and features provided by the NF service),
NF Service Location (e.g., geographic or logical location where the NF service is
deployed), NF Service Status (e.g., current operational status of the NF service (e.g.,
10 registered, running, stopped, degraded)), NF Service Dependencies (e.g., other NFs
or resources that the NF service depends on).
[00115] At step 408, the method (400A) may include performing, by the
NWDAF (114), mapping of the received NF instances (e.g., nfserviceinstance) of
the NF. The NF instances may include instances of the NFs within the network. For
15 example, load balancing service instances, authentication service instances, routing
service instances, etc.
[00116] At step (410), the method (400A) may include subscribing, by the
NWDAF (114), for load value changes and NF service status updates to the NRF
(112), after receiving the discovery response. The subscription is used to request
20 updates corresponding to the SCP instances received in the list. The step of
subscribing, by the NWDAF, to the NRF includes the NWDAF initiates a
subscription to the NRF. The NRF acknowledges the subscription by sending the
response to the NWDAF. The NWDAF receives load data updates from the NRF.
In an aspect, the load values of the network function (NF) instances refer to metrics
25 related to resource utilization and operational performance of the NF instances
within the network. The changes in the load values may use to adjust or estimate
the resource allocation, configuration, or operational parameters of the NF instances
within the network. For example, in configuring and improving service instances,
determining changes in the values of the current configuration settings of NF
30 instances, including CPU allocation, memory limits, network settings, and queue
management parameters. The determined changes are used to make changes in
26
configuration settings based on performance analysis and capacity planning to
improve resource utilization and efficiency.
[00117] At step (412), the method (400A) may include sending, by the NRF
(112), a notification including load values for SCP instances in the list (e.g.,
5 nfservicelist) to the NWDAF (114), after a configured time interval. In an aspect,
the NRF (112) may send the load values of the NF instances after the configured
time interval on receiving request for updates in load values of the NF instances. In
this way, responses from the NRF after the configured or predefined time period
enable the NWDAF to perform real-time analytics and decision-making, facilitating
10 rapid network enhancements and service improvements.
[00118] At step (414), the method (400A) may include sending, by the
NWDAF (114), the received notification towards the consumer NF (110), upon
receiving the notifications from the NRF (112). The NWDAF (114) may send the
received load values to the consumer NF. In an aspect, the NWDAF (114) may store
15 the received load values corresponding to the NF instances of the NF (116) in the
database (218).
[00119] The NWDAF (114) may provide real-time, historical, and predictive
displays of the NF load status for all subscribed NF instances (e.g., SCP instances),
which may be utilized to estimate future resource allocations based on load patterns
20 and utilization trends. The load pattern of NF instances allows network
administrators to implement appropriate strategies for capacity planning, resource
scaling, load balancing, and performance enhancement.
[00120] FIG. 4B illustrates an exemplary flow diagram implementing a
method (400B) for performing load data reporting in the network (106), in
25 accordance with an embodiment of the present disclosure.
[00121] At step (422), the method (400B) includes receiving, by a network
data analytics function (NWDAF) (114), a subscription request for load data of at
least one network function (NF) from a consumer network function (NF) (110). The
subscription request comprises at least one public land mobile network (PLMN)
30 identifier corresponding to the at least one NF (116) and a network function type.
For example, the subscription request comprises the network function type is SCP

and the PLMN ID corresponding to the SCP.
[00122] At step 424, the method (400B) includes on receiving the
subscription request, sending, by the NWDAF (114), a discovery request for the at
least one NF (116) to a network repository function (NRF). The discovery request
5 may send to find out the NF (116) corresponding to the received network function
type and the PLMN ID from the subscription request.
[00123] At step 426, the method (400B) includes in response to the discovery
request, receiving, by the NWDAF (114), a discovery response comprising a list of
a plurality of NF instances corresponding to the at least one NF (116) from the NRF
10 (112). The NRF (112) may determine the NF corresponding to the network function
type and the PLMN ID received in the NWDAF (114). Then, the NRF (112) may
send the discovery response. The discovery response may include the list of the
plurality of NF instances corresponding to the at least one NF (116).
[00124] At step 428, the method (400B) includes performing, by the
15 NWDAF (114), a mapping for the received plurality of NF instances corresponding
to the at least one NF in the list. The NWDAF (114) may perform the mapping for
the received plurality of NF instances corresponding to the at least one NF in the
list. The mapping may act as an internal cache to store the received plurality of NF
instances corresponding to the at least one NF in the list. The instances may be
20 fetched from the mapping at the time of subscription.
[00125] At step 430, the method (400B) includes subscribing, by the
NWDAF (114), for load values corresponding to the plurality of NF instances of
the at least one NF (116) in the mapping, to the NRF (112). The NWDAF (114)
may subscribe to the NRF (112) to receive the load values corresponding to the
25 plurality of NF instances of the at least one NF (116) in the mapping.
[00126] At step 432, the method (400B) includes receiving, by the NWDAF
(114), a response from the NRF (112) after a predefined time period. The response
comprises load values corresponding to the at least one NF (116). In response to the
subscription, the NRF (112) may send the response to the NWDAF (114) after the
30 predefined time period. The response comprises the load values corresponding to
the plurality of NF instances of the at least one NF (116).
28
[00127] At step 434, the method (400B) includes sending, by the NWDAF
(114), the response towards the consumer NF (110). The NWDAF (114) may send
the received load values corresponding to the plurality of NF instances of the at
least one NF (116) to the customer NF (110). In this way, the customer NF (110)
5 may receive the load values corresponding to the NF by sending the subscription
request to the NWDAF (114). Further, the NWDAF (114) may store the received
load values corresponding to the NF instances of the NF in the database (218).
[00128] In an aspect, the NWDAF may discover multiple SCP instances by
sending the discovery request to the NRF. In response to the discovery request, the
10 NWDAF may receive the multiple SCP instances in a list from the NRF. The
NWDAF may perform a mapping (e.g., for internal storage) for the received SCP
instances in the list. The NWDAF may subscribe to the NRF for load values of the
SCP instances of the mapping. The NRF may send the load information towards
the NWDAF in a single notification for the multiple SCP instances in the list (e.g.,
15 nfservicelist). The NWDAF may display real-time, historical, and predictive values
of the load for all subscribed SCP instances. The load information is used to
estimate resource allocations based on load patterns and utilization trends. As single
notification is used to provide load information corresponding the SCP instances,
this reduces huge traffic due to increased signalling between multiple network
20 functions (e.g., consumer NF, NRF, NWDAF).
[00129] FIG. 5 illustrates an exemplary computer system (500) in which or
with which the embodiments of the present disclosure may be implemented.
[00130] As shown in FIG. 5, the computer system (500) may include an
external storage device (510), a bus (520), a main memory (530), a read-only
25 memory (540), a mass storage device (550), a communication port(s) (560), and a
processor (570). A person skilled in the art will appreciate that the computer system
(500) may include more than one processor and communication ports. The
processor (570) may include various modules associated with embodiments of the
present disclosure. The communication port(s) (560) may be any of an RS-232 port
30 for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit
or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other

existing or future ports. The communication ports(s) (560) may be chosen
depending on a network, such as a Local Area Network (LAN), Wide Area Network
(WAN), or any network to which the computer system (500) connects.
[00131] In an embodiment, the main memory (530) may be Random-Access
5 Memory (RAM), or any other dynamic storage device commonly known in the art.
The read-only memory (540) may be any static storage device(s) e.g., but not
limited to, a Programmable Read Only Memory (PROM) chip for storing static
information e.g., start-up or basic input/output system (BIOS) instructions for the
processor (570). The mass storage device (550) may be any current or future mass
10 storage solution, which can be used to store information and/or instructions.
Exemplary mass storage solutions include, but are not limited to, Parallel Advanced
Technology Attachment (PATA) or Serial Advanced Technology Attachment
(SATA) hard disk drives or solid-state drives (internal or external, e.g., having
Universal Serial Bus (USB) and/or Firewire interfaces).
15 [00132] In an embodiment, the bus (520) may communicatively couple the
processor(s) (570) with the other memory, storage, and communication blocks. The
bus (520) may be, e.g., a Peripheral Component Interconnect (PCI)/PCI Extended
(PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus
(USB), or the like, for connecting expansion cards, drives, and other subsystems as
20 well as other buses, such a front side bus (FSB), which connects the processor (570)
to the computer system (500).
[00133] In another embodiment, operator and administrative interfaces, e.g.,
a display, keyboard, and cursor control device may also be coupled to the bus (520)
to support direct operator interaction with the computer system (500). Other
25 operator and administrative interfaces can be provided through network
connections connected through the communication port(s) (560). Components
described above are meant only to exemplify various possibilities. In no way should
the aforementioned exemplary computer system (500) limit the scope of the present
disclosure.
30 [00134] While considerable emphasis has been placed herein on the preferred
embodiments, it will be appreciated that many embodiments can be made and that
30
many changes can be made in the preferred embodiments without departing from
the principles of the disclosure. These and other changes in the preferred
embodiments of the disclosure will be apparent to those skilled in the art from the
disclosure herein, whereby it is to be distinctly understood that the foregoing
5 descriptive matter is to be implemented merely as illustrative of the disclosure and
not as a limitation. The present disclosure provides technical advancement related
to load data reporting. This advancement addresses the limitations of existing
solutions by enabling a NWDAF to discover multiple network function (NF)
instances in single request as a list from a NRF, on receiving a subscription request
10 for NF load data from a customer NF. The NWDAF may subscribe to the NRF for
the load data of the discovered NF instances. The NRF sends load information of
multiple NF instances to the NWDAF in a single notification. The NWDAF send
the received load information of multiple NF instances to the customer NF. This
offers significant improvements in reducing notification traffic towards the
15 NWDAF and consequently towards the consumer NF. The disclosed invention
enhances resource utilization at the network function by reducing signaling traffic.
ADVANTAGES OF THE INVENTION
[00135] The present disclosure provides a system and a method for reporting
load information to a Network Function (NF).
20 [00136] The present disclosure provides a system and a method that includes
a Network Repository Function (NRF) to provide load information for Service
Communication Proxy (SCP) instances in a single notification towards Network
data analytics function (NWDAF) for a particular Public Land Mobile Network
(PLMN).
25 [00137] The present disclosure provides a system and a method that includes
the NWDAF to discover multiple SCP instances in a list from the NRF and
subscribe to the NRF for load values of the discovered SCP instances for load
analytics.
[00138] The present disclosure provides a system and a method that reduces
30 notification traffic towards the NWDAF and consequently towards a consumer NF.
Therefore, resource utilization at NF end may be enhanced.

WE CLAIM:

1. A method (400B) for reporting load data in a network (106), the method
(400B) comprising:
receiving (422), by a network data analytics function (NWDAF)
(114), a subscription request for load data of at least one network function
(NF) (116) from a consumer network function (NF) (110);
on receiving the subscription request, sending (424), by the NWDAF
(114), a discovery request for the at least one NF (116) to a network
repository function (NRF) (112);
in response to the discovery request, receiving (426), by the
NWDAF (114), a discovery response from the NRF (112), wherein the
discovery response comprises a list of a plurality of NF instances
corresponding to the at least one NF (116);
performing (428), by the NWDAF (114), a mapping for the received
plurality of NF instances corresponding to the at least one NF (116) in the
list;
subscribing (430), by the NWDAF (114), for load values
corresponding to the plurality of NF instances of the at least one NF (116)
in the mapping, to the NRF (112);
receiving (432), by the NWDAF (114), a response from the NRF
(112) after a predefined time period, wherein the response comprises load
values corresponding to the plurality of NF instances of the at least one NF
(116); and
sending (434), by the NWDAF (114), the response towards the
consumer NF (110).

2. The method (400B) as claimed in claim 1, wherein the subscription request
and the discovery request comprise at least one public land mobile network
(PLMN) identifier (ID) corresponding to the at least one NF (116) and a
network function type.

3. The method (400B) as claimed in claim 1, wherein the at least one NF (116)
is a service communication proxy (SCP).

4. The method (400B) as claimed in claim 1, wherein the list comprises NF
instances endpoints, NF instance IDs, NF instance names, NF service
names, and NF service statuses.

5. The method (400B) as claimed in claim 1, wherein the NWDAF (114) is
configured to fetch the plurality of NF instances of the at least one NF (116)
from the mapping.

6. The method (400B) as claimed in claim 1, wherein the load values are values
corresponding to load of the plurality of NF instances corresponding to the
at least one PLMN ID of the at least one NF (116).

7. A system (108) for reporting load data in a network, the system (108)
comprising a network data analytics function (NWDAF) (114), a network
function repository (NRF) (112), a consumer network function (NF) (110),
and a plurality of NFs (116), the NWDAF (114) comprising:
a receiving unit (212) configured to receive a subscription request
for load data of at least one network function (NF) (116) from the consumer
NF (110);
on receiving the subscription request, a sending unit (214) is
configured to send a discovery request for the at least one NF (116) to the
NRF (112);
in response to the discovery request, the receiving unit (212) is
configured to receive a discovery response from the NRF (112), wherein the
discovery response comprises a list of a plurality of NF instances
corresponding to the at least one NF (116);

a processing unit (216) configured to perform a mapping for the
received plurality of NF instances corresponding to the at least one NF (116)
in the list;
the processing unit (216) configured to subscribe for load values
corresponding to the plurality of NF instances of the at least one NF (116)
in the mapping, to the NRF (112);
the receiving unit (212) configured to receive a response from the
NRF (112) after a predefined time period, wherein the response comprises
load values corresponding to the plurality of NF instances of the at least one
NF (116); and
the sending unit (214) configured to send the response towards the
consumer NF (110).

8. The system (108) as claimed in claim 7, wherein the subscription request
comprise at least one public land mobile network (PLMN) identifier (ID)
corresponding to the at least one NF (116) and a network function type.

9. The system (108) as claimed in claim 7, wherein the at least one NF (116)
is a service communication proxy (SCP).

10. The system (108) as claimed in claim 7, wherein the list comprises NF
instances endpoints, NF instance IDs, NF instance names, NF service
names, and NF service statuses.

11. The system (108) as claimed in claim 7, wherein the processing unit (216)
is configured to fetch the plurality of NF instances of the at least one NF
(116) from the mapping.

12. The system (108) as claimed in claim 7, wherein the load values are values
corresponding to load of the plurality of NF instances corresponding to the
at least one PLMN ID of the at least one NF (116).

13. A user equipment (104) communicatively coupled with a system (108), the
coupling comprises steps of:
receiving, by the system (108), a connection request;
sending, by the system (108), an acknowledgment of the connection
request to the UE (104); and
transmitting a plurality of signals in response to the connection
request, wherein the system (108) is configured for performing load data
reporting in a network (106) as claimed in claim 7.