A method, system, and computer-readable medium for providing updated network slice information to the 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] Claims of Priority This application claims the benefit of priority of U.S. Patent Application No. 17 / 382,299, filed on July 21, 2021, the disclosure of which is hereby incorporated by reference in its entirety.

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

Background Art

[0003] Background In a 5G telecommunications network, network nodes that provide services are called producer network functions (NFs). Network nodes that consume services are called consumer NFs. A network function can be both a producer NF and a consumer NF depending on whether it is consuming or providing a service.

[0004] A given Producer NF can have many service endpoints, which are combinations of Internet Protocol (IP) addresses and port numbers on the network node hosting the Producer NF. Producer NFs register with the Network Function Repository (NRF). The NRF maintains NF profiles of available NF instances and the services supported by each NF instance. Consumer NFs can subscribe to the NRF to receive information about the Producer NF instances they have registered with.

[0005] One example of a Network Function (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, connectivity management, reachability management, mobility management, and other services for UE devices. The AMF acts as a point of contact between the radio access network and the remaining nodes within the 5G core network. The AMF also serves as an access point for network slice services.

[0006] Network slicing is a service provided in 5G networks where network resources are logically allocated in parts 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 network functions that are arranged and configured to form and satisfy a specific set of network requirements or characteristics. For example, a network slice instance for access network services could be virtualized gnode B and AMF resources to provide access network services for the UE. A network slice instance for core network services could include a virtualized NRF and network exposure function (NEF) resources configured to provide core network services for the UE, such as IoT, digital call sessions, and similar applications. [Overview of the project] [Problems that the invention aims to solve]

[0007] In 5G telecommunications networks, there are scenarios where the AMF attempts to obtain network slice information from the NSSF. Specifically, the AMF requests network slice information from the NSSF when requesting the identity of the appropriate network slice instance in order to route call sessions for supported user equipment. One problem that exists is that the NSSF receives updated network slice instance status information from the NRF infrequently and statically. Therefore, the NSSF may frequently provision (or access) expired or inaccurate network slice instance information (for example, a supported network slice instance may recently encounter overload conditions without the NSSF's knowledge).

[0008] Therefore, considering these difficulties, there is a need for methods, systems, and computer-readable media for providing updated network slice information to the NSSF. [Means for solving the problem]

[0009] overview A method for providing updated network slice information to the Network Slice Selection Function (NSSF) includes the Network Slice Management Function (NSMF) registering an NF profile corresponding to the NSMF with the Network Function (NF) Repository Function (NRF), and the NSMF subscribing to the NRF for status updates corresponding to NF instances belonging to network slice instances created by the NSMF. The method further includes the NSMF receiving notification messages from the NRF that include one or more network traffic load level updates related to at least one of the NF instances, processing 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 the NSSF managing at least one of the network slice instances.

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

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

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

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

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

[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 memory. The system further includes an orchestration engine stored in memory and performed by at least one processor for registering NF profiles corresponding to the NSMF with an NRF; subscribing to the NRF for status updates corresponding to NF instances belonging to network slice instances created by the NSMF; receiving notification messages from the NRF including one or more network traffic load level updates related to at least one of the NF instances; processing 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 system described herein, network slice instance configuration information includes instructions for creating additional network slice instances, instructions for modifying network slice instances, or instructions for removing one or more network slice instances.

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

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

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

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

[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-temporary computer-readable medium having executable instructions stored on the non-temporary computer-readable medium, the executable instructions, when executed by the computer's processor, control the computer to perform a step. The step includes the 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 network slice instances created by the NSMF. The method includes the NSMF receiving an alert message from the NRF containing one or more network traffic load level updates related to at least one of the NF instances, processing 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 the NSSF managing at least one of the network slice instances.

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

[0025] The subject matter described in this specification will now be described with reference to the accompanying drawings.

Brief Description of the Drawings

[0026] [Figure 1] FIG. 1 is a network diagram showing an exemplary 5G network architecture according to an embodiment of the subject matter described in this specification. [Figure 2] FIG. 2 is a message flow diagram showing communication of network slice instance modification information according to an embodiment of the subject matter described in this specification. [Figure 3] FIG. 3 is a network slice instance architecture diagram according to an embodiment of the subject matter described in this specification. [Figure 4]This flowchart shows an exemplary process for establishing message priority in a network slice based on QoS parameters, according to embodiments of the subject matter described herein. [Modes for carrying out the invention]

[0027] Detailed explanation Figure 1 is a block diagram illustrating an exemplary 5G system network architecture. In Figure 1, the network includes an NRF 100 and a service communication proxy (SCP) 101. As described above, the NRF 100 maintains profiles of available producer NF service instances and their supported services, and can 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 for producer NFs. Furthermore, the SCP 101 can perform load balancing of connections between consumer NFs and producer NFs.

[0028] NRF100 is a repository for NF profiles. Consumer NFs or SCPs must obtain NF profiles from NRF100 in order to communicate with a Producer NF. NF profiles are JavaScript object notation (JSON) data structures. An NF profile definition includes at least one of the following: a fully qualified domain name (FQDN), an Internet Protocol (IP) version 4 (IPv4) address, or an IP version 6 (IPv6) address.

[0029] In Figure 1, any of the nodes (other than SCP101 and NRF100) can be either a consumer NF or a producer NF, depending on whether they consume or provide services. In the example shown, the node includes a policy control function (PCF) 102 that performs policy-related operations within 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 shown in Figure 1 further includes a session management function (SMF) 108 that manages the session between AMF110 and PCF102. AMF110 performs mobility and registration management operations similar to those performed by a mobility management entity (MME) in a 4G network. AMF110 also acts as an access point for network slice services. AMF110 can also perform AMF selection to select a service-providing AMF that will provide access to network slice services requested by the UE during registration.

[0030] The authentication server function (AUSF) 112 performs authentication services for user devices (UEs), such as UE 114, that request 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 seeking access to specific network functions. The NSSF 116 can obtain AMF loading information from the NRF and NSSAI availability information from the AMF. The NSSF 116 can store AMF loading information and NSSAI availability information in an AMF selection database maintained by the NSSF 116. When the NSSF 116 receives an NSSAI selection request from an AMF, it can use the stored AMF loading information and NSSAI availability information to calculate an AMF relevance score and weight for each AMF capable of supporting the network slice service requested by the UE seeking access to the network slice service. The NSSF 116 can generate a prioritized list of AMFs capable of providing the requested service and its corresponding weight, and communicate this list to the requesting AMF. The requesting AMF can then use the prioritized list and weights of AMFs to select an AMF to provide access to the requested network slice service.

[0032] The Network Exposure Function (NEF) 118 provides an application programming interface (API) for application functions that attempt to retrieve information about Internet of Things (IoT) devices and other UEs connected to the network. The NEF 118 performs a function similar to that of 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 radio link. The radio access network 120 can be accessed using g-node B (gNB) (not shown in Figure 1) or other radio access points. The user plane function (UPF) 122 can support various proxy functions for user plane services. One example of such a proxy function is the multipath transmission control protocol (MPTCP) proxy function. The UPF 122 can also support performance measurement functions that can be used by the UE 114 to obtain network performance measurements. Similarly, Figure 1 also shows a data network (DN) 124 through which the UE accesses data network services such as Internet services.

[0034] The Service Edge Protection Proxy (SEPP) 126 filters incoming traffic from another PLMN and performs topology concealment for traffic leaving the home PLMN. SEPP 126 can communicate with SEPPs within the external PLMN that manage security for the external PLMN. Therefore, traffic between NFs within different PLMNs can traverse a minimum of two SEPP functions, one for the home PLMN and the other for the external PLMN.

[0035] As described above, network slicing involves providing virtual network functions and allocating resources to those virtual network functions to meet given requirements. For example, network slicing may include virtualizing any of the network functions shown in Figure 1 and providing access to services performed by multiple different network functions as network slice instances.

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

[0037] Network slices as a service can be offered to a provider's customers by a telecommunications service provider. Network slice services can be characterized by a number of parameters, including wireless access technology, bandwidth, end-to-end latency, guaranteed / unguaranteed QoS, and security level.

[0038] In some embodiments, the disclosed subject matter establishes a mode of information exchange between the NSMF and the NSSF, where updates concerning network slice instances are directly pushed or provided to the NSSF in real time. For example, the NSSF may be enhanced to expose a representative state transfer (REST) ​​application programming interface (API) that can be used by the NSMF to send out network slice instance configuration information directing corrective changes to network slices. In particular, the disclosed subject matter makes available the automatic provisioning of updated network slice instance information in the NSSF based on network functionality and / or NF service network traffic load level feedback received from the NRF. Provisioning network slice information in this manner avoids and / or prevents intervention by network operators, in particular.

[0039] Currently, NSSF exposes the Nnssf_NSSelection_Get service operation, which enables network slice selection in both public land mobile networks (PLMNs) and home public land networks (HPLMNs). This service operation further enables NSSF to provide the AMF with authorized NSSAIs and configured NSSAIs for public land mobile networks (PLMNs). Using this service operation, NSSF can assign network slices to requesting user equipment during registration procedures, inter-PLMN mobility procedures, PDU session establishment procedures, UE configuration update procedures, and similar procedures. In response to receiving a network slice selection request message (e.g., via the Nnssf_NSSelection_Get service operation), NSSF selects a network slice instance based on pre-provisioned information. Furthermore, NSSF then determines and returns the appropriate NRFs (e.g., via the Nnssf_NSSelection_Get response message) 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 for the NSMF to interact directly with the NSSF for any updated configuration changes in a generated / supported network slice (e.g., NSI) as a result of management and orchestration. Furthermore, performance data collection typically involves a network slice subset management function (NSSMF) that collects performance data from NF services and network functions within 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 employs a more dynamic push-based system, as described below.

[0041] Figure 2 is a message flow diagram illustrating the communication of network slice instance modification information according to an embodiment of the subject matter described herein. As shown in Figure 2, 5G messaging can occur between NSMF212, NRF214, and NSSF216. In some embodiments, NSMF212 may include an orchestration engine 220 that provides a list of steps (or changes to steps) that are embodied in the state machine of NSMF212 (e.g., by software code programming or by a set of rules). As described herein, NSMF212 and / or the orchestration engine 220 may be configured to be responsible for collecting performance data at the NSSI level by creating measurement jobs regarding network functionality within the NSSI. NSMF212 may also be responsible for generating performance data at the network slice interface level, which may include network traffic load data for all network slice instances, indicating the total user traffic level and / or total signaling traffic level present within the network slice instance. Performance data generated at the network slice interface level may also include service performance data provided by the network slice instance. In some embodiments, service performance data includes total user traffic data, signaling traffic data, and quality of service data corresponding to a specific service instance (for example, service QoS data may indicate whether the network slice instance is delivering the service at the expected QoS level). Furthermore, NSSF212 may be configured to manage and orchestrate network slice instances based on performance data and service performance data, and to provide performance feedback to the operator along with snapshots of network slice instances for updates in NSSF216 (for example, used by 5G NF). As an illustration, Figure 3 shows a network slice instance architecture diagram according to an embodiment of the subject matter described herein.For example, system 300 is generated / created by NSSF304, NSMF302, and NSMF312, and includes network slice instances 301-303 (e.g., NSI-X, NSI-Y, and NSI-Z) supported by NSMF312. Although only three network slice instances are shown in Figure 3, any number of network slice instances may be supported by NSMF312 and / or NSSF316 without deviating from the scope of the disclosed subject matter. Furthermore, as shown in Figure 3, each of network slice instances 301-303 includes multiple network slice subnet instances. For example, network slice instance 301 includes network slice subset instances 311-312. Furthermore, each of the network slice subset instances 311-332 shown in Figure 3 includes one or more underlying network functions and / or NF services. The communication links connecting NSMF302 and network slice subset instances 311-332 can help facilitate performance feedback from network slice instances and / or network slice instance level updates based on policies. For example, NSMF302 orchestrates the management of various network slices by utilizing the communication links to collect performance and / or metric information about network slice instances, network slice subset instances, and underlying network functionality. Similarly, the communication links connecting NSMF302 and NSSF304 can be used to communicate network slice instance level policies and thresholds without requiring an operator or system administrator. Furthermore, performance feedback can also be used by NSMF302 to push network slice instance updates to NSSF316 in the manner described below (e.g., method 400 in Figure 4).

[0042] Returning to Figure 2, NSSF216 and / or orchestration engine 220 are configured to register their network function profiles with NRF214. Specifically, NSSF216 sends an NF profile registration message 201 containing the services provided by NSSF216 to NRF214. As shown above, NSSF216 is responsible for maintaining network slice instance information for network slices supported by NSSF, along with the associated network slice instance identifier (e.g., NSI-ID). After receiving registration message 201, NRF214 registers NSSF216's NF profile and its associated services and records them in the local registry. In a similar manner, NSMF212 similarly registers its NF profile and the services it provides with NRF214. As shown in Figure 2, NSMF212 sends an NF profile registration message 202 containing its NF profile and the services it provides. In particular, registration message 202 further specifies NSMF212 as a custom network function (i.e., a "CUSTOM NF" identifier) ​​for NRF214.

[0043] After registering as a custom network function, NSMF212 and / or orchestration engine 220 may be configured to subscribe to NRF214 to receive status update information (e.g., NF network traffic load level information / updates / changes) from the specified NF. In particular, NSMF212 and / or orchestration engine 220 send subscription request messages 203 to request and receive network traffic load levels for network functions (and associated NF services) instantiated and / or belonging to network slice instances created by NSMF212. For example, NSMF212 subscribes to NRF214 to request capacity and performance metric data for network functions registered with NRF214. In particular, this information includes changes in traffic load levels for all network functions running in network slice instances managed by NSMF216.

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

[0045] In block 205, NSMF212 and / or orchestration engine 220 are configured to process network traffic load levels and apply local policies to the network slice instance layer. In some embodiments, NSMF212 and / or orchestration engine 220 may be provisioned or configured with local policies targeting the orchestration and management of network slices. In particular, NSMF212 and / or orchestration engine 220 may be provisioned with policies that can 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 mitigated. For example, NSMF212 and / or orchestration engine 220 may be configured to process changes in the traffic load levels of a network function when notified by NRF214. NSMF212 may also leverage 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 is required for a network slice instance(s). For example, if a change in network traffic load level experienced by a network function exceeds a predetermined threshold defined by a policy, NSMF212 and / or the orchestration engine 220 may be configured to modify the characteristics of the underlying network slice instance (e.g., by adjusting / increasing additional network resources for the network slice, such as compute, RAM, and storage). In response to determining that the network slice instance and / or network function needs to be modified, NSMF212 and / or the orchestration engine 220 may use local policies to generate network slice instance configuration data, including an updated NSI configuration, which can then be used by NSSF216 for enforcement.In some embodiments, network slice management tasks may include, but are not limited to, creating network slice instances, updating network slice instances, deleting network slice instances, and / or similar actions. In some embodiments, this information may be entirely based on the PLMN, because network slices supported beyond the PLMN may indicate that the NRF and NSMF212 may need to interact, even if they exist outside the per-view of the NSMF212.

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

[0047] In response to receiving network slice instance configuration information, the NSSF216 may be configured to perform network slice modifications for its supported consumer NFs (i.e., within the NSSF216). For example, the NSSF216 can use the NSI configuration information to modify the characteristics of a particular network slice instance. Furthermore, the NSSF216 can immediately begin using the received configuration information to respond to 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, NSSF216 may be configured to pull or request network slice instance configuration information from NSMF212. For example, NSSF216 can send NSI configuration information request messages to NSMF212 via a REST API. In such a scenario, NSSF216 can first subscribe to NSMF212 to establish permission to request updated NSI configuration information stored in NSMF212.

[0049] Figure 4 is a flowchart illustrating an exemplary process or method 400 for providing updated network slice information to the NSMF according to embodiments of the subject matter described herein. In some embodiments, the method 400 shown in Figure 4 is a memory-stored algorithm, program, or script (e.g., the orchestration engine 220 shown in Figure 2) that, when executed by a processor, performs the steps described in blocks 402-410. In some embodiments, the orchestration engine provides a list (or modification of steps) of steps that are embodied in the state machine of the NSMF (e.g., by software code programming or by a set of rules).

[0050] In block 402, the NF profile corresponding to NSMF is registered with the NRF. More specifically, NSMF registers its NF profile (including NSMF services) with the NRF. The registration message specifically indicates NSMF as a custom NF. As shown above, NSMF does not normally register with the NRF because NSMF is typically configured to handle network slice orchestration duty according to the 3GPP standard. It should also be noted that NSMF(s) supported by NSMF similarly register (or have registered) their NF profiles with the NRF according to 3GPP TS29.510.

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

[0052] In block 406, an alert message is received containing one or more network traffic load level changes occurring in the NF instance. In some embodiments, the NSMF receives network traffic load level change alerts from the NFF. In particular, by subscribing to the NFR, the NSMF receives NF network traffic load level update information from the NRF when supported network functions (e.g., NFs in network slice instances created by the NSMF) experience changes in their traffic target levels. Specifically, network functions in various network slice instances are configured to report their network traffic load level changes to the NRF (the NRF then reports the changes to the subscribed NSMF).

[0053] In block 408, 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, NSMF is configured and / or provisioned with local policies that can be used by the orchestration engine to orchestrate an existing set of network functional resources to be allocated to different network slice instance responses by NSMF. When NSMF receives notification of a traffic load level change, it is configured to orchestrate network slice update information to address the traffic load level change for supported network slice instances. For example, NSMF may perform post-processing steps to add more resources to a network slice instance experiencing an overload condition.

[0054] In block 410, network slice instance configuration information is provided to the NSSF. In some embodiments, the NSSF sends (i.e., "pushes") 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 NSSF and / or the orchestration engine. Furthermore, the NSSF is configured to expose a REST API to enable provisioning of NSI configuration information updates from the NSSF. After receiving the updated network slice instance configuration information, the NSSF may be configured to begin utilizing the updated NSI information to respond to network slice selection service request messages (e.g., Nnssf_NSSelection_Get service request messages).

[0055] Each of the following references is incorporated herein by reference, to the extent that it does not conflict with the present invention, and to the extent that it complements, explains, provides or teaches the 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; 3 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 subject matter disclosed at this time may be changed without deviating from the scope of the subject matter disclosed at this time. Furthermore, the above explanation is for illustrative purposes only and not for limitation.

Claims

1. A method for providing updated network slice information to the Network Slice Selection Function (NSSF), The Network Slice Management Function (NSMF) registers an NF profile corresponding to the NSMF in the Network Function (NF) Repository Function (NRF), The NSMF subscribes to the NRF for status updates corresponding to NF instances belonging to network slice instances created by the NSMF, The NSMF receives notification messages from the NRF that include one or more network traffic load level updates related to at least one of the NF instances, To generate network slice instance configuration information for at least one of the aforementioned network slice instances, the process involves updating one or more network traffic load levels. A method comprising the NSMF providing the network slice instance configuration information to the NSSF managing 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 additional network slice instances, instructions for modifying the network slice instances, 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 update messages 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 pull messages.

5. The method according to claim 1 or 2, wherein the NSSF is configured to utilize the network slice instance configuration information in order 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 as a custom NF in the NRF.

8. A system for providing updated network slice information to the Network Slice Selection Function (NSSF), A network slice management function (NSMF) including at least one processor and memory, A system comprising: an orchestration engine stored in the memory and performed by the at least one processor, wherein the orchestration engine is for registering NF profiles 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 network slice instances created by the NSMF; receiving notification messages from the NRF 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 in order 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 the NSSF managing 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 additional network slice instances, instructions for modifying the network slice instances, 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 update messages 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 pull messages.

12. The system according to claim 8 or 9, wherein the NSSF is configured to utilize the network slice instance configuration information in order 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 is registered in the NRF as a custom NF.

15. A computer program storing executable instructions, wherein the instructions control the computer to perform steps when executed by the computer's processor, and the steps are: The Network Slice Management Function (NSMF) registers an NF profile corresponding to the NSMF in the Network Function (NF) Repository Function (NRF), The NSMF subscribes to the NRF for status updates corresponding to NF instances belonging to network slice instances created by the NSMF, The NSMF receives notification messages from the NRF that include one or more network traffic load level updates related to at least one of the NF instances, To generate network slice instance configuration information for at least one of the aforementioned network slice instances, the process involves updating one or more network traffic load levels. A computer program comprising the NSMF providing the network slice instance configuration information to the NSSF managing 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 additional network slice instances, instructions for modifying the network slice instances, 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 update messages 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 pull messages.

19. The computer program according to claim 15 or 16, wherein the NSSF is configured to utilize the network slice instance configuration information in response 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