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

SYSTEMS AND METHODS FOR NETWORK SLICE LOAD DISTRIBUTION FOR SESSION MANAGEMENT FUNCTIONS
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 network slice load distribution for session management functions (SMFs).

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 expression ‘Session Management Function (SMF)’ used hereinafter in the specification refers to a network function responsible for session management, including establishing, modifying, and terminating sessions. The SMF allocates IP addresses, manages session contexts, and handles mobility-related activities.
[0005] The expression ‘Network Slice Admission Control Function (NSACF)’ used hereinafter in the specification refers to the network function responsible for controlling the admission of user equipment into network slices. NSACF ensures that the resources within a network slice are allocated efficiently and that the slice can meet its intended quality of service requirements.
[0006] The term ‘NSACF server’ used herein refers to a Network Slice Admission Control Function server, which is a network function responsible for managing and controlling the registration and distribution of user equipments (UEs) across various network slices.
[0007] The expression ‘Public Land Mobile Network (PLMN)’ used hereinafter in the specification refers to a network established and operated by mobile network operators. The PLMN provides mobile communication services to the public and comprises the infrastructure, network components, and resources necessary to deliver these services.
[0008] 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 availability assessment.
[0009] The term ‘Application Programming Interface (API)’ 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.
[0010] 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 application or user need.
[0011] In network slice management, the term ‘reference count’ refers to a numerical value that tracks the number of User Equipment (UEs) associated with a specific network slice. The reference count serves as a counter to monitor the load on a slice.
[0012] These definitions are in addition to those expressed in the art.
BACKGROUND OF DISCLOSURE
[0013] 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.
[0014] 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.
[0015] 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 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. Session management function (SMF) is a control function that manages user sessions, including the establishment, modification, and release of sessions. For example, the sessions may be protocol data unit (PDU) sessions. For example, a UE registered on a network slice may initiate a PDU session establishment request through the SMF. The network slice admission control function (NSACF) is responsible for managing and controlling the number of PDU sessions established on a specific network slice.
[0016] The SMF plays a crucial role in managing user sessions within these network slices, including establishing, modifying, and releasing the PDU sessions. However, a significant challenge arises in distributing PDU session loads among network slices. Currently, there is no effective mechanism to monitor and control how PDU session loads are distributed among the various network slices managed by the SMF. This lack of visibility and control often leads to uneven and suboptimal slice load distribution, resulting in imbalances that can degrade network performance and stability.
[0017] 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
[0018] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies are as listed herein below.
[0019] An objective of the present disclosure is to provide a system and a method for network slice load distribution for session management functions (SMFs). The system and the method track and monitor the distribution of protocol data unit (PDU) sessions across network slices for a designated SMF. The system and the method provide efficient and balanced resource allocation across network slices, improving overall network performance.
[0020] Another objective of the present disclosure is to provide a system and a method that generates a list of network slices on which the SMF has made PDU establishment requests. This functionality enhances session management and assists in optimizing resource allocation.
[0021] Another objective of the present disclosure is to provide a system and a method that enable network operators to make data-driven decisions to ensure optimal use of each network slice, thereby enhancing the efficiency and efficacy of network operations.
[0022] Yet another objective of the present disclosure is to provide a system and a method that generates real-time reference count data indicative of a number of PDU sessions established on network slices for a defined SMF.
[0023] 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
[0024] In an exemplary embodiment, the present invention discloses a system for network slice load distribution for one or more session management functions (SMFs). The system comprises a network slice admission control function (NSACF) server configured to receive a request from at least one SMF to initiate a network slice availability assessment for one or more protocol data unit (PDU) sessions associated with a user equipment (UE). The system further includes a processing engine (104) to execute the network slice availability assessment for the one or more PDU sessions, wherein the network slice availability assessment comprises adjusting a number of the one or more PDU sessions associated with a defined network slice. The processing engine is further configured to modify a reference count associated with the one or more PDU sessions based on result of the network slice availability assessment and create a data report indicating the modified reference count, wherein the data report comprises a number of the one or more PDU sessions established on the defined network slice for the at least one SMF.
[0025] In some embodiments, the request comprises a flag indicating whether to increase or decrease the number of one or more PDU sessions associated with the defined network slice.
[0026] In some embodiments, the network slice availability assessment for the one or more PDU sessions comprises verifying the one or more PDU sessions existence within the defined network slice based on a registration list stored in a memory, admitting the one or more PDU sessions if the one or more PDU sessions do not exist within the defined network slice, and rejecting the one or more PDU sessions if the one or more PDU sessions already exist within the defined network slice.
[0027] In some embodiments, the processing engine is further configured to reject the request when the one or more PDU sessions established on the defined network slice reach a maximum value.
[0028] In some embodiments, the processing engine is further configured to provide the created data report to at least one network operator.
[0029] In some embodiments, the processing engine is configured to store the reference count of each network slice for the one or more PDU sessions in a database.
[0030] In some embodiments, the processing engine is configured to store the modified reference count of each network slice for the one or more PDU sessions in the database.
[0031] In an exemplary embodiment, a method for network slice load distribution for one or more session management functions (SMFs) is disclosed. The method comprises of receiving, by a network slice admission control function (NSACF) server, a request from at least one SMF to initiate a network slice availability assessment for one or more protocol data unit (PDU) sessions associated with a user equipment (UE), executing the network slice availability assessment for the one or more PDU sessions, wherein the network slice availability assessment comprises adjusting a number of the one or more PDU sessions associated with a defined network slice, modifying a reference count associated with the one or more PDU sessions based on result of the network slice availability assessment and creating a data report indicating the modified reference count, wherein the data report comprises a number of the one or more PDU sessions established on the defined network slice for the at least one SMF.
[0032] In an exemplary embodiment, user equipment (UE) is disclosed. 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 for one or more session management functions (SMFs). The method comprises of receiving, by a network slice admission control function (NSACF) server, a request from at least one SMF to initiate a network slice availability assessment for one or more protocol data unit (PDU) sessions associated with a user equipment (UE), executing the network slice availability assessment for the one or more PDU sessions, wherein the network slice availability assessment comprises adjusting a number of the one or more PDU sessions associated with a defined network slice, modifying a reference count associated with the one or more PDU sessions based on result of the network slice availability assessment and creating a data report indicating the modified reference count, wherein the data report comprises a number of the one or more PDU sessions established on the defined network slice for the at least one SMF.
[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 network slice load distribution for one or more session management functions (SMFs), in accordance with embodiments of the present disclosure.
[0036] FIG. 2A illustrates a block diagram of a system for network slice load distribution for one or more SMFs, in accordance with embodiments of the present disclosure.
[0037] FIG. 2B illustrates an exemplary network architecture for network slice load distribution for one or more SMFs, 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 network slice load distribution for one or more SMFs, in accordance with embodiments of the present disclosure.
[0039] FIG. 4 illustrates an exemplary flow diagram of a method for network slice load distribution for one or more SMFs, 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
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
200B – System architecture
222-1, 222-2…222-N – Session Management Functions (SMFs)
224 – Internal bus communication
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 user equipments (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. Session management function (SMF) is a control function that manages user sessions, including establishment, modification, and release of sessions. For example, the sessions may be protocol data unit (PDU) sessions. For example, a UE registered on a network slice may initiate a PDU session establishment request through the SMF. The network slice admission control function (NSACF) manages and controls the number of PDU sessions established on a specific network slice.
[0050] Slice load distribution for an SMF is essential for maintaining network stability and performance. However, there is no way to know how the PDU session load is distributed among network slices for a particular SMF. This results in uneven and suboptimal slice load distribution. For instance, when a UE registered on a network slice initiates a PDU session establishment request through the SMF, there is no mechanism to determine the current PDU load of the network slice. Consequently, network slices are allocated without knowledge of their load, leading to an imbalance in load distribution among network slices and suboptimal resource utilization.
[0051] Accordingly, there is a need for systems and methods that facilitate dynamic slice load distribution for one or more SMFs.
[0052] 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 generate real-time reference count data indicative of a number of PDU sessions established on network slices for a defined (or designated) SMF. This involves the distribution of PDU sessions across all network slices tied to their respective public land mobile networks (PLMNs) under the administration of the defined SMF. As a result, the operational efficiency and performance of the network are enhanced. The system and the method allow users to monitor the distribution of PDU sessions among network slices for a specific SMF. This functionality enhances session management and assists in optimizing resource allocation. The system and the method enable network operators to make data-driven decisions based on the real-time reference count data indicative of a number of PDU sessions established on network slices for a defined SMF. This ensures optimal use of each network slice and more agile and streamlined network operations.
[0053] The various embodiments throughout the disclosure will be explained in more detail with reference to FIG. 1- FIG. 5.
[0054] 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.
[0055] 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.
[0056] 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.
[0057] 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.
[0058] FIG. 2A illustrates a block diagram (200) of the system (108) for dynamic slice load distribution for at least one session management function (SMF), in accordance with embodiments of the present disclosure.
[0059] 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.
[0060] 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, processing unit/engine(s) (208) and a database (220).
[0061] 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) (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(s) (210) may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine(s) (210) 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) (210). 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) (210) may be implemented by electronic circuitry.
[0062] 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).
[0063] In an aspect, the NSACF server (208) and/or the receiving unit (212) may be configured to receive a request (for example, a POST request) from at least one SMF (not shown in FIG. 2A) to initiate a network slice availability assessment for one or more protocol data unit (PDU) sessions associated with a UE (104). In an embodiment, the NSACF server (208) facilitates communication between the at least one SMF and the processing engine (210). In particular, the NSACF server (208) receives the request from the at least one SMF and forwards the received request to the receiving unit (212). The request pertains to initiating one or more PDU sessions per network slice. For example, the request may include one or more flags indicating whether to increase or decrease the number of PDU sessions associated with a defined network slice. The receiving unit (212) may transmit the received request to the NSACF provisioning unit (214) for further processing. For example, suppose the for at least one SMF detects a spike in data demand in a specific network slice, then the at least one SMF may send a request to the receiving unit (212), indicating the need to increase the number of PDU sessions associated with that slice. For example, the request includes a flag to ‘increase’ the number of PDU sessions and details about the specific slice and required session capacity.
[0064] In an aspect, the NSACF provisioning unit (214) may be configured to execute the received request from the for at least one SMF. Based on the received request, the NSACF provisioning unit (214) may execute a network slice availability assessment for the PDU sessions. The network slice availability assessment comprises adjusting a number of the one or more PDU sessions associated with a defined network slice. The request includes a flag indicating whether to increase or decrease the number of PDU sessions associated with a defined network slice. For example, upon receiving the request to increase PDU sessions, the NSACF provisioning unit (214) may check the current resource availability within the network slice. The NSACF provisioning unit (214) may validate that there are adequate resources (e.g., bandwidth, processing power) to support additional PDU sessions and update the network slice configuration accordingly.
[0065] In an aspect, the network slice availability assessment for the one or more PDU sessions comprises verifying the existence of the one or more PDU sessions within the defined network slice based on a registration list stored in the memory (204). If the one or more PDU sessions do not exist within the defined network slice, the system (108) admits the one or more PDU sessions. Conversely, if the one or more PDU sessions already exist within the defined network slice, the system (108) rejects the one or more PDU sessions.
[0066] In an aspect, the defined network slice refers to a specific, isolated network segment configured to meet specific service requirements. Each network slice is designed to support a distinct 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 network slice may be designed for IoT devices with low data demands and extended battery life. These slices are defined because they are pre-configured with specific network resources and capabilities to support the intended use case.
[0067] In an aspect, the request may include a flag. The flag in the request may serve as a crucial indicator for the type of action needed. The flag explicitly states whether the number of PDU sessions should be increased or decreased. The flag can have values such as ‘increase’ or ‘decrease,’ which direct the subsequent processing steps. When the flag is set to ‘increase,’ it signals that the network slice is experiencing higher demand and requires additional PDU sessions to accommodate the increased data traffic. The request will include specific details such as the network slice identifier, the current number of active PDU sessions, and the desired number of additional sessions needed to meet the demand. Conversely, when the flag is set to ‘decrease,’ it indicates that the demand on the network slice has reduced, and some PDU sessions can be deactivated. This helps optimize resource utilization by freeing up resources that can be allocated elsewhere. The request will detail the network slice identifier, the current number of active PDU sessions, and the number of sessions to be deactivated
[0068] In an aspect, the updating unit (216) is configured to modify or update the reference count (interchangeably referred to as reference count data) associated with the one or more PDU sessions based on result of the network slice availability assessment. This ensures that the data reflecting the number of active PDU sessions on the defined network slice is current and accurate. For example, after the NSACF provisioning unit (214) adjusts the PDU sessions, the updating unit (216) records the new count of active PDU sessions in the database (220). This update is crucial for maintaining an accurate record of resource utilization.
[0069] In an aspect, the reference count typically refers to a numerical value that keeps track of the number of active associations or registrations for a particular resource. Specifically, in mobile networks, reference count can indicate the number of UEs registered to a specific network slice or service function, such as an Access and Mobility Function (AMF) within a defined Public Land Mobile Network (PLMN).
[0070] In an aspect, the generating unit (218) creates (or generates) a data report indicating the modified reference count. The data report includes a number of the one or more PDU sessions established on the defined network slice for the at least one SMF. The data report includes statistical data of the reference count of the PDU sessions established on the defined network slice. The generating unit (218) is configured to provide the created data report to at least one network operator for data-driven decision-making. For example, after updating/modifying the reference count, the generating unit (218) compiles a data report detailing the current number of PDU sessions, historical changes, and overall resource utilization. The generating unit (218) sends the report to the at least one SMF and network operators, helping them understand the network load and make informed decisions about future resource allocation.
[0071] In an aspect, the request comprises a flag indicating whether to increase or decrease the number of the one or more PDU sessions associated with the defined network slice. In an aspect, the processing engine (210) is further configured to reject the request when the one or more PDU sessions established on the defined network slice reach a maximum value.
[0072] In an embodiment, the database (220) 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 (210). In an embodiment, the database (220) may be separate from the system (108). In an embodiment, the database (220) may be indicative of including, but not limited to, a relational database, a distributed database, a cloud-based database, or the like.
[0073] In an aspect, the processing engine (210) is configured to store the reference count for each network slice in the database (220). In an aspect, the processing engine (210) is configured to store the modified reference count for each network slice in the database (220).
[0074] Referring to FIG. 2B, an example network architecture (200B) for network slice load distribution for at least one session management function (SMF), is illustrated in accordance with an embodiment of the present disclosure.
[0075] As shown in FIG. 2B, the network architecture (200B) includes the NSACF provisioning unit (214), a plurality of SMFs (222-1, 222-1,222-N), the NSACF server (208), and the database (220). A person of ordinary skill in the art will understand that the plurality of SMFs (222-1, 222-1,222-N) may be individually referred to as the SMF (222) and collectively referred to as the SMFs (222).
[0076] The NSACF provisioning unit (214), an one SMF (222), the NSACF server (208), and the database (220) may be in communication with each other and other network architecture components via internal bus communication (224). In an aspect, the NSACF provisioning unit (214) may operate in conjunction with the NSACF server (208). In an implementation, the SMF (222) communicates with the NSACF provisioning unit (214) via the NSACF server (208). In some implementations, the SMF (222) directly communicates with the NSACF provisioning unit (214). Although the database (220) is shown externally to the NSACF provisioning unit (214), in some embodiments, the database (220) may be implemented within the NSACF provisioning unit (214).
[0077] Additionally, the network architecture (300) may include a plurality of user equipments (UEs) (not shown in FIG. 1). In examples, the network architecture (300) may be a 5G network architecture that may be divided into a plurality of network slices (interchangeably referred to as slices).
[0078] The NSACF provisioning unit (214) may be an application programming interface (API) configured to generate a real-time reference count indicative of a number of PDU sessions established on network slices for at least one SMF (222). In an embodiment, the number of PDU Sessions per network slice availability assessment (or network slice availability check and update procedure) is to update (i.e. increase or decrease) the number of PDU Sessions established on an NSACF server. The SMF (222) is configured with the information indicating which network slice is subject to the NSACF server. The SMF (222) is a control function that manages user sessions, including establishment, modification, and release of sessions. In an embodiment, the SMF (222) triggers the number of PDU sessions per network slice availability check and update procedure for the network slices subject to NSACF at the beginning of a PDU Session Establishment procedure. In an aspect, the SMF (222) requests the NSACF provisioning unit (214) (for example, via the NSACF server (208)) to control for the number of PDU sessions established on a specific network slice. In an embodiment, if the SMF (222) sends Nnsacf_NumberOfPDUsPerSliceAvailabilityCheckAndUpdate_Request message to the NSACF server (208), then the SMF (222) includes in the message the S-NSSAI for which the number of PDU Sessions per network slice update is required and the update flag which indicates that the number of PDUs established on the S-NSSAI is to be increased if the procedure is triggered at the beginning of PDU Session Establishment procedure or indicates that the number of PDU Sessions on the S-NSSAI is to be decreased if the procedure is triggered at the end of PDU sessions release procedure. The NSACF server (208) manages several PDU sessions established on a network slice. In an implementation, the database (220) stores a list of network slices on which the SMF (222) has requested PDU sessions. In some implementations, the database (220) also stores a reference count indicative of one or more PDU requests made for each network slice by the SMF (222). For example, data stored in the database (220) is periodically or dynamically updated as required.
[0079] In operation, at least one SMF (222) requests current load distribution. In an implementation, the at least one SMF (222) triggers the number of PDU sessions per network slice availability assessment. The number of PDU sessions per network slice availability assessment is to update (i.e., increase or decrease) the number of PDU sessions established on a specific network slice. In an implementation, the at least one SMF (222) triggers the number of PDU sessions per assessment by sending a request (also referred to as PDU establishment request) to the NSACF provisioning unit (214), for example, via the NSACF server (208). In some implementations, the at least one SMF (222) sends the request directly to the NSACF provisioning unit (214). The request includes a flag indicating whether the number of PDU sessions established on a network slice will be increased or decreased. For example, the flag is set to “INCREASE” or “DECREASE”.
[0080] According to an implementation, the NSACF server (208) updates the current number of PDU sessions established on the network slice, i.e., increases or decreases the number of PDU sessions per network slice based on the information provided by the at least one SMF (222) in the request. In an embodiment, if the NSACF server (208) updates the current number of PDU Sessions established on the S-NSSAI, i.e. increase or decrease the number of PDU Sessions per network slice based on the information provided by the at least one SMF (222) in the update flag parameter. For example, if the flag is set to “INCREASE”, the NSACF server (208) checks whether the maximum number of PDU sessions established on the network slice has not been reached yet. If the maximum number of PDU sessions established on the network slice has not been reached yet, the NSACF server (208) increases the number of the one or more PDU sessions associated with that network slice. In an embodiment, if the maximum number of PDU Sessions established on the network slice has already been reached, then the NSACF server returns a result parameter indicating that the maximum number of PDU Sessions per network slice has been reached. If the maximum number of the one or more PDU sessions established on the network slice has been reached, the NSACF server (208) rejects the request received from the at least one SMF (222). In an implementation, if the flag is set to “DECREASE”, the NSACF server (208) decreases the number of PDU sessions associated with that network slice. Similarly, as described above, the at least one SMF (222) triggers the number of the one or more PDU sessions availability check and update procedure for all the network slices. In an embodiment, the number of PDU Sessions established on a network slice (e.g. increase or decrease) are updated. Also, if the number of PDU sessions on the network slice is to be increased, the NSACF first checks whether the number of the PDU Sessions on that network slice has reached the maximum number of PDU Sessions per network slice threshold. If the maximum number of PDU Sessions on the network slice has already been reached, the PDU Session Establishment procedure is rejected.
[0081] In an implementation, the NSACF server (208) stores the number of PDU sessions established on each network slice for the at least one SMF (222) in the database (220). In an embodiment, the Nnsacf_NumberOfPDUsPerSlice services control the number of PDU Sessions with a network slice for the network slices subject to the NSACF server (208). The at least one SMF (222) can request the NSACF server (208) to check whether the number of PDU Sessions established on a network slice has reached the maximum number of PDU Sessions per network slice and the at least one SMF (222) can also request the NSACF server (208) to update the number of PDU Sessions established on a network slice.
[0082] According to an implementation, the NSACF provisioning unit (214) interacts with the database (220) and obtains data. In an implementation, the NSACF provisioning unit (214) processes the data and generates a record file. For example, the record file includes a list of network slices on which PDU establishment requests have been made from the at least one SMF (222), along with the current load for the at least one SMF (222). For example, the current load is indicative of PDU sessions. In an implementation, the NSACF provisioning unit (214) stores the record file in the database (220). The record file stored in the database (220) is periodically or dynamically updated as required. For example, the record file is updated per second or per minute.
[0083] In an implementation, the NSACF provisioning unit (214) generates real-time statistical data including reference count indicative of a number of PDU sessions established on the network slices for the at least one SMF (222).
[0084] The reference count related to PDU sessions enables tracking and monitoring of the distribution of PDU sessions among network slices for the at least one SMF (222). This ensures more efficient and balanced resource allocation across network slices, improving overall network performance.
[0085] The NSACF provisioning unit (214) provides the real-time statistical data related to a number of PDU sessions established on network slices for the at least one SMF (222) to one or more network operators or other consumers (for example, on-demand). The one or more network operators make data-driven decisions based on the statistical data related to the number of PDU sessions established on network slices for the at least one SMF (222).
[0086] FIG. 3 illustrates an example flow diagram (300) for dynamic slice load distribution for at least one session management function (SMF) (222), in accordance with an embodiment of the present disclosure.
[0087] At step (302) of the flow diagram (300), the NSACF provisioning unit (214) receives a slice load distribution for an SMF request from the at least one SMF (222) via the NSACF server (208). In an example, the slice load distribution for the at least one SMF (222) pertains to managing the distribution of PDU sessions among the network slices for the at least one SMF (222).
[0088] At step (304) of the flow diagram (300), the NSACF provisioning unit (214) requests a parser and/or a processor to obtain information from a data context (410) created by the NSACF server (208). The data context (310) includes information on the number of PDU sessions established on each network slice for the at least one SMF (222). According to an implementation, the data context (310) may be connected to the NSACF server (208). The NSACF server (208) 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. In an implementation, the parser and the processor are sub-components of the NSACF provisioning unit (214). According to an implementation, the parser and/or the processor process the information from the data context. 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 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. The processor applies business rules or algorithms to the data, driving the dynamic slice load distribution process forward.
[0089] At step (306) of the flow diagram (300), the parser and/or the processor processes 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. For example, the processed data includes reference count related to PDU sessions. The processed data also includes a list of network slices on which the at least one SMF (222) has requested PDU sessions.
[0090] At step (308) of the flow diagram (300), the NSACF provisioning unit (214) generates a response based on the processed data. In examples, the response is indicative of a comprehensive overview of the reference count related to the PDU sessions. In an implementation, the NSACF provisioning unit (214) sends the response to one or more network operators. The one or more network operators make data-driven decisions based on the response. This encompasses the distribution of load across all network slices tied to their respective PLMNs, under the administration of the at least one SMF (222). Accordingly, optimal use of each network slice is ensured, creating a way for more agile and streamlined network operations. In an implementation, the NSACF provisioning unit (214) sends the response to the one or more network operators based on the request received from the one or more network operators.
[0091] FIG. 4 illustrates a method (400) for dynamic slice load distribution for at least one session management function (SMF) (222), in accordance with embodiments of the present disclosure.
[0092] At step (402), the method (400) is configured to receive, by a network slice admission control function (NSACF) server, a request from at least one SMF (222) to initiate a network slice availability assessment for one or more protocol data unit (PDU) sessions associated with a user equipment (UE). This initial step involves receiving a request containing details necessary for the network slice availability assessment. The request may include information about the PDU sessions that must be established, modified, or terminated. Further, the request may comprise a flag indicating whether to increase or decrease the number of the one or more PDU sessions associated with the defined network slice.
[0093] At step (404), the method (400) is configured to execute the network slice availability assessment for the one or more PDU sessions, wherein the network slice availability assessment comprises adjusting a number of the one or more PDU sessions associated with a defined network slice. This step verifies whether the requested PDU sessions can be accommodated within the defined network slice. Executing network slice availability assessment involves assessing the current network slice capacity and determining if the number of PDU sessions can either increase or decrease as requested. Further, the network slice availability assessment for the one or more PDU sessions comprises verifying the existence of the one or more PDU sessions within the defined network slice based on a registration list stored in the memory (204). If the one or more PDU sessions do not exist within the defined network slice, the method admits the one or more PDU sessions. Conversely, if the one or more PDU sessions already exist within the defined network slice, the method rejects the one or more PDU sessions. Additionally, the method is configured to reject the request when the one or more PDU sessions established on the defined network slice reach a maximum value.
[0094] At step (406), the method (400) is configured to modify a reference count associated with the one or more PDU sessions based on result of the network slice availability assessment. This step involves modifying the reference count to reflect the changes made during the availability check. The reference count includes information on the number of active PDU sessions per network slice, ensuring accurate tracking and management. Further, the processing engine (210) is configured to store the modified reference count of each network slice for the one or more PDU sessions in the database (220). This ensures that the most current data is maintained for future reference and decision-making.
[0095] At step (408), the method (400) is configured to create a data report indicating the modified reference count, wherein the data report comprises a number of the one or more PDU sessions established on the defined network slice for the at least one SMF (222). This step involves creating a comprehensive report detailing PDU session status and counts on each network slice. This report is crucial for network operators to understand the current load and make informed decisions regarding resource allocation and network management. Further, the processing engine (210) is further configured to provide the created data report to at least one network operator, facilitating transparent and data-driven network operations. Furthermore, the processing engine (210) is configured to store the reference count of each network slice for the one or more PDU sessions in a database (220), ensuring persistent data storage for ongoing network monitoring and analysis.
[0096] In an exemplary embodiment, user equipment (UE) is disclosed. 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 for one or more session management functions (SMFs). The method comprises of receiving, by a network slice admission control function (NSACF) server, a request from at least one SMF to initiate a network slice availability assessment for one or more protocol data unit (PDU) sessions associated with a user equipment (UE), executing the network slice availability assessment for the one or more PDU sessions, wherein the network slice availability assessment comprises adjusting a number of the one or more PDU sessions associated with a defined network slice, modifying a reference count associated with the one or more PDU sessions based on result of the network slice availability assessment and creating a data report indicating the modified reference count, wherein the data report comprises a number of the one or more PDU sessions established on the defined network slice for the at least one SMF.
[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). The 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 (660) 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] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made, and 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.
[00104] The present disclosure provides a technical advancement by providing a system and a method that enables tracking and monitoring slice load for one or more SMF(s). The system and the method allow users to monitor the distribution of PDU sessions among network slices for a specific SMF. Additionally, the system and the method provide a list of network slices on which the SMF has requested PDU sessions. As a result, session management is enhanced. This ensures more efficient and balanced resource allocation across network slices, improving overall network performance. Furthermore, the system and the method provide a mechanism for resource assignment and balancing workloads across the network. This mechanism enhances both the operational efficiency and performance of the network.
ADVANTAGES OF THE PRESENT DISCLOSURE
[00105] The present disclosure provides a system and a method for effectively managing network congestion. This ensures that network resources are utilized optimally, reducing the likelihood of overload and improving overall network performance.
[00106] The present disclosure provides the system and method for prioritizing UEs based on their historical data and operational parameters, ensuring that high-priority users experience fewer interruptions.
[00107] The present disclosure provides the system and the method that ensures the network can respond swiftly to changing congestion levels, maintaining stability and efficiency.
[00108] In an implementation, the system and method equip network operators with the ability to make decisions rooted in actual data. This ensures optimal use of each network slice, paving the way for more agile and streamlined network operations.

,CLAIMS:CLAIMS
We claim:
1. A system (108) for network slice load distribution for one or more session management functions (SMFs) (222), the system (108) comprising:
a network slice admission control function (NSACF) server (208) configured to receive a request from at least one SMF (222) to initiate a network slice availability assessment for one or more protocol data unit (PDU) sessions associated with a user equipment (UE) (104); and
a processing engine (210) configured to:
execute the network slice availability assessment for the one or more PDU sessions, wherein the network slice availability assessment comprises adjusting a number of the one or more PDU sessions associated with a defined network slice;
modify a reference count associated with the one or more PDU sessions based on result of the network slice availability assessment; and
create a data report indicating the modified reference count, wherein the data report comprises a number of the one or more PDU sessions established on the defined network slice for the at least one SMF (222).

2. The system (108), as claimed in claim 1, wherein the request comprises a flag indicating whether to increase or decre¬¬ase number of the one or more PDU sessions associated with the defined network slice.

3. The system (108) as claimed in claim 1, wherein the network slice availability assessment for the one or more PDU sessions comprises:
verifying the one or more PDU sessions existence within the defined network slice based on a registration list stored in a memory (204);
admitting the one or more PDU sessions if the one or more PDU sessions do not exist within the defined network slice; and
rejecting the one or more PDU sessions if the one or more PDU sessions already exist within the defined network slice.

4. The system (108) as claimed in claim 1, wherein the processing engine (210) is configured to reject the request when the one or more PDU sessions established on the defined network slice reach a maximum value.

5. The system (108) as claimed in claim 1, wherein processing engine (210) is configured to provide the created data report to at least one network operator.

6. The system (108) as claimed in claim 1, wherein the processing engine (210) is configured to store the reference count of each network slice for the one or more PDU sessions in a database (220).

7. The system (108) as claimed in claim 6, wherein the processing engine (210) is configured to store the modified reference count of each network slice for the one or more PDU sessions in the database (220).

8. A method (400) for network slice load distribution for one or more session management functions (SMFs) (222), the method (400) comprising of steps:
receiving (402), by a network slice admission control function (NSACF) server (208), a request from at least one SMF (222) to initiate a network slice availability assessment for one or more protocol data unit (PDU) sessions associated with a user equipment (UE) (104);
executing (404) the network slice availability assessment for the one or more PDU sessions, wherein the network slice availability assessment comprises adjusting a number of the one or more PDU sessions associated with a defined network slice;
modifying (406) a reference count associated with the one or more PDU sessions based on result of the network slice availability assessment; and
creating (408) a data report indicating the modified reference count, wherein the data report comprises a number of the one or more PDU sessions established on the defined network slice for the at least one SMF (222).

9. The method (400), as claimed in claim 8, wherein the request comprises a flag indicating whether to increase or decrease number of the one or more PDU sessions associated with the defined network slice.

10. The method (400) as claimed in claim 8, wherein the network slice availability assessment for the one or more PDU sessions comprises:
verifying the one or more PDU sessions existence within the defined network slice based on a registration list stored in the memory (204);
admitting the one or more PDU sessions if the one or more PDU sessions do not exist within the defined network slice; and
rejecting the one or more PDU sessions if the one or more PDU sessions already exist within the defined network slice.

11. The method (400) as claimed in claim 8, wherein the request is rejected when the one or more PDU sessions established on the defined network slice reach a maximum value.

12. The method (400) as claimed in claim 8, wherein the created data report is provided to at least one network operator.

13. The method (400) as claimed in claim 8, wherein the reference count is stored of each network slice for the one or more PDU sessions in a database (220).

14. The method (400) as claimed in claim 13, wherein the modified reference count is stored of each network slice for the one or more PDU sessions in the database (220).

15. 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 network slice load distribution for one or more session management functions (SMFs) (222), as claimed in claim 8.