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 INITIATING LOAD ATTRIBUTE NOTIFICATION SCHEDULING FROM A NETWORK REPOSITORY FUNCTION (NRF)”
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 INITIATING LOAD ATTRIBUTE NOTIFICATION SCHEDULING FROM A NETWORK REPOSITORY FUNCTION (NRF)
TECHNICAL FIELD
[0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to methods and systems for initiating a load attribute notification scheduling from a Network Repository Function (NRF).
BACKGROUND
[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. The third-generation (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] A Network Function Repository (NRF) is a component within the telecommunications network that serves as a central repository that maintains information about one or more available network functions (NFs) and their corresponding network locations. The NRF
2

facilitates a dynamic identification and selection of network functions for establishing and maintaining one or more communication sessions. In the context of the NRF, there exists a need to effectively manage, and schedule notifications triggered by changes in monitored attributes. Current known solutions typically initiate notifications immediately upon the change of an attribute value when a subscription is created at the NRF.
[0005] However, when monitoring a load attribute in a NF-profile/NF-service profile, there arises a requirement for more advanced scheduling options. The NRF should possess the capability to set the frequency of corresponding notifications in terms of time or threshold, enabling the timely and organized initiation of notifications based on the monitoring requirements rather than triggering them instantly.
[0006] Further, over the period of time, various solutions have been developed to improve the performance of communication devices and to optimize scheduling a notification at the network repository function (NRF). However, there are certain challenges with existing solutions. One significant limitation is the lack of granularity in scheduling options. Current solutions primarily offer a binary approach, where a notification is either initiated instantly upon a change in the attribute value or not at all. This lack of fine-grained control restricts the ability to tailor the notification delivery to specific conditions or thresholds associated with the monitored attribute. Another technical limitation is the inability to handle complex scheduling scenarios.
[0007] Existing solutions often lack the capability to handle intricate scheduling patterns, such as recurring notifications at specific intervals or time-based schedules that depend on multiple attributes and/or conditions. These limitations prevent users from efficiently managing and organizing notifications according to their specific requirements and preferences. Thus, there exists a need for method and system for initiating a load attribute notification scheduling from a Network Repository Function (NRF).
SUMMARY
[0008] 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.

[0009] An aspect of the present disclosure may relate to a method for initiating a load attribute notification scheduling from a Network Repository Function (NRF). The method comprising receiving, by a transceiver unit from a Network Data Analytics Function (NWDAF) at the NRF, a subscription request associated with one or more network functions, wherein the subscription request comprises at least a load attribute and a threshold associated with the load attribute. The method comprises identifying, by a processing unit at the NRF, a target network function (NF) from the one or more network functions based on the load attribute. The method comprises generating, via the processing unit by the NWDAF at the NRF, a load attribute subscription associated with the target NF based on at least the load attribute. The method comprises receiving, via the transceiver unit at the NRF from the target NF, a load attribute value. The method comprises detecting, via the processing unit at the NRF, a positive load attribute enable monitoring notification based on the load attribute value. The method comprises detecting, via the processing unit at the NRF, a load attribute timer value based on the positive load attribute enable monitoring notification. The method comprising initiating, via the processing from the NRF to the NWDAF, the load attribute notification scheduling associated with the load attribute based on at least one of the load attribute timer value and the threshold associated with the load attribute.
[0010] In an exemplary aspect of the present disclosure, the threshold associated with the load attribute is at least one of a predefined threshold and a dynamically defined threshold.
[0011] In an exemplary aspect of the present disclosure, the identifying the target network function is further based on the threshold associated with the load attribute.
[0012] In an exemplary aspect of the present disclosure, the subscription request further comprises a network function type.
[0013] In an exemplary aspect of the present disclosure, generating the load attribute subscription associated with the target NF is further based on the network function type.
[0014] In an exemplary aspect of the present disclosure, the load attribute value is received in a heartbeat request.

[0015] Another aspect of the present disclosure may relate to a system for initiating a load attribute notification scheduling from a Network Repository Function (NRF). The system comprises a transceiver unit, wherein the transceiver unit is configured to receive, from a Network Data Analytics Function (NWDAF) at the NRF, a subscription request associated with one or more network functions, wherein the subscription request comprises at least a load attribute and a threshold associated with the load attribute. The system further comprises a processing unit connected to the transceiver unit, wherein the processing unit is configured to identify, at the NRF, a target network function (NF) from the one or more network functions based on the load attribute. The processing unit is further configured to generate, by the NWDAF at the NRF, a load attribute subscription associated with the target NF based on at least the load attribute. The transceiver unit is further configured to receive, at the NRF from the target NF, a load attribute value. The processing unit is further configured to detect, at the NRF, a positive load attribute enable monitoring notification based on the load attribute value. The processing unit is further configured to detect, at the NRF, a load attribute timer value based on the positive load attribute enable monitoring notification. The processing unit is further configured to initiate, from the NRF to the NWDAF, the load attribute notification scheduling associated with the load attribute based on at least one of the load attribute timer value and the threshold associated with the load attribute.
[0016] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for initiating a load attribute notification scheduling from a Network Repository Function (NRF), the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver unit of the system to receive, from a Network Data Analytics Function (NWDAF) at the NRF, a subscription request associated with one or more network functions, wherein the subscription request comprises at least a load attribute and a threshold associated with the load attribute, a processing unit of the system to identify, at the NRF, a target network function (NF) from the one or more network functions based on the load attribute, the processing unit to generate, at the NRF, a load attribute subscription associated with the target NF based on at least the load attribute, the transceiver unit to receive, at the NRF from the target NF, a load attribute value, the processing unit to detect, at the NRF, a positive load attribute enable monitoring notification based on the load attribute value, the processing unit to detect, at the NRF, a load attribute timer value based on the positive load attribute enable monitoring notification, and the processing unit to initiate, from the NRF to the NWDAF, the load attribute notification

scheduling associated with the load attribute based on at least one of the load attribute timer value and the threshold associated with the load attribute.
[0017] Yet another aspect of the present disclosure may relate to a user equipment (UE) for initiating a load attribute notification scheduling from a Network Repository Function (NRF), the UE comprises: a memory; and a processor coupled with the memory, wherein the processor is configured to: transmit, to the system, a subscription request associated with one or more network functions, and receiving, from the system, a response comprising the load attribute notification scheduling associated with the subscription request, wherein the response comprising the load attribute notification scheduling is received based on: fetching, by the system from a Network Data Analytics Function (NWDAF) at the NRF, at least a load attribute and a threshold associated with the load attribute based on the subscription request, identifying, at the NRF, a target network function (NF) from the one or more network functions based on the load attribute, generating, by the system by the NWDAF at the NRF, a load attribute subscription associated with the target NF based on at least the load attribute, receiving, by the system at the NRF from the target NF, a load attribute value, detecting, by the system at the NRF, a positive load attribute enable monitoring notification based on the load attribute value, detecting, by the system at the NRF, a load attribute timer value based on the positive load attribute enable monitoring notification, and initiating, by the system from the NRF to the NWDAF, the load attribute notification scheduling associated with the load attribute based on at least one of the load attribute timer value and the threshold associated with the load attribute.
OBJECTS OF THE INVENTION
[0018] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0019] It is an object of the present disclosure to provide a system and a method for initiating a load attribute notification scheduling from a Network Repository Function (NRF).
[0020] It is another object of the present disclosure to provide a solution that eliminates one or more unnecessary notification requests from the NRF.

[0021] It is another object of the present disclosure to provide a solution that schedules one or more notifications as per requirement of the subscriber’s NF.
[0022] It is another object of the present disclosure to provide a method and system which is implemented at the NRF that saves a development and verification effort.
[0023] It is yet another object of the present disclosure to provide a solution that helps in delivering the notification in a more timely or accurate manner.
DESCRIPTION OF THE DRAWINGS
[0024] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
[0025] FIG. 1 illustrates an exemplary block diagram [100] representation of 5th generation core (5GC) network architecture.
[0026] FIG. 2 illustrates an exemplary block diagram [1000] of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
[0027] FIG. 3 illustrates an exemplary block diagram [300] of a system for initiating a load attribute notification scheduling from a Network Repository Function (NRF), in accordance with exemplary implementations of the present disclosure.

[0028] FIG. 4 illustrates a method flow diagram [400] indicating a process for initiating a load attribute notification scheduling from a Network Repository Function (NRF) in accordance with exemplary implementations of the present disclosure.
[0029] FIG. 5 illustrates an exemplary scenario method flow diagram [500] indicating process for initiating a load attribute notification scheduling from a Network Repository Function (NRF) in accordance with exemplary implementations of the present disclosure.
[0030] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
[0031] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.
[0032] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0033] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.

[0034] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order 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.
[0035] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
[0036] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
[0037] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment/device may 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 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.
[0038] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
[0039] As used herein “interface” or “user interface refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
[0040] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[0041] As used herein the transceiver unit include at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units/components within the system and/or connected with the system.

[0042] As discussed in the background section, effective management and scheduling of
notifications are important within the context of a Network Function Repository (NRF). The
current solutions for handling these notifications only offer some basic options, like triggering
notifications instantly upon a change in attribute value. Further, the current solutions fail to
5 operate in complex scheduling scenarios such as recurring notifications or time-based
schedules dependent on multiple attributes or conditions, and hence 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 a method and system for initiating a load attribute notification scheduling from the Network Repository
10 Function (NRF) by eliminating one or more unnecessary notification requests from the NRF,
scheduling one or more notifications as per the requirements of the network function, and saving development and verification effort at each consumer NF sharing information. Additionally, the present disclosure controls the delivery of one or more notifications in run-time based on a flag value and a threshold value.
15
[0043] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure. As shown in FIG. 1, the 5GC network architecture [100] includes a user equipment (UE) [102], a radio access network (RAN) [104], an access and mobility management function
20 (AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy
(SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122], a Unified Data Management
25 (UDM) [124], an application function (AF) [126], a User Plane Function (UPF) [128], a data
network (DN) [130], wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.
30 [0044] Radio Access Network (RAN) [104] is the part of a mobile telecommunications system
that connects user equipment (UE) [102] to the core network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.
11

[0045] 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.
5 [0046] 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.
10 [0047] 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.
[0048] Authentication Server Function (AUSF) [112] is a network function in the 5G core
15 responsible for authenticating UEs during registration and providing security services. It
generates and verifies authentication vectors and tokens.
[0049] Network Slice Specific Authentication and Authorization Function (NSSAAF) [114] is
a network function that provides authentication and authorization services specific to network
20 slices. It ensures that UEs can access only the slices for which they are authorized.
[0050] Network Slice Selection Function (NSSF) [116] is a network function responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies. 25
[0051] Network Exposure Function (NEF) [118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
30 [0052] 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.
12

[0053] Policy Control Function (PCF) [122] is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies.
5 [0054] Unified Data Management (UDM) [124] is a network function that centralizes the
management of subscriber data, including authentication, authorization, and subscription information.
[0055] Application Function (AF) [126] is a network function that represents external
10 applications interfacing with the 5G core network to access network capabilities and services.
[0056] User Plane Function (UPF) [128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.
15 [0057] 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.
[0058] FIG. 2 illustrates an exemplary block diagram of a computing device [1000] (also referred herein as computing system [1000]) upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device [1000] may also implement a method for initiating a load attribute notification scheduling from a Network Repository Function (NRF), utilising the system. In another implementation, the computing device [1000] itself implements the method for initiating the load attribute notification scheduling from the Network Repository Function (NRF) [120] using one or more units configured within the computing device [1000], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
30 [0059] The computing device [1000] may include a bus [1002] or other communication
mechanism for communicating information, and a hardware processor [1004] coupled with the bus [1002] for processing information. The hardware processor [1004] may be, for example, a general-purpose microprocessor. The computing device [1000] may also include a main memory [1006], such as a random-access memory (RAM), or other dynamic storage device,
13

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

[0062] The computing device [1000] also may include a communication interface [1018]
coupled to the bus [1002]. The communication interface [1018] provides a two-way data
communication coupling to a network link [1020] that is connected to a local network [1022].
5 For example, the communication interface [1018] may be an integrated services digital network
(ISDN) card, cable modem, satellite modem, or a modem to provide a data communication
connection to a corresponding type of telephone line. As another example, the communication
interface [1018] may be a local area network (LAN) card to provide a data communication
connection to a compatible LAN. Wireless links may also be implemented. In any such
10 implementation, the communication interface [1018] sends and receives electrical,
electromagnetic, or optical signals that carry digital data streams representing various types of information.
[0063] The computing device [1000] can send messages and receive data, including program
15 code, through the network(s), the network link [1020] and the communication interface [1018].
In the Internet example, a server [1030] might transmit a requested code for an application
program through the Internet [1028], the ISP [1026], the Host [1024], the local network [1022]
and the communication interface [1018]. The received code may be executed by the processor
[1004] as it is received, and/or stored in the storage device [1010], or other non-volatile storage
20 for later execution.
[0064] Referring to FIG. 3, an exemplary block diagram of a system [300] for initiating a load attribute notification scheduling from a Network Repository Function (NRF), is shown, in accordance with the exemplary implementations of the present disclosure. The system [300]
25 comprises at least one transceiver unit [302] and at least one processing unit [304]. Also, all of
the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Also, in Fig. 1 only a few units are shown, however, the system [300] may comprise multiple such units or the system [300] may comprise
30 any such numbers of said units, as required to implement the features of the present disclosure.
In another implementation, the system [300] may reside in a server or a network entity. In yet another implementation, the system [300] may reside partly in the server/ network entity.
15

[0065] The system [300] is configured for initiating the load attribute notification scheduling from the Network Repository Function (NRF) [120], with the help of the interconnection between the components/units of the system [300].
5 [0066] 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 particular functionality of these
units for clarity, it is recognized that various configurations and combinations thereof are
within the scope of the disclosure. The functionality of specific units as disclosed in the
10 disclosure should not be construed as limiting the scope of the present disclosure.
Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
15 [0067] In order to initiate the load attribute notification scheduling from the Network
Repository Function (NRF) [120], the transceiver unit [302] is configured to receive from a Network Data Analytics Function (NWDAF) at the NRF [120], a subscription request associated with one or more network functions, wherein the subscription request comprises at least a load attribute and a threshold associated with the load attribute.
20
[0068] The present disclosure as disclosed herein encompasses that the threshold associated with the load attribute is at least one of a predefined threshold and a dynamically defined threshold.
25 [0069] The present disclosure as disclosed herein encompasses that the subscription request
may further comprise a network function type.
[0070] The present disclosure as disclosed herein encompasses that the Network Data
Analytics Function (NWDAF) is a component within a Fifth Generation (5G) network which
30 is responsible for collecting, processing, and analyzing a network data to provide one or more
insights. The NWDAF enables one or more network management functions and services, such as network optimization, resource allocation, service assurance, and network security.
16

[0071] The present disclosure encompasses that the load attribute notification scheduling refers to scheduling of the notification based on changes in a specific attribute (i.e. load) with the network. Also, when the specific attribute meets a threshold value, the notification may be scheduled, in accordance with the embodiments of the present disclosure as disclosed herein. 5
[0072] In an implementation of the present disclosure as disclosed herein, the subscription
request is a request that is made to the NRF [120] from the NWDAF to receive a notification
related to one or more network functions, wherein the said notification may be a load attribute
notification associated with the one or more network functions and a threshold notification
10 associated with the load attribute associated with the one or more network functions.
[0073] Further, the load attribute is a specific attribute within the network such as the 5G
network which may refer to an amount of workload or traffic that a particular network function
is experiencing. The threshold associated with the load attribute is a predetermined value, when
15 exceeded by the load attribute may trigger the generation of the notification such as a load
attribute notification.
[0074] Further, the processing unit [304] is connected to the transceiver unit [302] and the
processing unit [304] is configured to identify, at the NRF [120], a target network function
20 (NF) from the one or more network functions based on the load attribute. As disclosed by the
present disclosure, the target network function may be further identified based on the threshold associated with the load attribute.
[0075] Further, the processing unit [304] is configured to generate, by the NWDAF at the NRF
25 [120], a load attribute subscription associated with the target NF based on at least the load
attribute.
[0076] The present disclosure encompasses that the load attribute subscription is generated via
processing a subscription request. The subscription request may include one or more
30 parameters that indicate a list of attributes such as vendor specific attributed in a network
function profile to be monitored.
[0077] The present disclosure encompasses that the load attribute subscription associated with the target NF is further generated based on the network function type.
17

[0078] The present disclosure encompasses that the load attribute subscription is a
configuration established between one or more network management components for
monitoring one or more load attributes which are associated with one or more network
5 functions (NFs), wherein the one or more network management components is configured to
perform the one or more network management functions and services. Further, in other words, the load attribute subscription defines which load attribute of the one or more network functions are to be monitored.
10 [0079] For example, the processing unit [304] identifies a specific NF (i.e. target NF) based on
a criteria i.e. a load attribute. Once identified, the processing unit [304] generates a subscription associated with the specific NF based on the criteria i.e., the subscription associated with the target NF based on the load attribute of the target NF.
15 [0080] Further, the transceiver unit [302] is further configured to receive, at the NRF [120]
from the target NF, a load attribute value. As disclosed by the present disclosure, the load attribute value is a value of the load attribute of the target NF.
[0081] Thereafter the processing unit [304] is further configured to detect, at the NRF [120], a
20 positive load attribute enable monitoring notification based on the load attribute value. Further,
as disclosed herein, the positive load attribute enable monitoring notification indicates that the load attribute value has reached a level that requires monitoring as it has exceeded the threshold associated with the load attribute. Further, said level may be a predefined level associated with the load attribute or a dynamically updated level associated with the load attribute. 25
[0082] Further, as disclosed by the present disclosure, the load attribute value is received in a
heartbeat request. The heartbeat request is a periodic signal sent by a network component, such
as a base station or network function, to another component to verify an operational status and
responsiveness. The heartbeat request ensures the reliability and availability of network
30 resources. For instance, if the recipient fails to respond within the expected timeframe, it may
indicate a potential issue or a failure that requires attention. The heartbeat request maintains the overall performance and stability of the 5G network by facilitating timely detection and response to one or more network disruptions or failures.
18

[0083] The processing unit [304] is further configured to detect, at the NRF [120], a load attribute timer value based on the positive load attribute enable monitoring notification. The load attribute timer value refers to a time parameter that is related to the duration for which the positive load attribute monitoring notification is active or valid. 5
[0084] The processing unit [304] is further configured to initiate, from the NRF [120] to the NWDAF, the load attribute notification scheduling associated with the load attribute based on at least one of the load attribute timer value and the threshold associated with the load attribute.
10 [0085] Further, in an implementation of the present solution as disclosed herein, the positive
load attribute enable monitoring notification may be sent to the NRF [120] at a predefined time interval based on a capacity of the NWDAF, wherein the positive load attribute enable monitoring notification may comprises one or more load information associated with the load attribute such as the load attribute value. Furthermore, in another implementation of the present
15 solution, the predefined time interval to send the positive load attribute enable monitoring
notification to the NRF [120] may be determined based on one or more predefined time interval determination rules such as to align the predefined time interval and the capacity of the NWDAF.
20 [0086] Referring to FIG. 4, an exemplary method flow diagram [400] indicating a process for
initiating a load attribute notification scheduling from a Network Repository Function (NRF), in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [400] is performed by the system [300]. Further, in an implementation, the system [300] may be present in a server device to implement the features
25 of the present disclosure. Also, as shown in Figure 4, the method [400] starts at step [402].
[0087] At step [404], the method [400] comprises receiving, by a transceiver unit [302] from
a Network Data Analytics Function (NWDAF) at the NRF [120], a subscription request
associated with one or more network functions, wherein the subscription request comprises at
30 least a load attribute and a threshold associated with the load attribute.
[0088] The present disclosure encompasses that the threshold associated with the load attribute is at least one of a predefined threshold and a dynamically defined threshold.
19

[0089] The present disclosure encompasses that the subscription request further comprises a network function type.
[0090] The present disclosure as disclosed herein encompasses that the Network Data
5 Analytics Function (NWDAF) is a component within a Fifth Generation (5G) network which
is responsible for collecting, processing, and analyzing a network data to provide one or more insights. The NWDAF enables one or more network management functions and services, such as network optimization, resource allocation, service assurance, and network security.
10 [0091] The present disclosure encompasses that the load attribute notification scheduling refers
to scheduling of the notification based on changes in a specific attribute (i.e. load) with the network. Also, when the specific attribute meets a threshold value, the notification may be scheduled in accordance with the embodiments of the present disclosure as disclosed herein.
15 [0092] In an implementation of the present disclosure as disclosed herein, the subscription
request is a request that is made to the NRF [120] from the NWDAF to receive a notification related to one or more network functions, wherein the said notification may be a load attribute notification associated with the one or more network functions and a threshold notification associated with the load attribute associated with the one or more network functions.
20
[0093] Further, the load attribute is a specific attribute within the network such as the 5G network which may refer to an amount of workload or traffic that a particular network function is experiencing. The threshold associated with the load attribute is a predetermined value, when exceeded by the load attribute may trigger the generation of the notification such as a load
25 attribute notification.
[0094] At step [406], the method [400] comprises identifying, by a processing unit [304] at the NRF [120], a target network function (NF) from the one or more network functions based on the load attribute. 30
[0095] The present disclosure encompasses that identifying the target network function is further based on the threshold associated with the load attribute.
20

[0096] At step [408], the method [400] comprises generating, via the processing unit [304] by the NWDAF at the NRF [120], a load attribute subscription associated with the target NF based on at least the load attribute.
5 [0097] The present disclosure encompasses that the load attribute subscription is generated via
processing a subscription request. The subscription request may include one or more parameters that indicate a list of attributes such as vendor specific attributed in a network function profile to be monitored.
10 [0098] The present disclosure encompasses that generating the load attribute subscription
associated with the target NF is further based on the network function type.
[0099] The present disclosure encompasses that the load attribute subscription is a configuration established between one or more network management components for
15 monitoring one or more load attributes which are associated with one or more network
functions (NFs), wherein the one or more network management components is configured to perform the one or more network management functions and services. Further, in other words, the load attribute subscription defines which load attribute of the one or more network functions are to be monitored.
20
[0100] For example, the processing unit [304] identifies a specific NF (i.e. target NF) based on a criteria i.e. a load attribute. Once identified, the processing unit [304] generates a subscription associated with the specific NF based on the criteria i.e., the subscription associated with the target NF based on the load attribute of the target NF.
25
[0101] At step [410], the method [400] comprises receiving, via the transceiver unit [302]at the NRF [120] from the target NF, a load attribute value. As disclosed by the present disclosure, the load attribute value is a value of the load attribute of the target NF.
30 [0102] The present disclosure encompasses that the load attribute value is received in a
heartbeat request. The heartbeat request is a periodic signal sent by a network component, such as a base station or network function, to another component to verify an operational status and responsiveness. The heartbeat request ensures the reliability and availability of network resources. For instance, if the recipient fails to respond within the expected timeframe, it may
21

indicate a potential issue or a failure that requires attention. The heartbeat request maintains the overall performance and stability of the 5G network by facilitating timely detection and response to one or more network disruptions or failures.
5 [0103] At step [412], the method [400] comprises detecting, via the processing unit [304] at
the NRF [120], a positive load attribute enable monitoring notification based on the load
attribute value. Further, as disclosed herein, the positive load attribute enable monitoring
notification indicates that the load attribute value has reached a level that requires monitoring
as it has exceeded the threshold associated with the load attribute. Further, said level may be a
10 predefined level associated with the load attribute or a dynamically updated level associated
with the load attribute.
[0104] At step [414], the method [400] comprises detecting, via the processing unit [304] at
the NRF [120], a load attribute timer value based on the positive load attribute enable
15 monitoring notification. The load attribute timer value refers to a time parameter that is related
to the duration for which the positive load attribute monitoring notification is active or valid.
[0105] At step [416], the method [400] comprises initiating, via the processing from the NRF
[120] to the NWDAF, the load attribute notification scheduling associated with the load
20 attribute based on at least one of the load attribute timer value and the threshold associated with
the load attribute.
[0106] Further, in an implementation of the present solution as disclosed herein, the positive load attribute enable monitoring notification may be sent to the NRF [120] at a predefined time
25 interval based on a capacity of the NWDAF, wherein the positive load attribute enable
monitoring notification may comprises one or more load information associated with the load attribute such as the load attribute value. Furthermore, in another implementation of the present solution, the predefined time interval to send the positive load attribute enable monitoring notification to the NRF [120] may be determined based on one or more predefined time interval
30 determination rules such as to align the predefined time interval and the capacity of the
NWDAF.
[0107] The method [400] terminates at step [418].
22

[0108] Referring to FIG. 5, wherein an exemplary scenario method flow diagram [500]
indicating process for initiating a load attribute notification scheduling from a Network
Repository Function (NRF) in accordance with exemplary implementations of the present
disclosure is shown. In an implementation the method [500] is performed by the system [300].
5 Further, in an implementation, the system [300] may be present in a server device to implement
the features of the present disclosure. Also, as shown in FIG. 5, at step S1, a network function (NF) is subscribed by a Network Repository Function (NRF) [120] based on a load attribute.
[0109] At step S2, the subscribed NF transmits via the transceiver unit [302], a load value in
10 one or more heartbeat requests. Further, at step 2, in an event if there is any error while sending
the load value from the subscribed NF, in said event no notification is initiated from the Network Repository Function (NRF) [120].
[0110] Next, at step S3, in an event the load value is successfully transmitted via the transceiver
15 unit [302] by the subscribed NF, in said event an “Enable-Monitored-Attribute-Notification”
flag is checked at the NRF [120] via the processing unit [304].
[0111] Further, at step S3 in a scenario a negative determination of the Enable-Monitored-Attribute-Notification” flag is detected, one or more notifications are initiated immediately initiated from the Network Repository Function (NRF) [120]. Further, the step S3 is necessary to confirm a successful transmission of load value, upon step S2. For example, the step S3, helps to check if the NRF [120] is configured to monitor a set of attributes and if not configured, then the one or more notifications are initiated immediately initiated from the Network Repository Function (NRF) [120]. Further, the “Enable-Monitored-Attribute-Notification” flag used herein is an exemplary scenario and is not intended to limit the scope, applicability, or configuration of the disclosure.
[0112] Next at step S4, in a scenario a positive determination of the Enable-Monitored-
Attribute-Notification” flag is detected at NRF [120], the processing unit [304] checks for a
30 “Load-Notification-Timer” value and schedules the one or more notifications as per a
configured interval from the Network Repository Function (NRF) [120]. Further, the “Load-Notification-Timer” value refers to a time parameter that is related to the duration for which the positive load attribute monitoring notification is active or valid. For example, the one or more notification may be scheduled at intervals of 5 minutes or 30 minutes as configured.
23

Further, the “Load-Notification-Timer” value used herein is an exemplary scenario and is not intended to limit the scope, applicability, or configuration of the disclosure.
[0113] The present disclosure further discloses a non-transitory computer readable storage
5 medium storing instructions for initiating a load attribute notification scheduling from a
Network Repository Function (NRF), the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver unit [302] of the system to receive, from a Network Data Analytics Function (NWDAF) at the NRF [120], a subscription request associated with one or more network functions, wherein the subscription request
10 comprises at least a load attribute and a threshold associated with the load attribute, a
processing unit [304] of the system to identify, at the NRF [120], a target network function (NF) from the one or more network functions based on the load attribute, the processing unit [304] to generate, at the NRF [120], a load attribute subscription associated with the target NF based on at least the load attribute, the transceiver unit [302] to receive, at the NRF [120] from
15 the target NF, a load attribute value, the processing unit [304] to detect, at the NRF [120], a
positive load attribute enable monitoring notification based on the load attribute value, the processing unit [304] to detect, at the NRF [120], a load attribute timer value based on the positive load attribute enable monitoring notification, and the processing unit [304] to initiate, from the NRF [120] to the NWDAF, the load attribute notification scheduling associated with
20 the load attribute based on at least one of the load attribute timer value and the threshold
associated with the load attribute.
[0114] The present disclosure further discloses a user equipment (UE) for initiating a load attribute notification scheduling from a Network Repository Function (NRF), the UE
25 comprises: a memory; and a processor coupled with the memory, wherein the processor is
configured to: transmit, to the system, a subscription request associated with one or more network functions, and receiving, from the system, a response comprising the load attribute notification scheduling associated with the subscription request, wherein the response comprising the load attribute notification scheduling is received based on: fetching, by the
30 system from a Network Data Analytics Function (NWDAF) at the NRF [120], at least a load
attribute and a threshold associated with the load attribute based on the subscription request, identifying, at the NRF [120], a target network function (NF) from the one or more network functions based on the load attribute, generating, by the system by the NWDAF at the NRF [120], a load attribute subscription associated with the target NF based on at least the load
24

attribute, receiving, by the system at the NRF [120] from the target NF, a load attribute value,
detecting, by the system at the NRF [120], a positive load attribute enable monitoring
notification based on the load attribute value, detecting, by the system at the NRF [120], a load
attribute timer value based on the positive load attribute enable monitoring notification, and
5 initiating, by the system from the NRF [120] to the NWDAF, the load attribute notification
scheduling associated with the load attribute based on at least one of the load attribute timer value and the threshold associated with the load attribute.
[0115] For ease of understating the present solution as disclosed herein, let consider a scenario wherein the present solution may be implemented by a telecommunications organization for initiating a load attribute notification scheduling from a Network Repository Function (NRF). The telecommunications organization may implement the method [400], which involves receiving a subscription request associated with one or more network functions, wherein the subscription request comprises at least a load attribute and a threshold associated with the load attribute. Thereafter, the processing unit [304] identifies, at the NRF [120], a target network function (NF) from the one or more network functions based on the load attribute and further generates, by the NWDAF at the NRF [120], a load attribute subscription associated with the target NF based on at least the load attribute. Also, the transceiver unit may receive a load attribute value. Thereafter, the processing unit [304] detects, at the NRF [120], a positive load attribute that enables monitoring notification based on the load attribute value. The processing unit [304] detects, at the NRF [120], a load attribute timer value based on the positive load attribute to enable monitoring notification. Thereafter, the processing unit [304] initiates, from the NRF [120] to the NWDAF, the load attribute notification scheduling associated with the load attribute based on at least one of the load attribute timer values and the threshold associated with the load attribute.
[0116] As is evident from the above, the present disclosure provides a technically advanced
solution for initiating a load attribute notification scheduling from a Network Repository
Function (NRF). The present solution eliminates one or more unnecessary notification
30 requests, schedules one or more notifications as per the requirement in an enhanced manner
and saves development and verification effort by enabling proactive monitoring and notification scheduling based on the type of NF. Further, the present solution includes a feature of dynamic subscription handling and threshold-based triggering, which allow for real-time adjustments and optimizations. These advancements have wide-ranging implications across
25

various industries and network infrastructures, leading to improved productivity, resource utilization, and customer satisfaction.
[0117] While considerable emphasis has been placed herein on the disclosed implementations,
5 it will be appreciated that many implementations can be made and that many changes can be
made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
26

We Claim:
1. A method [400] for initiating a load attribute notification scheduling from a Network
Repository Function (NRF), the method comprising:
- receiving, by a transceiver unit [302] from a Network Data Analytics Function (NWDAF) at the NRF [120], a subscription request associated with one or more network functions, wherein the subscription request comprises at least a load attribute and a threshold associated with the load attribute;
- identifying, by a processing unit [304] at the NRF [120], a target network function (NF) from the one or more network functions based on the load attribute;
- generating, via the processing unit [304] by the NWDAF at the NRF [120], a load attribute subscription associated with the target NF based on at least the load attribute;
- receiving, via the transceiver unit [302] at the NRF [120] from the target NF, a load attribute value;
- detecting, via the processing unit [304] at the NRF [120], a positive load attribute enable monitoring notification based on the load attribute value;
- detecting, via the processing unit [304] at the NRF [120], a load attribute timer value based on the positive load attribute enable monitoring notification; and
- initiating, via the processing unit [304] from the NRF [120] to the NWDAF, the load attribute notification scheduling associated with the load attribute based on at least one of the load attribute timer value and the threshold associated with the load attribute.

2. The method as claimed in claim 1, wherein the threshold associated with the load attribute is at least one of a predefined threshold and a dynamically defined threshold.
3. The method as claimed in claim 1, wherein identifying the target network function is further based on the threshold associated with the load attribute.
4. The method as claimed in claim 1, wherein the subscription request further comprises a network function type.

5. The method as claimed in claim 4, wherein generating the load attribute subscription associated with the target NF is further based on the network function type.
6. The method as claimed in claim 1, wherein the load attribute value is received in a heartbeat request.
7. A system [300] for initiating a load attribute notification scheduling from a Network Repository Function (NRF), the system comprises:
- a transceiver unit [302] configured to:
• receive, from a Network Data Analytics Function (NWDAF) at the NRF [120],
a subscription request associated with one or more network functions, wherein
the subscription request comprises at least a load attribute and a threshold
associated with the load attribute; and
- a processing unit [304] connected to the transceiver unit [302], wherein the
processing unit [304] is configured to:
• identify, at the NRF [120], a target network function (NF) from the one or more network functions based on the load attribute,
• generate, by the NWDAF at the NRF [120], a load attribute subscription associated with the target NF based on at least the load attribute,
wherein the transceiver unit [302] is further configured to receive, at the NRF [120] from the target NF, a load attribute value, wherein the processing unit [304] is further configured to:
• detect, at the NRF [120], a positive load attribute enable monitoring notification based on the load attribute value,
• detect, at the NRF [120], a load attribute timer value based on the positive load attribute enable monitoring notification, and
• initiate, from the NRF [120] to the NWDAF, the load attribute notification scheduling associated with the load attribute based on at least one of the load attribute timer value and the threshold associated with the load attribute.
8. The system [300] as claimed in claim 7, wherein the threshold associated with the load
attribute is at least one of a predefined threshold and a dynamically defined threshold.

9. The system [300] as claimed in claim 7, wherein the target network function is further identified based on the threshold associated with the load attribute.
10. The system [300] as claimed in claim 7, wherein the subscription request further comprises a network function type.
11. The system [300] as claimed in claim 10, wherein the load attribute subscription associated with the target NF is further generated based on the network function type.
12. The system [300] as claimed in claim 7, wherein the load attribute value is received in a heartbeat request.
13. A user equipment (UE) for initiating a load attribute notification scheduling from a Network Repository Function (NRF), the UE comprises:

- a memory; and
- a processor coupled with the memory, wherein the processor is configured to: transmit, to a system, a subscription request associated with one or more network functions, and
receiving, from the system, a response comprising the load attribute notification scheduling associated with the subscription request,
wherein the response comprising the load attribute notification scheduling is received based on:
fetching, by the system from a Network Data Analytics Function (NWDAF) at the NRF [120], at least a load attribute and a threshold associated with the load attribute based on the subscription request,
identifying, at the NRF [120], a target network function (NF) from the one or more network functions based on the load attribute,
generating, by the system by the NWDAF at the NRF [120], a load attribute subscription associated with the target NF based on at least the load attribute,
receiving, by the system at the NRF [120] from the target NF, a load attribute value,

detecting, by the system at the NRF [120], a positive load attribute enable monitoring notification based on the load attribute value,
detecting, by the system at the NRF [120], a load attribute timer value based on the positive load attribute enable monitoring notification, and
initiating, by the system from the NRF [120] to the NWDAF, the load attribute notification scheduling associated with the load attribute based on at least one of the load attribute timer value and the threshold associated with the load attribute.