Method and apparatus for switching network slices
By selecting network elements based on resource information and switching strategies, terminal devices can be switched to the target network slice in a timely manner, which solves the problem of service interruption caused by network slice failure and ensures the service continuity and user experience of terminal devices.
Patent Information
- Application Number
- CN202111509743.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-12-10
- Publication Date
- 2026-03-20
- Estimated Expiration
- 2041-12-10
AI Technical Summary
How to ensure service continuity and user experience for terminal devices when network slicing on user devices fails or cannot meet business needs?
The network element receives resource and alarm information of the original network slice and determines whether to switch to the target network slice in a timely manner based on the network slice switching policy, so as to ensure that the service needs of the terminal device are met.
It enables timely switching to a backup slice in the event of network slice failure or performance degradation, ensuring service continuity and user experience for terminal devices.
Smart Images

Figure CN116261189B_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of communication, and in particular to a method and device for switching network slices. BACKGROUND
[0002] Network slice (NS) is one of the key technologies of the 5th Generation (5G) system, which is a complete instantiated logical network composed of a group of network functions (NFs), and is intended to use optimal resource allocation to more efficiently address the special needs of vertical services (such as high-definition video services with higher bandwidth requirements, game services with higher latency requirements, etc.). Network slices enable operators to build multiple end-to-end, virtual, isolated, and on-demand customized dedicated logical networks on one physical network. Each logical network has different network functions, thereby better adapting to the differentiated needs of different vertical services.
[0003] If the current network slice of a user equipment (UE) fails or cannot meet the service requirements of the UE, the UE can be switched to another network slice to ensure service continuity. For example, in an industrial scenario, due to the high availability requirement of network services, an industrial terminal may need to back up a 5G slice under the same operator or other operators when connecting to a 5G slice, so as to switch the UE to the backup network slice when the current slice has a connection problem, and continue to provide services for the UE by the backup network slice, thereby ensuring service continuity.
[0004] How to switch the network slice of the UE is a problem to be solved at present. SUMMARY
[0005] The present application provides a method and device for switching network slices, which can guarantee the service experience of a terminal device after network slice switching.
[0006] In a first aspect, a method for switching network slices is provided, which includes: a slice selection network element receiving resource information of an original network slice from a network slice management function network element, the resource information of the original network slice including one or more of the following information: performance indicators of the original network slice, alarm information of the original network slice, and an analysis report for the original network slice; the slice selection network element determining whether to switch a terminal device on the original network slice to a target network slice according to the resource information of the original network slice and a network slice switching policy, the network slice switching policy including a trigger condition for switching network slices, an identifier of the target network slice, an identifier of the original network slice, and an identifier of the terminal device and / or an application identifier on the original network slice.
[0007] Based on the above scheme, the slice selection network element can determine whether to perform network slice switching for the terminal device on the original network slice according to the resource information of the original network slice and the network slice switching policy, so as to guarantee the service experience of the terminal device after switching.
[0008] In combination with the first aspect, in some implementations of the first aspect, the slice selection network element determines whether to switch the terminal device on the original network slice to the target network slice according to the resource information of the original network slice and the network slice switching policy, including: the slice selection network element determines whether the resource information of the network slice meets the trigger condition of the switching network slice; in the case that the resource information of the network slice meets the trigger condition of the switching network slice, the slice selection network element determines to switch the terminal device on the network slice to the target network slice.
[0009] Based on the above scheme, in the case that the resource information of the original network slice meets the trigger condition of the switching network slice, the slice selection network element determines to switch the terminal device on the network slice to the target network slice, that is, the slice selection network element can determine the timing of the network slice switching, so that the slice selection network element can timely perform network slice switching for the terminal device on the original network slice that meets the trigger condition, avoiding the impact on the service experience of the terminal device due to untimely network slice switching.
[0010] In combination with the first aspect, in some implementations of the first aspect, the method further includes: the slice selection network element receives the resource information of the target network slice from the network slice management function network element; and the slice selection network element determines that the resource information of the target network slice does not meet the trigger condition.
[0011] Based on the above scheme, in the case that the resource information of the original network slice meets the trigger condition of the switching network slice, and the resource information of the target network slice does not meet the trigger condition of the switching network slice, the slice selection network element determines to switch the terminal device on the network slice to the target network slice. That is, in the case that the original network slice cannot meet the demand, and the target network slice meets the demand, the terminal device on the original network slice can be switched to the target network slice, so as to guarantee the service experience of the terminal device by switching the terminal device to the network slice.
[0012] In some implementations of the first aspect, the trigger condition for switching the network slice comprises one or more of: a performance indicator of the network slice being greater than or equal to a first threshold value or being less than or equal to a second threshold value; the slice selection network element receiving alarm information of the network slice and / or the performance indicator of the network slice; the slice selection network element receiving alarm information of the original network slice, and the alarm information being high-priority alarm information; an analysis report of the network slice satisfying a switching condition.
[0013] The first threshold value and the second threshold value herein can be threshold values representing different meanings. For example, the first threshold value is a latency threshold value, the second threshold value is a bandwidth threshold value, the performance indicator corresponding to the first threshold value is latency, and the performance indicator corresponding to the second threshold value is bandwidth. That is, the trigger condition for switching the network slice can comprise: the latency of the network slice being greater than or equal to the latency threshold value, or the bandwidth of the network slice being less than or equal to the bandwidth threshold value.
[0014] Based on the above scheme, when the performance indicator of the original network slice is greater than or equal to the first threshold value or is less than or equal to the second threshold value, or when the slice selection network element receives the alarm information and / or the performance indicator of the network slice, or when the slice selection network element receives the alarm information of the original network slice and the alarm information is high-priority alarm information, or when the analysis report of the original network slice satisfies the switching condition, the slice selection network element can switch the terminal device on the network slice to a target network slice. That is, the slice selection network element can timely switch the terminal device on the original network slice to the target network slice when the original network slice satisfies any of the above conditions, thereby avoiding the impact on the service experience of the terminal device due to the untimely switching of the network slice.
[0015] In some implementations of the first aspect, the method further comprises: sending, by the slice selection network element, a subscription request message to the network slice management function network element, the subscription request message comprising an identifier of the original network slice, the subscription request message being used to subscribe to resource information of the original network slice.
[0016] Based on the above scheme, the slice selection network element can subscribe to the resource information of the original network slice from the network slice management function network element, so that the slice selection network element can determine whether the resource information of the original network slice satisfies the trigger condition, so as to timely switch the terminal device on the original network slice to the target network slice when the resource information of the original network slice satisfies the trigger condition.
[0017] In a possible implementation of the first aspect, the method further includes: in a case where the slice selection network element determines to switch the terminal device on the original network slice to the target network slice, the slice selection network element sends, to a network slice capability management service-providing network element, a network slice configuration request message, the network slice configuration request message including an identifier of the target network slice, and an identifier of the terminal device on the original network slice and / or the application identifier, the network slice configuration request message being used to request configuration of the target network slice for the terminal device on the network slice.
[0018] Based on the above scheme, when it is determined to switch the terminal device on the original network slice to the target network slice, the slice selection network element can request the network slice capability management service-providing network element to configure the target network slice for the terminal device on the original network slice, so as to switch the terminal device on the original network slice to the target network slice, and guarantee the service experience of the terminal device.
[0019] In a possible implementation of the first aspect, the method further includes: the slice selection network element receives a network slice configuration response message from the network slice capability management service-providing network element, the network slice configuration response message being used to indicate that the configuration of the target network slice for the terminal device is successful; and according to the network slice configuration response message, the slice selection network element sends, to an application server, a network slice configuration feedback message, the network slice configuration feedback message including an identifier of the target network slice and an identifier of the terminal device on the original network slice.
[0020] Based on the above scheme, when the slice selection network element determines, according to the network slice configuration response message of the network slice capability management service-providing network element, that the terminal device on the original network slice is successfully switched to the target network slice, the slice selection network element can send, to the application server, the identifier of the target network slice and the identifier of the terminal device on the original network slice, so as to indicate that the terminal device on the original network slice is switched to the target network slice.
[0021] According to the above scheme, after the application server receives the identifier of the target network slice and the identifier of the original network slice from the slice selection network element, the application server can modify or reconfigure the network slice switching policy.
[0022] In a possible implementation of the first aspect, the method further includes: in a case where the slice selection network element determines not to switch the terminal device on the network slice to the target network slice, the slice selection network element sends, to an application server, a network slice configuration feedback message, the network slice configuration feedback message including an identifier of the original network slice, the network slice configuration feedback message being used to indicate that the switching of the network slice for the terminal device on the network slice is not successful.
[0023] Based on the above scheme, when the slice selection network element does not switch the terminal device on the original network slice to the target network slice, the slice selection network element can indicate the application server, so that the application server can determine that the network slice switching of the terminal device fails
[0024] Based on the above scheme, when the application server determines that the network slice switching of the terminal device fails, the application server can formulate a coping strategy, for example, re-modify the network slice switching strategy, so that when the resource information of the original network slice meets the trigger condition of switching the network slice, the terminal device on the original network slice can be successfully switched to the target network switch, so as to guarantee the service experience of the terminal device after switching.
[0025] In combination with the first aspect, in some implementations of the first aspect, the network configuration feedback message further includes a reason value and / or a suggested behavior indication information, the reason value is used to indicate the reason for not switching the terminal device on the network slice to the target network slice, and the suggested behavior indication information is used to indicate the operation performed by the application server.
[0026] Based on the above scheme, when the slice selection network element does not switch the terminal device on the original network slice to the target network slice, the slice selection network element can indicate the application server, and indicate the reason value and / or the suggested behavior indication information, so that the application server can formulate a coping strategy according to the reason value and / or the suggested behavior. For example, the reason value indicates that the failure reason is that the resource utilization rate of the target network slice is greater than the set threshold, and then the application server can modify or increase the target network slice in the network slice switching strategy.
[0027] In combination with the first aspect, in some implementations of the first aspect, the method further includes: the slice selection network element receives a policy configuration request message from the network slice capability management service consumption network element or the application server, the policy configuration request message including the network slice switching strategy; and the slice selection network element saves the network slice switching strategy.
[0028] Based on the above scheme, the network slice capability management service consumption network element or the application server can configure the network slice switching strategy to the slice selection network element, and the slice selection network element can determine the target network slice, the trigger condition of switching the network slice, and the identifier of the terminal device on the original network slice according to the network slice switching strategy, so that the terminal device on the original network slice can be switched to the target network slice when the original network slice meets the trigger condition of switching the network slice, in order to guarantee the service experience of the terminal device after switching.
[0029] In some implementations of the first aspect, the method further includes: receiving, by the slice selection network element, a policy modification request message from the network slice capability management service consumer network element or the application server, the policy modification request message including policy modification information, the policy modification information indicating a modification to be performed on the network slice switching policy; and modifying, by the slice selection network element, the network slice switching policy according to the policy modification information.
[0030] According to the above scheme, the slice selection network element can modify the network slice switching policy according to the request or indication of the network slice capability management service consumer network element or the application server. For example, when the network slice switching of the terminal device on the original network slice fails, the network slice capability management service consumer network element or the application server can modify the network slice switching policy so that the terminal device on the original network slice can switch to the target network slice, thereby guaranteeing the service experience of the terminal device.
[0031] In some implementations of the first aspect, the method further includes: receiving, by the slice selection network element, a policy deletion request message from the network slice capability management service consumer network element or the application server, the policy deletion request message indicating that the network slice switching policy is to be deleted; and deleting, by the slice selection network element, the network slice switching policy.
[0032] According to the above scheme, the slice selection network element can delete the network slice switching policy according to the request or indication of the network slice capability management service consumer network element or the application server.
[0033] In some implementations of the first aspect, the method further includes: updating, by the slice selection network element, an association between the identity of the target network slice and the identity of the terminal device.
[0034] According to the above scheme, when the slice selection network element determines that the terminal device on the original network slice successfully switches to the target network slice according to the network slice configuration response message of the network slice capability management service providing network element, the slice selection network element can update the association between the identity of the target network slice and the identity of the terminal device for use in subsequent processes.
[0035] In a second aspect, a method for selecting a network slice is provided. The method includes: receiving, by an application server, a network slice configuration feedback message from a slice selection network element, the network slice configuration feedback message including an identification of an original network slice, the network slice configuration feedback message indicating that a network slice switching for a terminal device on the original network slice is not successful; determining, by the application server, a modification scheme for a network slice switching policy according to the network slice configuration feedback message; and sending, by the application server, a network slice switching policy modification request message to the slice selection network element, the network slice switching policy modification request message including an identification of the network slice switching policy and policy modification information indicating the modification scheme.
[0036] Based on the above scheme, when the application server determines that the terminal device on the original network slice fails to switch to the target network slice, the application server can modify the network slice switching policy, so that when the original network slice meets the triggering condition of switching the network slice, the terminal device can be switched to the network slice, thereby guaranteeing the service experience of the terminal device.
[0037] In combination with the second aspect, in some implementations of the second aspect, the network slice configuration feedback message includes a cause value and / or suggestion behavior indication information, the cause value indicating a reason for not switching the terminal device on the network slice to the target network slice, and the suggestion behavior indication information indicating an operation performed by the application server; and the application server determines the modification scheme for the network slice switching policy according to the network slice configuration feedback message, including: the application server determines the modification scheme for the network slice switching policy according to the cause value and / or the suggestion behavior indication information.
[0038] Based on the above scheme, the application server can determine the modification scheme for the network slice switching policy according to the cause value, so that the modified network slice switching policy can successfully switch the terminal device on the original network slice to the target network slice, thereby guaranteeing the service experience of the terminal device after the network slice switching.
[0039] In combination with the second aspect, in some implementations of the second aspect, the method further includes: sending, by the application server, a policy configuration request message to the slice selection network element, the policy configuration request message including the network slice switching policy, the policy configuration request message being used to request to configure the network slice switching policy.
[0040] Based on the above scheme, the application server can configure the network slice switching policy to the slice selection network element, so that the slice selection network element can determine whether the terminal device on the original network slice can be switched to the target network slice according to the network slice switching policy, thereby guaranteeing the service experience of the terminal device.
[0041] With reference to the second aspect, in some implementations of the second aspect, the method further includes: sending, by the application server, a policy deletion request message to the slice selection network element, the policy deletion request message including an identifier of the network slice switching policy, the policy deletion request message being used to indicate deletion of the network slice switching policy.
[0042] Based on the above scheme, the application server can instruct the slice selection network element to delete the network slice switching policy, so as to save resources when there is no need to switch network slices.
[0043] With reference to the second aspect, in some implementations of the second aspect, the method further includes: sending, by the application server, a policy deletion request message to the slice selection network element, the policy deletion request message including an identifier of the network slice switching policy, the policy deletion request message being used to indicate deletion of the network slice switching policy.
[0044] Based on the above scheme, the application server can query the network slice switching policy from the slice selection network element.
[0045] The third aspect provides a device for switching network slices, which is configured to execute the method provided in the first aspect or the second aspect. Specifically, the device can include units and / or modules for executing the method provided in the first aspect or the second aspect, such as a processing unit and / or a communication unit. In one implementation, the device is a slice selection network element. When the device is a slice selection network element, the communication unit can be a transceiver or an input / output interface, and the processing unit can be a processor.
[0046] In another implementation, the device is a chip, a chip system or a circuit used in a slice selection network element. When the device is a chip, a chip system or a circuit used in a communication device, the communication unit can be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or related circuit on the chip, the chip system or the circuit, etc., and the processing unit can be a processor, a processing circuit or a logic circuit, etc.
[0047] In one possible case, the device is a chip, a chip system or a circuit used in a slice selection network element. In this case, the device can include units and / or modules for executing the method provided in the first aspect, such as a processing unit and / or a communication unit.
[0048] In another possible case, the device is a chip, a chip system or a circuit used in an application server. In this case, the device can include units and / or modules for executing the method provided in the second aspect, such as a processing unit and / or a communication unit.
[0049] Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.
[0050] In a fourth aspect, a device for switching network slices is provided. The device includes a memory configured to store a program, and a processor configured to execute the program stored in the memory. When the program stored in the memory is executed, the processor is configured to perform the method provided in the first aspect or the second aspect.
[0051] In a fifth aspect, a processor is provided for performing the method provided in the above aspects. In the process of performing these methods, the processes of sending and obtaining / receiving the information in the above method can be understood as the process of outputting the information by the processor, and the process of receiving the input information by the processor. When the information is output, the processor outputs the information to the transceiver for transmission by the transceiver. After the information is output by the processor, it may also need to be processed further before reaching the transceiver. Similarly, when the processor receives the input information, the transceiver obtains / receives the information and inputs it to the processor. Furthermore, after the transceiver receives the information, the information may need to be processed further before being input to the processor.
[0052] Based on the above principles, for example, the receiving request message mentioned in the foregoing method can be understood as the processor receiving the input information.
[0053] For the transmission, sending, and obtaining / receiving operations of the processor, if there is no special description, or if it does not conflict with the actual role or inherent logic in the related description, it can be more generally understood as the processor outputting and receiving, inputting, etc., rather than the transmission, sending, and receiving operations directly performed by the radio frequency circuit and the antenna.
[0054] In the implementation process, the processor can be a processor specially used to execute these methods, or a processor that executes computer instructions in a memory to execute these methods, such as a general-purpose processor. The memory can be a non-transitory memory, such as a read only memory (ROM), which can be integrated on the same chip as the processor, or can be separately arranged on different chips. The type of memory and the arrangement of the memory and the processor are not limited by the embodiments of the present application.
[0055] In a sixth aspect, a computer readable storage medium is provided. The computer readable medium stores program code for execution by an apparatus. The program code includes code for performing the method provided in the first aspect or the second aspect.
[0056] In a seventh aspect, a computer program product including instructions, which when executed on a computer, cause the computer to perform the method provided by the first aspect or the second aspect.
[0057] In an eighth aspect, a chip is provided, which includes a processor and a communication interface, the processor reads instructions stored on a memory through the communication interface, and performs the method provided by the first aspect or the second aspect.
[0058] Optionally, as an implementation manner, the chip can further include a memory, the memory stores instructions, and the processor is configured to execute the instructions stored on the memory, and when the instructions are executed, the processor is configured to perform the method provided by the first aspect or the second aspect. BRIEF DESCRIPTION OF DRAWINGS
[0059] Figure 1 A network architecture suitable for the embodiments of the present application is shown.
[0060] Figure 2 Another network architecture suitable for the embodiments of the present application is shown.
[0061] Figure 3 A schematic flowchart of network slice adaptation is shown.
[0062] Figure 4 A network system schematic diagram provided by the embodiments of the present application is shown.
[0063] Figure 5 A network architecture schematic diagram provided by the embodiments of the present application is shown.
[0064] Figure 6 A schematic flowchart of a method of switching network slices is shown.
[0065] Figure 7 A schematic flowchart of another method of switching network slices is shown.
[0066] Figure 8 A schematic flowchart of yet another method of switching network slices is shown.
[0067] Figure 9 A schematic flowchart of yet another method of switching network slices is shown.
[0068] Figure 10 A schematic flowchart of yet another method of switching network slices is shown.
[0069] Figure 11 A schematic block diagram of an apparatus provided by the embodiments of the present application is shown.
[0070] Figure 12is another schematic block diagram of the apparatus provided by an embodiment of the present application. DETAILED DESCRIPTION
[0071] In order to make the purposes, technical solutions and advantages of the present application clearer, the technical solutions in the present application will be described below with reference to the drawings. The specific operation methods in the method embodiments can also be applied to the apparatus embodiments or system embodiments. In the description of the present application, the meaning of "a plurality of" is two or more, unless otherwise specified.
[0072] In various embodiments of the present application, the terms and / or descriptions of different embodiments are consistent and can be mutually referred to, unless otherwise specified and there is no logical conflict. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.
[0073] It can be understood that the various numbers involved in the present application are only distinguished for the convenience of description, and do not limit the scope of the present application. The size of the serial number of the above processes does not mean the execution order, and the execution order of the processes should be determined according to its function and inherent logic.
[0074] The terms "first", "second", "third", "fourth" and other various terms labels and the like (if any) in the specification and claims of the present application and the above drawings are used to distinguish similar objects, and do not have to be used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device including a series of steps or units does not have to be limited to those steps or units clearly listed, but can include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0075] Figure 1A schematic diagram of a network architecture 100 of a service enabler architecture layer for verticals (SEAL) suitable for embodiments of the present application is shown. In the vertical application layer (VAL), a VAL client communicates with a VAL server through a VAL-UU interface, which supports both unicast and groupcast information transmission modes. The service enabler architecture layer for verticals (SEAL) on the UE and server are divided into a SEAL client and a SEAL server, respectively. The SEAL can provide the service enabler layer support functions to the VAL client through a SEAL-C interface; the VAL server can communicate with the SEAL server through a SEAL-S interface. The SEAL server can communicate with the 3GPP network through the network interfaces provided by the 3GPP, including the N33 interface provided by the network exposure function (NEF) of the core network element, the service interface provided by the OAM, etc.
[0076] The vertical application layer supports the following SEAL services:
[0077] • Location management function
[0078] • Group management function
[0079] • Configuration management function
[0080] • Key management function
[0081] • Network resource management function
[0082] • Network slice capability management function
[0083] The VAL Server can invoke one or more of the above SEALs to implement the use of 3GPP network capabilities.
[0084] Figure 2 A schematic diagram of a network architecture 200 of a network slice capability management (NSCM) applicable to the embodiments of the present application is shown. The network architecture 200 is used to support the management of network slices for vertical applications. Among them, the network slice management server (NSCM server) function entity provides functions in the aspect of network slices to support VAL applications. This empowerment supports the mapping or migration of one or more vertical applications to one or more network slices. The network slice management client (NSCM client) function entity is an application client of slice empowerment. The NSCM client can interact with the NSCM server to trigger network slice adaptation caused by application requirement changes, where the application requirement changes can be application QoS requirement changes, service operation changes, etc. The NSCM client can receive network slice / DNN remapping notifications from the NSCM server. The NSCM client communicates with the NSCM server through the NSCM-UU interface. The network slice capability management client provides support for network slice capability management functions to the VAL client through the NSCM-C interface. The VAL server communicates with the NSCM server through the NSCM-S interface. Assuming that the NSCM server is deployed in the 5G system domain, the NSCM server as an AF can communicate with the 5G core network functions through the NEF (N33) reference point (used to interact with the PCF).
[0085] It should be understood that the above network architecture applicable to the embodiments of the present application is only an example, and the network architecture applicable to the embodiments of the present application is not limited thereto, and any network architecture capable of realizing the functions of the above-mentioned network elements is applicable to the embodiments of the present application.
[0086] The network architecture and service scenarios described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. It can be known by those skilled in the art that, with the evolution of network architecture and the appearance of new service scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.
[0087] Various aspects or features of embodiments of the disclosure can be implemented as a method, apparatus, or article of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used in the disclosure is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g., compact disk (CD), digital versatile disk (DVD), etc.), smart cards, and flash memory devices (e.g., EPROM, card, stick, or key drive, etc.). Additionally, various storage media described herein can represent one or more devices and / or other machine-readable media for storing information. The term "machine- readable medium" can include, without being limited to, wireless channels and various other media capable of storing, containing, and / or carrying instruction(s) and / or data.
[0088] With the rapid development of wireless communication technology, current communication networks face diversified application scenarios. Network slicing can provide customized virtual networks for different application requirements to meet the differentiated performance indicators in different scenarios. Network slicing not only provides quality- guaranteed network services for users, but also improves resource utilization and reduces costs by sharing resources. When the location information or service information of a terminal device changes, or the current network slice of the terminal device fails or performance decreases, the service or user experience of the terminal device can be affected. In this case, the terminal device can be switched to a backup network slice that meets the requirements to meet the service requirements of the terminal device.
[0089] For example, in a power grid scenario, power grid industry users supply power in different regions through a distributed power distribution network, and form a micro-grid in a region, which can be self-sufficient in power supply. Under normal circumstances, the 5G communication terminal of the power grid works on a large electronic dedicated slice, and all gNBs and core networks in the micro-grid support the normal operation of the slice. When an emergency situation such as a large-scale power outage occurs, the gNBs in the micro-grid can stop working due to power failure. In this case, the 5G power terminal can be switched to a network slice according to the gNB facilities that can still work, and a new slice can be formed by the gNBs that are still working to support 5G power terminal communication, so that the power grid equipment can communicate with the power grid control center and support power restoration. If the 5G power terminal in the micro-grid cannot maintain communication outside the micro-grid, the terminal can also be switched to a network switch to maintain communication between power grid equipment within the coverage of the micro-grid and keep the micro-grid running.
[0090] Figure 3 An exemplary flow chart of a network slice adaptation method 300 for a VAL application is shown, which can be used for switching network slices for vertical industry application terminals. The method 300 comprises the following steps:
[0091] S301, the VAL server sends a network slice adaptation request message to the NSCM server.
[0092] Exemplarily, the VAL server sends a network slice adaptation request message of the VAL application (and the VAL UE using the VAL application) to the NSCM server. The network slice adaptation request message can be for the VAL UE using the VAL application, or for the VAL application. It should be understood that the VAL UE using the VAL application can also be referred to as the VAL UE in the VAL application. For example, the network slice adaptation request message is used to request network slice (and optional DNN) adaptation for all VAL UEs using a certain VAL application, or the network slice adaptation request message is used to request remapping of the VAL application to a different network slice (and / or to a DNN). It should be understood that the message itself does not limit the message itself, and "network slice adaptation" in this context can also be referred to as "network slice configuration", "network slice selection", etc. in some scenarios, which is not limited in the present application.
[0093] Table 1 shows a list of possible parameters carried in the network slice adaptation request message.
[0094] Table 1
[0095] Information element Status Description VAL service ID Mandatory Identity of VAL application List of VAL UE IDs Mandatory Identity of VAL UE Network slice adaptation cause Optional Cause of network slice adaptation Requested S-NSSAI Optional Identity of target network slice Requested DNN Optional Identity of target DNN
[0096] As can be seen from Table 1, the network slice adaptation request message includes the identification of the VAL application (VAL service ID) and the identification of the VAL UE (List of VAL UE IDs). Optionally, the network slice adaptation request message can also include the reason for network slice adaptation, the identification of the target network slice (or referred to as the requested network slice), and the identification of the target DNN (or referred to as the requested DNN).
[0097] S302, the NSCM server triggers configuration of network slices for each VAL UE using the VAL application.
[0098] Exemplarily, the NSCM server receives a network slice adaptation request message from the VAL server, and according to the network slice adaptation request message, the NSCM triggers to configure a network slice for each VAL UE (or each VAL UE in the VAL application) using the VAL application.
[0099] S303, the NSCM server configures a network slice for each VAL UE through the 5GC.
[0100] Exemplarily, the NSCM server provides an updated S-NSSAI and DNN for each VAL UE. Specifically, the NSCM server configures the network slice of the VAL UE by calling the interface of the core network. The specific configuration process can refer to the existing protocol, and the present application does not make any limitation.
[0101] S304, the NSCM server sends a network slice adaptation response message to the VAL server.
[0102] Exemplarily, after successfully configuring the network slice, the NSCM server sends a network slice adaptation response message to the VAL server, and provides the network slice adaptation result of each VAL UE through the network slice adaptation response message.
[0103] Therefore, in the above method flow, the UE (or the vertical industry client) decides the timing of network slice switching and the target of network slice switching, and the Seal service platform only provides a slice configuration interface. However, the vertical industry client cannot perceive the resource status of the network slice, and therefore may not be able to select a suitable network slice at a suitable time, resulting in the reliability and availability of the vertical industry business being affected.
[0104] To solve the above technical problems, the embodiments of the present application introduce a network slice selection network element, which can also be called a network slice selector, or a network slice configuration network element, a network slice adapter, etc. It can be a separate network element, or a module in a certain network element, and the present application does not make any limitation. Any network element or device with similar functions shall be within the protection scope of the present application. The network slice selector is an automatic slice selection module or network element, which can automatically determine the target network slice according to the network slice resource information and the network slice switching strategy. And it can realize the function of switching the network slice for the UE by calling the slice selection configuration interface provided by the NSCM. The network slice selector can be integrated in the NSCM server, i.e. deployed in the same server as the NSCM, for example, in Figure 4 The system structure 400 shown in the figure, the network slice selector is deployed in the NSCM server. The network slice selector can also be deployed on a separate server, for example, inFigure 5 In the system architecture 500 shown, the network slice selector is deployed on the network slice selection server. In addition, in the system architecture 500 shown, the network slice selection server is deployed in the network slice management function (NSMF) of the 5G core network (5GC). Figure 4 or Figure 5 In the system architecture shown, the VAL server is responsible for providing the network slice switching policy for the network slice selector, and receiving the slice change result notification. The 5GC (5G core network) provides the network slice selection configuration capability of the UE through the NEF. The NSMF (network slice management function) is responsible for providing the network slice related KPI, alarm, and related prediction report information to the network slice selector.
[0105] The specific interaction process in the above solution can refer to the method flow in Figure 6 , and the specific implementation solution is described in detail in the method 600.
[0106] The method for switching network slices provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings. The embodiments provided by the present application can be applied in the network structure shown in Figure 1 or Figure 2 , or the system architecture shown in Figure 4 or Figure 5 , without limitation.
[0107] Figure 6 An exemplary flowchart of the method 600 for switching network slices provided by the embodiments of the present application is shown. The method 600 can include the following steps:
[0108] S601, the slice selection network element receives resource information of an original network slice from a network slice management function network element.
[0109] Exemplarily, the resource information of the original network slice includes one or more of the following information: performance indicators of the original network slice, alarm information of the original network slice, and analysis report for the original network slice.
[0110] The performance indicators of the original network slice can include one or more performance parameters of the original network slice, such as latency, throughput, utilization, etc.; the alarm information of the original network slice is an alarm information used in the case where the original network slice fails, or cannot be used, or cannot meet the demand, such as a fault alarm when a physical fault occurs, or a power failure alarm when a power failure occurs, etc.; the analysis report for the original network slice can be an analysis (optionally also including a suggested behavior) given by the network slice management function network element for the original network slice, for example, the network slice management function network element predicts that the network resource occupancy rate of the original network slice will exceed the threshold value after a period of time (for example, 10 minutes).
[0111] Optionally, before S601, the slice selection network element can subscribe the resource information of the original network slice from the network slice management function network element, or in other words, the network slice management function network element can send the resource information of the original network slice to the slice selection network element according to the subscription request message from the slice selection network element. For example:
[0112] S602, the slice selection network element sends a subscription request message to the network slice management function network element.
[0113] Exemplarily, the subscription request message includes the identification of the original network slice, and the subscription request message is used to request to subscribe the resource information of the original network slice, which can be one or more of the performance indicators, the alarm information, and the analysis report of the original network slice.
[0114] Correspondingly, the network slice management function network element receives the subscription request message from the slice selection network element, and when certain conditions are met, the network slice management function network element sends the resource information of the original network slice to the slice selection network element in S601. Wherein, the network slice management function network element can determine the conditions for reporting the resource information of the original network slice according to the subscription request message from the slice selection network element.
[0115] For example, the slice selection network element subscribes the alarm information from the network slice management function network element, and when the original network slice occurs an alarm situation (for example, NSI alarm), the network slice management function network element sends the resource information of the original network slice to the slice selection network element, and the resource information of the original network slice includes the alarm information of the original network slice.
[0116] For another example, the slice selection network element subscribes the performance indicators of the original network slice from the network slice management function network element. In one implementation, the slice selection network element can indicate the conditions for reporting the performance indicators of the original network slice in the subscription request message, for example, the slice selection network element can carry the threshold value of one or more performance indicators in the subscription request message, for example, the delay threshold value, when the delay of the original network slice is greater than or equal to the delay threshold value, the network slice management function network element reports the performance indicators of the original network slice to the slice selection network element, and the performance indicators include the delay of the original network slice. In another implementation, the slice selection network element can indicate the time interval for reporting the performance indicators of the original network slice in the subscription request message. For example, the slice selection network element indicates in the subscription request message that the network slice management function network element actively reports the delay of the original network slice every 10 minutes, in this implementation, the network slice management function network element reports the resource information of the original network slice to the slice selection network element every 10 minutes, and the resource information includes the delay of the original network slice.
[0117] For example, the slice selection network element subscribes to the analysis report of the original network slice from the network slice management function network element. When the network slice management function network element makes an analysis report of the original network slice according to the operator's policy or other conditions, the analysis report of the original network slice needs to be reported to the slice selection network element.
[0118] S603, the slice selection network element determines whether to switch the terminal device on the original network slice to the target network slice according to the resource information of the original network slice and the network slice switching policy.
[0119] For example, after the slice selection network element receives the resource information of the original network slice from the network slice management function network element, it determines whether to switch the terminal device on the original network slice to the target network slice according to the resource information of the original network slice and the network slice switching policy.
[0120] The network slice switching policy includes the trigger condition of switching the network slice, the identifier of the target network slice, the identifier of the original network slice, and the identifier and / or application identifier of the terminal device on the original network slice. Optionally, the network slice switching policy can also include the target data network name.
[0121] It should be understood that the original network slice here refers to the current network slice of the terminal device, and the target network slice refers to the network slice to be switched (or the backup network slice) of the terminal device. The names here are only used to distinguish different network slices, and they can also have other names in some other scenarios, which are not limited by the present application.
[0122] It should also be understood that the network slice switching policy here can be pre-configured by the application server or the service consumption network element to the slice selection network element. For example:
[0123] S604, the application server sends a policy configuration request message to the slice selection network element.
[0124] For example, the policy configuration request message includes the network slice switching policy, and the policy configuration request message is used to request configuration (or creation) of the network slice switching policy. Correspondingly, the slice selection network element receives the policy configuration request message and obtains the network slice switching policy from the policy configuration request message. Then the slice selection network element creates (or saves) the network slice switching policy locally.
[0125] It should be understood that the slice selection network element can subscribe to the resource information of the original network slice from the network slice management function network element after the network slice switching policy is configured. That is, S602 can be executed after S604.
[0126] The following exemplary describes an implementation of the slice selection network element determining whether to switch the terminal device on the original network slice to the target network slice according to the resource information of the original network slice and the network slice switching policy.
[0127] Exemplarily, after receiving the resource information of the original network slice from the network slice management function network element, the slice selection network element determines the network slice switching policy corresponding to the original network slice according to the identifier of the original network slice. The network slice switching policy includes the trigger condition of switching the network slice, the identifier of the target network slice, the identifier of the original network slice, and the identifier and / or application identifier of the terminal device on the original network slice. The following exemplary describes the network slice switching policy and whether the slice selection network element judges to switch the network slice of the terminal device according to the network slice switching policy:
[0128] When the resource information of the original network slice meets the trigger condition of switching the network slice, the slice selection network element determines to switch the terminal device on the original network slice to the target network slice. The trigger condition of switching the network slice can include one or more of the following: the performance indicator of the network slice is greater than or equal to a first threshold value or less than or equal to a second threshold value; the slice selection network element receives the alarm information of the network slice; the slice selection network element receives the performance indicator of the network slice; the slice selection network element receives the alarm information of the network slice, and the alarm information is a high priority alarm; the analysis report of the network slice meets the switching condition, for example, the network slice can have a high load (or the load is greater than a threshold value) within 1 hour.
[0129] It should be understood that the first threshold value and the second threshold value described above can be threshold values representing different meanings, for example, the first threshold value is a delay threshold value, the second threshold value is a bandwidth threshold value, the performance indicator corresponding to the first threshold value is delay, and the performance indicator corresponding to the second threshold value is bandwidth. That is, the trigger condition of switching the network slice can include that the delay of the network slice is greater than or equal to the delay threshold value, or the bandwidth of the network slice is less than the bandwidth threshold value.
[0130] For example, the resource information of the original network slice includes the physical resource alarm of the original network slice, and the trigger condition of switching the network slice includes that the slice selection network element receives the alarm information of the network slice. The slice selection network element can determine to switch the terminal device on the original network slice to the target network slice.
[0131] For another example, the resource information of the original network slice includes that the delay of the original network slice is 90 ms, and the trigger condition of switching the network slice includes that the delay of the original network slice is greater than 100 ms. The slice selection network element can determine not to switch the terminal device on the original network slice to the target network slice.
[0132] For another example, the resource information of the original network slice includes that the utilization of the original network slice is 70%, and the trigger condition of the switching network slice includes that the slice selection network element receives the performance index of the network slice, and then the slice selection network element can determine to switch the terminal device on the original network slice to the target network slice.
[0133] For another example, the resource information of the original network slice includes a power-off alarm, and the trigger condition of the switching network slice includes that the alarm information of the network slice is received, and the alarm information is high-priority alarm, and then the original network slice determines whether the power-off alarm is high-priority alarm according to the high-priority alarm information list preset locally, and if yes, the slice selection network element can determine to switch the terminal device on the original network slice to the target network slice.
[0134] Optionally, in the case that the resource information of the original network slice meets the trigger condition, the slice selection network element can directly determine to switch the terminal device on the original network slice to the target network slice. For example, the target network slice is a backup and unused network slice, and thus when the resource information of the original network slice meets the trigger condition of the switching network slice, it can be determined by default that the target network slice can meet the demand, and the terminal device on the original network slice is directly switched to the target network slice.
[0135] Alternatively, in the case that the resource information of the original network slice meets the trigger condition, the slice selection network element can further determine whether the target network slice meets the trigger condition, and in the case that the target network slice does not meet the trigger condition of the switching network slice, it indicates that the target network slice can meet the switching demand, and then the slice selection network element determines to switch the terminal device on the original network slice to the target network slice.
[0136] In an implementation, in a case that the resource information of the original network slice meets the triggering condition, the slice selection network element sends a resource information request message to the network slice management function network element, the resource information request message comprising an identity of the target network slice, the resource information request message being used to request resource information of the target network slice, the resource information can comprise one or more of performance indicators, alarm information, or analysis report of the target network slice. After the network slice management function network element receives the resource information request message from the slice selection network element, the network slice management function network element sends the resource information of the target network slice to the slice selection network element. Then the slice selection network element judges whether the resource information of the target network slice meets the triggering condition of switching network slice, in a case that the resource information of the target network slice does not meet the triggering condition of switching network slice, the slice selection network element determines to switch the terminal device on the original network slice to the target network slice.
[0137] In another implementation, the slice selection network element can pre-subscribe the resource information of the target network slice from the network slice management function network element, the specific process is similar to S602, the difference is only that S602 is to subscribe the resource information of the original network slice, here is to subscribe the resource information of the target network slice, therefore, here is not described again. It should be understood that the slice selection network element can subscribe the resource information of the original network slice and the resource information of the target network slice at the same time, that is, the slice selection network element can subscribe the resource information of the original network slice and the resource information of the target network slice from the network slice management function network element at the same time in S602. Therefore, in this implementation, in a case that the resource information of the original network slice meets the triggering condition, if the slice selection network element does not receive the resource information of the target network slice, or the resource information of the target network slice does not meet the triggering condition of switching network slice, the slice selection network element determines to switch the terminal device on the original network slice to the target network slice.
[0138] Optionally, S605, the slice selection network element sends a network slice configuration request message to the network slice capability management service providing network element.
[0139] Exemplarily, when the slice selection network element determines to switch the terminal device on the original network slice to the target network slice, the slice selection network element sends a network slice configuration request message to the network slice capability management service providing network element, the network slice configuration request message comprising an identity of the target network slice, and an identity of the terminal device and / or an application identity on the original network slice. The network slice configuration request message is used to request to configure the target network slice for the terminal device on the original network slice.
[0140] Correspondingly, the network slice capability management service providing network element receives a network slice configuration request message from the slice selection network element, and according to the network slice configuration request message, the network slice capability management service providing network element modifies the network slice configuration of the terminal device on the original network slice by calling a core network interface. The specific process can refer to the related content of the existing protocol, and the present application does not limit this.
[0141] After the configuration is successful, the network slice capability management service providing network element sends a network slice configuration response message to the slice selection network element, and the network slice configuration response message is used to indicate that the configuration of the target network slice for the terminal device on the original network slice is successful.
[0142] Correspondingly, the slice selection network element receives a network slice configuration response message from the network slice capability management service providing network element, and according to the network slice configuration response message, the slice selection network element updates the association between the identifier of the target network slice and the identifier of the terminal device on the original network slice locally. Then, optionally,
[0143] S606, the slice selection network element sends a network slice configuration feedback message to the application server, and the network slice configuration feedback message includes the identifier of the target network slice and the identifier of the terminal device on the original network slice.
[0144] Correspondingly, the slice selection network element receives a network slice configuration feedback message from the application server. If the network slice configuration feedback message includes the identifier of the target network slice and the identifier of the terminal device on the original network slice, the application server can determine that the terminal device on the original network slice switches to the target network slice.
[0145] Optionally, in this case, the application server can generate a new network slice switching policy, and instruct the slice selection network element to modify or replace the network slice switching policy through a policy modification procedure. For example, the application server generates a new network slice switching policy, which includes a new switching network slice trigger condition, an identity of a new target network slice, an identity of a new original network slice, an identity of a terminal device on the new original network slice, and the like. It should be understood that the new original network slice here is the target network slice in the above embodiment, and the terminal device on the new original network slice here is the terminal device on the original network slice in the above embodiment. The new switching network slice trigger condition here can be the same as or different from the previous switching network slice trigger condition, which is not limited in the present application. Then, the application server sends a policy modification request message to the switching selection network element, the policy modification request message including the new network slice switching policy and an identity of the original network slice switching policy. After receiving the policy modification request message from the application server, the switching selection network element replaces the local network slice switching policy with the new network slice switching policy.
[0146] The application function network element can also configure a new network slice switching policy to the slice selection network element through a policy configuration procedure. In this case, the application function network element can also instruct the slice selection network element to delete the original network slice switching policy through a policy deletion procedure.
[0147] If the slice selection network element determines not to switch the terminal device on the original network slice to the target network slice at S603, or in other words, when the target network element slice meets the switching network slice trigger condition, or in other words, when the target network slice cannot meet the switching requirement, the slice selection network element can directly send a network slice configuration feedback message to the application server.
[0148] Exemplarily, in this case, the network slice configuration feedback message includes an identity of the original network slice, and the network slice configuration feedback message is used to indicate that the network slice switching for the terminal device on the original network slice is not successful, or in other words, the network slice configuration feedback message is used to indicate that the target network element slice cannot meet the switching requirement, or in other words, the network slice configuration feedback message is used to indicate that the target network slice meets the switching network slice trigger condition. Optionally, the network slice configuration feedback message can also include a reason value, which is used to indicate the reason why the network slice switching is not successful, for example, the utilization rate of the target network slice is greater than a threshold.
[0149] Correspondingly, the application server receives the network slice configuration feedback message from the slice selection network element, and determines that the switching of the terminal device performing the network slice on the original network slice is not successful according to the network slice configuration feedback message. Optionally, the application server can also perform some countermeasures according to the cause value. For example, when the cause value indicates that the reason why the network slice switching is not successful is that the utilization rate of the target network slice is greater than a threshold, the application server can modify the network slice switching strategy, so that part of the terminal devices on the original network slice are switched to the target network slice. For example, the application server sends a policy modification request message to the slice selection network element, and the policy modification request message carries the modified network slice switching strategy. Correspondingly, the slice selection network element receives the policy modification request message from the application server, and then replaces the original network slice switching strategy with the network slice switching strategy carried in the policy modification request message. Alternatively, the application server can also carry the identifier of the network slice switching strategy and the modification indication information in the policy modification request message, and the modification indication information is used to indicate that the network slice switching strategy is modified. The slice selection network element can modify the local network slice switching strategy according to the modification indication information.
[0150] Based on the above scheme, the slice selection network element can determine whether to switch the terminal device performing the network slice on the original network slice according to the resource information of the original network slice and the network slice switching strategy, so as to guarantee the service experience of the terminal device after the network slice switching.
[0151] Figure 6 The method 600 in the above embodiment describes a method for switching network slices provided by the present application. The following is based on the 5G architecture, and the method 600 is combined with the method 700 in the above embodiment to describe the method 600. Figure 7 The method 700 in the above embodiment describes a preferred embodiment of the application applied to the 5G architecture. The method 700 includes the following steps:
[0152] S701, the NSMF sends a network slice notification message to the slice selection network element.
[0153] Exemplarily, the NSMF sends a network slice notification message to the slice selection network element, the network slice notification message includes the resource information of the original network slice, the network slice notification message includes the identifier of the original network slice, and the resource information of the original network slice can include one or more of the following information: network slice key performance indicator (KPI), network slice alarm, and network slice analysis report.
[0154] Table 2
[0155]
[0156] For ease of illustration, Table 2 lists three kinds of information that the resource information of the original network slice can include. The three kinds of information are introduced respectively as follows in combination with Table 2:
[0157] (1) Network slice KPI (S-NSSAI KPI): The network slice KPI includes one or more performance parameters of the original network slice, such as latency, throughput, utilization, etc. of the original network element slice. The network slice KPI can be used to evaluate the performance or resource status of the original network slice.
[0158] (2) Network slice alarm (S-NSSAI Alarm): The network slice alarm is a kind of alarm information used when the original network slice fails or cannot be used, which can be a physical resource alarm, or a network slice instance (NSI) alarm, or a network slice alarm, etc.
[0159] (3) Network slice analysis report: The network slice analysis report can be an analysis report and / or a recommended behavior obtained by the MDAS component in the NSMF through analysis of the original network slice. The network slice analysis report can include one or more of the following analysis reports, for example: end-to-end latency analysis (E2E latency analysis) report, network slice load analysis (Network slice load anyalysis for S-NSSAI) report, service experience analysis (Service experience analysis) report, KPI anomaly analysis (KPI anomaly analysis) report, etc.
[0160] S702, the slice selection network element determines whether to perform network slice switching for the UE on the original network slice according to the resource information of the original network slice and the network slice switching policy.
[0161] Exemplarily, the slice selection network element receives the network slice notification message from the NSMF, and then determines whether to perform network slice switching for the UE on the original network slice according to the resource information of the original network slice in the network slice notification message and the network slice switching policy, or in other words, determines whether to switch the UE on the original network slice to the target network slice.
[0162] The network slice switching policy is used for the slice selection network element to automatically switch the network slice, or the network slice switching policy is used for the slice selection network element to determine whether to switch the network slice for the UE on the original network slice, or the network slice switching policy is used for the slice selection network element to determine whether to switch the UE on the network slice to the target network slice.
[0163] It should be understood that the network slice switching policy can be created by a vertical industry or a network operator and pre-configured to the slice selection network element, or initially pre-configured in the slice selection network element, which is not limited in the present application.
[0164] Table 3 lists the contents that can be included in the network slice switching policy.
[0165] Table 3
[0166]
[0167] As can be seen from Table 3, the network slice switching policy includes a policy identifier (Policy ID), which is used to identify the network slice switching policy, or the Policy ID is used to distinguish different network slice switching policies.
[0168] The network slice switching policy also includes a condition, which is used to indicate the trigger condition for switching the network slice for the UE, or the field is used to indicate the trigger condition for switching the UE to the target network slice. The trigger condition may, for example, include one or more of the following:
[0169] (1) The network slice KPI exceeds the set threshold. The network slice KPI can be any one or more network slice KPIs, such as network slice latency, throughput, utilization, etc. For example, the network slice latency is greater than or equal to 100 ms, and / or the maximum number of connections of the network slice is greater than or equal to 1000.
[0170] (2) The slice selection network element receives a high priority alarm, or the resource information of the original network slice includes a high priority alarm. The high priority alarm may, for example, be a network element failure alarm, a network element power failure alarm, etc.
[0171] (3) The network slice analysis report reaches the set condition. For example, the network slice analysis report predicts that the network resource occupancy rate will exceed the threshold in a certain period of time.
[0172] (4) The slice selection network element receives the alarm information and / or KPI of the original network slice. Or, the resource information of the original network slice includes the alarm information or KPI.
[0173] When one or more of the above trigger conditions are met, the UE on the original network slice can be switched to the target network slice.
[0174] The network slice switching policy can further comprise an identity of the original network slice, which is associated with the network slice switching policy, or in other words, the network slice switching policy is for UEs on the original network slice, or in other words, the network slice switching policy is a policy for instructing UEs on the original network slice to switch network slices. The identity of the original network slice can comprise an identity of one or more network slices.
[0175] The network slice switching policy can further comprise an identity of the target network slice, or in other words, an identity of the network slice to which the UE is to be switched, or in other words, an identity of the backup network slice. When one or more of the above trigger conditions for switching network slices are met, the UE on the network slice can be switched to the target network slice.
[0176] Optionally, the network slice switching policy can further comprise a target DNN, or in other words, a data network name to which the UE is to be switched. When one or more of the above trigger conditions for switching network slices are met, the UE on the network slice can be switched to the data network corresponding to the target DNN.
[0177] The network slice switching policy can further comprise a List of VAL UE ID(s), or in other words, a list of identities of VAL UEs on the original network slice, or in other words, a list of identities of VAL UEs that need to switch network slices. It should be understood that the List of VAL UE ID(s) can comprise identities of all UEs on the original network slice, or can only comprise identities of part of the UEs on the original network slice, which is not limited in the present application. The List of VAL UE ID(s) can comprise an identity of one or more UEs. When one or more of the above trigger conditions for switching network slices are met, the UEs in the List of VAL UE ID(s) can be switched to the target network slice.
[0178] The network slice switching policy can further comprise a VAL Service ID, or in other words, an identity of a service (or application) corresponding to the original network slice, or in other words, an identity of a service (or application) that needs to switch network slices. When one or more of the above trigger conditions for switching network slices are met, the VAL UEs corresponding to the service (or application) identity can be switched to the target network slice.
[0179] It should be understood that in some implementations, the network slice switching policy can only comprise one of the List of VAL UE ID(s) and the VAL Service ID, or can comprise both, which is not limited in the present application.
[0180] In S702, after the slice selection network element obtains the resource information of the network slice through the network slice notification message, it determines whether to switch the UE on the original network slice (i.e., the UE corresponding to the VAL UE identification list) to the target network slice or whether to switch the network slice for the UE of the network slice, in combination with the network slice switching strategy. As a possible implementation manner, when the resource information of the original network slice meets the triggering condition for switching the network slice, the UE of the original network slice can be switched to the target network slice. The following is an example:
[0181] In an example, the slice selection network element receives a network slice notification message from the NSMF, which includes the identification of the network slice, the network slice KPI, and the network slice alarm. The network slice KPI is a time delay of 90 ms, the network slice alarm is a physical resource alarm, and the identification is a high priority alarm. The slice management network element is pre-configured with a network slice switching strategy. The triggering condition for switching the network slice in the network slice switching strategy is that the time delay of the network slice is greater than 100 ms, and / or a high priority alarm information is received. In this case, since the network slice notification message carries the high priority physical resource alarm information, the slice selection network element switches the VAL UE (or the UE corresponding to the VAL service ID) in the List of VAL UE ID(s) to the target network slice.
[0182] In another example, the slice selection network element receives a network slice notification message from the NSMF, which includes the identification of the original network slice and the network slice analysis report. The network slice analysis report includes a network slice load analysis report, which shows that the load of the original network slice will be greater than a threshold value after 10 minutes in the future. The slice management network element is pre-configured with a network slice switching strategy. The triggering condition for switching the network slice in the network slice switching strategy is that the network slice analysis report meets a set condition, where the condition is that the load of the network slice in a certain time period is greater than a threshold value. In this case, since the network slice analysis report in the network slice notification message meets the triggering condition for switching the network slice, the slice selection network element switches the VAL UE (or the UE corresponding to the VAL service ID) in the List of VAL UE ID(s) to the target network slice.
[0183] Optionally, if the resource information of the original network slice meets the triggering conditions, the slice selection network element can further determine whether the target network slice meets the triggering conditions for switching network slices. Only if the resource information of the target network slice does not meet the triggering conditions for switching network slices will the slice selection network element switch the UE on the original network slice to the target network slice. Optionally, the slice selection network element can obtain the resource information of the target network slice through NSMF; the specific method is not limited in this application.
[0184] S703, the slice selection network element sends a network slice configuration request message to the NSCM service providing network element.
[0185] For example, when it is determined that a UE on the original network slice will be switched to the target network slice, the slice selection network element sends a network slice configuration request message to the NSCM service providing network element. The network slice configuration request message includes the identifier of the target network slice and a List of VAL UE ID(s) or VAL Service ID. The network slice configuration request message is used to request the configuration of the target network slice for the UE corresponding to the List of VAL UE ID(s) or VAL Service ID.
[0186] S704, NSCM service provides network elements with the ability to modify network slice configuration for UE through 5GC.
[0187] For example, after receiving a network slice configuration request message from the slice selection network element, the NSCM service providing network element modifies the network slice configuration of the UE corresponding to the List of VAL UE ID(s) or VALService ID by calling the core network interface (which may be an existing 3GPP interface). The specific process can be found in the relevant content of existing protocols, and this application does not limit it.
[0188] S705, 5GC provides network element-based network slice configuration response messages to the NSCM service.
[0189] S706, the NSCM service provides network elements with the ability to send network slice configuration response messages to the slice selection network elements.
[0190] For example, after the 5GC completes the modification of the network slice configuration, it sends a network slice configuration response message to the NSCM. This response message indicates whether the network slice configuration modification was successful. After receiving the network slice configuration response message, the NSCM service-providing network element sends it to the slice selection network element.
[0191] S707, the network element selection update of the mapping relationship between the UE and the network slice.
[0192] Exemplarily, in a possible implementation, the slice selection network element receives a network slice configuration response message from the NSCM service providing network element, and if the network slice configuration response message indicates that the network slice configuration modification of the UE is successful, the slice selection network element updates the mapping relationship between the UE and the target network slice, which can be an association relationship between the identifier of the UE (VAL UE ID) and the identifier of the target network slice. It should be understood that the mapping relationship between the UE and the target network slice updated by the slice selection network element herein can refer to associating the identifier of the VAL UE and the identifier of the target network slice, or updating the association relationship between the identifier of the UE and the identifier of the original network slice to the association relationship between the identifier of the UE and the identifier of the target network slice.
[0193] In another possible implementation, the slice selection network element receives a network slice configuration response message from the NSCM service providing network element, and if the network slice configuration response message indicates that the network slice configuration modification of the VAL service (or the UE corresponding to the VAL service) is successful, the slice selection network element updates the mapping relationship between the VAL service and the target network slice, which can be an association relationship between the VAL service ID and the identifier of the target network slice.
[0194] S708, the slice selection network element sends a network slice configuration feedback message to the VAL server.
[0195] Exemplarily, after the slice selection network element updates the mapping relationship between the VAL UE (or the VAL service) and the identifier of the target network slice, the slice selection network element sends a network slice configuration feedback message to the VAL server, and the network slice configuration feedback message includes the identifier of the UE (or the VAL service ID) and the identifier of the target network slice.
[0196] Therefore, in the above scheme, the slice selection network element can determine whether to perform network slice switching for the UE according to the resource information of the network slice and the network slice switching policy, or in other words, can determine whether to switch the UE to the target network slice, or in other words, determine the target network slice for the network slice switching of the UE, thereby realizing the capability of automatic network slice switching.
[0197] Meanwhile, when the slice selection network element performs network slice switching for the UE, the resource information of the network slice is considered, so that the reliability and availability of the business of the vertical industry after the network slice switching can be ensured.
[0198] In the method 700, when the slice selection network element determines to switch the terminal device on the original network slice to the target network slice, the slice selection network element requests the NSCM service providing network element to configure the network slice for the terminal device on the original network slice. However, if the slice selection network element does not switch the terminal device on the original network slice to the target network slice because the target network slice does not meet the switching condition (for example, the resource information of the target network slice meets the trigger condition of switching the network slice), the service experience of the terminal device may be affected. In view of this, Figure 8 An exemplary flowchart of the method 800 provided by the embodiments of the present application is shown. In the method 800, when the slice selection network element informs the VAL server of the failure of network slice switching for the terminal device on the original network slice, the VAL server can formulate a coping strategy to guarantee the service experience of the terminal device. It should be understood that the method 800 can be independently implemented, or can be implemented in combination with the method 700, which is not limited herein. The method 800 includes the following steps:
[0199] S801, the NSMF sends a network slice notification message to the slice selection network element.
[0200] It should be understood that S801 is similar to S701 in the method 700, and will not be repeated here for brevity.
[0201] S802, the slice selection network element determines whether to switch the network slice for the UE on the network slice according to the resource information of the network slice and the network slice switching strategy.
[0202] Exemplarily, after the slice selection network element receives the resource information of the network slice through the network slice notification message, it determines whether to switch the network slice for the UE on the network slice in combination with the network slice switching strategy. The related description about the network slice switching strategy can be referred to the S702 part of the method 700, which will not be repeated here.
[0203] S803, the slice selection network element sends a network slice configuration feedback message to the VAL server.
[0204] Exemplarily, when the UE on the original network slice fails to switch to the target network slice, for example, due to that the resource information of the target network slice meets the trigger condition of switching network slice, or in other words, the target network slice does not meet the switching requirement, resulting in that the UE on the original network slice cannot be switched to the target network slice, the slice selection network element sends a network slice configuration feedback message to the VAL server, the network slice configuration feedback message being used to indicate that the network slice switching of the UE on the original network slice fails, or in other words, the network slice configuration feedback message is used to indicate that the UE on the original network slice fails to be switched to the target network slice. It should be understood that the trigger condition of switching network slice used for judging the resource information of the target network slice and the trigger condition of switching network slice used for judging the resource information of the original network slice can be the same, that is, only one trigger condition of switching network slice can be configured in the network slice switching strategy. Alternatively, the network slice configuration feedback message can further include the reason for the network slice switching failure and / or the recommended behavior.
[0205] For the convenience of description, Table 4 lists the contents that can be included in the network slice configuration feedback message.
[0206] Table 4
[0207]
[0208] The above several pieces of information will be described in combination with Table 4 as follows:
[0209] The network slice configuration feedback message includes a network slice switching result, the network slice switching result indicating that the network slice switching fails.
[0210] Alternatively, the network slice configuration feedback message includes a failure reason value, the failure reason value being used to indicate the specific reason for the network slice switching failure. For example, the failure reason value is that the target network slice has too high load; for another example, the failure reason value is that the target network slice cannot meet the service requirements of all UEs of the original network slice due to that the number of UEs of the original network slice is too large (or the performance requirement is too high).
[0211] Alternatively, the network slice configuration feedback message can further indicate a recommended behavior, that is, a subsequent behavior that can be performed by the vertical industry server, for example: the recommended behavior is to modify the target network slice order (or upgrade the target network slice configuration); for another example, the recommended behavior is to modify the network slice switching strategy, such as grouping the UEs to be switched and switching a part (for example, 60%) of the UEs to the target network slice.
[0212] Correspondingly, the VAL server receives the network slice configuration feedback message from the slice selection network element. The VAL server can formulate a subsequent policy according to the network slice configuration feedback message. For example, the network slice configuration feedback message carries a cause value, and the cause value indicates that the reason for the handover failure is that the target network slice is too high in load. Then the VAL server can modify the network slice handover policy by adding one or more target network element slices (or replacing the original target network slice) in the network slice handover policy. For another example, the network slice configuration feedback message carries a cause value, and the cause value indicates that the reason for the handover failure is that the target network slice cannot meet the service requirements of all UEs on the original network slice. Then the VAL server can modify the network slice handover policy by modifying the List of VAL UE ID(s) in the network slice handover policy (for example, only keeping the identifiers of 60% of the UEs).
[0213] Therefore, in the above scheme, if the network slice handover fails, or in other words, if the target network slice cannot meet the network slice handover requirements, the slice selection network element can notify the VAL server of the result, and can also notify the VAL server of the cause of the failure and the recommended behavior, so that the VAL server can reformulate the network slice handover policy.
[0214] Figure 9 An exemplary flowchart of the method 900 provided by the embodiments of the present application is shown. It should be understood that the method 900 can be independently implemented, or can be implemented in combination with the method 00 or the method 800, which is not limited by the present application. The method 900 can include the following steps:
[0215] S901, the NSCM service consumption network element / VAL server sends a policy configuration / modification / query / deletion request message to the slice selection network element.
[0216] An exemplary scheme, the NSCM service consumption network element, or the VAL server sends a policy configuration request message (or also can be called a policy creation request message, which is not limited herein) to the slice selection network element, the policy configuration request message includes a network slice handover policy, and the policy configuration request message is used to configure the network slice handover policy. The network slice handover policy can be a policy for determining whether to perform network slice handover on a UE, which is not limited by the embodiments. For example, the network slice handover policy is similar to the network slice handover policy described in S702 of the method 700, which is not repeated here.
[0217] In another example, the NSCM service consumer or the VAL server sends a policy modification request message to the slice selection network element, the policy modification request message including an identifier of the network slice switching policy and policy modification information, the policy modification request message being used to request modification or update of the network slice switching policy. The policy modification information can be a modified network slice switching policy, in which case the slice selection network element can directly replace the original network slice switching policy with the modified network slice switching policy. Alternatively, the policy modification information can be used to indicate specific modification content, such as modification of a trigger condition for switching network slices or an identifier of an original network slice.
[0218] In another example, the NSCM service consumer or the VAL server sends a policy modification request message to the slice selection network element, the policy modification request message including an identifier of the network slice switching policy and policy modification information, the policy modification request message being used to request modification or update of the network slice switching policy. The policy modification information can be a modified network slice switching policy, in which case the slice selection network element can directly replace the original network slice switching policy with the modified network slice switching policy. Alternatively, the policy modification information can be used to indicate specific modification content, such as modification of a trigger condition for switching network slices or an identifier of an original network slice.
[0219] In another example, the NSCM service consumer or the VAL server sends a policy modification request message to the slice selection network element, the policy modification request message including an identifier of the network slice switching policy and policy modification information, the policy modification request message being used to request modification or update of the network slice switching policy. The policy modification information can be a modified network slice switching policy, in which case the slice selection network element can directly replace the original network slice switching policy with the modified network slice switching policy. Alternatively, the policy modification information can be used to indicate specific modification content, such as modification of a trigger condition for switching network slices or an identifier of an original network slice.
[0220] In another example, the NSCM service consumer or the VAL server sends a policy modification request message to the slice selection network element, the policy modification request message including an identifier of the network slice switching policy and policy modification information, the policy modification request message being used to request modification or update of the network slice switching policy. The policy modification information can be a modified network slice switching policy, in which case the slice selection network element can directly replace the original network slice switching policy with the modified network slice switching policy. Alternatively, the policy modification information can be used to indicate specific modification content, such as modification of a trigger condition for switching network slices or an identifier of an original network slice.
[0221] In another example, the NSCM service consumer or the VAL server sends a policy modification request message to the slice selection network element, the policy modification request message including an identifier of the network slice switching policy and policy modification information, the policy modification request message being used to request modification or update of the network slice switching policy. The policy modification information can be a modified network slice switching policy, in which case the slice selection network element can directly replace the original network slice switching policy with the modified network slice switching policy. Alternatively, the policy modification information can be used to indicate specific modification content, such as modification of a trigger condition for switching network slices or an identifier of an original network slice.
[0222] In another example, the NSCM service consumer or the VAL server sends a policy modification request message to the slice selection network element, the policy modification request message including an identifier of the network slice switching policy and policy modification information, the policy modification request message being used to request modification or update of the network slice switching policy. The policy modification information can be a modified network slice switching policy, in which case the slice selection network element can directly replace the original network slice switching policy with the modified network slice switching policy. Alternatively, the policy modification information can be used to indicate specific modification content, such as modification of a trigger condition for switching network slices or an identifier of an original network slice.
[0223] In another example, the slice selection network element receives a policy query request message from the NSCM service consumer network element / VAL server, the policy query request message including an identifier of a network slice switching policy, and the slice selection network element locally searches for the network slice switching policy according to the identifier, and if the search is successful, the slice selection network element sends the network slice switching policy to the NSCM service consumer network element / VAL server through a network slice query response message.
[0224] In another example, the slice selection network element receives a policy deletion request message from the NSCM service consumer network element / VAL server, the policy deletion request message including an identifier of a network slice switching policy, and the slice selection network element deletes the network slice switching policy in the local storage according to the policy deletion request message.
[0225] S903, the slice selection network element sends a policy configuration / modification / query / deletion response message to the NSCM service consumer network element / VAL server.
[0226] In an example, after S902 is performed, the slice selection network element sends a policy configuration / modification / query / deletion response message to the NSCM service consumer network element / VAL server, the policy configuration / modification / query / deletion response message including an indication of success or failure of the operation. However, it should be noted that for a network slice switching policy query response message, the response message can also carry the network slice switching policy queried by the slice selection network element.
[0227] Therefore, in the above examples, the interface for configuration / modification / query / deletion of the network slice switching policy is defined, or in other words, the capability of the NSCM service consumer network element / VAL server for configuration / modification / query / deletion of the network slice switching policy is defined, so that the NSCM service consumer network element / VAL server can perform the configuration / modification / query / deletion operation of the network slice switching policy through the slice selection network element.
[0228] Figure 10 An example flowchart of a method 1000 for switching network slices is shown. The method 1000 includes the following steps:
[0229] S1001: The NSCM service consumer network element / VAL server sends a policy configuration request message to the slice selector.
[0230] S1002, the slice selection network element configures a network slice switching policy.
[0231] It should be understood that S1001 and S1002 are similar to the network slice switching policy configuration process in S901 and S902 in method 900, and will not be repeated here.
[0232] S1003, the slice selection network element sends a subscription request message to the NSMF.
[0233] Exemplarily, the slice selection network element can send a subscription request message to the NSMF after creating the network slice switching policy, the subscription request message including the identification of the original network slice, the subscription request message being used to request subscription of resource information of the original network slice, the resource information can include one or more of the following information: network slice alarm, network slice key performance indicator, network slice analysis report. The slice selection network element can carry information in the subscription request message to indicate the type of subscription, for example, the slice selection network element indicates in the subscription request message that the network slice alarm is subscribed; or the default mode can also be used, for example, if the slice selection network element does not indicate the type of subscription in the subscription request message, then the network slice alarm is subscribed by default.
[0234] The specific implementation of the slice selection network element subscribing to the resource information of the three types of network slices will be exemplarily described below.
[0235] (1) Network slice alarm subscription:
[0236] The slice selection network element can subscribe to the network slice alarm from the NSMF. When the original network slice has an alarm (or a high priority alarm) condition, the NSMF sends alarm information to the slice selection network element. The alarm condition here can include network slice alarm, or NSI alarm, etc.
[0237] Optionally, the slice selection network element can indicate the condition of the alarm, for example, the slice selection network element adds indication information of the alarm condition in the subscription request message, for example, when the network slice is powered off, the alarm is triggered.
[0238] (2) Network slice key performance indicator subscription:
[0239] The slice selection network element can subscribe to the network slice KPI from the NSMF, which can include the latency, throughput, utilization, etc. of the original network slice.
[0240] Optionally, the slice selection network element can indicate to the NSMF the condition for reporting the network slice KPI. For example, the slice selection network element adds a KPI threshold, such as a delay threshold, in the subscription request message, and when the delay of the original network slice is greater than or equal to the delay threshold, the NSMF reports the delay of the original network slice to the slice selection network element. The network slice KPI reported by the NSMF to the network slice selection network element in this implementation manner can also be regarded as a kind of alarm information (KPI alarm), and when the slice selection network element receives the network slice KPI and the target network slice also meets the demand, the UE on the original network slice can be switched to the target network slice.
[0241] Optionally, the slice selection network element can indicate to the NSMF the time interval for reporting the network slice KPI. For example, the slice selection network element indicates in the subscription request message that the NSMF actively reports the delay of the original network slice every 10 minutes. In this implementation manner, when the slice selection network element receives the network slice KPI from the NSMF, whether the network slice KPI meets the switching policy of the network slice can be judged according to the network slice switching policy.
[0242] (3) Network slice analysis report subscription:
[0243] The slice selection network element can subscribe to the network slice analysis report from the NSMF, and the network slice analysis report can include the report and recommended behavior of the NSMF on the network slice. When the NSMF makes an analysis report on the original network slice according to the strategy of the operator or other conditions, the network slice analysis report of the original network slice needs to be reported to the slice selection network element.
[0244] Optionally, the slice selection network element can indicate to the NSMF the time interval for reporting the network slice analysis report. For example, the slice selection network element indicates in the subscription request message that the NSMF actively reports the analysis report of the original network slice every 10 minutes. In this implementation manner, when the slice selection network element receives the network slice analysis report from the NSMF, whether the network slice analysis report meets the switching policy of the network slice can be judged according to the network slice switching policy.
[0245] Optionally, the subscription request message can also include the identification of the target network slice. That is, the slice selection network element can request to subscribe to the resource information of the target network slice through the subscription request message. The specific mode can be similar to the mode of subscribing to the resource information of the original network slice, which will not be described here.
[0246] S1004, the NSMF sends a subscription response message to the slice selection network element.
[0247] Exemplarily, after receiving the subscription request message from the slice selection network element, the NSMF can send a subscription response message to the slice selection network element, where the subscription response message is used to indicate that the subscription is successful.
[0248] Optionally, if the NSCM service consumption network element / VAL server indicates the slice selection network element to modify or update the network slice switching policy after S1004, the slice selection network element can re-subscribe the resource information of the original network slice and / or the target network slice from the NSMF. For example:
[0249] The slice selection network element receives a policy modification request message from the NSCM service consumption network element / VAL server, where the policy modification request message includes the network slice switching policy and policy modification information, and the policy modification information indicates that the identification of the original network slice in the original network slice switching policy is modified (for example, the identification of the original network slice is modified from “UE1, UE2, UE3” to “UE1”). According to the policy modification request message, the slice selection network element sends a subscription request message to the NSMF, where the subscription request message includes the modified identification of the original network slice, and the subscription request message is used to request to subscribe the resource information of the modified original network slice.
[0250] Optionally, S1005, the slice selection network element receives a network policy deletion request message from the NSCM service consumption network element / VAL server.
[0251] Optionally, S1006, the slice selection network element deletes the network slice switching policy.
[0252] It should be understood that S1005 and S1006 are similar to the network slice switching policy deletion process in S901 and S902 in method 900, and will not be repeated here.
[0253] Optionally, S1007, the slice selection network element sends a unsubscription request message to the NSMF.
[0254] Exemplarily, after receiving the network slice switching policy deletion request message from the NSCM service consumption network element / VAL server, the slice selection network element can send a unsubscription request message to the NSMF, where the unsubscription request message is used to unsubscribe the resource information of the original network slice (optionally, the target network slice can also be included).
[0255] Optionally, S1008, the NSMF sends a unsubscription response message to the slice selection network element.
[0256] Exemplarily, after receiving the unsubscription request message from the slice selection network element, the NSMF can send a unsubscription response message to the slice selection network element, where the unsubscription response message is used to indicate that the unsubscription is successful.
[0257] Therefore, in the above solution, the slice selection network element can first subscribe to the resource information of the original network slice from the NSMF, so that the slice selection network element can determine whether the UE on the original network slice can be switched to the target network slice according to the resource information of the original network slice, so as to guarantee the service experience of the UE after the network slice switching.
[0258] Corresponding to the method given in each of the method embodiments, the embodiments of the present application also provide a corresponding device, which includes a module for executing the corresponding modules of each of the above method embodiments. The module can be software, hardware, or a combination of software and hardware. It can be understood that the technical features described in the above method embodiments are also applicable to the following device embodiments.
[0259] Figure 11 is a schematic block diagram of a device for switching network slices provided by the embodiments of the present application. The device 10 includes a transceiver module 11 and a processing module 12. The transceiver module 11 can be used to implement the corresponding communication function. The transceiver module 11 can also be referred to as a communication interface or a communication unit. The processing module 12 can be used to implement the corresponding processing function.
[0260] Optionally, the device 10 can also include a storage module, which can be used to store instructions and / or data. The processing module 12 can read the instructions and / or data in the storage module, so that the device implements the actions of the equipment or network element in each of the above method embodiments.
[0261] In one design, the device 10 can be the slice selection network element in the above embodiments, or a component (such as a chip) of the slice selection network element. The device 10 can implement the steps or processes corresponding to the steps or processes performed by the slice selection network element in the above method embodiments, wherein the transceiver module 11 can be used to perform the transceiver-related operations of the slice selection network element in the above method embodiments, and the processing module 12 can be used to perform the processing-related operations of the slice selection network element in the above method embodiments.
[0262] In a first possible implementation, the transceiver module 11 is configured to receive resource information of an original network slice from a network slice management function network element, the resource information of the original network slice including one or more of the following information: performance indicators of the original network slice, alarm information of the original network slice, and an analysis report for the original network slice; and the processing module 12 is configured to determine whether to switch a terminal device on the original network slice to a target network slice according to the resource information of the original network slice and a network slice switching policy, the network slice switching policy including a trigger condition for switching network slices, an identifier of the target network slice, an identifier of the original network slice, and an identifier of the terminal device and / or an application identifier on the original network slice.
[0263] Optionally, the processing module 12 is specifically configured to determine whether the resource information of the network slice meets a triggering condition of switching the network slice; and in a case where the resource information of the network slice meets the triggering condition of switching the network slice, determine to switch the terminal device on the network slice to the target network slice.
[0264] Optionally, the transceiver module 11 is further configured to receive resource information of a target network slice from the network slice management function network element; and the processing module 12 is further configured to determine that the resource information of the target network slice does not meet the triggering condition.
[0265] Optionally, the triggering condition of switching the network slice comprises one or more of the following: a performance indicator of the network slice is greater than or equal to a first threshold value, or less than or equal to a second threshold value; the slice selection network element receives alarm information of the network slice and / or the performance indicator of the network slice; the slice selection network element receives alarm information of the original network slice, and the alarm information is high-priority alarm information; an analysis report of the network slice meets a switching condition.
[0266] Optionally, the transceiver module 11 is further configured to send a subscription request message to the network slice management function network element, the subscription request message comprising an identifier of the original network slice, the subscription request message being used to subscribe to resource information of the original network slice.
[0267] Optionally, the transceiver module 11 is further configured to send a network slice configuration request message to a network slice capability management service providing network element, the network slice configuration request message comprising an identifier of the target network slice, and an identifier of the terminal device on the original network slice and / or an application identifier, the network slice configuration request message being used to request to configure the target network slice for the terminal device on the network slice.
[0268] Optionally, the transceiver module 11 is further configured to receive a network slice configuration response message from the network slice capability management service providing network element, the network slice configuration response message being used to indicate that the configuration of the target network slice for the terminal device is successful; and send a network slice configuration feedback message to the application server, the network slice configuration feedback message comprising the identifier of the target network slice and the identifier of the terminal device on the original network slice.
[0269] Optionally, the processing module 12 is further configured to update an association relationship between the identifier of the target network slice and the identifier of the terminal device locally.
[0270] Optionally, the transceiver 11 is further configured to send a network slice configuration feedback message to the application server, the network slice configuration feedback message comprising the identifier of the original network slice, the network slice configuration feedback message being used to indicate that the switching of the network slice for the terminal device on the original network slice is not successful.
[0271] Optionally, the network configuration feedback message further comprises a cause value and / or a suggested behavior indication information, the cause value being used to indicate a cause for not switching the terminal device on the network slice to the target network slice, and the suggested behavior indication information being used to indicate an operation performed by the application server.
[0272] Optionally, the transceiver 11 is further configured to receive a policy configuration request message from the network slice capability management service consumer network element or the application server, the policy configuration request message comprising the network slice switching policy; and the processing module 12 is further configured to save the network slice switching policy.
[0273] Optionally, the transceiver 11 is further configured to receive a policy modification request message from the network slice capability management service consumer network element or the application server, the policy modification request message comprising policy modification information, the policy modification information being used to indicate a modification performed on the network slice switching policy; and the processing module 12 is further configured to modify the network slice switching policy according to the policy modification information.
[0274] Optionally, the transceiver 11 is further configured to receive a policy deletion request message from the network slice capability management service consumer network element or the application server, the policy deletion request message comprising an identifier of the network slice switching policy, the policy deletion request message being used to indicate a deletion performed on the network slice switching policy; and the processing module 12 is further configured to delete the network slice switching policy.
[0275] It should be understood that the specific processes in which the respective modules perform the above-mentioned corresponding steps have been described in detail in the above-mentioned method embodiments, and thus will not be described here again for the sake of brevity.
[0276] It should also be understood that the apparatus 10 here is embodied in the form of functional modules. The term “module” here can refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (for example, a shared processor, a dedicated processor, or a group processor, etc.) and a memory for executing one or more software or firmware programs, a combination of logic circuitry and / or other suitable components that support the described functions. In an optional example, those skilled in the art can understand that the apparatus 10 can be embodied as the slice selection network element in the above-mentioned embodiments, and can be used to perform the respective processes and / or steps corresponding to the slice selection network element in the above-mentioned method embodiments. To avoid repetition, these will not be described here again.
[0277] The apparatus 10 of each of the above solutions has a function of implementing the corresponding steps performed by the slice selection network element in the above method. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver module can be replaced by a transceiver (for example, the sending unit in the transceiver module can be replaced by a transmitter, and the receiving unit in the transceiver module can be replaced by a receiver), and other units, such as the processing module, can be replaced by a processor, which respectively performs the transceiving operation and related processing operation in each method embodiment.
[0278] In addition, the transceiver module 11 described above can also be a transceiver circuit (for example, which can include a receiving circuit and a sending circuit), and the processing module can be a processing circuit.
[0279] It should be noted that, Figure 11 The apparatus in the above embodiments can be a network element or a device, or a chip or a chip system, such as a system on chip (SoC). The transceiver module can be an input / output circuit or a communication interface, and the processing module can be a processor or a microprocessor or an integrated circuit integrated on the chip. In this regard, no limitation is made.
[0280] As shown in FIG. 20, Figure 12 The embodiments of the present application provide another apparatus 20 for switching network slices. The apparatus 20 includes a processor 21, which is configured to execute computer programs or instructions stored in a memory 22, or read data / signaling stored in the memory 22, to perform the methods in the above method embodiments. Optionally, the processor 21 is one or more.
[0281] Optionally, as shown in FIG. 21, Figure 12 The apparatus 20 further includes a memory 22, which is configured to store computer programs or instructions and / or data. The memory 22 can be integrated with the processor 21, or can be separately arranged. Optionally, the memory 22 is one or more.
[0282] Optionally, as shown in FIG. 22, Figure 12 The apparatus 20 further includes a transceiver 23, which is configured to receive and / or send signals. For example, the processor 21 is configured to control the transceiver 23 to receive and / or send signals.
[0283] As a solution, the apparatus 20 is configured to implement the operations performed by the slice selection network element in the above method embodiments.
[0284] For example, the processor 21 is configured to execute the computer programs or instructions stored in the memory 22 to implement the operations of the slice selection network element in each of the above method embodiments. For example, Figure 6 to Figure 9 the method performed by the slice selection network element in any one of the above embodiments.
[0285] It should be understood that the processor mentioned in the embodiments of the present application can be a central processing module (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor.
[0286] It should also be understood that the memory mentioned in the embodiments of the present application can be a volatile memory and / or a non-volatile memory. The non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically EPROM (EEPROM) or a flash memory. The volatile memory can be a random access memory (RAM). For example, the RAM can be used as an external cache. As an example but not limitation, the RAM includes the following various forms: static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM) and direct rambus RAM (DR RAM).
[0287] It should be noted that when the processor is a general processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated in the processor.
[0288] It should also be noted that the memory described herein is intended to include, but not limited to, these and any other suitable type of memory.
[0289] The embodiments of the present application also provide a computer readable storage medium, which has stored computer instructions for implementing the method executed by the core network element in each of the above method embodiments.
[0290] For example, the computer program is executed by a computer, so that the computer can implement the method executed by the slice selection network element in each of the above method embodiments.
[0291] The embodiments of the present application also provide a computer program product, which contains instructions, and the instructions are executed by a computer to implement the method executed by the slice selection network element in each of the above method embodiments.
[0292] The explanations and beneficial effects of the related contents in any of the above provided devices can refer to the corresponding method embodiments provided above, and will not be repeated here.
[0293] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented by other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division way, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.
[0294] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable apparatus. For example, the computer can be a personal computer, a server, a network device, etc. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transferred from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) manner. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. integrated with one or more available media sets. The available media can be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (SSD), etc. For example, the foregoing available media includes but is not limited to: a variety of media that can store program codes such as a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.
[0295] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.
Claims
1. A method for switching network slices, characterized in that, include: The slice selection network element receives resource information of the original network slice from the network slice management function network element. The resource information of the original network slice includes one or more of the following: performance indicators of the original network slice and analysis report of the original network slice. The slice selection network element determines whether to switch the terminal device on the original network slice to the target network slice based on the resource information of the original network slice and the network slice switching strategy. The network slice switching strategy includes the triggering conditions for switching the network slice, the identifier of the target network slice, the identifier of the original network slice, and the identifier and / or application identifier of the terminal device on the original network slice.
2. The method according to claim 1, characterized in that, The slice selection network element determines whether to switch the terminal devices on the original network slice to the target network slice based on the resource information of the original network slice and the network slice switching strategy, including: The slice selection network element determines whether the resource information of the original network slice meets the triggering condition for switching the network slice; If the resource information of the original network slice meets the triggering condition for switching the network slice, the slice selection network element determines to switch the terminal device on the original network slice to the target network slice.
3. The method according to claim 1 or 2, characterized in that, The triggering conditions for switching network slices include one or more of the following: The performance metrics of a network slice are greater than or equal to the first threshold, or less than or equal to the second threshold; The network slice analysis report meets the switching conditions.
4. The method according to claim 3, characterized in that, The triggering conditions for switching network slices also include one or more of the following: The slice selection network element receives alarm information and / or performance indicators of the network slice. The slice selection network element receives alarm information for network slices, and the alarm information is a high-priority alarm information.
5. The method according to claim 1, characterized in that, The method further includes: The slice selection network element sends a subscription request message to the network slice management function network element. The subscription request message includes the identifier of the original network slice and is used to subscribe to the resource information of the original network slice.
6. The method according to claim 1, characterized in that, When the slice selection network element determines to switch the terminal device on the original network slice to the target network slice, the method further includes: The slice selection network element sends a network slice configuration request message to the network slice capability management service providing network element. The network slice configuration request message includes the identifier of the target network slice, the identifier of the terminal device on the original network slice, and / or the application identifier. The network slice configuration request message is used to request the configuration of the target network slice for the terminal device on the original network slice.
7. The method according to claim 6, characterized in that, The method further includes: The slice selection network element receives a network slice configuration response message from the network slice capability management service providing network element. The network slice configuration response message is used to indicate that the target network slice has been successfully configured for the terminal device. According to the network slice configuration response message, the slice selection network element sends a network slice configuration feedback message to the application server. The network slice configuration feedback message includes the identifier of the target network slice and the identifier of the terminal device on the original network slice.
8. The method according to claim 7, characterized in that, The method further includes: The slice selection network element updates the association between the identifier of the target network slice and the identifier of the terminal device locally.
9. The method according to claim 1, characterized in that, If the slice selection network element determines that it will not switch the terminal device on the original network slice to the target network slice, the method further includes: The slice selection network element sends a network slice configuration feedback message to the application server. The network slice configuration feedback message includes the identifier of the original network slice and is used to indicate that the network slice switching for the terminal device on the original network slice was unsuccessful.
10. The method according to claim 9, characterized in that, The network slice configuration feedback message also includes a reason value and / or suggested behavior indication information. The reason value is used to indicate the reason for not switching the terminal device on the original network slice to the target network slice, and the suggested behavior indication information is used to indicate the operation to be performed by the application server.
11. The method according to claim 1, characterized in that, The method further includes: The slice selection network element receives a policy configuration request message from the application server, the policy configuration request message including the network slice switching policy; The network element selected by the slice selection stores the network slice switching strategy.
12. The method according to claim 1, characterized in that, The method further includes: The slice selection network element receives a policy modification request message from the network slice capability management service consuming network element or application server. The policy modification request message includes policy modification information, which is used to indicate the modification to be performed on the network slice switching policy. The slice selection network element modifies the network slice switching strategy according to the strategy modification information.
13. The method according to claim 1, characterized in that, The method further includes: The slice selection network element receives a policy deletion request message from the network slice capability management service consuming network element or application server. The policy deletion request message includes the identifier of the network slice switching policy and is used to indicate that the network slice switching policy should be deleted. The network slice selection network element deletes the network slice switching strategy.
14. An apparatus for switching network slices, characterized in that, The apparatus includes: a module for performing the method as described in any one of claims 1 to 13, or a unit for performing the method as described in any one of claims 1 to 13.
15. An apparatus for switching network slices, characterized in that, include: A processor for executing a computer program stored in memory to cause the apparatus to perform the method as described in any one of claims 1 to 13.
16. The apparatus according to claim 15, characterized in that, The device also includes the memory.
17. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1 to 13.
18. A computer program product, characterized in that, The computer program product includes instructions for performing the method as described in any one of claims 1 to 13.
Citation Information
Patent Citations
Network slice selection in a network based on use case
WO2020209861A1
Cited By
Network slice switching method and apparatus
WO2023103585A1