Methods, systems, and computer-readable media for providing network slice management using a feedback mechanism

Abstract

A method for feedback-based network slice management includes steps performed at a network slice management function (NSMF) including at least one processor. The steps include subscribing directly to a network data analysis function (NWDAF) of the NSMF to create a subscription to be notified of network slice load information, and as part of the subscription, specifying network slice load information report generation criteria defined by the NSMF. The steps further include receiving network slice load information directly from the NWDAF via the NWDAF subscription interface of the NSMF and in response to meeting the network slice load information report triggering criteria defined by the NSMF. The steps further include determining, based on the network slice load information, that a change in network slice resource allocation is required. The steps further include dynamically changing the network slice resource allocation during the operation of the network slice in response to determining that a change in network slice resource allocation is required.

Description

[0001] Priority declaration

[0002] This application claims priority to U.S. Patent Application No. 16 / 712,973, filed on December 12, 2019, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] The subject matter described herein relates to network slicing. More specifically, the subject matter described herein relates to methods, systems, and computer-readable media for network slice management using a feedback mechanism. Background Art

[0004] In 5G telecommunication networks, a network node that provides services is called a producer network function (NF). A network node that consumes services is called a consumer NF. A network function can be both a producer NF and a consumer NF, depending on whether it is consuming services or providing services.

[0005] A given producer NF can have many service endpoints, where a service endpoint is a combination of an IP address and a port number on the network node hosting the producer NF. Producer NFs register with the Network Function Repository Function (NRF). NRF maintains NF profiles of available NF instances and their supported services. Consumer NFs can subscribe to receive information about producer NF instances that have registered with NRF.

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

[0007] Network slicing is a service provided in a 5G network where network resources are logically allocated into portions or slices for use by UE devices. Each network slice can provide specific capabilities or services to the UE. A network slice instance is defined as a set of network functions and resources for these 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 may be the resources of a virtualized g-Node B and AMF that provide access network services to the UE. A network slice instance for a core network service may include resources of a virtualized NRF and a network exposure function (NEF), which is configured to provide core network services to UEs such as Internet of Things (IoT) devices.

[0008] The 3rd Generation Partnership Project (3GPP) defines service orchestration processes for the creation and modification of network slices. However, these processes do not include feedback mechanisms to optimize the utilization of network slice components after they are created. For example, 3GPP TR 28.801 defines a network slice instance (NSI) lifecycle that includes slice creation, modification, and decommissioning. However, post-creation slice modifications are performed based on input from service consumers, rather than performance feedback on slice utilization or capacity.

[0009] Thus, there are methods, systems, and computer-readable media for network slice management using a feedback mechanism. Summary of the invention

[0010] A method for feedback-based network slice management includes steps performed at a network slice management function (NSMF) including at least one processor. The steps include subscribing directly to a network data analysis function (NWDAF) of the NSMF to create a subscription to be notified of network slice load information, and as part of the subscription, specifying network slice load information report generation criteria defined by the NSMF. The steps further include receiving network slice load information directly from the NWDAF via the NWDAF subscription interface of the NSMF and in response to meeting the network slice load information report triggering criteria defined by the NSMF. The steps further include determining, based on the network slice load information, that a change in network slice resource allocation is required. The steps further include dynamically changing the network slice resource allocation during the operation of the network slice in response to determining that a change in network slice resource allocation is required.

[0011] According to another aspect of the subject matter described herein, subscribing directly to the NWDAF includes sending an Eventsubscription_Subscribe message from the NSMF to the NWDAF, wherein the Eventsubscription_Subscribe message includes an event type, data selection, and trigger parameters, and the trigger parameters are used to define a network slice load event that triggers reporting of network slice load information to the NSMF.

[0012] According to yet another aspect of the subject matter described herein, the triggering parameters include parameters based on service level agreement (SLA) criteria.

[0013] According to yet another aspect of the subject matter described herein, receiving network slice load information includes receiving real-time load information indicating utilization of the network slice after the network slice is created, independent of monitoring by a network slice service consumer.

[0014] According to another aspect of the subject matter described herein, determining that a change in network slice resource allocation is required includes comparing network slice load information with a threshold defined by an operator, and if the network slice load level indicated by the network slice load information exceeds the threshold, determining that a change in network slice resource allocation is required.

[0015] According to another aspect of the subject matter described herein, dynamically updating network slice resource allocation includes generating a network slice subnet instance change request, and sending the network slice subnet instance change request to a network slice subnet management function (NSSMF) to implement the change in network slice resource allocation.

[0016] According to another aspect of the subject matter described herein, a method for providing real-time feedback for network slice management is provided. The method includes steps performed at a network data analysis function (NWDAF) including at least one processor. The steps include receiving a message and NSMF-defined criteria directly from a network slice management function (NSMF) via an NWDAF subscription interface of the NSMF, wherein the message is used to create a subscription to be notified of real-time, created network slice load information, and the NSMF-defined criteria are used to trigger the reporting of network slice load information. The steps further include creating a subscription. The steps further include checking the NSMF-defined criteria defined for the subscription definition for the load information received from the network function (NF) providing the network slice service. The steps further include determining that the NSMF-defined criteria associated with one of the subscriptions are met. The steps further include transmitting the load information directly to the NSMF in response to determining that the NSMF-defined criteria associated with one of the subscriptions are met.

[0017] According to another aspect of the subject matter described herein, receiving a message from the NSMF includes receiving an Eventsubscription_Subscribe message, wherein the Eventsubscription_Subscribe message includes an event type, data selection, and a trigger parameter, and the trigger parameter is used to define a network slice load event that triggers reporting of network slice load information to the NSMF.

[0018] According to yet another aspect of the subject matter described herein, creating a subscription includes creating an entry in a network slice analysis and subscription management database.

[0019] According to another aspect of the subject matter described herein, checking the criteria defined by the NSMF includes accessing an entry in a network slice analysis and subscription management database and determining whether the network slice load information reporting trigger criteria associated with the entry have been met.

[0020] According to another aspect of the subject matter described herein, transmitting the network slice load information directly to the NSMF includes sending an Eventsubscription_Notify message to the NSMF, wherein the Eventsubscription_Notify message includes the network slice load information.

[0021] According to another aspect of the subject matter described herein, a system for feedback-based network slice management is provided. The system includes a network slice management function (NSMF) including at least one processor. The system further includes a network data analysis function (NWDAF) subscription interface implemented by at least one processor, and the NWDAF subscription interface is used to: subscribe directly to the NWDAF to create a subscription to be notified of network slice load information, and as part of the subscription, specify the network slice load information report generation criteria defined by the NSMF; receive network slice load information directly from the NWDAF via the NWDAF subscription interface of the NSMF and in response to meeting the network slice load information report triggering criteria defined by the NSMF. The system further includes a network slice resource manager implemented by at least one processor, and the network slice resource manager is used to: determine the need for a change in network slice resource allocation based on the network slice load information; and in response to determining that a change in network slice resource allocation is required, dynamically change the network slice resource allocation during the operation of the network slice.

[0022] According to another aspect of the subject matter described herein, the NWDAF subscription interface is configured to subscribe directly to the NWDAF by sending an Eventsubscription_Subscribe message from the NSMF to the NWDAF, wherein the Eventsubscription_Subscribe message includes an event type, data selection, and trigger parameters, and the trigger parameters are used to define a network slice load event that triggers reporting of network slice load information to the NSMF.

[0023] According to yet another aspect of the subject matter described herein, the NWDAF subscription interface is configured to receive real-time load information indicating utilization of the network slice after the network slice is created, independent of monitoring by a network slice service consumer.

[0024] According to another aspect of the subject matter described herein, the network slice resource manager is configured to determine the need for a change in network slice resource allocation by comparing network slice load information with an operator-defined threshold, and determining that a change in network slice resource allocation is needed if the network slice load level indicated by the network slice load information exceeds the threshold.

[0025] According to another aspect of the subject matter described herein, the network slice resource manager is configured to dynamically update the network slice resource allocation by generating a network slice subnet instance change request and sending the network slice subnet instance change request to a network slice subnet management function (NSSMF) to implement the change in the network slice resource allocation.

[0026] According to another aspect of the subject matter described herein, a system for providing real-time feedback for network slice management is provided. The system includes a network data analysis function (NWDAF) including at least one processor. The system further includes a network slice load information subscription manager, the network slice load information subscription manager is used to: receive messages and NSMF-defined criteria directly from the network slice management function (NSMF) via the NWDAF subscription interface of the NSMF, the message is used to create a subscription to be notified of real-time, created network slice load information, and the NSMF-defined criteria are used to trigger the reporting of network slice load information; and create a subscription. The system further includes a network slice load information analysis engine, the network slice load information analysis engine is used to: for load information received from a network function (NF) providing a network slice service, check the NSMF-defined criteria defined for the subscription definition; determine that the NSMF-defined criteria associated with one of the subscriptions are met; and in response to determining that the NSMF-defined criteria associated with one of the subscriptions are met, transmit the load information directly to the NSMF.

[0027] According to another aspect of the subject matter described herein, the network slice load information subscription manager is configured to receive an Eventsubscription_Subscribe message, wherein the Eventsubscription_Subscribe message includes an event type, data selection, and trigger parameters, and the trigger parameters are used to define a network slice load event that triggers reporting of network slice load information to the NSMF.

[0028] According to yet another aspect of the subject matter described herein, the network slice load information subscription manager creates a subscription by creating an entry in a network slice analysis and subscription management database.

[0029] According to another aspect of the subject matter described herein, the network slice load information analysis function is configured to check the criteria defined by the NSMF by accessing an entry in a network slice analysis and subscription management database and determining whether the network slice load information reporting trigger criteria associated with the entry have been met.

[0030] According to another aspect of the subject matter described herein, the network slice data load information analysis engine is configured to transmit the network slice load information directly to the NSMF by sending an Eventsubscription_Notify message to the NSMF, wherein the Eventsubscription_Notify message includes the network slice load information.

[0031] According to another aspect of the subject matter described herein, there is provided a non-transitory computer-readable medium storing executable instructions, which, when executed by a processor of a computer, control the computer to perform steps. The steps include subscribing directly to a network data analysis function (NWDAF) subscription interface of a network slice management function (NSMF) to create a subscription to be notified of network slice load information, and as part of the subscription, specifying network slice load information report generation criteria defined by the NSMF. The steps further include receiving network slice load information directly from the NWDAF via the NWDAF subscription interface of the NSMF and in response to meeting the network slice load information report triggering criteria defined by the NSMF. The steps further include determining, based on the network slice load information, that a change in network slice resource allocation is required. The steps further include dynamically changing the network slice resource allocation during the operation of the network slice in response to determining that a change in network slice resource allocation is required.

[0032] According to another aspect of the subject matter described herein, there is provided a non-transitory computer-readable medium storing executable instructions, which, when executed by a processor of a computer, controls the computer to perform steps. The steps include receiving a message and NSMF-defined criteria directly from a network slice management function (NSMF) via a network data analysis function (NWDAF) subscription interface of the NSMF, wherein the message is used to create a subscription that is notified of real-time, created network slice load information, and the NSMF-defined criteria are used to trigger the reporting of network slice load information. The steps further include creating a subscription. The steps further include checking the NSMF-defined criteria defined for the subscription definition for the load information received from the network function (NF) providing the network slicing service. The steps further include determining that the NSMF-defined criteria associated with one of the subscriptions are met. The steps further include transmitting the load information directly to the NSMF in response to determining that the NSMF-defined criteria associated with one of the subscriptions are met.

[0033] The subject matter described herein may be implemented in hardware, software, firmware, or any combination thereof. As such, the terms "function," "node," or "module" as used herein refer to hardware, which may also include software and / or firmware components for implementing the features being described. In an exemplary implementation, the subject matter described herein may be implemented using a computer-readable medium having computer-executable instructions stored thereon, which control the computer to perform steps when executed by a processor of a computer. 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. In addition, the computer-readable medium implementing the subject matter described herein may be placed on a single device or computing platform, or may be distributed on multiple devices or computing platforms. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] The subject matter described herein will now be described with reference to the accompanying drawings:

[0035] Figure 1 is a network diagram illustrating an exemplary 5G network architecture;

[0036] Figure 2 is a network diagram illustrating exemplary relationships between network communication services, core network resources, access network resources, network slice instances, and network slice subnet instances;

[0037] Figure 3 is a network diagram illustrating exemplary relationships between network slice instances, network slice subnet instances, and network functions;

[0038] Figure 4 is a network diagram illustrating an exemplary management structure for communication services, network slices, and network slice subnets;

[0039] Figure 5 is a message flow diagram illustrating exemplary messaging initiated by a network slice service consumer for checking the feasibility of provisioning resources for a network slice;

[0040] Figure 6 is a message flow diagram illustrating exemplary messaging exchanged between a network slice management function, a network data analysis function, and a network slice subnet management function in obtaining feedback regarding network slice utilization and using the feedback to modify a network slice subnet instance;

[0041] Figure 7 is a message flow diagram illustrating exemplary messaging exchanged between a network slice management function and a network data analysis function in obtaining feedback information regarding utilization of a network slice;

[0042] Figure 8 is a block diagram illustrating exemplary network slice management functionality and network data analysis functionality suitable for dynamically monitoring network slice resource utilization and modifying network slice resource allocation based on network slice utilization information;

[0043] Fig. 9 is a flow chart illustrating an exemplary process for network slice management using a feedback mechanism; and

[0044] Fig.10 is a flowchart illustrating exemplary steps performed by the NWDAF in providing network slice utilization feedback to the NSMF. DETAILED DESCRIPTION

[0045] Figure 1 is a block diagram illustrating an exemplary 5G network architecture. Figure 1 In the embodiment, the network includes NRF 100 and service communication agent (SCP) 101. As described above, NRF 100 can maintain the profile of available producer NF service instances and their supported services, and allow consumer NF or SCP to subscribe and be notified of the registration of new / updated producer NF service instances. SCP 101 can also support the discovery and selection of producer NF. In addition, SCP 101 can perform load balancing of connections between consumer NF and producer NF.

[0046] NRF 100 is a repository of NF profiles. In order to communicate with producer NF, consumer NF or SCP must obtain NF profile from NRF 100. NF profile is a JavaScript Object Notation (JSON) data structure. NF profile definition includes at least one of the following: fully qualified domain name (FQDN), Internet Protocol (IP) version 4 (IPv4) address or IP version 6 (IPv6) address.

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

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

[0049] 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 capabilities. NSSF 116 can obtain AMF loading information from NRF and obtain NSSAI availability information from AMF. NSSF 116 can store AMF loading information and NSSAI availability information in the AMF selection database maintained by NSSF 116. When NSSF 116 receives an NSSAI selection request from AMF, NSSF 116 can use the stored AMF loading information and NSSAI availability information to calculate the AMF relevance score and the weight of each AMF that can support the network slice service requested by the UE seeking access network slice service. NSSF 116 can generate a priority table and corresponding weights of AMFs that can provide the requested service, and transmit the table to the requesting AMF. The requesting AMF can then use the priority table and weights of the AMF to select an AMF for providing access to the requested network slice service.

[0050] The Network Exposure Function (NEF) 118 provides an Application Programming Interface (API) for application functions seeking to obtain information about Internet of Things (IoT) devices and other UEs attached to the network. The NEF 118 performs functions similar to the Service Capability Exposure Function (SCEF) in 4G networks.

[0051] Radio access network (RAN) 120 connects UE 114 to the network via wireless links. Radio access network 120 can be connected to the network by using g-Node B (gNB) (in Figure 1 The UE 114 may access the wireless network through a wireless access point (not shown) or other wireless access point. The user plane function (UPF) 122 may support various proxy functionalities for user plane services. An example of such proxy functionality is multi-path transport control protocol (MPTCP) proxy functionality. The UPF 122 may also support performance measurement functionality, which the UE 114 may use to obtain network performance measurements. Figure 1 Also illustrated in FIG. 1 is a data network (DN) 124 through which the UE accesses data network services, such as Internet services.

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

[0053] As indicated above, network slicing involves providing virtual network functions and allocating resources to the virtual network functions to meet given requirements. Figure 1 The network functions shown are virtualized and provide access to services implemented by multiple different network functions as a network slice instance.

[0054] At the highest level, a network slice is accessible via communication services provided by a communication service provider. Communication services may include business-to-consumer communication services, such as mobile web browsing, voice over LTE calls, and rich communication services. Communication services may also include business-to-business services, such as Internet access and local area network (LAN) interconnection.

[0055] Network slicing as a service can be provided by communications service providers to their consumers. Network slicing services can be characterized by several parameters, including:

[0056] Radio access technology;

[0057] bandwidth;

[0058] End-to-end delay;

[0059] Guaranteed / non-guaranteed QoS;

[0060] Security level, etc.

[0061] Figure 2 An example is provided to illustrate the relationship between a communication service, a network slice instance (NSI), a network slice subnet instance (NSSI), a core network (CN), and an access network (AN). Figure 2, the communication service 200 provided by the service provider includes service 1 202, service 2 204, and service 3 206. Service 1 202, service 2 204, and service 3 206 are each implemented using a network slice instance consisting of virtual NF resources in the core network 208 and the access network 210. In the illustrated example, service 1 202 is implemented using network slice instance A 212. Network slice instance A 212 is implemented using core network NSSI 1 212A and access network NSSI 1 212B. Service 2 204 is implemented using network slice instance B 214. Network slice instance B 214 is implemented using core network NSSI 2 214A and access network NSSI 2 214B. Service 3 206 is implemented using network slice instance C 216. Network slice instance C 216 is implemented using core network NSSI 3 216A and access network NSSI 2 214B. It should be noted that access network NSSI 2 214B is shared by network slice instances 214 and 216.

[0062] Figure 3 is a network diagram illustrating exemplary relationships between network slice instances, network slice subnet instances, and network functions. Figure 3 , a network slice instance X 300 and a network slice instance Y 302 are illustrated. The network slice instance X 300 includes a network slice subnet instance A 304 and a network slice subnet instance C 306. The network slice instance Y 302 includes a network slice subnet instance B 308 and a network slice subnet instance A 304 shared with the network slice instance Y 302. The network slice subnet instance A 304 includes NFs NF1-NF4. The network slice subnet instance C 306 includes NFs NF5 and NF6. The network slice subnet instance C 306 includes NFs NF7-NF9. Therefore, Figure 3 The idea of ​​sharing network slice subnet instances and corresponding NF resources between network slice instances is further illustrated.

[0063] To manage communication services, network slice instances and network slice subnet instances, 3GPP TR 28.801 defines three management functions, the Communication Service Management Function (CSMF), the Network Slice Management Function (NSMF) and the Network Slice Subnet Management Function (NSSMF). Figure 4 These functions are illustrated in Figure 4In the present invention, CSMF 400 is the highest level node in the management hierarchy and is responsible for translating communication service related requirements into network slice related requirements and communicating with NSMF 402. NSMF 402 is the next level node in the hierarchy and is responsible for the management and orchestration of network slice instances. NSMF 402 also derives network slice subnet related requirements from network slice related requirements. NSMF 402 communicates with CSMF 400 and NSSMF 404. The lowest level node in the management hierarchy is NSSMF 404. NSSMF 404 is responsible for the management and orchestration of network slice subnet instances. NSSMF 404 communicates with NSMF 402 and communicates with the NFs that implement the network slice subnet instances.

[0064] 3GPP TS 28.531 defines the procedures for network slicing service consumers to request the creation, deletion, and checking of the feasibility of network slice instances and network slice subnet instances. Figure 5 The process of defining a network slice feasibility check for a network slice management service provider is illustrated in FIG. Figure 5 In line 1, the network slice subnet management service provider (NSSMS_Provider) 500 receives a request to allocate NSSI (e.g., AllocateNssi request or ModifyNssi request) and network slice subnet related requirements (e.g., area information, user number, traffic demand, QoS quality, whether the requested network slice instance can be shared) from the network slice subnet management service consumer (NSSMS_Consumer) 502. The request is evaluated and the initial resources to be allocated are identified. NSSMS_Provider 500 can be NSMF 402, and NSSMS_Consumer 502 can be the above-mentioned Figure 4 CSMF 400 described.

[0065] exist Figure 5 In line 2 of the message flow diagram in FIG. 5 , NSSMS_Provider 500 may optionally request information and updates about resources from Other_MS_Provider 504. Other_MS_Provider 504 may be a NSMF in another network.

[0066] In line 3 of the message flow diagram, NSSMS_Provider 500 sends a subscription request to Other_MS_Provider 504, e.g., Management and Orchestration (MANO), TN Manager. NSSMS_Provider 500 receives a response with information about the subscribed resources (e.g., their availability, identification information of the subscribed resources, etc.).

[0067] In line 4 of the message flow diagram, NSSMS_Provider 500 evaluates the response to determine whether the network slice subnet requirements can be met.

[0068] If the allocation of network resources is determined to be feasible, NSSMS_Provider 500 executes lines 5a and 5b of the message flow diagram. In line 5a, NSSMS_Provider 500 determines that it is ready to allocate the required network slice resources. In line 5b of the message flow diagram, NSSMS_Provider 500 optionally sends a feasibility response (Acknowledgement) message to NSSMS_Consumer 502 indicating that the requested resources are available.

[0069] If NSSMS_Provider 500 determines that the requested resource allocation is not feasible, lines 6a-6c of the message flow diagram are executed. In line 6a, NSSMS_Provider 500 cancels the reservation and can optionally receive a reply. In line 6b, NSSMS_Provider500 determines that it is not ready to allocate the requested network slice resources. In line 6c, NSSMS_Provider 500 optionally sends a negative reply to NSSMS_Consumer502 regarding the result of the reservation check.

[0070] therefore, Figure 5 The illustration illustrates a network slice consumer driven feasibility check of network slice resources. These steps are initiated by the network slice consumer and are performed before the network slice resources are allocated. What is required is a process driven by the network slice management function, independent of monitoring requests from network slice consumers to monitor and modify network slice and network slice subnet resources.

[0071] Figure 6 is a diagram illustrating a process performed by the NSMF to obtain network slice load information from a network data analysis function (NWDAF) dynamically and independently of a network slice service consumer (i.e., without receiving a monitoring request from a network slice service consumer) during operation of the network slice instance after the network slice instance is created. Figure 6In line 1 of the message flow diagram, NSMF 402 sends an Eventsubscription_Subscribe / Unsubscribe message to NWDAF. In this example, it is assumed that the message is an Eventsubscription_Subscribe message. The Eventsubscription_Subscribe message is used by NSMF 402 to subscribe to receive information about the real-time, instantaneous load level of the network slice. Figure 7 Exemplary parameters that may be included in the event subscription message are described in more detail. NWDAF 600 is an analysis function defined in 3GPP TS 29.520 that collects information about utilization of network functions and provides a subscription service for other nodes to be informed of the information it collects.

[0072] In line 2 of the message flow diagram, assuming that the network slice load information reporting condition(s) associated with the Eventsubscription_Subscribe message is met, the NWDAF 600 sends an Eventsubscription_Notify message to the NSMF 402. The Eventsubscription_Notify message includes network slice related parameters, such as load information parameters about the status of the network slice.

[0073] In line 3 of the message flow diagram, NSMF 402 sends an NSSI modification request message to NSSMF 404 to modify the network slice subnet instance based on the load information received from NWDAF 600. For example, if the Eventsubscription_Notify message indicates that the network slice is 80% loaded, the NSSI modification request may request that additional computing resources be allocated to the network slice subnet instances that constitute the network slice. Figure 6 In the present invention, network slice characteristics are dynamically monitored and resource allocations are changed without requiring messages from network slice service consumers. Because the resources associated with the network slice are updated dynamically and transparently to the network slice service consumer, any degradation in service quality will not be visible to the consumer and no consumer-driven resource monitoring or updates need to be performed to maintain service quality.

[0074] Figure 7 The subscription and event notification processing between NSMF and NWDAF is illustrated in more detail. Figure 7, in line 1 of the message flow diagram, NSMF 402 sends an Eventsubscription_Subscribe message to NWDAF 600. The Eventsubscription_Subscribe message registers NSMF 402 to receive load information about the network slice instance identified in the Eventsubscription_Subscribe message from NWDAF 600. A network slice or multiple network slices may be identified by a single network slice identifier (one or more), a group network slice identifier, or a parameter identifying all slices monitored by NWDAF 600. Other parameters that NSMF may specify in the Eventsubscription_Subscribe message include data analysis parameters that are input to the analysis engine of NWDAF 600 to determine the triggering conditions that control dynamic network slice event reporting and the content of the report to NSMF 402. Examples of data analysis parameters that may be included in the Eventsubscription_Subscribe message include:

[0075] Event Type {Location, Time of Day, Day of Week}

[0076] Data selection criteria {#samples, #intervals, #both}

[0077] samples {integer: #samples – maximum number of samples for example

[0078] To allow monthly}

[0079] interval{integer:value, e.g. hours, days, weeks}

[0080] Trigger Details

[0081] Type – Periodic / Threshold

[0082] Value – value for the time interval / load threshold

[0083] Notification URI – The URI to which notification messages will be sent.

[0084] Therefore, the above parameters that can be included in the Eventsubscription_Subscribe message enable NSMF402 to obtain load information about a network slice or a group of network slices and define the conditions for generating a network slice load information report.

[0085] In line 2 of the message flow diagram, in response to the Eventsubscription_Subscribe message and the satisfaction of one or more report trigger conditions defined in the message, the NWDAF 600 generates an Eventsubscription_Notify message and sends the message to the NSMF 402. The Eventsubscription_Notify message may include the following parameters:

[0086] - real-time load information (mandatory) integer 0..100

[0087] -Analysis data set (optional) 1..N sets (as shown below)

[0088] - {Type:(Day of Week:Sunday).(Location:Mumbai)} Collection

[0089] -Maximum load information (optional) integer 0..100

[0090] - Average load information (optional) integer 0..100

[0091] In the above example, the parameters included in the Eventsubscription_Notify message may include real-time load information about the network slice. The real-time load information may indicate the percentage of used (or unused) capacity of the network slice or network slice subnet, together with a timestamp indicating the time when the network slice load information was recorded. The Eventsubscription_Notify message may also include one or more analysis data sets. In the above example, the analysis data set includes statistical load information for each time period and / or each location. For example, an analysis data set may include the average, instantaneous, and maximum load of a network slice instance or network slice subnet instance for a specific location during a day. The location may indicate the area served by the network slice instance or network slice subnet instance. Therefore, Figure 7 The network slice and network slice subnet instance load information feedback received in is generated independently of the request from the network slice service consumer and occurs dynamically after the network slice is created when the trigger conditions are met.

[0092] The NSMF with the NWDAF subscription interface described in this article includes the following features:

[0093] 1. Mechanisms including subscription and notification methods that enable NSMF to make dynamic network slicing and slice subnet orchestration decisions based on current network criteria and historical patterns (through usage analytics)

[0094] 2. These notification inputs provided from NWDAF to NSMF may include:

[0095] a. The current or historical load on the network slice or network slice subnet;

[0096] b. Radio conditions associated with the access network portion of the network slice or network slice subnet;

[0097] c. Location-specific updates of the load on a network slice or network slice subnet;

[0098] d. time-based updates, where the load information of a network slice or a network slice subnet is automatically updated by the NWDAF to the NSMF at intervals defined by the NSMF as part of a subscription to receive the load information of the network slice or network slice subnet; and

[0099] e. Traffic-based updates, where NWDAF automatically updates NSMF with network slice or network slice subnet load information triggered by traffic conditions defined by NSMF in load information subscription.

[0100] Figure 7 The network slice load information feedback shown can be used to change the resource allocation between the network slice instance and the network slice subnet instance. For example, if the Eventsubscription_Notify message indicates that the network slice instance is 80% loaded when the report is triggered, the NSMF 402 can send a message to the NSSMF 404 to allocate additional resources to the network slice subnet instance that constitutes the network slice instance. In another example, if the Eventsubscription_Notify message indicates that the network slice instance is only 20% loaded during a given time period, the NSMF 402 can send a message to the NSSMF 404 to deallocate some of the resources allocated to the network slice subnet instance corresponding to the underutilized network slice instance.

[0101] Figure 8 is a block diagram illustrating an NSMF and an NWDAF suitable for implementing the network slice load information feedback mechanism described in this document. Figure 8 , NSMF 402 and NWDAF 600 each include at least one processor 800 and a memory 802. NSMF 402 includes a NWDAF subscription interface 804, which subscribes to receive network slice load information directly from NWDAF 600, obtains the load information, and stores the load information in a network slice load / resource allocation database 805. NSMF further includes a network slice resource management function 806, which uses the load information in the database 805 to issue network slice resource allocation and deallocation control commands via network slice resource management.

[0102] Compared to the static provisioning of network slices, or even to the implementation in which the network slice load information is not customized to the criteria defined by the NSMF, it is advantageous to provide the NSMF with a NWDAF subscription interface that subscribes directly to the NWDAF, defines the criteria that trigger the sending of network slice load information, and uses the network slice load information to dynamically update the network slice resource allocation. For example, the NSMF described in this article can define load information reporting triggering criteria based on a service level agreement with a communication service provider as part of a network slice load information subscription. If the NWDAF reports load information triggered by network conditions that are close to the criteria defined based on the SLA, the NSMF can independently maintain the service quality defined by the SLA without the need for SLA monitoring by the service consumer. In addition, the direct subscription interface between the NSMF and the NWDAF increases the possibility that the load information reported to the NSMF will be current.

[0103] The NWDAF 600 includes a network slice load information subscription manager 808. The network slice load information subscription manager 808 receives subscription requests from the NSMF 402 and other consumers who wish to receive load information about network slices. After confirming the subscribing entity, the network slice load information subscription manager 808 creates a network slice load information subscription by storing a record corresponding to the subscription in the network slice analysis and subscription database 810. The record may identify the subscribing entity (e.g., NSMF 402), the network slice instance and network slice subnet instance to which each entity subscribes, and the triggering conditions that trigger the reporting of network slice load information for each subscription.

[0104] The network slice load information analysis engine 809 receives load information from network functions (e.g., PCF, SMF, AMF, etc.), performs analysis based on the load information, and stores the analysis results and load information in the network slice analysis and subscription database 810.

[0105] When the network slice load information analysis engine 809 receives load information about a network slice, the network slice load information analysis engine 809 updates any record in the database 810 with the network slice load information.

[0106] The network slice load information analysis engine 809 may continuously evaluate the network slice reporting conditions associated with the records in the database 810 to determine whether the network slice load information event reporting conditions are met. When the network slice load information analysis engine 809 determines that the network slice load information event reporting conditions associated with the network slice instance load information subscription from the NSMF 402 have been met, the network slice load information analysis engine 809 generates a report with the requested load information and sends the report to the NSMF 402. The NSMF 402 utilizes the load information to make network slice instance resource allocation and deallocation decisions.

[0107] It should be noted that although Figure 8 The network slice load information subscription manager 808 and the network slice load information analysis engine 809 are illustrated as separate functional blocks, but their functionality may be combined to be performed by a single logical or physical entity within the NWDAF600 without departing from the scope of the subject matter described herein.

[0108] Fig. 9 is a flow chart illustrating an exemplary process for providing and utilizing real-time network slice load information feedback for network slice resource allocation. Fig. 9 The steps shown may be performed by NSMF 402. Fig. 9 In step 900, the processing includes subscribing directly to the NWDAF to receive network slice load information. For example, the NSMF 402 may send an Eventsubscription_Subscribe message to the NWDAF 600, where the Eventsubscription_Subscribe message identifies one or more network slice instances related to the load information that the NSMF 402 expects to receive. As described above, the Eventsubscription_Subscribe message may also include event type, data selection, and trigger information parameters. The Eventsubscription_Subscribe message may be sent by or via Figure 8 The Eventsubscription_Subscribe message is sent by the NWDAF subscription interface 804 of the NSMF 402 shown. The Eventsubscription_Subscribe message may include NSMF-defined criteria for triggering the NWDAF to report real-time network slice load information to the NSMF.

[0109] In step 902, the process includes receiving network slice load information from the NWDAF. For example, the NSMF 402 may receive an Eventsubscription_Notify message from the NWDAF 600, the Eventsubscription_Notify message including load information about the network slice instance and the network slice subnet instance identified in the Eventsubscription_Subscribe message. The load information may identify the percentage load (or availability) of each network slice instance or subnet instance. The Eventsubscription_Notify message may be received by or via Figure 8 The NWDAF subscription interface 804 of the NSMF 402 is shown to receive the report. The report can be triggered in response to satisfying the NSMF-defined criteria associated with the subscription.

[0110] In step 904, the processing includes determining whether a network slice resource allocation change is required. In this step, the NSMF 402 may compare the load information received in the Eventsubscription_Notify message with a threshold (such as an SLA-based threshold), and determine whether a network slice resource allocation change is required based on the relationship between the load information and the threshold. For example, a network slice service provider may define a 60% utilization threshold for a given network slice before a resource allocation change is triggered. If the load information about the network slice indicates that the network slice is currently utilized by 70%, the NSMF 402 may determine that a network slice resource modification is required. If the current load of the network slice is less than the threshold, control returns to step 902, in which the next load information about the network slice is received.

[0111] If the NSMF 402 determines that network slice resource modification is required, control proceeds to step 906, in which the NSMF 402 dynamically modifies the network slice resource allocation. In one example, dynamically modifying the network slice resource allocation may include generating and sending a message to modify the allocation of network slice resources. For example, if the NSMF 402 determines that a given network slice instance requires additional resources, the NSMF 402 may generate a message to allocate the additional resources to the network slice subnets that constitute the given network slice, and send the message to the NSSMF 404. Similarly, if the NSMF 402 determines that the resources allocated to the given network slice instance are underutilized, the NSMF 402 may generate a message to deallocate at least some of the resources allocated to the network slice subnet instances that constitute the network slice instance, and send the message to the NSSMF 404. In one example, the message sent to the NSSMF 404 may be sent by the network slice resource management function 806 via Figure 8 The network slice resource management interface 807 of the NSMF402 shown is set to NSSMF 404.

[0112] Fig.10 is a flow chart illustrating an exemplary process for providing network slice feedback information to a network slice management function. Fig.10 The steps shown are performed by NWDAF 600. Fig.10 In step 1000, the process includes receiving a message from the NSMF for creating a subscription to be notified of network slice load information. For example, the NWDAF 600 may receive an Eventsubscription_Subscribe message from the NSMF 402. The Eventsubscription_Subscribe message may identify one or more network slice instances and / or subnet instances that the NSMF 402 desires to monitor. As described above, the Eventsubscription_Subscribe message may also include an event type, data selection and trigger parameters, or other NSMF-defined network slice load information reporting trigger criteria. In one example, the Eventsubscription_Subscribe message may be received by Figure 8 The network slice load information subscription manager 808 of the NWDAF 600 shown receives directly from the NWDAF subscription interface 804 of the NSMF 402.

[0113] In step 1002, the process includes validating the NSMF. For example, the NWDAF 600 may access an internal authentication database to determine whether the NSMF 402 is authorized to receive load information about the network slice identified in the Eventsubscription_Subscribe message. Fig.10 In the example shown, it is assumed that the NSMF is successfully authenticated. In one example, authentication can be performed by the network slice load information subscription manager 808 using the information stored in Figure 8 The network slice analysis of the NWDAF 600 shown is performed based on the authentication data in the subscription database 810.

[0114] In step 1004, the NWDAF creates a subscription corresponding to the parameters received from the NSMF in the Eventsubscription_Subscribe message. For example, the network slice load information subscription manager 808 of the NWDAF 600 may create an entry in the network slice analysis and subscription database 810 that identifies the subscribing NSMF, and the type of network slice load information event notification and the parameters that the NSMF expects to receive.

[0115] In step 1006, the processing includes checking the NSMF defined criteria associated with the subscription for the load information obtained from the network function received from the NF implementing the network slice service. For example, the network slice load information analysis engine 809 of the NWDAF 600 can receive the load information from the NF (such as AMF, SMF, NRF, UDM, NEF, etc.), and can determine whether the load information is applicable to any subscription in the database 810. If the received load information corresponds to the monitored network slice information subscription, control proceeds to step 1008, in which it is determined whether the network slice load information reporting criteria associated with one of the subscriptions are met. If the network slice load information reporting criteria associated with one of the subscriptions have been met, control proceeds to step 1010, in which the network slice load information is transmitted to the NSMF. For example, the network slice load information analysis engine 809 of the NWDAF 600 can generate an Eventsubscription_Notify message and send the message to the NSMF 402. The Eventsubscription_Notify message may contain load information about the requested network slice or network slice subnet, and may also contain metadata about the network slice load information. The metadata may include the location and time at which the network slice load information was collected.

[0116] If it is determined in step 1008 that the load information reporting criteria associated with one of the subscriptions has not been met, control returns to step 1006, in which the subscription is checked for load information from the NF providing the network slicing service.

[0117] The subject matter described herein provides one or more of the following features and / or benefits:

[0118] The subject matter described in this paper introduces a feedback framework for NSMF to effectively manage and optimize network slices and network slice subnets.

[0119] The feedback mechanism described in this document enables the NSMF to maintain the Service Level Agreement (SLA) required by the CSMF in accordance with the service requirements of the CSMF.

[0120] • SLA terms may be used to define the amount of capacity allowed for the NSMF to perform NSI resizing.

[0121] Feedback mechanisms provide more efficient resource utilization of network slices.

[0122] The disclosure of each of the following references is incorporated herein by reference in its entirety.

[0123] 1. 3GPP TS 23.501, "Technical Specification Group Services and SystemAspects; System Architecture for the 5G System," (Release 16) V16.2.0 (2019-09).

[0124] 2. 3GPP TS 23.502, "Technical Specification Group Services and SystemAspects; Procedures for the 5G System," (Release 16) V16.2.0 (2019-09).

[0125] 3. 3GPP TS 28.531, "Technical Specification Group Services and SystemAspects; Management and orchestration; Provisioning," (Release 16) V16.3.0 (2019-09).

[0126] 4. 3GPP TR 28.801, "Technical Specification Group Services and SystemAspects; Telecommunication management; Study on management and orchestration ofnetwork slicing for next generation network," (Release 15) V15.1.0 (2018-01).

[0127] 5. 3GPP TS 29.520, "Technical Specification Group Core Network and Terminals; 5G System; Network Data Analytics Services," Stage 3 (Release 16) V16.1.0 (2019-09).

[0128] It will be understood that various details of the presently disclosed subject matter may be changed without departing from the scope of the presently disclosed subject matter. Furthermore, the foregoing description is for the purpose of illustration only, and not for the purpose of limitation.

Claims

1. A method for feedback-based network slice management, the method comprising: At a network slice management function (NSMF) comprising at least one processor: subscribing directly to the NWDAF via a Network Data Analysis Function (NWDAF) subscription interface of the NSMF to create a subscription to be notified of network slice load information, and as part of the subscription, specifying network slice load information report generation criteria defined by the NSMF; receiving network slice load information directly from the NWDAF via a NWDAF subscription interface of the NSMF and in response to satisfying a network slice load information report triggering criterion defined by the NSMF; Based on the network slice load information, determining that a change in network slice resource allocation is required; as well as In response to determining that a network slice resource allocation change is required, the network slice resource allocation is dynamically changed during operation of the network slice.

2. The method of claim 1, wherein directly subscribing to the NWDAF comprises sending an Eventsubscription_Subscribe message from the NSMF to the NWDAF, wherein the Eventsubscription_Subscribe message comprises an event type, data selection, and trigger parameters, and the trigger parameters are used to define a network slice load event that triggers reporting of network slice load information to the NSMF.

3. The method of claim 2, wherein the triggering parameters include parameters based on service level agreement (SLA) criteria.

4. A method as described in any one of claims 1 to 3, wherein receiving network slice load information includes receiving real-time load information indicating the utilization of the network slice after the network slice is created, independent of the monitoring of the network slice service consumer.

5. The method of any one of claims 1 to 3, wherein determining that a change in network slice resource allocation is required comprises: Comparing the network slice load information with a threshold defined by an operator; If the network slice load level indicated by the network slice load information exceeds the threshold, it is determined that the network slice resource allocation needs to be changed.

6. The method of any one of claims 1 to 3, wherein dynamically updating network slice resource allocation comprises: Generate and send a network slice subnet instance change request to the network slice subnet management function (NSSMF) to implement the change in the network slice resource allocation.

7. A method for providing real-time feedback for network slice management, the method comprising: At a network data analysis function (NWDAF) comprising at least one processor: Receiving, via a NWDAF subscription interface of a network slice management function (NSMF), a message directly from the NSMF and criteria defined by the NSMF, the message being used to create a subscription to be notified of real-time, post-creation network slice load information, the criteria defined by the NSMF being used to trigger reporting of the network slice load information; creating the subscription; For load information received from the Network Function (NF) providing the network slice service, check the criteria defined by the NSMF for the subscription definition; determining that criteria defined by the NSMF associated with one of the subscriptions are satisfied; as well as Responsive to determining that criteria defined by the NSMF associated with one of the subscriptions are satisfied, the load information is communicated directly to the NSMF.

8. The method as claimed in claim 7, wherein receiving a message from the NSMF includes receiving an Eventsubscription_Subscribe message, wherein the Eventsubscription_Subscribe message includes an event type, data selection and trigger parameters, and the trigger parameters are used to define a network slice load event that triggers reporting of network slice load information to the NSMF.

9. A method as claimed in claim 7 or 8, wherein creating the subscription includes creating an entry in a network slice analysis and subscription management database.

10. The method of claim 9, wherein checking the criteria defined by the NSMF comprises: Access an entry in the network slice analysis and subscription management database and determine whether a network slice load information reporting triggering criteria associated with the entry has been met.

11. The method of claim 7 or 8, wherein transmitting the network slice load information directly to the NSMF comprises sending an Eventsubscription_Notify message to the NSMF, wherein the Eventsubscription_Notify message comprises the network slice load information.

12. A system for feedback-based network slice management, the system comprising: A network slice management function (NSMF) comprising at least one processor: a network data analysis function (NWDAF) subscription interface implemented by the at least one processor, the NWDAF subscription interface being configured to: subscribe directly to the NWDAF to create a subscription to be notified of network slice load information, and as part of the subscription, specify network slice load information report generation criteria defined by the NSMF; receiving network slice load information directly from the NWDAF via a NWDAF subscription interface of the NSMF and in response to satisfying a network slice load information report triggering criterion defined by the NSMF; as well as a network slice resource manager implemented by the at least one processor, the network slice resource manager being configured to: determine, based on the network slice load information, that a change in network slice resource allocation is required; And in response to determining that a network slice resource allocation change is required, dynamically changing the network slice resource allocation during operation of the network slice.

13. A system as claimed in claim 12, wherein the NWDAF subscription interface is configured to subscribe directly to the NWDAF by sending an Eventsubscription_Subscribe message from the NSMF to the NWDAF, wherein the Eventsubscription_Subscribe message includes an event type, data selection and trigger parameters, and the trigger parameters are used to define a network slice load event that triggers reporting of network slice load information to the NSMF.

14. The system of claim 13, wherein the triggering parameters include parameters based on service level agreement (SLA) criteria.

15. A system as described in any one of claims 12 to 14, wherein the NWDAF subscription interface is configured to receive real-time load information indicating utilization of the network slice after the network slice is created, independent of monitoring by a network slice service consumer.

16. A system as described in any one of claims 12 to 14, wherein the network slice resource manager is configured to determine the need for a change in network slice resource allocation by comparing the network slice load information with a threshold defined by an operator, and if the network slice load level indicated by the network slice load information exceeds the threshold, determining that the network slice resource allocation needs to be changed.

17. A system as described in any one of claims 12 to 14, wherein the network slice resource manager is configured to dynamically update the network slice resource allocation by: generating and sending a network slice subnet instance change request to a network slice subnet management function (NSSMF) to implement the change of the network slice resource allocation.

18. A system for providing real-time feedback for network slice management, the system comprising: A network data analysis function (NWDAF) comprising at least one processor: A network slice load information subscription manager, the network slice load information subscription manager is used to: directly receive a message and a NSMF-defined criteria from a network slice management function (NSMF) via an NWDAF subscription interface of the NSMF, the message being used to create a subscription to be notified of real-time, created network slice load information, and the NSMF-defined criteria being used to trigger a report of the network slice load information; and creating said subscription; as well as A network slice load information analysis engine, the network slice load information analysis engine is used to: for load information received from a network function (NF) providing a network slice service, check the NSMF defined criteria defined for the subscription; determine that the NSMF defined criteria associated with one of the subscriptions are met; And in response to determining that NSMF-defined criteria associated with one of the subscriptions are satisfied, the load information is communicated directly to the NSMF.

19. The system of claim 18, wherein the network slice load information subscription manager is configured to receive an Eventsubscription_Subscribe message, wherein the Eventsubscription_Subscribe message includes an event type, data selection, and trigger parameters, and the trigger parameters are used to define a network slice load event that triggers reporting of network slice load information to the NSMF.

20. A system as described in claim 18 or 19, wherein the network slice load information subscription manager creates the subscription by creating an entry in a network slice analysis and subscription management database.

21. A system as claimed in claim 20, wherein the network slice load information analysis function is configured to check the criteria defined by the NSMF by: accessing an entry in the network slice analysis and subscription management database, and determining whether the network slice load information reporting trigger criteria associated with the entry have been met.

22. A system as described in claim 18 or 19, wherein the network slice data load information analysis engine is configured to transmit the network slice load information directly to the NSMF by sending an Eventsubscription_Notify message to the NSMF, wherein the Eventsubscription_Notify message includes the network slice load information.

23. A non-transitory computer readable medium storing executable instructions, wherein when the executable instructions are executed by a processor of a computer, the computer is controlled to perform the following steps: At a network slice management function (NSMF) comprising at least one processor: subscribing directly to a network data analysis function (NWDAF) of a network slice management function (NSMF) via a subscription interface of the NWDAF to create a subscription to be notified of network slice load information, and as part of the subscription, specifying network slice load information report generation criteria defined by the NSMF; receiving network slice load information directly from the NWDAF via a NWDAF subscription interface of the NSMF and in response to satisfying a network slice load information report triggering criterion defined by the NSMF; Based on the network slice load information, determining that a change in network slice resource allocation is required; as well as In response to determining that a network slice resource allocation change is required, the network slice resource allocation is dynamically changed during operation of the network slice.

24. A non-transitory computer readable medium storing executable instructions, wherein when the executable instructions are executed by a processor of a computer, the computer is controlled to perform the following steps: Receiving a message and NSMF-defined criteria directly from a network slice management function (NSMF) via a network data analysis function (NWDAF) subscription interface of the NSMF, wherein the message is used to create a subscription to be notified of real-time, post-creation network slice load information, and the NSMF-defined criteria are used to trigger reporting of the network slice load information; creating the subscription; For load information received from the Network Function (NF) providing the network slice service, check the criteria defined by the NSMF for the subscription definition; determining that criteria defined by the NSMF associated with one of the subscriptions are satisfied; as well as In response to determining that NSMF-defined criteria associated with one of the subscriptions are satisfied, the load information is communicated directly to the NSMF.

Images