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 REPORTING SLICE-SPECIFIC LOAD
INFORMATION”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR REPORTING SLICE-SPECIFIC LOAD INFORMATION
TECHNICAL FIELD
[0001] Embodiments of the present disclosure generally relate to the field of network
performance management. More particularly, embodiments of the present disclosure relate to method and system for reporting slice-specific load information.
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. 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] Moreover, 5G core networks are based on service-based architecture (SBA) that is
centered around network function (NF) services. Each NF can register itself and its supported services to a Network Repository Function (NRF), which is used by other NFs for the discovery of NF instances and their services. The NRF therefore supports functions related to 1) maintaining the profiles of the available network function (NF) instances and their supported services in the 5G core network, 2) allowing NF instances to discover other NF instances in the 5G core network, and 3) allowing the NF instances to track the status of other NF instances.

[0005] Also, as defined in 3gpp TS 29.510, NFs may report the NF Level or Service Level
load information to NRF in Heartbeat messages. Further, each NF can provide service for one or many slices. Currently, there is no method defined in standard or in the existing solutions for reporting full NF Level load on a per slice basis. Similarly, an individual service within NF may also require reporting load on per slice basis.
[0006] Both the above-mentioned problems are not currently addressed by 3gpp TS 29.510
and/or any other existing solutions in the art, therefore the present disclosure aims to address these limitations.
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 reporting slice-specific
load information in a 5G network. The method includes receiving, by a receiver via a network repository function (NRF), a registration request from a network function (NF). The registration request comprises a load attribute indicative of a load level for at least one network slice. The method further includes updating, by a processing unit via the NF, a profile with the load attribute associated with a respective network slice identifier and a corresponding load value. Furthermore, the method includes transmitting, by a transmitter via the NF, a heartbeat message to the NRF. The heartbeat message comprises the load attribute for the at least one network slice. Further, the method encompasses storing, by a storage unit via the NRF, the load attribute in database. The method further includes subscribing, by the processing unit via a network data analytics entity, to the load attribute for the at least one network slice. Also, the method encompasses sending, by the transmitter via the NRF, a notification to the network data analytics entity comprising the load attribute, upon detecting a change in the load value for the at least one network slice.
[0009] In an exemplary aspect of the present disclosure, the load attribute is defined as a map
data type with the network slice identifier as a key and the load value as a value, with the load value ranging from 0 to 100.
[0010] In an exemplary aspect of the present disclosure, the notification comprising the load
attribute is sent within a configuration interval to prevent unnecessary data transmission to the

network data analytics entity. The configuration interval is a predefined time period that that corresponds to a frequency of updates to the network data analytics entity.
[0011] In an exemplary aspect of the present disclosure, the load attribute is stored at a profile
level within the NF to determine the load level for each network slice serviced by the NF.
[0012] In an exemplary aspect of the present disclosure, the load attribute is stored at a service
level within the NF to determine the load level for each network slice specific to a NF service.
[0013] In an exemplary aspect of the present disclosure, the load attribute is transmitted within
the heartbeat message at a pre-defined time interval.
[0014] In an exemplary aspect of the present disclosure, the notification to the network data
analytics entity is triggered by a predetermined threshold of load value change for the network slice.
[0015] In an exemplary aspect of the present disclosure, the network data analytics entity is a
Network Data Analytics Function (NWDAF) node.
[0016] Another aspect of the present disclosure may relate to a system for reporting slice-
specific load information in a 5G network. The system includes a receiver, configured to receive, via a network repository function (NRF), a registration request from a network function (NF), wherein the registration request comprises a load attribute indicative of a load level for at least one network slice. The system further includes a processing unit, configured to update, via the NF, a profile with the load attribute associated with a respective network slice identifier and a corresponding load value. Furthermore, the system encompasses a transmitter, configured to transmit via the NF, a heartbeat message to the NRF. The heartbeat message comprises the load attribute for the at least one network slice. The system further includes a storage unit, configured to store, via the NRF, the load attribute in database. Further, the system includes the processing unit, configured to subscribe, via a network data analytics entity, to the load attribute for the at least one network slice. Furthermore, the system encompasses the transmitter, configured to send, via the NRF to the network data analytics entity, a notification comprising the load attribute upon detecting a change in the load value for the at least one network slice.
[0017] Yet another aspect of the present disclosure relates to a user equipment (UE) for
reporting slice-specific load information in a communication network. The UE includes a Processor, configured to transmit a registration request from a network function (NF), wherein the registration request comprises a load attribute indicative of a load level for at least one network slice. The

processor is further configured to update a profile with the load attribute associated with a respective network slice identifier and a corresponding load value. Furthermore, the processor is configured to transmit a heartbeat message to the NRF. The heartbeat message comprises the load attribute for the at least one network slice. Furthermore, the processor is configured to store the load attribute in a database. The processor is further configured to subscribe to the load attribute for the at least one network slice. The processor is further configured to send a notification to the network data analytics entity comprising the load attribute upon detecting a change in the load value for the at least one network slice.
[0018] Yet another aspect of the present disclosure may relate to a non-transitory computer
readable storage medium storing instructions for reporting slice-specific load information in a 5G network, the instructions include executable code which, when executed by a one or more units of a system, causes: a receiver of the system to receive via a network repository function (NRF), a registration request from a network function (NF). The registration request comprises a load attribute indicative of a load level for at least one network slice. In addition, the instructions include executable code which, when executed by a one or more units of a system causes a processing unit of the system to update via the NF, a profile with the load attribute associated with a respective network slice identifier and a corresponding load value; a transmitter of the system to transmit via the NF, a heartbeat message to the NRF, wherein the heartbeat message comprises the load attribute for the at least one network slice; a storage unit of the system to store via the NRF, the load attribute in database; the processing unit of the system to subscribe, via a network data analytics entity, to the load attribute for the at least one network slice; and the transmitter of the system to send, via the NRF to the network data analytics entity, a notification comprising the load attribute upon detecting a change in the load value for the at least one network slice.
OBJECTS OF THE INVENTION
[0019] Some of the objects of the present disclosure, which at least one embodiment disclosed
herein satisfies are listed herein below.
[0020] It is an object of the present disclosure to provide a system and a method that can
overcome the limitations of the existing solutions and the 3gpp TS 29.510, related to slice level load reporting.
[0021] It is another object of the present disclosure to provide the system and the method that
may enable all 5G NFs to report to the NRF, the NF Load level, on a per slice basis in addition to full NF Level load in Heartbeat or NF Update.

[0022] It is yet another object of the present disclosure to provide the system and the method
that may enable all 5G NFs to report to the NRF, the Service Load Level on per slice basis in addition to full-Service Level load in Heartbeat or NF Update.
DESCRIPTION OF THE DRAWINGS
[0023] 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.
[0024] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core
(5GC) network architecture, in accordance with exemplary implementation of the present disclosure.
[0025] FIG. 2 illustrates an exemplary block diagram of a computing device for reporting
slice-specific load information in a 5G network, in accordance with exemplary implementation of the present disclosure.
[0026] FIG. 3 illustrates an exemplary block diagram of a system for reporting slice-specific
load information in the 5G network, in accordance with exemplary implementations of the present disclosure.
[0027] FIG. 4 illustrates a flow diagram of a method for reporting slice-specific load
information in the 5G network, in accordance with exemplary implementations of the present disclosure.
[0028] FIG.5 illustrates an exemplary signalling flow diagram indicating an exemplary
process for providing slice level load reporting, in accordance with exemplary implementation of the present disclosure.

[0029] The foregoing shall be more apparent from the following more detailed description of
the disclosure.
DETAILED DESCRIPTION
[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 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 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.
[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 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.
[0033] 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.
[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 aspect or design described herein as “exemplary”

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. 5
[0035] 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
10 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.
15
[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
20 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
25 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 form readable by a computer
30 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.
35
[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
8

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.
5 [0039] 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
10 circuits (FPGA), any other type of integrated circuits, etc.
[0040] The 5G core networks are based on service-based architecture (SBA) that is centered
around network function (NF) services. Each NF can register itself and its supported services to a
Network Repository Function (NRF), which is used by other NFs for the discovery of NF instances
15 and their services. The NRF supports functions related to maintaining the profiles of the available
network function (NF) instances and their supported services in the 5G core network, allowing NF instances to discover other NF instances in the 5G core network, and allowing the NF instances to track the status of other NF instances.
20 [0041] Also, as defined in 3gpp TS 29.510, NFs can report the NF Level or Service Level load
information to NRF in Heartbeat messages. Further, each NF may provide service for one or many slices. Currently, there is no method defined in standard or in the existing solutions for reporting full NF Level load on per slice basis. Similarly, an individual service within NF may also require to report load on per slice basis. Both of these problems are not currently addressed by 3gpp TS 29.510
25 and/or any other existing solutions in the art, therefore the present disclosure aims to address these
limitations.
[0042] 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
30 problems in this field of technology by providing a method and a system for reporting slice-specific
load information in the 5G network.
[0043] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core
(5GC) network architecture [100], in accordance with exemplary implementation of the present
35 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],
9

an Authentication Server Function (AUSF) [112], and a Network Slice Specific Authentication and
Authorization Function (NSSAAF) [114]. In addition, the 5GC network architecture [100] includes
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
5 Management (UDM) [124], an application function (AF) [126], a User Plane Function (UPF) [128],
and a data network (DN) [130]. All the components of the 5GC network architecture [100] 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.
10 [0044] The 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.
15 [0045] The 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.
[0046] The Session Management Function (SMF) [108] is a 5G core network function
20 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.
[0047] The Service Communication Proxy (SCP) [110] is a network function in the 5G core
25 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] The 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
30 and verifies authentication vectors and tokens.
[0049] The Network Slice Specific Authentication and Authorization Function (NSSAAF)
[114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized. 35
10

[0050] The 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.
5 [0051] The 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.
[0052] The Network Repository Function (NRF) [120] is a network function that acts as a
10 central repository for information about available network functions and services. It facilitates the
discovery and dynamic registration of network functions.
[0053] The 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
15 network policies.
[0054] The Unified Data Management (UDM) [124] is a network function that centralizes the
management of subscriber data, including authentication, authorization, and subscription information. 20
[0055] The Application Function (AF) [126] is a network function that represents external
applications interfacing with the 5G core network to access network capabilities and services.
[0056] The User Plane Function (UPF) [128] is a network function responsible for handling
25 user data traffic, including packet routing, forwarding, and QoS enforcement.
[0057] The 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. 30
[0058] FIG. 2 illustrates an exemplary block diagram of a computing device [1000] (also
referred to herein as a computer system [1000]) upon which the features of the present disclosure
may be implemented in accordance with exemplary implementation of the present disclosure. In an
implementation, the computing device [1000] may also implement a method for reporting slice-
35 specific load information in a 5G network utilising the system. In another implementation, the
computing device [1000] implements the method for reporting slice-specific load information in the
11

5G network 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.
[0059] The computing device [1000] may include a bus [1002] or other communication
5 mechanism for communicating information, and a hardware processor [1004] coupled with 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, coupled to the bus [1002] for storing information and instructions to be executed by the processor [1004]. The main memory
10 [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 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
15 other static storage device coupled to the bus [1002] for storing static information and instructions
for the processor [1004].
[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
20 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 (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
25 input device may be a cursor controller [1016], such as a mouse, a trackball, or cursor direction keys,
for communicating direction information and command selections to the processor [1004], and for controlling cursor movement on the display [1012]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
30
[0061] The computing device [1000] may implement the techniques described herein using
customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [1000] causes or programs the computing device [1000] to be a special-purpose machine. According to one implementation, the techniques herein are
35 performed by the computing device [1000] in response to the processor [1004] executing one or
more sequences of one or more instructions contained in the main memory [1006]. Such instructions may be read into the main memory [1006] from another storage medium, such as the storage device
12

[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. 5
[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]. For example, the communication interface [1018] may be an integrated services digital network (ISDN)
10 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 implementation, the communication interface [1018] sends and receives electrical, electromagnetic or optical signals that carry digital
15 data streams representing various types of information.
[0063] The computing device [1000] can send messages and receive data, including program
code, through the network(s), the network link [1020] and the communication interface [1018]. In
the Internet example, a server [1030] might transmit a requested code for an application program
20 through the Internet [1028], the ISP [1026], the local network [1022] and the communication
interface [1018]. The received code may be executed by the processor [1004] as it is received, and/or stored in the storage device [1010], or other non-volatile storage for later execution.
[0064] Referring to FIG. 3, an exemplary block diagram of a system [300] for reporting slice-
25 specific load information in the 5G core network, is shown, in accordance with the exemplary
implementations of the present disclosure. The system [300] comprises at least one receiver [302],
at least one processing unit [304], at least one transmitter [308], and at least one storage unit [306].
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
30 also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however,
the system [300] may comprise multiple such units or the system [300] may comprise any such
numbers of said units, as required to implement the features of the present disclosure. Further, in an
implementation, the system [300] may be present in a user device to implement the features of the
present disclosure. The system [300] may be a part of the user device / or may be independent of but
35 in communication with the user device (may also referred herein as a UE). In another
implementation, the system [300] may reside in a server or a network entity. In yet another
13

implementation, the system [300] may reside partly in the server/ network entity and partly in the user device.
[0065] The system [300] is configured for reporting slice-specific load information in the 5G
5 core network, with the help of the interconnection between the components/units of the system [300].
[0066] The system [300] includes a receiver [302], configured to receive, via a network
repository function (NRF) [310], a registration request from a network function (NF) [312]. The registration request is associated with receiving a current load attribute for at least one network slice.
10 The registration request comprises a load attribute indicative of a load level for at least one network
slice. A load attribute in a network refers to the capacity of the system in a network to handle the data or traffic. For instance, a load attribute can be "data throughput capacity" of a network router, which means the maximum amount of data that the device may be transmitted or received within a given time frame. Another load attribute may be a ‘Concurrent user capacity’, wherein the attributes
15 indicate the number of users who can be supported in a network simultaneously. Generally, network
slice is a virtualized, customized, and logically isolated portion of a telecommunications network (5G core network) that represents a dedicated instance of network resources, configurations, and functionalities within a shared network infrastructure. The load attribute is defined as a map data type with the network slice identifier as a key and the load value as a value of utilization or traffic
20 load on the network, the load value may range from 0 to 100. In an embodiment of the present
disclosure, a load value range from 0-50 may indicate low traffic load on the network whereas a load value above 50 may indicate a high traffic load on the network.
[0067] The network slice identifier refers to an identifier assigned to a specific slice of a
25 network. In the 5th generation core network, network slicing is used to divide a single network in
various slices of virtualized network instances. Generally, physical network resources are partitioned
into multiple virtual slices of network, where each network slice is configured for individual
services, applications. These slices are isolated from each other and operate independently, allowing
for dedicated resource allocation for each slice. The network slicing is done for specific use cases,
30 applications, or user requirements. For instance, where there is an increased demand for a high-speed
internet access, a network slice may be created optimized for high-speed internet. The network slice prioritizes high data throughput and low latency, which may be ideal for applications such as ultra-high-definition video streaming, online gaming, and virtual reality experiences allowing users subscribing to experience seamless connectivity and fast download/upload speeds. 35
[0068] In an implementation of the present disclosure, "NF123" is a unique identifier of the
network function (NF) [312] sending the registration request.
14

slice_1: Identifier of the first network slice, with a load value of 80, indicating a relatively high load level.
slice_2: Identifier of the second network slice, with a load value of 65, indicating a moderate load
level.
5 slice_3: Identifier of the third network slice, with a load value of 40, indicating a relatively low load
level.
[0069] The load attribute is stored at a profile level within the NF [312] to determine the load
level for each network slice serviced by the NF [312]. The load attribute is stored at a service level
10 within the NF [312] to determine the load level for each network slice specific to a NF service.
[0070] In an implementation of the present disclosure, the load values for slice_1, slice_2 and
slice_3 may be stored at NF [312] at different profile levels associated with the NF [312]. For
example,
15 Profile1 stores the above-mentioned load values of slice_1, slice_2 and slice_3.
Profile2 stores a different set of load values such as Slice_1: 90, slice_2: 75 and slice_3:50.
[0071] The service level refers to the list of services performed by the specific slice of a
network. According to the services, the load values may vary for different services. Service1 has the
20 above-mentioned load values, while Service2 has values such as Slice_1: 55, Slice_2: 95, Slice_3:
75.
[0072] Further, the processing unit [304] is configured to update, via the NF [312], a profile
with the load attribute associated with a respective network slice identifier and a corresponding load
25 value. In an implementation of the present disclosure, the processing unit [304] may update the
profile with the load attribute associated with a respective network slice identifier and a corresponding load value. For example, Profile2 load values are updated at the NF [312] to dynamically adjust resource allocations and configurations based on the current load levels of network slices associated with each profile.
30
[0073] The processing unit [304] is further configured to subscribe, via a network data
analytics entity [314], to the load attribute for the at least one network slice. The network data analytics entity [314] is a Network Data Analytics Function (NWDAF) node.
35 [0074] In an implementation of the present disclosure, the processing unit [304] of the network
data analytics entity [314] may subscribe to the load values stored at the Profile2 and Service2 load values in the 5th Generation Core network.
15

[0075] A storage unit [306], configured to store, via the NRF [310], the load attribute in a
database.
5 [0076] In an implementation of the present disclosure, the storage unit [306] may store the
subscribed to load values- Profile2 and Service2.
[0077] A transmitter [308], configured to transmit via the NF [312], a heartbeat message to the
NRF [310]. The heartbeat message comprises the load attribute for the at least one network slice.
10 The transmitter [308], configured to send, via the NRF [310] to the network data analytics entity
[314], a notification comprising the load attribute, upon detecting a change in the load value for the at least one network slice. The load attribute is reported by NFs in the heartbeat message towards the NRF [310]. Generally, when the NRF [310] detects that a given NF has not updated its profile for a configurable amount of time (longer than the heart-beat interval), the NRF changes the status
15 of the NF to SUSPENDED and considers that the NF and its services can no longer be discovered
by other NFs. The notification to the network data analytics entity [314] is triggered by a predetermined threshold of load value change for the network slice. The load attribute is transmitted within the heartbeat message at a pre-defined time interval. The pre-defined time interval for sending the heartbeat message maybe determined by the user. The notification comprising the load attribute
20 is sent within a configuration interval to prevent unnecessary data transmission to the network data
analytics entity. The configuration interval is a predefined time period that corresponds to a frequency of updates to the network data analytics entity.
[0078] In an implementation of the present disclosure, the transmitter [308] of the NF [312]
25 may send the heartbeat message to the NRF [310] which includes the current load values stored in
the storage unit [306]. The heartbeat message refers to a signal sent between devices within a network at regular intervals to indicate that they are working. The heartbeat message is sent to assist in monitoring the status of network slices, detecting failures or disruptions in communication, and facilitating detection of fault in the network slice. 30
[0079] Additionally, the notification may be triggered by the transmitter [308] to be sent to the
network data analytics entity [314] when the change in the previous load value and current load value breaches a predetermined threshold value. For example, the heartbeat message-"network_element_1" sends out the current load value of slice_1 of service2, i.e. 55. 35
16

[0080] The previous load value of slice_1 was 80. The difference between the previous and
current load values is 25. If the threshold is set to 20, since the difference breaches the predetermined threshold, a notification will be sent out to the NWDAF node [314].
5 [0081] Referring to FIG. 4, an exemplary method flow diagram [400] for reporting slice-
specific load information in a 5G core network, in accordance with exemplary implementations of
the present disclosure is shown. In an implementation the method [400] is performed by the system
[300]. Further, in an implementation, the system [300] may be present in a server device to
implement the features of the present disclosure. Also, as shown in Figure 4, the method [400] starts
10 at step [402].
[0082] At step [404], the method comprises receiving, by a receiver [302] via a network
repository function (NRF) [310], a registration request from a network function (NF) [312]. The registration request is associated with receiving a current load attribute for at least one network slice.
15 The registration request comprises a load attribute indicative of a load level for at least one network
slice. The load attribute refers to a map data type with the network slice identifier as a key and the load value as a value, with the load value ranging from 0 to 100. The network slice identifier refers to an identifier assigned to a specific slice of a network. In the 5th generation core network, network slicing is used to divide a single network in various slices of virtualized network instances. Network
20 slicing is done for specific use cases, applications, or user requirements. Generally, physical network
resources are partitioned into multiple virtual slices of network, where each network slice is configured for individual services, applications. These slices are isolated from each other and operate independently, allowing for dedicated resource allocation for each slice. The network slicing is done for specific use cases, applications, or user requirements. For instance, where there is an increased
25 demand for a high-speed internet access, a network slice may be created optimized for high-speed
internet. The network slice prioritizes high data throughput and low latency, which may be ideal for applications such as ultra-high-definition video streaming, online gaming, and virtual reality experiences allowing users subscribing to experience seamless connectivity and fast download/upload speeds.
30
[0083] In an implementation of the present disclosure, "NF123" may be a unique identifier of
the network function (NF) sending the registration request.
slice_1: Identifier of the first network slice, with a load value of 80, indicating a relatively high load
level.
35 slice_2: Identifier of the second network slice, with a load value of 65, indicating a moderate load
level.
17

slice_3: Identifier of the third network slice, with a load value of 40, indicating a relatively low load level.
[0084] The load attribute is stored at a profile level within the NF [312] to determine the load
5 level for each network slice serviced by the NF [312]. The load attribute is stored at a service level
within the NF [312] to determine the load level for each network slice specific to a NF service. The load attribute is transmitted within the heartbeat message at a pre-defined time interval.
[0085] In an implementation of the present disclosure, storing of the load values for slice_1,
10 slice_2 and slice_3 may be performed at NF [312] at different profile levels associated with the NF
[312]. For example,
Profile1 stores the above-mentioned load values of slice_1, slice_2 and slice_3. Profile2 stores a different set of load values such as Slice_1: 90, slice_2: 75 and slice_3:50.
15 [0086] The Service level refers to the list of services performed by the specific slice of a
network. According to the services, the load values may vary for different services.
Service1 has the above-mentioned load values, while Service2 has- Slice_1: 55, Slice_2: 95, Slice_3: 75.
20 [0087] Next, at step [406], the method encompasses updating, by a processing unit [304] via
the NF, a profile with the load attribute associated with a respective network slice identifier and a corresponding load value.
[0088] In an implementation of the present disclosure, updating of the profile with the current
25 load attribute may be performed at the processing unit [304]. For example, Profile2 load values are
updated at the NF [312] to dynamically adjust resource allocations and configurations based on the current load levels of network slices associated with each profile.
[0089] Further, at step [408], the method includes transmitting, by a transmitter [308] via the
30 NF [312], the heartbeat message to the NRF [310]. The heartbeat message comprises the load
attribute for the at least one network slice. In an implementation of the present disclosure, storing the subscribed to load values- Profile2 and Service2 may be performed at the storage unit [306].
[0090] In an implementation of the present disclosure, in the 5th Generation Core network
35 subscription may be performed by the processing unit [304] of the network data analytics entity
[314] to the current load values which are stored at the Profile2 and Service2 load values. Further,
at step [410], the method includes storing, by a storage unit [306] via the NRF [310], the load
18

attribute in database. The database is a part of the storage unit [306] which stores the current set of load attributes. Storing the current load attributes in the database eases the process of analysis and visualisation of the load attributes.
5 [0091] Next, at step [412], the method encompasses subscribing, by the processing unit [304]
via the network data analytics entity [314], to the load attribute for the at least one network slice. The network data analytics entity [314] is the Network Data Analytics Function (NWDAF) node.
[0092] Further, at step [414], the method includes sending, by the transmitter [308] via the
10 NRF [310], a notification to the network data analytics entity comprising the load attribute upon
detecting a change in the load value for the at least one network slice. The notification comprising
the load attribute is sent within a configuration interval to prevent unnecessary data transmission to
the network data analytics entity [314]. The configuration interval is a predefined time period that
corresponds to a frequency of updates to the network data analytics entity. The predefined time
15 period of the configuration interval may be defined a user. The notification to the network data
analytics entity [314] is triggered by a predetermined threshold of load value change for the network
slice. The predetermined threshold of the load value change for the network slice may be defined by
the user. The load attribute is defined as a map data type with the network slice identifier as a key
and the load value as a value of utilization or traffic load on the network, with the load value may
20 range from 0 to 100. In an embodiment of the present disclosure, a load value ranges from 0-50 may
indicate low traffic load on the network whereas a load value above 50 may indicate a high traffic
load on the network.
[0093] In an implementation of the present disclosure, sending of a heartbeat message by the
25 NF [312] to the NRF [310] may be performed by the transmitter [308], which may include the current
load values stored in the storage unit [306]. The heartbeat message refers to a signal sent between
devices within a network at regular intervals to indicate that they are working. The heartbeat message
is sent to assist in monitoring the status of network slices, detecting failures or disruptions in
communication, and facilitating detection of fault in the network slice. A notification may be
30 triggered to be sent by the transmitter [308] to the network data analytics entity [314] when a change
in the previous load value and current load value breaches a predetermined threshold value.
[0094] For example, the heartbeat message- "network_element_1" sends out the current load
value of slice_1 of service2, i.e. 55. The previous load value of slice_1 was 80. The difference
35 between the previous and current load values is 25. If the predetermined threshold is set to 20, since
the difference breaches the predetermined threshold, a notification will be sent out to the NWDAF node [314].
19

[0095] Referring to FIG.5 illustrates an exemplary signalling flow diagram [500] indicating
an exemplary process for providing slice level load reporting, in accordance with exemplary embodiments of the present disclosure. 5
[0096] The 5G Network Function (NF) [312] sends a registration request to a network
repository function (NRF) [310] via the receiver [302]. The registration request comprises a load attribute indicative of a load level for at least one network slice. The NF [312] updates a profile with the load attribute associated with the respective slice identifier and a corresponding load value.
10
[0097] During the NF Register or NF Update process, NFs may include an Attribute
“sliceLoad” with Data Type as Map object of load where key is “sNssai” with value as “load”. The Attribute can be present at “NF Profile” level in case NF Level load per slice is needed or can be present at “NFService” level in case service level load per slice is needed. Calculation of NF at slice
15 level load at NF level or at slice level is determined by individual NFs.
[0098] The NF [312] transmits the heartbeat message to the NRF [310]. The heartbeat message
includes the load attribute for the network slice. The load attribute is the map data type with the network slice identifier as the key and the load value as the value of utilization or traffic load on the
20 network, the load value may range from 0 to 100. In an embodiment of the present disclosure, a load
value range from 0-50 may indicate low traffic load on the network whereas a load value above 50 may indicate a high traffic load on the network. NF may be able to send the above attribute “sliceLoad” with the “value” set between 0-100 indicating the NF Level load for that specific slice. It is to be noted that multiple slices may be present in a message. Similarly, for Service level load,
25 path may be set as with the “value” set between 0-100 indicating the Service Level load for that
specific slice.
[0099] The heartbeat message may include a heart-beat timer, i.e., time duration expected
between the heartbeat message(s). The heartbeat message may be included in the registration
30 request, and the heartbeat timer may be defined by the user. The heartbeat message may be included
in response from the NRF [310] to registration requests. The registration request maybe indicated by ‘PUT’. The heartbeat message may be included in response from the NRF [310] to the NF profile . The response may be indicated by ‘PUT’ or ‘PATCH’.
35 [0100] The NRF [310] stores the load attribute parameter in the internal object list similar to
how it stores the load value reported by NFs in Heartbeat or NF Register or NF Update message.
20

[0101] The NFs [312] such as network data analytics entity (NWDAF) [314], the NWDAF
[314] in the present scenario, may also subscribe to the load attribute for the network slice by the processing unit [304]. Slice Level load as defined in 3gpp TS 29.510 and the NRF [310] may send notifications including the new parameter. 5
[0102] The NRF [310] sends a notification to the network data analytics entity [314]
(NWDAF). The notification includes the load attribute which is determined on the basis of change in the load value at the network slice.
10 [0103] The present disclosure further discloses a user equipment (UE) for reporting slice-
specific load information in a 5G network. The UE comprising a Processor [1004], configured to transmit a registration request from a network function (NF) [312], wherein the registration request comprises a load attribute indicative of a load level for at least one network slice. The processor [1004] is further configured to update a profile with the load attribute associated with a respective
15 network slice identifier and a corresponding load value. Furthermore, the processor [1004] is
configured to transmit a heartbeat message to the NRF [310], wherein the heartbeat message comprises the load attribute for the at least one network slice. The processor [1004] is further configured to store the load attribute in a database. Furthermore, the processor [1004] is configured to subscribe to the load attribute for the at least one network slice. The processor [1004] is further
20 configured to send a notification to the network data analytics entity comprising the load attribute
upon detecting a change in the load value for the at least one network slice.
[0104] The present disclosure further discloses a non-transitory computer readable storage
medium storing instructions for reporting slice-specific load information in a 5G network, the
25 instructions include executable code which, when executed by a one or more units of a system,
causes: a receiver of the system to receive via a network repository function (NRF), a registration request from a network function (NF), wherein the registration request comprises a load attribute indicative of a load level for at least one network slice; a processing unit of the system to update via the NF, a profile with the load attribute associated with a respective network slice identifier and a
30 corresponding load value; a transmitter of the system to transmit via the NF, a heartbeat message to
the NRF, wherein the heartbeat message comprises the load attribute for the at least one network slice; a storage unit of the system to store via the NRF, the load attribute in database; the processing unit of the system to subscribe, via a network data analytics entity, to the load attribute for the at least one network slice; and the transmitter of the system to send, via the NRF to the network data
35 analytics entity, a notification comprising the load attribute upon detecting a change in the load value
for the at least one network slice.
21

[0105] As is evident from the above, the present disclosure provides a technically advanced
solution for reporting slice-specific load information in the 5G core network. The present solution
provides a method and a system that can overcome the limitations of the existing solutions and the
3gpp TS 29.510, related to slice level load reporting which provides a solution that may enable all
5 5G NFs to report to the NRF, the NF Load level, on per slice basis in addition to full NF Level load
in Heartbeat or NF Update. It may also enable 5G NFs to report to the NRF, the Service Load Level on per slice basis in addition to full Service Level load in Heartbeat or NF Update.
[0106] While considerable emphasis has been placed herein on the disclosed implementations,
10 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. 15
22

We Claim:
1. A method for reporting slice-specific load information in a 5G network, the method comprising:
- receiving, by a receiver [302] via a network repository function (NRF) [310], a registration request from a network function (NF) [312], wherein the registration request comprises a load attribute indicative of a load level for at least one network slice;
- updating, by a processing unit [304] via the NF, a profile with the load attribute associated with a respective network slice identifier and a corresponding load value;
- transmitting, by a transmitter [308] via the NF [312], a heartbeat message to the NRF [310], wherein the heartbeat message comprises the load attribute for the at least one network slice;
- storing, by a storage unit [306] via the NRF [310], the load attribute in a database;
- subscribing, by the processing unit [304] via a network data analytics entity [314], to the load attribute for the at least one network slice; and
- sending, by the transmitter [308] via the NRF [310], a notification to the network data analytics entity comprising the load attribute upon detecting a change in the load value for the at least one network slice.

2. The method as claimed in claim 1, wherein the load attribute is defined as a map data type with the network slice identifier as a key and the load value as a value, with the load value ranging from 0 to 100.
3. The method as claimed in claim 1, wherein the notification comprising the load attribute is sent within a configuration interval to prevent unnecessary data transmission to the network data analytics entity [314], wherein the configuration interval is a predefined time period that that corresponds to a frequency of updates to the network data analytics entity.
4. The method as claimed in claim 1, wherein the load attribute is stored at a profile level within the NF [312] to determine the load level for each network slice serviced by the NF [312].
5. The method as claimed in claim 1, wherein the load attribute is stored at a service level within the NF [312] to determine the load level for each network slice specific to a NF service.
6. The method as claimed in claim 1, wherein the load attribute is transmitted within the heartbeat message at a pre-defined time interval.
7. The method as claimed in claim 1, wherein the notification to the network data analytics entity [314] is triggered by a predetermined threshold of load value change for the network slice.

8. The method as claimed in claim 1, wherein the network data analytics entity [314] is a Network Data Analytics Function (NWDAF) node.
9. A system for reporting slice-specific load information in a 5G network, the system comprising:

- a receiver [302], configured to receive, via a network repository function (NRF) [310], a registration request from a network function (NF) [312], wherein the registration request comprises a load attribute indicative of a load level for at least one network slice;
- a processing unit [304], configured to update, via the NF [312], a profile with the load attribute associated with a respective network slice identifier and a corresponding load value;
- a transmitter [308], configured to transmit via the NF [312], a heartbeat message to the NRF, wherein the heartbeat message comprises the load attribute for the at least one network slice;
- a storage unit [306], configured to store, via the NRF [310], the load attribute in a database;
- the processing unit [304], configured to subscribe, via a network data analytics entity [314], to the load attribute for the at least one network slice; and
- the transmitter [308], configured to send, via the NRF [310] to the network data analytics entity [314], a notification comprising the load attribute upon detecting a change in the load value for the at least one network slice.

10. The system as claimed in claim 9, wherein the load attribute is defined as a map data type with the network slice identifier as a key and the load value as a value, with the load value ranging from 0 to 100.
11. The system as claimed in claim 9, wherein the notification comprising the load attribute is sent within a configuration interval to prevent unnecessary data transmission to the network data analytics entity wherein the configuration interval is a predefined time period that corresponds to a frequency of updates to the network data analytics entity.
12. The system as claimed in claim 9, wherein the load attribute is stored at a profile level within the NF [312] to determine the load level for each network slice serviced by the NF [312].
13. The system as claimed in claim 9, wherein the load attribute is stored at a service level within the NF [312] to determine the load level for each network slice specific to a NF service.
14. The system as claimed in claim 9, wherein the load attribute is transmitted within the heartbeat message at a pre-defined time interval.

15. The system as claimed in claim 9, wherein the notification to the network data analytics entity is triggered by a predetermined threshold of load value change for the network slice.
16. The system as claimed in claim 9, wherein the network data analytics entity [314] is a Network Data Analytics Function (NWDAF) node.
17. A user equipment (UE) for reporting slice-specific load information in a 5G network, said UE comprising:
- a processor [1004] configured to:
o transmit a registration request from a network function (NF) [312], wherein the registration request comprises a load attribute indicative of a load level for at least one network slice; o update a profile with the load attribute associated with a respective network slice
identifier and a corresponding load value; o transmit a heartbeat message to a NRF [310], wherein the heartbeat message comprises
the load attribute for the at least one network slice; o store the load attribute in a database;
o subscribe to the load attribute for the at least one network slice; and o send a notification to a network data analytics entity comprising the load attribute upon detecting a change in the load value for the at least one network slice.