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 UPDATING NETWORK SLICE PARAMETERS DYNAMICALLY 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 (herein after referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.
TECHNICAL FIELD
[0002] The present disclosure generally relates to the field of wireless communication systems. More particularly, the present disclosure relates to a provisioning system for updating network slice parameters dynamically.
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 services requirements.
[0005] The expression “UE registration” used herein in the specification refers to a process where a user equipment (UE), such as a mobile phone or other wireless device, connects and registers with a network to obtain services and establish communication capabilities.
[0006] The expression “PDU session establishment" used herein in the specification refers to a process of setting up a Protocol Data Unit (PDU) session in the network. The PDU session is a logical association between the user equipment (UE) and a data network. It enables the transfer of user data over the network and can support various types of services, such as internet browsing, video streaming, and Internet of Things (IoT) applications.
[0007] The expression “Network slice thresholds” used herein in the specification refer to predefined limits or criteria that determine the behavior or allocation of resources within the network slice. The network slice thresholds help to manage and maintain the quality of service (QoS), performance, and resource utilization for the applications or services running within the network slice.
[0008] The expression “3rd Generation Partnership Project (3GPP) access type” used herein in the specification refers to the technology or generation of mobile network that a User Equipment (UE) or device uses to connect to the network. The 3GPP access type includes 2G (GSM), 3G (UMTS/HSPA), 4G (LTE), and 5G (5G NR).
[0009] The expression “Non-3GPP access type" used herein in the specification refers to access technologies or networks that are not based on the standards developed by the 3GPP. The Non-3GPP access type includes Wi-Fi, Bluetooth, satellite networks, fixed-line broadband networks, local area networks (LANs).
[0010] The expression “Network Slice Admission Control Function (NSACF)” used herein in the specification refers to a network element responsible for managing the admission of network slices into the network based on various criteria and policies.
[0011] These definitions are in addition to those expressed in the art.
BACKGROUND
[0012] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0013] In fifth generation (5G) communication 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. Access and Mobility management function (AMF) receives these requests, handles all access and mobility management-related tasks, and forwards session management requirements to session management function (SMF). The AMF determines which SMF to be selected for processing 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).
[0014] Data is communicated between the UE and the data network through various components along its path. In 5G, 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 slice is a logical concept that splits the resources along the data path into multiple sets that are 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 the use of network resources and service flexibility.
[0015] In 5G architecture, the network slice admission control function (NSACF) server is a function that enables multiple independent network slices to coexist and interoperate on the same physical infrastructure. NSACF server is used to monitor the 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 obtain various information in real-time corresponding to the network slicing and update threshold value of each network slice to perform efficient load balancing across the 5G network. In such a scenario, network efficiency, stability, and performance of the communication system are drastically reduced.
[0016] Hence, there is a need for a system that is configured to update the network slice parameters dynamically for effective and efficient allocation of network resources.
OBJECTS
[0017] Some of the objects of the present disclosure, which at least one embodiment herein satisfies, are as follows:
[0018] An object of the present disclosure is to provide a provisioning system that updates at least one threshold value of a network slice.
[0019] Another object of the present disclosure is to provide a provisioning system that updates the threshold values of the network slice for both user equipment (UE) registration and protocol data unit (PDU) session establishment.
[0020] Yet another object of the present disclosure is to provide a provisioning system that sets the threshold values of the network slices based upon access types.
[0021] Still another object of the present disclosure is to provide a provisioning system that offers enhanced control and flexibility to a network operator in managing network resources.
[0022] Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.
SUMMARY
[0023] In an exemplary embodiment, a provisioning system for updating at least one parameter of a network slice is described. The provisioning system comprising a receiving unit configured to receive a request for updating the at least one parameter of the network slice from a computing device. On receiving the request, a connection unit is configured to establish a connection with at least one network slice admission control function (NSACF) server and a database coupled with the NSACF server. A processing unit is configured to cooperate with the receiving unit to receive the request. The processing unit is further configured to process the received request to generate at least one updation signal. An updating unit is configured to cooperate with the processing unit to receive the at least one updation signal. The updating unit is further configured to update the at least one parameter of the network slice in the database based on the at least one updation signal and generate a notification comprising the at least one updated parameter of the corresponding network slice. A communication unit is configured to send the generated notification to the NSACF server.
[0024] In some embodiments, the communication unit is configured to send the at least one updated parameter of the corresponding network slice to the database. Upon receiving the at least one updated parameter from the provisioning system, the database is configured to update context data of the corresponding network slice based on the received the at least one updated parameter.
[0025] In some embodiments, the at least one parameter includes a first threshold value representing a total number of user equipments to be connected with the network slice, and a second threshold value representing a total number of PDU sessions to be established with the network slice.
[0026] In some embodiments, updation of the at least one parameter is based on one or more access types. The one or more access types include a third-generation partnership project (3GPP) access type and a non-3GPP access type.
[0027] In some embodiments, the processing unit is configured to update the at least one parameter of the network slices based upon a plurality of use cases including at least one of an ultra-high bandwidth use case, a very low-latency use case, an ultra-reliable low-latency use case, a high-bandwidth use case, and a massive IoT use case.
[0028] In some embodiments, the NSACF server is configured to update one or more network slice metrics on receiving the notification from the provisioning system.
[0029] In another exemplary embodiment, a method for updating at least one parameter of a network slice is described. The method includes receiving, by a receiving unit, a request for updating the at least one parameter of the network slice from a computing device. On receiving the request, the method includes establishing, by a connection unit, a connection with at least one network slice admission control function (NSACF) server and a database associated with the at least one NSACF server. The method includes processing, by a processing unit, the received request to generate at least one updation signal. The method includes updating, by an updating unit, the at least one parameter of the network slice in the database. The method includes generating, by the updating unit, a notification comprising the at least one updated parameter of the corresponding network slice. The method includes sending, by a communication unit, the generated notification to the NSACF server.
[0030] In some embodiments, the method further comprising sending, by the communication unit, the at least one updated parameter of the corresponding network slice to the database. Upon receiving the at least one updated parameter from the provisioning system, the database is configured to update context data of the corresponding network slice based on the received the at least one updated parameter.
[0031] In some embodiments, the at least one parameter includes a first threshold value representing a total number of user equipments to be connected with the network slice, and a second threshold value representing a total number of PDU sessions to be established with the network slice.
[0032] In some embodiments, updation of the at least one parameter is based on one or more access types. The one or more access type includes a third-generation partnership project (3GPP) access type and a non-3GPP access type.
[0033] In some embodiments, the method further includes a step of updating at least one parameter of the network slice based upon one or more access type, wherein the one or more access type includes at least one of an ultra-high bandwidth use case, a very low-latency use case, an ultra-reliable low-latency use case, a high-bandwidth use case, and a massive IoT use case.
[0034] In some embodiments, the NSACF server is configured to update one or more network slice metrics on receiving the notification from the communication unit.
[0035] In some embodiments, the present disclosure discloses a user equipment communicatively coupled with a provisioning system. The coupling comprises steps of receiving, by the provisioning system, a connection request and sending, by the provisioning system, an acknowledgment of the connection request to the UE. The coupling further comprises transmitting a plurality of signals in response to the connection request. The provisioning system is configured to update at least one parameter of a network slice.
BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING
[0036] 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.
[0037] FIG. 1A illustrates an exemplary network architecture for implementing a provisioning system for updating at least one parameter of a network slice dynamically, in accordance with an embodiment of the present disclosure.
[0038] FIG. 1B illustrates an exemplary block diagram of the provisioning system for updating the at least one parameter of the network slice dynamically, in accordance with an embodiment of the present disclosure.
[0039] FIG. 1C illustrates another exemplary network architecture for implementing a Network Slice Admission Control Function (NSACF) cluster for updating the at least one parameter of the network slice dynamically, in accordance with an embodiment of the present disclosure.
[0040] FIG. 1D illustrates an exemplary flow diagram for updating the at least one parameter of the network slice dynamically, in accordance with an embodiment of the present disclosure.
[0041] FIG. 2 illustrates an exemplary flow diagram of a method for updating network slice parameters dynamically, in accordance with an embodiment of the present disclosure.
[0042] FIG. 3 illustrates an exemplary computer system in which or with which embodiments of the present disclosure may be implemented.
[0043] The foregoing shall be more apparent from the following more detailed description of the disclosure.
LIST OF REFERENCE NUMERALS
100A Network Architecture
102 User
104 User Equipment (UE)
106 Network
108 Provisioning System
110 Base Station
112 Network Slice Admission Control Function (NSACF) Server
114 Database
100B Block Diagram of System
122 Processor
124 Memory
126 Interface(s)
128 Receiving Unit
130 Connection Unit
132 Processing Unit
134 Updating Unit
136 Communication Unit
138 Database of System
100C Network Architecture
116 NSACF Cluster
100D Flow Diagram
200 Method Flow Diagram
300 Computing System
310 External Storage Device
320 Bus
330 Main Memory
340 Read Only Memory
350 Mass Storage Device
360 Communication Port
370 Processor
DETAILED DESCRIPTION
[0044] 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.
[0045] 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.
[0046] 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.
[0047] 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.
[0048] 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.
[0049] 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.
[0050] 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.
[0051] 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.
[0052] 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.
[0053] 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.
[0054] 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.
[0055] 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.
[0056] 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. 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. 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. Load balancing across the network slices allows the network operators (service providers) to optimize the performance of their networks by allocating traffic to the most appropriate network slice based on factors such as traffic type, network congestion, and user priority. Overloaded network slices can indeed cause issues with UE (User Equipment) admissions and Protocol Data Unit (PDU) session creations. The present disclosure updates network slice parameters dynamically based upon network load across the network slices for efficient resource allocation and optimization.
[0057] A preferred embodiment of a provisioning system for updating network slice parameters dynamically of the present disclosure is now being described in detail with reference to FIG. 1A – FIG. 3.
[0058] FIG. 1A illustrates an exemplary network architecture (100A) for implementing a provisioning system (108) for updating at least one parameter of a network slice, in accordance with an embodiment of the present disclosure.
[0059] The exemplary network architecture (100A) includes a user equipment (UE) (104), a base station (110), a core network (106), and the provisioning system (108). In an example, the core network (106) includes a number of components, such as a plurality of access and mobility management functions (AMFs), a plurality of session management functions (SMFs), a user plane function (UPF), a network slice admission control function (NSACF) server (112), and so on.
[0060] As illustrated in FIG. 1A, the network architecture (100A) comprises one or more computing devices (104) that may be connected to the provisioning system (108) through the core network (106). A person of ordinary skill in the art will understand that the one or more computing devices (104) may be collectively referred as computing devices (104) and individually referred as a computing device (104). One or more users (102) may provide one or more requests to the provisioning system (108). A person of ordinary skill in the art will understand that the one or more users (102) may be collectively referred as users (102) and individually referred as a user (102). Further, the computing devices (104) may also be referred as a user equipment (UE) (104) or as UEs (104) throughout the disclosure.
[0061] In an embodiment, the computing device (104) may include, but not be limited to, a mobile, a laptop, etc. Further, the computing device (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, audio aid, microphone, or keyboard. Furthermore, the computing device (104) may include a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, and a mainframe computer. Additionally, input devices for receiving input from the user (102) such as a touchpad, touch-enabled screen, electronic pen, and the like may be used.
[0062] In an embodiment, the core network (106) may include at least one of a Fifth Generation (5G) network, Sixth Generation (6G) network, or the like. The core network (106) may enable the user equipment (104) to communicate with other devices in the network architecture (100A) and/or with the system (108). The core network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the core 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.
[0063] In an embodiment, the core network (106) may include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth. The network (106) may also include, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.
[0064] In an embodiment, the base station (110) may be a network infrastructure that provides wireless access to one or more terminals associated therewith. The base station (110) may have coverage defined to be a predetermined geographic area based on the distance over which a signal may be transmitted. The base station (110) may include, but not be limited to, wireless access point, evolved NodeB (eNodeB), 5G node or next generation NodeB (gNB), wireless point, transmission/reception point (TRP), and the like. In an embodiment, the base station (110) may include one or more operational units that enable telecommunication between two or more UEs (104).
[0065] In an embodiment, the one or more operational units may include, but not be limited to, transceivers, baseband unit (BBU), (remote radio unit - RRU), antennae, mobile switching centres, radio network control units, one or more processors associated thereto. In an embodiment, the user equipment (104) is communicatively coupled with the provisioning system (108). The provisioning system (108) may receive a connection request from the UE (104). The provisioning system (108) may send an acknowledgment of the connection request to the UE (104). The UE (104) may transmit a plurality of signals in response to the connection request. The provisioning system (108) may be configured to update at least one parameter of a network slice.
[0066] In an aspect, the core network (106) 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 a connection with a data network via the core network (106). For example, the UE (104) may set up a connection to the base station (110). The UE (104) performs the random-access procedure to initiate communication with the base station (110) and sends a radio resource control (RRC) connection request message to the base station (110). After receiving the RRC connection request message, the base station (110) performs network attached storage (NAS) level authentication and initiates ciphering for the NAS messages with the core network (106). The core network (106) completes the security procedure with the base station (110) and handles the RRC reconfiguration from the base station (110). The UE (104) responds with a channel state information (CSI) report as requested by the base station (110), and the connection is established.
[0067] For example, without limitation, the UE (104) may refer to a mobile phone, a personal digital assistant (PDA), a desktop computer, a Global Positioning System (GPS) device, an automotive navigation system, a wearable object, a smartwatch, a wearable sensor, a cellular telephone, a tablet, a netbook, a wireless terminal, a laptop computer, a wearable computer device, Internet of Things (IoT) device, or any other device. In an example, the network architecture (100A) may include any number of UEs being used by any number of users. The example of a single UE is merely provided for illustrative purposes. The UE (104) may be 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 (104) may also communicate with networks over a wired connection.
[0068] The UE (104) and the base station (110) are connected to the core network (106). The plurality of AMFs is configured to perform connection and mobility management in the 5G RAN. In an example, the AMF is configured to perform operations related to registration procedure management between the UE (104) and the SMF. The AMF is configured to determine which SMF is best suited to handle the requirements of the UE (104).
[0069] The plurality of SMFs is configured to perform operations related to session management, such as, but not limited to, session establishment, session release, IP address allocation, policy and quality of service (QoS) enforcement, etc.
[0070] The plurality of AMFs and the plurality of SMFs are also connected to the NSACF server (112). The NSACF server (112) is configured to perform operations related to controlling the number of UEs and/or sessions registered per network slice. During operation, the NSACF server (112) is configured to check the count of registered UEs and/or established PDU sessions.
[0071] As shown in FIG. 1A, the provisioning system (108) is commutatively coupled to the NSACF server (112) and a database (114).
[0072] The NSACF server (112) is operatively coupled with the database (114). The database (also known as context data store) (114) is configured to store network slice data. In an example, the network slice data (also known as context data) includes a number of registered UEs through the plurality of AMFs, a number of connected UEs through the plurality of SMFs, the number of active PDU sessions, the number of UEs connected to each of the network slice(s), a predefined threshold value (first threshold value) corresponding to the UE registration for each network slice, a predefined threshold value (second threshold 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. In an aspect, the context data includes, but is not limited to, number of UEs, number of PDU session and data corresponding to application programming interface (API) corresponding to the NSACF server (112) (e.g., Nnsacf_NSAC API).
[0073] In an aspect, the NSACF server (112) is configured to periodically provide the network slice data to the database (114).
[0074] The provisioning system (108) is configured to receive a request for updating at least one parameter of at least one network slice from a user via a computing device. In some examples, the computing device may be implemented as any type of 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. In an example, the computing device may include an extractor and a processor. The extractor may be configured to extract the network slice data from the database (114) in real-time and generate the request for updating the at least one parameter of the network slice.
[0075] In an aspect, the received request comprises, but is not limited to, information corresponding to the network slice (e.g., slice number, threshold value, traffic data, quality of service, security, resource usage, etc.)
[0076] In an example, each network slice may include three subnets: a Radio Access Network (RAN) subnet, a core network (CN) subnet, and a transport network (TN) subnet. In an example, the at least one parameter includes a first threshold value representing a total number of user equipments to be connected with the network slice, and a second threshold value representing a total number of PDU sessions to be established with the network slice. In an example, the at least one parameter includes a number of UEs per subnet of the network slice. For example, the user is a network operator or a service provider. In an aspect, the user is configured to analyze a plurality of network slice usage metrics in real-time. Based on the analysis, the user is configured to generate the request for updating the at least one parameter of the at least one network slice such that the network resources can be utilized fully. Furthermore, in an example, the parameter of at least one network slice may include, but is not limited to, number of UEs, number of PDU sessions, bandwidth, network latency, quality of service (QoS), security, mobility, etc. The bandwidth includes minimum bandwidth, maximum bandwidth, priority levels, etc. The network latency includes maximum latency, latency variations, etc. The QoS includes packet loss rate, error rate, reliability, etc. The security may include type of encryption, firewall rules, access control, etc.
[0077] In an aspect, the provisioning system (108) is configured to analyze the throughput of each network slice. In another aspect, the provisioning system (108) is configured to analyze the load of each network slice.
[0078] FIG. 1B illustrates an exemplary block diagram (100B) of the provisioning system (108) for updating at least parameter of the network slice dynamically, in accordance with an embodiment of the present disclosure.
[0079] Referring to FIG. 1B, in an embodiment, the provisioning system (108) may include one or more processor(s) (122). The one or more processor(s) (122) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (122) may be configured to fetch and execute computer-readable instructions stored in a memory (124) of the provisioning system (108). The memory (124) 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 (124) 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
[0080] In an embodiment, the provisioning system (108) may include an interface(s) (126). The interface(s) (126) may include a variety of interfaces, for example, interfaces for data input and output devices (I/O), storage devices, and the like. The interface(s) (126) may facilitate communication through the system (108). The interface(s) (126) may also provide a communication pathway for one or more components of the system (108).
[0081] The provisioning system (108) further includes a receiving unit (128), a connection unit (130), a processing unit (132), an updating unit (134), a communication unit (136), and a database (138).
[0082] The receiving unit (128) is configured to receive the request for updating the at least one parameter of the at least one network slice from the computing device. In an embodiment, the at least one parameter includes a first threshold value representing a total number of user equipments to be connected with the network slice, and a second threshold value representing a total number of PDU sessions to be established with the network slice. Further, the request for updating the at least one parameter of the at least one network slice includes access type, network slice identifier (ID), etc.
[0083] In an aspect, the provisioning system (108) is configured to update the at least one parameter of the network slice based on one or more access type mentioned in the received request for updating the at least one parameter of the network slice. For example, the one or more access type includes a third-generation partnership project (3GPP) access type and a non-3GPP access type. In an aspect, the 3GPP access type refers to the radio access technologies and standards defined by the 3rd Generation Partnership Project (3GPP) for mobile telecommunications. The 3GPP access type includes, but is not limited to, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Evolved Universal Terrestrial Radio Access (E-UTRA) in Long-Term Evolution (LTE), New Radio (NR) in 5G. In an aspect, Non-3GPP Access Type refers to connectivity technologies and networks that are not defined or standardized by the 3GPP. The non-3GPP access type includes interworking wireless local area networks (I-WLANs), code division multiple access (CDMA) networks, Wi-Fi networks, WiMAX networks, and fixed networks. In an aspect, the non-3GPP service access further includes two types of access: a trusted non-3GPP access and an untrusted non-3GPP access.
[0084] After receiving the request from the computing device, the connection unit (130) is configured to establish a connection with the NSACF server (112). During the establishment of the connection, the connection unit (130) may be configured to perform a number of steps, such as retrieve data, access a service, or perform some other action that requires communication with the NSACF server (112). In an aspect, upon receiving the request from the computing device, the connection unit (130) is activated, which involves initializing necessary resources and preparing to establish a connection. In an aspect, the connection unit (130) may create a socket, representing the communication endpoint. The connection unit (130) may send a connection request to the NSACF server (112). This request includes details like the server's IP address and port number. If the NSACF server (112) is available and accepts the connection request, it responds affirmatively. A communication channel is established once both sides acknowledge and agree to the connection. With the connection established, data can now be exchanged between the provisioning system (108) and the NSACF server (112). This could involve sending requests, receiving responses, and any other necessary interactions to fulfill the original request from the computing device.
[0085] The processing unit (132) cooperates with the receiving unit (128) to receive the request. On receiving the request, the processing unit (132) is configured to process the received request to generate at least one updation signal. In an aspect, the at least one updation signal may trigger a process of updating the parameters of the network slice. In an aspect, the at least one updation signal indicates that the request received from the computing device has been processed and validated by the processing unit. In an aspect, the at least one updation signal serves as a coordinated signal that instructs various units (such as the connection unit and communication unit) on what actions to take next. The processing unit (132) ensures that updates to network slice parameters are synchronized by generating the updation signal.
[0086] The updating unit (134) is configured to cooperate with the processing unit (132) to receive the at least one updation signal. On receiving the at least one updation signal, the updating unit (134) is further configured to update the at least one parameter of the network slice in the database (114) based on the at least one updation signal. In an aspect, information is extracted from the updation signal upon receiving the at least one updation signal. The extracted information includes, but is not limited to, network slice identifier (ID), access type. The value of the parameter of the network slice is then updated based on the extracted information (i.e., access type, network slice identifier).
[0087] In an example, the processing unit (132) is configured to generate a first updation signal for updating the first threshold value. The first threshold value represents the total number of user equipment to be connected with the network slice. In another example, the processing unit (132) is configured to generate a second updation signal for updating the second threshold value. The second threshold value represents the total number of PDU sessions to be established with the network slice. The updating unit (134) is configured to update the at least one parameter of the network slice in real-time. In an aspect, the updating unit (134) is configured to update the at least one parameter of the network slices based upon a plurality of use cases including an ultra-high bandwidth use case, a very low-latency use case, an ultra-reliable low-latency use case, a high-bandwidth use case, and a massive IoT use case. In an example, updating parameters of the network slices based on use case (e.g., ultra-high bandwidth). The network slice for media streaming services (e.g., video streaming) is initially configured with parameters suited for high-bandwidth such as bandwidth (e.g., min =100 Mbps, max = 1 Gbps), latency (e.g., max latency = 50 ms, jitter = 10 ms), QoS (e.g., packet loss rate = less than 0. 1%, error rate = 10-6), security (e.g., encryption = AES-256, firewall rule = restrictive rules to protect content and user data). After performing the updation of the network slice from the high-bandwidth to the ultra-high bandwidth, the updated parameters for ultra-high bandwidth are as follows: bandwidth (e.g., min =1 Gbps, max = 10 Gbps), latency (e.g., max latency = 50 ms, jitter = 5 ms), QoS (e.g., packet loss rate = less than 0. 1%, error rate = 10-6), security (e.g., encryption = apply advanced encryption standards, firewall rule = applying intrusion detection systems (IDS) and applying dynamic and adaptive access controls). The updating unit (134) is configured to generate a notification with the updated parameters of the network slice. The communication unit (136) is configured to send the notification including the at least one updated parameter of the corresponding network slice to the NSACF server (112). Based on the updated parameters, the NSACF server (112) may be configured to allocate the network resources, thereby improving the utilization of the network slice resources. In an aspect, after receiving the notification from the communication unit (136), the NSACF Server (112) modifies the metrics related to the modified network slice. The metrics include, but is not limited to, number of user equipments, number of PDU sessions, latency, throughput, packet loss, error rate, network resources, security, etc.
[0088] In an aspect, the provisioning system (108) is configured to extract real-time network slice data and generate a plurality of updated slice usage metrics. The provisioning system (108) is configured to communicate the generated plurality of updated slice usage metrics to 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 saves many of the 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.
[0089] In an aspect, the database (138) is configured to store program instructions. The database (138) is configured to store the request received from the receiving unit (128). The program instructions include a program that implements a method to update the at least one parameter of the network slice in accordance with embodiments of the present disclosure and may implement other embodiments described in this specification. The database (138) may be configured to store the updated parameter, the generated notification. The database (138) may include any computer-readable medium known in the art including, for example, volatile memory, such as Static Random Access Memory (SRAM) and Dynamic Random Access Memory (DRAM) and/or nonvolatile memory, such as Read Only Memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes.
[0090] FIG. 1C illustrates another exemplary network architecture (100C) for implementing a NSACF cluster (116) for updating the at least one parameter of the network slice dynamically, in accordance with an embodiment of the present disclosure.
[0091] The NSCAF cluster (116) comprises the provisioning system (108), the NSACF server (112) and the database (114). The provisioning system (108) is commutatively coupled to the NSACF server (112) and the database (114).
[0092] The NSACF server (112) is operatively coupled with the database (114).
[0093] The provisioning system (108) is configured to receive a request for updating at least one parameter of at least one network slice from a computing device. In an aspect, the received request comprises, but is not limited to, information corresponding to the network slice (e.g., slice identifier, access type, threshold value, traffic data, quality of service, security, resource usage, etc.). After receiving the request, the provisioning system (108) is configured to establish connection with the NSACF server (112) and the database (114). The provisioning system (108) is configured to process the received request to generate at least one updation signal. In an aspect, the generated at least one updation signal comprises values to be updated for the at least one parameter. In an example, for parameter bandwidth for network slice 1, the current value = 50 Mbps. The updation signal includes the value to be updated for bandwidth = 100 Mbps.
[0094] The provisioning system (108) is configured to update the at least one parameter of the network slice in the database (114) based on the at least one updation signal and generate a notification comprising the at least one updated parameter of the corresponding network slice. In an example, the value for parameter (e.g., bandwidth) of the network slice 1 is updated from 50 Mbps to 100 Mbps. The notification comprising the updated bandwidth value of 100 Mbps for the network slice 1 is sent to the NSACF server (112).
[0095] FIG. 1D illustrates an exemplary flow diagram (100D) for updating the at least one parameter of the network slice dynamically, in accordance with an embodiment of the present disclosure.
[0096] At step (142), the provisioning system (108) receives a slice update request from the user. The slice update request is a request to modify parameters or configuration of the network slice. The slice update request includes, but is not limited to, a network slice identifier, an access type, a priority level, a timestamp, etc.
[0097] The provisioning system (108) processes the received request to determine the parameter to be updated of the network slice. Based on the determination, the provisioning system (108) generates an updation signal.
[0098] The provisioning system (108) updates the parameter based on the updation signal and generates a notification signal. The notification signal includes the updated parameter of the network.
[0099] At step 144, the provisioning system (108) sends the generated notification signal towards the NSACF server (112).
[00100] Further, the provisioning system (108) sends the updated data of the network slice to the database (114). The database includes context data corresponding to the plurality of network slices. The context data of the network slices includes a number of registered UEs, a number of connected UEs, the number of active PDU sessions, the number of UEs connected to each of the network slice(s), a predefined threshold value (first threshold value) corresponding to the UE registration for each network slice, a predefined threshold value (second threshold 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. Further, the context data includes data corresponding to APIs of the NSCAF server (112).
[00101] At step 146, on receiving the updated data corresponding to the network slice, the database updates the context data corresponding to the network slice based on the received updated data. In this way, the parameters of the network slice are updated in the database (114).
[00102] In an embodiment, an operation: update (POST) request is a custom operation used to update the Slice Collection configurations, i.e. local configurations of the maximum number of registered UEs and/or maximum number of protocol data unit (PDU) sessions established at the network slice. In data structures supported by the POST request, the data type (e.g., ACUpdateData) provides the local configuration data for Network Slice Admission Control (NSAC) procedure related to update the local maximum number of registered UEs and/or the local maximum number of PDU sessions of the network slice at the NSACF. In data structures supported by a POST response, the POST response indicates successful processing of the request to update the local configuration for NSAC procedure, i.e., the local maximum number of registered UEs and/or the local maximum number of PDU sessions per network slice. Furthermore, the Nnsacf_NSAC may use the Nnsacf_NSAC API. The API URI of the Nnsacf_NSAC API may be {apiRoot}//. In an aspect, the POST request refers to a specific type of data transfer method used in a Hypertext Transfer Protocol (HTTP) communication for sending data to the NSACF server. This data may be for various purposes, such as creating or updating information on the NSACF server. On receiving a POST request, the NSACF server performs network slice admission control related to the number of UEs registered to a network slice or a group of network slices.
[00103] In another embodiment, a primary NSACF may update the allocated local Maximum number of UE and/or PDU sessions configured at the NSACFs. The Primary NSACF decides to update the local maximum number of UE or PDU session values at the NSACF(s), i.e. the configured value at NSACF(s) based on the current registered UE/PDU session number at NSACFs and based on operator policy. The Primary NSACF invokes Nnsacf_NSAC_LocalNumberUpdate Request to the NSACF(s). The message includes the new configured value of local Maximum number of UE or PDU sessions. The new configured value(s) of local maximum number given by the Primary NSACF can be lower than the existing local maximum number configured at the NSACF(s). The NSACF replaces the local maximum number with the received new local maximum number value. The NSACF returns the Nnsacf_NSAC_LocalNumberUpdate Response to the Primary NSACF.
[00104] In yet another embodiment, a Nnsacf_NSAC service enables consumer NF to check the availability per network slice and update the number of UEs registered with a network slice, or the number of UEs with at least one PDU Session/PDN connection established on the network slice in the case of EPC interworking, or the number of PDU Sessions established on the network slice.
[00105] FIG. 2 illustrates an exemplary flow diagram of a method (200) for updating the at least one parameter of the network slice dynamically, in accordance with an embodiment of the present disclosure.
[00106] Step (202) includes receiving, by the receiving unit (128), the request for updating at least one parameter of the network slice from a computing device. In an aspect, the request for updating at least one parameter of the network slice includes, but is not limited to, an access type and a network slice identifier (ID). In an embodiment, the at least one parameter includes a first threshold value representing a total number of user equipments to be connected with the network slice, and a second threshold value representing a total number of PDU sessions to be established with the network slice. In an embodiment, updation of the at least one parameter is based on one or more access types. The one or more access types includes a third-generation partnership project (3GPP) access type and a non-3GPP access type.
[00107] Step (204) includes establishing, by a connection unit (130), a connection with at least one network slice admission control function (NSACF) server (112) and the database (114) associated with at least one the NSACF server (112). In an aspect, the connection unit (130) may initiate communication protocols and protocols defined by the respective NSACF server (112) and database (114), establishing a secure and reliable link for data exchange. This includes negotiating connection parameters, such as authentication credentials, network configurations, and communication protocols, to ensure compatibility and secure access between the connection unit (130), NSACF server (112), and database (114). The established connection facilitates seamless data retrieval, transmission, and management required for network slice operations.
[00108] Step (206) includes processing, by the processing unit (132), the received request to generate at least one updation signal. In an aspect, the updation signal refers to a signal that conveys specific instructions to modify the configuration or performance parameters of the network slice.
[00109] The processing unit (132) analyzes the received request to determine modifications needed for the network slice parameters stored in the database (114). Based on this analysis, the processing unit (132) generates the at least one updation signal, which specifies the changes or updates to be made to the parameters of the network slice. The generation of the updation signal may involve computing new values, validating input data, applying predefined algorithms or rules, or any other suitable method for determining the necessary updates.
[00110] In an aspect, the generation of the updation signal involves determining which parameters need to be updated. The current values of the parameters that need to be updated are assessed and compared with the required values of the parameters to identify the necessary updates. Based on this analysis, the updation signal is generated.
[00111] Step (208) includes updating, by an updating unit (134), the at least one parameter of the network slice in the database (114). The updating unit (134) collaborates with the processing unit (132) to receive at least one updation signal and is further configured to update at least one parameter of the network slice stored in the database (114) based on the received updation signal. In an embodiment, the at least one parameter includes a first threshold value representing a total number of user equipments to be connected with the network slice, and a second threshold value representing a total number of PDU sessions to be established with the network slice. In an example, current values of number of user equipments = 1000 and number of PDU session = 500 for network slice ID = Slice132. On receiving the update request, the information (e.g., network slice ID, access type) is extracted by processing the received update request. The network slice ID = Slice132, the access type = 3GPP access type (e.g., 5G) are determined. The updation signal is generated based on the processed update request. The updation signal includes updated values for number of user equipments = 2000 and number of PDU session = 1000. Based on the updation signals, the values of number of user equipments changed from 1000 to 2000 and number of PDU sessions changed from 500 to 1000 for the network slice ID = Slice 132.Step (210) includes generating, by the updating unit (134), a notification comprising the at least one updated parameter of the network slice. The updating unit (134) is further configured to generate a notification that comprises the at least one updated parameter of the corresponding network slice. The notification may include, but is not limited to, one or more of the following types: a status update message, an alert message, or an event notification. In an example, the notification comprising the updated values for number of user equipments = 2000 and number of PDU sessions = 1000 for network slice = Slice 132 is generated.
[00112] Step (212) includes sending, by the communication unit (136), the generated notification to the NSACF server (112). In an aspect, the NSACF server (112) is configured to update one or more network slice metrics on receiving the notification from the provisioning system (108). The network slice metrics includes, but is not limited to, number of UEs, number of PDU session, latency, throughput, packet loss, error rate, network resources, security, etc. In an example, the NSACF server (112) updates network slice metrics such as number of user equipments = 2000 and number of PDU sessions = 1000 for network slice = Slice 132.
[00113] The updated network slice metrics are provided to a network operator. The network operator uses the received updated network slice metrics to manage the network resources for the network slice. In this way, the provisioning system (108) and the NSACF server (112) dynamically update the at least one parameter corresponding to the network slice which offers enhanced control and flexibility to the network operator in managing network resources.
[00114] In an aspect, the method (200) may include a step of modifying, by the NSACF server (112), a plurality of network slice usage metrics based on the modified network slice details (parameters). The number of network slice usage metrics includes number of active UEs, number of PDU sessions, bandwidth, throughput, latency, error rates, etc. On receiving the updated at least one parameter from the provisioning system (108), the NSACF server (112) updates or modifies network slice usage metrics based on the received at least one updated parameter. Furthermore, the NSACF server (112) sends the updated or modified network slice usage metrics to the network operators. In an example, when a notification of a traffic event occurs (e.g., an increase in active UEs in the network), the NSACF server (112) updates the throughput (e.g., from 80 Mbps to 90 Mbps) and latency (e.g., from 25 ms to 30 ms).
[00115] FIG. 3 illustrates an exemplary computer system (300) in which or with which embodiments of the present disclosure may be implemented.
[00116] As shown in FIG. 3, the computer system may include an external storage device (310), a bus (320), a main memory (330), a read-only memory (340), a mass storage device (350), communication port(s) (360), and a processor (370). A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. The processor (370) may include various modules associated with embodiments of the present disclosure. The communication port(s) (360) may be any of an RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port(s) (360) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system connects.
[00117] The main memory (330) may be random-access memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (340) 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 (370). The mass storage device (350) may be any current or future mass storage solution, which can be used to store information and/or instructions. Exemplary mass storage device (350) includes, but is not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and/or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks.
[00118] The bus (320) communicatively couples the processor (370) with the other memory, storage, and communication blocks. The bus (320) 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 (370) to the computer system.
[00119] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus (320) to support direct operator interaction with the computer system. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (360). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.
[00120] 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.
[00121] The present disclosure provides technical advancement related to dynamically updating network slice parameters. This advancement addresses the limitations of existing solutions by generating an updation signal for updating the network slice parameters. The disclosure involves updating the network slice parameters based on the use cases which offers enhanced control and flexibility to a network operator in managing network resources.
TECHNICAL ADVANCEMENTS
[00122] The present disclosure described herein above has several technical advantages including, but not limited to, the realization of a provisioning system for updating network slice parameters dynamically that:
1. updates at least one parameter of a network slice.
2. updates the threshold values of the network slice update for both user equipment (UE) registration and protocol data unit (PDU) session establishments
3. sets the threshold values for individual type of access types, and
4. offers enhanced control and flexibility to a network operator in managing network resources.
,CLAIMS:CLAIMS
We Claim:
1. A provisioning system (108) for updating at least one parameter of a network slice, the provisioning system (108) comprising:
a receiving unit (128) configured to receive a request for updating the at least one parameter of the network slice from a computing device (104);
on receiving the request, a connection unit (130) configured to establish a connection with at least one network slice admission control function (NSACF) server (112), and a database (114) coupled with the NSACF server (112);
a processing unit (132) configured to cooperate with the receiving unit (128) to receive the request and is further configured to process the received request to generate at least one updation signal;
an updating unit (134) configured to cooperate with the processing unit (132) to receive the at least one updation signal and is further configured to update the at least one parameter of the network slice in the database (114) based on the at least one updation signal and generate a notification comprising the at least one updated parameter of the corresponding network slice; and
a communication unit (136) configured to send the generated notification to the NSACF server (112).
2. The provisioning system (108) as claimed in claim 1, wherein the communication unit (136) is configured to send the at least one updated parameter of the corresponding network slice to the database (114), wherein upon receiving the at least one updated parameter from the provisioning system (108), the database (114) is configured to update context data of the corresponding network slice based on the received the at least one updated parameter.

3. The provisioning system (108) as claimed in claim 1, wherein the at least one parameter includes a first threshold value representing a total number of user equipments to be connected with the network slice, and a second threshold value representing a total number of PDU sessions to be established with the network slice.

4. The provisioning system (108) as claimed in claim 1, wherein updation of the at least one parameter is based on one or more access type, wherein the one or more access type includes a third-generation partnership project (3GPP) access type and a non-3GPP access type.

5. The provisioning system (108) as claimed in claim 1, wherein the processing unit (132) is configured to update the at least one parameter of the network slices based upon a plurality of use cases including at least one of an ultra-high bandwidth use case, a very low-latency use case, an ultra-reliable low-latency use case, a high-bandwidth use case, and a massive IoT use case.

6. The provisioning system (108) as claimed in claim 1, wherein the NSACF server (112) is configured to update one or more network slice metrics on receiving the notification from the communication unit (136).

7. A method (200) for updating at least one parameter of a network slice, the method (200) comprising:
receiving (202), by a receiving unit (128), a request for updating the at least one parameter of the network slice from a computing device (104);
on receiving the request, establishing (204), by a connection unit (130), a connection with at least one network slice admission control function (NSACF) server (112) and a database (114) associated with the at least one NSACF server (112);
processing (206), by a processing unit (132), the received request to generate at least one updation signal;
updating (208), by an updating unit (134), the at least one parameter of the network slice in the database (114);
generating (210), by the updating unit (134), a notification comprising the at least one updated parameter of the corresponding network slice; and
sending (212), by a communication unit (136), the generated notification to the NSACF server (112).
8. The method (200) as claimed in claim 7 further comprising:
sending, by the communication unit (136), the at least one updated parameter of the corresponding network slice to the database (114), wherein upon receiving the at least one updated parameter from the provisioning system (108), the database (114) is configured to update context data of the corresponding network slice based on the received the at least one updated parameter.

9. The method (200) as claimed in claim 7, wherein the at least one parameter includes a first threshold value representing a total number of user equipments to be connected with the network slice, and a second threshold value representing a total number of PDU sessions to be established with the network slice.

10. The method (200) as claimed in claim 7, wherein updation of the at least one parameter is based on one or more access types, wherein the one or more access type includes a third-generation partnership project (3GPP) access type and a non-3GPP access type.

11. The method (200) as claimed in claim 7 further includes a step of updating at least one parameter of the network slice based upon one or more access type, wherein the one or more access type includes at least one of an ultra-high bandwidth use case, a very low-latency use case, an ultra-reliable low-latency use case, a high-bandwidth use case, and a massive IoT use case.

12. The method (200) as claimed in claim 7, wherein the NSACF server (112) is configured to update one or more network slice metrics on receiving the notification from the communication unit (136).

13. A user equipment (104) communicatively coupled with a provisioning system (108) in a network (106), the coupling comprises steps of:
receiving, by the provisioning system (108), a connection request;
sending, by the provisioning system (108), an acknowledgment of the connection request to the user equipment (104); and
transmitting a plurality of signals in response to the connection request, wherein the provisioning system (108) is configured for updating at least one parameter of a network slice.