DESC:FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
The Patent Rules, 2003
COMPLETE SPECIFICATION
(See section 10 & rule 13)
1. TITLE OF THE INVENTION

SYSTEM AND METHOD FOR MANAGING NETWORK SLICE LOAD DISTRIBUTION IN A NETWORK

2. APPLICANT (S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED IN Office-101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
3. PREAMBLE TO THE DESCRIPTION

The following specification particularly describes the invention and the manner in which it is to be performed.

RESERVATION OF RIGHTS
[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and/or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.
FIELD OF DISCLOSURE
[0002] The present disclosure relates generally to the field of wireless communication systems. More particularly, the present disclosure relates to systems and methods for managing network slice load distribution in a network.

DEFINITIONS
[0003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.
[0004] 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.
[0005] 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.
[0006] 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.
[0007] 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 real-time admission control and management of the UEs across multiple network slices.
[0008] 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.
[0009] The term “public land mobile network (PLMN)” 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 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] The term “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.
[0012] The term “reference count” in the context of network slice management is a numerical value that keeps track of the number of User Equipments (UEs) associated with a specific network slice. The reference count serves as a counter to monitor the load on a slice.
[0013] These definitions are in addition to those expressed in the art.
BACKGROUND OF DISCLOSURE
[0014] 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.
[0015] 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 IoT devices with low-data requirements to high-bandwidth applications like video streaming, by allocating resources as needed to each network slice.
[0016] In a 5G network, various user equipment (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. In contrast, a UE with low data requirements may register to a network slice configured for low-resource usage. The access and mobility management function (AMF) is a control plane network function in the 5G core network responsible for handling registration and mobility management of UEs within the 5G network. The network slice admission control function (NSACF) manages and controls the number of registered UEs per network slice.
[0017] Further, some AMFs may become overloaded with the UEs from slices requiring high bandwidth, while others may be underutilized. This imbalance can be exacerbated by the limitations of traditional load-balancing methods, which often rely on static resource allocation or manual intervention. These methods may not adapt effectively to real-time fluctuations in network traffic. Moreover, during peak times, such as when a network slice experiences an unexpected surge in UEs (due to a popular event requiring high bandwidth), the AMF responsible for that slice can become overloaded. This overload can lead to service delays, dropped connections, and a degraded user experience. Conversely, slices with lower-than-expected traffic may have AMFs with significant idle capacity, representing wasted network resources.
[0018] Due to the above issues, overloaded AMFs can impede the network’s ability to handle user requests efficiently, reducing network performance. Additionally, inefficient resource utilization due to uneven distribution and underutilized resources prevents the network from achieving its full potential. The resultant service delays and connection drops significantly impact user satisfaction, highlighting the need for a more adaptive and efficient load management solution.
[0019] There is, therefore, a need in the art to provide a method and a system that can overcome the shortcomings of the existing prior arts.
OBJECTIVES OF THE PRESENT DISCLOSURE
[0020] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies are as listed herein below.
[0021] An objective of the present disclosure is to provide a system and a method for real-time reference count data-based dynamic load distribution monitoring for individual network slices and their public land mobile networks (PLMNs) identifiers (IDs).
[0022] Another objective of the present disclosure is to provide a system and method that allows network operators to make data-driven decisions to optimize resource allocation, thereby preventing any individual access and mobility management function (AMF) from becoming overloaded.
[0023] Another objective of the present disclosure is to provide a system and a method that optimizes network performance and resource utilization, ensuring smooth network operation even during high demand.
[0024] Other objectives 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.
SUMMARY
[0025] In an exemplary embodiment, a system for managing network slice load distribution in a network is disclosed. The system comprises a network slice admission control function (NSACF) server configured to receive a request from an access and mobility management function (AMF) to initiate a network slice availability check for one or more user equipments (UEs) associated with the AMF. The system further comprises a processing engine configured to process the received request to execute an admission control operation for the one or more UEs associated with the AMF (212), wherein the admission control operation comprises one of admitting and rejecting the one or more UEs to a defined network slice associated with a public land mobile network (PLMN), modify a reference count information for the one or more UEs within the defined network slice associated with the PLMN based on admission control result and create, by the NSACF server, a data report corresponding to the modified reference count information for the one or more UEs associated with the AMF.
[0026] In some embodiments, the request includes a flag indicating one or increasing and decreasing the one or more UEs for managing registration of the one or more UEs.
[0027] In some embodiments, the processing engine is configured to periodically update the reference count data in a database.
[0028] In some embodiments, if the flag is set to increase the one or more UEs, the processing engine is configured to verify whether a UE from amongst the one or more UEs is already registered based on a registration list stored in the database.
[0029] In some embodiments, if the one or more UEs are already registered in the registration list, the processing engine is configured to reject registration of the one or more UEs.
[0030] In some embodiments, if the one or more UEs are not registered in the registration list, the processing engine is configured to register the one or more UEs to the registration list stored in the database.
[0031] In another exemplary embodiment, a method for managing network slice load distribution in a network. The method comprises receiving, by a processing engine, a request from an access and mobility management function (AMF) to initiate a network slice availability check for one or more user equipments (UEs) associated with the AMF. The method comprises processing, by the processing engine, the received request to execute an admission control operation for the one or more UEs associated with the AMF, wherein the admission control operation comprises one of admitting and rejecting the one or more UEs to a defined network slice associated with a public land mobile network (PLMN). The method comprises modifying, by the processing engine, a reference count information for the one or more UEs within the defined network slice associated with the PLMN based on the admission control result. The method comprises creating, by the processing engine, a data report corresponding to the modified reference count information for the one or more UEs associated with the AMF.
[0032] In accordance with one embodiment of the present disclosure, a user equipment that is communicatively coupled with a network is disclosed. The coupling comprises receiving, by a processing engine, a request from an access and mobility management function (AMF) to initiate a network slice availability check for one or more user equipment (UEs) associated with the AMF, processing, by the processing engine, the received request to execute an admission control operation for the one or more UEs associated with the AMF, wherein the admission control operation comprises one of admitting and rejecting the one or more UEs to a defined network slice associated with a public land mobile network (PLMN), modifying, by the processing engine, a reference count information for the one or more UEs within the defined network slice associated with the PLMN based on the admission control result and creating, by the processing engine, a data report corresponding to the modified reference count information for the one or more UEs associated with the AMF.
[0033] 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.
BRIEF DESCRIPTION OF DRAWINGS
[0034] 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 the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0035] FIG. 1 illustrates an exemplary architecture for managing network slice load distribution in a network, in accordance with embodiments of the present disclosure.
[0036] FIG. 2A illustrates a block diagram of a system for managing network slice load distribution in a network, in accordance with embodiments of the present disclosure.
[0037] FIG. 2B illustrates an exemplary network architecture for implementing the system for managing network slice load distribution in a network, in accordance with an embodiment of the present disclosure, in accordance with embodiments of the present disclosure.
[0038] FIG. 3 illustrates an exemplary flow diagram for managing network slice load distribution in a network, in accordance with embodiments of the present disclosure.
[0039] FIG. 4 illustrates an exemplary flow diagram of a method for managing network slice load distribution in a network, in accordance with embodiments of the present disclosure.
[0040] FIG. 5 illustrates an exemplary computer system in which or with which the system may be implemented, in accordance with an embodiment of the present disclosure.
[0041] The foregoing shall be more apparent from the following more detailed description of the disclosure.
LIST OF REFERENCE NUMERALS
100 – Network Architecture
102-1, 102-2…102-N – Users
104-1, 104-2…104-N – User equipments
106 – Network
108 – System
202 – One or more processor(s)
204 – Memory
206 – Interface
207 – Network Slice Admission Control Function (NSACF) server
208 – Processing engine
209 - NSACF provisioning unit
210 – Database
212 – Access and Mobility Function (AMF)
510 – External storage device
520 – Bus
530 – Main memory
540 – Read only memory
550 – Mass storage device
560 – Communication port
570 – Processor

DETAILED DESCRIPTION OF DISCLOSURE
[0042] 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 all 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.
[0043] 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.
[0044] 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.
[0045] 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 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.
[0046] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.
[0047] 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.
[0048] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly 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 and all combinations of one or more of the associated listed items.
[0049] 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 with a network slice optimized for high data rates. In contrast, a UE with low data requirements may register to a network slice configured for low-resource usage. The AMF is a control plane network function in the 5G core network responsible for handling registration and mobility management of UEs within the 5G network, and the NSACF is a network function responsible for managing and controlling the number of registered UEs per network slice. However, balancing the workload among AMFs can be challenging. Neglecting careful monitoring of the workload among the AMFs can lead to overloading of the AMFs and inefficient resource utilization.
[0050] Accordingly, there is a need for systems and methods that facilitate dynamic AMF load distribution across network slices.
[0051] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a real-time reference count data-based dynamic load distribution monitoring system and method for individual network slices and their respective public land mobile networks (PLMNs) identifiers (IDs). Based on utilizing the real-time reference count data for all AMFs serving a specific network slice in a PLMN, the system and the method can dynamically and proactively allocate network resources to prevent any single AMF from becoming overloaded. This approach optimizes network performance and resource utilization, ensuring smooth network operation even during high demand.
[0052] The various embodiments throughout the disclosure will be explained in more detail with reference to FIG. 1- FIG. 5.
[0053] Referring to FIG. 1, the architecture (100) may include one or more computing devices or user equipments (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 be individually referred to as the user (102) and collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more user equipments (104-1, 104-2…104-N) may be individually referred to as the user equipment (104) and collectively referred to as the user equipment (104). A person of ordinary skill in the art will appreciate that the terms “computing device(s)” and “user equipment” may be used interchangeably throughout the disclosure. Although two user equipments (104) are depicted in FIG. 1, however any number of the user equipments (104) may be included without departing from the scope of the ongoing description.
[0054] In an embodiment, the user equipment (104) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device(e.g., a head-mounted 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 user equipment (104) may include but is not limited to, any electrical, electronic, electro-mechanical, or an 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, where the user equipment (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 a touchpad, touch-enabled screen, electronic pen, and the like. A person of ordinary skill in the art will appreciate that the user equipment (104) may not be restricted to the mentioned devices and various other devices may be used.
[0055] In an embodiment, the user equipment (104) may include smart devices operating in a smart environment, for example, an internet of things (IoT) system. In such an embodiment, the user equipment (104) may include but is 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 user equipment (104) may include, but is not limited to, intelligent, multi-sensing, network-connected devices that can integrate seamlessly with each other and/or with a central server or a cloud-computing system or any other device that is network-connected.
[0056] Referring to FIG. 1, the user equipment (104) may communicate with a system (108) through a network (106). In an embodiment, the network (106) may include at least one of a Fifth Generation (5G) network, 6G network, or the like. The network (106) may enable the user equipment (104) to communicate with other devices in the 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. In an embodiment, each of the UE (104) may have a unique identifier attribute associated therewith. In an embodiment, the unique identifier attribute may be indicative of Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Equipment Identity (IMEI) number, International Mobile Subscriber Identity (IMSI), Subscriber Permanent Identifier (SUPI) and the like.
[0057] 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.
[0058] 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).
[0059] FIG. 2A illustrates a block diagram (200) of the system (108) for managing network slice load distribution in a network (106), in accordance with embodiments of the present disclosure.
[0060] In an aspect, 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, edge or fog 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.
[0061] Referring to FIG. 2A, 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, referred to as I/O devices, storage devices, and the like. The interface(s) (206) may facilitate communication to/from 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, a Network Slice Admission Control Function (NSACF) server (207), processing unit/engine(s) (208), and a database (210).
[0062] In an embodiment, the processing unit/engine(s) (208) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) (208). In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) (208) may be processor-executable instructions stored on a non-transitory machine-readable storage medium, and the hardware for the processing engine(s) (208) may include 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(s) (208). In such examples, the system (108) may include 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 (108) and the processing resource. In other examples, the processing engine(s) (208) may be implemented by electronic circuitry.
[001] In an aspect, the processing engine (208) is configured to manage various operations related to network slice admission control. The processing engine (208) works in conjunction with other units of the system (108) to ensure efficient load distribution across the network slices. In an embodiment, the processing engine (208) may include an NSACF provisioning unit (209).
[002] In an aspect, a network slice admission control function (NSACF) server (207) may receive a request (for example, a POST request) from an AMF (212). The request (interchangeably referred to as POST request) is intended to initiate a network slice availability check and update procedure for one or more user equipment (UEs) (104). In an aspect, the network slice availability check and update procedure is a process that may assess the capacity of a specific network slice to accommodate additional user equipment (UEs) or increased traffic. It involves evaluating the current load on the slice, comparing it to the slice’s capacity, and potentially adjusting resource allocations to accommodate new one or more UEs (104) or increased traffic. For instance, when multiple users initiate high-bandwidth activities simultaneously, the AMF (212) sends a request to check if the network slice can handle the increased load. 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. In contrast, another slice may be designed for IoT devices with low data demands and extended battery life. These slices are said to be defined because they are pre-configured with specific network resources and capabilities to support the intended use case.
[0063] In an aspect, 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 (207). If the flag is set to increase the one or more UEs (104), the processing engine (208) or the NSACF provisioning unit (209) 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 (210). If the at least one UE is already registered in the registration list, the processing engine (208) or the NSACF provisioning unit (209) may reject registration of the at least one UE. Additionally, if the one or more UEs (104) is not registered in the registration list, the processing engine (208) or the NSACF provisioning unit (209) may register the at least one UE to the registration list stored in the database (210). In an embodiment, the registration list refers to a database record or structured set of entries maintained by the NSACF server (207) that tracks all currently registered one or more UEs (104) within a network slice. This list includes unique identifiers for the one or more UEs (104), such as their International Mobile Subscriber Identity (IMSI), and other relevant registration details. The registration list serves as a reference point to verify whether the one or more UEs (104) 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.
[0064] In an aspect, if the flag is set to decrease the one or more UEs (104), the processing engine (208) or the NSACF provisioning unit (209) 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 (210). If the at least one UE is already registered in the registration list, the processing engine (208) or the NSACF provisioning unit (209) may remove the at least one UE from the registration list.
[0065] In an aspect, upon receiving the POST request, the processing engine (208) or the NSACF provisioning unit (209) may process the POST request to perform admission control operation for the one or more UEs (104). The term admission control operation refers to the process of determining whether or not to allow the UE (104) to access a specific network slice. This decision is based on the current availability of resources within the network slice and the requirements specified in the POST request. The performing of the admission control operation for the one or more UEs (104) comprises one of admitting and rejecting the one or more UEs (104) to a defined network slice. In examples, the POST request may be processed to understand the requirements and current network slice availability. This step involves validating the POST request and preparing for the following stages of admission control. The admission control operation involves evaluating whether the network slice has sufficient resources to accommodate the new user equipment (UE) requesting access. The processing engine (208) or the NSACF provisioning unit (209) is configured to modify a reference count information 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). 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.
[0066] 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, 6G, etc.) that allow the UE (104) 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.
[0067] In an aspect, the processing engine (208) or the NSACF provisioning unit (209) may perform admission control operation for the UEs based on the processed POST request. This involves one of admitting and rejecting the UEs to a defined network slice, depending on the current load and available resources. For example, if a network slice is nearing its capacity, additional UEs might be temporarily rejected to maintain performance quality.
[0068] In an aspect, the processing engine (208) or the NSACF provisioning unit (209) may modify the reference count information for the one or more UEs within the defined network slice associated with the corresponding PLMN based on the admission control result or decision. This ensures that the system (108) always has the latest data on network slice utilization. The admission control result determines whether the UE (104) can be admitted or rejected to access a particular network slice associated with a corresponding PLMN. This decision is typically made based on predefined rules or criteria, such as the current network load, available resources, and the priority level of the UE (104) requesting access.
[0069] In an aspect, the processing engine (208) or the NSACF provisioning unit (209) may create a data report corresponding to the modified reference count information for the one or more UEs (104) associated with the AMF (212) serving the defined network slice in the PLMN. This report provides insights into network slice utilization and helps in making informed decisions for resource allocation.
[0070] In an embodiment, the database (210) may include 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 engines (208). In an embodiment, the database (210) may be separate from the system (108). 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. In some embodiments, the database (210) may be used to store information such as network slice configurations, subscriber profiles, and registration lists. For example, the database (210) may maintain a registration list of the UE, network slices, PLMNs, and other relevant data required for efficient network management.
[0071] FIG. 2B illustrates an example of network architecture (250) for managing network slice load distribution in a network (106), in accordance with an embodiment of the present disclosure.
[0072] As shown in FIG. 2B, the network architecture (250) includes the NSACF provisioning unit (209), an AMF (212), the NSACF server (207), and the database (210). Although, a single AMF (212) is shown in FIG. 2B, there may be more than one AMF deployed in the network architecture (250).
[0073] The NSACF provisioning unit (209), the AMF (212), the NSACF server (207), and the database (210) may be in communication with each other, and other network architecture components. In an aspect, the NSACF provisioning unit (209) may operate in conjunction with the NSACF server (207). In an implementation, the AMF (212) may communicate with the NSACF provisioning unit (209) via the NSACF server (207). In some implementations, the AMF (212) may directly communicate with the NSACF provisioning unit (209). Although the database (210) is shown external to the NSACF provisioning unit (209), in some embodiments, the database (210) may be implemented within the NSACF provisioning unit (209).
[0074] Additionally, the network architecture (250) may include a plurality of UEs (not shown in FIG. 2B). In examples, the network architecture (250) may be a 5G network architecture that may be divided into a plurality of network slices (interchangeably referred to as slices).
[0075] The NSACF provisioning unit (209) may be an application programming interface (API) that is configured to generate real-time reference count data of all AMFs (212) deployed in the network architecture (250) that serve a particular network slice in a PLMN. The AMF (212) 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 (212) may request the NSACF provisioning unit (209) (for example, via the NSACF server (207)) to perform network slice admission control for the number of UEs. The NSACF server (207) may manage several registered UEs to a network slice. In an implementation, the database (210) may store a registered list of the plurality of UEs. For example, the registered list stored in the database (210) may be periodically or dynamically updated as required.
[0076] The AMF (212) may trigger the number of UEs per network slice availability check and update procedure. The number of UEs per network slice availability check and update procedure is to update (i.e., increase or decrease) the number of UEs registered to a specific network slice. The AMF (212) may trigger the number of UEs per network slice availability check and update procedure by initiating a request (e.g. a POST request). The POST request may pertain to managing the number of UEs within the NSACF. In an implementation, through the POST request, the AMF (212) may request the NSACF provisioning unit (209) (for example, via the NSACF server (207) to perform an admission control operation to control the number of UEs registered to a network slice. The POST request refers to a method in HTTP (Hypertext Transfer Protocol) used to send data to the NSACF server (207) or create/update a resource. The POST request is typically used by various network functions like the AMF (212) 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 the UE (104), facilitating the admission and management of UEs (104) within network slices.
[0077] In an implementation, the AMF (212) may send the POST request to the resource representing the NSACF provisioning unit (209). In an embodiment, the AMF (212) may send the POST request to the NSACF provisioning unit (209) via the NSACF server (207). In some embodiments, the AMF (212) may send the POST request directly to the NSACF provisioning unit (209). The POST request may pertain to managing the number of UEs within the NSACF provisioning unit (209). The POST request may include a flag that indicates whether the number of UEs registered with a network slice is 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 the UE to be registered to a specific network slice, and the flag is set to “DECREASE” for the UE to be deregistered from a specific network slice.
[0078] According to an implementation, if the flag is set to “INCREASE” for the UE, the NSACF provisioning unit (209) may check whether the UE is already registered according to the registration list stored in the database (210). If the UE is not included (or recorded) in the registration list stored in the database (210), the NSACF server (207) may admit the UE. If the UE is included in the registration list stored in the database (210), the NSACF server (207) may remove the UE.
[0079] In an implementation, if the flag is set to “DECREASE” for a UE, the NSACF provisioning unit (209) may check whether the UE is already registered according to the registration list stored in the database (210). If the UE is included in the registration list stored in the database (210), the NSACF server (207) may remove the UE. If the UE is not included in the registration list stored in the database (210), the NSACF server (207) may not perform any action.
[0080] According to an implementation, the NSACF provisioning unit (209) may maintain a record file in the database (210). The record file may include reference count information (or reference count data) for the one or more UEs (104) associated with the AMF (212) serving a particular network slice in a PLMN. In an implementation, based on whether the UE is admitted or removed, the NSACF provisioning unit (209) may modify (or update) the reference count information for that specific UE within the designated network slice and corresponding PLMN. 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 (209) may update the reference count of all UEs within a designated network slice. For example, the record file stored in the database (210) may be periodically or dynamically updated as required. For example, the record file may be updated per second or minute.
[0081] Although it has been described that a single AMF, i.e., the AMF (212) sends a POST request to the NSACF provisioning unit (209), via the NSACF server (207), in some implementations, all AMFs may send respective POST requests to the NSACF provisioning unit (209), via the NSACF server (207). Accordingly, the NSACF provisioning unit (209) may maintain up-to-the-minute reference count data for all AMFs serving a specific network slice in the PLMN.
[0082] According to an implementation, the NSACF provisioning unit (209) is configured to perform an admission control operation based on which it is decided which UEs are allowed on a defined network slice, and which are not. For example, the NSACF provisioning unit (209) may perform the admission control of UEs based on threshold criteria. The threshold criteria may be configured for each network slice. The NSACF provisioning unit (209) may configure the threshold criteria as per the requirements of each network operator. In an example, according to the threshold criteria, the NSACF provisioning unit (209) may admit a defined number of UEs to a particular network slice. Beyond that number, the NSACF provisioning unit (209) may reject the UEs. According to some implementations, for high-priority UEs, the NSACF provisioning unit (209) is configured to perform the admission control without implementing any threshold criteria.
[0083] In an implementation, the NSACF provisioning unit (209) may generate real-time statistical data, including reference count information for all the AMFs serving a particular network slice in the PLMN. The reference count information for each network slice and PLMN ID can dynamically and proactively allocate resources to prevent any AMF (for example, the AMF (212)) from becoming overloaded.
[0084] The NSACF provisioning unit (209) 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 the AMF (212) serving a particular network slice in the PLMN.
[0085] FIG. 3 illustrates an exemplary flow diagram (300) for managing network slice load distribution in a network (106), in accordance with an embodiment of the present disclosure.
[0086] At step (302) of the flow diagram (300), the NSACF provisioning unit (209) may receive a request (e.g., POST request) from the AMF (212) via the NSACF server (207) for managing network slice load distribution in the network (106). In an example, the AMF load distribution for slice request may pertain to managing the number of UEs within the NSACF provisioning unit (209).
[0087] At step (304) of the flow diagram (300), the NSACF server (207) may create a data context (312) based on slice load distribution data. In examples, the data context (312) may include all the information related to the network architecture (250). According to an implementation, the data context (310) may be connected to the NSACF server (304). The NSACF server (304) may be configured to provide the slice load distribution data to the data context (310) for storage. The data context (310) may store the slice load distribution data. The NSACF server (304) may be the NSACF server (207).
[0088] At step (306) of the flow diagram (300), the NSACF provisioning unit (209) may request a parser and/or a processor to obtain information from the data context (312). In an implementation, the parser and the processor may be sub-components of the NSACF provisioning unit (209). According to an implementation, the parser and/or the processor may process the information from the data context (312). In an aspect, the parser may be a software component that reads, interprets, and analyses 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.
[0089] At step (308) of the flow diagram (300), the parser and/or the processor may process the data stored in the database (210) based on the processed information obtained from the data context (312). As a result, the processed data from the database (210) is obtained. For example, the processed data may include real-time reference count data of the AMF (212) serving a particular network slice in a PLMN.
[0090] In an implementation, steps (302) - (308) may be iterated until real-time reference count data of all the AMFs (212) serving the particular network slice in the PLMN is obtained.
[0091] At step (310) of the flow diagram (300), the NSACF provisioning unit (209) may generate a response based on the processed data. For example, the response may indicate a comprehensive overview of reference count data of the AMFs (212) serving a particular network slice in the PLMN. In an implementation, the NSACF provisioning unit (209) 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 resource allocation is optimized, and any individual AMF (212) is prevented from becoming overloaded. In an implementation, the NSACF provisioning unit (209) may send the response to the one or more network operators based on the request received from the one or more network operators.
[0092] FIG. 4 illustrates a method (400) for managing network slice load distribution in a network (106), in accordance with embodiments of the present disclosure.
[0093] At step 402, the method (400) includes receiving, by a processing engine (208), a request from an access and mobility management function (AMF) (212) to initiate a network slice availability check for one or more user equipments (UEs) (104) associated with the AMF (212). The request may be a POST request and may include a flag indicating one of increasing and decreasing for managing registration of the UEs within the NSACF server (207). The processing engine (208) receives the POST request from the AMF (212), via the NSACF server (207), to initiate a network slice availability check and update procedure for one or more user equipment (UEs). For example, consider a scenario where a user with a UE1 starts using their 5G-enabled device to stream a high-definition video. This UE requires a network slice connection that offers the bandwidth and low latency for seamless streaming. The AMF (212), responsible for managing mobility and connection, sends a request (e.g., a POST request) to the processing engine (208). This request aims to determine if the selected network slice has the available resources to accommodate UE 1 session with the network (106).
[0094] At step 404, the method (400) includes processing, by the processing engine (208), the received request to execute an admission control operation for the one or more UEs (104) associated with the AMF (212), wherein the admission control operation comprises one of admitting and rejecting the one or more UEs (104) to a defined network slice associated with a public land mobile network (PLMN). The admission control for the one or more UEs (104) includes one of admitting and rejecting the one or more UEs (104) to a defined network slice. For example, upon receiving the request, the processing engine (208) examines the request details to understand the specific requirements for the UE 1 session with the network (106). This includes evaluating parameters such as bandwidth, latency, and priority levels. The processing engine (208) also deciphers the flag within the request, indicating whether the UE registrations within the network slice should be increased or decreased. The processing engine (208) performs admission control based on the processed request, deciding whether to admit or reject the one or more UEs (104) to a defined network slice. For example, the processing engine (208) may check the current load on the network slice intended for the UE 1. If the slice has sufficient resources and is not heavily loaded, it admits the UE 1, allowing the high-definition video stream to proceed without interruption. Conversely, if the slice is already at capacity, the unit might reject the request, prompting the UE 1 to try connecting to another slice or wait until resources become available. In an aspect, if the flag is set to increase the one or more UEs (104), the processing engine (208) may verify whether a UE is already registered based on a registration list stored in the database (210). In an aspect, if the UE is already registered in the registration list, the processing engine (208) may reject the registration. In an aspect, if the one or more UEs (104) are not registered in the registration list, the processing engine (208) may register the UE to the registration list stored in the database (210).
[0095] At step 406, the method (400) includes modifying, by the processing engine (208), a reference count information for the one or more UEs (104) within the defined network slice associated with the PLMN based on admission control result. Based on the admission control decision, the processing engine (208) may update/modify the reference count data for the one or more UEs (104) within the defined network slice and the corresponding PLMN. For example, after admitting the UE1 to the network slice, the processing engine (208) may modify the reference count data to reflect the new load. This update/modification indicates that an additional UE is now utilizing the resources of this slice, which is crucial for maintaining accurate tracking of the one or more UEs (204) distributions and ensuring effective load management. In an aspect, the reference count data is updated periodically in the database (210).
[0096] At step 408, the method (400) includes creating, by the processing engine (208), a data report corresponding to the modified reference count information for the one or more UEs (104) associated with the AMF (212). For example, the processing engine (208) may compile a report detailing the one or more UEs (104) admitted or rejected to each network slice. This report, including the data for the UE 1 and others, provides insights into usage patterns and helps network operators optimize resource allocation for improved performance. l
[0097] FIG. 5 illustrates an exemplary computer system (500) in which or with which embodiments of the present disclosure may be implemented. As shown in FIG. 5, the system (108) may include an external storage device (510), a bus (520), a main memory (530), a read-only memory (540), a mass storage device (550), a communication port (560), and a processor (570). A person skilled in the art will appreciate that the system (108) may include more than one processor (570) and communication ports (560). Processor (570) may include various modules associated with embodiments of the present disclosure.
[0098] In an embodiment, the communication port (560) is 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 (560) is chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the system (108) connects.
[0099] In an embodiment, the memory (530) is Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. Read-only memory (540) is 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).
[00100] In an embodiment, the mass storage (550) is any current or future mass storage solution which is used to store information and/or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and/or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks (e.g., SATA arrays).
[00101] In an embodiment, the bus (520) communicatively couples the processor(s) (570) with the other memory, storage, and communication blocks. The bus (520) is, e.g., a Peripheral Component Interconnect (PCI)/PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB) or the like, for connecting expansion cards, drives and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (570) to the system (108).
[00102] 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 system (108). Other operators and administrative interfaces are provided through network connections connected through the communication port (560). The components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary illustration (500) limit the scope of the present disclosure.
[00103] In an embodiment, the UE is described. The UE is communicatively coupled with a network, the coupling comprises steps of receiving, by a processing engine, a request from an access and mobility management function (AMF) to initiate a network slice availability check for one or more user equipment (UEs) associated with the AMF, processing, by the processing engine, the received request to execute an admission control operation for the one or more UEs associated with the AMF, wherein the admission control operation comprises one of admitting and rejecting the one or more UEs to a defined network slice associated with a public land mobile network (PLMN),modifying, by the processing engine, a reference count information for the one or more UEs within the defined network slice associated with the PLMN based on the admission control result and creating, by the processing engine, a data report corresponding to the modified reference count information for the one or more UEs associated with the AMF.
[00104] 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.
[00105] 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.
[00106] 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
[00107] 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.
[00108] 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.
[00109] 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.
[00110] 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.
[00111] While considerable emphasis has been placed herein on 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 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 implemented merely as illustrative of the disclosure and not as a limitation.
[00112] The present disclosure provides a technical advancement related to dynamic load distribution in 5G and 6G networks. This advancement addresses the limitations of existing solutions by utilizing real-time reference count data to manage load distribution across network slices and PLMN IDs. The present disclosure creates a data context, processes information to obtain real-time data from a database, and generates responses for network operators. The present disclosure significantly improves resource allocation, network performance, and efficiency. By implementing this real-time, data-driven approach, the present disclosure enhances network management, ensuring optimal operation and preventing overloads, resulting in a smoother user experience and more efficient network utilization.
ADVANTAGES OF THE PRESENT DISCLOSURE
[00113] The present disclosure provides a system and a method that continuously monitors the number of UEs associated with each AMF serving a specific network slice and PLMN identifier. This real-time data provides information on network load distribution across slices.
[00114] The present disclosure provides the system and the method that dynamically adjusts resource allocation and prevents AMFs from becoming overloaded, ensuring efficient handling of user requests even during unexpected traffic surges in a specific slice.
[00115] The present disclosure provides the system and the method that prevents AMF overloads and helps maintain consistent, high-quality network performance. Users experience fewer service delays and connection drops, resulting in a smoother and more reliable user experience across all applications and services.
[00116] The present disclosure provides the system and the method that prevents the waste of resources that can occur when some AMFs are underutilized, leading to more efficient overall network operation.
[00117] The present disclosure provides the system and the method that enhances user satisfaction, as they can rely on the network to meet their needs without interruptions, even during peak usage times.

,CLAIMS:CLAIMS
We claim:
1. A system (108) for managing network slice load distribution in a network (106), the system (108) comprising:
a network slice admission control function (NSACF) server (207) configured to receive a request from an access and mobility management function (AMF) (212) to initiate a network slice availability check for one or more user equipments (UEs) (104) associated with the AMF (212); and
a processing engine (208) configured to:
process the received request to execute an admission control operation for the one or more UEs (104) associated with the AMF (212), wherein the admission control operation comprises one of admitting and rejecting the one or more UEs (104) to a defined network slice associated with a public land mobile network (PLMN);
modify a reference count information for the one or more UEs (104) within the defined network slice associated with the PLMN based on admission control result; and
create a data report corresponding to the modified reference count information for the one or more UEs (104) associated with the AMF (212).
2. The system (108) as claimed in claim 1, wherein the request includes a flag indicating one of increasing and decreasing the one or more UEs (104) for managing registration of the one or more UEs (104).
3. The system (108) as claimed in claim 1, wherein the processing engine (208) is configured to periodically update the reference count in a database (210).
4. The system (108) as claimed in claim 1, wherein if the flag is set to increase the one or more UEs (104), the processing engine (208) is configured to verify whether a UE (104) from amongst the one or more UEs (104) is already registered based on a registration list stored in a database (210).
5. The system (108) as claimed in claim 4, wherein if the one or more UEs (104) are already registered in the registration list, the processing engine (208) is configured to reject registration of the one or more UEs (104).
6. The system (108), as claimed in claim 4, wherein if the one or more UEs (104) are not registered in the registration list, the processing engine (208) is configured to register the one or more UEs (104) to the registration list stored in the database (210).
7. A method (400) for managing network slice load distribution in a network (106), the method (400) comprising of steps:
receiving (402), by a processing engine (208), a request from an access and mobility management function (AMF) (212) to initiate a network slice availability check for one or more user equipments (UEs) (104) associated with the AMF (212);
processing (404), by the processing engine (208), the received request to execute an admission control operation for the one or more UEs (104) associated with the AMF (212), wherein the admission control operation comprises one of admitting and rejecting the one or more UEs (104) to a defined network slice associated with a public land mobile network (PLMN);
modifying (406), by the processing engine (208), a reference count information for the one or more UEs (104) within the defined network slice associated with the PLMN based on admission control result; and
creating (410), by the processing engine (208), a data report corresponding to the modified reference count information for the one or more UEs (104) associated with the AMF (212).
8. The method (400) as claimed in claim 7, wherein the request includes a flag indicating one of increasing and decreasing the one or more UEs (104) for managing registration of the one or more UEs (104).
9. The method (400) as claimed in claim 7 further comprising periodically updating the reference count in a database (210).
10. The method (400) as claimed in claim 8 further comprising, if the flag is set to increase the one or more UEs (104), verifying whether a UE (104) from amongst the one or more UEs (104) is already registered based on a registration list stored in a database (210).
11. The method (400) as claimed in claim 10 further comprising, if the one or more UEs (104) are already registered in the registration list, rejecting registration of the one or more UEs (104).
12. The method (400) as claimed in claim 10 further comprising, if the one or more UEs (104) are not registered in the registration list, registering the one or more UEs (104) to the registration list stored in a database (210).
13. A user equipment (UE) (104) communicatively coupled to 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 communication network (104) is configured for performing a method (400) for managing network slice load distribution in the network (106), as claimed in claim 7.