DESC:
FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
A PROVISIONING SYSTEM FOR MONITORING DYNAMIC SLICE LOAD DISTRIBUTION AND A METHOD THEREOF
2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN 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.
TECHNICAL FIELD
[0002] The present disclosure generally relates to the field of wireless communication systems. More particularly, the present disclosure relates to a provisioning system for monitoring dynamic session management functions (SMFs) load distribution across network slices.
DEFINITION
[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 ‘network slicing’ used hereinafter in the specification refers to a process of slicing (dividing) a single physical network into multiple logical and independent networks that are configured to effectively meet the various service requirements.
[0005] The expression ‘Session Management Function (SMF)’ used hereinafter in the specification refers to a key component of the 5G network architecture responsible for managing user sessions and ensuring efficient connectivity.
[0006] The expression ‘Network Slice Admission Control Function (NSACF) server’ used hereinafter in the specification refers to a key component of the network architecture responsible for managing the admission of user requests into specific network slices.
[0007] The expression ‘Network Slices’ used hereinafter in the specification refers to virtualized, isolated segments of a physical network infrastructure that provide tailored connectivity and services to different applications, users, or business needs. Each network slice operates independently and can be optimized for specific requirements.
[0008] The expression ‘PDU Session Establishment Requests’ used hereinafter in the specification refers to essential messages in 5G networks that initiate the creation of a Protocol Data Unit (PDU) session between a user equipment (UE) and the network. The Session Management Function (SMF) is responsible for managing the session, including the allocation of resources and policy enforcement.
[0009] These definitions are in addition to those expressed in the art.
BACKGROUND
[0010] 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.
[0011] In fifth generation (5G) network, a user equipment (UE) and a Next Generation NodeB (gNB) use next-generation application protocol (ngap) to transfer NAS (non-access stratum) messages, requesting a new session via N1 or N2 interface. In examples, the N1 interface may refer to an interface between the UE and an access and mobility management function (AMF). In examples, the N2 interface may refer to an interface between the AMF and the next generation NodeB (gNB). The AMF receives these requests, handles all access and mobility management-related tasks, and forwards session management requirements to a session management function (SMF). The AMF determines which SMF will handle the processing of the session request. The SMF is responsible for interacting with a separate data plane, creating, updating, and deleting protocol data unit (PDU) sessions, and managing session connections (session context) with the user plane function (UPF).
[0012] Network slice is a collection of network elements that cater to specific types of services. For instance, there could be a network slice for Internet of Things (IoT), another one for UEs, and yet another one for Vehicle-to-everything (V2X). Network slice splits the resources along the data path into multiple sets optimized for specific UEs or use cases. Each network slice is an isolated end-to-end network that can be customized for different applications, services, or customers. Different network slices can be dedicated to different purposes, such as ensuring a specific application or service gets priority access to capacity and delivery or isolating traffic for specific users or device classes. Slicing networks enables a network operator to maximize network resources and service flexibility.
[0013] In 5G architecture, the network slice admission control function (NSACF) server (service) enables multiple independent network slices to coexist and interoperate on the same physical infrastructure. The NSACF server monitors number of registered terminals (UEs) and the number of protocol data unit (PDU) sessions on the network slice. However, it is a cumbersome task for the NSACF server to monitor and track how many SMFs have requested PDU establishment on each network slice and the number of PDU establishment requests for the network slice. Therefore, the NSACF server is prone to distribute the load among SMFs in an even and optimal way. In such a scenario, load balancing between various SMFs, network efficiency, stability, and network performance are drastically reduced.
[0014] Hence, there is a need for a system that is configured to monitor dynamic SMFs load distribution over a network slice for effective and efficient allocation of network resources.
OBJECTIVES
[0015] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies, are as follows:
[0016] An objective of the present disclosure is to provide a provisioning system and a method that monitors the distribution of protocol data unit (PDU) session load for individual network slices and their public land mobile networks (PLMNs) identifiers (IDs).
[0017] Another objective of the present disclosure is to provide a provisioning system and a method that provides a list of the plurality of SMFs from which PDU session establishment requests have been made for that slice and monitors how many SMFs have requested PDU establishment on a user-defined network slice.
[0018] Yet another objective of the present disclosure is to provide a provisioning system and a method that tracks the number of requests for PDU establishment on a particular network slice.
[0019] Still another objective of the present disclosure is to provide a provisioning system and a method that offers enhanced control and flexibility to a network operator in managing network resources.
[0020] 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
[0021] The present disclosure discloses a provisioning system for monitoring dynamic session management functions (SMFs) load distribution over at least one network slice. The provisioning system includes a receiving unit and a processing unit. The receiving unit is configured to receive a request from a user equipment for providing real-time SMFs load distribution data for a user-defined network slice. The processing unit is communicatively coupled with the receiving unit to receive the request and is configured to establish a connection with a database coupled with at least one network slice admission control function (NSACF) server. The processing unit is configured to retrieve network slice load distribution details from the database. The processing unit is configured to process the retrieved network slice load distribution details to generate a list having SMFs load distribution data of a plurality of SMFs for the user-defined network slice.
[0022] In an embodiment, the provisioning system includes a communication unit configured to send the generated list to the user and the NSACF server. The NSACF server is configured to analyze the received list to perform one or more operations including determining resource availability and/or optimizing at least one provisioning process based on the dynamic SMFs load distribution
[0023] In an embodiment, the generated list includes a number of Protocol Data Unit (PDU) session establishment requests received from each SMF along with a request count, a timestamp corresponding to each PDU session establishment request, and session identifiers corresponding to active sessions on the user-defined network slice.
[0024] In an embodiment, the provisioning system includes a display unit to display the generated list to a user.
[0025] In an embodiment, the NSACF server is configured to define a maximum number of PDU session establishment requests to be served by each SMF over the user-defined network slice by analyzing the generated list.
[0026] The present disclosure discloses a method for monitoring dynamic session management functions (SMFs) load distribution over at least one network slice in real time. The method includes receiving, by a receiving unit, a request from a user equipment for providing real-time SMFs load distribution data for a user-defined network slice. The method includes establishing, by a processing unit, a connection with a database coupled with at least one network slice admission control function (NSACF) server. The method includes retrieving, by the processing unit, network slice load distribution details from the database. The method includes processing, by the processing unit, the retrieved network slice load distribution details to generate a list having SMFs load distribution data of a plurality of SMFs for the user-defined network slice.
[0027] In an embodiment, the method further includes sending, by a communication unit, the generated list to the user and the NSACF server. The NSACF server is configured to analyze the received list to perform one or more operations including determining resource availability and/or optimizing at least one provisioning process based on the dynamic SMFs load distribution.
[0028] In an embodiment, the method further includes displaying, on a display unit, the generated list to a user.
[0029] In an embodiment, the method further includes defining, by the NSACF server, a maximum number of PDU session establishment requests to be served by each SMF over the user-defined network slice by analyzing the generated list.
[0030] The present disclosure further discloses a user equipment (UE) communicatively coupled with a network. The coupling comprises steps of receiving a connection request, sending an acknowledgment of the connection request to the network, and transmitting a plurality of signals in response to the connection request, wherein the UE is configured to communicate with a provisioning system (200) to obtain dynamic session management functions (SMFs) load distribution. The provisioning system in the network is configured to monitor dynamic SMFs load distribution over at least one network slice in real time. The provisioning system includes a receiving unit and a processing unit. The receiving unit is configured to receive a request from a user to provide real-time SMFs load distribution data for a user-defined network slice. The processing unit is configured to cooperate with the receiving unit to receive the request and is configured to establish a connection with a database coupled with at least one network slice admission control function (NSACF) server. The processing unit is configured to retrieve network slice load distribution details from the database. The processing unit is configured to process the retrieved network slice load distribution details to generate a list having SMFs load distribution data of a plurality of SMFs for the user-defined network slice.
BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING
[0031] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0032] FIG. 1A illustrates an exemplary network architecture for implementing a provisioning system for monitoring dynamic session management functions (SMFs) load distribution over at least one network slice, in accordance with an embodiment of the present disclosure.
[0033] FIG. 1B illustrates another exemplary network architecture for implementing the provisioning system, in accordance with an embodiment of the present disclosure.
[0034] FIG. 2 illustrates a block diagram of the provisioning system, in accordance with an embodiment of the present disclosure.
[0035] FIG. 3 illustrates an exemplary flow diagram illustrating a method of monitoring dynamic SMFs load distribution over the at least one network slice, in accordance with an embodiment of the present disclosure.
[0036] FIG. 4 illustrates an exemplary computer system in which or with which the embodiments of the present disclosure may be implemented.
[0037] The foregoing shall be more apparent from the following more detailed description of the disclosure.
LIST OF REFERENCE NUMERALS
100, 150 – Network Architecture
102-1, 102-2…102-N – Users
104-1, 104-2…104-N – User Equipments
106 – Network
110 –A Plurality of Session Management Functions (SMFs)
120 – Network Slice Admission Control Function (NSACF) Server
130 – Database
160 – NSACF cluster
200 – Provisioning System
202 – Receiving Unit
204 – Memory
206 – A Plurality of Interfaces
210 – Processing Unit
212 – Communication unit
214 – Display unit
300 – Method flow chart
302 – 308 - Steps
400 – Computer System
410 – External Storage Device
420 – Bus
430 – Main Memory
440 – Read Only Memory
450 – Mass Storage Device
460 – Communication Port
470 – Processor
DETAILED DESCRIPTION
[0038] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.
[0039] 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.
[0040] 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.
[0041] Also, it is noted that individual embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.
[0042] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive like the term “comprising” as an open transition word without precluding any additional or other elements.
[0043] 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.
[0044] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any combinations of one or more of the associated listed items. It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.
[0045] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical and computing device. The user device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating with other user devices and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery and an input-means such as a hard keypad and/or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.
[0046] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor is a hardware processor.
[0047] As portable electronic devices and wireless technologies continue to improve and grow in popularity, the advancing wireless technologies for data transfer are also expected to evolve and replace the older generations of technologies. In the field of wireless data communications, the dynamic advancement of various generations of cellular technology are also seen. The development, in this respect, has been incremental in the order of second generation (2G), third generation (3G), fourth generation (4G), and now fifth generation (5G), and more such generations are expected to continue in the forthcoming time.
[0048] Radio Access Technology (RAT) refers to the technology used by mobile devices/ user equipment (UE) to connect to a cellular network. It refers to the specific protocol and standards that govern the way devices communicate with base stations, which are responsible for providing the wireless connection. Further, each RAT has its own set of protocols and standards for communication, which define the frequency bands, modulation techniques, and other parameters used for transmitting and receiving data. Examples of RATs include GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), UMTS (Universal Mobile Telecommunications System), LTE (Long-Term Evolution), and 5G. The choice of RAT depends on a variety of factors, including the network infrastructure, the available spectrum, and the mobile device's/device's capabilities. Mobile devices often support multiple RATs, allowing them to connect to different types of networks and provide optimal performance based on the available network resources.
[0049] While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment as well as other embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.
[0050] Data is communicated between a user and a data network through various components. In 5G and 6G, resource allocation and data path configuration are performed either statically or semi-statically. To ensure optimization for each individual UE or use case (such as rush hour traffic, regular hour traffic, enhanced mobile broadband (eMBB), Internet of Things (IoT), etc.), all these components are to be optimized. The resource allocation and parameters of these components can be configured dynamically through automation, or a set of parameters of all components along the data path for specific UEs or use cases may also be defined by a network operator. This set of parameters assigned for UEs or use cases is referred to as a “network slice”. 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 that are configured to effectively meet the various service requirements. Network slicing 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. It is required that the traffic be distributed efficiently across multiple network slices so that resource utilization and user experience can be improved, and latency can be reduced. Once the UE registration request is successfully completed with AMF, the SMF initiates a PDU establishment request for a specific network slice. However, there is no way to know how PDU sessions load is distributed among the SMFs for a particular network slice. This results in uneven and suboptimal slice load distribution. Due to the lack of information about the current PDU load of the network slice, the network slices are allocated between the SMFs without load knowledge. This resulted in an uneven load distribution among the network slices and suboptimal resource utilization. Load distribution among SMFs is crucial for ensuring optimal performance and resource utilization in the network. Accordingly, there is a need for systems and methods that monitor dynamic load distribution for SMFs over at least one network slice. The present disclosure monitors the SMF load distribution across the network slices for efficient resource allocation and optimization. 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 (provisioning system) and a 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 SMFs serving a specific network slice in a PLMN, the system and the method can dynamically and proactively allocate network resources to prevent any single SMF from becoming overloaded. This approach optimizes network performance and resource utilization, ensuring smooth network operation even during high demand. By employing the load distribution among SMFs in the effective manner, the present disclosure may be configured to provide the following enhanced capabilities:
• distributing session requests evenly across multiple SMFs to prevent any single SMF from becoming overwhelmed;
• continuously monitoring the load and performance metrics of each SMF to make real-time adjustments to the distribution of session requests based on current conditions;
• employing policies defined by a network operator to guide load distribution decisions. In an example, the policies may consider factors such as user location, service type, or resource availability;
• allocating session requests to SMFs based on the specific network slice requirements, ensuring that the right resources are available for different types of services;
• ensuring that the load distribution strategy can scale as the number of users and devices in the network increases, maintaining efficiency and reliability; and
• implementing mechanisms to redistribute load in the event of an SMF failure, ensuring that session management continues seamlessly without significant disruption.
[0051] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
[0052] FIG. 1A illustrates an exemplary network architecture (100) for implementing a provisioning system (200) for monitoring dynamic session management functions (SMFs) load distribution over at least one network slice, in accordance with an embodiment of the present disclosure.
[0053] As illustrated in FIG. 1A, the network architecture (100) may include one or more computing devices or user equipments (UEs) (104-1, 104-2, …. 104-N) associated with one or more users (102-1, 102-2, …., 102-N) in an environment. A person of ordinary skill in the art will understand that one or more users (102-1, 102-2, …102-N) may 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 UEs (104-1, 104-2, ….104-N) may be individually referred to as the UE (104) and collectively referred to as the UEs (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 three UEs (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. 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 at least one of a Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Equipment Identity (IMEI) number, an International Mobile Subscriber Identity (IMSI), a Subscriber Permanent Identifier (SUPI), and the like.
[0054] In an embodiment, the UE (104) may include smart devices operating in a smart environment, for example, an Internet of Things (IoT) system. In such an embodiment, the UE (104) may include, but is not limited to, smart phones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, a networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, a smart security system, a 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 UE (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.
[0055] In an embodiment, the UE (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 a wireless communication capabilities, and the like. In an embodiment, the UE (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, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device. In addition, the UE (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 an entity such as touch pad, a touch enabled screen, an electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE (104) may not be restricted to the mentioned devices and various other devices may be used.
[0056] In FIG. 1A, the UE (104) may communicate with the provisioning system (200) via a network (106) to enable the provisioning system (200) to monitor dynamic SMFs load distribution over at least one network slice. In an example, at least one network slice may be selected from an Enhanced Mobile Broadband (eMBB) slice, a Massive Machine Type Communication (mMTC) slice, and an Ultra-Reliable Low Latency Communication (URLLC) slice. The eMBB slice provides high data rates and improved capacity for applications requiring substantial bandwidth, such as video streaming and virtual reality. The mMTC slice supports a vast number of low-power devices, enabling efficient communication for applications like smart sensors and IoT devices that transmit small data packets infrequently. The URLLC slice ensures extremely low latency and high reliability, making it ideal for critical applications such as autonomous driving and remote surgery, where timely data transmission is essential.
[0057] In an embodiment, the network (106) may include at least one of a second generation (2G), third generation (3G), fourth generation (4G), fifth generation (5G) network, a sixth generation (6G) network, or the like. The network (106) may enable the UEs (104) to communicate with other devices in the network architecture (100) and/or with the provisioning system (200). 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, the network (106) may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. In an embodiment, the UE (104) may be communicatively coupled with the network (106). The network (106) may receive a connection request from the UE (104). The network (106) may send an acknowledgment of the connection request to the UE (104). The UE (104) may transmit several signals in response to the connection request.
[0058] FIG. 1B illustrates another exemplary network architecture (150) for implementing the provisioning system (200), in accordance with an embodiment of the present disclosure.
[0059] As shown in FIG. 1B, the network architecture (150) includes the provisioning system (200), a plurality of SMFs (110), a network slice admission control function (NSACF) server (120), and a database (130). Although, a single NSACF server (120) is shown in FIG. 1B, there may be more than one NSACF server (120) deployed in the network architecture (150).
[0060] In an exemplary aspect, the exemplary network architecture (150) includes the user equipment (UE), a 5G Next Generation NodeB (gNB) (not shown in FIG.), and a core network of the 5G network. In an example, the core network includes a number of components, such as a plurality of access and mobility management functions (AMFs), the plurality of SMFs (110), a user plane function (UPF), a plurality of NSACF servers (120), and so on. In an aspect, the provisioning system (200) is configured to be embedded with each NSACF server (120), and the database (130), thereby forming an NSACF cluster (160).
[0061] The core network of the 5G network is responsible for managing the network resources and providing connectivity between different UEs. To establish a connection (Protocol Data Unit (PDU) session), the UE (104) is required to establish the connection with a data network via the core network. For example, the UE (104) may set up a connection to the gNB. The UE (104) performs the random access procedure to initiate communication with the gNB and sends a radio resource control (RRC) connection request message to the gNB. After receiving the RRC connection request message, the gNB performs network attached storage (NAS) level authentication and initiates ciphering for the NAS messages with the core network. The core network completes the security procedure with the gNB and handles the RRC reconfiguration from the gNB. The UE (104) responds with a channel state information (CSI) report as requested by the gNB and the connection is established.
[0062] The UE (104) is configured to communicate with one or more networks. In an aspect, the UE (104) may also communicate with other types of networks (e.g., 5G cloud RAN, a next generation RAN (NG-RAN), long-term evolution (LTE) RAN, a cellular network, a wireless local area network (WLAN), etc.) and the UE may also communicate with networks over a wired connection.
[0063] The UE (104) and the gNB are connected to the core network. The plurality of AMFs is configured to perform connection and mobility management in the 5G RAN. In an example, the AMF may perform operations related to registration procedure management between the UE and the SMF. The AMF is configured to determine which SMF is best suited to handle the requirements of the UE. Bases upon the connection request received (having a requested network slice) from the UE, the AMF queries the NRF (Network Repository Function) to find the SMF for the requested network slice. The selection of the SMF is based on various parameters like service type (S-NSSAI), network data (DNN), and operator policies. The selected SMF sets up the PDU session according to the defined network slice, ensuring the UE connects to the desired service efficiently.
[0064] In an aspect, the UE sends a PDU session establishment request to the SMF after authentication. In an example, the PDU session establishment request may include various parameters such as session type (Type of PDU session (e.g., IPv4, IPv6), requested QoS (quality of service requirements for the session), and network slice information (identifies the network slice for the session).
[0065] The plurality of SMFs (110) performs operations related to session management, such as, but not limited to, session establishment, session release, IP address allocation, policy and QoS enforcement, etc. When the UE registration request is successfully completed with the AMF, the determined SMF initiates the PDU establishment request for a specific network slice. The SMF processes the request, checks resource availability, and interacts with other functions (e.g., Policy Control Function, PCF) for policy enforcement. User Plane Function (UPF) is configured to manage the data traffic associated with the PDU session. Upon successful validation, the SMF instructs the UPF to establish the data path, and a confirmation is sent back to the UE. Once established, the session allows for user data transmission between the UE and the network.
[0066] In an operative aspect, the plurality of SMFs (110) may configured to transmit multiple PDU session establishment requests pertaining to a designated network slice. For instance, in the context of a network slice P, the plurality of SMFs (110) (SMF A, SMF B, and SMF C) initiate the transmission of PDU session establishment requests concurrently. To enhance operational efficiency, it is required to analyze the frequency with which each participating SMF transmits these requests. By systematically evaluating the received PDU session establishment requests, the system can ascertain the SMF generating a higher volume of requests, thereby identifying it as an active SMF within the operational context. The identification process allows the system to adjust resource allocation dynamically, ensuring a more equitable distribution of network resources across the participating SMFs. By doing so, the system effectively contributes to the optimization of resource utilization, fostering a balanced operational environment and enhancing overall network performance.
[0067] The plurality of AMFs and the plurality of SMFs (110) are also connected to the NSACF server (120). The NSACF server (120) is configured to perform operations related to controlling the number of UEs and/or sessions registered per network slice. The NSACF server (120) is configured to continuously monitor and verify a count of registered UEs and/or PDU sessions associated with each network slice. This monitoring is performed to maintain an accurate and up-to-date representation of the real-time PDU load for each network slice, enabling effective load balancing across the 5G network infrastructure. It is a requirement that the NSACF server (120) possesses detailed insights into the operational metrics and performance indicators of each network slice. This data is critical to ensure optimal resource allocation and to facilitate dynamic adjustments in response to varying traffic conditions and user demands. The operational capabilities of the NSACF server (120) are fundamental to achieving a balanced distribution of network resources, thereby enhancing overall network performance and user experience within the network.
[0068] As shown in FIG. 1B, the provisioning system (200) is commutatively coupled to the NSACF server (120) and the database (130).
[0069] The NSACF server (120) is operatively coupled with the database (130). The database (also known as a context data store) (130) is configured to store a plurality of details (representing network slice load distribution details) corresponding to each network slice. In an example, the plurality of details includes a number of registered UEs through the plurality of AMFs, a number of connected UEs along with their corresponding PLMN IDs through the plurality of SMFs (110), a predefined list of SMFs having a unique number corresponding to each SMF of the plurality of SMFs (110), the number of active PDU sessions, the number of UEs connected to each of the network slice(s), a predefined threshold value corresponding to the UE registration for each network slice, a value corresponding to PDU session establishments for SMF of the plurality of SMFs (110), a value corresponding to PDU session establishments for each network slice, a list of identifiers having a unique number for each network slice, types of network slice(s), network slice selection assistance information (NSSAI), and a list of service providers. The NSSAI refers to the set of information elements that assist in selecting and identifying the appropriate network slice instance for a particular service or user equipment (UE). In an example, the plurality of details may include reference count data of the SMF (110) serving a particular network slice in the PLMN. In an aspect, the NSACF server (120) is configured to periodically provide the network slice information to the database (130). In an embodiment, the database may be indicative of including, but not limited to, a relational database, a distributed database, a cloud-based database, or the like.
[0070] Although FIG. 1A and FIG. 1B show exemplary components of the network architectures (100, 150), in other embodiments, the network architectures (100, 150) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1A and FIG. 1B. Additionally, or alternatively, one or more components of the network architectures (100, 150) may perform functions described as being performed by one or more other components of the network architectures (100, 150).
[0071] FIG. 2 illustrates an exemplary block diagram of the provisioning system (200), in accordance with embodiments of the present disclosure.
[0072] In an embodiment, the provisioning system (200) includes a receiving unit (202), a memory (204), a processing unit (210), a communication unit (212), and a display unit (214).
[0073] The receiving unit (202) is configured to receive a request from the user (102), via the user equipment (104), to provide real-time SMFs load distribution data for a user-defined network slice. In an aspect, the user-defined network slice may be defined as a particular network slice corresponding to which real-time SMFs load distribution data is required. In an aspect, the SMF load distribution data refers to the Protocol Data Unit (PDU) session load corresponding to each SMF of the plurality of SMFs. The PDU session load refers to the total volume and characteristics of data traffic associated with a session in a network. The PDU session load includes metrics such as data volume, throughput, session duration, traffic type, and Quality of Service (QoS) parameters, all of which help to assess and manage the efficiency and performance of the network.
[0074] In the network, each SMF is configured to manage a plurality of PDU sessions. Therefore, each SMF is configured to handle the PDU session load to an extent without compromising the QoS of the network. Balancing the load across the SMFs is required for ensuring network efficiency, stability, and performance. The present system is configured to monitor and track the number of SMFs that have initiated requests for Protocol Data Unit (PDU) establishment within the user defined network slice, as well as the cumulative number of such requests made to date.
[0075] By calculating the SMF load distribution data corresponding to each SMF or the user-defined network slice, the system is configured to provide details about various aspects such as how many SMFs are serving the user-defined network slice and what is the total load served by each SMF. By analyzing such details, a network operator may be able to redistribute the PDU session loads among the SMFs associated with the user-defined network slice in an even and suboptimal manner.
[0076] In an aspect, the user is the network operator or a service provider. For example, the receiving unit (202) is a user interfacing unit, facilitating interaction between the user and the provisioning system (200). In an aspect, the provisioning system (200) is configured to transfer the real-time SMFs load distribution data to the computer device periodically over a predefined time. In an aspect, the user, via the computer device, may define the network slices (user-defined network slice) along with their corresponding slice ID number and set a configuration in which whenever an update regarding these specific network slices occurs, the provisioning system (200) automatically transfers updated SMFs load distribution data for these specific network slices to the computing device. In some examples, the computing device may be implemented as any computing device for hosting a webpage or website accessible via the network, such as, but without limitation, a web server, application server, cloud server, or other host. For example, the computing device acts as a management server that is capable of performing data communication with respect to the device(s). The management server provides access to the hardware resources that are required for establishing network connectivity.
[0077] In an embodiment, the provisioning system (200) is an application programming interface (API) that is configured to generate real-time reference count data of all SMFs deployed in the network architecture (150) that serve the user-defined network slice in a PLMN.
[0078] For example, in an operational scenario, a network administrator (network operator) utilizes the receiving unit (202) (user interfacing unit) to submit the request that specifies a particular network slice, such as an IoT network slice designated for massive machine-type communications. In an example, the request may include a specific network slice identifier, a time interval, and one or more performance metrics. The specific network slice identifier helps the provisioning system (200) locate and retrieve the relevant data pertaining to that particular slice. The user may request data for a specific time period or interval (e.g., the last hour, day, or week), which aids in analyzing trends and performance over time. Users can also specify the particular metrics or indicators they are interested in, such as CPU utilization, memory usage, network traffic, latency, or throughput. These metrics provide insights into how resources within the network slice are being utilized. Additionally, users may specify how they want the data to be presented, such as in graphical charts, tables, or reports, which aids in understanding trends and anomalies more effectively. Furthermore, users can set thresholds for certain metrics, triggering alerts when performance metrics exceed or fall below-specified levels. Setting thresholds helps in proactive monitoring and management of network slice performance. Lastly, users may request comparative data, such as comparing the current performance with historical data or benchmarking against other network slices or predefined standards. Upon receipt of this request, the receiving unit engages with the processing unit to retrieve the current load distribution data (SMFs load distribution data) across the various SMFs associated with the specified network slice. In an example, the current load distribution data may include a total count of active PDU sessions managed by each SMF within the specified network slice, a percentage of available resources being utilized by each SMF, indicating the operational capacity, and an average response time for session management requests handled by the SMFs, reflecting the efficiency of the network slice. By providing this real-time load distribution data, the receiving unit enables the user to make informed decisions regarding resource allocation, performance optimization, and potential scaling of network resources to ensure efficient operation of the user-defined network slice.
[0079] The processing unit (210) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, the processing unit (210) may be configured to fetch and execute computer-readable instructions stored in the memory (204) of the provisioning system (200). 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 comprise 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.
[0080] In an embodiment, the provisioning system (200) may include an interface(s) (206). The interface(s) (206) may comprise a variety of interfaces, for example, interfaces for data input and output devices (I/O), storage devices, and the like. The interface(s) (206) may facilitate communication through the provisioning system (200). The interface(s) (206) may also provide a communication pathway for one or more components of the provisioning system (200). Examples of such components include, but are not limited to, a processing engine and a database.
[0081] In an embodiment, the processing unit (210) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing unit (210). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing unit (210) may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing unit (210) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing unit (210). In such examples, the system may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system and the processing resource. In other examples, the processing unit (210) may be implemented by electronic circuitry.
[0082] In an embodiment, the memory may store data that may be generated as a result of functionalities implemented by any of the components of the provisioning system (200). In an exemplary embodiment, the processing unit (210) may include one or more units having functions that may include, but are not limited to, testing, storage, and peripheral functions, such as a wireless communication unit for remote operation, and the like.
[0083] The processing unit (210) is configured to cooperate with the receiving unit (202) and receive the request. Upon receiving the request, the processing unit (210) establishes a connection with the database (130) coupled with the at least one NSACF server (120). For example, when the network operator (user) submits the request via the receiving unit (202) for real-time load distribution data regarding a user-defined network slice, the processing unit (210) may perform the following steps:
• Collaboration with the receiving unit (202): The processing unit (210) actively collaborates with the receiving unit (202) to confirm the details of the request, ensuring that all necessary parameters (such as the target network slice) are accurately specified.
• Connection establishment: Upon verification, the processing unit (210) establishes a secure connection with the database (130) that is associated or integrated with the NSACF server (120). In an example, the processing unit (210) may utilize protocols such as RESTful APIs or RPC (remote procedure call) to facilitate efficient data retrieval.
[0084] The processing unit (210) is configured to retrieve network slice load distribution details from the database (130). This retrieval process involves several systematic steps to ensure accurate and timely access to relevant data. First, upon receiving the request, the processing unit (210) constructs a specific query tailored to retrieve load distribution details for the user-defined network slice. For example, the query may include parameters such as, a network slice identifier (to specify which slice’s load details are required) and a timeframe (to define the period for which the load distribution data is being requested (e.g., real-time, last hour, last 24 hours)). The processing unit (210) executes the formulated query against the database (130). This involves sending the request to the database and waiting for a response containing the requested data.
[0085] The processing unit (210) is configured to process the retrieved network slice load distribution details to generate a list. In an example, the network slice load distribution details may include the total number of active sessions associated with each SMF within the designated network slice. For example, SMF A is managing X active sessions, SMF B is handling Y active sessions, and SMF C is handling Z active sessions. In another example, the network slice load distribution details may include the percentage of utilized resources for each SMF, reflecting the operational load. For example, the load distribution data may reveal that SMF A is utilizing 75% of its allocated resources, whereas SMF B is operating at 60% utilization. The SMF C is utilizing 95% of its allocated resources. In an example, the network slice load distribution details may include average response times for session establishment and management requests processed by each SMF. An example may indicate that the average response time for SMF A is 120 milliseconds, while SMF B averages 80 milliseconds. In an example, the network slice load distribution details may include metrics related to the success rate of session establishment requests, illustrating the reliability of each SMF. For example, SMF A may exhibit a success rate of 98%, while SMF B achieves a success rate of 95%. In another example, the network slice load distribution details may include the volume of data traffic handled by each SMF, indicating the overall network slice load. For instance, SMF A might process 500 GB of data traffic daily, whereas SMF B manages 800 GB. In an example, the network slice load distribution details may include peak usage times for each SMF, providing insights into when network slices experience the highest demand. For example, the data could show that SMF A experiences peak loads between 6 PM and 8 PM. For example, the network slice load distribution details may include geographic information regarding where sessions are being established or terminated, helping to identify regional load patterns. For example, SMF A might serve a majority of its sessions from urban areas, SMF B serves rural regions, and SMF C is handling sub urban areas. The list includes SMFs load distribution data of the plurality of SMFs over the user-defined network slice. In an example, the list includes a number of PDU session establishment requests sent by each SMF towards the specific network slice. In another example, the list further includes a current count representing a number of active establishment requests made by each SMFs. In an aspect, the list further includes an old count representing a number of previously sent establishment requests made by each SMF. In a structural aspect, the processing unit includes a parser. The parser is configured to retrieve the network slice load distribution details from the database (130). Upon successful retrieval, the processing unit processes the incoming data to ensure it is formatted correctly and meets the user’s request. This may involve aggregating results, calculating averages, or converting data formats. After retrieving the necessary data, the processing unit (210) processes the information. In an example, the processing may involve several operations, including aggregating results, calculating averages, or converting data formats. The processing unit (210) formulates a response (list) to be sent to the display unit, enabling the user to view the requested load distribution data.
[0086] The communication unit (212) is configured to receive the generated request from the computing device (104). The communication unit (212) is configured to send the generated list to the user equipment (104) and the NSACF server (120) over the network (106). In an example, the network is a wireless network or a wired network. The NSACF server is configured to analyze the received list to perform one or more operations, including determining resource availability and/or optimizing at least one provisioning process based on the dynamic load distribution of SMFs. By analyzing the received list, the NSACF server may assesses the current condition of resources throughout the network. In an aspect, the assessing the current condition may include reviewing the status of servers, storage, network bandwidth, and other assets to identify which resources may be allocated. The NSACF server may employ dynamic distribution of loads based on the current resource availability. The NSACF server will monitor how much load each resource is handling and redistribute tasks to ensure no single resource is overwhelmed while others remain underutilized. The NSACF server may optimize the at least one provisioning process. In an example, the at least one provisioning process may include virtual machine provisioning, network bandwidth allocation, storage provisioning and load balancer configuration. The virtual machine provisioning involves the allocation of virtual machines (VMs) within a cloud infrastructure. For example, when a SMF requires additional computational resources, the system dynamically provisions one or more VMs with predefined configurations such as CPU, memory, and storage capacity. The network bandwidth allocation describes the dynamic assignment of bandwidth resources to various SMFs based on their current load requirements. For instance, in a scenario where a SMF P experiences a surge in user activity, the system can allocate additional bandwidth to ensure that data packets are transmitted smoothly, thereby minimizing buffering and enhancing user experience. Conversely, during periods of low activity, bandwidth can be reallocated to other services needing more resources. The storage provisioning refers to an allocation of storage resources to accommodate the data needs of applications. For example, when an application (SMF) experiences increased data generation, such as a social media platform collecting user-generated content, the system can provision additional storage resources automatically. The load balancer configuration involves the configuration of load balancers to distribute incoming network traffic evenly across multiple SMFs.
[0087] By employing the optimization of the provisioning process, the NSACF may automate the allocation of resources for applications or services, ensuring that they have the necessary capacity to function effectively. The NSACF server can adjust provisioning strategies using real-time data to better meet current demands, thus enhancing efficiency. In an aspect, the processing unit (210) is configured to generate an update signal to notify the computing device with the updated SMFs load distribution data of the network slice.
[0088] In an embodiment, the display unit (214) is configured to display the generated list to the user. The display unit (214) is designed to present the information (list) in a user-friendly format, allowing easy interpretation of the network slice load distribution data. This may include graphical representations, such as charts or tables. The display unit (214) is capable of dynamically updating the information in real-time, reflecting the most current load distribution metrics as retrieved from the processing unit.
[0089] In an example, the provisioning system (200) employs an automated refresh mechanism that updates the displayed data every few seconds or upon receiving new data from the processing unit (210). The display unit (214) may also include interactive features, allowing the network operator to filter, sort, or select specific network slices for detailed analysis. The display can incorporate visual indicators, such as color-coding or alerts, to highlight critical load conditions or performance thresholds that require immediate attention.
[0090] In an aspect, the NSACF server (120) is configured to analyze the throughput of each network slice. In another aspect, the NSACF server (120) is configured to analyze the load of each network slice. The NSACF server (120) is further configured to define a maximum number of PDU session establishment requests to be served by each SMF (SMF A, SMF B, and SMF C) over the user-defined network slice based on the generated list. To define the maximum number of PDU session establishment requests, the NSACF server (120) analyzes the generated list of current PDU session requests, considering Quality of Service (QoS) requirements. For example, SMF A may be dedicated to the eMBB slice, optimized for high-capacity requests, such as video streaming and virtual reality applications. The NSACF assesses that SMF A can effectively manage up to P concurrent PDU session establishment requests, then the NSACF server (120) may change a current PDU session establishment requests of the SMF A to the Q values.
[0091] In an aspect, the user is configured to analyze the received SMFs load distribution data in real-time. Based on the analysis, if it is found that the specific network slice is overloaded, the user is configured to generate a diversion request to divert the new PDU establishment request to another available network slice (s). In an aspect, the provisioning system (200) is configured to receive and forward the diversion request to the NSACF server (120) such that the network resources can be utilized fully. In an example, based on the diversion request, the NSACF server (120) is configured to generate a plurality of slice usage metrics.
[0092] In an example, the provisioning system (200) is configured to communicate the generated list (a plurality of network slice usage metrics) to the NSACF server (120) or the computing device for further analysis. Based on the network slice usage metrics, the network operator is configured to employ network reconfiguration and provide a portion of their network according to the requirements of their customers (UEs). Due to the reconfiguration and network slicing, the network operator is able to save many of the network resources that are not required by the users at that particular time. The reconfiguration and network slicing based on the generated network slice usage metrics resulted in reduced latency, high bandwidth, seamless mobility, and better QoS.
[0093] In an aspect, the UE is configured to register itself for a particular network slice based on its specific requirements or preferences. In one aspect, the provisioning system (200) is configured to ensure that the UE receives the customized network services and performance characteristics associated with that particular network slice. For example, a UE with high-bandwidth needs for video streaming may register with a network slice optimized for high-data rates, while a UE with low-data requirements may select a network slice configured for low-resource usage. In an example, a network slice 1 is configured to handle 5G enhanced mobile broadband. Another network slice 2 is configured to handle ultra-reliable low-latency communications (URLLC). A network slice 3 is configured to handle massive IoT, and a network slice 4 is configured to handle V2X services. In an aspect, the provisioning system (200) is configured to ensure that each network slice is efficiently utilized based on the generated network slice usage metrics. For example, if the slice 3 is serving maximum capacity (having a maximum number of active PDU sessions) and a new request for establishing a massive IoT request has come, then by monitoring the dynamic SMFs load distribution over at least one network slice, via the provisioning system (200), the network operator is able to divert the new establishment request towards the network slice having a capacity for handling massive IoT requests.
[0094] In an aspect, the provisioning system (200) is configured to enhance the management of SMFs requests and contributes to a more balanced allocation of resources across the network slices.
[0095] FIG. 3 illustrates an exemplary flow diagram illustrating a method (300) for monitoring dynamic SMFs load distribution over the at least one network slice, in accordance with an embodiment of the present disclosure.
[0096] Step (302) includes receiving the request by the receiving unit (202) from the to provide real-time SMFs load distribution data for the user-defined network slice. In an aspect, the receiving unit (202) is configured to receive the request from the user via the user equipment. In an example, the request may include a specific network slice identifier, a time interval, and one or more performance metrics.
[0097] Step (304) includes establishing, by the processing unit (210), a connection with the database (130) coupled with the at least one network slice admission control function (NSACF) server (120). Upon receiving the request, the processing unit (210) establishes a secure connection with the database associated or integrated with the NSACF server (120). In an example, the processing unit (210) may utilize protocols such as RESTful APIs (Application Programming Interfaces) or RPC (Remote Procedure Call) to facilitate efficient data retrieval. In an aspect, the processing unit (210) actively collaborates with the receiving unit to confirm the details of the request, ensuring that all necessary parameters (such as the target network slice) are accurately specified.
[0098] Step (306) includes retrieving, by the processing unit (210), network slice load distribution details from the database (130). This retrieval process involves several systematic steps to ensure accurate and timely access to relevant data. First, upon receiving the request, the processing unit (210) constructs a specific query tailored to retrieve load distribution details for the user-defined network slice. For example, the query may include parameters such as, a network slice identifier (to specify which slice’s load details are required) and a timeframe (to define the period for which the load distribution data is being requested (e.g., real-time, last hour, last 24 hours)). The processing unit (210) executes the formulated query against the database. This involves sending the request to the database and waiting for a response containing the requested data.
[0099] Step (308) includes processing, by the processing unit (210), the retrieved network slice load distribution details to generate a list having SMFs load distribution data of a plurality of SMFs (110) for the user-defined network slice. In an example, the list includes a number of Protocol Data Unit (PDU) session establishment requests received on the user-defined network slice sent by each SMF of the plurality of SMFs along with a request count, timestamp corresponding to each PDU session establishment request, and session identifiers corresponding to active sessions on the user-defined network slice. In an aspect, the list further includes an old count representing a number of previously sent establishment requests made by each SMF. Upon successful retrieval, the processing unit processes the incoming data to ensure it is formatted correctly and meets the user’s request. This may involve aggregating results, calculating averages, or converting data formats. After retrieving the necessary data, the processing unit processes the information. In an example, the processing may involve several operations, including aggregating results, calculating averages, or converting data formats.
[00100] In an aspect, the method (300) further includes a step of sending, by the communication unit (212), the generated list to the NSACF server. The NSACF server is configured to analyze the received list to perform one or more operations, including determining resource availability and/or optimizing at least one provisioning process based on the dynamic load distribution of SMFs. In an example, based on the received list, the NSACF server (120) is configured to generate a plurality of slice usage metrics. Based on the network slice usage metrics, the network operator is configured to employ network reconfiguration and provide a portion of their network according to the requirements of their customers (UEs). The method further includes a step of defining, by the NSACF server (120), a maximum number of PDU session establishment requests to be served by each SMF over the user-defined network slice by analyzing the generated list.
[00101] In an aspect, the method (300) further includes a step of displaying the generated list on the display unit (214) to the user (network operator). The display unit is designed to present the information (list) in a user-friendly format, allowing easy interpretation of the network slice load distribution data. This may include graphical representations, such as charts or tables.
[00102] FIG. 4 illustrates an example computer system (400) in which or with which the embodiments of the present disclosure may be implemented.
[00103] As shown in FIG. 4, the computer system (400) may include an external storage device (410), a bus (420), a main memory (430), a read-only memory (440), a mass storage device (450), a communication port (460), and a processor (470). A person skilled in the art will appreciate that the computer system (400) may include more than one processor (470) and communication ports (460). Processor (470) may include various modules associated with embodiments of the present disclosure.
[00104] In an embodiment, the communication port (460) may be any of an RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port (460) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (400) connects.
[00105] In an embodiment, the memory (430) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. Read-only memory (440) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input/Output System (BIOS) instructions for the processor (470).
[00106] In an embodiment, the mass storage device (450) may be any current or future mass storage solution, which may be 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).
[00107] In an embodiment, the bus (420) communicatively couples the processor(s) (470) with the other memory, storage, and communication blocks. The bus (420) may be, 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 (470) to the computer system (400).
[00108] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus (420) to support direct operator interaction with the computer system (400). Other operator and administrative interfaces may be provided through network connections connected through the communication port (460). The components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system (400) limit the scope of the present disclosure.
[00109] The present disclosure further discloses a user equipment (UE) communicatively coupled with a network or the provisioning system (200). The coupling comprises steps of receiving a connection request, sending an acknowledgment of the connection request to the network, and transmitting a plurality of signals in response to the connection request, wherein a provisioning system in the network is configured to monitor dynamic session management functions (SMFs) load distribution over at least one network slice in real time. The provisioning system includes a receiving unit and a processing unit. The receiving unit is configured to receive a request from a user for providing real-time SMFs load distribution data for a user-defined network slice. The processing unit is configured to cooperate with the receiving unit to receive the request and is configured to establish a connection with a database coupled with at least one network slice admission control function (NSACF) server. The processing unit is configured to retrieve network slice load distribution details from the database. The processing unit is configured to process the retrieved network slice load distribution details to generate a list having SMFs load distribution data of a plurality of SMFs for the user-defined network slice.
[00110] In an embodiment, the SMF triggers a “Number of PDU Sessions per network slice availability check and update procedure” for the network slices that are subject to Network Slice Admission Control (NSAC) at the beginning of a PDU Session Establishment procedure and as a last step of successful PDU Session Release procedure. The SMF sends a message (Nnsacf_NumberOfPDUsPerSliceAvailabilityCheckAndUpdate_Request message) to the NSACF. The SMF includes in the message the Network Slice Selection Assistance Information (S-NSSAI) for which the number of PDU Sessions per network slice update is required and the update flag. The update flag 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.
[00111] The NSACF 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 SMF in the update flag parameter.
• If the update flag parameter from the SMF indicates an increase in the current number of PDU Sessions per network slice and the maximum number of PDU Sessions established on the network slice has not been reached yet, the NSACF increases the number of PDU Sessions for that network slice. If the maximum number of PDU Sessions established on the network slice has already been reached, then the NSACF returns a result parameter indicating that the maximum number of PDU Sessions per network slice has been reached.
• If the update flag parameter from the SMF indicates a decrease in the current number of PDU Sessions per network slice, the NSACF decreases the number of PDU Sessions for that network slice.
[00112] The NSACF acknowledges the update to the SMF with a response (Nnsacf_NumberOfPDUsPerSliceAvailabilityCheckAndUpdate_Response message). If the NSACF returned a maximum number of PDU Sessions per network slice reached result, the SMF rejects the PDU Session establishment request with a maximum number of PDU Sessions per network slice reached reject cause. In case of a PDU Session Establishment failure, the SMF triggers another request to the NSACF with the update flag parameter equal to decrease in order to re-adjust the PDU Session counter in the NSACF.
[00113] In another embodiment, the NSACF server proactively collects the data from a database (may receive data from various network functions) and analyses the collected data to know how PDU sessions load is distributed among the SMFs for a particular network slice. The NSACF server monitors the SMF load distribution across the network slices for efficient resource allocation and optimization. Based on utilizing the real-time reference count data for all SMFs serving the specific network slice, the present system and the method dynamically and proactively allocate network resources to prevent any single SMF from becoming overloaded. This approach optimizes network performance and resource utilization, ensuring smooth network operation even during high demand.
[00114] The present disclosure provides a technical advancement related to the efficient management of network resources through a sophisticated provisioning system for monitoring protocol data unit (PDU) session loads across individual network slices. This advancement addresses the challenges in balancing network traffic by enabling real-time tracking of PDU session requests and the distribution of load among various service management functions (SMFs) for specific network slices. By providing operators with comprehensive insights into the utilization of SMFs and the activity levels on defined network slices, the system enhances operational control and flexibility. This ultimately ensures optimal resource allocation and improved network performance, thereby supporting dynamic network environments and user demands more effectively.
[00115] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.
TECHNICAL ADVANTAGES
[00116] The present disclosure described herein above has several technical advantages including, but not limited to, the realization of a provisioning system for monitoring dynamic session management functions (SMFs) load distribution over at least one network slice that:
• monitors the distribution of protocol data unit (PDU) session load for a user-defined network slice;
• provides a list of the plurality of SMFs from which PDU session establishment requests have been made for that slice monitors how many SMFs have requested PDU establishment on a user-defined network slice;
• tracks the number of requests for PDU establishment on a network slice; and
• offers enhanced control and flexibility to a network operator in managing network resources.
,CLAIMS:CLAIMS
We Claim:
1. A provisioning system (200) for monitoring dynamic session management functions (SMFs) load distribution over at least one network slice, the provisioning system (200) comprising:
a receiving unit (202) configured to receive a request from a user equipment for providing real-time SMFs load distribution data for a user-defined network slice; and
a processing unit (210) communicatively coupled with the receiving unit to receive the request and is configured to:
establish a connection with a database (130) coupled with at least one network slice admission control function (NSACF) server (120);
retrieve network slice load distribution details from the database (130); and
process the retrieved network slice load distribution details to generate a list having SMFs load distribution data of a plurality of SMFs (110) for the user-defined network slice.
2. The provisioning system (200) as claimed in claim 1, includes a communication unit (212) configured to send the generated list to the NSACF server, wherein the NSACF server is configured to analyze the received list to perform one or more operations including determining resource availability and/or optimizing at least one provisioning process based on the dynamic SMFs load distribution.
3. The provisioning system (200) as claimed in claim 1, wherein the generated list includes a number of Protocol Data Unit (PDU) session establishment requests from each SMF along with a request count, a timestamp corresponding to each PDU session establishment request, and session identifiers corresponding to active sessions on the user-defined network slice.
4. The provisioning system (200) as claimed in claim 1, wherein the provisioning system (200) includes a display unit (214) to display the generated list to a user.
5. The provisioning system (200) as claimed in claim 1, wherein the NSACF server (120) is configured to define a maximum number of PDU session establishment requests to be served by each SMF over the user-defined network slice by analyzing the generated list.
6. A method (300) for monitoring dynamic session management functions (SMFs) load distribution over at least one network slice in real time, the method comprising:
receiving (302), by a receiving unit (202), a request from a user equipment for providing real-time SMFs load distribution data for a user-defined network slice;
establishing (304), by a processing unit (210), a connection with a database (130) coupled with at least one network slice admission control function (NSACF) server (120);
retrieving (306), by the processing unit (210), network slice load distribution details from the database (130); and
processing (308), by the processing unit (210), the retrieved network slice load distribution details to generate a list having SMFs load distribution data of a plurality of SMFs (110) for the user-defined network slice.
7. The method (300) as claimed in claim 6, further comprising sending, by a communication unit (212), the generated list to the NSACF server, wherein the NSACF server is configured to analyze the received list to perform one or more operations including determining resource availability and/or optimizing at least one provisioning process based on the dynamic SMFs load distribution.
8. The method (300) as claimed in claim 6, wherein the generated list includes a number of Protocol Data Unit (PDU) session establishment requests received from each SMF along with a request count, a timestamp corresponding to each PDU session establishment request, and session identifiers corresponding to active sessions on the user-defined network slice.
9. The method (300) as claimed in claim 6, further comprising displaying, on a display unit (214), the generated list to a user.
10. The method (300) as claimed in claim 6, further comprising defining, by the NSACF server (120), a maximum number of PDU session establishment requests to be served by each SMF over the user-defined network slice by analyzing the generated list.
11. A user equipment (UE) (104) communicatively coupled with a network (106), the coupling comprises steps of:
receiving a connection request;
sending an acknowledgment of the connection request to the network (106); and
transmitting a plurality of signals in response to the connection request, wherein the UE is configured to communicate with a provisioning system (200) to obtain dynamic session management functions (SMFs) load distribution, wherein the provisioning system (200) in the network (106) is configured to monitor dynamic SMFs load distribution over at least one user defined network slice in real time as claimed in claim 1.