CN114071605A - A switching method, device and system - Google Patents

Abstract

This embodiment of the present application provides a method for handover. The method includes: the target access network device acquires session information, where the session information indicates a session to be handed over from the source access network device to the target access network device; wherein, the network slice associated with the session is the first network slice; if If the target access network device does not support the first network slice, obtain a second network slice supported by the target access network device and corresponding to the first network slice, and prepare for handover for the session according to the second network slice . Through the above method, when the target access network device does not support the first network slice associated with the session to be switched, the target access network device does not release the session, but maps the network slice of the session to the target access network slice The second network slice supported by the network device and corresponding to the first network slice is used to prepare the session for handover, which avoids the interruption of the session during the handover process and ensures the service continuity of the terminal device during the handover process.

Description

A switching method, device and system

technical field

The present application relates to communication technologies, and in particular, to a handover method, apparatus and system.

Background technique

The third generation partnership project (3rd generation partnership project, 3GPP) standard group released the fifth-generation mobile communication technology (fifth-generation, 5G) network communication technology. 5G networks support network slices. Generally, different network slices can have different network capabilities and network characteristics to meet different service requirements. For example, some services require the network to provide support for large bandwidth and low latency; some services require the network to provide access support for massive terminal devices, but have lower requirements for bandwidth and latency. A physical network can support multiple network slices, and different network slices are logically isolated from each other. In this way, a physical network of the operator can meet the differentiated requirements of the service data flow of different applications on the network.

In order to support network slicing, 3GPP defines that terminal devices and networks use Network Slice Selection Assistance Information (NSSAI) to select appropriate network slices for various application services. The NSSAI consists of a set of single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI). Each S-NSSAI can identify a network slice.

In actual deployment, operators may support different network slices in different areas of a physical network. For example, it may support enhanced mobile broadband (Enhanced Mobile Broadband, eMBB) slices in the entire network, and support ultra-low latency and ultra-reliable communication (Ultra-Reliable and Low-Latency Communication, URLLC) slices in the region where an enterprise is located. Therefore, network slices supported by access networks in different regions may be different. When a terminal device (User Equipment, UE) establishes a session associated with a network slice in one area and moves from this area to another area, the ongoing service of the UE may be interrupted.

SUMMARY OF THE INVENTION

The embodiment of the present application provides a handover method, which ensures the service continuity of the terminal device during the handover process.

In order to achieve the above purpose, the embodiments of the present application provide the following solutions.

In a first aspect, an embodiment of the present application provides a handover method, the method includes: a target access network device obtains session information, where the session information indicates a session to be handed over from a source access network device to the target access network device; The network slice associated with the session is the first network slice; if the target access network device does not support the first network slice, the target access network device obtains a network slice supported by the target access network device that is compatible with the first network slice. A second network slice corresponding to the slice; the target access network device prepares for handover for the session according to the second network slice.

With the handover method provided in the first aspect, when the target access network device does not support acquiring the first network slice associated with the session to be handed over, the target access network device does not release the session, but the network Slice mapping prepares the session for handover for the network slice supported by the target access network device, which avoids the interruption of services carried in the session during the handover process, and ensures the service continuity of the terminal device.

As a possible implementation manner, the method further includes: the second network slice satisfies the service level agreement of the first network slice (for example, the service requirement information corresponding to the second network slice satisfies the service level agreement of the first network slice) ; or, the second network slice corresponds to the same service as the first network slice.

Through the switching method provided by one of the above possible implementations, the second network slice corresponding to the first network slice is determined according to the service level agreement of the network slice or the service corresponding to the network slice.

As a possible implementation manner, the target access network device performs handover preparation for the session according to the second network slice, including: the target access network device allocates resources for the session according to the second network slice; the target access network device allocates resources for the session; The device sends first information to the terminal device, the first information indicates the resource; the target access network device sends second information to the source access network device, the second information indicates that the target access network device accepts the session switch.

With the handover method provided by one of the above possible implementations, the target access network device allocates resources for the session according to the second network slice, and sends the resources to the terminal device to ensure that the terminal device successfully switches the session to the target access network. network equipment.

As a possible implementation manner, allocating resources to the session according to the second network slice by the target access network device includes: configuring, by the target access network device, a physical channel and a physical channel corresponding to the second network slice for the session. / or logical channel.

With the handover method provided by one of the above possible implementations, the target access network device allocates resources for the session by configuring the physical channel and/or logical channel corresponding to the second network slice for the session.

As a possible implementation manner, obtaining, by the target access network device, a second network slice supported by the target access network device corresponding to the first network slice includes: the target access network device according to the first network slice The second network slice is obtained by the corresponding relationship with the second network slice.

As a possible implementation manner, the method further includes: the target access network device receiving the corresponding relationship from the source access network device; or, the target access network device receiving the corresponding relationship from the core network element.

As a possible implementation manner, the method further includes: setting, by the target access network device, a network slice associated with the session as the second network slice.

As a possible implementation manner, the method further includes: the target access network device stores second information, where the second information indicates that the network slice of the session is mapped from the first network slice to the second network slice.

With the handover method provided by one of the above possible implementations, when the session is to be handed over to other access network devices, the other access network devices can obtain the second information from the target access network device, and use the second information according to the first access network device. The second information preferentially selects the first network slice to allocate resources for the session.

As a possible implementation manner, the method further includes: the target access network device sends network slice mapping information to the core network element, where the network slice mapping information enables providing services for the session according to the second network slice. When the target access network device accepts the session switch, it generates the network slice mapping information according to the correspondence between the first network slice and the second network slice.

With the handover method provided by one of the above possible implementations, the core network element provides services for the session according to the second network slice, and maps the network slice associated with the session to the second network slice, avoiding the need for a session during the handover process. The interruption of the carried services ensures the service continuity of the terminal equipment.

As a possible implementation manner, the network slice mapping information includes: a network slice identifier of the first network slice and a network slice identifier of the second network slice.

In a second aspect, an embodiment of the present application provides a method for handover. The method includes: a source access network device obtains a correspondence between a first network slice and a second network slice; and the source access network device sends a message to a target access network device. The corresponding relationship; wherein, the target access network device supports the second network slice and does not support the first network slice, and the corresponding relationship enables when the session associated with the first network slice is to be switched to the target access network device, the target access network device should perform handover preparation for the session according to the second network slice.

With the handover method provided in the second aspect, the source access network device sends the corresponding relationship between the first network slice and the second network slice to the target access network device, and the target access network device does not support the association of the session to be handed over. When the target access network device does not release the session, it maps the network slice of the session to the network slice supported by the target access network device to prepare the session for handover, which avoids the need for handover during the handover process. The interruption of the service carried in the session ensures the service continuity of the terminal device.

As a possible implementation manner, the method further includes: the second network slice satisfies the service level agreement of the first network slice (for example, the service requirement information corresponding to the second network slice satisfies the service level agreement of the first network slice) ; or, the second network slice corresponds to the same service as the first network slice.

Through the switching method provided by one of the above possible implementations, the corresponding relationship between the first network slice and the second network slice is determined according to the service level agreement of the network slice or the service corresponding to the network slice.

As a possible implementation manner, acquiring the corresponding relationship by the source access network device includes: receiving the corresponding relationship from the core network by the source access network device.

In a third aspect, an embodiment of the present application provides a method for handover. The method includes: acquiring a correspondence between a first network slice and a second network slice; sending the correspondence to a target access network device; wherein the target access network The network device supports the second network slice and does not support the first network slice, and the corresponding relationship enables when the session associated with the first network slice is to be switched to the target access network device, the target access network The device should prepare for handover for the session according to the second network slice.

Through the handover method provided in the third aspect, the corresponding relationship between the first network slice and the second network slice is obtained, and the corresponding relationship is sent to the target access network device, where the target access network device does not support the session to be handed over. When the associated first network slice is used, the target access network device does not release the session, but maps the network slice of the session to the network slice supported by the target access network device to prepare the session for handover, avoiding the handover process. The interruption of the service carried in the middle session ensures the service continuity of the terminal equipment.

As a possible implementation manner, the acquiring the corresponding relationship includes: receiving the corresponding relationship from the unified data management network element.

As a possible implementation manner, the receiving the corresponding relationship from the unified data management network element includes: acquiring subscription data of the terminal device from the unified data management network element, where the subscription data includes the corresponding relationship.

As a possible implementation manner, the acquiring the corresponding relationship includes: receiving the corresponding relationship from a network slice selection function or a policy control function.

As a possible implementation manner, the method further includes: the second network slice satisfies the service level agreement of the first network slice (for example, the service requirement information corresponding to the second network slice satisfies the service level agreement of the first network slice) ; or, the second network slice corresponds to the same service as the first network slice.

Through the switching method provided by one of the above possible implementations, the corresponding relationship between the first network slice and the second network slice is determined according to the service level agreement of the network slice or the service corresponding to the network slice.

As a possible implementation manner, the sending the corresponding relationship to the target access network device includes: sending the corresponding relationship to the target access network device through the target core network element; or sending the corresponding relationship to the target access network device through the source access network device The network access device sends the corresponding relationship.

With the handover method provided by the above possible implementation manner, the target core network element or the source access network device sends the corresponding relationship between the first network slice and the second network slice to the target access network device. When the network access device does not support the first network slice associated with the session to be switched, the target access network device does not release the session, but maps the network slice of the session to the network slice supported by the target access network device to The session is prepared for handover, which avoids the interruption of the services carried in the session during the handover process, and ensures the service continuity of the terminal equipment.

As a possible implementation manner, the method further includes: receiving network slice mapping information from the target access network device, and providing a service for the session according to the second network slice based on the network slice mapping information.

With the handover method provided by the above possible implementation manner, the session is provided with services according to the second network slice based on the network slice mapping information, and the network slice associated with the session is mapped to the second network slice, so as to avoid any problems in the session during the handover process. The interruption of the carried services ensures the service continuity of the terminal equipment.

As a possible implementation manner, the providing services for the session according to the second network slice based on the network slice mapping information includes: selecting a user plane function network element for the session according to the second network slice; establishing the session for the session The connection between the target access network device and the user plane functional network element.

With the handover method provided by one of the above possible implementations, a user plane functional network element is selected for the session according to the second network slice, and the network slice associated with the session is mapped to the second network slice, so as to avoid the session in the handover process. The interruption of the carried services ensures the service continuity of the terminal equipment.

As a possible implementation manner, establishing a connection between the target access network device and the user plane function network element for the session further includes: establishing the user plane function network element and the anchor user of the session for the session Connections between plane functional network elements.

As a possible implementation manner, the providing a service for the session according to the second network slice includes: acquiring a charging rule of the second network slice; and performing charging control on the session by using the charging rule.

The switching method provided by one of the above possible implementations ensures the accuracy of charging after session switching.

As a possible implementation manner, the method further includes: sending the network slice mapping information to the session management network element of the session, so as to enable the session management network element to provide services for the session according to the second network slice.

In a fourth aspect, an embodiment of the present application provides a handover method. The method includes: receiving network slice mapping information sent by a first communication network element, where the network slice mapping information indicates that a target access network device will be handed over to the target access network. The network slice associated with the session of the network access device is set as the second network slice; the session is provided with services according to the second network slice.

With the handover method provided in the fourth aspect, the session is provided with a service according to the second network slice indicated by the network slice mapping information, and the network slice associated with the session is mapped to the second network slice, thereby avoiding any problems in the session during the handover process. The interruption of the carried services ensures the service continuity of the terminal equipment.

As a possible implementation manner, the network slice mapping information includes: a network slice identifier of the first network slice and a network slice identifier of the second network slice.

As a possible implementation manner, providing a service for the session according to the second network slice includes: selecting a user plane function network element for the session according to the second network slice; establishing a target access network device for the session and the session Connections between user plane functional network elements.

With the handover method provided by one of the above possible implementations, a user plane functional network element is selected for the session according to the second network slice, and the network slice associated with the session is mapped to the second network slice, so as to avoid the session in the handover process. The interruption of the carried services ensures the service continuity of the terminal equipment.

As a possible implementation manner, the method further includes: establishing a connection between the user plane function network element and the anchor user plane network element of the session for the session.

As a possible implementation manner, the providing a service for the session according to the second network slice further includes: acquiring a charging rule of the second network slice; and performing charging control on the session by using the charging rule.

The switching method provided by one of the above possible implementations ensures the accuracy of charging after session switching.

As a possible implementation manner, the method further includes: establishing the session for the terminal device, and the network slice associated with the session is the first network slice.

In a fifth aspect, an embodiment of the present application provides a communication device, including a processor, where the processor is configured to read and execute instructions from a memory, so as to implement the method in the first aspect or any possible implementation manner. Optionally, the communication device further includes the above-mentioned memory.

In a sixth aspect, an embodiment of the present application provides a communication device, which is characterized in that it includes a processor, and the processor is configured to read and execute instructions from a memory, so as to implement the second aspect or any possible implementation manner as described above. Methods. Optionally, the communication device further includes the above-mentioned memory.

In a seventh aspect, an embodiment of the present application provides a communication device, characterized in that it includes a processor, and the processor is configured to read and execute instructions from a memory, so as to implement the third aspect or any possible implementation manner as described above. Methods. Optionally, the communication device further includes the above-mentioned memory.

In an eighth aspect, an embodiment of the present application provides a communication device, which is characterized in that it includes a processor, and the processor is configured to read and execute instructions from a memory, so as to implement the fourth aspect or any possible implementation manner as described above. Methods. Optionally, the communication device further includes the above-mentioned memory.

In a ninth aspect, an embodiment of the present application provides a program product, characterized in that it includes an instruction, when the instruction is executed on a communication device, so that the communication device can implement the first aspect or any possible implementation manner as described above. , or the second aspect or any possible implementation, or the third aspect or any possible implementation, or the fourth aspect or any possible implementation.

In a tenth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores the program product provided in the ninth aspect.

In an eleventh aspect, a communication system is characterized by comprising one or more communication apparatuses according to the fifth aspect to the eighth aspect.

Through the solutions of the above aspects, when the target access network device does not support the first network slice associated with the session to be switched, the target access network device does not release the session, but maps the network slice of the session to the The second network slice supported by the target access network device and corresponding to the first network slice is used to prepare the session for handover, which avoids the interruption of the session during the handover process and ensures the service continuity of the terminal device during the handover process.

Description of drawings

In order to illustrate the technical solutions of the present application more clearly, the following briefly introduces the accompanying drawings used in the description of the embodiments.

Figure 1 is a schematic diagram of a 5G network architecture defined by 3GPP;

2 is a schematic diagram of a switching system provided by an embodiment of the present application;

3 is a schematic diagram of a handover method provided by an embodiment of the present application;

FIG. 4 is a schematic diagram of obtaining a network slice correspondence according to an embodiment of the present application;

FIG. 5 is a schematic flowchart of a handover method provided by an embodiment of the present application;

FIG. 6 is a schematic flowchart of a handover method provided by an embodiment of the present application;

FIG. 7 is a schematic flowchart of obtaining a network slice correspondence according to an embodiment of the present application;

FIG. 8 is a schematic diagram of a communication device provided by an embodiment of the present application;

FIG. 9 is a schematic diagram of another communication device provided by an embodiment of the present application;

FIG. 10 is a schematic diagram of an access network device provided by an embodiment of the present application.

Detailed ways

The embodiments of the present application will be described below with reference to the accompanying drawings in the present application.

As shown in FIG. 1 , it is a schematic structural diagram of a communication system provided by an embodiment of the present application. In this communication system, a terminal device accesses the core network through an access network (radio access network, RAN) device. The terminal equipment can establish a connection with a data network (DN) through the access network and the core network. The data network may include, for example, operator services, the Internet (Internet), or third-party services. In a 4G communication system, the connection may be a packet data network connection (PDN connection) or a bearer. In a 5G communication system, the connection may be a protocol data unit session (PDUSession). In a future communication system such as a sixth generation (6th generation, 6G) communication system, the connection may be a PDU session, a PDN connection, or other similar concepts, which are not limited in this embodiment of the present application. In this embodiment, the connection established between the terminal device and the data network is also called a session.

The communication system may support network slices. The connection established between the terminal device and the data network can be associated with a certain network slice. At this time, it is also called establishing a connection for the terminal device in the network slice, that is, the network resources associated with the network slice are used to provide services for the connection of the terminal device. . A network slice is a logical network that provides specific network capabilities and network characteristics. Network slicing is a concept in the 5G communication system. In the 4G communication system, network slicing corresponds to a dedicated core network (DCN). In the future 6G communication system, the network slice may have other names, which are not limited in this embodiment of the present application.

A terminal device is a device used to implement wireless communication functions, such as a terminal or a chip that can be used in a terminal, etc. It can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on water (such as ships, etc.); can also be deployed in the air (such as on airplanes, balloons, satellites, etc.). The terminal may be a user equipment (UE), an access terminal, a terminal unit, a terminal station, a mobile station, a mobile station in a 4G network, a 5G network, or a public land mobile network (PLMN) evolved in the future. station, remote station, remote terminal, mobile device, wireless communication device, terminal agent or terminal device, etc. The access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (SIP) telephone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a telephone with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices or wearable devices, virtual reality (VR) end devices, augmented reality (AR) end devices, industrial control (industrial) wireless terminal in control), wireless terminal in self driving, wireless terminal in remote medical, wireless terminal in smart grid, wireless terminal in transportation safety Terminals, wireless terminals in smart cities, wireless terminals in smart homes, and the like. Terminal equipment can be mobile or fixed.

An access network device is a device that provides wireless communication functions for terminal devices. Access network equipment, for example, includes but is not limited to: next generation access network (Next Generation RAN, NG-RAN), next generation base station (gnodeB, gNB), evolved node B (evolved node B, eNB), radio network controller (radio network controller, RNC), node B (node B, NB), base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved node B, or home node B, HNB), baseband unit (baseBand unit, BBU), transmission point (transmitting and receiving point, TRP), transmitting point (transmitting point, TP), mobile switching center, etc.

The core network includes mobility management network elements, session management network elements, and user plane network elements. Optionally, the core network further includes a user data management network element, a network slice selection network element or a policy control network element.

The mobility management network element is mainly used for mobility management in the mobile network, such as user location update, user registration network, user handover, etc. In a 4G communication system, the mobility management network element may be a mobility management entity (mobility management entity, MME). In a 5G communication system, the mobility management network element may be an access and mobility management function (access and mobility management function, AMF).

The session management network element is mainly used for session management in the mobile network, such as session establishment, modification and release. Specific functions include allocating an Internet Protocol (IP) address to a user, selecting a user plane network element that provides a packet forwarding function, and the like. In a 4G communication system, the session management network element may be a serving gateway control plane (SGW-C) or a packet data network gateway control plane (PGW-C), or an SGW-C and a PGW-C C co-located network element. In the 5G system, the session management network element may be a session management function (session management function, SMF).

The user plane network element is mainly used to forward user data packets according to the routing rules of the session management network element. In a 4G communication system, a user plane network element may be a serving gateway user plane (SGW-U) or a packet data network gateway user plane (PGW-U), or an SGW-U and a PGW -U co-located network element. In a 5G communication system, a user plane network element may be a user plane function (user plane function, UPF) network element.

The network slice selection network element is the network element used to select network slices for terminal devices. In a 5G communication system, the network slice selection network element may be a network slice selection function (NSSF).

The policy control network element includes user subscription data management function, policy control function, charging policy control function, quality of service (quality of service, QoS) control, and the like. In a 4G communication system, the policy control network element may be a policy control and charging function (policy control and charging function, PCRF). In a 5G communication system, the policy control network element may be a policy control function (PCF). It should be pointed out that the PCF in the actual network may also be divided into multiple entities according to layers or functions, such as the global PCF and the PCF within the slice, or the session management PCF (session management PCF, SM-PCF) and the access management PCF (access management PCF). , AM-PCF).

The unified data management network element is the network element responsible for managing the subscription information of the terminal equipment. In a 4G communication system, the unified data management network element may be a home subscriber server (home subscriber server, HSS). In the 5G communication system, the unified data management network element may be unified data management (unified data management, UDM).

In future communication systems such as 6G communication systems, the above network elements or equipment can still use their names in 4G or 5G communication systems, or have other names; the functions of the above network elements or equipment can be completed by an independent network element, It may also be performed jointly by several network elements, which is not limited in this embodiment of the present application.

In actual deployment, network elements in the core network can be co-located. For example, the mobility management network element can be co-located with the session management network element; the session management network element can be co-located with the user plane network element; the network slice selection function network element, the policy control network element, and the unified data management network element can be co-located. When two network elements are combined, the interaction between the two network elements provided in this embodiment of the present application becomes an internal operation of the combined network element or can be omitted.

FIG. 2 depicts a schematic diagram of a switching system provided by an embodiment of the present application. The switching system includes a first access network device, a second access network device and a core network. The terminal device is switched from the first access network device to the second access network device. The first access network device is also referred to as a source access network device. The second access network device is also referred to as a target access network device. The functions of each network element of the terminal device, the access network device, and the core network may refer to the description in FIG. 1 . Before the handover process occurs, the terminal device accesses the core network from the source access network device, and establishes a first session, and the network slice associated with the first session is the first network slice. When the terminal device is handed over from the source access network device to the target access network device, the target access network device will prepare for the handover for the first session. Since different access network devices may support different network slices, when the terminal device switches, it may switch to an access network device that does not support the first network slice. As shown in FIG. 2 , the source access network device supports the first network slice, and the target access network device does not support the first network slice. When the terminal device is switched from the source access network device to the target access network device, because the target access network device does not support the first network slice, it will release the first session associated with the first network slice, which may cause The service carried in the first session is interrupted.

Based on the schematic handover architecture shown in FIG. 2 , an embodiment of the present application provides a handover method. When the terminal device switches from the source access network device to the target access network device, if the target access network device does not support the first network slice associated with the session, the first network slice is mapped to the first network slice it supports. Two network slices, and based on the second network slice, the handover preparation of the session is completed. According to the above switching method, when the network slice of the session to be switched is a network slice not supported by the target access network device, the target access network device does not release the session, but maps the network slice of the session to the target access network device. The network slicing supported by the network access device is used to prepare the session for handover, which avoids the interruption of the services carried in the session during the handover process, and ensures the service continuity of the terminal device.

A handover method provided by an embodiment of the present application is introduced in detail below. As shown in Figure 3, the method includes:

S301: The target access network device acquires session information.

The session information indicates a session to be switched from the source access network device to the target access network device; wherein, the network slice associated with the session is the first network slice. Exemplarily, the session information includes a session identifier of the session.

As a possible implementation manner, the target access network device receives the session information from the network element of the first core network. In other words, the first core network element sends the session information to the target access network device. Exemplarily, when there is no interface between the source access network device and the target access network device, the target access network device receives the session information from the first core network element.

As another possible implementation manner, the target access network device receives the session information from the source access network device. In other words, the source access network device sends the session information to the target access network device. Exemplarily, when an interface exists between the source access network device and the target access network device, the target access network device receives the session information from the source access network device.

Optionally, the session information further includes a network slice identifier of the first network slice. Through the network slice identifier, the target access network device can learn that the network slice associated with the session is the first network slice. Optionally, the target access network device may obtain the network slice associated with the session from other devices, for example, obtain the network slice associated with the session from the unified data management network element or the mobility management network element according to the session identifier.

As an understanding, the session information enables the target access network device to switch the above-mentioned session to prepare.

S302: If the target access network device does not support the first network slice, the target access network device obtains a second network slice supported by the target access network device and corresponding to the first network slice.

Optionally, the target access network device acquires the second network slice according to the correspondence between the first network slice and the second network slice. Optionally, the network may configure the correspondence between the slices, including the correspondence between the first network slice and the second network. The target access network device may acquire the correspondence between the first network slice and the second network slice from the correspondence between the network slices. Optionally, one network slice may correspond to multiple network slices.

Optionally, as an example of a network slice, a default network slice can be set. When the target access network device does not support the first network slice, the default network slice may be used as the second network slice corresponding to the first network slice. Exemplarily, a default second network slice is configured on the target access network device. When the target access network device does not support the network slice associated with the session to be switched, the second network slice can be used to prepare the session for switching.

Optionally, when the first network slice corresponds to multiple second network slices, the target access network device may select a second network slice supported by the target access network device among the multiple second network slices. Optionally, the target access network device may select one second network slice from multiple second network slices according to the priority.

The target access network device may determine that it does not support the first network slice according to the configuration. Correspondingly, the target access network device may also determine according to the configuration that it supports the second network slice. For example, a list of supported network slices can be configured on an access network device. A network slice that does not belong to this list is a network slice that is not supported by the access network device, and a network slice in this list is the access network device. Supported network slices.

As a possible implementation manner, the correspondence between the first network slice and the second network slice may be configured on the target access network device.

As another possible implementation manner, the target access network device receives the correspondence between the first network slice and the second network slice from the source access network device or the first core network element; in other words, the source access network The device or the network element of the first core network sends the correspondence between the first network slice and the second network slice to the target access network device. The above-mentioned corresponding relationship may be configured on the source access network device or the first core network network element, or acquired from other network elements by the source access network device or the first core network network element.

Optionally, the second network slice satisfies the service level agreement of the first network slice, for example, the service requirement information corresponding to the second network slice satisfies the service level agreement of the first network slice; or, the second network slice corresponds to the first network slice same business.

S303: The target access network device performs handover preparation for the session according to the second network slice.

The target access network device performing handover preparation for the session according to the second network slice includes: the target access network device allocates resources, such as air interface resources, for the session according to the second network slice. In other words, the target access network device performs air interface resource configuration for the session according to the second network slice.

Exemplarily, the target access network device configures or reserves corresponding physical channel and/or logical channel resources according to the configuration for each network slice supported by the target access network device for use by a session associated with the network slice. When the target access network device allocates resources for the session according to the second network slice, the target access network device allocates resources for the session from the corresponding physical channel and/or logical channel resources configured or reserved for the second network slice .

Exemplarily, the target access network device configures a physical channel and/or a logical channel corresponding to the second network slice for the session.

Optionally, the target access network device sends first information to the terminal device, where the first information indicates resources allocated for the session, that is, the target access network device notifies the terminal device of the resources allocated for the session. In other words, the target access network device sends the air interface resource configuration parameters for the session to the terminal device. The terminal device will use the configuration parameter to switch the session to the target access network device.

Exemplarily, the target access network device sends the configuration parameter to the terminal device through the source access network device; or, the target access network device sends the configuration parameter to the terminal device through the first core network network element and the source access network device .

Optionally, the target access network device sends second information to the source access network device, where the second information indicates that the target access network device accepts the handover of the session.

Exemplarily, the target access network device directly sends the second information to the source access network device; or, the target access network device sends the second information to the source access network device through the first core network network element.

Optionally, the target access network device stores the third information in the context of the session. The third information indicates that the network slice associated with the session is mapped from the first network slice to the second network slice. Exemplarily, when accepting the session switch, the target access network device generates the network slice mapping information according to the correspondence between the first network slice and the second network slice. When the session is to be switched to another access network device, the other access network device may acquire the third information from the target access network device, and preferentially select the first network slice to allocate resources for the session according to the third information.

Through S303, the target access network device may prepare for handover for the session according to the second network slice, that is, accept the handover of the session from the source access network device to the target access network device.

Through the above S301-S303, in the process of switching the session associated with the first network slice of the terminal device from the source access network device to the target access network device, the target access network device is based on the The second network slice corresponding to the first network slice prepares the session of the terminal device for handover, which avoids interruption of services carried by the session because the target access network device does not support the first network slice, and ensures that the terminal device is switched over business continuity in the process.

Optionally, a switching method provided in the embodiment of the present application further includes:

S304: The target access network device sends network slice mapping information to the first core network element. Wherein, the network slice mapping information enables to provide services for the session according to the second network slice.

Exemplarily, the network slice mapping information includes a network slice identifier of the first network slice and a network slice identifier of the second network slice.

Correspondingly, the first core network element receives the network slice mapping information from the target access network device.

Exemplarily, serving the session according to the second network slice includes:

Select a user plane network element for the session according to the second network slice; or,

The session is charged according to the second network slice; or,

The core network control plane network elements, such as mobility management network elements, session management network elements, policy control network elements, etc., are reselected for the session according to the second network slice.

Optionally, the first core network element sends the network slice mapping information to the second core network element to enable the second core network element to provide the above-mentioned service for the session according to the second network slice. The first core network network element may be a mobility management network element, and the second core network network element may be a session management network element.

Through the above S304, the target access network device sends the network slice mapping information to the core network element, enabling to provide services for the session according to the second network slice, and to provide service guarantee for the terminal device after switching to the target access network device.

In practical use, the above method is also applicable to the handover of other types of connections of the terminal equipment, such as bearers, quality of service flows or connections in future communication systems.

In the method of FIG. 3 , the target access network device may acquire the correspondence between the first network slice and the second network slice from the source access network device or the first core network network element.

4 , a method for obtaining the correspondence between the first network slice and the second network slice from the first mobility management network element by the source access network device or the first core network network element is described by way of example.

As shown in Figure 4, the method includes:

S401: The first mobility management network element acquires the correspondence between the first network slice and the second network slice.

Optionally, the first mobility management network element may acquire the correspondence between the first network slice and the second network slice from the unified data management network element, the network slice selection function network element, and the policy control function network element. Alternatively, the correspondence between the first network slice and the second network slice may also be configured on the first mobility management network element.

Optionally, when the terminal device is in a roaming scenario, the first mobility management network element acquires the correspondence between the network slices of the home network from the above network element. Optionally, the first mobility management network element may further map the acquired correspondence between network slices of the home network to the correspondence between network slices of the visited network.

Exemplarily, the correspondence between the network slices of the home network acquired by the first mobility management network element is the correspondence between the third network slice and the fourth network slice. Both the third network slice and the fourth network slice are network slices of the home network. The third network slice is mapped to the first network slice in the visited network, and the fourth network slice is mapped to the second network slice in the visited network. According to the mapping relationship, the first mobility management network element maps the correspondence between the third network slice and the fourth network slice to the correspondence between the first network slice and the second network slice.

Exemplarily, the first mobility management network element may acquire the correspondence between network slices during the registration process of the terminal device.

S402: The first mobility management network element sends the first network element the correspondence between the first network slice and the second network slice.

Wherein, the corresponding relationship between the first network slice and the second network slice enables when the session associated with the first network slice is to be switched to the target access network device, when the target access network device does not support the first network slice, the target access network The access network device allocates resources for the session according to the second network slice supported by the target access network device.

The first network element may be a second mobility management network element, a source access network device or a target access network device.

Correspondingly, the first network element receives the correspondence between the first network slice and the second network slice from the first mobility management network element.

When the first network element is the source access network device, the source access network device receives the foregoing correspondence from the first mobility management network element. Exemplarily, the source access network device may receive the foregoing correspondence from the first mobility management network element in the process of registering the terminal device.

When the first network element is the target access network device, the target access network device receives the foregoing correspondence from the first mobility management network element. Exemplarily, the target access network device may receive the foregoing correspondence from the first mobility management network element in the process of switching the terminal device.

Optionally, after acquiring the above-mentioned corresponding relationship, the first mobility management network element sends the above-mentioned corresponding relationship to the target access network device according to the information that the target access network device supports the second network slice. The first mobility management network element may obtain information that the target access network device supports the first network slice according to the configuration or from the source access network device or from the target access network device.

When the first network element is the second mobility management network element, the second mobility management network element receives the foregoing correspondence from the first mobility management network element. Exemplarily, the second mobility management network element may receive the correspondence between the network slices from the first mobility management network element in the process of switching the terminal device.

Optionally, after acquiring the above-mentioned corresponding relationship, the first mobility management network element sends the above-mentioned corresponding relationship to the second mobility management network element according to the information that the target access network device supports the second network slice. The first mobility management network element may acquire information that the target access network device supports the first network slice according to the configuration or from the source access network device or from the second mobility management network element.

Through the above S401-S402, the first mobility management network element obtains the corresponding relationship between the first network slice and the second network slice, and optionally, the mobility management network element sends the target mobility management network element, the source access network device or the The target access network device sends the above corresponding relationship, so that in the process of switching the terminal device from the source access network device to the target access network device, if the target access network device does not support the first network slice associated with the session, the The session of the terminal device can be prepared for handover according to the second network slice, so as to avoid interruption of the service carried by the session during the handover process and ensure the service continuity of the terminal device during the handover process.

It should be noted that the first core network element in S301-S304 may be the first mobility management network element in S401-S402, or may be the second mobility management network element in S301-S304.

It should be noted that the source access network device or the first core network network element may also acquire the correspondence between the first network slice and the second network slice from other core network network elements. For example, the correspondence between the first network slice and the second network slice may be acquired from the session management network element.

It should be noted that the above-mentioned terminal device registration process is just an example, and the first mobility management network element and the source access network device may also be in other processes, such as the subscription data modification process of the terminal device, the configuration update process of the terminal device, or The corresponding relationship between the first network slice and the second network slice is acquired in the first session establishment process of the terminal device.

Based on the schematic handover architecture shown in FIG. 2 , an embodiment of the present application provides a handover method. The following terminal equipment takes UE as an example, the access network equipment takes NG-RAN as an example, the mobility management network element takes AMF as an example, the session management network element takes SMF as an example, and the connection between the terminal equipment and the data network takes the PDU session as an example. As an example, a handover method provided by an embodiment of the present application is introduced. Before the handover procedure, the UE is connected to the core network through the source NG-RAN. The UE has established the first PDU session associated with the first network slice. In this embodiment of the present application, there is an interface between the source NG-RAN and the target NG-RAN that can transmit messages in the handover process. As shown in Figure 5, the method includes:

S501: The source NG-RAN decides to handover the UE to the target NG-RAN.

Exemplarily, the source NG-RAN may decide to switch the UE to the target NG-RAN according to the UE's measurement report.

S502: The source NG-RAN sends a handover request (eg, Handover Request) message to the target NG-RAN. The handover request message requests the target NG-RAN to prepare for the handover of the UE to the target NG-RAN.

The handover request message includes session information of the first PDU session. The session information of the first PDU session enables the target NG-RAN to prepare resources for the first PDU session.

Exemplarily, the session information of the first PDU session includes a PDU session identifier of the first PDU session. Optionally, the session information of the first PDU session further includes the slice identifier S-NSSAI 1 of the first network slice.

Optionally, the handover request message further includes the correspondence between the first network slice and the second network slice. For example, the handover request message may include the slice identifier S-NSSAI 1 of the first network slice and the slice identifier S-NSSAI 2 of the second network slice, which are used to indicate the correspondence between the first network slice and the second network slice.

Optionally, the handover request message further includes an uplink N3 interface tunnel information parameter. The upstream N3 interface tunnel information parameter represents the endpoint identifier of the upstream tunnel between the RAN and the UPF of the first PDU session. The upstream tunnel endpoint is identified for transmission of upstream data packets of the first PDU session. Specifically, when the target NG-RAN sends the uplink data packet of the first PDU session, the uplink data packet needs to carry the identifier of the uplink tunnel endpoint.

As an implementation manner of S301, through S502, the target NG-RAN receives session information from the source NG-RAN. Through the session information, the target NG-RAN learns the session to be handed over, and the session is associated with the first network slice.

S503: The target NG-RAN determines that the first network slice is not supported.

The target NG-RAN may determine that the first network slice is not supported according to the configuration.

Exemplarily, the operator may configure a set of supported network slice identifiers on the target NG-RAN. The target NG-RAN determines that S-NSSAI 1 is not in the set of network slice identities supported by the configuration.

As an implementation of S302, through S503, the target NG-RAN determines that the first network slice is not supported.

S504: The target NG-RAN determines to support the second network slice.

After the target NG-RAN determines that the first network slice is not supported, it may further determine whether to support the second network slice corresponding to the first network slice received in S502.

Exemplarily, through S502, the target NG-RAN receives S-NSSAI 1 and S-NSSAI 2 from the handover request message, and the target NG-RAN confirms that the second network slice indicated by the S-NSSAI 2 is supported.

As a possible implementation manner, the target NG-RAN may determine whether to support the second network slice according to the configuration.

Exemplarily, the operator may configure a set of supported network slice identifiers on the target NG-RAN. The target NG-RAN determines that S-NSSAI 2 is in the set of network slice identities supported by the configuration.

As an implementation manner of S302, through S504, the target NG-RAN determines a supported second network slice corresponding to the first network slice.

S505: The target NG-RAN allocates resources for the first PDU session according to the second network slice.

As a possible implementation manner, the target NG-RAN performs L1/L2 configuration related to the second network slice for the first PDU session. The layer one configuration includes physical channel configuration, and the layer two configuration includes logical channel configuration.

Exemplarily, the target NG-RAN may configure or reserve physical channels and/or logical channels for each network slice it supports for use by sessions associated with that network slice. The physical channel and/or logical channel resources configured or reserved for each network slice are referred to as the radio resource pool associated with the network slice. When the target NG-RAN allocates resources for the first PDU session according to the second network slice, the target NG-RAN allocates resources for the first PDU session from the radio resource pool associated with the second network slice.

For example, the target NG-RAN performs layer 1 configuration for the first PDU session from the radio resource pool related to the second network slice, including the subcarrier interval, the cyclic prefix length of the subcarrier interval; optionally, also includes and system bandwidth Parameter configuration, transmission time interval (transmission time interval, TTI) length, etc.

For example, the target NG-RAN performs Layer 2 configuration on the first PDU session from the radio resource pool related to the second network slice, including configuring a data radio bearer (DRB) and a signaling radio bearer (SRB) . The DRB configuration includes allocating a resource instance associated with the terminal, adding a logical channel group and logical channel identifier to the instance, allocating radio link control (RLC) service parameters, and configuring DRB-related parameters to packet data aggregation Protocol (packet data convergence protocol, PDCP) and RLC examples. The SRB configuration includes allocating dedicated random access channel (RACH) resources, synchronization signals and physical broadcast channel (PBCH) blocks associated with the RACH resources.

The above-mentioned layer 1 and layer 2 configuration performed by the target NG-RAN for the first PDU session according to the second network slice also includes the configuration used by the UE to access the target NG-RAN.

Optionally, the target NG-RAN sets the network slice associated with the first PDU session as the second network slice.

Exemplarily, the target NG-RAN changes the network slice associated with the first PDU session from the first network slice to the second network slice. Alternatively, the target NG-RAN sets the network slice currently associated with the first PDU session as the second network slice.

Optionally, the target NG-RAN stores the network slice mapping information in the context of the first PDU session. The network slice mapping information indicates that the network slice of the first PDU session is mapped from the first network slice to the second network slice. Exemplarily, when accepting the handover of the first PDU session, the target NG-RAN generates the network slice mapping information according to the correspondence between the first network slice and the second network slice.

As an implementation manner of S303, through S505, the target NG-RAN allocates resources for the first PDU session according to the second network slice.

S506: The target NG-RAN sends a handover request acknowledgement (eg, Handover RequestAcknowledge) message to the source NG-RAN.

The handover request acknowledgement message confirms to the source NG-RAN that the first PDU session is accepted for handover to the target NG-RAN.

Exemplarily, the handover request acknowledgment message includes a PDU session acknowledgment list, and the PDU session acknowledgment list includes a PDU session identifier of the first PDU session, indicating that resources have been allocated for the handover of the first PDU session, and the first PDU session is accepted. switch.

Optionally, the handover request confirmation message further includes information about the UE accessing the target NG-RAN. The information of the UE accessing the target NG-RAN includes the configuration performed by the NG-RAN on the first PDU session in S505. The source NG-RAN will send the UE access information to the target NG-RAN.

As an implementation manner of S303, through S506, the target NG-RAN sends first information to the source NG-RAN, where the first information indicates that the target NG-RAN accepts the handover of the first PDU session. In addition, the target NG-RAN sends the resource allocated for the first PDU session to the terminal device through the source NG-RAN.

The foregoing S505 and S506 can be understood as the target access network device performing handover preparation according to the second network slice. In addition, the handover preparation may also include some other steps not listed as the technology evolves. In different switching scenarios, the operations to be completed for switching preparation may be different.

S507: The target NG-RAN allocates a downlink tunnel endpoint identifier for the first PDU session.

The downlink tunnel endpoint is identified for transmission of downlink data packets of the first PDU session. Specifically, when the core network sends the downlink data packet of the first PDU session to the target NG-RAN, the downlink data packet needs to carry the downlink tunnel endpoint identifier.

S508: The target NG-RAN sends the downlink tunnel endpoint identifier to the AMF.

Exemplarily, the target NG-RAN sends a path switch request (eg, Path Switch Request) message to the AMF. The path switch request message includes the PDU session identifier of the first PDU session and downlink N3 interface tunnel information. The downlink N3 interface tunnel information parameter represents the endpoint identifier of the downlink tunnel between the RAN and the UPF of the first PDU session. That is, the downlink N3 interface tunnel information parameter includes the downlink tunnel endpoint identifier allocated by the target NG-RAN in S507.

Optionally, the path switching request message further includes network slice mapping information. The network slice mapping information enables serving the first PDU session according to the second network slice.

Exemplarily, the path switch request message further includes a PDU session map slice parameter. The value of the PDU session map slice parameter is S-NSSAI 2. S-NSSAI 2 indicates that the network slice of the first PDU session is mapped to the second network slice.

Or, exemplarily, the path switch request message further includes a PDU session slice mapping indication and a network slice associated with the first PDU session. The PDU session slice mapping indication is used to indicate that the network slice associated with the first PDU session is mapped to the network slice indicated by the network slice parameter associated with the first PDU session during the handover process. Exemplarily, the value of the network slice parameter associated with the first PDU session is S-NSSAI 2.

As an implementation manner of S304, through S508, the target NG-RAN sends the network slice mapping information to the AMF. Wherein, the network slice mapping information enables to provide services for the first PDU session according to the second network slice.

In some switching scenarios, the switching preparation further includes S507 and S508.

S509: The AMF sends a session modification request message to the SMF. The session modification request message is used to request modification of the downlink tunnel endpoint identifier of the first PDU session.

The session modification request message includes the downlink tunnel endpoint identifier received in S508.

Exemplarily, the session modification request message includes a downlink N3 interface tunnel information parameter, and the downlink N3 interface tunnel information parameter includes the downlink tunnel endpoint identifier received in S508.

Optionally, the session modification request message further includes the network slice mapping information received in S508.

Exemplarily, the session modification request message further includes a PDU session map slice parameter. The value of the PDU session map slice parameter is S-NSSAI 2. Alternatively, the session modification request message further includes a PDU session slice map indicating a network slice associated with the first PDU session. The PDU session slice mapping indication is used to indicate that the network slice associated with the first PDU session is mapped to the network slice indicated by the network slice parameter associated with the first PDU session during the handover process.

Optionally, the AMF provides services for the first PDU session according to the second network slice.

As a possible implementation manner for the AMF to provide services for the first PDU session according to the second network slice, the AMF changes the network slice associated with the first PDU session to the second network slice. Exemplarily, the AMF changes the network slice identifier in the context of the first PDU session to S-NSSAI 2.

As another possible implementation manner for the AMF to provide the service for the first PDU session according to the second network slice, the AMF stores the information of mapping the first PDU session to the second network slice. Exemplarily, the AMF stores the information that the first PDU session is mapped to the S-NSSAI 2 in the context of the first PDU session.

In the above two possible implementation manners, optionally, the AMF performs AMF reselection according to the second network slice. That is, the AMF selects the target AMF to serve the first PDU session according to the second network slice. The AMF will trigger the AMF reselection process, including: sending the context of the UE to the target AMF, enabling the target AMF to establish an N2 connection with the target NG-RAN and a connection with the SMF.

In the above two possible implementation manners, optionally, the AMF performs SMF reselection or intermediate SMF selection according to the second network slice. That is, the AMF selects the target SMF to serve the first PDU session according to the second network slice, or selects the target intermediate SMF to serve the first PDU session. The AMF will trigger the SMF reselection or intermediate SMF selection procedure, including sending a message to the target SMF or the target intermediate SMF to create the UE's session management context, and thereby possibly trigger the target SMF or the target intermediate SMF to acquire the SMF of the first PDU session UE's session management context, UPF or intermediate UPF reselection process.

Exemplarily, the session modification request message may be PDU Session Update Request or Nsmf_PDUSession_UpdateSMContext Request.

S510: The SMF provides services for the first PDU session according to the second network slice.

As a possible implementation manner for the SMF to provide services for the first PDU session according to the second network slice, the SMF changes the network slice associated with the first PDU session to the second network slice. Exemplarily, the SMF changes the network slice identifier in the context of the first PDU session to S-NSSAI 2.

As another possible implementation manner for the SMF to provide the service for the first PDU session according to the second network slice, the SMF stores the information of mapping the first PDU session to the second network slice. Exemplarily, the SMF stores the information that the first PDU session is mapped to the S-NSSAI 2 in the context of the first PDU session.

Optionally, the SMF selects the UPF for the first PDU session according to the second network slice. The SMF establishes the connection between the target NG-RAN and the UPF for the first PDU session. The UPF may act as an intermediate UPF or an anchor UPF for the first PDU session. When the UPF acts as an intermediate UPF of the first PDU session, the SMF further establishes a connection between the UPF and the anchor point UPF of the first PDU session for the first PDU session.

Exemplarily, the SMF selects the UPF according to S-NSSAI 2. The SMF sends the first core network tunnel information parameter to the UPF. The first core network tunnel information parameter includes the downlink tunnel endpoint identifier received in S509. The SMF sends the second core network tunnel information parameter to the target NG-RAN. The second core network tunnel information parameter includes the identifier of the uplink tunnel endpoint of the UPF. The SMF may send the second core network tunnel information parameter to the target NG-RAN through the AMF. Optionally, further, the SMF sends the third core network tunnel information parameter to the anchor UPF. The third core network tunnel information parameter includes the downlink tunnel endpoint identifier of the UPF. The downlink tunnel endpoint identifier of the UPF indicates the downlink tunnel endpoint identifier of the channel between the UPF and the anchor UPF for the first PDU session. Optionally, the SMF also sends the fourth core network tunnel information parameter to the UPF. The fourth core network tunnel information parameter includes the uplink tunnel endpoint identifier of the anchor point UPF. The uplink tunnel endpoint identifier of the anchor UPF indicates the uplink tunnel endpoint identifier of the channel between the UPF and the anchor UPF for the first PDU session.

Optionally, the SMF acquires the charging rule of the second network slice, and uses the charging rule to perform charging for the first PDU session.

Exemplarily, the SMF acquires the charging rule of the second network slice according to S-NSSAI 2, and uses the charging rule to perform charging for the first PDU session.

Optionally, the SMF receives the charging rule of the second network slice from the PCF, and uses the charging rule to charge the first PDU session.

Exemplarily, the SMF sends a Policy Control Update Request (eg, Policy Control UpdateRequest) message to the PCF. The policy control update request message includes the policy association identifier and S-NSSAI 2 . The policy association identifier is an identifier of the policy association corresponding to the first PDU session. The SMF receives a Policy Control Update Response (eg PolicyControl Update Response) message from the PCF. The policy control update response message includes PCC rules. The PCC rule includes the updated QoS policy and charging rule of the first PDU session.

The SMF charges the first PDU session according to the updated charging rule for the first PDU session.

Optionally, the SMF triggers a PDU session modification process according to the updated QoS policy of the first PDU session, and modifies the QoS parameters of the first PDU session.

As an implementation manner of S304, through S509-S510, the AMF and the SMF provide services for the first PDU session according to the second network slice.

In the above method, in the process of switching the session of the terminal device from the source access network device to the target access network device, if the target access network device does not support the first network slice associated with the session, the target access network device Allocate resources for the session of the terminal device according to the second network slice it supports, so as to avoid the interruption of the service carried by the session during the handover process, and ensure the service continuity of the terminal device during the handover process.

In practical use, the above method is also applicable to the handover of other types of connections of the terminal equipment, such as bearers, quality of service flows or connections in future communication systems.

Based on the schematic handover architecture shown in FIG. 2 , an embodiment of the present application provides a handover method. The following terminal equipment takes UE as an example, the access network equipment takes NG-RAN as an example, the mobility management network element takes AMF as an example, the session management network element takes SMF as an example, and the connection between the terminal equipment and the data network takes PDU session as an example. As an example, a handover method provided by an embodiment of the present application is introduced. Before the handover procedure, the UE is connected to the core network through the source RAN. The UE has established the first PDU session associated with the first network slice. In this embodiment of the present application, the source NG-RAN and the target NG-RAN communicate messages in the handover process through AMF. As shown in Figure 6, the method includes:

S601: The source NG-RAN decides to handover the UE to the target NG-RAN.

S601 may refer to the description of S501.

S602: The source NG-RAN sends a handover required (eg, Handover Required) message to the AMF. The handover request message is used to request the target NG-RAN to prepare for the handover of the UE to the target NG-RAN through the AMF.

The handover request message includes session information of the first PDU session. The session information of the first PDU session is used to request the target NG-RAN to prepare resources for the first PDU session through the AMF.

Exemplarily, the session information of the first PDU session includes a PDU session identifier of the first PDU session. Optionally, the session information of the first PDU session further includes S-NSSAI 1.

Optionally, the handover request message further includes the message also includes the correspondence between the first network slice and the second network slice.

Exemplarily, the handover request message further includes a slice identifier S-NSSAI 1 of the first network slice and a slice identifier S-NSSAI 2 of the second network slice, which are used to indicate the correspondence between the first network slice and the second network slice.

S603: The AMF sends a handover request (eg, Handover Request) message to the target NG-RAN. The handover request message requests the target NG-RAN to prepare resources for the handover of the UE.

The handover request message includes session information of the first PDU session. The session information of the first PDU session enables the target NG-RAN to prepare resources for the first PDU session.

Exemplarily, the session information of the first PDU session includes a PDU session identifier of the first PDU session and a slice identifier S-NSSAI 1 of the first network slice.

Optionally, the handover request message further includes the correspondence between the first network slice and the second network slice.

Exemplarily, the handover request message further includes a slice identifier S-NSSAI 1 of the first network slice and a slice identifier S-NSSAI 2 of the second network slice, which are used to indicate the correspondence between the first network slice and the second network slice.

Exemplarily, the handover request message includes a PDU session resource establishment parameter, and the PDU session resource establishment parameter includes a PDU session identifier PDU session identifier and S-NSSAI 1 of the first PDU session. The PDU session resource establishment parameters also include S-NSSAI 2.

Or, exemplarily, the handover request message includes an allowed network slice selection assistance information (eg, Allowed NSSAI) parameter. The allowed network slice selection auxiliary information parameters include S-NSSAI 1 and S-NSSAI2. Wherein S-NSSAI 2 indicates a second network slice associated with the first network slice identified by S-NSSAI 1.

Optionally, the handover request message further includes an uplink N3 interface tunnel information parameter. The upstream N3 interface tunnel information parameter represents the endpoint identifier of the upstream tunnel between the RAN and the UPF of the first PDU session. For the endpoint identifier of the uplink tunnel, reference may be made to the description of S502.

As an implementation manner of S301, through S603, the target NG-RAN receives session information from the AMF. Through the session information, the target NG-RAN learns the session to be handed over, and the session is associated with the first network slice.

S604: The target NG-RAN determines that the first network slice is not supported.

S604 may refer to the description of S503.

As an implementation of S302, through S604, the target NG-RAN determines that the first network slice is not supported.

S605: The target NG-RAN determines to support the second network slice.

S605 can refer to the description of S504.

As an implementation manner of S302, through S605, the target NG-RAN determines a supported second network slice corresponding to the first network slice.

S606: The target NG-RAN allocates resources for the first PDU session according to the second network slice.

S606 may refer to the description of S505.

As an implementation manner of S303, through S606, the target NG-RAN allocates resources for the first PDU session according to the second network slice.

S607: The target NG-RAN allocates a downlink tunnel endpoint identifier for the first PDU session.

S607 can refer to the description of S507.

S608: The target NG-RAN sends a handover request acknowledgement (eg, Handover RequestAcknowledge) message to the AMF. The handover request confirmation message is used to confirm to the AMF that the first PDU session is accepted for handover to the target NG-RAN.

Optionally, the handover request confirmation message includes a PDU session identifier of the first PDU session and downlink N3 interface tunnel information.

The PDU session identifier of the first PDU session indicates that resources have been allocated for the handover of the first PDU session, and the handover of the first PDU session is accepted. The downlink N3 interface tunnel information parameter represents the endpoint identifier of the downlink tunnel between the RAN and the UPF of the first PDU session. That is, the downlink N3 interface tunnel information parameter includes the downlink tunnel endpoint identifier allocated by the target NG-RAN in S607.

Optionally, the handover request confirmation message further includes network slice mapping information. The network slice mapping information indicates that the network slice of the first PDU session is mapped from the first network slice to the second network slice. The network slice mapping information enables the core network element to serve the session according to the second network slice.

Exemplarily, the handover request confirmation message further includes S-NSSAI 2 . The S-NSSAI 2 enables serving the first PDU session according to the second network slice.

Optionally, the handover request confirmation message further includes information about the UE accessing the target NG-RAN. For the information used by the UE to access the target NG-RAN, refer to the description in S506.

The AMF will send the PDU session identifier of the first PDU session and the information that the UE accesses the target NG-RAN to the source NG-RAN. After receiving the information that the UE accesses the target NG-RAN, the source NG-RAN will send the information to the UE.

Exemplarily, the AMF sends a handover command (eg, Handover Command) message to the source NG-RAN, where the handover command message includes the PDU session identifier of the first PDU session and the information that the UE accesses the target NG-RAN.

As an implementation of S303, through S608, the target NG-RAN sends the PDU session identifier of the first PDU session to the source NG-RAN through the AMF, and indicates to the source NG-RAN that the target NG-RAN accepts the handover of the first PDU session. The target NG-RAN sends the resource allocated for the first PDU session to the terminal device through the AMF and the source NG-RAN.

As an implementation manner of S304, through S608, the target NG-RAN sends the network slice mapping information to the AMF.

The foregoing S606 and S607 can be understood as the target access network device performing handover preparation according to the second network slice. In addition, the handover preparation may also include some other steps not listed as the technology evolves. In different switching scenarios, the operations to be completed for switching preparation may be different. In some switching scenarios, the switching preparation does not include S607.

S609: The AMF sends a session modification request message to the SMF. The session modification request message is used to request modification of the downlink tunnel endpoint identifier of the first PDU session.

S609 may refer to the description of S509.

S610: The SMF provides services for the first PDU session according to the second network slice.

S610 may refer to the description of S510.

As an implementation manner of S304, through S609-S610, the AMF and the SMF provide services for the first PDU session according to the second network slice.

Optionally, the above method further includes:

S611: The AMF sends the allowed network slice selection assistance information to the UE. Wherein, the allowed network slice selection auxiliary information includes the network slice identifier S-NSSAI 1 of the first network slice.

Exemplarily, the UE initiates a mobility registration procedure. In this mobility registration procedure, the AMF sends the allowed network slice selection assistance information to the UE. Wherein, the allowed network slice selection auxiliary information includes the network slice identifier S-NSSAI 1 of the first network slice.

Through S611, the AMF sends the allowed network slice selection assistance information including the network slice identifier of the first network slice to the UE, so the UE does not perceive that the network slice associated with the first PDU session has been mapped to the second network slice. Therefore, the network maps the network slice associated with the first PDU session from the unsupported first network slice to the supported second network slice without the UE being aware of it, so as to avoid the interruption of the session during the handover process and ensure the terminal equipment Service continuity in the handover process avoids the impact on the UE.

Through the above method, in the process of switching the terminal device from the source access network device to the target access network device, if the target access network device does not support the first network slice associated with the session, the target access network device will The second network slice allocates resources for the session of the terminal device, which avoids interruption of services carried by the session during the handover process, and ensures the service continuity of the terminal device during the handover process.

It should be noted that during the handover process, the AMF may change, that is, the source AMF serves the source NG-RAN, and the target AMF serves the target NG-RAN. At this time, in S602, the source NG-RAN sends a handover request message to the source AMF. The source AMF sends the correspondence between the first network slice and the second network slice to the target AMF. The source AMF triggers the target AMF to send a handover request message to the target NG-RAN.

Exemplarily, the source AMF sends a UE context establishment request message to the target AMF. The UE context establishment request message instructs the target AMF to establish a context for the UE. The UE context establishment request message includes the correspondence between the first network slice and the second network slice. The UE context establishment request message triggers the target AMF to send the handover request message to the target NG-RAN.

Exemplarily, the UE context establishment request message includes allowed network slice selection auxiliary information, and the allowed network slice selection auxiliary information includes S-NSSAI 1 and S-NSSAI 2, which are used to indicate the first network slice and the second network slice. Correspondence of slices.

Or, in an example, the UE context establishment request message includes the context of the first PDU session. The context of the first PDU session includes S-NSSAI 1 and S-NSSAI 2, which are used to indicate the correspondence between the first network slice and the second network slice.

Correspondingly, in S603, the target AMF sends a handover request message to the target NG-RAN. For the handover request message, reference may be made to the description of the handover request message in S603.

Correspondingly, in S608, the target NG-RAN sends a handover request confirmation message to the target AMF. The target AMF triggers the source AMF to send a handover command message to the source NG-RAN.

Exemplarily, the target AMF sends a UE context establishment response message to the source AMF. The UE Context Setup Response message confirms to the source AMF that the context is established for the UE. The UE context establishment response message includes the PDU session identifier of the first PDU session and the information that the UE accesses the target NG-RAN. The UE context establishment response message triggers the source AMF to send a handover command message to the source NG-RAN. For the handover command message, reference may be made to the description of the handover command message in S608.

Correspondingly, in S611, the target AMF sends the allowed network slice selection assistance information to the UE. Wherein, the permitted network slice selection auxiliary information includes the network slice identifier of the first network slice.

In practical use, the above method is also applicable to the handover of other types of connections of the terminal equipment, such as bearers, quality of service flows or connections in future communication systems.

In the above S502, the source NG-RAN sends the correspondence between the first network slice and the second network slice to the target NG-RAN. In the above S602, the source NG-RAN sends the correspondence between the first network slice and the second network slice to the AMF.

In the above S603, the AMF sends the correspondence between the first network slice and the second network slice to the target NG-RAN.

As a possible implementation manner, a method for acquiring the correspondence between the first network slice and the second network slice by the source NG-RAN and the AMF is described below by taking the registration process of the UE as an example. As shown in Figure 7, the method includes:

S701: The UE sends a registration request message to the AMF through the source NG-RAN.

S702: The AMF acquires the correspondence between the first network slice and the second network slice.

The AMF acquires the correspondence between the first network slice and the second network slice in the following four ways, refer to the description of S703-S706. In actual use, the AMF may simultaneously use one or more of S703-S706 to obtain the correspondence between the first network slice and the second network slice.

S703: The AMF obtains the correspondence between the first network slice and the second network slice from the UDM.

Exemplarily, the AMF acquires subscription information of the UE from the UDM, where the subscription information includes a correspondence between the first network slice and the second network slice.

S704: The AMF acquires the correspondence between the first network slice and the second network slice from the NSSF.

Optionally, as a possible implementation manner for the NSSF to obtain the correspondence between the first network slice and the second network slice, the NSSF obtains the correspondence between the first network slice and the second network slice according to the configuration.

Optionally, as another possible implementation manner for the NSSF to obtain the correspondence between the first network slice and the second network slice, the NSSF determines the correspondence between the first network slice and the second network slice according to the service level agreement with the network slice. .

Exemplarily, the NSSF determines, according to the service level agreement of the first network slice and the service requirement information of each slice, that the data network that meets the service level agreement requirements of the first network slice and that the related data network is the same as the data network related to the first network slice the second network slice.

Exemplarily, the service requirement information includes delay, data transmission bandwidth, reliability, bit error rate, maximum packet length, or maximum moving speed.

Optionally, the service level agreement may include information on whether the user accepts the change of the service requirement information of the network slice. For example, whether it is acceptable to reduce or increase the guaranteed bandwidth or reliability of data transmission, and the proportion of reduction or increase; whether to allow the reduction or increase of service rates, and the proportion of reduction or increase; whether to allow changes in service isolation, etc.

Exemplarily, the data networks related to the first network slice are data network 1 and data network 2, which can provide a data transmission bandwidth of 10M/S. The data networks related to the second network slice are data network 1 and data network 2, which can provide a data transmission bandwidth of 8M/S. The service level agreement of the first network slice indicates that the data transmission bandwidth is allowed to be reduced, and the reduction ratio is within 25%. Then the NSSF determines that the second network slice is a network slice that satisfies the service level agreement requirement of the first network slice, and the related data network is the same as the data network related to the first network slice. That is, the NSSF determines that the second network slice is a network slice associated with the first network slice.

The NSSF sends the correspondence between the first network slice and the second network slice to the AMF. Correspondingly, the AMF acquires the correspondence between the first network slice and the second network slice from the NSSF.

S705: The AMF acquires the correspondence between the first network slice and the second network slice from the PCF.

Optionally, the PCF selects the correspondence between the first network slice and the second network slice according to the UE routing policy.

Exemplarily, the routing policy of the UE includes service description information and corresponding routing description information. The routing description information includes the network slice identifier. If the two routing policies of the UE include the same service description information, the PCF determines that the network slices indicated by the network slice identifiers in the two routing policies have a corresponding relationship.

Exemplarily, the routing strategy 1 of the UE includes: applying the network slice corresponding to A as the first network slice; and the routing strategy 2 of the UE includes: applying the network slice corresponding to A as the second network slice. Then the PCF determines that the first network slice and the second network slice have a corresponding relationship.

The PCF sends the correspondence between the first network slice and the second network slice to the AMF. Correspondingly, the AMF receives the correspondence between the first network slice and the second network slice from the PCF.

Optionally, when the UE is currently in a visited network, that is, when the communication network to which the AMF belongs is different from the home network of the UE, through S703-S705, the AMF obtains the correspondence between the network slices of the UE's home network. The AMF determines the corresponding relationship of network slices in the visited network according to the network slice mapping relationship between the home network and the visited network.

Exemplarily, when the UE is currently in the visited network, through S703-S705, the AMF obtains the correspondence between the third network slice and the fourth network slice of the UE's home network. The third network slice is mapped to the first network slice in the visited network, and the fourth network slice is mapped to the second network slice in the visited network. According to the mapping relationship, the AMF maps the correspondence between the third network slice and the fourth network slice to the correspondence between the first network slice and the second network slice.

Optionally, when the UE is currently in the visited network, the AMF stores the correspondence between the first network slice and the second network slice of the visited network.

S706: The AMF acquires the correspondence between the first network slice and the second network slice according to the local configuration.

As an implementation manner of S401, through S702 (including one or more of the four manners S703-S706), the AMF acquires the correspondence between the first network slice and the second network slice.

S707: The AMF sends the correspondence between the first network slice and the second network slice to the source NG-RAN.

Exemplarily, the AMF sends an Initial Context Setup Request (eg, Initial ContextSetup Request) message to the source NG-RAN. Wherein, the initial context establishment request message includes the correspondence between the first network slice and the second network slice.

Exemplarily, the corresponding relationship between the first network slice and the second network slice may be described by a network slice associated parameter. The network slice association parameter includes a network slice identifier S-NSSAI 1 of the first network slice and a network slice identifier S-NSSAI 2 of the second network slice.

Or, exemplarily, the corresponding relationship between the first network slice and the second network slice may be described by an allowed network slice selection auxiliary information parameter. The allowed network slice selection auxiliary information parameters include a network slice identifier S-NSSAI 1 of the first network slice and a network slice identifier S-NSSAI 2 of the second network slice.

As an implementation manner of S402, in S707, the AMF sends the correspondence between the first network slice and the second network slice to the source NG-RAN.

It should be noted that when the AMF changes during the handover process, that is, the source AMF serves the source NG-RAN and the target AMF serves the target NG-RAN, the AMF in S701-S707 is the same as the source AMF in S601-S610. same.

Through the above S701-S707, the AMF obtains the correspondence between the first network slice and the second network slice. Optionally, the AMF sends the correspondence between the first network slice and the second network slice to the source NG-RAN to enable the UE to During the handover process from the source NG-RAN to the target NG-RAN, if the target NG-RAN does not support the first network slice associated with the session, the UE's session can be prepared for handover according to the second network slice, thereby avoiding handover The interruption of the session during the process ensures the service continuity of the UE during the handover process.

It should be noted that the above UE registration process is just an example, and the AMF may also obtain the correspondence between the first network slice and the second network slice in other processes.

Exemplarily, in the process of establishing the first PDU session of the UE, the SMF obtains the corresponding relationship between the first network slice and the second network slice, and sends the information of the first network slice and the second network slice to the AMF and the source NG-RAN. Correspondence.

FIG. 8 is a schematic block diagram of a communication apparatus 800 according to an embodiment of the present application.

The communication device includes a processing module 801 and a transceiver module 802 . The processing module 801 is used to realize the processing of data by the communication device. The transceiver module 802 is used to implement content interaction between the communication device and other units or network elements. It should be understood that the processing module 801 in this embodiment of the present application may be implemented by a processor or a processor-related circuit component (or referred to as a processing circuit), and the transceiver module 802 may be implemented by a transceiver or a transceiver-related circuit component.

Exemplarily, the communication apparatus 800 may be a communication apparatus, or may be a chip applied in the communication apparatus or other combined devices, components, etc. having the functions of the foregoing communication apparatus.

Exemplarily, the communication apparatus 800 may be the target access network device in FIG. 3 , or the target NG-RAN in FIG. 5 and FIG. 6 .

The processing module 801 may be configured to perform data processing operations performed by the target access network device in FIG. 3 or the target NG-RAN in FIG. 5 and FIG. 6 . For example, S301, S302, S303, S503, S504, S505, S507, S604, S605, S606, S607, and/or other processes for supporting the techniques described herein.

The transceiving module 802 may be configured to perform the transceiving operation performed by the target access network device in FIG. 3 or the target NG-RAN in FIG. 5 and FIG. 6 . For example, S304, S502, S506, S508, S603, S608, and/or other processes for supporting the techniques described herein.

Exemplarily, the communication apparatus 800 may be the first network element in FIG. 4 , or the source NG-RAN in FIG. 5 , FIG. 6 and FIG. 7 .

The processing module 801 may be configured to perform the first network element in FIG. 4 or the data processing operations performed by the source NG-RAN in FIG. 5 , FIG. 6 and FIG. 7 . For example, S501, S601, and/or other processes for supporting the techniques described herein.

The transceiving module 802 may be configured to perform the transceiving operation performed by the first network element in FIG. 4 or the source NG-RAN in FIG. 5 , FIG. 6 and FIG. 7 . For example, S402, S502, S506, S602, S707, and/or other processes for supporting the techniques described herein.

Exemplarily, the communication apparatus 800 may be the core network element in FIG. 3 , the mobility management network element in FIG. 4 , or the AMF in FIG. 5 , FIG. 6 and FIG. 7 .

The processing module 801 may be configured to perform data processing operations performed by the core network element in FIG. 3 , the mobility management network element in FIG. 4 , or the AMF in FIGS. 5 , 6 and 7 . For example, S401, S702, S703, S704, S705, S706, and/or other processes for supporting the techniques described herein.

The transceiving module 802 may be configured to perform transceiving operations performed by the core network element in FIG. 3 , the mobility management network element in FIG. 4 , or the AMF in FIGS. 5 , 6 and 7 . For example, the transceiving operations in S304, S402, S508, S509, S608, S609, S602, S611, S701, S707, and S703, S704, S705, and/or other processes for supporting the techniques described herein.

Exemplarily, the communication apparatus 800 may be the core network element in FIG. 3 , or the SMF in FIG. 5 and FIG. 6 .

The processing module 801 may be configured to perform the core network element in FIG. 3 or the data processing operations performed by the SMF in FIG. 5 and FIG. 6 . For example, S510, S610, and/or other processes for supporting the techniques described herein.

The transceiving module 802 may be configured to perform the transceiving operation performed by the core network element in FIG. 3 or the SMF in FIG. 5 and FIG. 6 . For example, the transceiving operations in S304, S509, S609, and/or other processes for supporting the techniques described herein.

An embodiment of the present application further provides a communication apparatus, as shown in FIG. 9 , including: a processor 901 , a communication interface 902 , and a memory 903 . The processor 901, the communication interface 902 and the memory 903 can be connected to each other through a bus 904; the bus 904 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus etc. The above-mentioned bus 904 can be divided into an address bus, a data bus, a control bus, and the like. For ease of presentation, only one thick line is used in FIG. 9, but it does not mean that there is only one bus or one type of bus. The processor 901 may be a central processing unit (CPU), a network processor (NP), or a combination of CPU and NP. The processor may further include a hardware chip. The above-mentioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (Generic Array Logic, GAL) or any combination thereof. Memory 903 may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory may be random access memory (RAM), which acts as an external cache.

The communication device shown in FIG. 9 may be the core network element in FIG. 3 , the mobility management network element in FIG. 4 , or the AMF in FIG. 5 , FIG. 6 and FIG. 7 , to complete corresponding functions.

Exemplarily, the processor 901 is configured to implement data processing operations of the communication device. For example, S401, S702, S703, S704, S705, S706, and/or other processes for supporting the techniques described herein.

Exemplarily, the communication interface 902 is used to implement the transceiving operation of the communication device. For example, the transceiving operations in S304, S402, S508, S509, S608, S609, S602, S611, S701, S707, and S703, S704, S705, and/or other processes for supporting the techniques described herein.

The communication apparatus shown in FIG. 9 may be the core network element in FIG. 3 or the SMF in FIG. 5 and FIG. 6 , to complete the corresponding functions.

Exemplarily, the processor 901 is configured to implement data processing operations of the communication device. For example, S510, S610, and/or other processes for supporting the techniques described herein.

Exemplarily, the communication interface 902 is used to implement the transceiving operation of the communication device. For example, the transceiving operations in S304, S509, S609, and/or other processes for supporting the techniques described herein.

The embodiment of the present application further provides an access network device, as shown in FIG. 10 . The device 1000 includes one or more radio frequency units, such as a remote radio unit (RRU) 1010 and one or more baseband units (BBU) (also referred to as digital units, digital units, DU) 1020 . The RRU 1010 may be referred to as a transceiver module, and the transceiver module may include a sending module and a receiving module, or the transceiver module may be a module capable of transmitting and receiving functions. The transceiver module may correspond to the transceiver module 802 in FIG. 8 . Optionally, the transceiver module may also be referred to as a transceiver, a transceiver circuit, or a transceiver, etc., which may include at least one antenna 1011 and a radio frequency unit 1012 . The part of the RRU 1010 is mainly used for transmitting and receiving radio frequency signals and converting radio frequency signals and baseband signals, for example, for sending indication information to terminal equipment. The part of the BBU1020 is mainly used to perform baseband processing, control the base station, and so on. The RRU 1010 and the BBU 1020 may be physically set together or physically separated, that is, a distributed base station.

The BBU 1020 is the control center of the base station, and can also be called a processing module, which can correspond to the processing module 801 in FIG. For example, the BBU (processing module) may be used to control the base station to perform the operation procedure of the network device in the foregoing method embodiments, for example, to generate the foregoing indication information and the like.

In an example, the BBU 1020 may be composed of one or more boards, and the multiple boards may jointly support a wireless access network (such as an LTE network) of a single access standard, or may respectively support a wireless access network of different access standards. Radio access network (such as LTE network, 5G network or other network). The BBU 1020 also includes a memory 1021 and a processor 1022. The memory 1021 is used to store necessary instructions and data. The processor 1022 is configured to control the base station to perform necessary actions, for example, to control the base station to perform the operation flow of the network device in the foregoing method embodiments. The memory 1021 and the processor 1022 may serve one or more single boards. That is to say, the memory and processor can be provided separately on each single board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits may also be provided on each single board.

An embodiment of the present application provides a communication system, which includes the foregoing target access network device and source access network device, or one or more of the target NG-RAN and the source NG-RAN.

Embodiments of the present application further provide a communication system, which includes the aforementioned target access network device, source access network device, and mobility management network element, or one of the target NG-RAN, the source NG-RAN, and the AMF, or multiple.

An embodiment of the present application further provides a communication system, which includes the aforementioned target access network device, source access network device, mobility management network element and session management network element, or the target NG-RAN, the source NG-RAN, One or more of AMF and SMF.

Embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium. When the computer program is executed by a computer, the computer can implement the method shown in FIG. 3 provided by the foregoing method embodiments. The process related to the target access network device in the embodiment, or the process related to the target NG-RAN in the embodiment shown in FIG. 5 and FIG. 6 .

Embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium. When the computer program is executed by a computer, the computer can implement the method shown in FIG. 4 provided by the foregoing method embodiments. The process related to the first network element in the embodiment, or the process related to the source NG-RAN in the embodiments shown in FIG. 5 , FIG. 6 and FIG. 7 .

Embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium. When the computer program is executed by a computer, the computer can implement the method shown in FIG. 3 provided by the foregoing method embodiment. The process related to the core network element in the embodiment, or the process related to the mobility management network element in the embodiment shown in FIG. 4, or the process related to the AMF in the embodiment shown in FIG. 5, FIG. process.

Embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium. When the computer program is executed by a computer, the computer can implement the method shown in FIG. 3 provided by the foregoing method embodiment. Processes related to core network elements in the embodiment, or processes related to SMF in the embodiments shown in FIG. 5 and FIG. 6 .

An embodiment of the present application further provides a computer program product, where the computer program product is used to store a computer program, and when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 3 provided by the above method embodiment. The process related to the target access network device, or the process related to the target NG-RAN in the embodiments shown in FIG. 5 and FIG. 6 .

An embodiment of the present application further provides a computer program product, where the computer program product is used to store a computer program, and when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 4 provided by the above method embodiment. The process related to the first network element, or the process related to the source NG-RAN in the embodiments shown in FIG. 5 , FIG. 6 and FIG. 7 .

An embodiment of the present application further provides a computer program product, where the computer program product is used to store a computer program, and when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 3 provided by the above method embodiment. Processes related to core network elements, or processes related to mobility management network elements in the embodiment shown in FIG. 4 , or processes related to AMF in the embodiments shown in FIGS. 5 , 6 and 7 .

An embodiment of the present application further provides a computer program product, where the computer program product is used to store a computer program, and when the computer program is executed by a computer, the computer can implement the embodiment shown in FIG. 3 provided by the above method embodiment. Processes related to core network elements, or processes related to SMF in the embodiments shown in FIG. 5 and FIG. 6 .

The present application also provides a chip including a processor. The processor is configured to read and run the computer program stored in the memory to execute the corresponding operations and/or procedures performed by the target access network device or the target NG-RAN in the method for handover provided by the present application. Optionally, the chip further includes a memory, the memory and the processor are connected to the memory through a circuit or a wire, and the processor is used for reading and executing the computer program in the memory. Further optionally, the chip further includes a communication interface, and the processor is connected to the communication interface. The communication interface is used to receive processed data and/or information, and the processor acquires the data and/or information from the communication interface and processes the data and/or information. The communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip, and the like. The processor may also be embodied as a processing circuit or a logic circuit.

The present application also provides a chip including a processor. The processor is configured to read and run the computer program stored in the memory to execute the corresponding operations and/or processes performed by the source access network device or the source NG-RAN in the method for handover provided in this application. Optionally, the chip further includes a memory, the memory and the processor are connected to the memory through a circuit or a wire, and the processor is used for reading and executing the computer program in the memory. Further optionally, the chip further includes a communication interface, and the processor is connected to the communication interface. The communication interface is used to receive processed data and/or information, and the processor acquires the data and/or information from the communication interface and processes the data and/or information. The communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip, and the like. The processor may also be embodied as a processing circuit or a logic circuit.

The present application also provides a chip including a processor. The processor is configured to read and run the computer program stored in the memory to execute the corresponding operations and/or processes performed by the core network element or the mobility management network element or the AMF in the method for handover provided in this application. Optionally, the chip further includes a memory, the memory and the processor are connected to the memory through a circuit or a wire, and the processor is used for reading and executing the computer program in the memory. Further optionally, the chip further includes a communication interface, and the processor is connected to the communication interface. The communication interface is used to receive processed data and/or information, and the processor acquires the data and/or information from the communication interface and processes the data and/or information. The communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip, and the like. The processor may also be embodied as a processing circuit or a logic circuit.

The present application also provides a chip including a processor. The processor is configured to read and run the computer program stored in the memory to execute the corresponding operations and/or processes performed by the core network element or the session management network element or the SMF in the method for handover provided by the present application. Optionally, the chip further includes a memory, the memory and the processor are connected to the memory through a circuit or a wire, and the processor is used for reading and executing the computer program in the memory. Further optionally, the chip further includes a communication interface, and the processor is connected to the communication interface. The communication interface is used to receive processed data and/or information, and the processor acquires the data and/or information from the communication interface and processes the data and/or information. The communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip, and the like. The processor may also be embodied as a processing circuit or a logic circuit.

The above-mentioned chip can also be replaced by a chip system, which will not be repeated here.

The terms "comprising" and "having" in this application, and any variations thereof, are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to the explicit lists Those steps or units listed may instead include other steps or units not expressly listed or inherent to these processes, methods, products or devices.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual conditions to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, removable hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .

In addition, the term "and/or" in this application is only an association relationship to describe associated objects, which means that there can be three kinds of relationships, for example, A and/or B, which can mean that A exists alone, and A and B exist at the same time. , there are three cases of B alone. In addition, the character "/" in this document generally indicates that the contextual object is an "or" relationship; the term "at least one" in this application can mean "one" and "two or more", for example, A At least one of , B, and C can mean: A alone exists, B exists alone, C exists alone, A and B exist simultaneously, A and C exist simultaneously, C and B exist simultaneously, and A and B and C exist simultaneously. seven situations.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. should be covered within the scope of protection of this application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims (31)

1. a method for switching, characterized in that, comprising: The target access network device acquires session information, where the session information indicates a session to be handed over from the source access network device to the target access network device; wherein, the network slice associated with the session is the first network slice; If the target access network device does not support the first network slice, the target access network device obtains a second network slice supported by the target access network device and corresponding to the first network slice; The target access network device performs handover preparation for the session according to the second network slice. 2. The method according to claim 1, wherein the target access network device performs handover preparation for the session according to the second network slice, comprising: The target access network device allocates resources for the session according to the second network slice; sending, by the target access network device, first information to the terminal device, where the first information indicates the resource; The target access network device sends second information to the source access network device, where the second information indicates that the target access network device accepts the handover of the session. 3. The method of claim 2, wherein the target access network device allocates resources for the session according to the second network slice, comprising: The target access network device configures a physical channel and/or a logical channel corresponding to the second network slice for the session. 4. The method according to any one of claims 1-3, wherein, The second network slice satisfies the service level agreement of the first network slice; or, The second network slice corresponds to the same service as the first network slice. The method according to any one of claims 1-4, wherein acquiring, by the target access network device, a second network slice supported by the target access network device corresponding to the first network slice, comprises: The target access network device acquires the second network slice according to the correspondence between the first network slice and the second network slice. 6. The method of claim 5, wherein the method further comprises: The target access network device receives the corresponding relationship from the source access network device; or, The target access network device receives the corresponding relationship from the core network element. 7. The method according to any one of claims 1-6, wherein the method further comprises: The target access network device sends network slice mapping information to the core network element, where the network slice mapping information enables serving the session according to the second network slice. 8. The method of claim 7, wherein the network slice mapping information comprises: The network slice identifier of the first network slice and the network slice identifier of the second network slice. 9. The method according to any one of claims 1-8, wherein the acquisition of session information by the target access network device comprises: The target access network device receives the session information from the core network element; or, The target access network device receives the session information from the source access network device. 10. The method according to any one of claims 1-9, wherein the session information comprises: The session identifier of the session and the network slice identifier of the first network slice. 11. The method of any one of claims 1-10, wherein the method further comprises: The target access network device sets the network slice associated with the session as the second network slice. 12. The method of any one of claims 1-11, wherein the method further comprises: assigning, by the target access network device, a downlink tunnel endpoint identifier to the session; The target access network device sends the downlink tunnel endpoint identifier to the core network element, where the downlink tunnel endpoint identifier is used for transmission of downlink data packets of the session. 13. The method of any one of claims 1-12, wherein the method further comprises: The target access network device stores second information indicating that a network slice of the session is mapped from the first network slice to the second network slice. 14. A method of switching, comprising: The source access network device acquires the correspondence between the first network slice and the second network slice; The source access network device sends the corresponding relationship to the target access network device; wherein, the target access network device supports the second network slice and does not support the first network slice, and the corresponding relationship is enabled when When the session associated with the first network slice is to be handed over to the target access network device, the target access network device prepares the session for handover according to the second network slice. 15. The method of claim 14, wherein, The second network slice satisfies the service level agreement of the first network slice; or, The second network slice corresponds to the same service as the first network slice. 16. The method according to claim 14 or 15, wherein acquiring the corresponding relationship by the source access network device comprises: The source access network device receives the correspondence from the core network. 17. The method of any one of claims 14-16, wherein the method further comprises: The source access network device sends session information to the target access network device, where the session information indicates a first session to be handed over from the source access network device to the access network device, wherein the first session is to be handed over from the source access network device to the access network device. A network slice associated with a session is the first network slice; The source access network device receives first information from the target access network device, the first information instructing the target access network device to accept the handover of the first session. 18. A method of switching, comprising: obtaining the correspondence between the first network slice and the second network slice; Send the corresponding relationship to the target access network device; wherein, the target access network device supports the second network slice and does not support the first network slice, and the corresponding relationship is enabled when the first network slice is enabled. When the session associated with the network slice is to be handed over to the target access network device, the target access network device prepares the session for handover according to the second network slice. 19. The method according to claim 18, wherein the acquiring the corresponding relationship comprises: The correspondence is received from a unified data management network element, a network slice selection function, or a policy control function. 20. The method of claim 18 or 19, wherein, The second network slice satisfies the service level agreement of the first network slice; or, The second network slice corresponds to the same service as the first network slice. 21. The method according to any one of claims 18-20, wherein the sending the corresponding relationship to the target access network device comprises: Send the corresponding relationship to the target access network device through the target core network element; or The corresponding relationship is sent to the target access network device through the source access network device. 22. The method of any of claims 17-21, wherein the method further comprises: receiving network slice mapping information from the target access network device, the network slice mapping information enabling serving of the session according to the second network slice; The network slice mapping information is sent to a session management network element serving the session. 23. The method of claim 22, wherein the network slice mapping information comprises: The network slice identifier of the first network slice and the network slice identifier of the second network slice. 24. A method of switching, comprising: receiving network slice mapping information from a mobility management network element, the network slice mapping information enabling serving the session according to the second network slice; wherein the network slice of the session is the first network slice; The session is served according to the second network slice. 25. The method of claim 24, wherein the serving the session according to the second network slice comprises: obtaining the charging rule of the second network slice; Charging control is performed on the session using the charging rule. 26. The method of claim 24 or 25, wherein, The second network slice satisfies the service level agreement of the first network slice; or, The second network slice corresponds to the same service as the first network slice. 27. A communication device, comprising a processor; The processor is configured to read and run a program from the memory to implement the method according to any one of claims 1-13. 28. A communication device, comprising a processor; The processor is configured to read and execute a program from the memory to implement the method according to any one of claims 14-17. 29. A communication device, comprising a processor; The processor is used to read and execute the program from the memory to implement the method according to any one of claims 18-23. 30. A communication device, comprising a processor; The processor is adapted to read and execute a program from the memory to implement the method of claim 24 or 25. 31. A communication system comprising one or more communication devices as claimed in claims 27-30.

Images