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 SHARING LOAD INFORMATION OF AN NF INSTANCE AND THE NF MICROSERVICES”
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 SHARING LOAD INFORMATION OF AN NF INSTANCE AND THE NF MICROSERVICES
FIELD OF THE DISCLOSURE
[0001] Embodiments of the present disclosure generally relate to the field of wireless communication system. More particularly, embodiments of the present disclosure relate to method and system for sharing load information of a network function (NF) instance and the NF microservices in a communication system.
BACKGROUND
[0002] The following description of 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 be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth-generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication

technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] In the 5G communication system, there are a plurality of network functions (NFs), for example an Access and Mobility Management Function (AMF), session management function (SMF), Authentication Server function (AUSF), a Network Slice Selection Function (NSSF), Policy control function (PCF), Network Repository Function (NRF), Network Data Analytics Function (NWDAF), Service Communication Proxy (SCP) and the like. One or more of the aforementioned NFs communicates with each other, to implement multiple activities on the 5G communication system. For example, for data transfer, the AMF communicates with SMF, to initiate the communication. Accordingly, one or more connections are established between two peer NFs, to allow communication therebetween, and thus enable such activities there between. Similarly, NWDAF communicates with other and NF functions for performing data analytics. NWDAF addresses some processes such as, data collection interface from network nodes, predefined analytics insights, and data exposure interface for consumers. Network Repository Function (NRF) works as a centralized repository for all the 5G network functions (NFs) in the network. The NRF allows 5G NFs to register and discover each other via a standards-based API. Service Communication Proxy (SCP) is a decentralized solution and composed of control plane and data plane. SCP Cluster is deployed as multiple microservices consisting of SCP Controller and SCP agent. SCP Controller manages all SCP agent Instances, provides the FCAPS functionality and communicates with NRF for NF Management and Discovery services. SCP agent Instances route HTTP2 traffic between 5GCN except for the NRF service traffic which is managed by Controller. It can work as an Egress or an Ingress Proxy. SCP is deployed along side of 5G Network Functions (NF) for providing routing control, resiliency, and observability to the core network.
[0005] In conventional method and solutions, SCP controller registers to NRF as a single NF with multiple SCP instances. Also, as SCP does not host any service,

there is no technique available for analysing and reporting SCP load analytics. Therefore, there is a need to find a way to report SCP instance load statistics. Similarly, there may be other NF nodes for which there is no prescribed way to report load analytics to the NWDAF.
[0006] Thus, there exists an imperative need in the art to provide a system and method of for sharing load information of a network function (NF) instance and the NF microservices in a communication system, which the present disclosure aims to address.
SUMMARY
[0007] 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.
[0008] An aspect of the present disclosure may relate to a method for sharing load information of a network function (NF) instance and the NF microservices in a communication system. The method includes receiving, by a Network Repository Function (NRF), a service discovery request from Network Data Analytics Function (NWDAF), wherein the service discovery request further comprises of one or more PLMN identifiers. Next, the method includes transmitting, by the NRF, the service discovery request based on the one or more PLMN identifiers to one or more network functions, wherein the one or more network functions are registered with the NRF, and each network function further comprises of one or more network function controllers and one or more network function microservices. Next, the method includes sending, by one or more network functions, a network profile data to the NRF, wherein the network profile data comprises of at least a load value of one or more network function controller and a load value of one or more network function microservices. Next, the method includes receiving, by the NRF, a status

update request from the NWDAF. Thereafter, the method includes sending, by the NRF, the network profile data to the NWDAF.
[0009] In an exemplary aspect of the present disclosure, at least one of the network function microservices are Service Communication Proxy (SCP), and the load value comprises operational statistics for each SCP.
[0010] In an exemplary aspect of the present disclosure, at least one of: the one or more network functions send the network profile data to the NRF in a heartbeat message, and wherein the heartbeat message is sent by the one or more network functions periodically.
[0011] In an exemplary aspect of the present disclosure, the network profile data comprises at least one of a service instance ID, IP endpoints, and allowed NF types for each network function microservice.
[0012] In an exemplary aspect of the present disclosure, the method comprises transmitting, by the NRF, an updated network profile data to the NWDAF upon change in load of the one or more network function controllers and the one or more network function microservices.
[0013] In an exemplary aspect of the present disclosure, the NWDAF utilizes the network profile data to predict scaling requirement for the one or more network functions based on the load value.
[0014] In an exemplary aspect of the present disclosure, predicting scaling requirement for the one or more network functions is performed based on an analysis of past load statistics generated using historical data associated with load on the one or more network functions.

[0015] In an exemplary aspect of the present disclosure, the method comprises storing, by the NWDAF, a real time data and a historical data of the network profile data in a memory; and displaying, by the NWDAF, at least one of the real time data and a historical data of the network profile data retrieved from the memory. 5
[0016] In an exemplary aspect of the present disclosure, the status update request comprises at least one of one or more attributes and a status of the one or more network function controllers and the one or more network function microservices.
10 [0017] Another aspect of the present disclosure may relate to a system for sharing
load information of a network function (NF) instance and the NF microservices in a communication system. The system comprising: a Network Repository Function (NRF) configured to receive a service discovery request from Network Data Analytics Function (NWDAF), wherein the service discovery request further
15 comprises of one or more PLMN identifiers. The system further comprising the
NRF configured to transmit the service discovery request based on the one or more PLMN identifiers to one or more network functions, wherein the one or more network functions are registered with the NRF, and each network function further comprises of one or more network function controllers and one or more network
20 function microservices. The system further comprising one or more network
functions configured to send a network profile data to the NRF, wherein the network profile data comprises of at least a load value of one or more network function controller and a load value of one or more network function microservices. The system further comprising the NRF configured to receive a status update request
25 from the NWDAF. The system further comprising the NRF configured to send the
network profile data to the NWDAF.
[0018] Yet another aspect of the present disclosure may relate to a non-transitory
computer readable storage medium storing instructions for sharing load information
30 of a network function (NF) instance and the NF microservices in a communication
system, the instructions include executable code which, when executed by one or
6

more units of a system, causes: a Network Repository Function (NRF) of the system
to receive a service discovery request from Network Data Analytics Function
(NWDAF), wherein the service discovery request further comprises of one or more
PLMN identifiers; the NRF of the system to transmit the service discovery request
5 based on the one or more PLMN identifiers to one or more network functions,
wherein the one or more network functions are registered with the NRF and each
network function further comprises of one or more network function controllers and
one or more network function microservices; one or more network functions of the
system to send a network profile data to the NRF, wherein the network profile data
10 comprises of at least a load value of one or more network function controller and a
load value of one or more network function microservices; the NRF of the system to receive a status update request from the NWDAF; and the NRF of the system to send the network profile data to the NWDAF.
15 OBJECTS OF THE PRESENT DISCLOSURE
[0019] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
20 [0020] It is an object of the present disclosure for providing method and system for
sharing/monitoring a 5G microservice load which is not a 3gpp defined microservice specifically for sharing load information to NWDAF via NRF.
[0021] It is another object of the present disclosure to provide a system and a
25 method for upscaling the microservice (e.g., SCP agent) by analysing and reporting
procedure for load distribution of the microservices.
DESCRIPTION OF DRAWINGS
[0022] The accompanying drawings, which are incorporated herein, and constitute
30 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
7

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
5 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.
10 [0023] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core (5GC) network architecture.
[0024] 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
15 exemplary implementation of the present disclosure.
[0025] FIG. 3 illustrates an exemplary block diagram of a system for sharing load
information of a network function (NF) instance and the NF microservices in a
communication system, in accordance with exemplary implementations of the
20 present disclosure.
[0026] FIG. 4 illustrates a method flow diagram for sharing load information of a network function (NF) instance and the NF microservices in a communication system in accordance with exemplary implementations of the present disclosure.
25
[0027] FIG. 5 illustrates an exemplary block diagram of a system for sharing load information of a network function (NF) instance (e.g., SCP instance) and the NF microservices (e.g., SCP microservice) in a communication system, in accordance with exemplary implementations of the present disclosure.
30
8

[0028] FIG. 6 illustrates a sequence flow diagram for sharing load information of a network function (NF) instance and the NF microservices in a communication system in accordance with exemplary implementations of the present disclosure.
5 [0029] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
10 [0030] 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
15 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.
[0031] The ensuing description provides exemplary embodiments only, and is not
20 intended to limit the scope, applicability, or configuration of the disclosure. Rather,
the ensuing description of the exemplary embodiments will provide those skilled in
the art with an enabling description for implementing an exemplary embodiment.
It should be understood that various changes may be made in the function and
arrangement of elements without departing from the spirit and scope of the
25 disclosure as set forth.
[0032] Specific details are given in the following description to provide a thorough
understanding of the embodiments. However, it will be understood by one of
ordinary skill in the art that the embodiments may be practiced without these
30 specific details. For example, circuits, systems, processes, and other components
9

may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
[0033] Also, it is noted that individual embodiments may be described as a process
5 which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure
diagram, or a block diagram. Although a flowchart may describe the operations as
a sequential process, many of the operations may be performed in parallel or
concurrently. In addition, the order of the operations may be re-arranged. A process
is terminated when its operations are completed but could have additional steps not
10 included in a figure.
[0034] 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
15 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
20 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.
[0035] As used herein, a “processing unit” or “processor” or “operating processor”
25 includes one or more processors, wherein processor refers to any logic circuitry for
processing instructions. A processor may be a general-purpose processor, a special
purpose processor, a conventional processor, a digital signal processor, a plurality
of microprocessors, one or more microprocessors in association with a (Digital
Signal Processing) DSP core, a controller, a microcontroller, Application Specific
30 Integrated Circuits, Field Programmable Gate Array circuits, any other type of
integrated circuits, etc. The processor may perform signal coding data processing,
10

input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
5 [0036] As used herein, “a user equipment”, “a user device”, “a smart-user-device”,
“a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The
10 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 of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of
15 a transceiver unit, a processing unit, a storage unit, a detection unit and any other
such unit(s) which are required to implement the features of the present disclosure.
[0037] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a
20 form readable by a computer or similar machine. For example, a computer-readable
medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective
25 functions.
[0038] 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
30 communication or interaction of one or more modules or one or more units with
11

each other, which also includes the methods, functions, or procedures that may be called.
[0039] All modules, units, components used herein, unless explicitly excluded
5 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
10 circuits (FPGA), any other type of integrated circuits, etc.
[0040] As used herein, Network Data Analytics Function (NWDAF) refers to a
component in the 5G network architecture designed to provide network analytics
services by collecting, analysing, and utilising data from various network functions
15 (NFs) to optimize network performance and management. NWDAF processes data
related to network usage, performance metrics, and load statistics, which helps in making informed decisions about network scaling, resource allocation, and quality of service (QoS) enhancements.
20 [0041] As used herein, IP endpoints refer to the distinct network addresses assigned
to devices or services within a communication network, facilitating the routing and delivery of data packets to their intended destinations. Each IP endpoint is identified by an IP address, which acts as a unique identifier in the network, enabling communication between different network functions, devices, and services.
25
[0042] As used herein, service instance identifier (ID) refers to a unique identifier assigned to a specific instance of a service within a network function (NF) or a microservice architecture. The identifier enables precise tracking and management of individual service instances, facilitating effective communication, load
30 balancing, and monitoring within the network.
12

[0043] As used herein, network function (NF) microservice refers to a modular and
independently deployable component of a network function (NF) within a
telecommunications network, particularly in a 5G architecture. The microservices
are designed to perform specific, discrete tasks within the overall functionality of
5 an NF, enabling greater flexibility, scalability, and resilience in network operations.
[0044] As used herein, network function controller refers to a component within
the 5G network infrastructure for managing and orchestrating various microservices
and operational tasks of a network function (NF). The network function controller
10 ensures that all associated microservices operate cohesively and efficiently,
handling tasks such as load balancing, resource allocation, and fault management.
[0045] As used herein, service discovery request refers to a communication mechanism within a network system where a network function (NF) seeks to
15 identify and locate other available network functions or services. The service
discovery request is sent to a Network Repository Function (NRF) or similar entity, which maintains a registry of all network functions and their capabilities. The service discovery request typically includes identifiers such as Public Land Mobile Network (PLMN) identifiers to limit the search to relevant network functions.
20
[0046] As used herein, network profile data refers to a dataset that encompasses various attributes and operational statistics of network functions (NFs) and their associated microservices within a communication system. The network profile includes details such as load values, service instance IDs, IP endpoints, allowed
25 network function types, and other relevant metrics that describe the current state
and capabilities of the NFs.
[0047] As used herein, historical data refers to the collected and archived information from past events, transactions, or activities over a period of time. 30
13

[0048] Real-time data refers to information that is collected, processed, and
available for immediate use as it is generated. This type of data is continuously
updated, providing current insights into the status and performance of systems or
processes.
5
[0049] As used herein, one or more attributes refers to characteristics or properties
used to describe and monitor entities within a system. Examples of attributes
include CPU usage, which measures the processing power consumed; memory
usage, indicating the amount of memory being utilized; network throughput,
10 reflecting the data transfer rate; and response time, showing how quickly the system
responds to requests.
[0050] As used herein the transceiver unit include at least one receiver and at least
one transmitter configured respectively for receiving and transmitting data, signals,
15 information, or a combination thereof between units/components within the system
and/or connected with the system.
[0051] As used herein, the network function (NF) instance may comprise one or
more NF controller and one or more NF microservices. The NF may have one or
20 more its instances for managing service traffic load in communication network. The
NF instances may share load distribution for smooth traffic management.
[0052] As used herein, public land mobile network (PLMN) is a combination of
wireless communication services offered by a specific network service operator in
25 a specific country. The PLMN may be recognised by assigning globally unique
PLMN identifier. The PLMN identifier may comprise consists Mobile Country Code (MCC) and Mobile Network Code (MNC).
[0053] As used herein, PLMN identifier refers to a unique identifier associated with
30 the PLMN.
14

[0054] As used herein, heartbeat (HB) message refers to a polling message, which is sent periodically or at preconfigured time for sending or receiving any pre-configured attributes or parameters update in the communication network.
5 [0055] As used herein, allowed NF types refer to the network functions that are
permitted to interact with or be served by a particular network service or
microservice. For example, in a communication network, an SCP (Service
Communication Proxy) might be configured to handle requests from certain types
of network functions such as AMF (Access and Mobility Management Function),
10 SMF (Session Management Function), or UPF (User Plane Function).
[0056] 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
15 method and system of sharing load information of a network function (NF) instance
and the NF microservices in a communication system.
[0057] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture, in accordance with exemplary
20 implementation of the present disclosure. As shown in FIG. 1, the 5GC network
architecture [100] includes a user equipment (UE) [102], a radio access network (RAN) [104], an access and mobility management function (AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific
25 Authentication and Authorization Function (NSSAAF) [114], a Network Slice
Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122], a Unified Data Management (UDM) [124], a Network Data Analytics Function (NWDAF) [126], a User Plane Function (UPF) [128], a data network (DN) [130],
30 an application function (AF) [132], wherein all the components are assumed to be
15

connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.
[0058] Radio Access Network (RAN) [104] is the part of a mobile
5 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 wireless communication.
10 [0059] 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 procedures like handovers and paging.
15 [0060] 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.
20 [0061] 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.
25 [0062] 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.
[0063] Network Slice Specific Authentication and Authorization Function
30 (NSSAAF) [114] is a network function that provides authentication and
16

authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized.
[0064] Network Slice Selection Function (NSSF) [116] is a network function
5 responsible for selecting the appropriate network slice for a UE based on factors
such as subscription, requested services, and network policies.
[0065] Network Exposure Function (NEF) [118] is a network function that exposes
capabilities and services of the 5G network to external applications, enabling
10 integration with third-party services and applications.
[0066] Network Repository Function (NRF) [120] is a network function that acts as a central repository for information about available network functions and services. It facilitates the discovery and dynamic registration of network functions. 15
[0067] 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.
20 [0068] Unified Data Management (UDM) [124] is a network function that
centralizes the management of subscriber data, including authentication, authorization, and subscription information.
[0069] Network Data Analytics Function (NWDAF) [126] is a network function
25 that collects data from different network functions, application functions,
operations, administration for the load or performance analysis and generates the report based on the analysis.
[0070] User Plane Function (UPF) [128] is a network function responsible for
30 handling user data traffic, including packet routing, forwarding, and QoS
enforcement.
17

[0071] Data Network (DN) [130] refers to a network that provides data services to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services. 5
[0072] Application Function (AF) [132] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.
10 [0073] FIG. 2 illustrates an exemplary block diagram of a computing device [200]
(also referred to herein as a computer system [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 sharing load information of a
15 network function (NF) instance and the NF microservices in a communication
system utilising the system. In another implementation, the computing device [200] itself implements the method for sharing load information of a network function (NF) instance and the NF microservices in a communication system using one or more units configured within the computing device [200], wherein said one or more
20 units are capable of implementing the features as disclosed in the present disclosure.
[0074] The computing device [200] may include a bus [202] or other communication mechanism for communicating information, and a processor [204] coupled with bus [202] for processing information. The processor [204] may be, for
25 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
30 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
18

[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
storage device coupled to the bus [202] for storing static information and
5 instructions for the processor [204].
[0075] 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 instructions. The computing device [200] may be coupled via the bus [202] to a
10 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 bus [202] for communicating information and command selections to the processor
15 [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 of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow
20 the device to specify positions in a plane.
[0076] 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
25 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,
30 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
19

process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
5 [0077] 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 integrated services digital network (ISDN) card, cable modem, satellite modem, or
10 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 implementation, the communication interface [218] sends and receives electrical,
15 electromagnetic, or optical signals that carry digital data streams representing
various types of information.
[0078] The computing device [200] can send messages and receive data, including program code, through the network(s), the network link [220] and the
20 communication interface [218]. In the Internet example, a server [230] might
transmit a requested code for an application program through the Internet [228], the ISP [226], the local network [222], 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
25 execution.
[0079] The computing device [200] encompasses a wide range of electronic
devices capable of processing data and performing computations. Examples of
computing device [200] include, but are not limited only to, personal computers,
30 laptops, tablets, smartphones, servers, and embedded systems. The devices may
operate independently or as part of a network and can perform a variety of tasks
20

such as data storage, retrieval, and analysis. Additionally, computing device [200] may include peripheral devices, such as monitors, keyboards, and printers, as well as integrated components within larger electronic systems, showcasing their versatility in various technological applications. 5
[0080] Referring to FIG. 3, an exemplary block diagram of a system [300] for sharing load information of a network function (NF) instance and the NF microservices in a communication system, is shown, in accordance with the exemplary implementations of the present disclosure. The system [300] comprises
10 at least one Network Repository Function (NRF) [120], at least one Network Data
Analytics Function (NWDAF) [126], at least one Graphical User Interface (GUI) [312], at least one Network Function (NF) [306], which further comprises: one or more NF controllers [308] and one or more NF Microservices [310]. Also, all of the components/ units of the system [300] are assumed to be connected to each
15 other unless otherwise indicated below. As shown in the figures all units shown
within the system should also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however, the system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure.
20
[0081] The system [300] is configured for sharing load information of a network function (NF) instance and the NF microservices in a communication system, with the help of the interconnection between the components/units of the system [300].
25 [0082] The system [300] comprises a network repository function (NRF) [120].
The NRF [120] is configured to receive a service discovery request from network data analytics function (NWDAF) [126], wherein the service discovery request further comprises of one or more PLMN identifiers for example, 4050 is PLMN id for West Bengal, 4054 for Maharashtra and 4057 for Punjab. The NRF [120] of the
30 system [300] may receive the service discovery request from the NWDAF [126].
The service discovery request further comprises one or more PLMN identifiers
21

(IDs). The NWDAF [126] may send request (such as Nnrf_NFDiscover request) with PLMN IDs to the NRF [120] to get the load information of the NF(s) with the requested PLMN IDs. In an exemplary aspect, the NWDAF [126] may also send the NF type with the service request to get the load information. 5
[0083] The load information of a Network Function (NF) refers to the current operational state and resource usage details of that NF. Each NF will calculate its own Load whose value can be from (0-100) in terms of percentage or absolute value on the basis of the various factors like: 10
[0084] CPU Usage: The percentage of CPU resources currently being utilized by the NF. High CPU usage can indicate high load or potential bottlenecks.
[0085] Memory Usage: The amount of RAM being consumed by the NF. Memory
15 usage is a critical factor for the performance and stability of the NF.
[0086] Network Throughput: The rate of data being processed by the NF. This includes the amount of incoming and outgoing traffic handled by the NF.
20 [0087] Session Count: The number of active sessions being managed by the NF.
This helps in understanding the current load in terms of user or service sessions.
[0088] The NRF [120] of the system [300] is further configured to transmit the service discovery request based on the one or more PLMN identifiers to one or
25 more NFs [306], wherein the one or more NFs [306] are registered with the NRF
[120] and each network function further comprises of one or more network function controllers [308] and one or more network function microservices [310]. In response to the receiving the service discovery request from the NWDAF [126], the NRF [120] may transmit the service discovery request based on the one or more
30 PLMN IDs to the one or more NF(s) [306]. The one or more NF(s) [306] are
registered with the NRF [120] and each NF further comprises of one or more NF
22

controller(s) [308] and one or more NF microservice(s) [310]. The NRF [120] acts
as depository in the communication system such as 5G system. The NRF [120]
stores all components or NF(s) details of the communication system. In an
exemplary aspect a NF may have plurality of instances as defined by the network
5 administrator or service provider. Each instance of the NF may have one or more
controller(s) and one or more microservice(s). In an exemplary implementation, NF may have one controller, which manage all the defined instances of that NF. In an exemplary aspect, the network function may be, such as, but not limited to, SCP [110], SMF [108], NSSF [116], and the like. In an exemplary aspect, the NRF [120]
10 may transmit the service discovery request based on the one or more PLMN
identifiers for the requested NF type in the service discovery request.
[0089] The system [300] further comprises one or more network functions (NFs) [306] configured to send a network profile data to the NRF [120], wherein the network profile data comprises of at least a load value of one or more network
15 function controllers [308] and a load value of one or more network function
microservices [310]. In response to the receiving the service discovery request from the NRF [120], the one or more NFs [306] may send the network profile data to the NRF [120]. The network profile data may comprise of at least a load value of one or more NF controller(s) [308] and a load value of one or more NF microservice(s)
20 [310]. In an exemplary aspect, at least one of: the one or more network function
microservices [310] corresponds to Service Communication Proxy (SCP) [110], and the load value comprises operational statistic for the SCP [110]. The operational statistics refer to quantifiable data that reflects performance, usage, and efficiency of a system or component within a network. For example, in a network function
25 such as SCP, operational statistics could include metrics such as CPU utilization,
memory usage, network throughput, response times, and error rates. The network profile data comprises at least one of a service instance ID, IP endpoints, and allowed NF types for each network function (NF) microservice(s). In an exemplary aspect, at least one of the one or more NFs [306] is further configured to send the
30 network profile data to the NRF [120] in a heartbeat message, and wherein the
heartbeat message is sent by the one or more NFs [306] periodically. In an
23

implementation, the load value may represent the current usage and consumption of resources such as hardware or software and traffic flow for service operation.
[0090] In response to the receiving the network profile data comprising of at least
5 the load value of one or more NF controller(s) [308] and the load value of one or
more NF microservice(s) [310] from the one or more NF(s), the NRF [120] may
send the network profile data to the NWDAF [126]. The NWDAF [126] may utilize
the network profile data to predict scaling requirement for the one or more NFs
[306] based on the load value. In an exemplary aspect, the prediction of the scaling
10 requirement for the one or more NFs [306] is performed based on an analysis of
past load statistics generated using historical data associated with load on the one or more NFs [306].
[0091] The NRF [120] of the system [300] is further configured to receive a status
15 update request from the NWDAF [126]. Further in an operation, the NRF [120]
may receive the status update request from the NWDAF [126]. The status update
request may comprise at least one of one or more attributes and a status of the one
or more network function controller(s) [308] and the one or more network function
microservice(s) [310]. In an exemplary aspect, the attributes may be such as, but
20 not limited to load capacity, load consumption and the like.
[0092] The NRF [120] of the system [3000] is further configured to send the network profile data to the NWDAF [126]. In response to the receiving status update request from the NWDAF [126], the NRF [120] may send the network
25 profile data to the NWDAF [126]. The network profile data may comprise such as,
but not limited to, at least one of load value, load capacity limit and the like. In an exemplary aspect, the NRF [120] may transmit an updated network profile data to the NWDAF [126] upon change in load of the one or more network function controllers [308] and the one or more network function microservices [310].
30
24

[0093] Further, the NWDAF [126] after receiving the network profile data from the NRF [120] may store a real time data and a historical data of the network profile data in a memory; and display at least one of the real time data network profile data and the historical data network profile data retrieved from the memory. 5
[0094] The system [300] comprises a graphical user interface (GUI) [312]. The GUI [312] may be a part of, such as, human machine interface (HMI), computing device, mobile device, and the like. The GUI [312] may display the collected network profile data associated with the network function(s). The GUI [312] may
10 also display the NWDAF [126] scaling prediction need based on the load
consumption of the NF(s). The NWDAF [126] collects load data (such as load values) from various network functions (NFs) and their microservices. The load values include metrics such as CPU usage, memory consumption, and network traffic, reflecting the current operational load. Next, the NWDAF [126] stores the
15 load values in the database. The database maintains both real-time load data and
historical load data. The NWDAF [126] analyses the historical load data to identify patterns and trends in network usage, such as peak traffic times or consistent growth or reduction in resource consumption. The NWDAF [126] may utilise artificial intelligence (AI) or machine learning (ML) based model to predict future load
20 values. Based on the predicted future load values, NWDAF [126] can determine
when additional resources or scaling actions are required to maintain optimal network performance. For example, if the analysis predicts a significant increase in load during specific periods, NWDAF [126] can recommend adding more SCP proxies or increasing capacity in certain areas of the network such as deploying
25 additional SCP proxies or increasing network capacity in specific areas.
[0095] Further, in accordance with the present disclosure, it is to be acknowledged
that the functionality described for the various the components/units can be
implemented interchangeably. While specific embodiments may disclose a
30 particular functionality of these units for clarity, it is recognized that various
configurations and combinations thereof are within the scope of the disclosure. The
25

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
5 of the present disclosure.
[0096] Referring to FIG. 4, an exemplary method flow diagram [400] for sharing
load information of a network function (NF) instance and the NF microservices in
a communication system, in accordance with exemplary implementations of the
10 present disclosure is shown. In an implementation the method [400] is performed
by the system [300]. Further, in an implementation, the system [300] may be present in a server device to implement the features of the present disclosure. Also, as shown in Figure 4, the method [400] starts at step [402].
15 [0097] At step [404], the method [400] as disclosed by the present disclosure
comprises receiving, by a Network Repository Function (NRF) [120], a service discovery request from Network Data Analytics Function (NWDAF) [126], wherein the service discovery request further comprises of one or more PLMN identifiers. The method [400] implemented by the NRF [120] of the system [300]
20 may receive the service discovery request from network data analytics function
(NWDAF) [126]. The service discovery request further comprises one or more PLMN identifiers (IDs). The NWDAF [126] may send Nnrf_NFDiscover request with PLMN IDs to the NRF [120] to get the load information of the NF(s) with the requested PLMN IDs. In an exemplary aspect, the NWDAF [126] may also send
25 any desired NF type with the service request to get the load information.
[0098] Next, at step [406], the method [400] as disclosed by the present disclosure
comprises transmitting, by the NRF [120], the service discovery request based on
the one or more PLMN identifiers to one or more NFs [306], wherein the one or
30 more network functions are registered with the NRF [120] and each network
function further comprises of one or more network function controllers [308] and
26

one or more network function microservices [310]. The method [400] implemented
by the NRF [120] of the system [300] may further, in response to the receiving the
service discovery request from the NWDAF [126], transmit the service discovery
request based on the one or more PLMN IDs to the one or more NF(s) [306]. The
5 one or more NF(s) [306] are registered with the NRF [120] and each NF further
comprises of one or more NF controller(s) [308] and one or more NF microservice(s) [310]. The NRF [120] acts as depository in the communication system such as 5G system. The NRF [120] stores all components or NF(s) details of the communication system. In an exemplary aspect a NF may have plurality of
10 instances as defined by the network administrator or service provider. Each instance
of the NF may have one or more controller(s) and one or more microservice(s). In an exemplary implementation, NF may have one controller, which manage all the defined instances of that NF. In an exemplary aspect, the network function may be, such as, but not limited to, SCP [110], SMF [108], NSSF [116], and the like. In an
15 exemplary aspect, the NRF [120] may transmit the service discovery request based
on the one or more PLMN identifiers for the requested NF type in the service discovery request.
[0099] Next, at step [408], the method [400] as disclosed by the present disclosure
20 comprises sending, by one or more NFs [306], a network profile data to the NRF
[120], wherein the network profile data comprises of at least a load value of one or
more network function controllers [308] and a load value of one or more network
function microservices [310]. In response to the receiving the service discovery
request from the NRF [120], the one or more NFs [306] may send the network
25 profile data to the NRF [120]. The network profile data may comprise of at least a
load value of one or more NF controller(s) [308] and a load value of one or more
NF microservice(s) [310]. In an exemplary aspect, at least one of: the one or more
network function microservices [310] corresponds to Service Communication
Proxy (SCP) [110], and the load value comprises operational statistic for the SCP
30 [110]. The network profile data comprises at least one of a service instance ID, IP
endpoints, and allowed NF types for each network function (NF) microservice(s).
27

In an exemplary aspect, at least one of the one or more NFs [306] is further
configured to send the network profile data to the NRF [120] in a heartbeat message,
and wherein the heartbeat message is sent by the one or more NFs [306]
periodically. In an implementation, the load value may represent the current usage
5 and consumption of resources such as hardware or software and traffic flow for
service operation.
[0100] In response to the receiving the network profile data comprising of at least the load value of one or more NF controller(s) [308] and the load value of one or
10 more NF microservice(s) [310] from the one or more NF(s), the NRF [120] may
send the network profile data to the NWDAF [126]. The NWDAF [126] may utilize the network profile data to predict scaling requirement for the one or more NFs [306] based on the load value. In an exemplary aspect, the prediction of the scaling requirement for the one or more NFs [306] is performed based on an analysis of
15 past load statistics generated using historical data associated with load on the one
or more NFs [306].
[0101] Next, at step [410], the method [400] as disclosed by the present disclosure comprises receiving, by the NRF [120], a status update request from the NWDAF
20 [126]. The method [400] implemented by the NRF [120] of the system [300] may
further receive the status update request from the NWDAF [126]. The status update request may comprise at least one of one or more attributes and a status of the one or more network function controller(s) [308] and the one or more network function microservice(s) [310]. In an exemplary aspect, the attributes may be such as, but
25 not limited to load capacity, load consumption and the like.
[0102] Next, at step [412], the method [400] as disclosed by the present disclosure
comprises sending, by the NRF [120], the network profile data to the NWDAF
[126]. The method [400] implemented by the NRF [120] of the system [300] may
30 further, in response to the receiving status update request from the NWDAF [126],
send the network profile data to the NWDAF [126]. The network profile data may
28

comprise such as, but not limited to, at least one of load value, load capacity limit
and the like. In an exemplary aspect, the NRF [120] may transmit an updated
network profile data to the NWDAF [126] upon change in load of the one or more
network function controllers [308] and the one or more network function
5 microservices [310].
[0103] Further, the NWDAF [126] after receiving the network profile data from the
NRF [120] may store a real time data and a historical data of the network profile
data in a memory; and display at least one of the real time data network profile data
10 and the historical data network profile data retrieved from the memory.
[0104] The system [300] comprises a graphical user interface (GUI) [312]. The
GUI [312] may be a part of, such as, human machine interface (HMI), computing
device, mobile device, and the like. The GUI [312] may display the collected
15 network profile data associated with the network function(s). The GUI [312] may
also display the NWDAF [126] scaling prediction need based on the load consumption of the NF(s).
[0105] Thereafter, the method [400] terminates at step [414].
20
[0106] FIG. 5 illustrates an exemplary block diagram of a system [500] for sharing load information of a network function (NF) instance (e.g., SCP instance) and the NF microservices (e.g., SCP microservice) in a communication system, in accordance with exemplary implementations of the present disclosure. As shown in
25 FIG. 5, the system [500] comprises at least one Network Repository Function
(NRF) [120], at least one Network Data Analytics Function (NWDAF) [126], at least one Graphical User Interface (GUI) [312], and at least one network function, such as Service Communication Proxy (SCP) [110], which further comprises: at least one SCP Controller [508] and at least one SCP Microservice or SCP Agent
30 [510]. In an exemplary aspect, SCP Agent [510] may represent a plurality of the
SCP Agent(s), such as (SCP1 [510a], SCP2 [510b]….SCPn [510n]) (collectively
29

referred to as SCP [510] or SCP agent [510] and individually referred to as SCP [510] or SCP agent [510] herein).
[0107] The SCP controller [508] and SCP Agent [510] may store load information
5 into the NRF [120]. The SCP controller [508] and SCP Agent [510] may register
and share load as a single SCP [110] instance. The SCP controller [508] may share its load and load of the SCP Agent [510] in a load profile to the NRF [120]. In an exemplary aspect, the SCP controller [508] may send load information in a heartbeat message to the NRF [120].
10
[0108] In an operation, the NWDAF [126] may get load data of SCP [110] from NRF [120] by using service (such as NFStatusSubscribe). The NRF [120] may share the load data with the NWDAF [126] in a fixed time interval defined at NRF [120] (such as LoadNotificationTimer). The NRF [120] may report the service level
15 load information towards NWDAF [126]. Further, the monitored attribute is set to
configuration (e.g., “/nfservices/0/load” or “/nfservices/load”). Subsequently, in subscribe request, it may allow NRF [120] to send the notification of load events at predefined intervals, which may also include service level load if included by SCP [110]. In an exemplary aspect, the NWDAF [126] may send
20 multiple subscribe requests to get service level load information.
"/nfservices/0/load" or "/nfservices/load" refers to monitored attributes within a network function's profile. The notation "/nfservices/0/load" or "/nfservices/load" is used to identify and monitor the load on services within a network function (NF) profile. The "/nfservices/0/load" refers to
25 the load of the first service instance within the NF profile, while
"/nfservices/load" allows for identification and monitoring of the load on a service instance by its unique identifier.
[0109] In an exemplary aspect, when load is sent outside the heartbeat (HB), it may
30 be considered as a normal profile change event, thus all NFs including NWDAF
[126] which have subscribed to SCP may also receive the profile change
30

notification. Further, if any other parameters such as other than nfstatus, load, and
service level load are sent by SCP [110] in the HB, then it may also be considered
as a Profile Update. The NWDAF [126] may use NFDiscovery operation to get the
SCP controller [508] load and SCP Agent [510] load with its service instance ids in
5 the NF profile and thus it can map the service instance ID to service. Further, in
case of a status change of service or addition or removal of service, NRF [120] may send the full notification to the NWDAF [126] even though NWDAF [126] has only subscribed to SCP Load or Service Level load.
10 [0110] FIG. 6 illustrates a sequence flow [600] diagram for sharing load
information of a network function (NF) instance and the NF microservices in a communication system in accordance with exemplary implementations of the present disclosure. As shown in FIG. 6, sequence flow [600] diagram comprises a NWDAF [126], a NWDAF DB [602], a NRF [120], one or more NFs [306] and a
15 dashboard [604].
[0111] At step [1A], the sequence flow [600] as disclosed by the present disclosure
comprises sending, by NWDAF [126], a request (such as Nnrf_NFDiscovery)
(nftype=any NF), PLMN id to local NRF [120]. The request includes the type of
20 network function (nftype=any NF) and the Public Land Mobile Network (PLMN)
identifier. The request (such as Nnrf_NFDiscovery), initiates the discovery process for network functions that match the criteria specified in the request.
[0112] Next, at step [1B], the sequence flow [600] as disclosed by the present
25 disclosure comprises sending, by NRF [120], a response (such as
Nnrf_NFDiscoveryResponse) (NF Profile) for each PLMN mapped to the requesting NWDAF [126]. The response includes the NF profiles for each PLMN mapped to the requesting NWDAF. An NF profile contains information associated with the network functions, such as their capability and corresponding status. 30
31

[0113] Further, at step [2], the sequence flow [600] as disclosed by the present
disclosure comprises sending, by the one or more NFs [306], load value of NF
instance in load of NF instance and load of microservices in nfservices in nfprofile
in NFRegister to NRF [120]. The load information includes both the load of the NF
5 instances and the load of the one or more microservices, encapsulated within the
NF profile. The transmission occurs during the NF registration process (such as NFRegister).
[0114] Further, as shown at step [3], the sequence flow [600] as disclosed by the
10 present disclosure comprises receiving, by the NRF [120], a subscription request
(such as Nnrf_NFManagement_NFStatus_subscribe), i.e., monitored attributes
from the NWDAF [126]. The monitored attributes include the load of the NF
instance and the load of the microservices as well as the status of the NF instance
of the microservice, wherein status may be one of registered, deregistered, and
15 suspended.
[0115] Further, as shown in step [4], the sequence flow [600] as disclosed by the
present disclosure comprises sending, by the one or more NFs [306], load value of
the NF instance and load value of the NF microservices to the NRF [120] with
20 timestamp in every nth heartbeat. The number n may be configurable at the NF
[306].
[0116] Next, at step [5], the sequence flow [600] as disclosed by the present
disclosure comprises sending, by the NRF [120], a notification (such as
25 Nnrf_NFManagement_NF Status_Notify), i.e., first complete NF profile with NF
load and nfservice with microservices load value to the NWDAF [126]. The notification includes the NF profile with load values for both the NF instances and their corresponding microservices.
30 [0117] Subsequently, at step [6], the sequence flow [600] as disclosed by the
present disclosure comprises sending, by the NRF [120], notification (such as
32

Nnrf_NFManagement_NF Status_Notify) for NF Profile Changed only with new NF load may be sent from the NRF [120] to the NWDAF [126]. At this step complete profile is not sent. Step (6) only includes the new load values, not the complete NF profile.
[0118] Also, at step [7], the sequence flow [600] as disclosed by the present disclosure comprises storing, by the NWDAF [126], real time data and historical data in NWDAF DB [602].
[0119] Further, at step [8], the sequence flow [600] as disclosed by the present disclosure comprises retrieving by the dashboard [604], real time data from the NWDAF DB [602] for displaying the information. The past load statistics may also be available to be shown at the dashboard [604] by fetching the historical data from the NWDAF DB [602].
[0120] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for sharing load information of a network function (NF) instance and the NF microservices in a communication system, the instructions include executable code which, when executed by one or more units of a system, causes: a Network Repository Function (NRF) [120] of the system to receive a service discovery request from Network Data Analytics Function (NWDAF) [126], wherein the service discovery request further comprises of one or more PLMN identifiers; the NRF [120] of the system to transmit the service discovery request based on the one or more PLMN identifiers to one or more NFs [306], wherein the one or more NFs [306] are registered with the NRF [120] and each network function further comprises of one or more network function controllers [308] and one or more network function microservices [310]; one or more NFs [306] of the system to send a network profile data to the NRF [120], wherein the network profile data comprises of at least a load value of one or more network function controllers [308] and a load value of one or more network function microservices [310]; the NRF [120] of the system to receive a status update request

from the NWDAF [126]; and the NRF [120] of the system to send the network profile data to the NWDAF [126].
[0121] As is evident from the above, the present disclosure provides a technically advanced solution for providing method and system for sharing NF instance load information to NWDAF via NRF. In the proposed method and system, the NF registers as a single NF with multiple NF microservices. The NF load may be sent in a load of Nfprofile. Further, each agent has a domain, IP endpoint, and allowed NF types similar to a nfservice, customization can be done, and each agent can be registered as a service, where each agent reports its service instance id, and its initial load value.
[0122] While considerable emphasis has been placed herein on the disclosed embodiments, it will be appreciated that many embodiments can be made and that many changes can be made to the embodiments without departing from the principles of the present disclosure. These and other changes in the embodiments of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

I/We Claim:
1. A method for sharing load information of a network function (NF) instance and
NF microservices in a communication system, the method comprising:
- receiving, by a Network Repository Function (NRF) [120], a service discovery request from Network Data Analytics Function (NWDAF) [126], wherein the service discovery request further comprises of one or more Public Land Mobile Network (PLMN) identifiers;
- transmitting, by the NRF [120], the service discovery request based on the one or more PLMN identifiers to one or more NFs [306], wherein the one or more network functions are registered with the NRF [120] and each network function further comprises of one or more network function controllers [308] and one or more network function microservices [310];
- sending, by one or more NFs [306], a network profile data to the NRF [120], wherein the network profile data comprises of at least a load value of one or more network function controllers [308] and a load value of one or more network function microservices [310];
- receiving, by the NRF [120], a status update request from the NWDAF [126]; and
- sending, by the NRF [120], the network profile data to the NWDAF [126].

2. The method as claimed in claim 1, wherein at least one of: the network function microservices [310] are Service Communication Proxy (SCP), and the load value comprises operational statistics for each SCP.
3. The method as claimed in claim 1, wherein at least one of: the one or more network functions [306] send the network profile data to the NRF [120] in a heartbeat message, and wherein the heartbeat message is sent by the one or more network functions [306] periodically.

4. The method as claimed in claim 1, wherein the network profile data comprises at least one of a service instance ID, IP endpoints, and allowed NF types for each network function microservice.
5. The method as claimed in claim 1, the method further comprising transmitting, by the NRF [120], an updated network profile data to the NWDAF [126] upon change in load of the one or more network function controllers [308] and the one or more network function microservices [310].
6. The method as claimed in claim 1, wherein the NWDAF [126] utilizes the network profile data to predict scaling requirement for the one or more network functions [306] based on the load value.
7. The method as claimed in claim 6, wherein predicting scaling requirement for the one or more network functions [306] is performed based on an analysis of past load statistics generated using historical data associated with load on the one or more network functions [306].
8. The method as claimed in claim 1, the method further comprising:

- storing, by the NWDAF [126], a real time data and a historical data of the network profile data in a memory; and
- displaying, by the NWDAF [126], at least one of the real time data and the historical data of the network profile data retrieved from the memory.

9. The method as claimed in claim 1, wherein the status update request comprises at least one of one or more attributes and a status of the one or more network function controllers [308] and the one or more network function microservices [310].
10. A system for sharing load information of a network function (NF) instance and NF microservices in a communication system, the system comprising:

- a Network Repository Function (NRF) [120] configured to receive a service discovery request from Network Data Analytics Function (NWDAF) [126], wherein the service discovery request further comprises of one or more PLMN identifiers;
- the NRF [120] configured to transmit the service discovery request based on the one or more PLMN identifiers to one or more NFs [306], wherein the one or more NFs [306] are registered with the NRF [120] and each network function further comprises of one or more network function controllers [308] and one or more network function microservices [310];
- one or more NFs [306] configured to send a network profile data to the NRF [120], wherein the network profile data comprises of at least a load value of one or more network function controllers [308] and a load value of one or more network function microservices [310];
- the NRF [120] configured to receive a status update request from the NWDAF [126]; and
- the NRF [120] configured to send the network profile data to the NWDAF [126].

11. The system as claimed in claim 10, wherein at least one of: the one or more network function microservices [310] corresponds to Service Communication Proxy (SCP) [110], and the load value comprises operational statistic for the SCP [110].
12. The system as claimed in claim 10, wherein at least one of: the one or more network functions [306] is further configured to send the network profile data to the NRF [120] in a heartbeat message, and wherein the heartbeat message is sent by the one or more network functions [306] periodically.
13. The system as claimed in claim 10, wherein the network profile data comprises at least one of a service instance ID, IP endpoints, and allowed NF types for each network function microservice.

14. The system as claimed in claim 10, wherein the NRF [120] is configured to transmit an updated network profile data to the NWDAF [126] upon change in load of the one or more network function controllers [308] and the one or more network function microservices [310].
15. The system as claimed in claim 10, wherein the NWDAF [126] utilizes the network profile data to predict scaling requirement for the one or more network functions [306] based on the load value.
16. The system as claimed in claim 15, wherein the prediction of the scaling requirement for the one or more network functions [306] is performed based on an analysis of past load statistics generated using historical data associated with load on the one or more network functions [306].
17. The system as claimed in claim 10, wherein the NWDAF [126] is further configured to:

- store a real time data and a historical data of the network profile data in a memory; and
- display at least one of the real time data network profile data and the historical data of the network profile data retrieved from the memory.
18. The system as claimed in claim 10, wherein the status update request comprises
at least one of one or more attributes and a status of the one or more network
function controllers [308] and the one or more network function microservices
[310].