Inter-Network Change Method and Apparatus, and Related Device

Abstract

An inter-network change method and apparatus, and a related device are disclosed. In the inter-network change method, a terminal determines second network slice information to which first network slice information is mapped, where the first network slice information is information about a first network slice accessed by the terminal, the second network slice information is information about a second network slice, the first network slice is a network slice in a first network, and the second network slice is a network slice in a second network. The terminal sends a request message to the second network and receives an accept message returned by the second network, so that the terminal accesses a network slice identified by network slice information accepted by the second network. It can be learned that embodiments of the present invention can implement a handover operation between network slices of different networks.

Claims

1. An inter-network change method, comprising: obtaining, by a terminal, second network slice information from a first network, wherein the second network slice information is information about a second network slice and the second network slice is a network slice in a second network; sending, by the terminal, a request message to the second network, wherein the request message carries the second network slice information, and the request message is used for the terminal to request to register with or be handed over to the second network slice; and receiving, by the terminal, an accept message returned by the second network, wherein the accept message carries network slice information accepted by the second network, and the network slice information accepted by the second network comprises a part or all of the second network slice information; wherein the first network and the second network have different access network devices and/or core network devices.

2. The method according to claim 1, wherein: mapping information between the first network slice information and the second network slice information is pre-configured on the terminal.

3. The method according to claim 1, wherein the obtaining, by a terminal, second network slice information from a first network comprises: obtaining, by the terminal in a procedure of registering or establishing a session with the first network, the second network slice.

4. The method according to claim 1, wherein the determining, by a terminal, second network slice information to which first network slice information is mapped comprises: obtaining, by the terminal from system information broadcast by the first network, the second network slice information to which the first network slice information is mapped.

5. The method according to claim 1, wherein the accept message further carries third network slice information to which the network slice information accepted by the second network is mapped, the third network slice information is information about a third network slice, and the third network slice is a network slice in the first network.

6. The method according to claim 1, wherein the second network slice is a network slice used by a network slice used after a session is changed from the first network to the second network.

7. The method according to claim 1, wherein the request message further carries a session identifier that is used to identify a session, and the session is changed from the first network slice to the second network slice.

8. The method according to claim 5, wherein the request message further carries a handover indication, and the handover indication is used to instruct the second network to assign, to the terminal, a session address that is the same as a session address assigned by the first network to the terminal.

9. An inter-network change apparatus, comprising: a obtaining module, configured to obtain second network slice information from a first network, wherein the second network slice information is information about a second network slice, and the second network slice is a network slice in a second network; a sending module, configured to send a request message to the second network, wherein the request message carries the second network slice information, and the request message is used for the terminal to request to register with or be handed over to the second network slice; and a receiving module, configured to receive an accept message returned by the second network, wherein the accept message carries network slice information accepted by the second network, and the network slice information accepted by the second network comprises a part or all of the second network slice information; wherein the first network and the second network have different access network devices and/or core network devices.

10. The apparatus according to claim 9, wherein: mapping information between the first network slice information and the second network slice information is pre-configured on the terminal.

11. The apparatus according to claim 9, wherein the obtaining module is specifically configured to obtain, in a procedure of registering or establishing a session with the first network, the second network slice information.

12. The apparatus according to claim 9, wherein the determining module is specifically configured to obtain, from system information broadcast by the first network, the second network slice information to which the first network slice information is mapped.

13. The apparatus according to any one of claim 9, wherein the accept message further carries third network slice information to which the network slice information accepted by the second network is mapped, the third network slice information is information about a third network slice, and the third network slice is a network slice in the first network.

14. The apparatus according to claim 9, wherein the second network slice is a network slice used by a network slice used after a session is changed from the first network to the second network.

15. The apparatus according to claim 9, wherein the request message further carries a session identifier that is used to identify a session, and the session is changed from the first network slice to the second network slice.

16. The apparatus according to claim 13, wherein the request message further carries a handover indication, and the handover indication is used to instruct the second network to assign, to the terminal, a session address that is the same as a session address assigned by the first network to the terminal.

17. A communication device, comprising a processor, a memory, and a communications interface, wherein the processor is connected to both the communications interface and the memory; the memory is configured to store a program instruction; and the processor is configured to invoke the program instruction in the memory to cause the communication device to execute the method as following: obtaining, by a terminal, second network slice information from a first network, wherein the second network slice information is information about a second network slice, and the second network slice is a network slice in a second network; sending, by the terminal, a request message to the second network, wherein the request message carries the second network slice information, and the request message is used for the terminal to request to register with or be handed over to the second network slice; and receiving, by the terminal, an accept message returned by the second network, wherein the accept message carries network slice information accepted by the second network, and the network slice information accepted by the second network comprises a part or all of the second network slice information; wherein the first network and the second network have different access network devices and/or core network devices.

18. The communication device according to claim 17, wherein the obtaining, by a terminal, second network slice information from a first network, the processor is specifically configured to invoke the program instruction in the memory to cause the communication device to execute the method as following: obtaining, by the terminal in a procedure of registering or establishing a session with the first network, the second network slice.

19. The communication device according to claim 17, wherein the second network slice is a network slice used by a network slice used after a session is changed from the first network to the second network.

20. The communication device according to claim 17, wherein the apparatus is a chip.

Description

BRIEF DESCRIPTION OF DRAWINGS

[0044] FIG. 1 is a schematic flowchart of an inter-network change method according to an embodiment of the present invention;

[0045] FIG. 2 is a schematic flowchart of another inter-network change method according to an embodiment of the present invention;

[0046] FIG. 3A, FIG. 3B, and FIG. 3C are a schematic flowchart of still another inter-network change method according to an embodiment of the present invention;

[0047] FIG. 4 is a schematic flowchart of still another inter-network change method according to an embodiment of the present invention;

[0048] FIG. 5 is a schematic flowchart of still another inter-network change method according to an embodiment of the present invention;

[0049] FIG. 6A, FIG. 6B, and FIG. 6C are a schematic flowchart of still another inter-network change method according to an embodiment of the present invention;

[0050] FIG. 7A and FIG. 7B are a schematic flowchart of handing over UE from a 5G network to a 4G network according to an embodiment of the present invention;

[0051] FIG. 8A and FIG. 8B are a schematic flowchart of handing over UE from a 4G network to a 5G network according to an embodiment of the present invention;

[0052] FIG. 9A and FIG. 9B are a schematic flowchart of handover preparations for handing over UE from a 5G network to a 4G network according to an embodiment of the present invention;

[0053] FIG. 10A and FIG. 10B are a schematic flowchart of a handover execution phase for handing over UE from a 5G network to a 4G network based on the handover preparations shown in FIG. 9 according to an embodiment of the present invention;

[0054] FIG. 11A, FIG. 11B, and FIG. 11C are a schematic flowchart of handover preparations for handing over UE from a 4G network to a 5G network according to an embodiment of the present invention;

[0055] FIG. 12A and FIG. 12B are a schematic flowchart of a handover execution phase for handing over UE from a 4G network to a 5G network based on the handover preparations shown in FIG. 11 according to an embodiment of the present invention;

[0056] FIG. 13 is a schematic diagram of a structure of an inter-network change apparatus according to an embodiment of the present invention;

[0057] FIG. 14 is a schematic diagram of a structure of another inter-network change apparatus according to an embodiment of the present invention;

[0058] FIG. 15 is a schematic diagram of a structure of still another inter-network change apparatus according to an embodiment of the present invention;

[0059] FIG. 16 is a schematic diagram of a structure of still another inter-network change apparatus according to an embodiment of the present invention;

[0060] FIG. 17 is a schematic diagram of a structure of a terminal according to an embodiment of the present invention;

[0061] FIG. 18 is a schematic diagram of a structure of an inter-network change device according to an embodiment of the present invention;

[0062] FIG. 19 is a schematic diagram of a structure of another inter-network change device according to an embodiment of the present invention; and

[0063] FIG. 20 is a schematic diagram of a structure of still another inter-network change device according to an embodiment of the present invention.

DESCRIPTION OF EMBODIMENTS

[0064] A rapidly developed mobile communications system needs to meet service requirements in a plurality of scenarios, for example, a mobile broadband service, a large-amount machine-to-device communication service, and a high reliable mobile device communication service. A network slice or a network slicing (Network Slicing, NS) method may be used to meet service requirements in different scenarios, for example, a network slice supporting a large-amount machine-to-device communication (massive Internet of Things, mIoT) service, a network slice supporting an evolved mobile broadband (evolved Mobile Broadband, eMBB) service, or a network slice supporting a critical communication (Critical Communication, CriC) service. The network slice may be defined as a set of logical network function entities that support a communication service requirement in a specific scenario.

[0065] In embodiments of the present invention, the network slice may also be referred to as a network slice instance (Network Slice Instance, NSI). In other words, in a general sense, the NSI may refer to a network slice (Network Slice, NS), or in a specific sense, may refer to one or more network slices. For example, in a specific sense, the NSI may refer to one or more network slices that support a specific service type or provide a specific network capability, or may refer to one or more network slices of a specific type that belong to a specific network slice tenant (such as an enterprise, an administrative organization, or an operator).

[0066] In the embodiments of the present invention, network slice information is information used to identify (or describe) a network slice. Contents included in the network slice information may vary with different communications systems.

[0067] For example, in 5G, network slice information may include at least one of a slice/service type (Slice/Service Type), a network slice identifier or a network slice instance identifier (Network Slice Instance Identifier, NSI ID), single-network slice selection assistance information (Single-Network Slice Selection Assistance Information, S-NSSAI), and network slice selection assistance information (NSSAI). The network slice selection assistance information NSSAI is a set of one or more pieces of S-NSSAI. The S-NSSAI is used to describe a specific network slice, and may include a slice/service type (Slice/Service Type) and slice differentiation information (Slice Differentiator). The slice/service type is used to describe a service or a feature of a network slice. When there are a plurality of network slices with a same slice/service type, the slice differentiation information is used to further differentiate supplementary information of the network slices. For example, the slice differentiation information may be a tenant identifier (Tenant ID), used to identify a specific user, a specific company, or a specific application that leases a network slice. Alternatively, the slice differentiation information may be a slice identifier (Slice ID) or other slice description supplementary information. This is not limited in the embodiments of the present invention.

[0068] In 4G, there is also a concept similar to a network slice, namely, a dedicated core network (DCN, Dedicated Core Network). Each DCN serves a specific type of users/terminals, for example, M2M (machine-to-machine communication) users/terminals, and users/terminals belonging to a specific enterprise. Network slice information may include a dedicated core network type (Dedicated Core Network Type, DCN Type), and/or a dedicated core network identifier (DCN ID), and the like.

[0069] In an interworking and evolution process between 5G and 4G, how to hand over a terminal between network slices of 5G and 4G is a problem that needs to be resolved urgently. The embodiments of this application provide an inter-network change method and a related device, so as to implement a handover between network slices of different communications systems.

[0070] It should be understood that first and second in this application are used to differentiate different objects rather than describe a specific sequence. In addition, the terms including and any other variant thereof, are intended to cover a non-exclusive inclusion. For example, a process, a method, a system, a product, or a device that includes a series of steps or modules is not limited to the listed steps or modules, but optionally further includes an unlisted step or module, or optionally further includes another inherent step or unit of the process, the method, the product, or the device.

[0071] For example, a first network may be a fourth generation mobile communications system, which is referred to as 4G. A second network is a fifth generation mobile communications system, which is referred to as 5G. Alternatively, the first network may be 5G, and the second network may be 4G. A terminal may be a terminal device, such as a mobile phone, a tablet computer, or a wearable device, that can access a network. The first network is used to identify a network currently accessed by the terminal. The second network is used to identify a network to which the terminal is handed over. The first network and the second network have different access network devices and/or core network devices.

[0072] First network slice information is information about a first network slice accessed by the terminal, and second network slice information is information about a second network slice. The first network slice is a network slice in the first network, and the second network slice is a network slice in the second network. The first network may include a first access network device. The first network slice may include a first core network device. Optionally, the first network may further include a first default core network device. Correspondingly, the second network is a network with which the terminal is to register or a network to which the terminal is to be handed over. The second network may include a second access network device, and the second network slice may include a second core network device. The second network may further include a second default core network device. The second network slice information is network slice information to which the first network slice information is mapped. Optionally, network slice information of the second network with which the terminal finally registers or the second network to which the terminal is handed over may be the same as or different from the second network slice information, or may be a part or all of the second network slice information.

[0073] In an optional implementation, when the terminal discovers the second network by measuring a cell signal and determines to move or be handed over to the second network, the terminal sends, to the second network, a request message used to request to register with or be handed over to the second network. The request message may be a registration request (Registration Request) message. Specifically, the registration request message may be an initial registration request (Initial Registration Request) message, an (initial) attach request ((Initial) Attach Request) message, a mobility registration request (Mobility Registration Request), or a tracking area update request (Tracking Area Update Request, TAU Request) message. The request message may carry a fixed identifier of the terminal, for example, an international mobile subscriber identity (International Mobile Subscriber Identity, IMSI), or carry a temporary identity (for example, a GUTI, Globally Unique Temporary Identity, globally unique temporary identity) of the terminal in the first network. The request message may further carry the second network slice information to which the first network slice information is mapped.

[0074] Correspondingly, when the terminal registers with or is handed over to the second network, an accept message returned by the second network to the terminal may be a registration accept (Registration Accept) message. Specifically, the registration accept message may be an initial registration accept (Initial Registration Accept) message, an (initial) attach accept ((Initial) Attach Accept) message, a mobility registration accept (Mobility Registration Accept) message, or a tracking area update accept (Tracking Area Update Accept, TAU Accept) message. The accept message may carry network slice information accepted by the second network, and may further carry network slice information to which the network slice information accepted by the second network is mapped, so that the terminal updates or stores a mapping relationship between the network slice information of the first network and the network slice information of the second network.

[0075] Optionally, the request message may further carry a handover identifier (Handover indication). The second core network device may not provide, based on the handover identifier, network slice information to which information about a network slice that the second network allows the terminal to access is mapped, in other words, the accept message does not carry third network slice information to which the network slice information accepted by the second network is mapped. The handover identifier may be further used to instruct the second network to assign, to the terminal, a session address that is the same as a session address assigned by the first network to the terminal.

[0076] In another optional implementation, when the terminal reports a measurement report (the measurement report may include signal measurement information of a serving cell and/or a neighboring cell, or the like) to the first access network device, and the first access network device determines, based on the measurement report, that the terminal needs to register with or be handed over to the second network, the first access network device sends a handover request message to the first core network device. The first core network device determines the second network slice information to which the first network slice information is mapped and determines the second core network device, and sends the request message to the determined second core network device.

[0077] Optionally, when the first core network device is an MME in the 4G network, the first access network sends the handover request message to the first core network device, the first core network device sends a second request message to the second default core network device, and the second default core network device (namely, a default core network device in 5G) determines the second network slice information to which the first network slice information is mapped and the second core network device supporting the second network slice. It can be learned that, in this implementation, the second default core network device rather than the first core network device performs an operation of determining a target network slice during an inter-network change. This avoids modifying the MME in the 4G network and facilitates promotion of the inter-network change method.

[0078] The request message sent by the first access network device or the first core network device is used to request a handover or request a handover preparation. For example, the request message may be a handover request message or a forwarding relocation request message. Correspondingly, a response message returned by a second core network service entity may be used to respond to the handover request or a handover preparation request. For example, the response message may be a handover command message or a forwarding relocation response message.

[0079] In the embodiments of the present invention, the first network slice may be a network slice used by the terminal to establish a session in the first network, and the second network slice is a network slice used by the terminal to re-establish the session in the second network or a network slice used after the session is changed from the first network to the second network. The request message may further carry a session identifier that is used to identify a session. The session may be established in the first network slice and be re-established in the second network slice, or be changed from the first network slice to the second network slice.

[0080] Specifically, the following describes in detail an inter-network change method, a related apparatus, and a device that are provided in the embodiments of the present invention.

[0081] FIG. 1 is a schematic flowchart of an inter-network change method according to an embodiment of the present invention. The inter-network change method shown in FIG. 1 is that a terminal discovers a second network by measuring a cell signal, and determines to register with or be handed over to the second network. The inter-network change method may include or include at least the following steps.

[0082] S101: The terminal determines second network slice information to which first network slice information is mapped.

[0083] In an optional implementation, the second network slice information to which the first network slice information is mapped may be pre-configured on the terminal.

[0084] In another optional implementation, that the terminal determines second network slice information to which first network slice information is mapped in the step S101 may include: obtaining, by the terminal in a procedure of registering or establishing a session with a first network, the second network slice information to which the first network slice information is mapped. For example, the terminal obtains the second network slice information to which the first network slice information is mapped from a registration accept message or a session establishment accept message sent by the first network to the terminal.

[0085] For example, the obtaining, by the terminal in a procedure of registering with a first network, the second network slice information may include or include at least the following steps: sending, by the terminal, a registration request message to the first network, where the registration request message carries parameters, such as an identifier of the terminal (for example, an international mobile subscriber identity (International Mobile Subscriber Identity, IMSI) of the terminal or a temporary identity of the terminal in the first network), and information about a first network slice that the terminal requests to access.

[0086] The first network continues to perform the terminal registration procedure according to the registration request message of the terminal. The registration procedure includes: A core network device in the first network performs authentication on the terminal, negotiates a security/encryption parameter, and the like; selects a corresponding first network slice and a first core network device in the first network slice for the terminal based on the first network slice information carried in the registration request message and based on subscription information determined based on the identifier of the terminal; and returns a registration accept message to the terminal through a first access network device.

[0087] The registration accept message may further carry the second network slice information to which the first network slice information is mapped.

[0088] For example, the obtaining, by the terminal in a procedure of establishing a session with a first network, the second network slice information may include or include at least the following steps: sending, by the terminal, a session establishment request message to the first network; where the session establishment request message carries parameters, such as an identifier of the terminal (for example, an IMSI of the terminal or a temporary identity of the terminal in the first network), and the first network slice information of the first network. Herein, the first network slice information of the first network is used to identify the first network slice and indicate that the terminal requests to establish a session in the network slice.

[0089] The first core network device in the first network slice allocates a user plane function entity to the terminal in the first network slice based on the session establishment request message.

[0090] The first core network device further sends a session establishment accept message to the terminal through the first access network device.

[0091] The session establishment accept message may carry the corresponding second network slice information, to which the first network slice information of the first network is mapped, of the second network.

[0092] In still another optional implementation, in step S101, that the terminal determines the corresponding second network slice information, to which the first network slice information of the first network accessed by the terminal is mapped, of the second network may include: obtaining, by the terminal from system information broadcast by the first network, the corresponding second network slice information, to which the first network slice information of the first network is mapped, of the second network.

[0093] For example, the terminal reads, from system information broadcast by a cell in a 4G network on which the terminal currently camps, network slice information, to which network slice information of the 4G network is mapped, of a 5G network, for the terminal to use when the terminal subsequently registers with or is handed over to the 5G network. Alternatively, the terminal reads, from system information broadcast by a cell in a 5G network on which the terminal currently camps, network slice information, to which network slice information of the 5G network is mapped, of a 4G network, for the terminal to use when the terminal subsequently registers with or is handed over to the 4G network.

[0094] S102: The terminal sends a request message to the second network.

[0095] The request message carries the second network slice information. The request message is used for the terminal to request to register with or be handed over to a second network slice.

[0096] In this embodiment of the present invention, that the terminal sends a request message to the second network may include: sending, by the terminal, the request message to a second access network device in the second network, determining, by the second access network device, a second core network device based on the second network slice information carried in the request message, and performing, by the second core network device, a registration operation or a handover operation to register or hand over the terminal with or to the second network.

[0097] Optionally, if the second access network device cannot determine, based on the second network slice information carried in the request message, the second core network device that can serve the terminal, the second access network device may forward the request message to a second default core network device in the second network. The second default core network device determines, based on the second network slice information and the subscription information of the terminal, whether the second default core network device is capable of serving the terminal. If the second default core network device is capable of serving the terminal, the second default core network device performs the registration operation, and registers the terminal with the second network. If the second default core network device is incapable of serving the terminal, the second default core network device selects a second core network device for the terminal, and sends information (for example, an identifier or a group identifier of a second core network service entity) about the selected second core network device to the second access network device. The second access network device selects, based on the information about the second core network device, the second core network device serving the terminal.

[0098] Optionally, the request message further carries a handover indication, and the handover indication is used to instruct the second network to assign, to the terminal, a session address that is the same as a session address assigned by the first network to the terminal. The session address herein may be a packet data session (Packet Data Unit or Protocol Data Unit session, PDU session), or an address of a packet data network connection (Packet Data Network Connection, PDN Connection), for example, an IP address of the PDU session or the PDN connection.

[0099] The request message may further carry a session identifier that is used to identify a session. The session is established in the first network slice and is re-established in the second network slice, or is changed from the first network slice to the second network slice.

[0100] S103: The terminal receives an accept message returned by the second network, where the accept message carries network slice information accepted by the second network.

[0101] In this embodiment of the present invention, that the terminal receives an accept message returned by the second network may include the following steps: receiving, by the second access network device, the accept message from the second core network device, and forwarding, by the second access network device, the accept message to the terminal. The accept message may be a registration accept message corresponding to the registration request message. The accept message may carry the network slice information accepted by the second network (or allowed by the second network for the terminal to access, or selected by the second network for the terminal). Herein, the network slice information accepted by the second network may be the same as or different from the second network slice information, or may be a part or all of the second network slice information.

[0102] Optionally, the accept message may further carry third network slice information to which the network slice information accepted by the second network is mapped. The third network slice information is information about a third network slice and the third network slice is a network slice in the first network. The third network slice information is used to update a mapping relationship between the first network slice information and the second network slice information on the terminal, or store the mapping relationship carried in the accept message.

[0103] If the request message carries the handover indication, the accept message may not carry the third network slice information to which the network slice information accepted by the second network is mapped.

[0104] It can be learned that in this implementation, the terminal may determine the second network slice information to which the first network slice information is mapped, and send the request message to the second network, where the request message carries the second network slice information and is used for the terminal to request to register with or be handed over to the second network slice; correspondingly, the terminal may receive the accept message returned by the second network, where the accept message carries the network slice information accepted by the second network. This implements a handover of the terminal between network slices of different networks.

[0105] FIG. 2 is a schematic flowchart of another inter-network change method disclosed in an embodiment of the present invention. The inter-network change method in FIG. 2 is described from a perspective of a target network with which a terminal is to register or to which a terminal is to be handed over, that is, a second network side. As shown in FIG. 2, the inter-network change method may include the following steps.

[0106] S201: A second access network device receives a request message sent by the terminal.

[0107] The request message carries second network slice information to which first network slice information is mapped. The first network slice information is information about a first network slice accessed by the terminal, and the second network slice information is information about a second network slice. The first network slice is a network slice in a first network, and the second network slice is a network slice in a second network.

[0108] The request message may further carry a handover indication, and the handover indication is used to instruct the second network to assign, to the terminal, a session address that is the same as a session address assigned by the first network to the terminal. The session address herein may be a packet data session (Packet Data Unit or Protocol Data Unit session, PDU session), or an address of a packet data network connection (Packet Data Network Connection, PDN Connection), for example, an IP address of the PDU session or the PDN connection.

[0109] The request message may further carry a session identifier that is used to identify a session. The session is established in the first network slice and is re-established in the second network slice, or is changed from the first network slice to the second network slice.

[0110] S202: The second access network device determines a second core network device.

[0111] The second core network device is a core network device in the second network slice.

[0112] S203: The second access network device sends the request message to the second core network device for processing, so as to perform a procedure in which the terminal registers with or is handed over to the second network.

[0113] S204: The second access network device receives an accept message returned by the second core network device, and sends the accept message to the terminal, where the accept message carries network slice information accepted by the second network.

[0114] In this embodiment of the present invention, when the second access network device cannot determine a second core network device that supports the second network slice, the second access network device forwards the request message to a second default core network device in the second network, so that the second default core network device selects, based on the second network slice information and subscription information of the terminal, the second core network device that supports the second network slice, and sends the request message to the second core network device for processing, so as to perform the procedure in which the terminal registers with or is handed over to the second network.

[0115] For example, if the first network is a 5G network and the second network is a 4G network, when the terminal is handed over from the 5G network to the 4G network, an access network (Radio Access Network, RAN) device in the 4G network may select a second core network device that supports a second network slice that is identified (or described) by using a DCN type and/or a DCN ID. The second core network device may be an MME in a dedicated core network (Dedicated Core Network, DCN). The MME processes the request message to complete a registration or handover procedure of the terminal in the 4G network.

[0116] If the RAN device in the 4G network cannot identify the second network slice information (for example, the DCN type and/or the DCN ID) or does not support an enhanced dedicated core network (enhanced Dedicated Core Network, eDecor) mechanism, the RAN device may send the request message to a default core network device, namely, a default mobility management entity (Mobility Management Entity, MME). By default, the MME determines whether the MME is capable of serving the terminal. If the MME is capable of serving the terminal, the MME processes the request message and completes a registration procedure of the terminal in the 4G network. If the MME is incapable of serving the terminal, by default the MME selects a new MME based on the second network slice information and the subscription information of the terminal, and sends a group identifier or an identifier of the new MME to the RAN device. The RAN device sends the request message to the new MME, to complete the registration or handover procedure of the terminal in the 4G network.

[0117] For another example, if the first network is a 4G network and the second network is a 5G network, when the terminal is to register with the 5G network or is to be handed over from the 4G network to the 5G network, an access network (Access Network, AN) in the 5G network may select a second core network device that supports a second network slice identified by the second network slice information. The second core network device may be a serving common control network function (Serving Common Control Network Function, S-CCNF) entity or an access and mobility management function (Access and Mobility Management Function, AMF) entity in an S-CCNF entity. The AN forwards the request message to the S-CCNF (or AMF) entity, processes the request message, and completes a registration or handover procedure of the terminal in the 5G network.

[0118] Optionally, if the AN in the 5G network cannot select an S-CCNF entity that supports the second network slice identified by the second network slice information, the AN sends the request message to a default core network service entity default CCNF or a network slice selection function (Network Slice Selection Function, NSSF) entity or an AMF in a default CCNF entity. The default CCNF (or AMF/NSSF) entity selects, based on the request message, the S-CCNF entity in the second network slice identified by the second network slice information, and forwards the request message to the S-CCNF entity, or forwards the request message to the S-CCNF entity through the AN in the 5G network, and the S-CCNF entity processes the request message, to complete a registration procedure of the terminal in the 5G network.

[0119] It can be learned that in this embodiment of the present invention, the second access network device may receive the request message sent by the terminal, where the request message carries the second network slice information to which the first network slice information is mapped; the second access network device determines the second core network device and sends the request message to the second core network device for processing, so as to perform a procedure in which the terminal registers with or is handed over to the second network; the second access network device receives the accept message returned by the second core network device and sends the accept message to the terminal, where the accept message carries the network slice information accepted by the second network. This implements a handover of the terminal between network slices of different networks.

[0120] FIG. 3, including FIG. 3A, FIG. 3B, and FIG. 3C is a schematic flowchart of still another inter-network change method disclosed in an embodiment of the present invention. The inter-network change method shown in FIG. 3 is described from a manner of interaction among a terminal, a first network, and a second network. In the inter-network change method shown in FIG. 3, the first network includes a first access network device, a first network slice, accessed by the terminal, in the first network may include a first core network device, the second network includes a second access network device, and the second network slice, in the second network, to which the terminal requests to be handed over may include a second core network device. Optionally, the first network may further include a first default core network device, and the second network may further include a second default core network device. Specifically, the inter-network change method shown in FIG. 3 may include the following steps.

[0121] S301: The terminal sends a first request message to the first access network device.

[0122] In this embodiment of the present invention, the first request message may be a registration request message used by the terminal to register with the first network, and the first request message may carry a terminal identifier and first network slice information of the first network that the terminal requests to access. The terminal identifier may be an IMSI or a temporary identity of the terminal in the first network.

[0123] S302: The first access network device receives and processes the first request message sent by the terminal, and performs a registration procedure of the terminal in the first network.

[0124] The registration procedure includes: The first core network device and/or the first access network device may perform authentication on the terminal, negotiate a security/encryption parameter, and the like, and select, based on the first network slice information and subscription information of the terminal, the first network slice and the first core network device, and establish a session or a packet data network connection, and the like for the terminal.

[0125] For example, when the first network is a 5G network, an access network AN in the 5G network selects a core network service entity S-CCNF that supports network slice information based on the network slice information carried in a request message. The S-CCNF entity selects a corresponding network slice for the terminal based on the network slice information and the subscription information of the terminal. Optionally, the S-CCNF entity may further establish a session with the terminal. A session identifier of the session may be carried in a request message for registering with or handing over to the second network, so that the session established in the first network slice identified by the first network slice information of the first network can be re-established in the second network slice of the second network, or can be changed from the first network slice to the second network slice.

[0126] For another example, when the first network is a 4G network, an access network RAN or a default mobility management entity MME in the 4G network may select, based on network slice information carried in a request message and the subscription information of the terminal, a network slice DCN and a mobility management entity MME that supports the network slice information for the terminal. Optionally, the MME may establish a packet data network connection PDN connection to the terminal.

[0127] S303: The first access network device receives a first accept message from the first core network device, and sends the first accept message to the terminal.

[0128] Optionally, in this embodiment of the present invention, the first accept message carries network slice information accepted by the first network (in other words, the terminal is allowed to access, or selected for the terminal). The network slice information may include a part or all of the first network slice information in the first request message. This embodiment of the present invention is described by using an example in which the network slice information accepted by the first network is the same as the first network slice information in the first request message. The information is not distinguished in the following description. The first accept message may be a registration accept message of the first network.

[0129] Optionally, the first accept message may further carry second network slice information to which the first network slice information is mapped, so that the terminal stores or updates a mapping relationship between the network slice information.

[0130] S304: The terminal discovers the second network by measuring a cell signal, and determines to move or be handed over to the second network.

[0131] S305: The terminal determines the second network slice information to which the first network slice information is mapped.

[0132] S306: The terminal sends a second request message to the second access network device, where the second request message carries the second network slice information and is used for the terminal to request to register with or be handed over to the second network.

[0133] Optionally, if the terminal is in connected mode, the second request message may further carry a handover indication, and the handover indication is used to instruct the second network to assign, to the terminal, a session address that is the same as a session address assigned by the first network to the terminal.

[0134] The second request message may be a registration request message of the second network, including an attach request message or a tracking area update request message.

[0135] S307: The second access network device receives the second request message sent by the terminal and determines the second core network device.

[0136] S308: The second access network device sends the request message to the second core network device for processing, so as to perform a procedure in which the terminal registers with or is handed over to the second network.

[0137] Optionally, if the second access network device cannot determine the second core network device, the second access network device may forward the second request message to the second default core network device, and the second default core network device determines the second core network device and forwards the second request message to the second core network device for processing, so as to perform the procedure in which the terminal registers with or is handed over to the second network.

[0138] S309: The second access network device receives a second accept message returned by the second core network device.

[0139] S310: The second access network device sends the second accept message to the terminal.

[0140] The second accept message may be a registration accept message of the second network, including an attach accept message or a tracking area update accept message.

[0141] Optionally, the second accept message further carries third network slice information to which the network slice information accepted by the second network is mapped, so that the terminal may update the locally configured or stored mapping relationship between the first network slice information and the second network slice information in time. The third network slice information is information about a third network slice, and the third network slice is a network slice in the first network.

[0142] It can be learned that in the inter-network change method shown in FIG. 3, the terminal may determine, based on the measurement of cell signal, to move or be handed over to the second network, and register with the second network based on the second network slice information to which the first network slice information is mapped. This implements a handover of the terminal between network slices of different networks.

[0143] Particularly, the methods shown in FIG. 1 to FIG. 3 may be applicable to a scenario in which the terminal is in idle mode, or the terminal is in connected mode and has a relatively low requirement for a handover delay (in other words, a session is allowed to be interrupted for a relatively long time).

[0144] FIG. 4 is a schematic flowchart of still another inter-network change method disclosed in an embodiment of the present invention. Specifically, the inter-network change method shown in FIG. 4 may include the following steps.

[0145] S401: A first core network device receives a first request message sent by a first access network device.

[0146] The first request message is used for a terminal to request to be handed over to a second network.

[0147] S402: The first core network device determines second network slice information to which first network slice information is mapped.

[0148] S403: The first core network device determines a second core network device and sends a second request message to the second core network device, where the second request message carries the second network slice information.

[0149] In this embodiment of the present invention, the request message may be a handover request message or a forwarding relocation request message. The first core network device may select, based on the second network slice information, the second core network device that supports a second network slice.

[0150] The request message may carry a session identifier that is used to identify a session. The session is established in a first network slice and is re-established in the second network slice, or is changed from the first network slice to the second network slice.

[0151] For example, if the first network is a 5G network and the second network is a 4G network, a core network service S-CCNF entity (or an AMF entity in an S-CCNF entity, and the AMF entity is also used hereinafter) in the 5G network may select, based on network slice information of the 4G network and subscription information of the terminal, an MME that supports a DCN identified by the network slice information of the 4G network. For another example, if the first network is a 4G network and the second network is a 5G network, a mobility management entity MME in the 4G network may select, based on network slice information of the 5G network, a core network service S-CCNF entity that supports a network slice identified by the network slice information. An existing MME needs to be modified to implement this implementation, and the modified MME may be referred to as an enhanced MME.

[0152] S404: The first core network device receives a response message returned by the second core network device, and sends a handover command to the terminal through the first access network device, so that the terminal is handed over to the second network slice.

[0153] In this embodiment of the present invention, when receiving the request message, the second core network device may select the second network slice based on the second network slice information carried in the request message, and send the request message to a session management function (Session Management Function, SMF) entity in the second network slice. Then, the SMF entity selects a user plane function (User Plane Function, UPF) entity in the second network slice, for example, a gateway, to establish a packet data session. In addition, the second core network device sends a handover request message to the second access network device in the second network, where the handover request message carries a parameter such as the second network slice information, so that the second access network device may select a second network slice instance for the terminal and determine a radio resource. When receiving a handover request acknowledgment message sent by the SMF entity and the second access network device, the second core network device may send a response message to the first core network device. The response message may be a forwarding relocation response message. The response message carries parameters, such as a list of the established packet data sessions mentioned above and a transparent container that is sent by a target access network node to a source access network node.

[0154] It can be learned that in the inter-network change method shown in FIG. 4, the first core network device may determine the second network slice information to which the first network slice information is mapped; the first core network device determines the second core network device and sends the request message to the second core network device, where the request message carries the second network slice information; and the first core network device receives the response message returned by the second core network device and sends the handover command to the terminal, so that the terminal is handed over to the second network slice. This implements a handover of the terminal between network slices of different networks.

[0155] FIG. 5 is a schematic flowchart of still another inter-network change method disclosed in an embodiment of the present invention. A different from the inter-network change method shown in FIG. 4 lies in that, the inter-network change method shown in FIG. 5 may also be implemented without modifying an MME in a 4G network, in other words, a second network with which a terminal is to register with or to which a terminal is to be handed over determines second network slice information and a second core network service entity. Specifically, the inter-network change method shown in FIG. 5 may include the following steps.

[0156] S501: A second default core network device receives a first request message sent by a first core network device.

[0157] The first request message is used for the terminal to request to register with or be handed over to the second network, and the first request message carries the first network slice information.

[0158] The first request message may carry a session identifier that is used to identify a session. The session is established in a first network slice and is re-established in a second network slice, or is changed from the first network slice to the second network slice.

[0159] S502: The second default core network device determines the second network slice information to which first network slice information is mapped.

[0160] The first network slice information is information about the first network slice accessed by the terminal, the second network slice information is information about the second network slice, the first network slice is a network slice in a first network, and the second network slice is a network slice in the second network.

[0161] S502: The second default core network device determines a second core network device.

[0162] S503: The second default core network device sends a second request message to the second core network device, where the second request message carries the second network slice information and is used for the terminal to request to register with or be handed over to the second network slice.

[0163] Optionally, the first request message may further carry a handover indication. The handover indication is used to instruct the second network to assign, to the terminal, a session address that is the same as a session address assigned by the first network to the terminal.

[0164] For example, when the first network is a 4G network, the second network is a 5G network, and a mobility management entity MME in the 4G network receives a handover request sent by an access network AN in the 4G network, the MME sends a request message to a default core network service entity Default CCNF (or an NSSF entity or an AMF entity in a Default CCNF entity, and the NSSF entity or the AMF entity are also used hereinafter) in the 5G network. The request message carries network slice information of the 4G network accessed by the terminal, for example, a DCN ID. The Default CCNF entity determines network slice information, of the 5G network, to which the DCN ID is mapped in the 5G network, and selects a core network service S-CCNF entity (or an AMF entity in an S-CCNF entity, and the AMF entity is also used hereinafter) that supports a network slice identified by the network slice information of the 5G network. The Default CCNF entity sends a forwarding redirection request message to the S-CCNF entity. The forwarding redirection request message carries the network slice information of the 5G network. The S-CCNF entity establishes a packet data session in the network slice of the 5G network and sends a handover request message to an access network AN in the 5G network. The access network AN in the 5G network returns a handover request acknowledgment message. The access network AN in the 5G network may select a 5G access network slice instance for the terminal and determine a radio resource. When receiving the handover request acknowledgment message sent by the access network in the 5G network, the S-CCNF entity may send a response message to the MME. The response message may be a forwarding relocation response message. The response message carries parameters, such as a session list of the established packet data sessions and a transparent container that is sent by a target access network node to a source access network node. Then, the terminal performs a handover operation to access the 5G network.

[0165] It can be learned that the second default core network device may determine the second network slice information to which the first network slice information is mapped, determines the second core network device, and sends the second request message to the second core network device, where the second request message carries the second network slice information and is used for the terminal to register with the second network. In this implementation, when the terminal is handed over from the 4G network to the 5G network, the 5G network determines the corresponding network slice information in the 5G network, and may further determine the core network service entity supporting the network slice information. In this way, the mobility management entity MME in the 4G network does not need to be modified, so that a difficulty of implementing the inter-network change method is reduced.

[0166] FIG. 6A, FIG. 6B, and FIG. 6C are a schematic flowchart of a still another inter-network change method disclosed in an embodiment of the present invention. The inter-network change method shown in FIG. 6 is described from a manner of interaction among a terminal, a first network, and a second network. Specifically, in the inter-network change method shown in FIG. 6, the first network includes a first access network device, and a first network slice, accessed by the terminal, in the first network may include a first core network device and a first session management entity; the second network includes a second access network device, and a second network slice, in the second network, to which the terminal requests to be handed over may include a second core network device and a second session management device. When the first network is a 4G network and the second network is a 5G network, the first access network device is a 4G AN, the first core network device is an MME, the first session management device is a serving gateway (Serving Gateway, S-GW) and/or a packet data network gateway (PDN Gateway, P-GW), the second access network device is a 5G AN, the second core network device is an S-CCNF (or AMF) entity, and the second session management device is an SMF entity.

[0167] The inter-network change method shown in FIG. 6 may include the following steps.

[0168] S601: The terminal sends a first request message to the first access network device.

[0169] In this embodiment of the present invention, the first request message may be a registration request message. The first request message carries a terminal identifier and first network slice information of a network slice that the terminal requests to access. The terminal identifier may be an IMSI or a temporary identity of the terminal in the first network.

[0170] S602: The first access network device receives and processes the first request message, and performs a registration procedure of the terminal accessing the first network.

[0171] The registration procedure may include: The first network core network device may perform operations, for example, perform authentication on the terminal, negotiate a security/encryption parameter, and select, for the terminal based on the first network slice information and subscription information of the terminal, the first network slice and the first core network device that supports the first network slice.

[0172] S603: The first access network device receives a first accept message from the first core network device, and sends the first accept message to the terminal.

[0173] In this embodiment of the present invention, the first accept message carries network slice information accepted by the first network (in other words, the terminal is allowed to access, or selected for the terminal). The network slice description information may be the same as the first network slice information in the first request message or a subset of the first network slice information. By way of example, they are the same in this embodiment of the present invention and are not differentiated in the following.

[0174] Optionally, the registration procedure may further include: establishing, by the terminal, a packet data session with the first network.

[0175] S604: The terminal reports a measurement report to the first access network device.

[0176] In this embodiment of the present invention, the measurement may include signal measurement information of a serving cell and/or a neighboring cell, and the like.

[0177] S605: The first access network device determines, based on the measurement report, that the terminal needs to be handed over to the second network.

[0178] S606: The first access network device sends a second request message to the first core network device.

[0179] In this embodiment of the present invention, the second request message may be a handover request message. The second request message carries the terminal identifier, a node identifier of the second access network device, a radio resource parameter allocated by the first access network device to the terminal, and the like. The radio resource parameter allocated by the first access network device to the terminal may also be referred to as a transparent container (Source to Target Transparent Container) sent by a source access network node to a target access network node.

[0180] S607: The first core network device determines second network slice information to which the first network slice information is mapped.

[0181] The first network slice information is information about the first network slice accessed by the terminal, the second network slice information is information about the second network slice, the first network slice is a network slice in the first network, and the second network slice is a network slice in the second network.

[0182] S608: The first core network device determines the second core network device.

[0183] The second core network device is a core network device in the second network slice and is determined by the first core network device based on the second network slice information.

[0184] S609: The first core network device sends the second request message to the second core network device.

[0185] Specifically, the second request message in this step may further carry the second network slice information. Alternatively, the second request message that carries the second network slice information may be a forwarding relocation request message.

[0186] S610: The second core network device selects a second session management entity based on the received second request message.

[0187] For example, when the second core network device is an MME, the MME selects the second session management device that supports a DCN ID of the second network slice information, namely, a packet data network gateway (Packet Data Network Gateway, PDN GW) and a serving gateway (Serving Gateway, S-GW). In addition, the MME may map a mobility management context (UE MM context) and a session management context (UE SM context) of the 5G network to a terminal context (UE context) in the 4G network. The UE context may include a packet data network connection (PDN connection), information about a 4G evolved packet system bearer (EPS bearer), and the like.

[0188] For another example, when the second core network device is an S-CCNF (or AMF) entity, the S-CCNF (or AMF) entity selects a specific 5G network slice instance NSI and selects an SMF entity in the NSI. In addition, the S-CCNF (or AMF) entity maps information related to UE mobility management (Mobility Management, MM) in the 4G UE context to the 5G terminal mobility management context (UE MM context) and maps an authentication/security parameter in the 4G UE context to a 5G UE authentication/security parameter for storing.

[0189] S611: The second core network device sends a session establishment request message to the selected second session management device.

[0190] The session establishment request message carries the terminal identifier, context information related to terminal session management, and the like.

[0191] S612: The second session management device maps context information related to terminal session management in the first network to context information related to terminal session management in the second network, and returns a session establishment response message to the second core network device.

[0192] S613: The second core network device sends a handover request message to the second access network device.

[0193] S614: The second access network device sends a handover request acknowledgement message to the second core network device.

[0194] Specifically, if the second access network device is a 5G access network, the second access network device may select a 5G access network slice instance for the terminal and determine a radio resource.

[0195] S615: The second core network device sends a second response message to the first core network device.

[0196] Corresponding to step S609, the second response message may be a forwarding relocation response message, and the second response message may carry a packet data session address and the context information of terminal session management.

[0197] S616: The first core network device receives the second response message returned by the second core network device, and sends a handover command to the terminal, so that the terminal is handed over to the second network slice identified by the second network slice information.

[0198] Specifically, that the first core network device sends a handover command to the terminal, so that the terminal is handed over to the second network slice may include the following operations: The first core network device sends the handover command to the first access network device; the first access network device forwards the handover command to the terminal, where the handover command carries a bearer list of to-be-released radio access bearers, a radio resource parameter, or the like; the terminal accesses the second access network device according to the handover command, and sends a handover complete message to the second access network device; the second access network device sends a handover notification message to the second core network device; the second core network device sends a forwarding redirection complete notification message to the first core network device; the second core network device sends a modify bearer request message to the second session management entity; the second session management device returns a modify bearer response message to the second core network device; the terminal initiates a tracking area update (Tracking Area Update, TAU) procedure to the second core network device; the first core network device sends a session deletion request message to the first session management device; and the first session management device releases a packet data session resource of the terminal in the first network and returns a session deletion response message to the first core network device.

[0199] It should be noted that, the core network device and the session management device may be combined in the 5G network. If the core network device and the session management device are combined, operations between the two devices may not be performed.

[0200] Correspondingly, the operations between the two devices may be all performed by the core network device.

[0201] In addition, it should be noted that, when the first network is the 4G network and the second network is the 5G network, steps S608 and S609 may be performed by the second network, namely, a default core network service entity in the 5G network. Specifically, steps S608 and S609 may be replaced with the following operations: receiving, by a second default core network device, a request message sent by the core network device in the first network, where the request message carries information about the first network slice accessed by the terminal; determining, by the second default core network device in the second network, the second network slice information to which the first network slice information is mapped; determining, by the second default core network device, the second core network device; and sending, by the second default core network device, a request message to the second core network device, where the request message carries the second network slice information, and the request message is used for the terminal to request to register with or be handed over to the second network slice in the second network.

[0202] In this implementation, the core network device in the 4G network does not need to be modified, so that a difficulty of implementing the inter-network change method is reduced.

[0203] Particularly, the inter-network change methods shown in FIG. 4 to FIG. 6 are applicable to a scenario in which the terminal is in connected mode or a to-be-changed session has a relatively high requirement on a handover delay (in other words, a session is allowed to be interrupted or changed for a relatively short time).

[0204] FIG. 7A and FIG. 7B are a schematic flowchart of handing over a terminal from a 5G network to a 4G network according to an embodiment of the present invention. In the embodiments shown in FIG. 7 to FIG. 12, the terminal may be user equipment (User Equipment, UE), an access network device in the 5G network is a 5G access network (Access Network, AN) node, a core network device in the 5G network is a serving common control network function (Serving Common Control Network Function, S-CCNF) entity in the 5G network, a default core network device in the 5G network is a default serving common control network function (Default Serving Common Control Network Function, Default S-CCNF) entity in the 5G network, and a network slice of the 5G network is an NS. An access network device in the 4G network is a 4G access network (Access Network, AN) node, a core network device in the 4G network is a mobility management entity (Mobility Management Entity, MME) in the 4G network, a default core network device in the 4G network is a default mobility management entity (Default Mobility Management Entity, Default MME) in the 4G network, and a network slice of the 4G network is a dedicated core network DCN. Optionally, the network slice of the 5G network may further include a session management function (Session Management Function, SMF) entity or an access and mobility management function (Access and Mobility Management Function, AMF) entity. The network slice of the 4G network may further include a serving gateway (Serving Gateway, S-GW) and/or a PDN gateway (PDN Gateway, P-GW). Handing over the terminal from the 5G network to the 4G network may include the following steps.

[0205] 1. The terminal reads, from a preconfiguration or a broadcast message, 4G DCN description information of the 4G network to which 5G NSI description information is mapped.

[0206] For example, a mapping relationship between the 5G NSI description information and the 4G DCN description information is pre-configured on the UE.

[0207] For another example, the UE reads, from system information broadcast by the 5G network, the 5G NSI description information and the corresponding 4G DCN description information.

[0208] 2. The UE sends a registration request message Registration Request to the 5G access network.

[0209] The Registration Request is a 5G registration/attach request message and may include a 5G initial registration (Initial Registration)/attach request (Attach Request) message or a 5G tracking area update request (Tracking Area Update Request) message. The Registration Request carries parameters, such as a first identifier (for example, an IMSI or a temporary identity of the 5G UE) of the UE, and description information of a 5G NSI to which the UE requests to access.

[0210] 3. Perform a 5G registration procedure.

[0211] The 5G registration procedure includes: A 5G core network function entity preforms steps, such as performing authentication on the UE, negotiating a security/encryption parameter, and selecting the NSI for the UE based on the description information of the 5G NSI and subscription information of the UE that are provided by the UE. Optionally, the procedure further includes a step, such as establishing a PDU session (namely, a packet data session between the UE and a core network user plane function entity, for example, a gateway).

[0212] 4. The 5G AN sends, to the UE, a registration accept message Registration Accept received from the 5G core network function entity.

[0213] The Registration Accept may be a 5G registration accept message. Corresponding to step 2, the Registration Accept may include a 5G initial registration (Initial Registration)/attach accept (Attach Accept) message or a 5G tracking area update accept (Tracking Area Update Accept) message. The Registration Accept carries parameters, such as description information of a 5G NSI accepted (in other words, the terminal is allowed to access, or selected for the terminal) by the network. Optionally, the Registration Accept further carries 4G DCN description information corresponding to the 5G NSI description information.

[0214] 5. The UE updates or stores the 5G NSI description information and the corresponding 4G DCN description information based on the 5G NSI description information and the corresponding 4G DCN description information that are carried in the registration accept message Registration Accept.

[0215] Optionally, if the Registration Accept carries the 5G NSI description information and the corresponding 4G DCN description information, the UE updates the locally configured/stored mapping relationship between the 5G NSI description information and the 4G DCN description information based on the 5G NSI description information and the corresponding 4G DCN description information that are carried in the Registration Accept.

[0216] 6. Establish a PDU session between the UE and the 5G network.

[0217] Specifically, the UE sends a session establishment request message (PDU session establishment request) to the 5G network. The PDU session establishment request message carries parameters, such as the first identifier (for example, the IMSI or the temporary identity of the 5G UE) of the UE, and the description information of the 5G NSI with which the UE requests to establish the session. Herein, the description information of the 5G NSI with which the UE requests to establish the session indicates that the session is established in the 5G NSI identified/described by the 5G NSI description information. The 5G core network function entity selects, based on the session establishment request message, the 5G NSI for establishing the session for the terminal, allocates a user plane function entity in the 5G NSI, and sends a session establishment accept (PDU session establishment accept) message to the terminal through the 5G access network. The session establishment accept message may carry the corresponding 4G DCN description information, of the 4G network, to which the 5G NSI description information is mapped.

[0218] Optionally, step 6 may be performed in step 3, in other words, the UE simultaneously establishes the PDU session in the registration procedure. In this case, the session establishment request message may be sent by the UE to the 5G network together with the registration request message. The session establishment accept message may also be sent to the UE by the network together with the registration accept message.

[0219] 7. The UE discovers the 4G network by measuring a cell signal, and determines to move or be handed over to the 4G network.

[0220] 8. The UE determines, based on description information of a currently registered 5G NSI and the configured/stored mapping relationship between the 5G NSI description information and the 4G DCN description information, 4G DCN description information used when the UE moves or is handed over to the 4G network.

[0221] 9. The UE sends an attach request message Attach Request to the 4G network.

[0222] The Attach Request may be a 4G registration/attach request message or a tracking area update request (Tracking Area Update Request) message. The Attach Request may further carry parameters, such as a second identifier of the UE (the second identifier may be the same as the first identifier in step 2, for example, may also be an IMSI, or may be different, for example, may be an old global unique temporary identity old GUTI of the UE in the 4G network), and the 4G DCN description information (for example, a DCN ID or a UE Usage Type) corresponding to the 5G NSI. If the UE is in connected mode (in other words, currently there is an active PDU session), the Attach Request further carries a handover indication handover indication, so as to instruct the PDN GW in the 4G network to assign, to the UE, an IP address that is the same as an IP address of the PDU session activated in the 5G network.

[0223] Correspondingly, if the UE is in connected mode (in other words, currently there is an active active PDU session), the Attach Request may further carry a session identifier of the session, and carries the 4G DCN description information corresponding to the description information of the 5G NSI with which the UE establishes the session, so that the session is changed to a corresponding DCN of the 4G network, or the session is re-established in a DCN of the 4G network.

[0224] 10-13. If a 4G RAN (an eNB or an evolved eNB) supports an eDecor/Decor (namely, an enhanced dedicated core network or a dedicated core network) and identifies the 4G DCN description information, for example, a DCN ID, in the Attach Request (or a Tracking Area Update Request), the 4G RAN (for example, the eNB or the evolved eNB) determines a DCN identified by the DCN ID, sends the Attach Request (or the Tracking Area Update Request) to an MME that supports the DCN, and the MME continues to process the Attach Request of the UE.

[0225] If the 4G RAN supports the eDecor/Decor but does not identify the 4G DCN description information, for example, the DCN ID or the UE Usage Type, in the Attach Request (or the Tracking Area Update Request), the 4G RAN ignores the DCN ID or the UE Usage Type, and sends the Attach Request (or the Tracking Area Update Request) to a default MME. The MME determines, based on the 4G DCN description information and the subscription information of the UE, whether the MME is capable of serving the UE. If the MME is capable of serving the UE, the MME continues to process the Attach Request of the UE (for example, sends a create session request Create Session Request to the S-GW). If the MME is incapable of serving the UE, the MME performs a rerouting procedure (step 12), to be specific, the MME sends information (for example, a new MME group identifier (MME Group ID, MMEGI)) about a DCN that serves the UE to the 4G RAN, and the RAN selects a new MME based on at least the MMEGI and sends the Attach Request to the MME to continue the registration procedure of the UE in the DCN.

[0226] If the 4G network (for example, the RAN and/or the MME) does not support the eDecor, the 4G network ignores the eDecor and continues to perform the registration procedure of the UE in the 4G network.

[0227] 14. The 4G RAN sends, to the UE, the Attach Accept or the Tracking Area Update Accept received from the MME.

[0228] If the 4G RAN (for example, the eNB or the evolved eNB) supports the eDecor (that is, supports an enhanced dedicated core network selection procedure), and the Attach Accept or the Tracking Area Update Accept carries parameters, such as the description information (for example, the DCN ID) of the 4G DCN that is accepted by the 4G network (in other words, the terminal is allowed to access, or selected for the terminal); optionally the Attach Accept or the Tracking Area Update Accept further carries the 5G NSI description information corresponding to the 4G DCN description information. Optionally, the Attach Request or the Tracking Area Update Request carries the handover indication, and the MME may not provide, according to the handover indication, the 5G NSI description information corresponding to the 4G DCN description information, in other words, may not perform step 14.

[0229] Optionally, step 15 may be further performed.

[0230] 15. If the Attach Accept (or the Tracking Area Update Accept) carries the 4G DCN description information and the corresponding 5G NSI description information, optionally the UE updates the locally configured or stored 4G DCN description information and the corresponding 5G NSI description information based on the 4G DCN description information and the corresponding 5G NSI description information that are carried in the Attach Accept (or the Tracking Area Update Accept).

[0231] FIG. 8A and FIG. 8B are a schematic flowchart of handing over UE from a 4G network to a 5G network according to an embodiment of the present invention. As shown in FIG. 8, registering or handing over the UE from the 4G network to the 5G network may include the following steps.

[0232] 1. The UE reads a mapping relationship between 5G NSI description information and 4G DCN description information from a pre-configuration or a broadcast message.

[0233] For example, the pre-configuration includes the mapping relationship between the 5G NSI description information and the 4G DCN description information. Alternatively, the UE may read the mapping relationship between the 5G NSI description information and the 4G DCN description information from system information broadcast by the 4G network.

[0234] 2. The UE sends an Attach Request to the 4G network.

[0235] The Attach Request may be a registration/attach request message. The Attach Request may carry parameters, such as a third identifier (for example, an IMSI, or an old global unique temporary identity old GUTI of the UE in the 4G network, or a packet-temporary mobile subscriber identity P-TMSI) of the UE, and description information (for example, a DCN ID or a UE Usage Type) of a 4G DCN that the UE requests to access.

[0236] 3. Perform a 4G registration procedure.

[0237] The 4G registration procedure includes: A 4G network function entity (for example, an MME and/or a 4G RAN) performs steps, such as performing authentication on the UE, negotiating a security/encryption parameter, selecting a DCN and an MME for the UE based on the 4G DCN description information and subscription information of the UE that are provided by the UE, and establishing a PDN connection and a default bearer of the PDN connection.

[0238] The step of establishing the PDN connection and the default bearer of the PDN connection in the registration procedure specifically includes: The UE sends a PDN connection establishment request message (PDN Connectivity Request) to the 4G network, where the message carries parameters, such as the third identifier of the UE and the description information of the 4G DCN with which the UE requests to establish the PDN connection. Herein, the description information of the 4G DCN with which the UE requests to establish the PDN connection indicates that the PDN connection is established in the 4G DCN identified/described by the 4G DCN description information. A 4G core network function entity selects, for the terminal based on the PDN connection establishment request message, the DCN and the MME for establishing a session, and sends a PDN connection establishment accept message (PDN Connectivity Accept) to the terminal through a 4G access network. The PDN connection establishment accept message may carry the corresponding 5G NSI description information, of the 5G network, to which the 4G DCN description information is mapped. Herein, the PDN connection establishment request message is sent by the UE to the 4G network together with a registration request message. The PDN connection establishment accept message may also be sent to the UE by the 4G network together with a registration accept message.

[0239] After the registration is completed, the UE may initiate an independent PDN connection establishment procedure to the 4G network. The specific procedure is the same as above.

[0240] 4. The 4G RAN (that is, an eNB or an evolved eNB) sends, to the UE, Attach Accept (a registration accept message) received from the MME.

[0241] The Attach Accept carries parameters, such as the description information (for example, the DCN ID) of the 4G DCN accepted (in other words, the terminal is allowed to access, or selected for the terminal) by the 4G network. Optionally, the Attach Accept further carries the 5G NSI description information (for example, a Slice/Service Type, an NSI ID, or a corresponding S-NSSAI or NSSAI) corresponding to the 4G DCN description information. If step 1 is performed, this parameter is optional.

[0242] 5. The UE stores the 4G DCN description information and the corresponding 5G NSI description information based on the 4G DCN description information and the corresponding 5G NSI description information that are carried in the Attach Accept.

[0243] Optionally, if the Attach Accept carries the 4G DCN description information and the corresponding 5G NSI description information, the UE updates the locally configured/stored 4G DCN description information and the 5G NSI description information based on the 4G DCN description information and the corresponding 5G NSI description information that are carried in the Attach Accept.

[0244] 6. The UE discovers the 5G network by measuring a cell signal, and determines to move or be handed over to the 5G network.

[0245] 7. The UE determines, based on description information of a currently registered 4G DCN and the configured/stored 4G DCN description information and the corresponding 5G NSI description information, corresponding 5G NSI description information used when the UE moves or is handed over to the 5G network.

[0246] 8. The UE sends a Registration Request to the 5G network.

[0247] The Registration Request may be a 5G initial registration (Initial Registration)/attach request (Attach Request) message or a 5G tracking area update request (Tracking Area Update Request) message. The Registration Request carries parameters, such as a fourth identifier (for example, an IMSI or a temporary identity of the 5G UE) of the UE, and the 5G NSI description information corresponding to the 4G DCN description information. If the UE is in connected mode (in other words, currently there is an active active PDN connection), the Registration Request further carries a handover indication handover indication, so as to instruct a user plane function entity (for example, a gateway) in the 5G network to assign, to the UE, an IP address that is the same as an IP address of the PDN connection activated in the 4G network.

[0248] If the UE is in connected mode (in other words, currently there is an active active PDN connection), the Registration Request may further carry an identifier of the PDN connection, and carries the 5G NSI description information corresponding to the description information of the 4G DCN with which the UE establishes the PDN connection, so that the PDN connection is changed to a corresponding NSI of the 5G network, or the PDN connection is re-established in an NSI of the 5G network. The identifier of the PDN connection may be represented by using an identifier (a default bearer ID) of a default bearer of the PDN connection.

[0249] 9-12. Perform a 5G registration procedure.

[0250] The 5G registration procedure includes: A 5G core network function entity performs steps, such as performing authentication on the UE, negotiating a security/encryption parameter, and selecting the NSI for the UE based on description information of the 5G NSI and the subscription information of the UE that are provided by the UE. Optionally, the procedure further includes a step, such as establishing a PDU session (namely, a packet data session between the UE and a core network user plane function entity, for example, a gateway).

[0251] Specifically, if a 5G AN cannot select, based on the 5G NSI description information provided by the UE, an S-CCNF entity that serves the UE, the following steps 9a-12 are performed; otherwise, steps 9b-12 are performed.

[0252] 9a. The 5G AN forwards the Registration Request to a default CCNF entity.

[0253] Optionally, the 5G AN may forward the Registration Request to the default CCNF entity (or a default AMF or NSSF entity, and the default AMF or NSSF entity is also used hereinafter, in other words, the default CCNF entity in the following steps may also be an AMF or NSSF entity in the default CCNF entity (when the S-CCNF entity is selected).

[0254] Herein, the default CCNF entity is a CCNF entity used by default. When the 5G AN cannot select, based on the 5G NSI description information provided by the UE, the S-CCNF entity (that is, a serving CCNF entity) that serves the UE, the 5G AN sends the Registration Request to the default CCNF entity.

[0255] 10a. The default CCNF entity selects the S-CCNF entity for the UE based on the 5G NSI description information in the Registration Request and the subscription information of the UE.

[0256] 11a. The default CCNF entity forwards the Registration Request to the S-CCNF entity.

[0257] Optionally, the default CCNF entity forwards the Registration Request to a serving AMF entity. The serving AMF entity is also used hereinafter. In other words, the S-CCNF entity in the following steps may be the AMF entity in the S-CCNF entity.

[0258] Optionally, the default CCNF entity sends S-CCNF information (for example, an S-CCNF identifier or an S-CCNF group identifier) to the 5G AN, and the 5G AN selects the S-CCNF entity based on the S-CCNF information and forwards the Registration Request to the S-CCNF entity.

[0259] 9b. The 5G AN selects the S-CCNF entity based on the 5G NSI description information (for example, an S-NSSAI) in the Registration Request.

[0260] 10b. The 5G AN forwards the Registration Request to the S-CCNF entity.

[0261] 11. The S-CCNF entity selects a specific network slice for the UE based on the 5G NSI description information in the Registration Request and the subscription information of the UE.

[0262] 12. The UE establishes a 5G PDU session with the 5G network.

[0263] For example, when the UE in connected mode is handed over, the 4G PDN connection established between the UE and the 5G network is changed to the corresponding 5G PDU session after the UE is handed over to the 5G network. An IP address of the PDU session is the same as an IP address of the 4G PDN connection before the handover.

[0264] 13. The 5G AN sends, to the UE, Registration Accept received from the 5G core network function entity.

[0265] The Registration Accept carries parameters, such as the description information of the 5G NSI accepted (in other words, the terminal is allowed to access, or selected for the terminal) by the network. Optionally, the Registration Accept further carries the 4G DCN description information corresponding to the 5G NSI description information. Optionally, the Registration Request carries the handover indication, and the 5G core network function entity may not provide, according to the handover indication, the 4G DCN description information corresponding to the 5G NSI description information.

[0266] 14. The UE updates the locally configured/stored 5G NSI description information and the corresponding 4G DCN description information based on the 5G NSI description information and the corresponding 4G DCN description information that are carried in the Registration Accept.

[0267] Step 14 may be performed when the Registration Accept carries the 5G NSI description information and the corresponding 4G DCN description information.

[0268] FIG. 9, including FIG. 9A and FIG. 9B is a schematic flowchart of handover preparations for handing over UE from a 5G network to a 4G network according to an embodiment of the present invention. In a handover preparation procedure shown in FIG. 9, the 5G network provides NSI/DCN description information for the 4G network, so that the 4G network selects a correct DCN.

[0269] A (default/serving) CCNF entity may be co-located or combined with an MME (co-located or combined, in other words, one physical entity has functions of two or more logical function entities). A session management function (Session Management Function, SMF) entity in a network slice instance (NSI) may be co-located or combined with an S-GW control plane function entity SGW-c or a P-GW control plane function entity PGW-c. A UP may be co-located or combined with an S-GW user plane function entity or a P-GW user plane function entity. The default CCNF entity may also be an AMF or NSSF entity in the default CCNF entity (when an S-CCNF entity is selected). The S-CCNF entity may also be an AMF entity in the S-CCNF entity.

[0270] Specifically, when the UE is handed over from the 5G network to the 4G network, the handover preparation (Handover preparation) phase (actually starting from step 6) may include the following steps.

[0271] 1. The UE sends a Registration Request to the 5G network.

[0272] The Registration Request may be a 5G registration request message and may include a 5G initial registration/attach request message Initial Registration/Attach Request or a 5G tracking area update request message Tracking Area Update Request. The Registration Request carries parameters, such as a first identifier (for example, an IMSI or a temporary identity of the 5G UE) of the UE, and description information of a 5G NSI to which the UE requests to access.

[0273] 2. Perform a 5G registration procedure.

[0274] The 5G registration procedure includes: A 5G core network function entity reforms steps, such as performing authentication on the UE, negotiating a security/encryption parameter, and selecting the NSI for the UE based on the description information of the 5G NSI and subscription information of the UE that are provided by the UE. Optionally, the procedure further includes a step, such as establishing a PDU session (namely, a packet data session between the UE and a core network user plane function entity, for example, a gateway).

[0275] 3. A 5G AN sends, to the UE, Registration Accept received from the 5G core network function entity S-CCNF.

[0276] The 5G AN may be a 5G access network node (Access Network Node, AN) or an access node (Access Node, AN). Corresponding to step 1, the Registration Accept may include the 5G initial registration/attach accept message Initial Registration/Attach Accept or the 5G tracking area update accept message Tracking Area Update Accept. The Attach Accept carries parameters, such as description information of a 5G NSI accepted (in other words, the terminal is allowed to access, or selected for the terminal) by the network.

[0277] The core network function entity S-CCNF is a serving common control network function (Serving-Common Control Network Function, S-CCNF) entity that is currently serving the UE. The CCNF entity may include an access and mobility management function (Access and Mobility Management Function, AMF) entity, an authentication server function (Authentication Server Function, AUSF) entity, and the like.

[0278] 4. Establish a PDU session between the UE and the 5G network.

[0279] Specifically, the UE sends a session establishment request (PDU session establishment request) message to the 5G network. The PDU session establishment request message carries parameters, such as the first identifier (for example, the IMSI or the temporary identity of the 5G UE) of the UE, and the description information of the 5G NSI with which the UE requests to establish the session. Herein, the description information of the 5G NSI with which the UE requests to establish the session indicates that the session is established in the 5G NSI identified/described by the 5G NSI description information. The 5G core network function entity selects, for the terminal based on the session establishment request message, the 5G NSI for establishing the session, allocates a user plane function entity in the 5G NSI, and sends a session establishment accept (PDU session establishment accept) message to the terminal through the 5G access network. The session establishment accept message may carry corresponding 4G DCN description information, of the 4G network, to which the 5G NSI description information is mapped.

[0280] Optionally, this step may be performed in step 2, in other words, the UE simultaneously establishes the PDU session in the registration procedure. In this case, the session establishment request message may be sent by the UE to the 5G network together with the registration request message. The session establishment accept message may also be sent to the UE by the network together with the registration accept message.

[0281] 5. The UE reports a measurement report to the 5G AN.

[0282] The measurement report may include signal measurement information of a serving cell and/or a neighboring cell, or the like.

[0283] 6. The 5G AN determines, based on the measurement report sent by the UE, to initiate a procedure of handing over the UE to the 4G network.

[0284] 7. The 5G AN sends a handover request message (Handover Required) to the serving CCNF entity.

[0285] The handover request message carries parameters, such as a UE identifier UE NG2 ID of an NG2 interface (the UE NG2 ID is used to uniquely identify the UE by the 5G AN and a core network control plane function entity), a target 4G access network node identifier Target 4G AN ID, a transparent container Source to Target Transparent Container sent by a source access network node to a target access network node (the Source to Target Transparent Container carries a radio resource parameter allocated by the source access network node to the UE, and the like).

[0286] 8. The S-CCNF entity selects a 4G DCN based on the 5G NSI description information of the UE and mapping information between (locally configured) 5G NSI description information and 4G DCN description information, and selects an MME that supports the DCN.

[0287] 9. The S-CCNF entity sends a forwarding relocation request message (Forward Relocation Request) to a session management function (Session Management Function, SMF) entity of a network slice NS that serves the terminal.

[0288] The Forward Relocation Request carries parameters, such as a DCN ID (an identifier of the DCN selected by the S-CCNF entity), an MME ID (an identifier of the MME supporting the DCN), a UE MM context (a context related to UE mobility management Mobility Management), the UE identifier (for example, the IMSI), a Target 4G AN ID, and a Source to Target Transparent Container, and the like.

[0289] The forwarding relocation request message may further carry a session identifier of the PDU session that the UE has established or activated (active) in the 5G network, and carries the 4G DCN description information (namely, the foregoing DCN ID) corresponding to the 5G NSI description information for establishing the PDU session, so that the PDU session is changed to the corresponding DCN of the 4G network, or the PDU session (corresponding to a PDN connection) is re-established in the 4G DCN.

[0290] 10. The SMF entity determines the MME based on the MME ID in the Forward Relocation Request and sends the Forward Relocation Request to the MME. The Forward Relocation Request carries parameters, such as the DCN ID (the identifier of the DCN selected by the S-CCNF entity), the UE MM context (the context related to UE mobility management Mobility Management), and a UE SM context (a context related to UE session management Session Management), for example, information about the PDU session that the UE establishes in the 5G network, the UE identifier (for example, the IMSI), the Target 4G AN ID, and the Source to Target Transparent Container.

[0291] The forwarding relocation request message may further carry the session identifier of the PDU session that the UE has established or activated (active) in the 5G network, and carries the 4G DCN description information (namely, the foregoing DCN ID) corresponding to the 5G NSI description information for establishing the PDU session, so that the PDU session is changed to the corresponding DCN of the 4G network, or the PDU session (corresponding to the PDN connection) is re-established in the 4G DCN.

[0292] If the S-CCNF entity has stored the UE SM context, steps 9 and 10 may be combined into the following step: The S-CCNF entity directly sends the Forward Relocation Request to the MME. The Forward Relocation Request carries parameters, such as the DCN ID (the identifier of the DCN selected by the S-CCNF entity), the UE MM context (the context related to UE mobility management Mobility Management), the UE SM context (the context related to UE session management Session Management), for example, the information about the PDU session that the UE establishes in the 5G network, the UE identifier (for example, the IMSI), the Target 4G AN ID, and the Source to Target Transparent Container. The forwarding relocation request message may further carry the session identifier of the PDU session that the UE has established or activated (active) in the 5G network, and carries the 4G DCN description information (namely, the foregoing DCN ID) corresponding to the 5G NSI description information for establishing the PDU session, so that the PDU session is changed to the corresponding DCN of the 4G network, or the PDU session (corresponding to the PDN connection) is re-established in the 4G DCN.

[0293] 11. The MME determines the DCN based on the DCN ID in the received Forward Relocation Request, and selects a packet data network gateway (Packet Data Network Gateway, PDN GW) and a 4G serving gateway (Serving Gateway, S-GW) that support the DCN. In addition, the MME maps the 5G UE MM context and the UE SM context to a 4G UE context (including a packet data network connection PDN connection, a 4G evolved packet system bearer EPS bearer information, and the like).

[0294] 12. The MME sends a Create Session Request to the S-GW, where the Create Session Request carries parameters, such as the UE identifier (for example, the IMSI), an MME address, a tunnel endpoint identifier TEID, and a PDN GW address.

[0295] 13. The S-GW allocates, based on the Create Session Request, a local resource (for example, an S-GW address of the 4G PDN connection/EPS bearer (that is established to the PDN GW and that corresponds to the 5G PDU session after the 5G PDU session is changed to the 4G network) and a TEID of the S-GW), and sends a Create Session Response to the MME, where the Create Session Response carries parameters, such as the S-GW address and the TEID.

[0296] 14. The MME sends a Handover Request to a 4G AN, where the Handover Request carries parameters, such as an MME UE S1AP ID (an identifier of an S1-AP interface allocated by the MME to the UE, and the S1-AP interface is an interface between the MME and an eNB/evolved eNB), the Source to Target Transparent Container, and the DCN ID.

[0297] 15. The 4G AN returns a handover request acknowledgment message Handover Request ACK to the MME, where the handover request acknowledgment message carries parameters, such as the MME UE S1AP ID, an eNB UE S1AP ID (an S1-AP interface identifier allocated by the eNB/evolved eNB to the UE), and a Target to Source Transparent Container.

[0298] 16. The MME sends a forwarding relocation response message Forward Relocation Response to the SMF entity, where the forwarding relocation response message carries parameters, such as a list of established 4G EPS bearers, a list of established radio access bearers (Radio Access Bearer, RAB), an MME TEID, and the Target to Source Transparent Container.

[0299] 17. The SMF entity forwards the Forward Relocation Response to the S-CCNF entity.

[0300] Herein, if the S-CCNF entity has stored the UE SM context, steps 16 and 17 may be combined into the following step: The MME directly sends the Forward Relocation Response to the S-CCNF entity, where the Forward Relocation Response carries parameters, such as the list of established 4G EPS bearers, the list of established radio access bearers (Radio Access Bearer, RAB), the MME TEID, and the Target to Source Transparent Container.

[0301] FIG. 10, including FIG. 10A and FIG. 10B are a schematic flowchart of a handover execution (Handover execution) phase for handing over UE from a 5G network to a 4G network based on the handover preparations shown in FIG. 9 according to an embodiment of the present invention. The handover execution phase includes the following steps.

[0302] 1. An S-CCNF entity (or AMF entity, and the AMF entity is also used hereinafter) entity sends a handover command message Handover Command to a 5G AN.

[0303] The Handover Command carries parameters, such as a Target to Source Transparent Container and a list of to-be-released RABs.

[0304] 2. The 5G AN sends the Handover Command to the UE.

[0305] The Handover Command carries parameters, such as a radio resource allocated by a target access network node (that is, a 4G AN) to the UE.

[0306] 3. The UE performs a 4G access procedure according to the Handover Command.

[0307] 4. The UE sends Handover to E-UTRAN Complete (a handover to E-UTRAN complete message) to the 4G AN.

[0308] 5. The 4G AN sends a handover notification message Handover Notify to an MME.

[0309] 6. The MME sends a forwarding relocation complete notification message Forward Relocation Complete Notification to a 5G SMF entity.

[0310] 7. The SMF entity sends the Forward Relocation Complete Notification to the S-CCNF entity.

[0311] If steps 9 and 10 are combined and steps 16 and 17 are combined in the handover preparation procedure in FIG. 9, steps 6 and 7 in the handover execution procedure herein are combined into the following step: The MME directly sends the forwarding relocation complete notification message Forward Relocation Complete Notification to the 5G S-CCNF entity.

[0312] 8. The S-CCNF entity returns a Forward Relocation Complete ACK (a forwarding relocation complete acknowledgment message) to the SMF entity.

[0313] 9. The SMF entity returns the Forward Relocation Complete ACK to the MME.

[0314] If steps 6 and 7 are combined, steps 8 and 9 herein are combined into the following step: The S-CCNF entity returns the Forward Relocation Complete ACK to the MME.

[0315] 10. The MME sends a modify bearer request message Modify Bearer Request to an S-GW.

[0316] 11. The S-GW returns a modify bearer response message Modify Bearer Response to the MME.

[0317] 12. The UE initiates a tracking area update (Tracking Area Update, TAU) procedure to the MME.

[0318] 13. The S-CCNF entity sends a delete session request message Delete Session Request to the SMF entity.

[0319] 14. The SMF entity releases a 5G PDU session resource of the UE.

[0320] 15. The SMF entity returns a delete session response message Delete Session Response to the S-CCNF entity.

[0321] If step 6 is performed (that is, steps 6 and 7 are not combined), steps 13 and 15 herein may not be performed, and step 14 may be performed after step 6.

[0322] 16. The S-CCNF entity sends an NG2 release command message Release Command to the 5G AN.

[0323] 17. The 5G AN sends an NG2 release complete message Release Completion to the S-CCNF entity.

[0324] FIG. 11A, FIG. 11B, and FIG. 11C are a schematic flowchart of handover preparations for handing over UE from a 4G network to a 5G network according to an embodiment of the present invention. In a handover preparation procedure shown in FIG. 11, the 4G network provides NSI description information for the 5G network, so that the 5G network selects a correct NSI. A default CCNF entity described below may also be an AMF or NSSF entity in the default CCNF entity (when an S-CCNF entity is selected). The S-CCNF entity may also be an AMF entity in the S-CCNF entity. The handover preparation (Handover preparation) phase (actually starting from step 6) includes the following steps.

[0325] 1. The UE sends an attach request message Attach Request to the 4G network.

[0326] The Attach Request carries parameters, such as a third identifier (for example, an IMSI or a temporary identity old GUTI or P-TMSI of the UE) of the UE, and description information (for example, a DCN ID or a UE Usage Type) of a 4G DCN that the UE requests to access.

[0327] That the UE sends the Attach Request to the 4G network may be: The UE sends the Attach Request to a 4G AN and then the 4G AN sends the Attach Request to an MME.

[0328] 2. Perform a 4G registration procedure.

[0329] The 4G registration procedure includes: A 4G network function entity (for example, an MME and/or a 4G RAN) performs steps, such as performing authentication on the UE, negotiating a security/encryption parameter, selecting the DCN and the MME for the UE based on the 4G DCN description information and subscription information of the UE that are provided by the UE, and establishing a PDN connection and a default bearer of the PDN connection.

[0330] The step of establishing the PDN connection and the default bearer of the PDN connection in the registration procedure specifically includes: The UE sends a PDN connection establishment request message (PDN Connectivity Request) to the 4G network, where the PDN connection establishment request message carries parameters, such as the third identifier of the UE and the description information of the 4G DCN with which the UE requests to establish the PDN connection. Herein, the description information of the 4G DCN with which the UE requests to establish the PDN connection indicates that the PDN connection is established in the 4G DCN identified/described by the 4G DCN description information. A 4G core network function entity selects, for the terminal based on the PDN connection establishment request message, the DCN and the MME for establishing a session, and sends a PDN connection establishment accept message (PDN Connectivity Accept) to the terminal through a 4G access network. The PDN connection establishment accept message may carry corresponding 5G NSI description information, of the 5G network, to which the 4G DCN description information is mapped. Herein, the PDN connection establishment request message is sent by the UE to the 4G network together with a registration request message. The PDN connection establishment accept message may also be sent to the UE by the 4G network together with a registration accept message.

[0331] After the registration is completed, the UE may initiate an independent PDN connection establishment procedure to the 4G network. The specific procedure is the same as above.

[0332] 3. The 4G AN (that is, an eNB or an evolved eNB) sends, to the UE, Attach Accept (a registration accept message) received from the MME.

[0333] The Attach Accept carries parameters, such as the description information (for example, the DCN ID) of the 4G DCN accepted (in other words, the terminal is allowed to access, or selected for the terminal) by the 4G network.

[0334] 4. Optionally, the UE establishes another PDN connection to the 4G network.

[0335] 5. The UE reports a measurement report to the 4G AN. The measurement report includes signal measurement information of a serving cell and/or a neighboring cell, or the like.

[0336] 6. The 4G AN determines, based on the measurement report sent by the UE, to initiate a procedure of handing over the UE to the 5G network.

[0337] 7. The 4G AN sends a handover request message Handover Required to the MME, where the handover request message carries parameters, such as an MME UE S1AP ID, an eNB UE S1AP ID, a target 5G access network node identifier Target 5G AN ID, and a Source to Target Transparent Container.

[0338] If the MME cannot determine the S-CCNF entity of the UE in the 5G network, the MME performs the following steps 8a to 10a; otherwise, performs the following steps 8b to 10b.

[0339] 8a. The MME sends a Forward Relocation Request to a default 5G CCNF entity, where the Forward Relocation Request carries the description information (for example, the DCN ID or the UE Usage Type) of the 4G DCN, the UE identifier (for example, the IMSI), the target 5G AN ID, a UE context (the UE context includes information about the PDN Connection and an EPS bearer, and the like), and the Source to Target Transparent Container. Herein, the default CCNF entity is a CCNF entity used by default. When the MME cannot determine that the S-CCNF entity of the UE in the 5G network, the MME sends the Forward Relocation Request to the default CCNF entity.

[0340] The Forward Relocation Request may further carry an identifier of the PDN connection that the UE has established or activated (active) in the 4G network, and carries the 4G DCN description information (namely, the foregoing DCN ID or UE Usage Type) for establishing the PDN connection, so as to instruct the S-CCNF entity to change the PDN connection to the corresponding NSI of the 5G network, or the PDN connection (a corresponding PDU Session) is re-established in the 5G NSI.

[0341] 9a. The default CCNF entity selects the 5G S-CCNF entity based on the 4G DCN description information of the UE in the Forward Relocation Request and mapping information between the 5G NSI and the 4G DCN.

[0342] 10a. The default CCNF entity sends the Forward Relocation Request to the S-CCNF entity, where the Forward Relocation Request carries parameters, such as the 4G DCN description information (for example, the DCN ID or the UE Usage Type), the corresponding 5G NSI description information, an MME ID, the UE identifier (for example, the IMSI), the Target 5G AN ID, the UE context, and the Source to Target Transparent Container.

[0343] The Forward Relocation Request may further carry the identifier of the PDN connection that the UE has established or activated (active) in the 4G network, and carries the 4G DCN description information (namely, the foregoing DCN ID or UE Usage Type) for establishing the PDN connection, so as to instruct the S-CCNF entity to change the PDN connection to the corresponding NSI of the 5G network, or the PDN connection (the corresponding PDU Session) is re-established in the 5G NSI.

[0344] 11a. If the received Forward Relocation Request carries the 4G DCN description information, the S-CCNF entity selects a specific 5G network slice instance NSI based on the 4G DCN description information and mapping information between the 5G NSI description information and the 4G DCN description information, and selects an SMF entity in the NSI. Alternatively, if the received Forward Relocation Request carries the 5G NSI description information, the S-CCNF entity selects a specific 5G network slice instance NSI based on the 5G NSI description information, and selects an SMF entity in the NSI. In addition, the S-CCNF entity maps information related to UE mobility management MM in the 4G UE context to a 5G UE MM context and maps an authentication/security parameter in the 4G UE context to a 5G UE authentication/security parameter for storing.

[0345] 8b. The MME selects the 5G S-CCNF entity based on the 4G DCN information of the UE and the mapping information between the 5G NSI description information and the 4G DCN description information.

[0346] 9b. The MME sends the Forward Relocation Request to the S-CCNF entity, where the Forward Relocation Request carries parameters, such as the 4G DCN description information (for example, the DCN ID or the UE Usage Type), the UE identifier (for example, the IMSI), the Target 5G AN ID, the UE context, and the Source to Target Transparent Container.

[0347] The Forward Relocation Request may further carry the identifier of the PDN connection that the UE has established or activated (active) in the 4G network, and carries the 4G DCN description information (namely, the foregoing DCN ID or UE Usage Type) for establishing the PDN connection, so as to instruct the S-CCNF entity to change the PDN connection to the corresponding NSI of the 5G network, or the PDN connection (the corresponding PDU Session) is re-established in the 5G NSI.

[0348] 10b. The S-CCNF entity selects the specific 5G network slice instance NSI based on the 4G DCN description information (for example, the DCN ID or the UE Usage Type) in the received Forward Relocation Request and the mapping information between the 5G NSI description information and the 4G DCN description information, and selects the SMF entity in the NSI. In addition, the S-CCNF entity maps the information related to UE mobility management MM in the 4G UE context to the 5G UE MM context and maps the authentication/security parameter in the 4G UE context to the 5G UE authentication/security parameter for storing.

[0349] 12. The S-CCNF entity sends a create session request message Create Session Request to the SMF entity in the selected NSI, where the create session request message carries parameters, such as the UE identifier (for example, the IMSI) and the 4G UE context (or information related to UE session management SM in the UE context).

[0350] 13. The SMF entity maps information (for example, the information about the PDN Connection and the EPS bearer) related to UE session management SM in the 4G UE context to a 5G UE SM context, and requests a 5G core network user plane function entity (for example, a gateway) to allocate a resource for establishing a 5G PDU session. The SMF entity sends a Create Session Response to the S-CCNF entity.

[0351] 14. The S-CCNF entity sends a Handover Request (a handover request message) to a 5G AN, where the Handover Request carries parameters, such as a UE NG2 ID, the Source to Target Transparent Container, and the 5G NSI description information.

[0352] 15. The 5G AN returns a Handover Request ACK (a handover request acknowledge message) to the S-CCNF entity, where the Handover Request ACK carries parameters, such as the UE NG2 ID and a Target to Source Transparent Container.

[0353] The 5G AN may select a 5G access network slice instance for the UE based on the 5G NSI description information and the Source to Target Transparent Container, and determine a radio resource.

[0354] 16. The S-CCNF entity sends a Forward Relocation Response (a forwarding relocation response message) to the MME, where the Forward Relocation Response carries parameters, such as a list of established PDU sessions and the Target to Source Transparent Container.

[0355] FIG. 12A and FIG. 12B are a schematic flowchart of a handover execution (Handover execution) phase for handing over UE from a 4G network to a 5G network based on the handover preparations shown in FIG. 11 according to an embodiment of the present invention. The handover execution phase includes the following steps.

[0356] 1. An MME sends a handover command message Handover Command to a 4G AN.

[0357] The Handover Command carries parameters, such as a Target to Source Transparent Container and a list of to-be-released RABs.

[0358] 2. The 4G AN sends a handover from E-UTRAN command message Handover from E-UTRAN Command to the UE.

[0359] The Handover from E-UTRAN Command carries parameters, such as a radio resource allocated by a target access network node (that is, a 5G AN) to the UE.

[0360] 3. The UE accesses the target 5G AN according to the Handover from E-UTRAN Command.

[0361] 4. The UE sends a Handover Complete (handover to 5G access network complete message) to the 5G AN.

[0362] 5. The 5G AN sends a handover notification message Handover Notify to an S-CCNF entity (or an AMF entity, and the AMF entity is also used hereinafter).

[0363] 6. The S-CCNF entity sends a forwarding relocation complete notification message Forward Relocation Complete Notification to the MME.

[0364] 7. The MME returns a forwarding relocation complete acknowledgment message Forward Relocation Complete ACK to the S-CCNF entity.

[0365] 8. The S-CCNF entity sends a modify bearer request message Modify PDU Session Request to an SMF entity in a network slice that serves the UE.

[0366] 9. The SMF entity returns a modify bearer response message Modify Bearer Response to the S-CCNF entity.

[0367] 10. The UE initiates a 5G tracking area update (Tracking Area Update, TAU) procedure to the MME.

[0368] 11. The MME sends a delete session request message Delete Session Request to an S-GW.

[0369] 12. The S-GW releases a 4G PDN Connection resource of the UE. The S-GW returns a delete session response message Delete Session Response to the MME.

[0370] 13. The MME sends a release resource command message Release Resources Command to the 4G AN, to request to release a radio resource allocated to the UE by the 4G AN.

[0371] 14. The 4G AN sends a release resource complete message Release Resources Complete to the MME.

[0372] FIG. 13 is a schematic diagram of a structure of an inter-network change apparatus according to an embodiment of the present invention. As shown in FIG. 13, the inter-network change apparatus 1300 may include the following modules: a determining module 1301, configured to determine second network slice information to which first network slice information is mapped, where the first network slice information is information about a first network slice accessed by the terminal, the second network slice information is information about a second network slice, the first network slice is a network slice in a first network, and the second network slice is a network slice in a second network; a sending module 1302, configured to send a request message to the second network, where the request message carries the second network slice information, and the request message is used for the terminal to request to register with or be handed over to the second network slice; and a receiving module 1303, configured to receive an accept message returned by the second network, where the accept message carries network slice information accepted by the second network, and the network slice information accepted by the second network includes a part or all of the second network slice information; where the first network and the second network have different access network devices and/or core network devices.

[0373] In an optional implementation, mapping information between the first network slice information and the second network slice information is pre-configured on the terminal.

[0374] In another optional implementation, the determining module 1301 is specifically configured to obtain, in a procedure of registering or establishing a session with the first network, the second network slice information to which the first network slice information of the first network is mapped.

[0375] In still another optional implementation, the determining module 1301 is specifically configured to obtain, from system information broadcast by the first network, the second network slice information to which the first network slice information is mapped.

[0376] The accept message further carries third network slice information to which the network slice information accepted by the second network is mapped, the third network slice information is information about a third network slice, and the third network slice is a network slice in the first network.

[0377] The first network slice is a network slice used by the terminal to establish a session in the first network, and the second network slice is a network slice used by the terminal to re-establish the session in the second network or a network slice used after the session is changed from the first network to the second network.

[0378] The request message further carries a session identifier that is used to identify a session, and the session is established in the first network slice and is re-established in the second network slice, or is changed from the first network slice to the second network slice.

[0379] The request message further carries a handover indication, and the handover indication is used to instruct the second network to assign, to the terminal, a session address that is the same as a session address assigned by the first network to the terminal.

[0380] It should be understood that the foregoing and other operations and/or functions of the modules in the inter-network change apparatus 1300 shown in FIG. 13 are used to implement corresponding procedures of any inter-network change method in FIG. 1 to FIG. 12. For brevity, details are not described herein again.

[0381] FIG. 14 is a schematic diagram of a structure of another inter-network change apparatus according to an embodiment of the present invention. As shown in FIG. 14, the inter-network change apparatus 1400 may include the following modules: a receiving module 1401, configured to receive a request message sent by a terminal, where the request message carries second network slice information to which the first network slice information is mapped, the first network slice information is information about a first network slice accessed by the terminal, the second network slice information is information about a second network slice, the first network slice is a network slice in a first network, and the second network slice is a network slice in a second network; a determining module 1402, configured to determine a second core network device, where the second core network device is a core network device in the second network slice; and a sending module 1403, configured to send the request message to the second core network device for processing, so as to perform a procedure in which the terminal registers with or is handed over to the second network; where the receiving module 1401 is further configured to receive an accept message returned by the second core network device, and send the accept message to the terminal, where the accept message carries network slice information accepted by the second network, and the network slice information accepted by the second network includes a part or all of the second network slice information.

[0382] That the determining module 1402 is configured to determine a second core network device, and the sending module is configured to send the request message to the second core network device for processing, so as to perform a procedure in which the terminal registers with or is handed over to the second network is specifically: forwarding the request message to a second default core network device in the second network, so that the second default core network device selects the second core network device and sends the request message to the second core network device for processing, so as to perform the procedure in which the terminal registers with or is handed over to the second network.

[0383] The accept message further carries third network slice information to which the network slice information accepted by the second network is mapped, the third network slice information is information about a third network slice, and the third network slice is a network slice in the first network.

[0384] The first network slice is a network slice used by the terminal to establish a session in the first network, and the second network slice is a network slice used by the terminal to re-establish the session in the second network or a network slice used after the session is changed from the first network to the second network.

[0385] The request message further carries a session identifier that is used to identify a session, and the session is established in the first network slice and is re-established in the second network slice, or is changed from the first network slice to the second network slice.

[0386] The request message further carries a handover indication, and the handover indication is used to instruct the second network to assign, to the terminal, a session address that is the same as a session address assigned by the first network to the terminal.

[0387] It should be understood that the foregoing and other operations and/or functions of the modules in the inter-network change apparatus 1400 shown in FIG. 14 are used to implement corresponding procedures of any inter-network change method in FIG. 1 to FIG. 12. For brevity, details are not described herein again.

[0388] FIG. 15 is a schematic diagram of a structure of still another inter-network change apparatus according to an embodiment of the present invention. The inter-network change apparatus 1500 may include the following modules: a receiving module 1501, configured to receive a first request message sent by a first access network device, where the first request message is used for a terminal to request to be handed over to a second network; a determining module 1502, configured to determine second network slice information to which first network slice information is mapped, where the first network slice information is information about a first network slice accessed by the terminal, the second network slice information is information about a second network slice, the first network slice is a network slice in a first network, and the second network slice is a network slice in the second network; where the determining module 1502 is further configured to determine a second core network device, where the second core network device is a core network device in the second network slice; a sending module 1503, configured to send a second request message to the second core network device, where the second request message carries the second network slice information; and a receiving module 1504 is further configured to receive a response message returned by the second core network device, and send a handover command to the terminal, so that the terminal is handed over to the second network slice.

[0389] The first network slice is a network slice used by the terminal to establish a session in the first network, and the second network slice is a network slice used by the terminal to re-establish the session in the second network or a network slice used after the session is changed from the first network to the second network.

[0390] The request message further carries a session identifier that is used to identify a session, and the session is established in the first network slice and is re-established in the second network slice, or is changed from the first network slice to the second network slice.

[0391] The request message further carries a handover indication, and the handover indication is used to instruct the second network to assign, to the terminal, a session address that is the same as a session address assigned by the first network to the terminal.

[0392] It should be understood that the foregoing and other operations and/or functions of the modules in the inter-network change apparatus 1500 shown in FIG. 15 are used to implement corresponding procedures of any inter-network change method in FIG. 1 to FIG. 12. For brevity, details are not described herein again.

[0393] FIG. 16 is a schematic diagram of a structure of still another inter-network change apparatus according to an embodiment of the present invention. The inter-network change apparatus 1600 may include the following modules: a receiving module 1601, configured to receive a first request message sent by a first core network device in a first network, where the first request message is used for a terminal to request to register with or be handed over to a second network, and the second default core network device is a core network device in the second network; a determining module 1602, configured to determine second network slice information to which first network slice information is mapped, where the first network slice information is information about a first network slice accessed by the terminal, the second network slice information is information about a second network slice, the first network slice is a network slice in the first network, and the second network slice is a network slice in the second network; where the determining module 1602 is further configured to determine a second core network device, where the second core network device is a core network device in the second network slice; and a sending module 1603, configured to send a second request message to the second core network device, where the second request message carries the second network slice information, and the request message is used for the terminal to request to register with or be handed over to the second network slice.

[0394] The first request message carries the first network slice information.

[0395] The first network slice is a network slice used by the terminal to establish a session in the first network, and the second network slice is a network slice used by the terminal to re-establish the session in the second network or a network slice used after the session is changed from the first network to the second network.

[0396] The second request message further carries a session identifier that is used to identify a session, and the session is established in the first network slice and is re-established in the second network slice, or is changed from the first network slice to the second network slice.

[0397] The second request message further carries a handover indication, and the handover indication is used to instruct the second network to assign, to the terminal, a session address that is the same as a session address assigned by the first network to the terminal.

[0398] It should be understood that the foregoing and other operations and/or functions of the modules in the inter-network change apparatus 1600 shown in FIG. 16 are used to implement corresponding procedures of any inter-network change method in FIG. 1 to FIG. 12. For brevity, details are not described herein again.

[0399] FIG. 17 is a schematic diagram of a structure of a terminal according to an embodiment of the present invention. As shown in FIG. 17, the terminal 1700 may include a processor 1701, a memory 1702, and a communications interface 1703. The communications interface 1703 is configured to implement communication connections between these components, and communication connections between machines. The memory 1702 may be a high-speed RAM memory, or may be a non-volatile memory (non-volatile memory), for example, at least one magnetic disk memory. The processor 1701 may be combined with the inter-network change apparatus shown in FIG. 13. The memory 1702 stores a group of program code, and the processor 1701 invokes the program code stored in the memory 1702 to perform the following operations: determining second network slice information to which first network slice information is mapped, where the first network slice information is information about a first network slice accessed by the terminal, the second network slice information is information about a second network slice, the first network slice is a network slice in a first network, and the second network slice is a network slice in a second network; sending a request message to the second network, where the request message carries the second network slice information, and the request message is used for the terminal to request to register with or be handed over to the second network slice; and receiving an accept message returned by the second network, where the accept message carries network slice information accepted by the second network, and the network slice information accepted by the second network includes a part or all of the second network slice information; where the first network and the second network have different access network devices and/or core network devices.

[0400] Mapping information between the first network slice information and the second network slice information is pre-configured on the terminal.

[0401] In this embodiment of the present invention, the processor 1701 invokes the program code stored in the memory 1702 to determine second network slice information to which first network slice information is mapped, and the processor 1701 may specifically perform the following operations: obtaining, by the terminal in a procedure of registering or establishing a session with the first network, the second network slice information to which the first network slice information of the first network is mapped.

[0402] In this embodiment of the present invention, the processor 1701 invokes the program code stored in the memory 1702 to determine second network slice information to which first network slice information is mapped, and the processor 1701 may specifically perform the following operations: obtaining, by the terminal from system information broadcast by the first network, the second network slice information to which the first network slice information is mapped.

[0403] The accept message further carries third network slice information to which the network slice information accepted by the second network is mapped, the third network slice information is information about a third network slice, and the third network slice is a network slice in the first network.

[0404] The first network slice is a network slice used by the terminal to establish a session in the first network, and the second network slice is a network slice used by the terminal to re-establish the session in the second network or a network slice used after the session is changed from the first network to the second network.

[0405] The request message further carries a session identifier that is used to identify a session, and the session is established in the first network slice and is re-established in the second network slice, or is changed from the first network slice to the second network slice.

[0406] The request message further carries a handover indication, and the handover indication is used to instruct the second network to assign, to the terminal, a session address that is the same as a session address assigned by the first network to the terminal.

[0407] It should be understood that the foregoing and other operations and/or functions of the modules in the terminal 1700 shown in FIG. 17 are used to implement corresponding procedures of any inter-network change method in FIG. 1 to FIG. 12. For brevity, details are not described herein again.

[0408] FIG. 18 is a schematic diagram of a structure of an inter-network change device according to an embodiment of the present invention. As shown in FIG. 18, the inter-network change device 1800 may include a processor 1801, a memory 1802, and a communications interface 1803. The inter-network change device 1800 is an access network device in a second network, and therefore may also be referred to as a second access network device 1800 below. The communications interface 1803 is configured to implement communication connections between these components, and communication connections between machines. The memory 1802 may be a high-speed RAM memory, or may be a non-volatile memory (non-volatile memory), for example, at least one magnetic disk memory. The processor 1801 may be combined with the inter-network change apparatus shown in FIG. 14. The memory 1802 stores a group of program code, and the processor 1801 invokes the program code stored in the memory 1802 to perform the following operations: receiving a request message sent by a terminal, where the second access network device 1800 is an access network device in a second network, the request message carries second network slice information to which the first network slice information is mapped, the first network slice information is information about a first network slice accessed by the terminal, the second network slice information is information about a second network slice, the first network slice is a network slice in a first network, and the second network slice is a network slice in the second network; determining a second core network device, where the second core network device is a core network device in the second network slice; sending the request message to the second core network device for processing, so as to perform a procedure in which the terminal registers with or is handed over to the second network; and receiving an accept message returned by the second core network device, and sending the accept message to the terminal, where the accept message carries network slice information accepted by the second network, and the network slice information accepted by the second network includes a part or all of the second network slice information.

[0409] In this embodiment of the present invention, that the processor 1801 invokes the program code stored in the memory 1802 to determine the second core network device and send the request message to the second core network device for processing, so as to perform the procedure in which the terminal registers with or is handed over to the second network may be specifically: forwarding the request message to a second default core network device in the second network, so that the second default core network device selects the second core network device and sends the request message to the second core network device for processing, so as to perform the procedure in which the terminal registers with or is handed over to the second network.

[0410] The accept message further carries third network slice information to which the network slice information accepted by the second network is mapped, the third network slice information is information about a third network slice, and the third network slice is a network slice in the first network.

[0411] The first network slice is a network slice used by the terminal to establish a session in the first network, and the second network slice is a network slice used by the terminal to re-establish the session in the second network or a network slice used after the session is changed from the first network to the second network.

[0412] The request message further carries a session identifier that is used to identify a session, and the session is established in the first network slice and is re-established in the second network slice, or is changed from the first network slice to the second network slice.

[0413] The request message further carries a handover indication, and the handover indication is used to instruct the second network to assign, to the terminal, a session address that is the same as a session address assigned by the first network to the terminal.

[0414] It should be understood that the foregoing and other operations and/or functions of the modules in the inter-network change device 1800 shown in FIG. 18 are used to implement corresponding procedures of any inter-network change method in FIG. 1 to FIG. 12. For brevity, details are not described herein again.

[0415] FIG. 19 is a schematic diagram of a structure of an inter-network change device according to an embodiment of the present invention. As shown in FIG. 19, the inter-network change device 1900 may include a processor 1901, a memory 1902, and a communications interface 1903. The inter-network change device 1900 is a core network device in a first network slice, and therefore may also be referred to as a first core network device 1900 below. The communications interface 1903 is configured to implement communication connections between these components, and communication connections between machines. The memory 1902 may be a high-speed RAM memory, or may be a non-volatile memory (non-volatile memory), for example, at least one magnetic disk memory. The processor 1901 may be combined with the inter-network change apparatus shown in FIG. 15. The memory 1902 stores a group of program code, and the processor 1901 invokes the program code stored in the memory 1902 to perform the following operations: receiving a first request message sent by a first access network device, where the first request message is used for a terminal to request to be handed over to a second network; determining second network slice information to which first network slice information is mapped, where the first network slice information is information about the first network slice accessed by the terminal, the second network slice information is information about a second network slice, the first network slice is a network slice in a first network, and the second network slice is a network slice in the second network; determining a second core network device, where the second core network device is a core network device in the second network slice; sending a second request message to the second core network device, where the second request message carries the second network slice information; and receiving a response message returned by the second core network device, and sending a handover command to the terminal, so that the terminal is handed over to the second network slice.

[0416] The first network slice is a network slice used by the terminal to establish a session in the first network, and the second network slice is a network slice used by the terminal to re-establish the session in the second network or a network slice used after the session is changed from the first network to the second network.

[0417] The request message further carries a session identifier that is used to identify a session, and the session is established in the first network slice and is re-established in the second network slice, or is changed from the first network slice to the second network slice.

[0418] The request message further carries a handover indication, and the handover indication is used to instruct the second network to assign, to the terminal, a session address that is the same as a session address assigned by the first network to the terminal.

[0419] It should be understood that the foregoing and other operations and/or functions of the modules in the inter-network change device 1900 shown in FIG. 19 are used to implement corresponding procedures of any inter-network change method in FIG. 1 to FIG. 12. For brevity, details are not described herein again.

[0420] FIG. 20 is a schematic diagram of a structure of an inter-network change device according to an embodiment of the present invention. As shown in FIG. 20, the inter-network change device 2000 may include a processor 2001, a memory 2002, and a communications interface 2003. The inter-network change device 2000 is a default core network device in a second network, and therefore may also be referred to as a second default core network device 2000 below. The communications interface 2003 is configured to implement communication connections between these components, and communication connections between machines. The memory 2002 may be a high-speed RAM memory, or may be a non-volatile memory (non-volatile memory), for example, at least one magnetic disk memory. The processor 2001 may be combined with the inter-network change apparatus shown in FIG. 16. The memory 2002 stores a group of program code, and the processor 2001 invokes the program code stored in the memory 2002 to perform the following operations: receiving a first request message sent by a first core network device in a first network, where the first request message is used for a terminal to request to register with or be handed over to a second network, and the second default core network device is a core network device in the second network; determining second network slice information to which first network slice information is mapped, where the first network slice information is information about a first network slice accessed by the terminal, the second network slice information is information about a second network slice, the first network slice is a network slice in the first network, and the second network slice is a network slice in the second network; determining a second core network device, where the second core network device is a core network device in the second network slice; and sending a second request message to the second core network device, where the second request message carries the second network slice information, and the request message is used for the terminal to request to register with or be handed over to the second network slice.

[0421] The first request message carries the first network slice information.

[0422] The first network slice is a network slice used by the terminal to establish a session in the first network, and the second network slice is a network slice used by the terminal to re-establish the session in the second network or a network slice used after the session is changed from the first network to the second network.

[0423] The second request message further carries a session identifier that is used to identify a session, and the session is established in the first network slice and is re-established in the second network slice, or is changed from the first network slice to the second network slice. The second request message further carries a handover indication, and the handover indication is used to instruct the second network to assign, to the terminal, a session address that is the same as a session address assigned by the first network to the terminal.

[0424] It should be understood that the foregoing and other operations and/or functions of the modules in the inter-network change device 2000 shown in FIG. 20 are used to implement corresponding procedures of any inter-network change method in FIG. 1 to FIG. 12. For brevity, details are not described herein again.

[0425] An embodiment of this application further provides a computer storage medium, configured to store a computer software instruction used by any terminal in FIG. 1 to FIG. 3. The computer software instruction includes a program designed to perform steps performed by the terminal in any inter-network change method in FIG. 1 to FIG. 12.

[0426] An embodiment of this application further provides a computer storage medium, configured to store a computer software instruction used by any access network device in FIG. 1 to FIG. 3. The computer software instruction includes a program designed to perform steps performed by the first access network device in any inter-network change method in FIG. 1 to FIG. 12.

[0427] An embodiment of this application further provides a computer storage medium, configured to store a computer software instruction used by any first core network device in FIG. 4 to FIG. 6. The computer software instruction includes a program designed to perform steps performed by the first core network device in any inter-network change method in FIG. 1 to FIG. 12.

[0428] An embodiment of this application further provides a computer storage medium, configured to store a computer software instruction used by any default core network device in FIG. 4 to FIG. 6. The computer software instruction includes a program designed to perform steps performed by the first core network device in any inter-network change method in FIG. 1 to FIG. 12.

[0429] A person of ordinary skill in the art may understand that all or some of the procedures of the methods in the embodiments may be implemented by a computer program instructing relevant hardware. The program may be stored in a computer readable storage medium. When the program runs, the procedures of the methods in the embodiments are performed.