Method, system, and computer-readable medium for providing updated network slice information to a network slice selection function (NSSF)

Abstract

A method for providing updated network slice information to a network slice selection function (NSSF) includes a network slice management function (NSMF) registering an NF profile corresponding to the NSMF in a network function (NF) repository function (NRF), and the NSMF subscribing to the NRF for status updates corresponding to NF instances belonging to a network slice instance created by the NSMF. The method further includes the NSMF receiving a notification message from the NRF, the notification message including one or more network traffic load level updates related to at least one of the NF instances, processing the one or more network traffic load level updates to generate network slice instance configuration information for at least one of the network slice instances, and the NSMF providing the network slice instance configuration information to an NSSF that manages at least one of the network slice instances.

Description

[Technical field]

[0001] Claiming priority This application claims the benefit of priority to U.S. Patent Application No. 17 / 382,299, filed July 21, 2021, the disclosure of which is incorporated herein by reference in its entirety.

[0002] Technical Field The subject matter described herein relates to communication of network slice information in a 5G network. More particularly, the subject matter described herein relates to a method, a system, and a computer-readable medium for a method for providing updated network slice information to a network slice selection function (NSSF). [Background technology]

[0003] background In a 5G telecommunications network, a network node that provides a service is called a producer network function (NF). A network node that consumes a service is called a consumer NF. A network function can be both a producer NF and a consumer NF depending on whether it consumes or provides a service.

[0004] A given producer NF can have many service endpoints, where a service endpoint is a combination of an Internet protocol (IP) address and a port number on the network node hosting the producer NF. The producer NF registers with a network function repository function (NRF). The NRF maintains NF profiles of available NF instances and the supported services of the NF instances. Consumer NFs can subscribe to receive information about producer NF instances that have registered with the NRF.

[0005] An example of an NF that provides services to user equipment (UE) devices, such as Internet of Things (IoT) devices, is the access and mobility management function (AMF). The AMF provides registration management, connection management, reachability management, mobility management, and other services for UE devices. The AMF serves as the interface between the radio access network and the rest of the nodes in the 5G core network. The AMF also serves as the access point to network slice services.

[0006] Network slicing is a service provided in 5G networks, where network resources are logically allocated in portions or slices for use by UE devices. Each network slice can provide a specific function or service to the UE. A network slice instance is defined as a set of network functions and resources for the network functions that are arranged and configured to form and meet a specific set of network requirements or characteristics. For example, a network slice instance for an access network service can be resources of a virtualized gNodeB and AMF to provide access network services for the UE. A network slice instance for a core network service can include resources of a virtualized NRF and a network exposure function (NEF) configured to provide core network services for the UE, e.g., IoT, digital call sessions, and the like. Summary of the Invention [Problem to be solved by the invention]

[0007] In a 5G telecommunications network, there are scenarios in which the AMF attempts to obtain network slice information from the NSSF. In particular, the AMF requests network slice information from the NSSF when it requests the identity of a suitable network slice instance to route a call session for a supported user equipment. One problem that exists is that the NSSF receives updated network slice instance status information from the NRF infrequently and in a static manner. Thus, the NSSF may often be provisioned with (or have access to) out-of-date or inaccurate network slice instance information (e.g., a supported network slice instance recently encounters an overload condition without the knowledge of the NSSF).

[0008] In view of these difficulties, therefore, there is a need for a method, system, and computer-readable medium for the method for providing updated network slice information to an NSSF. [Means for solving the problem]

[0009] overview A method for providing updated network slice information to a network slice selection function (NSSF) includes a network slice management function (NSMF) registering an NF profile corresponding to the NSMF in a network function (NF) repository function (NRF), and the NSMF subscribing to the NRF for status updates corresponding to NF instances belonging to a network slice instance created by the NSMF. The method further includes the NSMF receiving a notification message from the NRF, the notification message including one or more network traffic load level updates related to at least one of the NF instances, processing the one or more network traffic load level updates to generate network slice instance configuration information for at least one of the network slice instances, and the NSMF providing the network slice instance configuration information to an NSSF that manages at least one of the network slice instances.

[0010] According to another aspect of the methods described herein, the method includes instructions for creating additional network slice instances, modifying the network slice instances, or removing one or more of the network slice instances.

[0011] According to another aspect of the method described herein, network slice instance configuration information is provided to the NSSF via an update message pushed by the NSMF.

[0012] According to another aspect of the method described herein, the NSSF is configured to request network slice instance configuration information from the NSMF via a pull message.

[0013] According to another aspect of the method described herein, the NSSF is configured to utilize the network slice instance configuration information to respond to the network slice selection service request message.

[0014] According to another aspect of the method described herein, network slice instance configuration information is provided by the NSMF to the NSSF in real time.

[0015] According to another aspect of the method described herein, the NSMF registers with the NRF as a custom NF.

[0016] According to another aspect of the subject matter described herein, a system for providing updated network slice information to an NSSF, the system comprising an NSMF including at least one processor and a memory. The system further includes an orchestration engine stored in the memory and implemented by the at least one processor for registering an NF profile corresponding to the NSMF with the NRF, subscribing to the NRF for status updates corresponding to NF instances belonging to a network slice instance created by the NSMF, receiving from the NRF a notification message including one or more network traffic load level updates related to at least one of the NF instances, processing the one or more network traffic load level updates to generate network slice instance configuration information for at least one of the network slice instances, and providing the network slice instance configuration information to an NSSF managing at least one of the network slice instances.

[0017] According to another aspect of the systems described herein, the network slice instance configuration information includes instructions for creating additional network slice instances, instructions for modifying the network slice instances, or instructions for removing one or more of the network slice instances.

[0018] According to another aspect of the system described herein, network slice instance configuration information is provided to the NSSF via an update message pushed by the NSMF.

[0019] According to another aspect of the system described herein, the NSSF is configured to request network slice instance configuration information from the NSMF via a pull message.

[0020] According to another aspect of the system described herein, the NSSF is configured to utilize the network slice instance configuration information to respond to a network slice selection service request message.

[0021] According to another aspect of the system described herein, network slice instance configuration information is provided by the NSMF to the NSSF in real time.

[0022] According to another aspect of the system described herein, the NSMF registers with the NRF as a custom NF.

[0023] According to another aspect of the subject matter described herein, a non-transitory computer-readable medium having executable instructions stored thereon, the executable instructions, when executed by a processor of the computer, control the computer to perform steps including: an NSMF registering an NF profile corresponding to the NSMF with the NRF; and the NSMF subscribing to the NRF for status updates corresponding to NF instances belonging to a network slice instance created by the NSMF. The method includes the NSMF receiving a notification message from the NRF, the notification message including one or more network traffic load level updates associated with at least one of the NF instances, processing the one or more network traffic load level updates to generate network slice instance configuration information for at least one of the network slice instances, and the NSMF providing the network slice instance configuration information to an NSSF that manages at least one of the network slice instances.

[0024] The subject matter described herein may be implemented in hardware, software, firmware, or any combination thereof. Thus, the terms "function," "node," or "module" as used herein refer to hardware that may also include software and / or firmware components for implementing the described features. In one exemplary embodiment, the subject matter described herein may be implemented using a computer-readable medium having stored thereon computer-executable instructions that, when executed by a processor of a computer, control a computer to perform a number of steps. Exemplary computer-readable media suitable for implementing the subject matter described herein include non-transitory computer-readable media, such as disk memory devices, chip memory devices, programmable logic devices, and application specific integrated circuits. Furthermore, computer-readable media implementing the subject matter described herein may be located on a single device or computing platform, or may be distributed across multiple devices or computing platforms.

[0025] The subject matter described herein will now be described with reference to the accompanying drawings. [Brief description of the drawings]

[0026] [Figure 1] FIG. 1 is a network diagram illustrating an example 5G network architecture, in accordance with an embodiment of the subject matter described herein. [Diagram 2] A message flow diagram illustrating communication of network slice instance modification information according to an embodiment of the subject matter described herein. [Diagram 3] FIG. 1 is a network slice instance architecture diagram according to an embodiment of the subject matter described herein. [Figure 4]1 is a flowchart illustrating an example process for establishing message priority in a network slice based on QoS parameters, in accordance with an embodiment of the subject matter described herein. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0027] Detailed Description FIG. 1 is a block diagram illustrating an example 5G system network architecture. In FIG. 1, the network includes an NRF 100 and a service communication proxy (SCP) 101. As described above, the NRF 100 can maintain profiles of available producer NF service instances and their supported services, and enable consumer NFs or SCPs to subscribe to new / updated producer NF service instances and be notified of their registration. The SCP 101 can also support service discovery and selection of producer NFs. Furthermore, the SCP 101 can perform load balancing of connections between consumer NFs and producer NFs.

[0028] The NRF 100 is a repository for NF profiles. To communicate with a producer NF, a consumer NF or an SCP must obtain an NF profile from the NRF 100. An NF profile is a JavaScript object notation (JSON) data structure. An NF profile definition includes at least one of a fully qualified domain name (FQDN), an Internet protocol (IP) version 4 (IPv4) address, or an IP version 6 (IPv6) address.

[0029] In FIG. 1, any of the nodes (other than the SCP 101 and the NRF 100) can be a consumer NF or a producer NF depending on whether they are consuming or providing a service. In the illustrated example, the node includes a policy control function (PCF) 102 that performs policy-related operations in the network, a unified data management (UDM) function 104 that manages user data, and an application function (AF) 106 that provides application services. The node illustrated in FIG. 1 further includes a session management function (SMF) 108 that manages a session between the AMF 110 and the PCF 102. The AMF 110 performs mobility and registration management operations similar to those performed by a mobility management entity (MME) in a 4G network. The AMF 110 also serves as an access point for the network slice service. The AMF 110 can also perform AMF selection to select a serving AMF that will provide access to the network slice service requested by the UE during registration.

[0030] An authentication server function (AUSF) 112 performs authentication services for user equipment (UE), such as UE 114, seeking access to the network.

[0031] The network slice selection function (NSSF) 116 provides network slice subnet availability information (NSSAI) and NS selection services for devices that seek to access a particular network function. The NSSF 116 can obtain AMF loading information from the NRF and NSSAI availability information from the AMF. The NSSF 116 can store the AMF loading information and the NSSAI availability information in an AMF selection database maintained by the NSSF 116. When the NSSF 116 receives an NSSAI selection request from the AMF, the NSSF 116 can utilize the stored AMF loading information and NSSAI availability information to calculate an AMF relevance score and weight for each AMF that can support a network slice service requested by a UE seeking access to the network slice service. The NSSF 116 can generate a prioritized list of AMFs that can provide the requested service and corresponding weights, and communicate the list to the requesting AMF. The requesting AMF can then use the prioritized list of AMFs and weights to select an AMF for providing access to the requested network slice service.

[0032] The Network Exposure Function (NEF) 118 provides an application programming interface (API) for application functions that want to obtain information about Internet of Things (IoT) devices and other UEs connected to the network. The NEF 118 performs a function similar to the service capability exposure function (SCEF) in 4G networks.

[0033] The radio access network (RAN) 120 connects the UE 114 to the network via a wireless link. The radio access network 120 may be accessed using a g-Node B (gNB) (not shown in FIG. 1) or other wireless access points. The user plane function (UPF) 122 may support various proxy functions for user plane services. One example of such a proxy function is a multipath transmission control protocol (MPTCP) proxy function. The UPF 122 may also support a performance measurement function that may be used by the UE 114 to obtain network performance measurements. Also shown in FIG. 1 is a data network (DN) 124 through which the UE accesses data network services, such as Internet services.

[0034] A service edge protection proxy (SEPP) 126 filters incoming traffic from another PLMN and performs topology hiding for traffic leaving the home PLMN. The SEPP 126 can communicate with a SEPP in a foreign PLMN that manages security for the foreign PLMN. Thus, traffic between NFs in different PLMNs can traverse a minimum of two SEPP functions, one for the home PLMN and the other for the foreign PLMN.

[0035] As indicated above, network slicing involves providing virtual network functions and allocating resources for the virtual network functions to meet given requirements. For example, network slicing may include virtualizing any of the network functions illustrated in FIG. 1 and providing access to services implemented by multiple different network functions as network slice instances.

[0036] At the highest level, the network slice is accessible through communication services provided by a communication service provider. The communication services can include business-to-consumer communication services, such as mobile web browsing, voice over LTE calling, and rich communication services. The communication services can also include business-to-business services, such as Internet access and local area networks (LANs).

[0037] Network slices as a service may be offered by communication service providers to their customers. Network slice services may be characterized by a number of parameters including radio access technology, bandwidth, end-to-end latency, guaranteed / non-guaranteed QoS, security level, etc.

[0038] In some embodiments, the disclosed subject matter establishes an exchange mode of information between the NSMF and the NSSF, and updates regarding the network slice instance are pushed or provided directly to the NSSF in real time. For example, the NSSF may be enhanced to expose a representational state transfer (REST) ​​application programming interface (API) that may be utilized by the NSMF to send network slice instance configuration information indicating modification changes to the network slice. In particular, the disclosed subject matter enables automatic provisioning of updated network slice instance information in the NSSF based on network traffic load level feedback of network functions and / or NF services received from the NRF. Provisioning the network slice information in this manner, in particular, avoids and / or obviates intervention by the network operator.

[0039] Currently, the NSSF exposes an Nnssf_NSSelection_Get service operation that enables network slice selection in both serving public land mobile networks (PLMNs) and home public land networks (HPLMNs). This service operation further enables the NSSF to provide the AMF with the authorized and configured NSSAIs for the serving PLMNs. Using this service operation, the NSSF can assign network slices to the requesting user equipment during registration procedures, inter-PLMN mobility procedures, PDU session establishment procedures, UE configuration update procedures, and the like. In response to receiving a network slice selection request message (e.g., via the Nnssf_NSSelection_Get service operation), the NSSF selects a network slice instance based on pre-provisioned information. Furthermore, the NSSF subsequently determines and returns (e.g., via the Nnssf_NSSelection_Get response message) an appropriate NRF to be used to select network functions and / or services within the selected network slice instance.

[0040] As indicated above, the 3GPP standard does not define a procedure by which the NSMF directly interacts with the NSSF for any updated configuration changes in the generated / supported network slices (e.g., NSIs) as a result of management and orchestration. Furthermore, performance data collection typically involves a network slice subset management function (NSSMF) collecting performance data from NF services and network functions in each network slice instance. This performance data is then provided to the NSMF using a pull mechanism (e.g., the NSMF sends a request message). In contrast, the disclosed subject matter employs a more dynamic push-based system, as described below.

[0041] FIG. 2 is a message flow diagram illustrating communication of network slice instance modification information according to an embodiment of the subject matter described herein. As shown in FIG. 2, 5G messaging may take place between the NSMF 212, the NRF 214, and the NSSF 216. In some embodiments, the NSMF 212 may include an orchestration engine 220 that indicates a list of steps (or changes in steps) embodied in a state machine (e.g., by software code programming or by a set of rules) of the NSMF 212. As described herein, the NSMF 212 and / or the orchestration engine 220 may be configured to be responsible for performance data collection at the NSSI level by creating measurement jobs for network functions in the NSSI. The NSMF 212 may also be responsible for generating performance data at the network slice interface level, where the performance data may include network traffic load data of all network slice instances indicating total user traffic levels and / or total signaling traffic levels present in the network slice instance. The performance data generated at the network slice interface level may also include service performance data provided by the network slice instance. In some embodiments, the service performance data includes total user traffic data, signaling traffic data, and service quality data (e.g., QoS data of a service may indicate whether a network slice instance delivers a service at an expected QoS level) corresponding to a particular service instance. Furthermore, the NSMF212 may be configured to manage and orchestrate the network slice instance based on the performance data and the service performance data, and provide performance feedback to the operator along with a snapshot of the network slice instance for updates in the NSSF216 (e.g., for use by the 5G NF). By way of illustration, FIG. 3 shows a network slice instance architecture diagram in accordance with an embodiment of the subject matter described herein.For example, the system 300 includes network slice instances 301-303 (e.g., NSI-X, NSI-Y, and NSI-Z) that are generated / produced by the NSSF 304, the NSMF 302, and the NSMF 312 and supported by the NSMF 312. Although only three network slice instances are shown in FIG. 3, any number of network slice instances may be supported by the NSMF 312 and / or the NSSF 316 without departing from the scope of the disclosed subject matter. Furthermore, as shown in FIG. 3, each of the network slice instances 301-303 includes multiple network slice subnet instances. For example, the network slice instance 301 includes network slice subset instances 311-312. Furthermore, each of the network slice subset instances 311-332 shown in FIG. 3 includes one or more underlying network functions and / or NF services. The communication links connecting the NSMF 302 and the network slice subset instances 311-332 can help facilitate performance feedback from network slice instance and / or network slice instance level updates based on policies. For example, the NSMF 302 orchestrates management of various network slices by utilizing the communication links to collect performance and / or metric information regarding the network slice instances, network slice subset instances, and underlying network functions. Similarly, the communication links connecting the NSMF 302 and the NSSF 304 can be used to communicate network slice instance level policies and thresholds without the need for an operator or system administrator. Furthermore, the performance feedback can likewise be used by the NSMF 302 to push network slice instance updates to the NSSF 316 in a manner described below (e.g., method 400 in FIG. 4).

[0042] Returning to FIG. 2, the NSSF 216 and / or the orchestration engine 220 are configured to register its network function profile with the NRF 214. In particular, the NSSF 216 sends an NF profile registration message 201 including the services provided by the NSSF 216 to the NRF 214. As indicated above, the NSSF 216 is responsible for maintaining the network slice instance information of the network slices it supports along with the associated network slice instance identifiers (e.g., NSI-IDs). After receiving the registration message 201, the NRF 214 registers the NF profile of the NSSF 216 and its associated services and records them in a local registry. In a similar manner, the NSMF 212 similarly registers its NF profile and the provided services with the NRF 214. As shown in FIG. 2, the NSMF 212 sends an NF profile registration message 202 including its NF profile and its services provided by the NSMF 212. In particular, the registration message 202 further specifies the NSMF 212 as a custom network function (i.e., a “CUSTOM NF” identifier) ​​to the NRF 214.

[0043] After registering as a custom network function, the NSMF 212 and / or orchestration engine 220 may be configured to subscribe to the NRF 214 to receive status update information (e.g., NF network traffic load level information / updates / changes) from the specified NF. In particular, the NSMF 212 and / or orchestration engine 220 transmit a subscription request message 203 to request and receive network traffic load levels for network functions (and associated NF services) instantiated on and / or belonging to the network slice instance created by the NSMF 212. For example, the NSMF 212 subscribes to the NRF 214 to request capacity and performance metric data for network functions registered with the NRF 214. In particular, this information includes traffic load level changes in all of the network functions executing in the network slice instances that the NSSF 216 is managing.

[0044] In response to subscribing to the network traffic load levels from the NRF 214, the NSMF 212 is configured to receive notification messages regarding the network traffic load information of all network functions from the NRF 214. In particular, all of the network functions and network function services are configured to share their network traffic load level data with the NRF 214 via the NF-NRF heartbeat message. For example, if a network function in a particular network slice instance (supported by the NRF 214) happens to experience a network traffic overload condition, the overloaded network function will report this change related to its target network traffic function to the NRF 214. Because the NSMF 212 is subscribed to four network function status updates for the NRF 214, the NSMF 212 will receive this network traffic load level change information from the NRF 214 immediately. For example, the NSMF 212 and / or the orchestration engine 220 may be configured to receive at least one subscription report message 204 from the NRF 214 in real time. In particular, the subscription report message 204 is generated / generated by the NSMF 212 and includes information including changes to network traffic load levels corresponding to one or more of the network functions associated with the network slice instance supported by the NRF 214.

[0045] At block 205, the NSMF 212 and / or orchestration engine 220 are configured to process the network traffic load levels and apply local policies to the network slice instance layer. In some embodiments, the NSMF 212 and / or orchestration engine 220 may be provisioned or configured with local policies directed to orchestration and management of the network slice. In particular, the NSMF 212 and / or orchestration engine 220 may be provisioned with policies that may be used to determine whether a particular traffic load level change experienced by a network function associated with a supported network slice instance needs to be addressed and / or remedied. For example, the NSMF 212 and / or orchestration engine 220 may be configured to process changes regarding the traffic load levels of the network function upon notification by the NRF 214. The NSMF 212 may also utilize the policies and configured network traffic load thresholds (e.g., operator-provisioned load thresholds) to perform network slice management tasks to evaluate whether a particular change to the network slice instance(s) is required. For example, if the network traffic load level change experienced by the network function exceeds a predetermined threshold defined by the policy, the NSMF 212 and / or orchestration engine 220 may be configured to modify the characteristics of the underlying network slice instance (e.g., adjust / increase additional network resources for the network slice, such as compute, RAM, storage, etc.). In response to determining that the network slice instance and / or network function needs to be modified, the NSMF 212 and / or orchestration engine 220 may utilize the local policy to generate network slice instance configuration data including an updated NSI configuration that may be used by the NSSF 216 for enforcement.In some embodiments, network slice management tasks may include, but are not limited to, creating a network slice instance, updating a network slice instance, removing a network slice instance, and / or the like. In some embodiments, this information may be based entirely on the PLMN, since network slices supported beyond the PLMN will indicate that the NSMF 212 may need to interact with an NRF that exists outside of the NSMF 212's perspective.

[0046] In some embodiments, the NSMF 212 and / or the orchestration engine 220 may be configured to send the network slice instance configuration information (e.g., NSI configuration changes) to the NSSF 216 in an update message 206. For example, in response to an NSI network traffic load level update received in a report message 204 and then processed in block 205, the NSMF 212 and / or the orchestration engine 220 may be configured to "push" the generated NSI configuration information to the NSSF 216 in real time. For example, the update message 206 may be provided by the NSMF 212 to the NSSF 216 by a push mechanism (i.e., send message) immediately after receiving and processing the NF status update information (e.g., network traffic load level change information). In some embodiments, the NSSF 216 may be configured to expose a REST API (and / or new interface) that may be used by the NSMF 212 to facilitate provisioning of network slice information level updates to the NSSF, as described above.

[0047] In response to receiving the network slice instance configuration information, the NSSF 216 may be configured to implement network slice changes for its supported consumer NFs (i.e., at the NSSF 216). For example, the NSSF 216 may utilize the NSI configuration information to modify characteristics of a particular network slice instance. Additionally, the NSSF 216 may immediately begin using the received configuration information to answer network slice selection service request messages (e.g., Nnssf_NSSelection_Get service requests) received from the AMF (or other NSSF).

[0048] In some alternative embodiments, the NSSF 216 may be configured to pull or request network slice instance configuration information from the NSMF 212. For example, the NSSF 216 may issue an NSI configuration information request message to the NSMF 212 via a REST API. In such a scenario, the NSSF 216 may first subscribe to the NSMF 212 to establish authorization to request updated NSI configuration information stored in the NSMF 212.

[0049] 4 is a flow chart illustrating an example process or method 400 for providing updated network slice information to an NSSF, according to an embodiment of the subject matter described herein. In some embodiments, the method 400 illustrated in FIG. 4 is an algorithm, program, or script stored in a memory (e.g., the orchestration engine 220 illustrated in FIG. 2) that, when executed by a processor, performs the steps described in blocks 402-410. In some embodiments, the orchestration engine indicates a list of steps (or changes in steps) to be embodied in a state machine (e.g., by software code programming or by a set of rules) of the NSMF.

[0050] At block 402, the NF profile corresponding to the NSMF is registered with the NRF. More specifically, the NSMF registers its NF profile (including NSMF services) with the NRF. In particular, the registration message indicates the NSMF as a custom NF. As indicated above, the NSMF does not typically register with the NRF because the NSMF is typically configured to handle network slice orchestration duties per 3GPP standards. It should also be noted that the NSSF(s) supported by the NSMF similarly register (or have registered) their NF profile with the NRF per 3GPP TS 29.510.

[0051] At block 404, status updates (e.g., network traffic load level data) corresponding to NF instances belonging to the network slice instance (created by the NSMF) are subscribed to. More specifically, the NSMF subscribes to network traffic load level updates corresponding to network functions (and including NF services) instantiated as part of the NSMF-generated network slice instance.

[0052] At block 406, a notification message is received that includes one or more network traffic load level changes occurring at the NF instance. In some embodiments, the NSMF receives the network traffic load level change notifications from the NFF. In particular, by subscribing to the NFR, the NSMF will receive NF network traffic load level update information from the NRF when supported network functions (e.g., NFs in a network slice instance created by the NSMF) experience changes in their traffic target levels. In particular, network functions in various network slice instances are configured to report their network traffic load level changes to the NRF, which in turn reports the changes to the subscribed NSMFs.

[0053] At block 408, the one or more network traffic load level changes are processed to generate network slice instance configuration information for at least one of the network slice instances. In some embodiments, the NSMF is configured and / or provisioned with local policies that may be utilized by the orchestration engine to orchestrate an existing set of network function resources allocated to different network slice instance responses by the NSMF. Upon receiving a notification of the traffic load level change, the NSMF is configured to orchestrate network slice update information to address the traffic load level change of the supported network slice instance. For example, the NSMF may perform post-processing procedures to add more resources to a network slice instance experiencing an overload condition.

[0054] At block 410, the network slice instance configuration information is provided to the NSSF. In some embodiments, the NSMF sends (i.e., "pushes") the new / updated network slice instance configuration information to the NSSF. In particular, the network slice instance configuration information includes modifications / changes to the network slice instance determined by the NSMF and / or the orchestration engine. Additionally, the NSSF is configured to expose a REST API to enable provisioning of NSI configuration information updates from the NSMF. After receiving the updated network slice instance configuration information, the NSSF may be configured to begin utilizing the updated NSI information to answer network slice selection service request messages (e.g., Nnssf_NSSelection_Get service request messages).

[0055] The disclosure of each of the following references is incorporated herein by reference in its entirety to the extent not inconsistent with the present invention and to the extent the reference supplements, explains, provides background or teaches methods, techniques, and / or systems used herein. References 1. 3GPP TS 23.501; 3 rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 17), V17.1.0 (2021-03) 2. 3GPP TS 29.531; 3 rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Network Slice Selection Services; Stage 3 (Release 17), V17.1.0 (2021-03) 3. 3GPP TR 28.801; rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Study on management and orchestration of network slicing for Next Generation Network; (Release 15), V15.1.0 (2018-01) 4. 3GPP TS 28.531; 3 rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Management and Orchestration; Provisioning; (Release 16), V16.9.0 (2021-03) It will be understood that various details of the presently disclosed subject matter can be changed without departing from the scope of the presently disclosed subject matter. Further, the above description is by way of illustration only, and not by way of limitation.

Claims

1. A method for providing updated network slice information to a Network Slice Selection Function (NSSF), comprising: a Network Slice Management Function (NSMF) registering an NF profile corresponding to the NSMF with a Network Function (NF) Repository Function (NRF); the NSMF subscribing to the NRF for status updates corresponding to NF instances belonging to a network slice instance created by the NSMF; the NSMF receiving, from the NRF, a notification message including one or more network traffic load level updates related to at least one of the NF instances; processing the one or more network traffic load level updates to generate network slice instance configuration information for at least one of the network slice instances; the NSMF providing the network slice instance configuration information to an NSSF that manages the at least one of the network slice instances.

2. The method according to claim 1, wherein the network slice instance configuration information includes instructions for creating an additional network slice instance, instructions for modifying the network slice instance, or instructions for removing one or more of the network slice instances.

3. The method according to claim 1 or 2, wherein the network slice instance configuration information is provided to the NSSF via an update message pushed by the NSMF.

4. The method according to claim 1 or 2, wherein the NSSF is configured to request the network slice instance configuration information from the NSMF via a pull message.

5. The method according to claim 1 or 2, wherein the NSSF is configured to utilize the network slice instance configuration information to respond to a network slice selection service request message.

6. The method according to claim 1 or 2, wherein the network slice instance configuration information is provided to the NSSF in real time by the NSMF.

7. The method according to claim 1 or 2, wherein the NSMF is registered with the NRF as a custom NF.

8. A system for providing updated network slice information to a Network Slice Selection Function (NSSF), comprising a Network Slice Management Function (NSMF) including at least one processor and a memory, and an orchestration engine stored in the memory and implemented by the at least one processor, the orchestration engine registering an NF profile corresponding to the NSMF with a Network Function (NF) Repository Function (NRF), subscribing to the NRF for status updates corresponding to NF instances belonging to a network slice instance created by the NSMF, receiving from the NRF a notification message including one or more network traffic load level updates related to at least one of the NF instances, processing the one or more network traffic load level updates to generate network slice instance configuration information for at least one of the network slice instances, and providing the network slice instance configuration information to an NSSF that manages the at least one of the network slice instances.

9. The system according to claim 8, wherein the network slice instance configuration information includes instructions for creating an additional network slice instance, instructions for modifying the network slice instance, or instructions for removing one or more of the network slice instances.

10. The system according to claim 8 or 9, wherein the network slice instance configuration information is provided to the NSSF via an update message pushed by the NSMF.

11. The system according to claim 8 or 9, wherein the NSSF is configured to request the network slice instance configuration information from the NSMF via a pull message.

12. The system according to claim 8 or 9, wherein the NSSF is configured to utilize the network slice instance configuration information to respond to a network slice selection service request message.

13. The system according to claim 8 or 9, wherein the network slice instance configuration information is provided to the NSSF in real time by the NSMF.

14. The system according to claim 8 or 9, wherein the NSMF registers with the NRF as a custom NF.

15. A computer program storing executable instructions, which, when executed by a processor of a computer, control the computer to perform steps, the steps comprising: registering, by a network slice management function (NSMF), an NF profile corresponding to the NSMF with a network function (NF) repository function (NRF); subscribing, by the NSMF, to the NRF for status updates corresponding to NF instances belonging to a network slice instance created by the NSMF; receiving, by the NSMF, from the NRF, a notification message including one or more network traffic load level updates related to at least one of the NF instances; processing, by the NSMF, the one or more network traffic load level updates to generate network slice instance configuration information for at least one of the network slice instances; and providing, by the NSMF, the network slice instance configuration information to a network slice selection service function (NSSF) that manages the at least one of the network slice instances.

16. The computer program according to claim 15, wherein the network slice instance configuration information includes instructions for creating an additional network slice instance, instructions for modifying the network slice instance, or instructions for removing one or more of the network slice instances.

17. The computer program according to claim 15 or 16, wherein the network slice instance configuration information is provided to the NSSF via an update message pushed by the NSMF.

18. The computer program according to claim 15 or 16, wherein the NSSF is configured to request the network slice instance configuration information from the NSMF via a pull message.

19. The computer program according to claim 15 or 16, wherein the NSSF is configured to utilize the network slice instance configuration information to respond to a network slice selection service request message.

20. The computer program according to claim 15 or 16, wherein the network slice instance configuration information is provided to the NSSF in real time by the NSMF.

Images