Network slicing switching method, device and communication system

Abstract

The present application discloses a network slice switching method, device, and communication system. The method comprises: an application function entity sends a first request message to a unified data management entity through a network open function entity, wherein the first request message includes a slice switching indication, and the first request message is used to cause the unified data management entity to send a second request message to an access and mobility management function entity, and the second request message is used to cause the access and mobility management function entity to switch the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice. The present application solves the technical problem in the related art that the user equipment needs to re-register after switching from the first network slice to the second network slice, resulting in the inability to provide continuous service.

Description

Technical Field

[0001] The present application relates to the field of communications, and specifically, to a network slicing switching method, device and communication system. Background Art

[0002] In vertical industry fields, users can notify the terminal to improve the service quality of the business by manually selecting the application function (AF). The 5GC terminal can be prompted to change from slice 1 service to slice 2 service through the network exposure function (NEF) interface. However, when the contract is changed to a slice contract, if the access and mobility management function (AMF) responsible for the access of the user equipment (UE) cannot support the access of the target slice, the UE needs to trigger the re-registration process, which will interrupt the user's mobile phone service and make it impossible to provide continuous service, and the user experience will not be satisfied.

[0003] To address the above-mentioned problems, no effective solutions have been proposed so far. Summary of the Invention

[0004] The embodiments of the present application provide a network slice switching method, device and communication system to at least solve the technical problem in the related art that a user device needs to re-register after switching from a first network slice to a second network slice, resulting in an inability to provide continuous services.

[0005] According to one aspect of an embodiment of the present application, a network slice switching method is provided, including: an application function (AF) entity sends a first request message to a unified data management entity (UDM) through a network exposure function (NEF) entity, wherein the first request message includes a slice switching indication, and the first request message is used to enable the unified data management entity to send a second request message to an access and mobility management function entity (AMF), and the second request message is used to enable the access and mobility management function entity to switch a protocol data unit session (PDU) corresponding to a user equipment from a first network slice to a second network slice.

[0006] Optionally, the first request message also includes at least one of the following: an identifier of the second network slice, service quality parameter information, a reason code indicating that the service quality of the user equipment cannot meet the requirements, and a slice switching indication.

[0007] Optionally, before the application function entity sends the first request message to the unified data management entity through the network open function entity, the method also includes: the application function entity receives a third request message sent by the user equipment, wherein the third request message is used to trigger the application function entity to send the first request message.

[0008] Optionally, the method also includes: a fourth request message sent by the access and mobility management function entity to the target session management function entity (Session Management Function, SMF) corresponding to the second network slice, the fourth request message including at least one of the following: the address of the source session management function entity corresponding to the first network slice, the session identifier and the session management context identifier.

[0009] Optionally, before the application function entity sends the first request message to the unified data management entity through the network open function entity, the method also includes: the application function entity receives a third request message sent by the user equipment, wherein the third request message is used to trigger the switching process of the network slice; or, the access and mobility management function entity sends a fifth request message to the unified data management entity, wherein the fifth request message is used to obtain at least one of the following: an identifier of the second network slice in the first request message, and a slice switching indication.

[0010] Optionally, the first network slice and the second network slice are network slices under the same network function NF; the method also includes: the access and mobility management function entity sends a sixth request message to the first session management function entity, so that the first session management function entity switches the protocol unit session corresponding to the user equipment from the first network slice to the second network slice, wherein the sixth request message includes at least: the identifier of the second network slice corresponding to the first session management function entity.

[0011] Optionally, the method also includes: the user plane function entity receives a seventh request message sent by the first session management function entity, and the seventh request message carries the identifier of the second network slice; the user plane function entity switches the user equipment from the first network slice to the second network slice.

[0012] The session management function entity queries the policy control function entity whether the protocol data unit session corresponding to the user equipment is allowed to switch between different network slices; if switching between different network slices is allowed, the session management function entity sends a notification message to the user plane function entity, wherein the notification message includes at least: the identifier of the second network slice.

[0013] Optionally, the slice switching indication includes: an identifier of the second network slice; or, the slice switching indication includes: indication information specifically used to indicate switching from the first network slice where the user equipment resides to the second network slice.

[0014] According to another aspect of an embodiment of the present application, another network slice switching method is provided, including:

[0015] The application function entity sends a first request message to the unified data management entity through the network open function entity, wherein the first request message includes at least an identifier of the second network slice, and the first request message is used to enable the unified data management entity to send a second request message to the access and mobility management function entity, and the second request message is used to enable the access and mobility management function entity to switch the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice.

[0016] According to another aspect of an embodiment of the present application, another network slice switching method is provided, including: an access and mobility management function entity receives a second request message sent by a unified data management entity; the access and mobility management function entity switches the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice based on the second request message, wherein the second request message includes at least an identifier of the second network slice.

[0017] Optionally, before the access and mobility management function entity receives the second request message sent by the unified data management entity, the method also includes: the access and mobility management function entity sends a fifth request message to the unified data management entity, wherein the fifth request message is used to obtain at least one of the following: an identifier of the second network slice in the first request message, a slice switching indication, wherein the first request message is used to enable the unified data management entity to send a second request message to the access and mobility management function entity.

[0018] Optionally, the method also includes: the access and mobility management function entity obtains the address of the target session management function entity corresponding to the second network slice.

[0019] Optionally, the access and mobility management function entity sends a fourth request message to the target session management function entity, wherein the fourth request message includes: the address, session identifier, and session management context identifier of the source session management function entity corresponding to the first network slice.

[0020] Optionally, the access and mobility management function entity obtains the address of the target session management function entity corresponding to the second network slice, including: the access and mobility management function entity obtains the address of the target session management function entity corresponding to the second network slice from the network storage function entity (Network Repository Function, NRF).

[0021] Optionally, at least one of the address, session identifier and session management context identifier of the source session management function entity is used to configure the user plane function entity (UPF) corresponding to the second network slice.

[0022] Optionally, the method further includes: the access and mobility management function entity receiving a response message to the fourth request message, wherein the response message is used to determine whether the session management context is successfully created.

[0023] Optionally, before the access and mobility management function entity receives a response message to the fourth request message, the method also includes: the target session management function entity sends an eighth request message to the source session management function entity, wherein the eighth request message includes at least one of the following: a session management context identifier and an identifier of the second network slice; the target session management function entity receives a response message to the eighth request message sent by the source session management function entity, wherein the response message to the eighth request message includes context information corresponding to the session management context identifier.

[0024] Optionally, before the target session management function entity receives a response message to the eighth request message sent by the source session management function entity, the method also includes: the source session management function entity sends a first message to the policy control function entity (Policy Control Function, PCF); the source session management function entity receives a response message to the first message, wherein the response message to the first message is used to determine whether slice conversion is allowed.

[0025] Optionally, after the access and mobility management function entity receives a response message to the fourth request message, the method also includes: the access and mobility management function entity sends a second message to the user equipment, wherein the second message includes at least: an identifier of the second network slice.

[0026] Optionally, before the access and mobility management function entity receives the second request message sent by the unified data management entity, the method also includes: the access and mobility management function entity sends a fifth request message to the unified data management entity, wherein the fifth request message is used to obtain at least one of the following: an identifier of the second network slice and a slice switching indication in the first request message; the access and mobility management function entity receives the second request message sent by the unified data management entity, wherein the second request message includes at least an identifier of the second network slice.

[0027] Optionally, after the access and mobility management function entity receives the second request message sent by the unified data management entity, the method also includes: the user equipment sends a registration request message to the access and mobility management function entity, wherein the registration request message includes at least: an identifier of the first network slice.

[0028] Optionally, the method also includes: the source session management function entity sends a ninth request message to the unified data management entity, wherein the ninth request message includes at least a slice switching indication; the source session management function entity receives a response message to the ninth request message, wherein the response message to the ninth request message includes at least one of the following: quality of service parameter information, an identifier of the second network slice, and a slice switching indication.

[0029] Optionally, the method also includes: the access and mobility management function entity receives a tenth request message sent by the source session management function entity, wherein the tenth request message includes at least one of the following: an identifier of the second network slice and a slice switching indication.

[0030] Optionally, the method also includes: the tenth request message is sent by the source session management function entity based on the quality of service parameter information, at least one of the identifier and slice switching indication of the second network slice, and the policy information obtained from the policy control function entity.

[0031] Optionally, before the access and mobility management function entity receives the second request message sent by the unified data management entity, the method also includes: the application function entity sends an eleventh request message to the unified data management entity through the network open function entity, wherein the eleventh request message includes at least one of the following: a universal public user identity list, service quality parameter information, an identifier of the second network slice, and a slice switching indication.

[0032] According to another aspect of an embodiment of the present application, another network slice switching method is provided, including: a unified data management entity receives a first request message sent by an application function entity through a network open function entity, the first request message is a parameter setting request message, and the first request message includes at least one of the following: an identifier of a second network slice, service quality parameter information, a reason code for indicating that the service quality of a user device cannot meet the requirements, and a slice switching indication; a second request message is sent to an access and mobility management function entity based on the first request message, the second request message includes at least an identifier of a second network slice allowed to be accessed, and the second request message is used to enable the access and mobility management function entity to switch the protocol data unit session corresponding to the user device from the first network slice to the second network slice.

[0033] Optionally, after sending the second request message to the access and mobility management function entity according to the first request message, the method also includes: receiving a ninth request message sent by the source session management function entity, wherein the ninth request message includes at least a slice switching indication; sending a response message to the ninth request message to the source session management function entity, wherein the response message to the ninth request message includes at least one of the following: quality of service parameter information, an identifier of the second network slice, and a slice switching indication.

[0034] According to another aspect of an embodiment of the present application, another network slice switching method is provided, including: a network open function entity receives a first request message sent by an application function entity, the first request message is a parameter setting request message, and the first request message includes at least one of the following: an identifier of a second network slice, service quality parameter information, a reason code for indicating that the service quality of a user device cannot meet the requirements, and a slice switching indication; and forwarding the first request message to a unified data management entity.

[0035] According to another aspect of an embodiment of the present application, another network slice switching method is provided, comprising: a user device residing on a first network slice network sends a slice switching indication to an application function entity; the user device receives a response message sent by an access and mobility management function entity, initiates a session modification process based on the response message, and connects to a data network. Optionally, the slice switching indication includes at least an identifier of the second network slice.

[0036] According to another aspect of an embodiment of the present application, another network slice switching method is provided, including: a target session management function entity corresponding to the second network slice sends an eighth request message to a source session management function entity corresponding to the first network slice, wherein the eighth request message includes at least one of the following: a session management context identifier and an identifier of the second network slice; the target session management function entity receives a response message to the eighth request message sent by the source session management function entity, wherein the response message to the eighth request message includes context information corresponding to the session management context identifier.

[0037] Optionally, before the target session management function entity receives a response message to the eighth request message sent by the source session management function entity, the method also includes: the source session management function entity sends a first message to the policy control function entity; the source session management function entity receives a response message to the first message, wherein the response message to the first message is used to determine whether slice conversion is allowed.

[0038] According to another aspect of an embodiment of the present application, a network slice switching method is also provided, including: a session management function entity queries a policy control function entity whether the protocol data unit session corresponding to a user equipment is allowed to be switched between different network slices; if switching between different network slices is allowed, the session management function entity sends a notification message to a user plane function entity, which includes S-NSSAI2, so that the user plane function entity switches the session of the user equipment to the network slice corresponding to the second network slice identifier, wherein the notification message includes at least: the identifier of the second network slice.

[0039] According to another aspect of an embodiment of the present application, a network slice switching device is also provided, including: a communication module, used to send a first request message to a unified data management entity based on a slice switching indication, the first request message being a parameter setting request message, the first request message including at least one of the following: an identifier of the second network slice, service quality parameter information, a reason code indicating that the service quality of the user equipment cannot meet the requirements, and a slice switching indication; a processing module, used to enable the unified data management entity to send a second request message to an access and mobility management function entity after receiving the first request message, the second request message including at least an identifier of the second network slice, the second request message being used to enable the access and mobility management function entity to switch the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice.

[0040] According to another aspect of the embodiment of the present application, a communication system is also provided, including: an application function entity, a network open function entity, a unified data management entity, an access and mobility management function entity, a target session management function entity corresponding to the second network slice, and a user device, wherein: the application function entity is used to send a first request message to the unified data management entity based on the slice switching indication, the first request message is a parameter setting request message, and the first request message includes at least one of the following: an identifier of the second network slice, service quality parameter information, a reason code for indicating that the service quality of the user equipment cannot meet the requirements, and a slice switching indication; the network open function entity is used to receive the first request message sent by the application function entity, and forward the first request message to the unified data management entity; the unified data management entity is used to receive the first request message forwarded by the network open function entity, and send a request to the access and mobility management function entity based on the first request message. Send a second request message, the second request message includes at least an identifier of the second network slice; an access and mobility management function entity is used to receive the second request message and switch the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice; the target session management function entity corresponding to the second network slice is used to send an eighth request message to the source session management function entity corresponding to the first network slice, wherein the eighth request message includes at least one of the following: a session management context identifier and an identifier of the second network slice; receive a response message to the eighth request message sent by the source session management function entity, wherein the response message to the eighth request message includes context information corresponding to the session management context identifier; the user equipment is used to send a slice switching indication to the application function entity, and receive a response message sent by the access and mobility management function entity, initiate a session protocol data unit modification process according to the response message, and connect to the data network.

[0041] According to another aspect of an embodiment of the present application, another network slice switching method is provided, including: an application function entity sends a thirteenth request message to a policy control function entity through a network open function entity, wherein the thirteenth request message includes a slice switching indication, and the thirteenth request message is used to enable the policy control function entity to send a fourteenth request message to an access and mobility management function entity, and the fourteenth request message is used to enable the access and mobility management function entity to switch the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice.

[0042] In an embodiment of the present application, after receiving a slice switching indication sent by a user device, the application function entity sends a first request message to the unified data management entity through the network open entity. The first request message enables the unified data management entity to send a second request message to the access and mobility management function entity, thereby achieving the purpose of the access and mobility management function entity switching the first network slice where the user device resides to the second network slice, thereby achieving the technical effect of notifying the user device of the relevant information of the second network slice through the access and mobility management function entity without the need for the user device to re-register, thereby solving the technical problem in the related technology that the user device needs to re-register after switching from the first network slice to the second network slice, resulting in the inability to provide continuous service. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0044] Figure 1 This is a flowchart of a first network slice switching method according to an embodiment of the present application;

[0045] Figure 2a This is a flowchart of a second network slice switching solution according to an embodiment of the present application;

[0046] Figure 2b This is a flowchart of a second network slice switching solution according to an embodiment of the present application;

[0047] Figure 3 This is a flowchart of a network slice switching method according to an embodiment of the present application;

[0048] Figure 4 is a flowchart of another network slice switching method according to an embodiment of the present application;

[0049] Figure 5 is a flowchart of another network slice switching method according to an embodiment of the present application;

[0050] Figure 6 is a flowchart of another network slice switching method according to an embodiment of the present application;

[0051] Figure 7 is a flowchart of another network slice switching method according to an embodiment of the present application;

[0052] Figure 8 is a flowchart of another network slice switching method according to an embodiment of the present application;

[0053] Figure 9This is a flowchart of another network slicing switching method according to an embodiment of the present application.

[0054] Figure 10 This is a structural diagram of a network slicing switching device according to an embodiment of the present application;

[0055] Figure 11 It is a structural diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0056] In order to enable those skilled in the art to better understand the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0057] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in a sequence other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0058] It should also be noted that the various functional entities involved in the embodiments of the present application, such as the Network Exposure Function (NEF) entity and the Session Management Function (SMF) entity, can be specific network functions instantiated on the same core network server. Optionally, the above entities can also be separate servers. In some cases, it can also be shown that multiple functional entities share one server.

[0059] The specific structure of the server includes, but is not limited to, a processor, a memory for storing data, and a transmission module for communication functions. In addition, it may also include a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, a power supply, and / or a camera.

[0060] It should be noted that the above-mentioned processor may generally be referred to as "data processing circuit" in this document. The data processing circuit may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be fully or partially integrated into any of the other components of the server. As involved in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0061] The memory can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the network slice switching method in the embodiment of the present application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory.

[0062] The transmission module is used to receive or send data via a network. In one embodiment, the transmission device includes a network interface controller (NIC), which can be connected to other network devices via a base station to communicate with the Internet. In another embodiment, the transmission module can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0063] To better understand the embodiments of the present application, some nouns or terms that appear in the description of the embodiments of the present application are explained as follows:

[0064] AF: refers to various application layer services. It can be an internal operator application such as Volte AF (similar to 4G VolteAs) or a third-party AF (such as a video server or game server). If it is an internal operator AF, it is in the same trusted domain as other NFs and can directly interact with other NFs such as PCF. However, a third-party AF is not in the trusted domain and must access other NFs through NEF.

[0065] NEF: Located between the 5G core network and external third-party application functions (possibly also some internal AFs), it manages publicly accessible network data. All external applications that wish to access data within the 5G core network must pass through the NEF. The NEF provides security guarantees for external applications accessing the 3rd Generation Partnership Project (3GPP) network, offering features such as QoS customization capabilities for external applications, subscription to mobility status events, and AF request distribution.

[0066] UDM: Responsible for the management of user identification, contract data, authentication data, and user service network element registration management (such as AMF, SMF, etc. that currently provide services to the terminal. For example, when the user switches the AMF they access, UDM will also initiate a deregistration message to the old AMF, requiring the old AMF to delete user-related information).

[0067] PCF: Supports a unified policy framework to manage network behavior, provides policy rules to network entities for implementation, and accesses subscription information in the Unified Data Repository (UDR).

[0068] UPF: includes routing and forwarding of user data packets, data interaction with the external data network (DN), user plane QoS processing, and flow control rule implementation (such as gating, redirection, and traffic steering).

[0069] UDR: used by UDM to store or read subscription data and PCF to store or read policy data.

[0070] DN: For example, operator business, Internet or third-party business, etc.

[0071] SMF: Mainly responsible for interacting with the separated data plane, creating, updating and deleting PDU sessions, and managing the session environment or session context with UPF.

[0072] AMF: Receives all connection and session related information from user equipment (N1 / N2), but is only responsible for handling connection and mobility management tasks.

[0073] Single-Network Slice Selection Assistance information (S-NSSAI): that is, a single network slice. In network signaling, S-NSSAI refers to a network slice instance. In the actual network environment, the network slice instance can be understood as a collection of network resources. For example, (1 AMF + 1 SMF + 4 UPFs + ...) constitute a network slice instance, and for example, (1 SMF + 1 UPF) constitutes a network slice instance.

[0074] NRF: Used for NF registration, management, and status detection to achieve automated management of all NFs. When each NF is started, it must register with the NRF to provide services. Registration information includes NF type, address, service list, etc.

[0075] Subscription Permanent Identifier (SUPI): In mobile communications, network operators usually assign a (unique) identifier to each SIM card. This identifier is the International Mobile Subscriber Identity (IMSI) in 4G networks and the SUPI in 5G networks.

[0076] Generic Public Subscription Identifier (GPSI): Equivalent to the 4G MSISDN. SUPI and GPSI do not necessarily correspond one-to-one. If a user accesses different data networks, multiple GPSIs will exist. The network needs to establish a relationship between the external network GPSI and the SUPI.

[0077] Example 1

[0078] The fifth-generation mobile communication technology (5G) system first introduced the concept of network slicing. Because 5G needs to meet diverse network requirements (such as high bandwidth, low latency, and multiple access points), network slicing can help meet the communication service needs of a specific category or use case. A complete 5G system can be composed of a large number of network slices that meet different scenarios or network characteristics. Network slicing can be implemented in different parts of the 5G network, such as the radio access network, core network, and transport network. The network slices of these multiple parts can be connected together to form a complete network slice that provides users with a complete set of services. The network slices of different parts are logically isolated.

[0079] 3GPPSA2 defines slicing-related core network elements and slice selection-related processes, and introduces the Network Slice Selection Function (NSSF) network element into the 5G core network framework. The NSSF network mainly provides the following functions:

[0080] 1) Select a set of network slice instances for the service and the UE;

[0081] 2) Determine the allowed NSSAI and the mapping relationship between the allowed NSSAI and the subscribed S-NSSAI;

[0082] 3) Determine the configured NSSAI and the mapping between the configured NSSAI and the subscribed S-NSSAI;

[0083] 4) Determine the set of AMFs that may be used to query the UE, or determine a list of candidate AMFs based on the configuration. The list of candidate AMFs may be obtained by querying the NRF.

[0084] During the initial registration process, the UE will carry the corresponding slice ID information NSSAI. The AMF will decide whether to allow the UE to access the slice corresponding to an S-NSSAI in the NSSAI based on the interaction with the UDM or NSSF. The network slice of the core network can include one or more network elements such as AMF, SMF and UPF. If the NSSF determines that the AMF initially accessed by the UE cannot serve the slice that the UE is about to access, the NSSF will notify the UE through the AMF to re-register with the AMF that can serve the target slice.

[0085] In related technologies, the 3GPP SA2 R18 slice enhancement project mainly studies how to ensure business continuity when slices or slice instances are overloaded. Currently, related technologies do not provide corresponding technical solutions for switching network slices when the slices are not overloaded and business continuity is to be guaranteed.

[0086] According to an embodiment of the present application, an embodiment of a network slice switching method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0087] In the embodiments of the present application, two network slice switching schemes are mainly provided. The first scheme is that a third request message is initiated by a user equipment. The third request message is a request to improve the service quality and is used to trigger the network slice switching process. After the application function entity receives the third request message sent by the user equipment, the third request message is converted into a slice switching indication and sent to the unified data management entity. The first request message includes a slice switching indication. According to the first request message, after data transmission and interaction between the various entities, the protocol data unit session corresponding to the user equipment is switched from the first network slice to the second network slice; the second scheme is not to initiate the third request message by the user equipment, but the application function entity on the network side obtains the triggering condition for slice switching, that is, service quality parameter information. Through service quality detection, it is found that the specified UE does not meet the service quality requirements, thereby triggering the slice switching operation for the UE, that is, sending a first request message (here referring to the eleventh request message) to the unified data management entity. The first request (eleventh request message) message includes a slice switching indication. Based on the first request message (eleventh request message), after data transmission and interaction between the various entities, the protocol data unit session corresponding to the user equipment can be switched from the first network slice to the second network slice.

[0088] It should be noted that the above two implementations have slightly different interaction processes between the entities, which are described in detail below.

[0089] Figure 1 This is a flow chart of a first network slicing switching solution according to an embodiment of the present application. Figure 1 As shown, the method includes the following steps:

[0090] Step S101: A user equipment registers with a first network slice and accesses a 5G network through the first network slice. The first network slice may be S-NSSAI 1.

[0091] Step S102: The access and mobility management function entity sends a fifth request message to the unified data management entity, where the fifth request message is used to obtain at least one of the following: an identifier of the second network slice (S-NSSAI2) and a slice switching indication in the first request message;

[0092] Optionally, the fifth request message may be a session data management subscription (Nudm_SDM_Subscribe) message, or other related interface messages, and the fifth request message used to obtain the slice switching indication may be an S-NSSAI update indication (S-NSSAI update indicator) message.

[0093] Step S103: When the application layer in the user equipment determines that the current quality of service does not meet the requirements, for example, the non-compliance may be caused by deterioration of QoS parameters that affect user experience, such as network delay, jitter, or throughput, the user equipment sends a third request message to the application function entity. The third request message is used to trigger the application function entity to send the first request message to the unified data management entity through the network open function entity.

[0094] Optionally, the application function entity may determine whether to send the first request message based on information such as a contract with the user equipment, that is, determine whether to trigger an operation of switching the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice. The basis for the judgment may be whether the user has permission to access the second network slice, or whether the user's priority meets the requirements for accessing the second network slice.

[0095] Step S104: The application function entity sends a first request message to the network open function entity. The first request message includes a GPSI, that is, a GPSI corresponding to a user equipment. The user equipment that needs to perform slice switching is determined by the identifier. The first request message also includes at least one of the following: an identifier of the second network slice, a slice switching indication, quality of service parameter information, and a reason code.

[0096] Optionally, the first request message may be a parameter provision update request (Nnef_ParameterProvision_Update_Req) ​​message, or other related interface messages, which are detected internally by the 5GC to determine whether to perform network slice switching; the identifier of the second network slice may be S-NSSAI 2, and the slice selection indication may be used to instruct the target network element (such as AMF) to perform a slice switching operation on the specified UE; the quality of service parameter information (QoS parameter) may be used to instruct the target network element (such as SMF) to trigger a slice switching operation when it detects that the service quality of the specified UE does not meet the service quality parameter; the reason code is used to indicate that the service quality of the user equipment cannot meet or cannot meet the preset requirements, and the reason code (Reason code) may include the reason for requesting to switch the slice, for example, the content included in the reason code may be that the UE or the specified application cannot meet the service quality requirements in the accessed slice, etc. In addition to the above parameters, the first request message may also include other parameter information, only part of which is listed here, and the specific other information included may be added according to actual conditions.

[0097] It should be noted that the slice switching indication in the embodiment of the present application can also be called a slice selection indication. For ease of understanding, it is collectively referred to as a slice switching indication below.

[0098] Optionally, after the network open function entity receives the first request message sent by the application function entity, it will send a response message to the first request message to the application function entity. The response message is used to notify the application function entity to confirm that the network open function entity has received the first request message sent by the application function entity and can successfully complete the transmission of subsequent messages.

[0099] Step S105: After receiving the first request message sent by the application function entity, the network open function entity forwards the first request message to the unified data management entity;

[0100] Optionally, since the receiving entities are different, the embodiment of the present application Figure 1 The first request message forwarded by the network open function entity in step S105 is not a parameter update request (Nnef_ParameterProvision_Update_Req) ​​message, but a parameter update request (Nudm_ParameterProvision_Update_Req) ​​message. Specifically, the parameter update request message (Nudm_ParameterProvision_Update_Req) ​​includes GPSI, that is, the GPSI corresponding to a user equipment, and at least one of the following: an identifier of the second network slice (S-NSSAI 2), a slice selection indication, quality of service parameter information (QoS parameter), and a reason code (Reasoncode); the identifier of the second network slice here is an identifier of the second network slice allowed to be accessed. The parameter update request (Nudm_ParameterProvision_Update_Req) ​​message may also include other information, and only part of the information is listed here.

[0101] Optionally, after receiving the first request message (here referring to the Nudm_ParameterProvision_Update_Req message) forwarded by the network open function entity, the unified data management entity will send a response message to the first request message (i.e., the Nudm_ParameterProvision_Update_Req message) to the network open function entity. The response message is used to notify the network open function entity to confirm that the unified data management entity has received the first request message (i.e., the Nudm_ParameterProvision_Update_Req message) forwarded by the network open function entity, and can successfully complete the transmission of subsequent messages.

[0102] Step S106: The unified data management entity sends a second request message to the access and mobility management function entity, where the second request message includes the SUPI and an identifier of the second network slice;

[0103] Optionally, the second request message may be a session data management notification (Nudm_SDM_Notification) message, or other related interface messages, and the identifier of the second network slice in step S106 is the identifier of the second network slice allowed to be accessed. The unified data management entity completes the conversion from GPSI to SUPI through interaction with other network elements.

[0104] Step S107: The access and mobility management function entity obtains the address of the target session management function entity corresponding to the second network slice from the network storage function entity;

[0105] Step S108: The access and mobility management function entity sends a fourth request message to the target session management function entity corresponding to the second network slice, wherein the fourth request message includes at least the address of the source session management function entity corresponding to the first network slice, a PDU session identifier (PDU Session ID), and a session management context identifier (SM Context ID);

[0106] Optionally, at least one of the address, session identifier and session management context identifier of the source session management function entity is used to configure the user plane function entity corresponding to the second network slice, and the UPF configuration can also be configured during the network-triggered PDU session modification process.

[0107] Optionally, the fourth request message may be a PDU session request (Nsmf_PDUsession_CreateSMContext Req) message for creating a session management context, or other related interface messages, and the address of the source session management function entity corresponding to the first network slice may be the source SMF.

[0108] Step S109: After receiving the fourth request message, the target session management function entity corresponding to the second network slice configures the corresponding UPF;

[0109] Optionally, the UPF configuration can also be configured during the network-triggered PDU session modification process.

[0110] Step S110: After the target session management function entity corresponding to the second network slice configures the corresponding UPF, the target session management function entity sends an eighth request message to the source target session management function entity corresponding to the first network slice, wherein the eighth request message includes at least one of the following: a session management context identifier (SM context ID) and an identifier of the second network slice (S-NSSAI 2);

[0111] Optionally, the eighth request message may be a PDU session management context request (Nsmf_PDUsession_Context Req) message, or other related interface messages. Optionally, before sending the eighth request message, the target SMF may send a PCF session management policy control update (Npcf_SMPolicyControl_Update) request message to the PCF, or other related interface messages, which is used to confirm whether the policy of the second network slice supports the transfer of session context across slices or whether it supports session switching, and may obtain the result of whether the policy supports the transfer of session context across slices or whether it supports session switching by receiving a PCF session management policy control update response message.

[0112] Step S111: The source session management function entity sends a first message to the PCF, where the first message is used to request confirmation of whether session switching (i.e., session switching) is allowed between slices (the first network slice and the second network slice in this application).

[0113] Optionally, the first message in the embodiment of the present application may be a session management policy control update (Npcf_SMPolicyControl_Update) request message, or other related interface messages. This message is used to confirm whether the policy of the first network slice supports the transfer of session context across slices or whether it supports session switching, and whether the policy supports the transfer of session context across slices or whether it supports session switching can be obtained by receiving a PCF session management policy control update response message.

[0114] Step S112: When confirming with the PCF that the policy allows session switching between slices, the source session management function entity sends a response message to the target session management function entity for the eighth request message, where the response message to the eighth request message includes at least session management context information (SM context) corresponding to the session management context identifier;

[0115] Optionally, the response message to the eighth request message may be a PDU session management context response (Nsmf_PDUsession_Context Res) message, or other related interface messages.

[0116] In step S113, after the target session management function entity receives the response message to the eighth request message, it sends a third message to the access and mobility management function entity, where the third message is a response message to the PDU session request message for creating a session management context, that is, a response message corresponding to the fourth request message in step S108, such as a PDU session response (Nsmf_PDUsession_CreatSMcontext Res) message for creating a session management context, or other related interface messages.

[0117] In step S114, after receiving the third message, the access and mobility management function entity sends a second message to the user equipment, where the second message is a network slice update message, and the second message includes at least: an identifier of the second network slice and a target data network access identifier (target DNAI). The user equipment accesses the corresponding second network slice according to the configuration information of the second network slice (for example, target DNAI). The second message can be a command message sent by the AMF to the terminal device, such as a PDU session modification command (PDUSessionModificationCommand) or a UE configuration update command (UEConfigurationupdateCommand) or other command message, which is not specifically limited in this embodiment.

[0118] In step S115, after the access and mobility management function entity sends the second message to the user equipment, the access and mobility management function entity triggers a PDU session modification process, so that the UE switches to the network corresponding to the second network slice. It should be noted that, in the embodiment of the present application, the user equipment switching from the first network slice to the second network slice means: switching the PDU session corresponding to the UE from the first network slice to the second network slice.

[0119] Step S116: After the PDU session modification is completed, the access and mobility management function entity sends a slice switching completion confirmation message to the unified data management entity;

[0120] Step S117: The unified data management entity forwards the slice switching completion confirmation message to the network open function entity;

[0121] Step S118, the network open function entity forwards the slice switching completion confirmation message to the application function entity.

[0122] Through the above steps S101 to S118, the switching process of the first network switching is realized, that is, the user equipment initiates a third request message, the third request message is used to trigger the switching process of the network slice, and the third request message is a request to improve the quality of service. After the application function entity receives the third request message sent by the user equipment, the third request message is converted into a slice switching indication, and the first request message is sent to the unified data management entity. The first request message includes a slice switching indication. According to the first request message, after data transmission and interaction between the various entities, the protocol data unit session corresponding to the user equipment is switched from the first network slice to the second network slice.

[0123] Figure 2a This is a flow chart of a second network slicing switching solution according to an embodiment of the present application. Figure 2a As shown, the method includes the following steps:

[0124] Step S201: The access and mobility management function entity sends a fifth request message to the unified data management entity, wherein the fifth request message is used to obtain at least one of the following: an identifier of the second network slice (S-NSSAI 2) in the first request message and a slice switching indication;

[0125] Optionally, the fifth request message may be a session data management subscription (Nudm_SDM_Subscribe) message, or other related interface messages, and the message used by the fifth request message to obtain the slice switching indication may be an S-NSSAI update indication message (S-NSSAIupdate indicator). The second slice identifier may enable the AMF to identify the second network slice identifier corresponding to the second network slice that can be switched after obtaining the slice switching related request, and trigger the corresponding slice switching operation.

[0126] It should be noted that in Figure 2a In the flowchart shown, step S201 is optional, that is, step S201 may be performed or may not be performed.

[0127] In step S202, the application function entity sends a first request message to the network open function entity. The first request message in this step is different from the first request message in step S104. The first request message in this step includes: a universal public user identifier list, and at least one of the following: an identifier of the second network slice, a slice switching indication, service quality parameter information, and a reason code; in order to distinguish the first request message in step S202 from the first request message in step S104, the first request message in step S202 can be named the eleventh request message, hereinafter collectively referred to as the eleventh request message.

[0128] Optionally, the application function entity can send the condition information for determining whether the UE needs to switch slices to the 5G core network element, such as NEF and UDM, through the eleventh request message. The application function entity can determine whether to send the eleventh request message based on information such as the contract with the user equipment, and then the core network element, such as SMF, determines whether to perform slice switching based on the QoS parameters measured by the N4 interface, and finally the AMF initiates the migration of the session management context across slices.

[0129] Optionally, the eleventh request message may be a parameter update request (Nnef_ParameterProvision_Update_Req) ​​message, or other related interface messages, which are detected internally by the 5GC to determine whether to perform network slice switching; the identifier of the second network slice may be S-NSSAI 2, and the slice selection indication may be used to instruct the target network element (such as AMF) to perform a slice switching operation on the specified UE; the quality of service parameter (QoS parameter) may be used to instruct the target network element (such as SMF) to trigger a slice switching operation when it detects that the service quality of the specified UE does not meet the service quality parameter; the reason code is used to indicate that the service quality of the user equipment cannot meet or cannot meet the preset requirements, and the reason code (Reason code) may include the reason for requesting to switch the slice, for example, the content included in the reason code may be that the UE or the specified application cannot meet the service quality requirements in the accessed slice, etc. In addition to the above parameters, the eleventh request message may also include other parameter information, only part of which is listed here, and the specific other information included can be added according to actual conditions.

[0130] It should be noted that the slice switching indication in the embodiment of the present application can also be called a slice selection indication. For ease of understanding, it is collectively referred to as a slice switching indication below.

[0131] Optionally, after the network open function entity receives the eleventh request message sent by the application function entity, it will send a response message to the eleventh request message to the application function entity. The response message is used to notify the application function entity that the network open function entity has received the eleventh request message sent by the application function entity and can successfully complete the transmission of subsequent messages.

[0132] Step S203: After receiving the eleventh request message sent by the application function entity, the network open function entity forwards the eleventh request message to the unified data management entity;

[0133] Figure 2aIn the process, since the receiving entities are different, the eleventh request message forwarded by the network open function entity is not a parameter update request (Nnef_ParameterProvision_Update_Req) ​​message, but a parameter update request (Nudm_ParameterProvision_Update_Req) ​​message. Specifically, the Nudm_ParameterProvision_Update_Req message in this step includes: a universal public user identifier list, and at least one of the following: an identifier of the second network slice (S-NSSAI 2), a slice selection indication, quality of service parameter information (QoS parameter), and a reason code; the identifier of the second network slice here is an identifier of the second network slice that is allowed to be accessed.

[0134] It should be noted that this embodiment Figure 2a The Nudm_ParameterProvision_Update_Req message in the Message field can also contain other information, only part of which is listed here.

[0135] Optionally, in Figure 2a In the process, after receiving the eleventh request message (here referring to the Nudm_ParameterProvision_Update_Req message) forwarded by the network open function entity, the unified data management entity will send a response message of the eleventh request message (i.e., the Nudm_ParameterProvision_Update_Req message) to the network open function entity. The response message is used to notify the network open function entity to confirm that the unified data management entity has received the eleventh request message (i.e., the Nudm_ParameterProvision_Update_Req message) forwarded by the network open function entity and can successfully complete the transmission of subsequent messages.

[0136] In step S204, the unified data management entity sends a second request message to the access and mobility management function entity, wherein the second request message includes an identifier of the second network slice; since the sender and receiver of the second request message in step S204 and step S106 are the same, but the contents included in the two steps are slightly different, in order to distinguish the second request messages in step S106 and step S204, the second request message in step S204 is named the twelfth request message, hereinafter collectively referred to as the twelfth request message.

[0137] Optionally, the twelfth request message may be a session data management notification (Nudm_SDM_Notification) message, or other related interface messages. The identifier of the second network slice included in the twelfth request message in step S204 is the identifier of the second network slice that is allowed to be accessed. The unified data management entity will complete the conversion from GPSI to SUPI through interaction with other network elements. The identifier of the second network slice can be used by the AMF to determine the second network slice as the switching object after obtaining the slice switching request, and trigger the switching of the specified UE to the second network slice. Optionally, before triggering the switching, the AMF can obtain the service quality parameters of the slice from the SMF corresponding to the second network slice. It is used to determine whether the service quality parameters meet the service quality requirements of the UE. When it is determined that the requirements are met, the operation of switching the UE to the second network slice is triggered.

[0138] It should be noted that in Figure 2a In the flowchart shown, step S204 is optional, that is, step S204 may be performed or not. When step S201 is performed, step S204 will be performed; when step S201 is not performed, step S204 will not be performed and step S205 will be performed directly.

[0139] Step S205: The user equipment registers with the first network slice and accesses the 5G network through the first network slice. The first network slice may be S-NSSAI 1.

[0140] Step S206: The source session management function entity corresponding to the first network slice sends a ninth request message to the unified data management entity, wherein the ninth request message includes at least SUPI and slice switching indication;

[0141] Optionally, the ninth request message may be a session data management request (Nudm_SDM_GetReq) message, or other related interface messages. This message may be sent by the SMF to the UDM during the PDU session establishment process, so that the SMF knows whether the UE is requested to perform corresponding slice switching operations when the QoS does not meet the requirements. Optionally, this message may also be triggered in the PDU session modification process.

[0142] Step S207: The source session management function entity receives a response message to the ninth request message sent by the unified data management entity, wherein the response message to the ninth request message includes at least one of the following: quality of service parameter information, an identifier of the second network slice, and a slice switching indication;

[0143] Optionally, the response message to the ninth request message may be a Get Session Data Management Response (Nudm_SDM_GetRes) message, or other related interface messages.

[0144] Step S208: After receiving the response message to the ninth request message sent by the unified data management entity, the source session management function entity sends a first message to the policy control function entity, where the first message is used to request confirmation of whether session switching (i.e., session switching) is allowed between slices (the first network slice and the second network slice in this application);

[0145] Optionally, the first message in an embodiment of the present application may be a session management policy control update (Npcf_SMPolicyControl_Update) request message, or other related interface messages, which is used to confirm whether the policy of the first network slice supports the transfer of session context across slices or whether it supports session switching.

[0146] Step S209: When confirming with the policy control function entity that the policy allows session switching across slices, the source session management function entity sends a tenth request message to the access and mobility management function entity, where the tenth request message includes at least the SUPI, the slice switching indication, and the identifier of the second network slice;

[0147] Optionally, the tenth request message is sent by the source session management function entity based on the quality of service parameter information, the identifier of the second network slice and at least one of the slice switch indication (Slice switch indication), and the policy information obtained from the policy control function entity. The tenth request message can be a session management context status notification message (Nsmf_PDUSession_SMContextStatusNotify) message, or other related interface messages.

[0148] It should be noted that if steps S201 and S204 are executed, then in steps S201 to S204, the access and mobile data management function entity has received the identifier of the second network slice. In subsequent messages sent by other entities to the access and mobile data management function entity, the identifier of the second network slice may not be carried or may be carried, which is not limited here. If steps S201 and S204 are not executed, then in subsequent messages sent by other entities to the access and mobile data management function entity, the identifier of the second network slice needs to be carried. Whether the identifier of the second network slice needs to be carried depends on the actual situation and is not limited here.

[0149] Step S210: After receiving the tenth request message, the access and mobility management function entity obtains the address of the target session management function entity corresponding to the second network slice from the network storage function entity;

[0150] Step S211: After obtaining the address of the target session management function entity corresponding to the second network slice, the access and mobility management function entity sends a fourth request message to the target session management function entity, wherein the fourth request message includes at least: the address of the source session management function entity corresponding to the first network slice, the PDU session identifier (PDU Session ID), and the session management context identifier (SM Context ID);

[0151] Optionally, at least one of the address, session identifier and session management context identifier of the source session management function entity is used to configure the user plane function entity corresponding to the second network slice, and the UPF configuration can also be configured during the network-triggered PDU session modification process.

[0152] Optionally, the fourth request message may be a PDU session request (Nsmf_PDUsession_CreateSMContext Req) message for creating a session management context, or other related interface messages, and the address of the source session management function entity corresponding to the first network slice may be the source SMF address.

[0153] Step S212: After receiving the fourth request message, the target session management function entity corresponding to the second network slice configures the corresponding UPF;

[0154] Optionally, the UPF configuration can also be configured during the network-triggered PDU session modification process.

[0155] Step S213: After the target session management function entity corresponding to the second network slice configures the corresponding UPF, the target session management function entity sends an eighth request message to the source target session management function entity corresponding to the first network slice, where the eighth request message includes at least one of the following: a session management context identifier (SM context ID) and an identifier of the second network slice (S-NSSAI 2);

[0156] Optionally, the eighth request message may be a PDU session management context request (Nsmf_PDUsession_Context Req) message, or other related interface messages. Optionally, before sending the eighth request message, the target SMF may send a PCF session management policy control update (Npcf_SMPolicyControl_Update) request message to the PCF, or other related interface messages, which is used to confirm whether the policy of the second network slice supports the transfer of session context across slices or whether it supports session switching, and may obtain the result of whether the policy supports the transfer of session context across slices or whether it supports session switching by receiving a PCF session management policy control update response message.

[0157] Step S214: After receiving the eighth request message, the source session management function entity sends a response message to the target session management function entity, wherein the response message to the eighth request message includes at least session management context information (SM context) corresponding to the session management context identifier;

[0158] Optionally, the response message to the eighth request message may be a PDU session management context response (Nsmf_PDUsession_Context Res) message, or other related interface messages.

[0159] In step S215, after the target session management function entity receives the response message to the eighth request message, it sends a third message to the access and mobility management function entity, where the third message is a response message to the PDU session request message for creating a session management context, that is, a response message corresponding to the fourth request message in step S211, such as a PDU session response (Nsmf_PDUsession_CreatSMcontext Res) message for creating a session management context, or other related interface messages.

[0160] In step S216, after receiving the third message, the access and mobility management function entity sends a second message to the user equipment, where the second message is a network slice update message, and the second message includes at least: an identifier of the second network slice and a target DNAI. The user equipment accesses the corresponding second network slice according to the configuration information of the second network slice (for example, the target DNAI). The second message can be a command message sent by the AMF to the terminal device, such as a PDU session modification command (PDUSessionModificationCommand) or a UE configuration update command (UEConfigurationupdateCommand) or other command message, which is not specifically limited in this embodiment.

[0161] Step S217, after the access and mobility management function entity sends the second message to the user equipment, the access and mobility management function entity triggers the PDU session modification (PDU session modification) process, so that the UE switches to the network corresponding to the second network slice.

[0162] Step S218: After the PDU session modification is completed, the access and mobility management function entity sends a slice switching completion confirmation message to the unified data management entity;

[0163] Step S219: The unified data management entity forwards the slice switching completion confirmation message to the network open function entity;

[0164] In step S220, the network open function entity forwards the slice switching completion confirmation message to the application function entity.

[0165] Through steps S201 to S219, the switching process of the second type of network switching is implemented, that is, the application function entity on the network side obtains the triggering condition for slice switching, that is, the service quality parameter information, and finds through service quality detection that the specified UE does not meet the service quality requirements, thereby triggering the slice switching operation for the UE, that is, sending the eleventh request message to the unified data management entity, the eleventh request message includes a slice switching indication, based on the eleventh request message, after data transmission and interaction between the various entities, the protocol data unit session corresponding to the user equipment can be switched from the first network slice to the second network slice.

[0166] In the related art, when the resources of an S-NSSAI are congested, the application performance of some UEs using the S-NSSAI resources may not be met. AF can notify the service performance degradation and then trigger a request to 5GC to slice and remap the corresponding PDU session, thereby ensuring the performance of the application while ensuring the service continuity of the application (such as cloud gaming and real-time high-resolution video streaming, which require service continuity to provide QoE to customers). The solution in the embodiment of the present application is based on the principle that each PDU session can be assigned to multiple (for example, two) network slices (S-NSSAI). In this case, NFs (network open functions) such as SMF and UPF in a network slice can support multiple S-NSSAIs, and each S-NSSAI has different network resources. Once the fixed network resources corresponding to the S-NSSAI become congested, the SMF and / or UPF can use the resources of other S-NSSAIs to ensure the service continuity of applications, such as cloud gaming and real-time high-resolution video streaming.

[0167] In other embodiments, the slice switching indication may be an identifier of the second network slice, that is, the AF entity may carry the identifier of the second network slice in the request message sent by the NEF entity to the UDM entity, so that the UDM entity may send a second request message to the AMF, so that the AMF switches the user equipment from the first network slice to the second network slice. Optionally, the AF entity may also send a request message to the PCF through the NEF entity to query the PCF for the session switching policy, that is, whether the PDU session is allowed to switch between different S-NSSAI network resources under the SMF entity and the UPF entity. And if the policy allows, the PCF triggers the sending of a message carrying the identifier of the second network slice to the AMF, so that the AMF triggers the PDU session modification process.

[0168] However, it should be noted that the above-mentioned slice switching indication can also be indication information specifically used to indicate switching from the first network slice where the user equipment resides to the second network slice, that is, the slice switching indication can be indication information newly added in the 3GPP protocol, and its form of expression is not limited.

[0169] It should be noted that before the SMF sends a session modification request to the UPF, the session management function entity may directly or indirectly send a request message to the policy control function entity to inquire whether the protocol data unit session corresponding to the user equipment is allowed to be switched between different network slices. In some embodiments, the session management function entity inquires with the policy control function entity whether the protocol data unit session corresponding to the user equipment is allowed to be switched between different network slices; if switching between different network slices is allowed, the session management function entity sends a notification message to the user plane function entity, wherein the notification message includes at least: the identifier of the second network slice; if switching between different network slices is allowed, the session management function entity sends a notification message to the user plane function entity, wherein the notification message includes at least: the identifier of the second network slice.

[0170] For the case where the slice switching indication can be the identifier of the second network slice, the following is combined with Figure 2b Detailed description. Figure 2b As shown: Step 1, the UE accesses the 5G network and resides on slice S-NSSAI 1.

[0171] Step 2: The AF sends an Nnef_ParameterProvision_Request message to the NEF (Network Exposure Function), which includes GPSI and S-NSSAI 2. It should be noted that S-NSSAI 2 can be considered a slice switching indication at this time, or it can be considered that the request message does not contain a slice switching indication and only includes the slice identifier of the target slice, namely S-NSSAI 2. Step 3: The NEF entity sends a Nudm_ParameterProvision_Request message to the UDM entity, which includes GPSI, AS-NSSAI 2, etc.

[0172] Step 4: The UDM entity sends a Nudm_SDM_Notification message to the AMF entity, where the message includes SUPI and S-NSSAI 2.

[0173] Step 5: The AMF entity sends a Namf_PDUsession_UpdateSMContext message to the SMF entity, which includes SUPI, S-NSSAI2 and PDU session ID;

[0174] Step 6: The SMF entity queries the PCF entity through the Npcf_SMPolicyControl_Update message whether the policy allows the PDU session to be switched between different S-NSSAI network resources under the SMF entity and the UPF entity;

[0175] Step 7: If the policy allows, the SMF entity sends an N4 session modification message to the UPF entity, which includes S-NSSAI2, so that the UPF entity can switch the corresponding PDU session to the network resources corresponding to S-NSSAI2.

[0176] Step 8: The SMF entity receives the session modification response (N4_session ModificationResponse) sent by the UPF entity.

[0177] Step 9: The SMF entity sends a session context update response (Response of NamfPDUSession_UpdateSMContext) to the AMF entity.

[0178] Step 10: Continue the PDU session modification procedure.

[0179] Step 11: AMF sends a notification message (Notification) to AF through UDM and AEF.

[0180] It should be noted that the interaction messages between AMF and SMF are not limited to the interface message types described in the embodiments of the present application, but can also be other types of interface messages.

[0181] Example 2

[0182] based on Figure 1 and Figure 2a-2b The process in the embodiment shown in the figure, the embodiment of the present application provides a method for switching network slices, Figure 3 This is a flow chart of a network slicing switching method according to an embodiment of the present application. Figure 3 As shown, the method includes the following processing steps:

[0183] Step S302: The application function entity sends a first request message to the unified data management entity through the network open function entity, where the first request message includes a slice switching indication;

[0184] Step S304: After receiving the first request message, the unified data management entity sends a second request message to the access and mobility management function entity. The second request message is used to enable the access and mobility management function entity to switch the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice.

[0185] In the above step S302, the application function entity first sends a first request message to the network open entity, and the network open entity forwards the first request message to the unified data management entity. The first request message includes GPSI, that is, the GPSI corresponding to a user device, and the user device that needs to perform slice switching is determined by this identifier. The first request message also includes at least one of the following: an identifier of the second network slice, service quality parameter information, a reason code for indicating that the service quality of the user device cannot meet the requirements, and a slice switching indication.

[0186] The first request message may be a parameter update request (Nnef_ParameterProvision_Update_Req) ​​message, or other related interface messages, which are detected internally by the 5GC to determine whether to perform network slice switching; the identifier of the second network slice may be S-NSSAI 2, and the slice selection indication may be used to instruct the target network element (such as AMF) to perform a slice switching operation on the specified UE; the quality of service parameter information (QoS parameter) may be used to instruct the target network element (such as SMF) to trigger a slice switching operation when it detects that the service quality of the specified UE does not meet the service quality parameter; the reason code is used to indicate that the service quality of the user equipment cannot meet or cannot meet the preset requirements, and the reason code (Reason code) may include the reason for requesting to switch the slice, for example, the content included in the reason code may be that the UE or the specified application cannot meet the service quality requirements in the accessed slice, etc. In addition to the above parameters, the first request message may also include other parameter information, only part of which is listed here, and the specific other information included may be added according to actual conditions.

[0187] It should be noted that the slice switching indication in the embodiment of the present application can also be called a slice selection indication. For ease of understanding, it is collectively referred to as a slice switching indication below.

[0188] Optionally, before the application function entity sends the first request message to the unified data management entity through the network open function entity, the method also includes the following steps: the application function entity receives a third request message sent by the user equipment, wherein the third request message is used to trigger the switching process of the network slice, that is, used to trigger the application function entity to send the first request message, and the third request message is a request to improve the quality of service.

[0189] After receiving the third request message sent by the user equipment, the application function entity converts the third request message into a slice switching indication and sends the first request message to the unified data management entity.

[0190] When the application layer in the user equipment believes that the current service quality does not meet the requirements, for example, the non-compliance may be caused by deterioration of QoS parameters such as network delay, jitter, or throughput that affect user experience, the user equipment sends a third request message to the application function entity, and the third request message is used to trigger the application function entity to send a first request message to the unified data management entity through the network open function entity.

[0191] The application function entity may determine whether to send the first request message based on information such as the contract with the user equipment, that is, determine whether to trigger the operation of switching the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice. The basis for the judgment may be whether the user has the right to access the second network slice, or whether the user's priority meets the requirements for accessing the second network slice.

[0192] After the network open function entity receives the first request message sent by the application function entity, it will send a response message to the first request message to the application function entity. The response message is used to notify the application function entity to confirm that the network open function entity has received the first request message sent by the application function entity and can successfully complete the transmission of subsequent messages.

[0193] After receiving the first request message sent by the application function entity, the network open function entity forwards the first request message to the unified data management entity. It should be noted that, due to the different receiving entities, the first request message forwarded by the network open function entity is not the Nnef_ParameterProvision_Update_Req message, but the Nudm_ParameterProvision_Update_Req message. Specifically, the Nudm_ParameterProvision_Update_Req message includes GPSI, that is, the GPSI corresponding to a user equipment, and at least one of the following: the identifier of the second network slice (S-NSSAI 2), slice selection indication, service quality parameter information (QoS parameter), and reason code. The identifier of the second network slice here is the identifier of the second network slice allowed to be accessed. The Nudm_ParameterProvision_Update_Req message may also include other information, and only part of the information is listed here.

[0194] After receiving the first request message (here referring to the Nudm_ParameterProvision_Update_Req message) forwarded by the network open function entity, the unified data management entity will send a response message to the first request message (i.e., the Nudm_ParameterProvision_Update_Req message) to the network open function entity. The response message is used to notify the network open function entity, confirming that the unified data management entity has received the first request message (i.e., the Nudm_ParameterProvision_Update_Req message) forwarded by the network open function entity, and can successfully complete the transmission of subsequent messages.

[0195] The unified data management entity sends a second request message to the access and mobility management function entity, wherein the second request message includes the SUPI and the identifier of the second network slice. In an embodiment of the present application, the second request message may be a session data management notification (Nudm_SDM_Notification) message, or other related interface messages, and the identifier of the second network slice is the identifier of the second network slice to which access is allowed. The unified data management entity completes the conversion from GPSI to SUPI through interaction with other network elements.

[0196] Optionally, after receiving the second request message, the access and mobility management function entity obtains the address of the target session management function entity corresponding to the second network slice from the network storage function entity.

[0197] Optionally, the network slice switching method in the embodiment of the present application also includes: a fourth request message sent by the access and mobility management function entity to the target session management function entity corresponding to the second network slice, and the fourth request message includes at least: the address of the source session management function entity corresponding to the first network slice, the PDU session identifier (PDU SessionID), and the session management context identifier (SM Context ID).

[0198] In an embodiment of the present application, at least one of the address, session identifier and session management context identifier of the source session management function entity is used to configure the user plane function entity corresponding to the second network slice, and the UPF configuration can also be configured during the network-triggered PDU session modification process.

[0199] In an embodiment of the present application, the fourth request message may be a PDU session request message (Nsmf_PDUsession_CreateSMContext Req) message for creating a session management context, or other related interface messages, and the address of the source session management function entity corresponding to the first network slice may be the source SMF address.

[0200] Optionally, before the application function entity sends the first request message to the unified data management entity through the network open function entity, the method also includes: the application function entity receives a third request message sent by the user equipment, wherein the third request message is used to trigger the switching process of the network slice; or, the access and mobility management function entity sends a fifth request message to the unified data management entity, wherein the fifth request message is used to obtain at least one of the following: the identifier of the second network slice (S-NSSAI 2) in the first request message, and the slice switching indication.

[0201] Optionally, the fifth request message may be a session data management subscription message (Nudm_SDM_Subscribe) message, or other related interface messages, and the fifth request message used to obtain the slice switching indication may be an S-NSSAI update indication (S-NSSAI update indicator) message.

[0202] The above steps provide two network slice switching schemes, namely, the first scheme is that the user equipment initiates a third request message, the third request message is a request to improve the quality of service, which is used to trigger the switching process of the network slice. After the application function entity receives the third request message sent by the user equipment, it converts the third request message into a slice switching indication and sends a first request message to the unified data management entity. The first request message includes a slice switching indication. According to the first request message, after data transmission and interaction between the various entities, the protocol data unit session corresponding to the user equipment is switched from the first network slice to the second network slice; the second scheme is not to initiate the third request message through the user equipment, but first by the network side The application function entity obtains the triggering condition for slice switching, that is, the service quality parameter information, and finds through service quality detection that the specified UE does not meet the service quality requirements, thereby triggering the slice switching operation for the UE, that is, the access and mobility management function entity sends a fifth request message to the unified data management entity, and then the application function entity sends a first request message (that is, the eleventh request message) to the unified data management entity. The first request message (that is, the eleventh request message) includes a slice switching indication. Based on the first request message (that is, the eleventh request message), after data transmission and interaction between the various entities, the protocol data unit session corresponding to the user equipment can be switched from the first network slice to the second network slice.

[0203] It should be noted that in the above-mentioned second solution, the step of the access and mobility management function entity sending the fifth request message to the unified data management entity is an optional step, that is, this step can be executed or not. Whether to execute this step depends on the actual situation and is not limited here.

[0204] It should be noted that the preferred implementation of the embodiments of the present application can be found in the relevant description in Example 1 and will not be repeated here.

[0205] It should be noted that for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

[0206] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods of each embodiment of the present application.

[0207] Example 3

[0208] based on Figure 1 and Figure 2a-2b The process in the embodiment shown in the figure, the embodiment of the present application provides another method for switching network slices, Figure 4 This is a flow chart of another network slice switching method according to an embodiment of the present application. Figure 4 As shown, the method includes the following processing steps:

[0209] Step S402: The access and mobility management function entity receives a second request message sent by the unified data management entity, where the second request message includes the SUPI and an identifier of the second network slice;

[0210] Optionally, the second request message may be a session data management notification (Nudm_SDM_Notification) message, or other related interface messages.

[0211] Step S404: The access and mobility management function entity switches the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice based on the second request message, wherein the second request message includes at least the identifier of the second network slice.

[0212] Optionally, before the access and mobility management function entity receives the second request message sent by the unified data management entity, the method also includes: the access and mobility management function entity sends a fifth request message to the unified data management entity, wherein the fifth request message is used to obtain at least one of the following: an identifier of the second network slice (S-NSSAI2) in the first request message, and a slice switching indication, wherein the first request message is used to enable the unified data management entity to send a second request message to the access and mobility management function entity.

[0213] Optionally, the fifth request message may be a session data management subscription (Nudm_SDM_Subscribe) message, or other related interface messages, and the fifth request message used to obtain the slice switching indication may be an S-NSSAI update indication (S-NSSAI update indicator) message.

[0214] Optionally, the method also includes: the access and mobility management function entity obtains the address of the target session management function entity corresponding to the second network slice, and after obtaining the address of the target session management function entity, the access and mobility management function entity sends a fourth request message to the target session management function entity, wherein the fourth request message includes at least: the address of the source session management function entity corresponding to the first network slice, the PDU session identifier (PDU Session ID), and the session management context identifier (SM Context ID).

[0215] In an embodiment of the present application, the fourth request message may be a PDU session request (Nsmf_PDUsession_CreateSMContext Req) message for creating a session management context, or other related interface messages, and the address of the source session management function entity corresponding to the first network slice may be the source SMF address.

[0216] Optionally, the access and mobility management function entity obtains the address of the target session management function entity corresponding to the second network slice, including: the access and mobility management function entity obtains the address of the target session management function entity corresponding to the second network slice from the network storage function entity.

[0217] Optionally, at least one of the address, session identifier and session management context identifier of the source session management function entity is used to configure the user plane function entity corresponding to the second network slice, and the UPF configuration can also be configured during the network-triggered PDU session modification process.

[0218] Optionally, the method further includes: the access and mobility management function entity receiving a response message to the fourth request message, wherein the response message is used to determine whether the session management context is successfully created.

[0219] In another optional embodiment, before the access and mobility management function entity receives a response message to the fourth request message, the method further includes the following steps: after the target session management function entity corresponding to the second network slice receives the fourth request message, it configures the corresponding UPF; after the target session management function entity corresponding to the second network slice configures the corresponding UPF, the target session management function entity sends an eighth request message to the source session management function entity, wherein the eighth request message includes at least one of the following: a session management context identifier (SM context ID), an identifier of the second network slice (S-NSSAI 2); the target session management function entity receives a response message to the eighth request message sent by the source session management function entity, wherein the response message to the eighth request message includes context information (SMcontext) corresponding to the session management context identifier.

[0220] In an embodiment of the present application, the eighth request message can be a PDU session management context request (Nsmf_PDUsession_Context Req) message, or it can be said to be other related interface messages, and the response message of the eighth request message can be a PDU session management context response (Nsmf_PDUsession_Context Res) message, or it can be said to be other related interface messages.

[0221] Optionally, before sending the eighth request message, the target SMF may send a PCF session management policy control update (Npcf_SMPolicyControl_Update) request message to the PCF, or other related interface messages, which are used to confirm whether the policy of the second network slice supports the transfer of session context across slices or whether it supports session switching, and may obtain the result of whether the policy supports the transfer of session context across slices or whether it supports session switching by receiving a PCF session management policy control update response message.

[0222] Optionally, before the target session management function entity receives a response message to the eighth request message sent by the source session management function entity, the method also includes: the source session management function entity sends a first message to the policy control function entity; the source session management function entity receives a response message to the first message, wherein the response message to the first message is used to determine whether session conversion (i.e., session switching) of slices is allowed across slices, which in this application refers to session switching between the first network slice and the second network slice.

[0223] Optionally, the first message in the embodiment of the present application may be a session management policy control update (Npcf_SMPolicyControl_Update) request message, or other related interface messages. This message is used to confirm whether the policy of the first network slice supports the transfer of session context across slices or whether it supports session switching.

[0224] It should be noted that when PCF allows session switching across slices, the source session management function entity sends a response message to the target session management function entity for the eighth request message.

[0225] In another optional embodiment, the method also includes: the source session management function entity sends a ninth request message to the unified data management entity, wherein the ninth request message includes at least SUPI and a slice switching indication; after the source session management function entity receives a response message to the ninth request message sent by the unified data management entity, the first message is sent to the policy control function entity, and the first message is used to request confirmation whether session switching (i.e., session switching) is allowed between slices (the first network slice and the second network slice in this application).

[0226] Optionally, the ninth request message may be a session data management request (Nudm_SDM_GetReq) message, or other related interface messages. This message may be sent by the SMF to the UDM during the PDU session establishment process, so that the SMF knows whether the UE is requested to perform corresponding slice switching operations when the QoS does not meet the requirements. Optionally, this message may also be triggered in the PDU session modification process.

[0227] In another optional embodiment of the present application, the response message of the ninth request message includes at least one of the following: quality of service parameter information, an identifier of the second network slice, and a slice switching indication.

[0228] Optionally, the response message to the ninth request message may be a Get Session Data Management Response (Nudm_SDM_GetRes) message, or other related interface messages.

[0229] In another optional embodiment mentioned above, after confirming with the policy control function entity that the policy allows session switching across slices, the access and mobility management function entity receives the tenth request message sent by the source session management function entity, wherein the tenth request message includes at least SUPI, a slice switching indication, and an identifier of the second network slice.

[0230] In another optional embodiment of the present application, the tenth request message is sent by the source session management function entity based on the quality of service parameter information, the identifier of the second network slice and at least one of the slice switch indication (Slice switch indication), and the policy information obtained from the policy control function entity. The tenth request message can be a session management context status notification (Nsmf_PDUSession_SMContextStatusNotify) message, or other related interface messages.

[0231] After receiving the tenth request message, the access and mobility management function entity obtains the address of the target session management function entity corresponding to the second network slice from the network storage function entity, and after obtaining the address of the target session management function entity, sends a fourth request message to the target session management function entity, wherein the fourth request message includes at least: the address of the source session management function entity corresponding to the first network slice, the PDU session identifier (PDU Session ID), and the session management context identifier (SM Context ID).

[0232] Optionally, at least one of the address, session identifier and session management context identifier of the source session management function entity is used to configure the user plane function entity corresponding to the second network slice, and the UPF configuration can also be configured during the network-triggered PDU session modification process.

[0233] Optionally, the fourth request message may be a PDU session request (Nsmf_PDUsession_CreateSMContext Req) message for creating a session management context, or other related interface messages, and the address of the source session management function entity corresponding to the first network slice may be the source SMF address.

[0234] Optionally, after the access and mobility management function entity receives a response message to the fourth request message, the method further includes: the access and mobility management function entity sends a second message to the user equipment, wherein the second message includes at least: an identifier of the second network slice and a target DNAI, and the user equipment accesses the corresponding second network slice according to the configuration information of the second network slice (for example, targetDNAI). The second message can be a command message sent by the AMF to the terminal device, such as a PDU session modification command (PDUSessionModificationCommand) or a UE configuration update command (UEConfigurationupdateCommand) or other command message, which is not specifically limited in this embodiment.

[0235] Optionally, after the access and mobility management function entity sends the second message to the user equipment, the access and mobility management function entity triggers a PDU session modification process, so that the UE switches to the network corresponding to the second network slice, and after the PDU session modification is completed, the access and mobility management function entity sends a slice switching completion confirmation message to the unified data management entity.

[0236] Optionally, before the access and mobility management function entity receives the second request message sent by the unified data management entity, the method also includes: the access and mobility management function entity sends a fifth request message to the unified data management entity, wherein the fifth request message is used to obtain at least one of the following: an identifier of the second network slice and a slice switching indication in the first request message; the access and mobility management function entity receives the second request message sent by the unified data management entity, wherein the second request message includes at least an identifier of the second network slice.

[0237] Optionally, the fifth request message may be a session data management subscription (Nudm_SDM_Subscribe) message, or other related interface messages, and the message used by the fifth request message to obtain the slice switching indication may be an S-NSSAI update indication (S-NSSAI update indicator) message. The second slice identifier may enable the AMF to identify the second network slice identifier corresponding to the second network slice that can be switched after obtaining the slice switching related request, and trigger the corresponding slice switching operation.

[0238] In an embodiment of the present application, the step of the access and mobility management function entity sending the fifth request message to the unified data management entity is an optional step, that is, this step can be executed or not. Whether to execute this step depends on the actual situation and is not limited here.

[0239] Optionally, after the access and mobility management function entity receives the second request message sent by the unified data management entity, the method also includes: the user equipment sends a registration request message to the access and mobility management function entity, wherein the registration request message includes at least: an identifier of the first network slice, and after the user equipment registers with the access and mobility management function entity, it accesses the first network slice.

[0240] In another optional embodiment, before the access and mobility management function entity receives the second request message sent by the unified data management entity, the method also includes: the application function entity sends an eleventh request message to the unified data management entity through the network open function entity, wherein the eleventh request message includes at least one of the following: a universal public user identity list, service quality parameter information, an identifier of the second network slice, a slice switching indication, and a reason code.

[0241] Optionally, the application function entity can send the condition information for determining whether the UE needs to switch slices to the 5G core network element, such as NEF and UDM, through the eleventh request message. The application function entity can determine whether to send the eleventh request message based on information such as the contract with the user equipment, and then the core network element, such as SMF, determines whether to perform slice switching based on the QoS parameters measured by the N4 interface, and finally the AMF initiates the migration of the session management context across slices.

[0242] Optionally, the eleventh request message may be a parameter update request (Nnef_ParameterProvision_Update_Req) ​​message, or other related interface messages, which are detected internally by the 5GC to determine whether to perform network slice switching; the identifier of the second network slice may be S-NSSAI 2, and the slice selection indication may be used to instruct the target network element (such as AMF) to perform a slice switching operation on the specified UE; the quality of service parameter (QoS parameter) may be used to instruct the target network element (such as SMF) to trigger a slice switching operation when it detects that the service quality of the specified UE does not meet the service quality parameter; the reason code is used to indicate that the service quality of the user equipment cannot meet or cannot meet the preset requirements, and the reason code (Reason code) may include the reason for requesting to switch the slice, for example, the content included in the reason code may be that the UE or the specified application cannot meet the service quality requirements in the accessed slice, etc. In addition to the above parameters, the eleventh request message may also include other parameter information, only part of which is listed here, and the specific other information included can be added according to actual conditions.

[0243] It should be noted that the preferred implementation methods of the embodiments of the present application can be found in the relevant descriptions in Examples 1-2 and will not be repeated here.

[0244] Example 4

[0245] based on Figure 1 and Figure 2a-2b The process in the embodiment shown in the figure, the embodiment of the present application provides another method for switching network slices, Figure 5 This is a flow chart of another network slice switching method according to an embodiment of the present application. Figure 5 As shown, the method includes the following processing steps:

[0246] Step S502: The unified data management entity receives a first request message sent by the application function entity through the network open function entity. The first request message is a parameter setting request message, and the first request message includes at least one of the following: an identifier of the second network slice, quality of service parameter information, a reason code indicating that the quality of service of the user equipment cannot meet the requirements, and a slice switching indication.

[0247] Step S504: Send a second request message to the access and mobility management function entity based on the first request message. The second request message includes at least an identifier of the second network slice allowed for access. The second request message is used to enable the access and mobility management function entity to switch the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice.

[0248] In another optional embodiment, the first request message can be replaced by the eleventh request message. When the unified data management entity receives the eleventh request message sent by the application function entity through the network open function entity, the eleventh request message includes at least one of the following: a universal public user identifier list, service quality parameter information, an identifier of the second network slice, a slice switching indication, and a reason code.

[0249] After sending the second request message to the access and mobility management function entity according to the first request message, the method also includes: receiving a ninth request message sent by the source session management function entity, wherein the ninth request message includes at least SUPI and a slice switching indication; sending a response message to the ninth request message to the source session management function entity, wherein the response message to the ninth request message includes at least one of the following: quality of service parameter information, an identifier of the second network slice, and a slice switching indication.

[0250] It should be noted that the preferred implementation methods of the embodiments of the present application can be found in the relevant descriptions in Examples 1-3 and will not be repeated here.

[0251] Example 5

[0252] based on Figure 1 and Figure 2a-2b The process in the embodiment shown in the figure, the embodiment of the present application provides another method for switching network slices, Figure 6 This is a flow chart of another network slice switching method according to an embodiment of the present application. Figure 6 As shown, the method includes the following processing steps:

[0253] Step S602: The network open function entity receives a first request message sent by the application function entity. The first request message is a parameter setting request message. The first request message includes at least one of the following: an identifier of the second network slice, quality of service parameter information, a reason code indicating that the quality of service of the user equipment cannot meet the requirements, and a slice switching indication.

[0254] Step S604: forward the first request message to the unified data management entity.

[0255] In another optional embodiment, the first request message can be replaced by the eleventh request message. When the network open function entity receives the eleventh request message sent by the application function entity, the eleventh request message includes at least one of the following: a universal public user identity list, service quality parameter information, an identifier of the second network slice, a slice switching indication, and a reason code; and the eleventh request message is forwarded to the unified data management entity.

[0256] It should be noted that the preferred implementation methods of the embodiments of the present application can be found in the relevant descriptions in Examples 1-4, which will not be repeated here.

[0257] Example 6

[0258] based on Figure 1 and Figure 2a-2b The process in the embodiment shown in the figure, the embodiment of the present application provides another method for switching network slices, Figure 7 This is a flow chart of another network slice switching method according to an embodiment of the present application. Figure 7 As shown, the method includes the following processing steps:

[0259] Step S702: The user equipment residing in the first network slice sends a slice switching indication to the application function entity;

[0260] Step S704: The user equipment receives a response message sent by the access and mobility management function entity, initiates a session modification process according to the response message, and connects to the data network.

[0261] In an embodiment of the present application, a slice switching indication is encapsulated in a third request message. That is, a user device residing in the first network slice network sends a third request message to an application function entity. The third request message is a request to improve the quality of service and is used to trigger the network slice switching process. After receiving the third request message sent by the user device, the application function entity converts the third request message into a slice switching indication and sends a first request message to the unified data management entity. The first request message includes the slice switching indication. The slice switching indication includes but is not limited to: an identifier of the second network slice.

[0262] In the above step S704, the response message sent by the access and mobility management function entity received by the user equipment may be a second message, wherein the second message is a network slice update message, and the second message includes at least: an identifier of the second network slice and a target DNAI, and the user equipment accesses the corresponding second network slice according to the configuration information of the second network slice (for example, the target DNAI). The second message may be a command message sent by the AMF to the terminal device, such as a PDU session modification command (PDUSessionModificationCommand) or a UE configuration update command (UEConfigurationupdateCommand) or other command message, which is not specifically limited in this embodiment.

[0263] It should be noted that the preferred implementation methods of the embodiments of the present application can be found in the relevant descriptions in Examples 1-5, which will not be repeated here.

[0264] Example 7

[0265] based on Figure 1 and Figure 2a-2b The process in the embodiment shown in the figure, the embodiment of the present application provides another method for switching network slices, Figure 8 This is a flow chart of another network slice switching method according to an embodiment of the present application. Figure 8 As shown, the method includes the following processing steps:

[0266] Step S802: The target session management function entity corresponding to the second network slice sends an eighth request message to the source session management function entity corresponding to the first network slice, wherein the eighth request message includes at least one of the following: a session management context identifier (SM context ID) and an identifier of the second network slice (S-NSSAI 2);

[0267] Step S804: The target session management function entity receives a response message to the eighth request message sent by the source session management function entity, wherein the response message to the eighth request message includes context information (SM context) corresponding to the session management context identifier.

[0268] Optionally, the eighth request message may be a PDU session management context request (Nsmf_PDUsession_Context Req) message, or other related interface messages, and the response message of the eighth request message may be a PDU session management context response (Nsmf_PDUsession_Context Res) message, or other related interface messages.

[0269] Optionally, before the target session management function entity receives a response message to the eighth request message sent by the source session management function entity, the method also includes: the source session management function entity sends a first message to the policy control function entity; the source session management function entity receives a response message to the first message, wherein the response message to the first message is used to determine whether session switching is allowed across slices, which in this application refers to session switching between the first network slice and the second network slice.

[0270] It should be noted that when PCF allows session switching across slices, the source session management function entity sends a response message to the target session management function entity for the eighth request message.

[0271] It should be noted that the preferred implementation methods of the embodiments of the present application can be found in the relevant descriptions in Examples 1-7, which will not be repeated here.

[0272] Example 8

[0273] based on Figure 1 and Figure 2a-2b The process in the embodiment shown in the figure, the embodiment of the present application provides another network slice switching method, which includes the following processing steps:

[0274] The application function entity sends a first request message to the unified data management entity through the network open function entity, wherein the first request message includes at least an identifier of the second network slice, and the first request message is used to enable the unified data management entity to send a second request message to the access and mobility management function entity, and the second request message is used to enable the access and mobility management function entity to switch the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice.

[0275] Specifically, when the UE accesses the 5G network and resides on slice S-NSSAI 1, the AF sends an Nnef_ParameterProvision_Req message to the NEF, which includes GPSI and S-NSSAI 2, etc.; the NEF sends a Nudm_ParameterProvision_Req message to the UDM, which includes GPSI, AS-NSSAI 2, etc.

[0276] It should be noted that the preferred implementation methods of the embodiments of the present application can be found in the relevant descriptions in Examples 1-7 and will not be repeated here.

[0277] Example 9

[0278] based on Figure 1 and Figure 2a-2bThe process in the embodiment shown in the figure, the embodiment of the present application provides another method for switching network slices, Figure 9 This is a flow chart of another network slice switching method according to an embodiment of the present application. Figure 9 As shown, the method includes the following processing steps:

[0279] Step S902: The session management function entity queries the policy control function entity whether the protocol data unit session corresponding to the user equipment is allowed to be switched between different network slices;

[0280] Step S904, when switching between different network slices is allowed, the session management function entity sends a notification message to the user plane function entity, so that the user plane function entity switches the session of the user equipment to the network slice corresponding to the second network slice identifier, wherein the notification message includes at least: the identifier of the second network slice.

[0281] It should be noted that the preferred implementation methods of the embodiments of the present application can be found in the relevant descriptions in Examples 1-8 and will not be repeated here.

[0282] Example 10

[0283] This embodiment provides a network slicing switching device for implementing the method for quality of service management in embodiment 2, such as Figure 10 As shown, the device includes:

[0284] The communication module 1002 is configured to send a first request message to the unified data management entity according to the slice switching indication, where the first request message is a parameter setting request message, and the first request message includes at least one of the following: an identifier of the second network slice, quality of service parameter information, a reason code indicating that the quality of service of the user equipment cannot meet the requirements, and the slice switching indication;

[0285] Processing module 1004 is used to enable the unified data management entity to send a second request message to the access and mobility management function entity after receiving the first request message, where the second request message includes at least an identifier of the second network slice, and the second request message is used to enable the access and mobility management function entity to switch the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice.

[0286] It should be noted that the preferred implementation of this embodiment can be found in the relevant descriptions in Examples 1-9, which will not be repeated here.

[0287] Example 11

[0288] This embodiment provides a network slice switching method, which is applied in a communication system 1100. Figure 11As shown, the system includes: an application function entity, a network open function entity, a unified data management entity, an access and mobility management function entity, a target session management function entity corresponding to the second network slice, and a user equipment, wherein:

[0289] The application function entity 1101 is configured to send a first request message to the unified data management entity according to the slice switching indication, where the first request message is a parameter setting request message, and the first request message includes at least one of the following: an identifier of the second network slice, quality of service parameter information, a reason code indicating that the quality of service of the user equipment cannot meet the requirements, and the slice switching indication;

[0290] The network open function entity 1102 is configured to receive a first request message sent by the application function entity and forward the first request message to the unified data management entity;

[0291] The unified data management entity 1103 is configured to receive the first request message forwarded by the network open function entity, and send a second request message to the access and mobility management function entity according to the first request message, where the second request message includes at least an identifier of the second network slice;

[0292] The access and mobility management function entity 1104 is configured to receive the second request message and switch the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice;

[0293] The target session management function entity 1105 corresponding to the second network slice is configured to send an eighth request message to the source session management function entity corresponding to the first network slice, wherein the eighth request message includes at least one of the following: a session management context identifier and an identifier of the second network slice; and receive a response message to the eighth request message sent by the source session management function entity, wherein the response message to the eighth request message includes context information corresponding to the session management context identifier;

[0294] User equipment 1106 is used to send a slice switching indication to the application function entity, and receive a response message sent by the access and mobility management function entity, initiate a session protocol data unit modification process based on the response message, and connect to the data network.

[0295] It should be noted that the preferred implementation of this embodiment can be found in the relevant descriptions in Examples 1-7, which will not be repeated here.

[0296] Example 12

[0297] This embodiment of the present application also provides another network slice switching method, including:

[0298] The application function entity sends a thirteenth request message to the policy control function entity through the network open function entity, wherein the thirteenth request message includes an identifier of the second network slice, and the thirteenth request message is used to enable the policy control function entity to send a fourteenth request message to the access and mobility management function entity, and the fourteenth request message is used to enable the access and mobility management function entity to switch the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice.

[0299] It should be noted that the above-mentioned thirteenth request message can be a message dedicated to indicating slice switching, or it can be a message in which a second network slice identifier is added to an existing message, wherein the existing message can include an existing message between the AF entity and the NEF entity and an existing message between the NEF and the PCF entity, or it can be an interactive message between any two of the three.

[0300] It should be noted that the preferred implementation of this embodiment can be found in the relevant descriptions in Examples 1-11 and will not be repeated here.

[0301] The serial numbers of the above embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0302] In the above embodiments of the present application, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0303] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of the units can be a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0304] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0305] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0306] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0307] The above is only a preferred embodiment of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A network slice switching method, characterized in that: include: The application function entity sends a first request message to the unified data management entity through the network open function entity, wherein the first request message includes a slice switching indication, and the first request message is used to enable the unified data management entity to send a second request message to the access and mobility management function entity, and the second request message is used to enable the access and mobility management function entity to switch the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice; The access and mobility management function entity is also used to send a second message to the user equipment when a third message is received, wherein the third message is sent when the session management function entity confirms that the policy allows session switching across slices, and the second message includes a network slice update message, which includes at least: an identifier and configuration information of the second network slice, and the user equipment is used to access the corresponding second network slice based on the configuration information of the second network slice.

2. The method according to claim 1, characterized in that The first request message also includes at least one of the following: an identifier of the second network slice, service quality parameter information, and a reason code indicating that the service quality of the user equipment cannot meet the requirements.

3. The method according to claim 1, characterized in that Before the application function entity sends the first request message to the unified data management entity through the network open function entity, the method further includes: The application function entity receives a third request message sent by user equipment, wherein the third request message is used to trigger the application function entity to send the first request message.

4. The method according to claim 1, wherein The method further comprises: The access and mobility management function entity sends a fourth request message to the target session management function entity corresponding to the second network slice, and the fourth request message includes at least one of the following: the address, session identifier and session management context identifier of the source session management function entity corresponding to the first network slice.

5. The method according to claim 1, wherein Before the application function entity sends the first request message to the unified data management entity through the network open function entity, the method further includes: The application function entity receives a third request message sent by the user equipment, wherein the third request message is used to trigger a switching process of the network slice; or, The access and mobility management function entity sends a fifth request message to the unified data management entity, wherein the fifth request message is used to obtain at least one of the following: the identifier of the second network slice in the first request message and the slice switching indication.

6. The method according to claim 1, wherein The first network slice and the second network slice are network slices under the same network function NF; the method further includes: The access and mobility management function entity sends a sixth request message to the first session management function entity, so that the first session management function entity switches the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice, wherein the sixth request message includes at least: an identifier of the second network slice corresponding to the first session management function entity.

7. The method according to claim 6, characterized in that The method further comprises: The user plane function entity receives a seventh request message sent by the first session management function entity, where the seventh request message carries an identifier of the second network slice; The user plane function entity switches the user equipment from the first network slice to the second network slice.

8. The method according to claim 1, characterized in that The method further comprises: The session management function entity queries the policy control function entity whether the protocol data unit session corresponding to the user equipment is allowed to be switched between different network slices; When switching between different network slices is allowed, the session management function entity sends a notification message to the user plane function entity, wherein the notification message includes at least: an identifier of the second network slice.

9. The method according to any one of claims 1 to 8, characterized in that The slice switching indication includes: an identifier of the second network slice; or the slice switching indication includes: indication information specifically used to instruct the protocol data unit session of the user equipment to switch from the first network slice to the second network slice.

10. A network slice switching method, characterized in that: include: The application function entity sends a first request message to the unified data management entity through the network open function entity, wherein the first request message includes at least an identifier of the second network slice, and the first request message is used to enable the unified data management entity to send a second request message to the access and mobility management function entity, and the second request message is used to enable the access and mobility management function entity to switch the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice; The access and mobility management function entity is also used to send a second message to the user equipment when a third message is received, wherein the third message is sent when the session management function entity confirms that the policy allows session switching across slices, and the second message includes a network slice update message, which includes at least: an identifier and configuration information of the second network slice, and the user equipment is used to access the corresponding second network slice based on the configuration information of the second network slice.

11. A network slice switching method, characterized in that: include: The access and mobility management function entity receives the second request message sent by the unified data management entity; The access and mobility management function entity switches the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice based on the second request message, wherein the second request message includes at least an identifier of the second network slice; The access and mobility management function entity is also used to send a second message to the user equipment when a third message is received, wherein the third message is sent when the session management function entity confirms that the policy allows session switching across slices, and the second message includes a network slice update message, which includes at least: an identifier and configuration information of the second network slice, and the user equipment is used to access the corresponding second network slice based on the configuration information of the second network slice.

12. The method according to claim 11, characterized in that Before the access and mobility management function entity receives the second request message sent by the unified data management entity, the method further includes: The access and mobility management function entity sends a fifth request message to the unified data management entity, wherein the fifth request message is used to obtain at least one of the following: an identifier of the second network slice in the first request message, a slice switching indication, wherein the first request message is used to enable the unified data management entity to send the second request message to the access and mobility management function entity.

13. The method according to claim 11, characterized in that The method further comprises: The access and mobility management function entity obtains the address of the target session management function entity corresponding to the second network slice.

14. The method according to claim 13, wherein: The method further comprises: The access and mobility management function entity sends a fourth request message to the target session management function entity, wherein the fourth request message includes: the address, session identifier, and session management context identifier of the source session management function entity corresponding to the first network slice.

15. The method according to claim 13, characterized in that The access and mobility management function entity obtains the address of the target session management function entity corresponding to the second network slice, including: the access and mobility management function entity obtains the address of the target session management function entity corresponding to the second network slice from the network storage function entity.

16. The method according to claim 15, characterized in that At least one of the address, session identifier and session management context identifier of the source session management function entity is used to configure the user plane function entity corresponding to the second network slice.

17. The method according to claim 13, characterized in that The method further comprises: The access and mobility management function entity receives a response message to the fourth request message, wherein the response message is used to determine whether the session management context is successfully created.

18. The method according to claim 16, characterized in that Before the access and mobility management function entity receives a response message to the fourth request message, the method further includes: The target session management function entity sends an eighth request message to the source session management function entity, wherein the eighth request message includes at least one of the following: the session management context identifier and the identifier of the second network slice; The target session management function entity receives a response message to the eighth request message sent by the source session management function entity, wherein the response message to the eighth request message includes context information corresponding to the session management context identifier.

19. The method according to claim 18, characterized in that Before the target session management function entity receives a response message to the eighth request message sent by the source session management function entity, the method further includes: The source session management function entity sends a first message to the policy control function entity; The source session management function entity receives a response message to the first message, wherein the response message to the first message is used to determine whether slice conversion is allowed.

20. The method according to claim 17, wherein After the access and mobility management function entity receives a response message to the fourth request message, the method further includes: The access and mobility management function entity sends a second message to the user equipment, wherein the second message includes at least: an identifier of the second network slice.

21. The method according to claim 11, wherein Before the access and mobility management function entity receives the second request message sent by the unified data management entity, the method further includes: The access and mobility management function entity sends a fifth request message to the unified data management entity, wherein the fifth request message is used to obtain at least one of the following: an identifier of the second network slice in the first request message and a slice switching indication.

22. The method according to claim 11, characterized in that After the access and mobility management function entity receives the second request message sent by the unified data management entity, the method further includes: The user equipment sends a registration request message to the access and mobility management function entity, wherein the registration request message includes at least: an identifier of the first network slice.

23. The method according to claim 11, wherein The method further comprises: The source session management function entity sends a ninth request message to the unified data management entity, wherein the ninth request message includes at least a slice switching indication; The source session management function entity receives a response message to the ninth request message, wherein the response message to the ninth request message includes at least one of the following: quality of service parameter information, an identifier of the second network slice, and the slice switching indication.

24. The method according to claim 23, wherein The method further comprises: The access and mobility management function entity receives the tenth request message sent by the source session management function entity, wherein the tenth request message includes at least one of the following: an identifier of the second network slice and a slice switching indication.

25. The method according to claim 24, characterized in that The method further comprises: The tenth request message is sent by the source session management function entity based on the service quality parameter information, the identifier of the second network slice and at least one of the slice switching indication, and the policy information obtained from the policy control function entity.

26. The method according to claim 21, characterized in that Before the access and mobility management function entity receives the second request message sent by the unified data management entity, the method further includes: The application function entity sends an eleventh request message to the unified data management entity through the network open function entity, wherein the eleventh request message includes at least one of the following: a universal public user identifier list, service quality parameter information, an identifier of the second network slice, and a slice switching indication.

27. A network slice switching method, characterized in that: include: The unified data management entity receives a first request message sent by the application function entity through the network open function entity, where the first request message is a parameter setting request message, and the first request message includes at least one of the following: an identifier of the second network slice, quality of service parameter information, a reason code for indicating that the quality of service of the user equipment cannot meet the requirements, and a slice switching indication; Sending a second request message to the access and mobility management function entity according to the first request message, where the second request message includes at least an identifier of the second network slice allowed to be accessed, and the second request message is used to enable the access and mobility management function entity to switch the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice; The access and mobility management function entity is also used to send a second message to the user equipment when a third message is received, wherein the third message is sent when the session management function entity confirms that the policy allows session switching across slices, and the second message includes a network slice update message, which includes at least: an identifier and configuration information of the second network slice, and the user equipment is used to access the corresponding second network slice based on the configuration information of the second network slice.

28. The method according to claim 27, characterized in that After sending a second request message to the access and mobility management function entity according to the first request message, the method further includes: receiving a ninth request message sent by the source session management function entity, wherein the ninth request message includes at least a slice switching indication; A response message to the ninth request message is sent to the source session management function entity, wherein the response message to the ninth request message includes at least one of the following: quality of service parameter information, an identifier of the second network slice, and the slice switching indication.

29. A network slice switching method, characterized in that: include: The network open function entity receives a first request message sent by the application function entity, where the first request message is a parameter setting request message, and the first request message includes at least one of the following: an identifier of the second network slice, quality of service parameter information, a reason code for indicating that the quality of service of the user equipment cannot meet the requirements, and a slice switching indication; Forwarding the first request message to a unified data management entity; The first request message is used to enable the unified data management entity to send a second request message to the access and mobility management function entity, and the second request message is used to enable the access and mobility management function entity to switch the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice. The access and mobility management function entity is also used to send a second message to the user equipment when a third message is received, wherein the third message is sent when the session management function entity confirms that the policy allows session switching across slices, and the second message includes a network slice update message, and the second message includes at least: an identifier and configuration information of the second network slice, and the user equipment is used to access the corresponding second network slice based on the configuration information of the second network slice.

30. A network slice switching method, characterized in that: include: The user equipment residing in the first network slice sends a slice switching indication to the application function entity; The user equipment receives a response message sent by the access and mobility management function entity, initiates a session modification process according to the response message, and connects to the data network; The application function entity is used to send a first request message to the unified data management entity through the network open function entity when receiving the slice switching indication, wherein the first request message includes the slice switching indication, and the first request message is used to enable the unified data management entity to send a second request message to the access and mobility management function entity, and the second request message is used to enable the access and mobility management function entity to switch the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice. The access and mobility management function entity is also used to send a second message to the user equipment when receiving a third message, wherein the third message is sent when the session management function entity confirms that the policy allows session switching across slices, and the second message includes a network slice update message, and the second message includes at least: an identifier and configuration information of the second network slice, and the user equipment is used to access the corresponding second network slice based on the configuration information of the second network slice.

31. The method according to claim 30, wherein The slice switching indication includes at least: an identifier of the second network slice.

32. A network slice switching method, characterized in that: include: The target session management function entity corresponding to the second network slice sends an eighth request message to the source session management function entity corresponding to the first network slice, wherein the eighth request message includes at least one of the following: a session management context identifier and an identifier of the second network slice; The target session management function entity receives a response message to the eighth request message sent by the source session management function entity, and after receiving the response message to the eighth request message, sends a third message to the access and mobility management function entity, wherein the response message to the eighth request message includes context information corresponding to the session management context identifier; The access and mobility management function entity is also used to send a second message to the user equipment when a third message is received, wherein the third message is sent when the session management function entity confirms that the policy allows session switching across slices, and the second message includes a network slice update message, which includes at least: an identifier and configuration information of the second network slice, and the user equipment is used to access the corresponding second network slice based on the configuration information of the second network slice.

33. The method according to claim 32, characterized in that Before the target session management function entity receives a response message to the eighth request message sent by the source session management function entity, the method further includes: The source session management function entity sends a first message to the policy control function entity; The source session management function entity receives a response message to the first message, wherein the response message to the first message is used to determine whether slice conversion is allowed.

34. A network slice switching method, characterized in that: include: The session management function entity queries the policy control function entity whether the protocol data unit session corresponding to the user equipment is allowed to be switched between different network slices; When switching between different network slices is allowed, the session management function entity sends a notification message to the user plane function entity so that the user plane function entity switches the protocol data unit session of the user equipment to the network slice corresponding to the second network slice identifier, and sends a third message to the access and mobility management function entity so that the access and mobility management function entity sends a second message to the user equipment, wherein the notification message includes at least: the identifier of the second network slice, the second message includes a network slice update message, and the second message includes at least: the identifier and configuration information of the second network slice, and the user equipment is used to access the corresponding second network slice according to the configuration information of the second network slice.

35. A network slicing switching device, characterized in that: include: a communication module, configured to send a first request message to a unified data management entity according to the slice switching indication, where the first request message is a parameter setting request message, and the first request message includes at least one of the following: an identifier of the second network slice, quality of service parameter information, a reason code indicating that the quality of service of the user equipment cannot meet the requirements, and the slice switching indication; a processing module, configured to, after receiving the first request message, enable the unified data management entity to send a second request message to the access and mobility management function entity, where the second request message includes at least an identifier of the second network slice, and the second request message is used to enable the access and mobility management function entity to switch the user equipment from the first network slice to the second network slice; The access and mobility management function entity is also used to send a second message to the user equipment when a third message is received, wherein the third message is sent when the session management function entity confirms that the policy allows session switching across slices, and the second message includes a network slice update message, which includes at least: an identifier and configuration information of the second network slice, and the user equipment is used to access the corresponding second network slice based on the configuration information of the second network slice.

36. A communication system, characterized in that: include: Application function entity, network open function entity, unified data management entity, access and mobility management function entity, target session management function entity corresponding to the second network slice, and user equipment, wherein: The application function entity is configured to send a first request message to the unified data management entity according to the slice switching indication, where the first request message is a parameter setting request message, and the first request message includes at least one of the following: an identifier of the second network slice, quality of service parameter information, a reason code indicating that the quality of service of the user equipment cannot meet the requirements, and the slice switching indication; The network open function entity is configured to receive a first request message sent by the application function entity, and forward the first request message to the unified data management entity; The unified data management entity is configured to receive the first request message forwarded by the network open function entity, and send a second request message to the access and mobility management function entity according to the first request message, where the second request message includes at least an identifier of the second network slice; The access and mobility management function entity is configured to receive the second request message and switch the user equipment from the first network slice to the second network slice. The access and mobility management function entity is further configured to send a second message to the user equipment when a third message is received, wherein the third message is sent when the session management function entity confirms that a policy allows session switching between slices. The second message includes a network slice update message, and the second message includes at least: an identifier and configuration information of the second network slice, and the user equipment is configured to access the corresponding second network slice according to the configuration information of the second network slice; The target session management function entity corresponding to the second network slice is used to send an eighth request message to the source session management function entity corresponding to the first network slice, wherein the eighth request message includes at least one of the following: a session management context identifier and an identifier of the second network slice; and receive a response message to the eighth request message sent by the source session management function entity, wherein the response message to the eighth request message includes context information corresponding to the session management context identifier; The user equipment is used to send the slice switching indication to the application function entity, and receive a response message sent by the access and mobility management function entity, initiate a session protocol data unit modification process based on the response message, and connect to the data network.

37. A network slice switching method, characterized in that: include: The application function entity sends a thirteenth request message to the policy control function entity through the network open function entity, wherein the thirteenth request message includes a slice switching indication, and the thirteenth request message is used to enable the policy control function entity to send a fourteenth request message to the access and mobility management function entity, and the fourteenth request message is used to enable the access and mobility management function entity to switch the protocol data unit session corresponding to the user equipment from the first network slice to the second network slice; The access and mobility management function entity is also used to send a second message to the user equipment when a third message is received, wherein the third message is sent when the session management function entity confirms that the policy allows session switching across slices, and the second message includes a network slice update message, which includes at least: an identifier and configuration information of the second network slice, and the user equipment is used to access the corresponding second network slice based on the configuration information of the second network slice.

Images