WO2025074382A1 - Systems and methods for network slice load distribution - Google Patents

Abstract

A system (108) and method (400) for network slice load distribution is described The method includes receiving (402), by a network slice admission control function (NSACF) server (208), a request from an AMF (222), to initiate a registration check and update procedure for one or more UEs (104) associated with a plurality of network slices. The method (400) includes processing (404) the request to perform an admission control for the one or more UEs (104). The method (400) further includes updating (406) a reference count for each of the one or more UEs (104) registered within the defined network slice that is associated with a corresponding public land mobile network (PLMN) based on admission control decision. The method (400) further includes generating (408) a data report pertaining to the one or more UEs (104) registered within the defined network slice for the network slice load distribution.

Description

SYSTEMS AND METHODS FOR NETWORK SLICE LOAD DISTRIBUTION

RESERVATION OF RIGHTS

[001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, integrated circuit (IC) layout design, and/or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (herein after referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.

TECHNICAL FIELD

[002] The present disclosure relates generally to a field of wireless communication networks. More particularly, the present disclosure relates to a system and a method for network slice load distribution across access and mobility management functions (AMFs).

DEFINITION

[003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.

[004] The term “Access and mobility management function (AMF),” as used herein, refers to a control plane network function in the 5G core network that is responsible for handling registration and mobility management of User Equipments (UEs) within the 5G network.

[005] The term “network slice admission control function (NSACF)” as used herein, refers to a network function that is responsible for managing and controlling the number of registered UEs per network slice. NSACF service allows network function service consumers (e.g., AMF) to request NSACF to perform per slice admission control for a number of UEs.

[006] The term “POST request” as used herein, refers to a specific type of data transfer method used in a Hypertext Transfer Protocol (HTTP) communication for sending data from the AMF to a server (e.g., NSACF server). This data may be for various purposes, such as creating or updating information on the NSACF server. On receiving a POST request, the NSACF server performs network slice admission control related to the number of UEs registered to a network slice or a group of network slices.

[007] The term “NSACF server” as used herein, refers to a server that hosts the NSACF. It is responsible for managing admission control policies and ensuring that the UEs are only admitted to network slices if there are enough resources available. The NSACF server interacts with the AMF using Application programming interface (APIs) or other communication mechanisms (e.g., POST requests) to maintain realtime admission control and management of the UEs across multiple network slices.

[008] The term “NSACF provisioning unit” as used herein, is responsible for managing the admission of UEs into specific network slices based on the network slice availability, capacity, and defined policies. The NSACF provisioning unit interacts with the AMF to enforce network slice-specific policies, which includes deciding whether to admit or reject UEs based on current network slice resources. The NSACF provisioning unit tracks the number of UEs admitted to a network slice and ensures that the network slice is not overloaded.

[009] The term “public land mobile network (PEMN)” as used herein, refers to a specific mobile network to which a network slice belongs. The PLMN typically consists of multiple network elements, including base stations, core network components, and various access technologies (such as 4G, 5G, 6G etc.) that allow the UE to connect and communicate. Each PLMN is identified by a unique identifier known as a PLMN ID, which consists of a Mobile Country Code (MCC) and Mobile Network Code (MNC). The PLMN enables mobile subscribers to access services such as voice, data, and messaging across different regions and countries, supporting both local and roaming access.

[0010] The term “Application Programming Interface (API)” as used herein, refers to a set of rules and protocols that allows one software application to communicate and interact with another. The APIs define the methods and data formats that applications can use to request and exchange information with each other, typically over a network. The API allows the AMF to send requests, retrieve data, and execute commands to manage UE registrations, network slice allocations, and other related tasks.

[0011] These definitions are in addition to those expressed in the art.

BACKGROUND

[0012] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0013] Network slicing is a prominent feature of 5G networks that allows a single physical network to be divided (or sliced) into multiple logical and independent networks configured to meet various service requirements effectively. Each virtual network may be referred to as a network slice. Each network slice is an isolated end- to-end network that can be customized for different applications, services, or customers. This allows a single physical network to support a wide range of use cases, from loT devices with low-data requirements to high-bandwidth applications like video streaming, by allocating resources as needed to each network slice.

[0014] In a 5G network, various user equipments (UEs) may register to different network slices based on their specific requirements and preferences. For example, a UE with high-bandwidth needs for video streaming may register to a network slice optimized for high-data rates, while a UE with low-data requirements may register to a network slice configured for low-resource usage.

[0015] As the number of UEs increases, certain network slices may become overloaded, leading to degraded performance and quality of service. This imbalance may result in the underutilization of some slices while others are overburdened, affecting the network's overall efficiency. Moreover, the dynamic nature of the UE registration and mobility adds complexity to network slice management. The UEs may frequently switch slices based on their changing requirements or mobility, involving real-time updates and adjustments to the network slice allocations. The network may suffer from latency issues, increased congestion, and potential service interruptions without an efficient mechanism to handle these dynamic changes.

[0016] There is, therefore, a need for a system and a method that overcomes the limitations of the prior art.

SUMMARY

[0017] In an exemplary embodiment, a method for network slice load distribution across a plurality of access and mobility management functions (AMFs) is described. The method includes receiving, by a network slice admission control function (NSACF) server, a request from an AMF to initiate a registration check and update procedure, for one or more user equipments (UEs) associated with a plurality of network slices. To initiate the registration check and update procedure, the method includes processing, by a processing engine, the request received from the AMF to perform an admission control for the one or more UEs. Performing the admission control includes one of admitting or rejecting the one or more UEs registered on a defined network slice of the plurality of network slices. To initiate the registration check and update procedure, the method further includes updating, by the processing engine, a reference count for each of the one or more UEs registered within the defined network slice that is associated with a corresponding public land mobile network (PLMN) based on admission control decision. The method further includes generating, by the processing engine, a data report pertaining to the one or more UEs registered within the defined network slice for the network slice load distribution.

[0018] In some embodiments, the request comprises a flag, and the flag is set to either increase or decrease the one or more UEs for managing registration of the one or more UEs within the NSACF server.

[0019] In some embodiments, if the flag is set to increase the one or more UEs, the method includes verifying, by the processing engine, whether at least one UE from amongst the one or more UEs is already registered based on a registration list stored in a database.

[0020] In some embodiments, if the at least one UE is already registered in the registration list, the method includes rejecting, by the processing engine, registration of the at least one UE.

[0021] In some embodiments, if the at least one UE is not registered in the registration list, the method includes registering, by the processing engine, the at least one UE to the registration list stored in the database.

[0022] In some embodiments, if the flag is set to decrease the one or more UEs within the defined network slice, the method includes verifying, by the processing engine, whether at least one UE from amongst the one or more UEs is registered based on a registration list stored in a database, and removing, by the processing engine, the at least one UE from the registration list if the at least one UE is registered in the registration list.

[0023] In some embodiments, the method includes updating the reference count comprises adjusting the reference count for the one or more UEs within the defined network slice that is associated with the corresponding PLMN. [0024] In another exemplary embodiment, a system for network slice load distribution across a plurality of access and mobility management functions (AMFs) is described. The system comprises an NSACF server, a memory, and a processing engine communicatively coupled with the memory, configured to receive, by the NSACF server, a request from an AMF, to initiate a registration check and update procedure for one or more user equipments (UEs) associated with a plurality of network slices. To initiate the registration check and update procedure, the processing engine is configured to process the request received from the AMF to perform an admission control for the one or more UEs. Performing the admission control includes one of admitting or rejecting the one or more UEs registered on a defined network slice of the plurality of network slices. To initiate the registration check and update procedure, the processing engine is configured to update a reference count for each of the one or more UEs registered within the defined network slice that is associated with a corresponding public land mobile network (PLMN) based on admission control decision. The processing engine is configured to generate a data report pertaining to the one or more UEs registered within the defined network slice for the network slice load distribution.

[0025] In some embodiments, the request comprises a flag, and the flag is set to either increase or decrease the one or more UEs for managing registration of the one or more UEs within the NSACF server.

[0026] In some embodiments, if the flag is set to increase the one or more UEs, the processing engine is configured to verify whether at least one UE from amongst the one or more UEs is already registered based on a registration list stored in a database.

[0027] In some embodiments, if the at least one UE is already registered in the registration list, the processing engine is configured to reject registration of the at least one UE.

[0028] In some embodiments, if the at least one UE is not registered in the registration list, the processing engine is configured to register the at least one UE to the registration list stored in the database. [0029] In some embodiments, if the flag is set to decrease the one or more UEs within the defined network slice, the processing engine is configured to verify whether at least one UE from amongst the one or more UEs is registered based on a registration list stored in a database and remove the at least one UE from the registration list if the at least one UE is registered in the registration list.

[0030] In some embodiments, to update the reference count, the processing engine is configured to adjust the reference count for the one or more UEs within the defined network slice that is associated with the corresponding PLMN.

[0031] In some embodiments, the processing engine is further is configured to dynamically update a database with the updated reference count for the one or more UEs based on the admission control decision.

[0032] In another exemplary embodiment, a user equipment (UE) is described. The UE is communicatively coupled with a network, the coupling comprises steps of receiving, by the network, a connection request from the UE, sending, by the network, an acknowledgment of the connection request to the UE and transmitting a plurality of signals in response to the connection request, the network is configured for performing a method for network slice load distribution across a plurality of AMFs.

[0033] In another exemplary embodiment, the present disclosure discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for network slice load distribution across a plurality of access and mobility management functions (AMFs). The method includes receiving, by a network slice admission control function (NSACF) server, a request from an AMF, to initiate a registration check and update procedure, for one or more user equipments (UEs) associated with a plurality of network slices. To initiate the registration check and update procedure, the method includes processing, by a processing engine, the request received from the AMF to perform an admission control for the one or more UEs. Performing the admission control includes one of admitting or rejecting the one or more UEs registered on a defined network slice of the plurality of network slices. To initiate the registration check and update procedure, the method further includes updating, by the processing engine, a reference count for each of the one or more UEs registered within the defined network slice that is associated with a corresponding public land mobile network (PLMN) based on admission control decision. The method further includes generating, by the processing engine, a data report pertaining to the one or more UEs registered within the defined network slice for the network slice load distribution.

[0034] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure and are not restrictive.

OBJECTIVES OF THE PRESENT DISCLOSURE

[0035] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies, are as follows:

[0036] An objective of the present disclosure is to provide a system and a method for tracking and managing registrations of one or more user equipments (UEs) across various network slices and their corresponding public land mobile networks (PLMNs). This facilitates a logical approach to resource allocation and load distribution within the network, thereby optimizing network performance and efficiency.

[0037] Another objective of the present disclosure is to provide a system and a method that allow network operators to make data-driven decisions to ensure that each network slice of the network is utilized effectively, resulting in a more responsive and efficient network operation. The network operators are empowered to effortlessly determine the slice load distribution of the one or more registered UEs, thereby enhancing the efficiency and efficacy of network operations. [0038] Another objective of the present disclosure is to provide a system and a method for network slice load distribution across multiple access and mobility management functions (AMFs).

[0039] Another objective of the present disclosure is to provide a system and a method for obtaining reference count data of UE registrations for distribution of all network slices associated with their respective PLMNs, managed by a particular AMF.

[0040] Another objective of the present disclosure is to generate reports based on reference count data of UE registrations for dynamic network slice load distribution.

[0041] Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.

BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

[0042] 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. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0043] FIG. 1 illustrates an exemplary network architecture for implementing a system for network slice load distribution across a plurality of AMFs, in accordance with an embodiment of the present disclosure. [0044] FIG. 2A illustrates an exemplary block diagram of the system for network slice load distribution across the plurality of AMFs, in accordance with an embodiment of the present disclosure.

[0045] FIG. 2B illustrates an exemplary system architecture for network slice load distribution across the plurality of AMFs, in accordance with an embodiment of the present disclosure.

[0046] FIG. 3 illustrates an exemplary flow diagram for network slice load distribution across the plurality of AMFs, in accordance with an embodiment of the present disclosure.

[0047] FIG. 4 illustrates an exemplary flow diagram of a method for network slice load distribution across the plurality of AMFs, in accordance with an embodiment of the present disclosure.

[0048] FIG. 5 illustrates an exemplary computer system in which or with which embodiments of the present disclosure may be implemented.

[0049] The foregoing shall be more apparent from the following more detailed description of the disclosure.

LIST OF REFERENCE NUMERALS

100 - Network architecture

102 - Users

104 - One or more User Equipments (UEs)

106 - Network

108 - System

202 - Processor

204 - Memory 206 -Interface(s)

208 - Network slice admission control function (NSACF) server

210 - Processing engine

212 - Receiving unit

214 - NSACF provisioning unit

216 - Updating unit

218 - Generating unit

220 - Database

222 - Access And Mobility Management Function (AMF)

500 - Computing system

510 - External Storage Device

520 - Bus

530 - Main Memory

540 - Read Only Memory

550 - Mass Storage Device

560 - Communication Port

570 - Processor

DETAILED DESCRIPTION

[0050] 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 can 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. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.

[0051] 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.

[0052] 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, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

[0053] Also, it is noted that individual embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

[0054] 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 like the term “comprising” as an open transition word without precluding any additional or other elements.

[0055] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0056] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any combinations of one or more of the associated listed items. It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.

[0057] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical and computing device. The user device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating with other user devices and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery and an input-means such as a hard keypad and/or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.

[0058] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The 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 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 is a hardware processor.

[0059] As portable electronic devices and wireless technologies continue to improve and grow in popularity, the advancing wireless technologies for data transfer are also expected to evolve and replace the older generations of technologies. In the field of wireless data communications, the dynamic advancement of various generations of cellular technology are also seen. The development, in this respect, has been incremental in the order of second generation (2G), third generation (3G), fourth generation (4G), and now fifth generation (5G), and more such generations are expected to continue in the forthcoming time.

[0060] While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment as well as other embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.

[0061] In a 5G network, various UEs may register to different network slices based on their specific requirements and preferences. For example, a UE with high- bandwidth requirements for video streaming may register to a network slice optimized for high-data rates, while a UE with low-data requirements may register to a network slice configured for low-resource usage. AMF is a control plane network function in the 5G core network that is responsible for handling registration and mobility management of UEs within the 5G network. NSACF is a network function that is responsible for managing and controlling the number of registered UEs per network slice. [0062] When multiple AMFs are deployed in the network, it is a cumbersome task for the NSACF to obtain information corresponding to the network slices in real time and perform efficient load balancing across AMFs. For example, the information may include the current number of registered UEs in each network slice. Efficient load balancing is essential, as overloaded network slices can cause hindrances in UE admissions. For example, when a network slice becomes overloaded, it can lead to multiple problems, including quality of service (QoS) violations, resource allocation problems, and degraded performance, such as slower data speeds, increased latency, or dropped connections.

[0063] Accordingly, there is a need for a system and a method that facilitate dynamic network slice load distribution across a plurality of AMFs.

[0064] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a system and a method that generates real-time statistical data pertaining to each AMF of a plurality of AMFs. In an aspect, statistical data related to an AMF may include information on the number of registrations of UEs across various network slices within a network and their corresponding public land mobile networks (PLMNs) for the given AMF. This may assist in balancing the load across different AMFs so that network resources are efficiently utilized. Also, owing to load balancing across different AMFs, network operators may be enabled to make data-driven decisions to ensure that each network slice of the network is utilized effectively, thereby enhancing the efficiency and efficacy of network operations.

[0065] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0066] FIG. 1 illustrates an example of network architecture (100) for implementing a system (108) for network slice load distribution across a plurality of AMFs, in accordance with an embodiment of the present disclosure. [0067] As illustrated in FIG. 1, the network architecture (100) may include one or more user equipments (UEs) (104-1, 104-2... 104-N) associated with one or more users (102-1, 102-2... 102-N) in an environment. A person of ordinary skill in the art will understand that one or more users (102-1, 102-2... 102-N) may collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more UEs (104-1, 104-2... 104-N) may be collectively referred to as the UEs (104). Although only three user UEs (104) are depicted in FIG. 1, however, any number of the UEs (104) may be included without departing from the scope of the ongoing description.

[0068] In an embodiment, the UEs (104) may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the UEs (104) may include, but are not limited to, smartphones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, smart security system, smart home system, other devices for monitoring or interacting with or for the users (102) and/or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UEs (104) may include, but not limited to, intelligent, multisensing, network-connected devices, that may integrate seamlessly with each other and/or with a central server or a cloud-computing system or any other device that is network-connected.

[0069] Additionally, in some embodiments, the UEs (104) may include, but not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a phablet device, and so on), a wearable computer device (e.g., a headmounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and/or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the UEs (104) may include, but are not limited to, any electrical, electronic, electromechanical, or equipment, or a combination of one or more of the above devices, such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device, wherein the UEs (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (102) or the entity such as touchpad, touch-enabled screen, electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE (104) may not be restricted to the mentioned devices and various other devices may be used.

[0070] Referring to FIG. 1, the UEs (104) may communicate with a system (108) through a network (106) for sending or receiving various types of data. In an embodiment, the network (106) may include at least one of a 5G network, 6G network, or the like. The network (106) may enable the UE (104) to communicate with other devices in the network architecture (100) and/or with the system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.

[0071] In an embodiment, the network (106) may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network (106) may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet- switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0072] In an embodiment, the UE (104) is communicatively coupled with the system (108) via the network (106). The system (108) may receive a connection request from the UE (104). The system (108) may send an acknowledgment of the connection request to the UE (104). The UE (104) may transmit a plurality of signals in response to the connection request. The system (108) may be configured to perform slice load distribution across the plurality of AMFs.

[0073] Although FIG. 1 shows exemplary components of the network architecture (100), in other embodiments, the network architecture (100) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture (100) may perform functions described as being performed by one or more other components of the network architecture (100).

[0074] FIG. 2A illustrates an exemplary block diagram (200A) of the system (108) for network slice load distribution across a plurality of AMFs, in accordance with an embodiment of the present disclosure.

[0075] Referring to FIG. 2A, in an embodiment, the system (108) may include one or more processor(s) (202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (108). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non- transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may include any non-transitory storage device including, for example, volatile memory such as random-access memory (RAM), or non-volatile memory such as erasable programmable read only memory (EPROM), flash memory, and the like.

[0076] In an embodiment, the system (108) may include an interface(s) (206). The interface(s) (206) may include a variety of interfaces, for example, interfaces for data input and output devices (I/O), storage devices, and the like. The interface(s) (206) may facilitate communication through the system (108). The interface(s) (206) may also provide a communication pathway for one or more components of the system (108). Examples of such components include, but are not limited to, an NSACF server (208), a processing engine (210), and a database (220).

[0077] In an embodiment, the processing engine (210) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine (210). In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine (210) may be processor-executable instructions stored on a non- transitory machine -readable storage medium and the hardware for the processing engine (210) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine- readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine (210). In such examples, the system may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system and the processing resource. In other examples, the processing engine (210) may be implemented by electronic circuitry.

[0078] In an embodiment, the database (220) includes data that may be either stored or generated as a result of functionalities implemented by any of the components of the processor (202) or the processing engine (210). In an embodiment, the database (210) may be indicative of including, but not limited to, a relational database, a distributed database, a cloud-based database, or the like.

[0079] In an embodiment, the processing engine (210) may include a plurality of units. The plurality of units of the processing engine (210) may include, but is not limited to, a receiving unit (212), an NSACF provisioning unit (214), an updating unit (216), and a generating unit (218).

[0080] The receiving unit (212) is configured to receive a request (for example, a POST request) from an AMF (not shown in FIG. 2A). In an embodiment, the NSACF server (208) facilitates communication between the AMF and the processing engine (210). In particular, the NSACF server (208) receives the request (interchangeably referred to as POST request) from the AMF and forwards the received request to the receiving unit (212).

[0081] The POST request may initiate a registration check and update procedure for one or more user equipments (UEs) associated with a plurality of network slices. The receiving unit (212) may transmit the received POST request to the NSACF provisioning unit (214) for further processing.

[0082] The NSACF provisioning unit (214) is configured to process the POST request received from the AMF. Based on the processed POST request, the NSACF provisioning unit (214) performs an admission control for the one or more UEs. The admission control may involve admitting or rejecting the one or more UEs on a defined network slice of the plurality of network slices.

[0083] The defined network slice refers to a specific, isolated network segment configured to meet particular service requirements. Each network slice is designed to support a distinct type of application or user need. For instance, one network slice may be optimized for high-bandwidth activities like video streaming, providing enhanced data output and low latency, while another slice may be designed for loT devices with low data demands and extended battery life. The slices are defined because these are pre-configured with specific network resources and capabilities to support the intended use case.

[0084] In a more elaborate way, to perform the admission control, i.e., admitting or rejecting one or more UEs, the POST request may include a flag. The flag is set to either increase or decrease the one or more UEs (104) for managing registration of the one or more UEs (104) within the NSACF server (208). If the flag is set to increase the one or more UEs (104), the NSACF provisioning unit (214) may verify whether at least one UE from amongst the one or more UEs (104) is already registered based on a registration list stored in the database (220). If the at least one UE is already registered in the registration list, the NSACF provisioning unit (214) may reject registration of the at least one UE. Additionally, if the at least one UE is not registered in the registration list, the NSACF provisioning unit (214) may register the at least one UE to the registration list stored in the database (220). In an embodiment, the registration list refers to a database record or structured set of entries maintained by the NSACF server (208) that tracks all currently registered UEs within a network slice. This list includes unique identifiers for UEs, such as their International Mobile Subscriber Identity (IMSI), and other relevant registration details. The registration list serves as a reference point to verify whether a UE is already registered within a specific network slice and helps manage the admission process by either permitting new registrations or rejecting duplicate ones. This ensures efficient management of UE registrations, avoiding redundancy or overloading within network slices.

[0085] Further, if the flag is set to decrease the one or more UEs (104), the NSACF provisioning unit (214) may verify whether at least one UE from amongst the one or more UEs (104) is registered based on the registration list stored in the database (220). If the at least one UE is already registered in the registration list, the NSACF provisioning unit (214) may remove the at least one UE from the registration list.

[0086] Based on admission control decision, the updating unit (216) is configured to update a reference count for each of the one or more UEs registered within the defined network slice that is associated with a corresponding public land mobile network (PLMN). The reference count is a numerical value that keeps track of the one or more UEs associated with a specific network slice. The reference count essentially serves as a counter that increases or decreases based on the registration or deregistration of UEs to the network slice. The reference count helps in managing and monitoring the load and resource allocation of each network slice, ensuring that the network slice does not become overloaded and may maintain desired performance levels for the registered UEs.

[0087] The public land mobile network (PLMN) refers to the specific mobile network to which the network slice belongs. The PLMN typically consists of multiple network elements, including base stations, core network components, and various access technologies (such as 4G, 5G, etc.) that allow the UE to connect and communicate. Each PLMN is identified by a unique identifier known as a PLMN ID, which consists of a Mobile Country Code (MCC) and Mobile Network Code (MNC). The PLMN enables mobile subscribers to access services such as voice, data, and messaging across different regions and countries, supporting both local and roaming access.

[0088] In an embodiment, the updating unit (216) may adjust the reference count dynamically based on the admission control decision and store the updated reference count in the database (220). The admission control decision refers to the process determining whether the UE can be admitted or rejected to access a particular network slice associated with a corresponding PLMN. This decision is typically made based on a set of predefined rules or criteria, such as the current network load, available resources, and the priority level of the UE requesting access. For example, consider a network slice optimized for high-bandwidth applications. If there are initially 10 UEs registered to a network slice, the reference count may be 10. When a new UE requests to register to the network slice, the admission control mechanism evaluates whether to admit or reject the UE based on predefined criteria such as network capacity and current load. If the UE is admitted, the reference count is incremented by one, reflecting the addition of a new UE to the network slice. On the contrary, if an existing UE deregisters from the network slice, the reference count is decremented by one, indicating the reduction in the number of UEs using that network slice.

[0001] For example, if the initial reference count is 10 and a new UE is admitted, the reference count may increase to 11. If a UE subsequently deregisters, the reference count may decrease back to 10. This dynamic updating ensures that the network always has an accurate count of active UEs per network slice, facilitating efficient resource management and dynamic load distribution across the network.

[0002] The generating unit (218) is configured to generate a data report pertaining to the one or more UEs registered for the dynamic network slice load distribution. The data report may include statistical data on the reference count of UE registrations, distribution of network slices, and other relevant data to facilitate efficient network management and resource allocation.

[0089] The database (220) is configured to store data generated or used by the processing engine (210). This data may include the registration list, reference counts, and statistical data reports. The database (220) may be a relational database, a distributed database, a cloud-based database, or any other suitable type of database that supports the functionalities of the system (108). In some embodiments, the database (220) may be used to store information such as network slice configurations, subscriber profiles, and registration lists. For example, the database (220) may maintain a registration list of the UE, network slices, Public Land Mobile Networks (PLMNs), and other relevant data required for efficient network management.

[0090] Although FIG. 2A shows exemplary components of the system (108), in other embodiments, the system (108) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 2A. Additionally, or alternatively, one or more components of the system (108) may perform functions described as being performed by one or more other components of the system (108). [0091] Referring to FIG. 2B, an exemplary system architecture (200B) for network slice load distribution across the plurality of AMFs is illustrated, in accordance with an embodiment of the present disclosure.

[0092] As shown in FIG. 2B, the system architecture (200B) includes the NSACF provisioning unit (214), a plurality of AMFs (222-1, 222-2...222-N), the NSACF server (208), and the database (220). A person of ordinary skill in the art will understand that the plurality of AMFs (222-1, 222-2...222-N) may collectively be referred to as the AMF (222). It should be noted that for the sake of clarity and understanding, only three AMFs (222) are depicted in FIG. 2B, however, any number of the AMFs (222) may be included in the system architecture without departing from the scope of the ongoing description.

[0093] The NSACF provisioning unit (214), the AMF (222), the NSACF server (208), and the database (220) may be in communication with each other, as well as other network architecture components. In an aspect, the NSACF provisioning unit (214) may operate in conjunction with the NSACF server (208). In an implementation, the AMF (222) may communicate with the NSACF provisioning unit (214) using the NSACF server (208). In some implementations, the AMF (222) may directly communicate with the NSACF provisioning unit (214). Although the database (220) is shown external to the NSACF provisioning unit (214), in some embodiments, the database (220) may be implemented within the NSACF provisioning unit (214).

[0094] Additionally, the system architecture (200B) may include a plurality of UEs (not shown in FIG. 2B). In an example, the system architecture (200B) may include a 5G network architecture or a 6G network architecture that may be divided into a plurality of network slices (interchangeably referred to as slices).

[0095] In an embodiment, the NSACF server (208) efficiently manages and allocate resources within a network composed of multiple slices. The primary function of the NSACF server (208) is admission control. It receives requests, such as the POST request from the AMF (222), containing flags that either request the registration of new UEs to a network slice or the deregistration of UEs already admitted. The NSACF server (208) processes the request and makes decisions based on the current network load, slice capacity, and admission policies. If the flag indicates an increase in the number of UEs, the NSACF server (208) checks whether the UEs are already registered by referring to a registration list stored in a database. If a UE is found to be already registered, the request for additional registration is rejected, ensuring no duplication. If not, the UE is registered, thereby updating the database with the new registration information.

[0096] The registration list maintained by the NSACF server (208) is a crucial aspect of the system (108). The registration list contains details of all UEs currently registered to each network slice, allowing the server to monitor the slice’s load and prevent overloading. The NSACF server (208) updates the reference count for UEs associated with the particular network slice for every registration or deregistration decision. This reference count helps in managing and distributing load dynamically, ensuring that resources are evenly allocated across slices and that no slice becomes congested due to an excessive number of UEs.

[0097] In addition to handling individual requests, the NSACF server (208) contributes to network slice load distribution. Based on real-time data and historical information about UE registrations, it generates data contexts that include UE registration records and network slice load statistics. This processed data informs slice load management and allows the NSACF server (208) to decide when and how to redistribute UEs across slices to maintain balance and avoid congestion.

[0098] Furthermore, the NSACF server (208) is important in enforcing network policies. Regulating which UEs can access which slices ensures that service-level agreements (SLAs) and operator-defined policies are upheld. This prevents unauthorized access to critical slices and guarantees that each UE receives the appropriate quality of service.

[0099] The NSACF provisioning unit (214) may be configured to track and manage the registration of the one or more UEs across various (distinct) network slices and their corresponding (or associated) PLMNs for the AMF (222). The AMF (222) may be a network function service that is responsible for managing the access, mobility, and quality of service (QoS) for the plurality of UEs. In an aspect, the AMF (222) may request the NSACF provisioning unit (214), for example, using the NSACF server (208) to perform admission control for the one or more UEs. The NSACF server (208) may be a server responsible for managing a number of registered UEs per network slice. In an embodiment, the database (220) may store a registered list pertaining to the one or more UEs. In an example, the registered list stored in the database (220) may be periodically or dynamically updated as required.

[00100] In an embodiment, the AMF (222) may trigger the NSACF provisioning unit (214) to initiate the registration check and update procedure. The registration check and update procedure is to update (i.e., increase or decrease) the one or more UEs registered to a specific network slice. The registration check and update procedure may be performed by initiating a request (e.g., a POST request). In an implementation, through the POST request, the AMF (222) may request the NSACF provisioning unit (214) to perform admission control to control the one or more UEs registered within a defined network slice. The POST request refers to a method in HTTP (Hypertext Transfer Protocol) used for sending data to the NSACF server (208) or the to create/update a resource. The POST request is typically used by various network functions like the Access and Mobility Management Function (AMF) to interact with other functions (such as the Network Slice Admission Control Function, NSACF). The POST request in this scenario would carry information like registration data or updates about user equipment (UE), facilitating the admission and management of UEs within network slices. The POST request the NSACF to perform network slice admission control related to the number of UEs registered to a network slice, or a group of network slices

[00101] In an embodiment, the AMF (222) may send the POST request to the resource representing the NSACF. In an embodiment, the AMF (222) may send the POST request to the NSACF provisioning unit (214) using the NSACF server (208). In some embodiments, the AMF (222) may send the POST request directly to the NSACF provisioning unit (214). The POST request may pertain to managing the number of UEs within the NSACF server (208). The POST request may include a flag that indicates whether the one or more UEs registered per network slice are to be increased or decreased. In an example, the flag may be set to either “INCREASE” or “DECREASE”. The flag is set to “INCREASE” for a UE to be registered to a specific network slice, and the flag is set to “DECREASE” for a UE to be deregistered from a specific network slice.

[00102] According to an implementation, if the flag is set to “INCREASE” for a UE, the NSACF provisioning unit (214) may check whether the UE is already registered according to the registration list stored in the database (220). If the UE is not included (or recorded) in the registration list stored in the database (220), the NSACF provisioning unit (214) may accept the registration of the UE. If the UE is included in the registration list stored in the database (220), the NSACF provisioning unit (214) may reject the registration of the UE.

[00103] In an embodiment, if the flag is set to “DECREASE” for a UE, the NSACF provisioning unit (214) may check whether the UE is already registered according to the registration list stored in the database (220). If the UE is included in the registration list stored in the database (220), the NSACF provisioning unit (214) may remove the UE from the registration list. If the UE is not included in the registration list stored in the database (220), the NSACF provisioning unit (214) may not perform any action.

[00104] In one implementation, the NSACF provisioning unit (214) may maintain a record file in the database (220). The record file may include reference count data of UE registrations for distribution of all network slices associated with their respective PLMNs, managed by the AMF (222). In an implementation, based on whether the registration of a UE is accepted or rejected, the NSACF provisioning unit (214) may update (or adjust) the reference count for that specific UE within the designated network slice and corresponding PLMN. For instance, if the registration of the UE to a defined network slice is accepted, the NSACF server (208) may admit the UE to the network slice, and the NSACF provisioning unit (214) may increase the total number of UEs registered to the network slice. If the registration of the UE to a defined network slice is rejected, the NSACF server (208) may reject the admission of the UE to the network slice, and the NSACF provisioning unit (214) may decrease the total number of UEs registered to the network slice. Although the reference count updating process is described with reference to a single UE, in an implementation, in a similar manner as described above, the NSACF provisioning unit (214) may update the reference count of all UEs across various network slices and their corresponding PLMNs. Accordingly, the NSACF provisioning unit (214) may track the number of registrations of UEs across various network slices and their corresponding PLMNs.

[00105] In an example, the record file stored in the database (220) may be periodically or dynamically updated as required. Accordingly, the NSACF provisioning unit (214) may maintain exhaustive records pertaining to the number of registrations of UEs across distinct network slices and their associated PLMNs for the AMF (222).

[00106] In some embodiments, the NSACF server (208) is configured to perform admission control as to which UEs are allowed on the defined network slice and which are not. In an example, the NSACF server (208) may perform the admission control of UEs based on a threshold criteria (e.g., total available bandwidth and storage space within a slice). The threshold criteria may be configured for each network slice. The NSACF server (208) may configure the threshold criteria as per the requirements of each network operator. In an example, according to the threshold criteria, the NSACF server (208) may admit only a limited number of UEs to a particular network slice, and beyond that number, the NSACF server (208) may reject the UEs. According to some implementations, for high-priority UEs, the NSACF server (208) is configured to perform the admission control without implementing any threshold criteria.

[00107] In an embodiment, the NSACF provisioning unit (214) may generate a data report pertaining to real-time statistical data. The real-time statistical data includes information of the number of registrations of the UEs across various network slices and their corresponding public land mobile networks (PLMNs) for the AMF (222). Although it has been described that real-time statistical data is generated for AMF (222), in an implementation, the NSACF provisioning unit (214) may generate realtime statistical data for all the AMFs deployed in the network architecture (100).

[00108] The NSACF provisioning unit (214) may provide real-time statistical data to one or more network operators or other consumers (for example, on-demand). One or more network operators may obtain a comprehensive overview of reference count data of UE registrations for the distribution of all network slices associated with their respective PLMNs, all managed by the AMF (222). In some embodiments, the NSACF provisioning unit (214) may be an application programming interface (API) for the AMF (222) to obtain a comprehensive overview of reference count data for UE registrations. As a result, one or more network operators may be enabled to effortlessly determine the slice load distribution of the registered UEs for the AMF (222), thereby enhancing the efficiency and efficacy of a network operation. For instance, the one or more network operators may be enabled to make data-driven decisions to ensure that each network slice is effectively utilized, resulting in a more responsive and streamlined network operation.

[00109] FIG. 3 illustrates an example flow diagram (300) for slice load distribution across the plurality of AMFs, in accordance with an embodiment of the present disclosure.

[00110] At step (302) of the flow diagram (300), the NSACF provisioning unit (214) may receive a request (e.g., POST request) from the AMF (222) for slice load distribution. In an example, the POST request may pertain to managing the number of UEs within the network slices.

[00111] At step (304) of the flow diagram (300), the NSACF server (208) may create data context (306) based on slice load distribution data. In examples, the data context may include information such as, but not limited to, records of UE registrations, historical data of UE registrations, and real-time updates of the network slice load distribution. [00112] At step (306) of the flow diagram (300), the NSACF provisioning unit (214) may request a parser and/or a processor to obtain information from the data context. In an embodiment, the parser and the processor may be sub -components of the NSACF provisioning unit (214). According to an implementation, the parser and/or the processor may process the information obtained from the data context. In an aspect, the parser may be a software component that reads, interprets, and analyzes structured data from the data context, such as slice load distribution information. The parser extracts meaningful information (e.g., UE registrations, slice data) and converts it into a format that the system (108) can process. It essentially breaks down the complex data into more understandable and usable components for further operations. Additionally, the processor is a component responsible for executing operations on the parsed data. Once the parser has interpreted and extracted the necessary data, the processor performs computations, logic checks, and updates, such as determining the number of UEs in a specific slice or analyzing trends in UE registration. The processor applies business rules or algorithms to the data, driving the dynamic slice load distribution process forward.

[00113] At step (308) of the flow diagram (300), the parser and/or the processor may process the data stored in the database (220) based on the processed information obtained from the data context. As a result, processed data from the database (220) is obtained. In an example, the processed data may include data pertaining to the number of registrations of UEs across distinct network slices and their associated PLMNs.

[00114] At step (310) of the flow diagram (300), the NSACF provisioning unit (214) may generate a response based on the processed data. In an example, the response may be indicative of a comprehensive overview of reference count data of UE registrations for distribution of all network slices associated with their respective PLMNs, managed by the AMF (222). In an implementation, the NSACF provisioning unit (214) may send the response to one or more network operators. The one or more network operators make data-driven decisions based on the response to ensure that each network slice is utilized effectively, resulting in a more responsive and efficient network operation. In an implementation, the NSACF provisioning unit (214) may send the response to the one or more network operators based on the request received from the one or more network operators.

[00115] FIG. 4 illustrates an exemplary flow diagram of a method (400) for slice load distribution across the plurality of access and mobility management functions (AMFs), in accordance with an embodiment of the present disclosure.

[00116] At step (402), the method (400) includes receiving, by a network slice admission control function (NSACF) server (208), a request from an AMF (222) to initiate a registration check and update procedure, for one or more user equipments (UEs) (104) associated with a plurality of network slices. The request includes a flag. The flag is set to either increase or decrease the one or more UEs (104) for managing registration of the one or more UEs (104) within the NSACF server (208). In examples, the request may be a POST request.

[00117] At step (404), the registration check and update procedure includes processing, by the processing engine (210), the request received from the AMF (222) to perform an admission control for one or more UEs (104). Performing the admission control includes one of admitting or rejecting the one or more UEs (104) registered on a defined network slice of the plurality of network slices.

[00118] At step (406), the method (400) includes updating, by the processing engine (210), a reference count for each of the one or more UEs (104) registered within the defined network slice that is associated with a corresponding public land mobile network (PLMN) based on admission control decision. In some embodiments, updating the reference count includes adjusting the reference count for the one or more UEs (104) within the defined network slice associated with the corresponding PLMN

[00119] At step (408), the method (400) includes generating, by the processing engine (210), a data report pertaining to the one or more UEs (104) registered within the defined network slice for the network slice load distribution.

[00120] In some embodiments, if the flag is set to increase the one or more UEs (104), the method (400) includes verifying, by the processing engine (210), whether at least one UE from amongst the one or more UEs (104) is already registered based on a registration list stored in a database (220).

[00121] In some embodiments, if the at least one UE is already registered in the registration list, the method (400) includes rejecting, by the processing engine (210), registration of the at least one UE.

[00122] In some embodiments, if the at least one UE is not registered in the registration list, the method (400) includes registering, by the processing engine (210), the at least one UE to the registration list stored in the database.

[00123] In some embodiments, if the flag is set to decrease the one or more UEs (104) within the defined network slice, the method (400) includes verifying, by the processing engine (210), whether at least one UE from amongst the one or more UEs (104) is registered based on a registration list stored in a database (220), and removing, by the processing engine (210), the at least one UE from the registration list if the at least one UE is registered in the registration list.

[00124] In some embodiments, the method (400) includes dynamically updating, by the processing engine (210), a database (220) with the updated reference count for the one or more UEs (104) based on the admission control decision.

[00125] In another exemplary embodiment, the UE is described. The UE is communicatively coupled with a network, the coupling comprises steps of receiving, by the network, a connection request from the UE, sending, by the network, an acknowledgment of the connection request to the UE and transmitting a plurality of signals in response to the connection request, the network is configured for performing a method for network slice load distribution across a plurality of AMFs. The method includes receiving, by the NSACF server, a request from an AMF, to initiate a registration check and update procedure, for one or more UEs associated with a plurality of network slices. To initiate the registration check and update procedure, the method includes processing, by a processing engine, the request received from the AMF to perform an admission control for the one or more UEs. Performing the admission control includes one of admitting or rejecting the one or more UEs registered on a defined network slice of the plurality of network slices. To initiate the registration check and update procedure, the method further includes updating, by the processing engine, a reference count for each of the one or more UEs registered within the defined network slice that is associated with a corresponding public land mobile network (PLMN) based on admission control decision. The method further includes generating, by the processing engine, a data report pertaining to the one or more UEs registered within the defined network slice for the network slice load distribution.

[00126] In another exemplary embodiment, the present disclosure discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for network slice load distribution across a plurality of access and mobility management functions (AMFs). The method includes receiving, by a network slice admission control function (NSACF) server, a request from an AMF, to initiate a registration check and update procedure, for one or more user equipments (UEs) associated with a plurality of network slices. To initiate the registration check and update procedure, the method includes processing, by a processing engine, the request received from the AMF to perform an admission control for the one or more UEs. Performing the admission control includes one of admitting or rejecting the one or more UEs registered on a defined network slice of the plurality of network slices. To initiate the registration check and update procedure, the method further includes updating, by the processing engine, a reference count for each of the one or more UEs registered within the defined network slice that is associated with a corresponding public land mobile network (PLMN) based on admission control decision. The method further includes generating, by the processing engine, a data report pertaining to the one or more UEs registered within the defined network slice for the network slice load distribution.

[00127] In an embodiment, the NSACF provides Nnsacf_NSAC service. The Nnsacf_NSAC service provides the service capability for the NF Service Consumer (e.g. AMF) to request admission control for UEs accessing a specific network slice, or for PDU sessions to be established to a specific network slice. The following are the key functionalities of this NF service: request the NSACF to control the number of UEs registered to a specific network slice, e.g. perform availability check and update the number of UEs registered to a specific network slice.

[00128] In another embodiment, for network slice admission control for controlling the number of UEs, the NF Service Consumer (e.g. AMF, combined SMF+PGW-C) shall invoke the NumOfUEsUpdate service operation to request the NSACF to perform network slice admission control procedure related to the number of UEs, by using the HTTP POST method. The NF Service Consumer (e.g. AMF, combined SMF+PGW-C) shall send a POST request to the resource representing the network slice admission control related to the number of UEs through resource URL (i.e... /slices/UEs) in the NSACF.

[00129] In an embodiment, the payload body of the POST request shall contain the input data structure (i.e. UeACRequestData) for network slice admission control, which shall contain the following information: the SUPI(s) of the UE(s); the access type, over which the UE registers to the network or deregisters from the network; a list of S-NSSAIs which are subject to NSAC, and for each S-NSSAI an update flag indicates the operation to that S-NSSAI

[00130] In an embodiment, the HTTP method or custom operation (e.g., the POST) may request the NSACF to perform network slice admission control related to the number of UEs registered to a network slice, or a group of network slices.

[00131] In an embodiment, the update flag shall be set to "INCREASE" for a UE to be registered to a specific slice and shall be set to "DECREASE" for a UE to be deregistered from a specific slice. [00132] For NSAC of roaming UEs, the NF Service Consumer (e.g. AMF) shall provide the S-NSSAI in serving PLMN, and the corresponding mapped S-NSSAI in home PLMN to the NSACF in serving PLMN.

[00133] In an embodiment, for each S-NSSAI included in UeACRequestData, the NSACF shall perform the following actions: if the UE ID is not recorded in the UE registration list and the total number of UEs (including the UEs indicated in the request and the UEs already stored in the NSACF) does not exceed the maximum number of UEs allowed to be registered to this slice, the NSACF records the indicated UEs to the UE registration list stored in the NSACF, and updates the total number of UEs registered to this slice accordingly; if the update flag is set to "DECREASE" and if the UE is recorded in the UE registration list, the NSACF shall remove the indicated UEs from the UE registration list stored in the NSACF. If there are two or more UE registration entries associated with the UE ID, the NSACF shall only remove the entry associated with the requester NF. After removal, if a UE is no longer recorded in the UE registration list, the NSACF shall decrease the total number of UEs registered to this slice.

[00134] The FIG. 5 illustrates an exemplary computer system (500) in which or with which embodiments of the present disclosure may be implemented.

[00135] As shown in FIG. 5, the computer system may include an external storage device (510), a bus (520), a main memory (530), a read-only memory (540), a mass storage device (550), communication port(s) (560), and a processor (570). A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. The processor (570) may include various modules associated with embodiments of the present disclosure. The communication port(s) (560) may be any of an RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port(s) (560) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system connects.

[00136] The main memory (530) may be random-access memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (540) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input/Output System (BIOS) instructions for the processor (570). The mass storage device (550) may be any current or future mass storage solution, which can be used to store information and/or instructions. Exemplary mass storage device (550) includes, but is not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and/or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks.

[00137] The bus (520) communicatively couples the processor (570) with the other memory, storage, and communication blocks. The bus (520) may be, e.g., a Peripheral Component Interconnect (PCI)/PCI Extended (PCLX) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (570) to the computer system.

[00138] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus (520) to support direct operator interaction with the computer system. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (560). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure. [00139] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.

[00140] The present disclosure provides technical advancement related to slice load distribution by providing a system and a method that ensures the optimal operation of network resources. The network operators can effortlessly discern the slice load distribution of registered UEs for the AMF, thereby enhancing the efficiency and efficacy of the network operations. The system and the method track the number of UE registrations across various network slices and their corresponding PLMNs. This level of detailed context management facilitates resource allocation and load distribution within the network, thereby optimizing network performance and efficiency. The network operators can make data-driven decisions to ensure that each slice of the network is utilized effectively, resulting in a more responsive and streamlined network operation.

ADVANTAGES OF THE PRESENT DISCLOSURE

[00141] The present disclosure provides a system and a method for slice load distribution across the plurality of AMFs.

[00142] The present disclosure tracks and manages the one or more UEs registration across various network slices.

[00143] The present disclosure provides network operators with a more comprehensive view of UE registrations across slices. This allows the network operators to make data-driven decisions for managing network resources and optimizing performance. [00144] The present disclosure provides the API functionality to optimize the process of managing the UEs registration and load distribution. The network operators may easily access and update registration data, making adapting the network to changing demands and user needs easier.

Claims

CLAIMS We Claim:

1. A method (400) for network slice load distribution across a plurality of access and mobility management functions (AMFs), the method (400) comprising: receiving (402), by a network slice admission control function (NSACF) server (208), a request from an AMF (222) to initiate a registration check and update procedure, for one or more user equipments (UEs) (104) associated with a plurality of network slices, wherein the registration check and update procedure comprises: processing (404), by a processing engine (210), the request received from the AMF (222) to perform an admission control for the one or more UEs (104), wherein performing the admission control comprises one of admitting or rejecting the one or more UEs (104) registered on a defined network slice of the plurality of network slices; and updating (406), by the processing engine (210), a reference count for each of the one or more UEs (104) registered within the defined network slice that is associated with a corresponding public land mobile network (PLMN) based on admission control decision; and generating (408), by the processing engine (210), a data report pertaining to the one or more UEs (104) registered within the defined network slice for the network slice load distribution.

2. The method (400) as claimed in claim 1, wherein the request comprises a flag, and wherein the flag is set to either increase or decrease the one or more UEs (104), for managing registration of the one or more UEs (104), within the NSACF server (208).

3. The method (400) as claimed in claim 2, wherein if the flag is set to increase the one or more UEs (104), verifying, by the processing engine (210), whether at least one UE from amongst the one or more UEs (104) is already registered based on a registration list stored in a database (220).

4. The method (400) as claimed in claim 3, wherein if the at least one UE is already registered in the registration list, rejecting, by the processing engine (210), registration of the at least one UE.

5. The method (400) as claimed in claim 3, wherein if the at least one UE is not registered in the registration list, registering, by the processing engine (210), the at least one UE to the registration list stored in the database.

6. The method (400) as claimed in claim 2, wherein if the flag is set to decrease the one or more UEs (104) within the defined network slice verifying, by the processing engine (210), whether at least one UE from amongst the one or more UEs (104) is registered based on a registration list stored in a database (220); and removing, by the processing engine (210), the at least one UE from the registration list if the at least one UE is registered in the registration list.

7. The method (400) as claimed in claim 1, wherein updating the reference count comprises adjusting the reference count for the one or more UEs (104) within the defined network slice that is associated with the corresponding PLMN.

8. The method (400) as claimed in claim 1, further comprising: dynamically updating, by the processing engine (210), a database (220) with the updated reference count for the one or more UEs (104) based on the admission control decision.

9. A system (108) for network slice load distribution across a plurality of access and mobility management functions (AMFs), the system (108) comprising: a network slice admission control function (NSACF) server (208) configured to receive a request from an AMF (222) to initiate a registration check and update procedure for one or more user equipments (UEs) (104) associated with a plurality of network slices; a memory (204); and a processing engine (210) communicatively coupled with the memory (204), wherein to initiate the registration check and update procedure, the processing engine (210) is configured to: process the request received from the AMF (222) to perform an admission control for the one or more UEs (104), wherein performing the admission control comprises one of admitting or rejecting the one or more UEs (104) registered on a defined network slice of the plurality of network slices; and update a reference count for each of the one or more UEs (104) registered within the defined network slice that is associated with a corresponding public land mobile network (PLMN) based on admission control decision; and generate a data report pertaining to the one or more UEs (104) registered within the defined network slice for the network slice load distribution.

10. The system (108) as claimed in claim 9, wherein the request comprises a flag, and wherein the flag is set to either increase or decrease the one or more UEs (104) for managing registration of the one or more UEs (104) within the NSACF server (208).

11. The system (108) as claimed in claim 10, wherein if the flag is set to increase the one or more UEs (104), the processing engine (210) is configured to: verify whether at least one UE from amongst the one or more UEs (104) is already registered based on a registration list stored in a database (220).

12. The system (108) as claimed in claim 11, wherein if the at least one UE is already registered in the registration list, the processing engine (210) is configured to: reject registration of the at least one UE.

13. The system (108) as claimed in claim 11, wherein if the at least one UE is not registered in the registration list, the processing engine (210) is configured to: register the at least one UE to the registration list stored in the database (220).

14. The system (108) as claimed in claim 10, wherein if the flag is set to decrease the one or more UEs (104) within the defined network slice, the processing engine (210) is configured to: verify whether at least one UE from amongst the one or more UEs (104) is registered based on a registration list stored in a database (220); and remove the at least one UE from the registration list if the at least one UE is registered in the registration list.

15. The system (108) as claimed in claim 9, wherein to update the reference count, the processing engine (210) is configured to adjust the reference count for the one or more UEs (104) within the defined network slice that is associated with the corresponding PLMN.

16. The system (108) as claimed in claim 9, wherein the processing engine (210) is further is configured to: dynamically update a database (220) with the updated reference count for the one or more UEs (104) based on the admission control decision.

17. A user equipment (UE) (104) communicatively coupled with a network (106), the coupling comprises steps of: receiving, by the network (106), a connection request from the UE (104); sending, by the network (106), an acknowledgment of the connection request to the UE (104); and transmitting a plurality of signals in response to the connection request, wherein the network is configured to execute a method (400) fornetwork slice load distribution across a plurality of access and mobility management functions (AMFs), as claimed in claim 1.

18. A computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method (400) for network slice load distribution across a plurality of access and mobility management functions (AMFs), the method (400) comprising: receiving (402), by a network slice admission control function (NSACF) server (208), a request from an AMF (222), to initiate a registration check and update procedure, for one or more user equipments (UEs) (104) associated with a plurality of network slices wherein the registration check and update procedure comprises: processing (404), by a processing engine (210), the request received from the AMF (222) to perform an admission control for the one or more UEs (104), wherein performing the admission control comprises one of admitting or rejecting the one or more UEs (104) registered on a defined network slice of the plurality of network slices; and updating (406), by the processing engine (210), a reference count for each of the one or more UEs (104) registered within the defined network slice that is associated with a corresponding public land mobile network (PLMN) based on admission control decision; and generating (408), by the processing engine (210), a data report pertaining to the one or more UEs (104) registered within the defined network slice for the network slice load distribution.

19.