Handover method, device, apparatus, and storage medium

Abstract

The present disclosure provides a handover method, a device, an apparatus, and a storage medium. The method comprises: a terminal selecting a target access network entity for handover on the basis of a service capability requirement of the terminal and service capability information of candidate access network entities; and sending a handover decision message to a source access network entity, the handover decision message comprising identification information of the target access network entity and service capability information of the target access network entity.

Description

Switching methods, equipment, devices and storage media

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411646466.9, filed on November 18, 2024, entitled “Switching Method, Apparatus, Device and Storage Medium”, which is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure relates to the field of wireless communication technology, and in particular to a switching method, device, apparatus, and storage medium. Background Technology

[0004] As a next-generation information service network, 6G (6th Generation Mobile Communication) technology is characterized by its ability to provide services beyond mere connectivity. Its network capabilities include ubiquitous connectivity, computing power, trusted security, sensing, data services, and AI-based intelligent network autonomy. Providing a more suitable handover mechanism for multi-element 6G service scenarios is a key technical challenge that needs to be addressed. Summary of the Invention

[0005] This disclosure provides a switching method, apparatus, device, and storage medium for providing a switching solution suitable for multi-element services.

[0006] In a first aspect, this disclosure provides a switching method applied to a terminal, comprising:

[0007] Based on the terminal's service capability requirements and the service capability information of candidate access network entities, select the target access network entity for handover.

[0008] A decision handover message is sent to the source access network entity. The decision handover message contains the identification information of the target access network entity and the service capability information of the target access network entity.

[0009] In some embodiments, the method further includes:

[0010] Receive broadcast messages sent by candidate access network entities, which contain service capability information of the candidate access network entities or indication information indicating the service capability information of the candidate access network entities.

[0011] In some embodiments, the service capability information includes capability information for providing a first service and service scope information for providing the first service. The first service includes at least one of connectivity service, data service, intelligent service, sensing service, and security service.

[0012] In some embodiments, the decision to switch messages may also include indications that allow split access and mobility management functions to be implemented.

[0013] Secondly, this disclosure also provides a handover method applied to a source access network entity, including:

[0014] Send a handover request message to the source access and mobility management function entity. The handover request message contains the terminal's connection session information and the terminal's data service management information; or,

[0015] A first handover request message is sent to the target access network entity. The first handover request message contains information on the data service capabilities that the target access network entity needs to have or perform.

[0016] In some embodiments, the method further includes:

[0017] The receiving terminal sends a handover decision message, which contains the identification information of the target access network entity and the service capability information of the target access network entity.

[0018] In some embodiments, the handover request message may also include the identification information of the target access network entity and the service capability information of the target access network entity.

[0019] In some embodiments, the method further includes:

[0020] Based on the terminal's service capability requirements and the service capability information of candidate access network entities, the target access network entity is selected.

[0021] In some embodiments, the decision to switch messages may also include indications that allow split access and mobility management functions to be implemented.

[0022] In some embodiments, the handover request message also includes indication information that allows split access and mobility management function entities to be permitted.

[0023] Thirdly, this disclosure also provides a handover method applied to a source access and mobility management function entity, including:

[0024] Receive a handover request message sent by the source access network entity. The handover request message contains the terminal's connection session information and the terminal's data service management information.

[0025] Based on the handover request message and the terminal's mobility restriction information, select the target access and mobility management function entity;

[0026] A Create UE Context Request message is sent to the target access and mobility management function entity. The Create UE Context Request message contains connection session information, data service management information, and mobility restriction information.

[0027] In some embodiments, the UE context creation request message may further include information about at least one network element among the service management function entity, session management function entity, and data management control function entity of the serving terminal.

[0028] In some embodiments, the handover request message may also include the identification information of the target access network entity and the service capability information of the target access network entity.

[0029] In some embodiments, the Create UE Context Request message may also include service capability information of the source access network entity and service capability information of the target access network entity.

[0030] In some embodiments, mobility restriction information includes restriction information on the terminal's use of a first service provided by the network and / or restriction information on the terminal's provision of a first service to the network, wherein the first service includes at least one of connectivity service, data service, intelligent service, sensing service, and security service.

[0031] In some embodiments, mobility restriction information includes RAT restriction information, prohibited area restriction information, service area restriction information, and network type restriction information.

[0032] In some embodiments, the method further includes:

[0033] Based on the service area restriction information and the service capability openness information of the terminal in the terminal's contract data, the service area restriction information of the terminal is determined.

[0034] In some embodiments, the service area restriction information includes a tracking area identifier associated with the service; or, the service area restriction information includes a tracking area identifier and service information.

[0035] In some embodiments, the handover request message also includes indication information that allows split access and mobility management function entities to be permitted.

[0036] In some embodiments, the target access and mobility management function entity is a split access and mobility management function entity.

[0037] Fourthly, this disclosure also provides a handover method applied to a target access and mobility management function entity, including:

[0038] Receive the Create UE Context Request message sent by the Source Access and Mobility Management Function Entity. The Create UE Context Request message contains the terminal's connection session information, the terminal's data service management information, and the terminal's mobility restriction information.

[0039] Based on mobility restriction information, determine the services the terminal can use after handover and / or the services the terminal can provide after handover, and perform any of the following operations based on connection session information and data service management information:

[0040] Send a service context update request message to the service management entity or session management entity;

[0041] Send a connection session context update request message to the session management function entity and a data service management context update request message to the data management control function entity.

[0042] In some embodiments, the method further includes:

[0043] Receive a service context update response message from a service management entity or a session management entity. This service context update response message contains user plane path information for the target user plane entity and data plane path information for the target data execution entity; or...

[0044] It receives a connection session context update response message sent by the session management function entity and a data service management context update response message sent by the data management control function entity. The connection session context update response message contains the user plane path information of the target user plane function entity, and the data service management context update response message contains the data plane path information of the target data execution function entity.

[0045] In some embodiments, the method further includes:

[0046] Send a second handover request message to the target access network entity. The second handover request message contains the user plane path information of the target user plane function entity and the data plane path information of the target data execution function entity.

[0047] Receive a handover request confirmation message sent by the target access network entity. The handover request confirmation message contains the connection session handover result and the data service management handover result.

[0048] In some embodiments, the handover request confirmation message may further include user plane path information and / or data plane path information of the target access network entity.

[0049] In some embodiments, the Create UE Context Request message also includes service capability information of the source access network entity and service capability information of the target access network entity.

[0050] The method also includes:

[0051] If the service capability information of the source access network entity is inconsistent with the service capability information of the target access network entity, send any one of the following information to the service management function entity, session management function entity, or data management and control function entity:

[0052] Indication information indicating that the service capability information of the source access network entity is inconsistent with the service capability information of the target access network entity;

[0053] Service capability information of the source access network entity and service capability information of the target access network entity;

[0054] Deviation information between the service capability information of the source access network entity and the service capability information of the target access network entity.

[0055] Fifthly, this disclosure also provides a terminal, including a memory, a transceiver, and a processor;

[0056] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0057] Based on the terminal's service capability requirements and the service capability information of candidate access network entities, select the target access network entity for handover.

[0058] A decision handover message is sent to the source access network entity. The decision handover message contains the identification information of the target access network entity and the service capability information of the target access network entity.

[0059] In some embodiments, the operation further includes:

[0060] Receive broadcast messages sent by candidate access network entities, which contain service capability information of the candidate access network entities or indication information indicating the service capability information of the candidate access network entities.

[0061] In some embodiments, the service capability information includes capability information for providing a first service and service scope information for providing the first service. The first service includes at least one of connectivity service, data service, intelligent service, sensing service, and security service.

[0062] In some embodiments, the decision to switch messages may also include indications that allow split access and mobility management functions to be implemented.

[0063] Sixthly, this disclosure also provides a source access network entity, including a memory, a transceiver, and a processor;

[0064] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0065] Send a handover request message to the source access and mobility management function entity. The handover request message contains the terminal's connection session information and the terminal's data service management information; or,

[0066] A first handover request message is sent to the target access network entity. The first handover request message contains information on the data service capabilities that the target access network entity needs to have or perform.

[0067] In some embodiments, the operation further includes:

[0068] The receiving terminal sends a handover decision message, which contains the identification information of the target access network entity and the service capability information of the target access network entity.

[0069] In some embodiments, the handover request message may also include the identification information of the target access network entity and the service capability information of the target access network entity.

[0070] In some embodiments, the operation further includes:

[0071] Based on the terminal's service capability requirements and the service capability information of candidate access network entities, the target access network entity is selected.

[0072] In some embodiments, the decision to switch messages may also include indications that allow split access and mobility management functions to be implemented.

[0073] In some embodiments, the handover request message also includes indication information that allows split access and mobility management function entities to be permitted.

[0074] In a seventh aspect, this disclosure also provides a source access and mobility management function entity, including a memory, a transceiver, and a processor;

[0075] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0076] Receive a handover request message sent by the source access network entity. The handover request message contains the terminal's connection session information and the terminal's data service management information.

[0077] Based on the handover request message and the terminal's mobility restriction information, select the target access and mobility management function entity;

[0078] A Create UE Context Request message is sent to the target access and mobility management function entity. The Create UE Context Request message contains connection session information, data service management information, and mobility restriction information.

[0079] In some embodiments, the UE context creation request message may further include information about at least one network element among the service management function entity, session management function entity, and data management control function entity of the serving terminal.

[0080] In some embodiments, the handover request message may also include the identification information of the target access network entity and the service capability information of the target access network entity.

[0081] In some embodiments, the Create UE Context Request message may also include service capability information of the source access network entity and service capability information of the target access network entity.

[0082] In some embodiments, mobility restriction information includes restriction information on the terminal's use of a first service provided by the network and / or restriction information on the terminal's provision of a first service to the network, wherein the first service includes at least one of connectivity service, data service, intelligent service, sensing service, and security service.

[0083] In some embodiments, mobility restriction information includes RAT restriction information, prohibited area restriction information, service area restriction information, and network type restriction information.

[0084] In some embodiments, the operation further includes:

[0085] Based on the service area restriction information and the service capability openness information of the terminal in the terminal's contract data, the service area restriction information of the terminal is determined.

[0086] In some embodiments, the service area restriction information includes a tracking area identifier associated with the service; or, the service area restriction information includes a tracking area identifier and service information.

[0087] In some embodiments, the handover request message also includes indication information that allows split access and mobility management function entities to be permitted.

[0088] In some embodiments, the target access and mobility management function entity is a split access and mobility management function entity.

[0089] Eighthly, this disclosure also provides a target access and mobility management function entity, including a memory, a transceiver, and a processor;

[0090] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0091] Receive the Create UE Context Request message sent by the Source Access and Mobility Management Function Entity. The Create UE Context Request message contains the terminal's connection session information, the terminal's data service management information, and the terminal's mobility restriction information.

[0092] Based on mobility restriction information, determine the services the terminal can use after handover and / or the services the terminal can provide after handover, and perform any of the following operations based on connection session information and data service management information:

[0093] Send a service context update request message to the service management entity or session management entity;

[0094] Send a connection session context update request message to the session management function entity and a data service management context update request message to the data management control function entity.

[0095] In some embodiments, the operation further includes:

[0096] Receive a service context update response message from a service management entity or a session management entity. This service context update response message contains user plane path information for the target user plane entity and data plane path information for the target data execution entity; or...

[0097] It receives a connection session context update response message sent by the session management function entity and a data service management context update response message sent by the data management control function entity. The connection session context update response message contains the user plane path information of the target user plane function entity, and the data service management context update response message contains the data plane path information of the target data execution function entity.

[0098] In some embodiments, the operation further includes:

[0099] Send a second handover request message to the target access network entity. The second handover request message contains the user plane path information of the target user plane function entity and the data plane path information of the target data execution function entity.

[0100] Receive a handover request confirmation message sent by the target access network entity. The handover request confirmation message contains the connection session handover result and the data service management handover result.

[0101] In some embodiments, the handover request confirmation message may further include user plane path information and / or data plane path information of the target access network entity.

[0102] In some embodiments, the Create UE Context Request message also includes service capability information of the source access network entity and service capability information of the target access network entity.

[0103] This operation also includes:

[0104] If the service capability information of the source access network entity is inconsistent with the service capability information of the target access network entity, send any one of the following information to the service management function entity, session management function entity, or data management and control function entity:

[0105] Indication information indicating that the service capability information of the source access network entity is inconsistent with the service capability information of the target access network entity;

[0106] Service capability information of the source access network entity and service capability information of the target access network entity;

[0107] Deviation information between the service capability information of the source access network entity and the service capability information of the target access network entity.

[0108] Ninthly, this disclosure also provides a switching device, comprising:

[0109] The first selection unit is used to select the target access network entity for handover based on the terminal's service capability requirements and the service capability information of the candidate access network entities.

[0110] The first sending unit is used to send a decision handover message to the source access network entity. The decision handover message contains the identification information of the target access network entity and the service capability information of the target access network entity.

[0111] In a tenth aspect, this disclosure also provides a switching device, comprising:

[0112] The second sending unit is configured to send a handover request message to the source access and mobility management function entity, the handover request message containing the terminal's connection session information and the terminal's data service management information; or, to send a first handover request message to the target access network entity, the first handover request message containing information on the data service capabilities that the target access network entity needs to possess or execute.

[0113] In an eleventh aspect, this disclosure also provides a switching device, comprising:

[0114] The third receiving unit is used to receive a handover request message sent by the source access network entity. The handover request message contains the terminal's connection session information and the terminal's data service management information.

[0115] The third selection unit is used to select the target access and mobility management function entity based on the handover request message and the terminal's mobility restriction information.

[0116] The third sending unit is used to send a UE context creation request message to the target access and mobility management function entity. The UE context creation request message contains connection session information, data service management information, and mobility restriction information.

[0117] In a twelfth aspect, this disclosure also provides a switching device, comprising:

[0118] The fourth receiving unit is used to receive the Create UE Context Request message sent by the source access and mobility management function entity. The Create UE Context Request message contains the terminal's connection session information, the terminal's data service management information, and the terminal's mobility restriction information.

[0119] The first processing unit is configured to determine, based on mobility restriction information, the services that the terminal can use after handover and / or the services that the terminal can provide after handover, and to perform any of the following operations based on connection session information and data service management information:

[0120] Send a service context update request message to the service management entity or session management entity;

[0121] Send a connection session context update request message to the session management function entity and a data service management context update request message to the data management control function entity.

[0122] In a thirteenth aspect, this disclosure also provides a non-transiently readable storage medium storing a program for causing a processor to execute the switching method described in the first aspect, or the switching method described in the second aspect, or the switching method described in the third aspect, or the switching method described in the fourth aspect.

[0123] In a fourteenth aspect, this disclosure also provides a communication device storing a program for causing the communication device to perform the switching method described in the first aspect, or the switching method described in the second aspect, or the switching method described in the third aspect, or the switching method described in the fourth aspect.

[0124] In a fifteenth aspect, this disclosure also provides a processor-readable storage medium storing a program for causing a processor to perform the switching method described in the first aspect, or the switching method described in the second aspect, or the switching method described in the third aspect, or the switching method described in the fourth aspect.

[0125] In a sixteenth aspect, this disclosure also provides a chip product storing a program for causing the chip product to perform the switching method described in the first aspect, or the switching method described in the second aspect, or the switching method described in the third aspect, or the switching method described in the fourth aspect.

[0126] The handover method, device, apparatus, and storage medium provided in this disclosure enable the terminal to select the target access network entity for handover based on the terminal's service capability requirements and the service capability information of the candidate access network entities. The handover decision message sent to the source access network entity includes the identification information and service capability information of the target access network entity, thereby better meeting the terminal's needs for multi-element services and improving the applicability of the handover mechanism in multi-element service scenarios. Attached Figure Description

[0127] To more clearly illustrate the technical solutions in the embodiments or related technologies of this disclosure, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0128] Figure 1 is a flowchart illustrating one of the switching methods provided in this embodiment of the present disclosure.

[0129] Figure 2 is an example diagram of the 6G network architecture for converged connectivity services and data services provided in the embodiments of this disclosure.

[0130] Figure 3 is a second schematic flowchart of the switching method provided in the embodiments of this disclosure.

[0131] Figure 4 is a flowchart of the switching method provided in this embodiment of the present disclosure.

[0132] Figure 5 is a fourth flowchart illustrating the switching method provided in this embodiment of the present disclosure.

[0133] Figure 6 is an example flowchart of the N2 handover preparation stage provided in an embodiment of this disclosure.

[0134] Figure 7 is an example flowchart of the N2 switching execution phase provided in an embodiment of this disclosure.

[0135] Figure 8 is a flowchart of an example of Xn switching provided in an embodiment of this disclosure.

[0136] Figure 9 is a flowchart of Example 2 provided in the embodiments of this disclosure.

[0137] Figure 10 is a network architecture diagram of introducing I-AMF provided in an embodiment of this disclosure.

[0138] Figure 11 is a schematic diagram of the structure of the terminal provided in the embodiment of this disclosure.

[0139] Figure 12 is a schematic diagram of the structure of the source access network entity, the source access and mobility management function entity, or the target access and mobility management function entity provided in the embodiments of this disclosure.

[0140] Figure 13 is one of the structural schematic diagrams of the switching device provided in the embodiments of this disclosure.

[0141] Figure 14 is a second schematic diagram of the switching device provided in the embodiments of this disclosure.

[0142] Figure 15 is a third schematic diagram of the switching device provided in the embodiments of this disclosure.

[0143] Figure 16 is a fourth schematic diagram of the switching device provided in the embodiments of this disclosure. Detailed Implementation

[0144] In this disclosure, the term "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0145] In this disclosure, the term "multiple" refers to two or more, and other quantifiers are similar.

[0146] In the embodiments of this disclosure, the terms "first," "second," etc., are used to distinguish similar objects and are not used to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this disclosure can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, and the number of objects is not limited; for example, the first object can be one or more.

[0147] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this disclosure.

[0148] To facilitate a clearer understanding of the technical solutions of the embodiments of this disclosure, some technical content related to the embodiments of this disclosure will be introduced first.

[0149] Fifth-generation mobile communication (5G) networks serve as "pipelines" for communication session data transmission, acting as pathways for information interaction between terminals and the network. Unlike point-to-point transmission of communication session data, data generated and consumed by intelligence, sensing, and network operations themselves in 6G networks requires distributed data collection, preprocessing, storage, and analysis. This necessitates a data plane architecture (or data framework, or other name that achieves the same function) independent of the traditional user plane, systematically addressing the 6G mobile communication network's need for control and value-added services of non-user plane data (or operator services data, system data), supporting 6G networks to achieve data service capabilities that transcend communication (or connectivity).

[0150] For 6G, communication networks are no longer just data transmission "channels," but also include a data plane (or data services, data frameworks, data functions, etc.) to achieve full lifecycle data management and data services, including data collection, transmission, processing, storage, and consumption. When a terminal (or User Equipment, UE) moves, its related connection and data services need to be managed for mobility. For example, terminal movement may cause changes in the connection and data services provided by the network the terminal is currently using, or it may cause changes in the terminal's ability to provide data services to the network. Therefore, a new mobility management scheme for 6G is needed, including mobility restriction management and handover mechanisms for 6G connection and data.

[0151] Figure 1 is a flowchart of one of the switching methods provided in this embodiment of the present disclosure. The method is applied to a terminal. As shown in Figure 1, the method includes the following steps 101 and 102.

[0152] Step 101: Based on the terminal's service capability requirements and the service capability information of the candidate access network entities, select the target access network entity for handover.

[0153] Step 102: Send a decision handover message to the source access network entity. The decision handover message contains the identification information of the target access network entity and the service capability information of the target access network entity.

[0154] Specifically, for multi-element service scenarios, in this embodiment of the disclosure, the terminal can select a suitable target access network entity to perform the handover based on its own service capability requirements, namely the service capabilities required by its own business, and the service capability information of the candidate access network entities, so as to better meet the terminal's needs for multi-element services.

[0155] After selecting a target access network entity, the terminal can send a handover decision message to the source access network entity. This message instructs the terminal to switch to the target access network entity and includes the target access network entity's identification information and service capability information. The source access network entity can determine the target access network entity based on the identification information contained in the handover decision message and send a handover request message to that entity. Alternatively, the source access network entity can send the target access network entity's identification information and service capability information to the source access and mobility management function entity, allowing the source access and mobility management function entity to select a suitable target access and mobility management function entity. Subsequently, the data management and control function entity can also select a suitable data execution function entity based on the target access network entity's service capability information.

[0156] The handover method provided in this disclosure allows the terminal to select a target access network entity for handover based on the terminal's service capability requirements and the service capability information of candidate access network entities. The handover decision message sent to the source access network entity includes the identification information and service capability information of the target access network entity, thereby better meeting the terminal's needs for multi-element services and improving the applicability of the handover mechanism in multi-element service scenarios.

[0157] Figure 2 is an example diagram of the 6G network architecture for converged connectivity services and data services provided in the embodiments of this disclosure. To facilitate understanding of the technical solutions of this disclosure, the relevant network functional entities involved in this disclosure will be described below in conjunction with Figure 2.

[0158] Service Management Function (SeMF) entity: responsible for the integrated management of multiple service or business elements.

[0159] The Data Management and Control Function (DMF) entity is responsible for the management and control of the data plane, data services, data framework, and data functions. It quickly completes the orchestration and control of data execution function entities based on data service requests (i.e., the discovery, selection, sorting / configuration generation, issuance of control instructions / instructions for configuration, etc. of data execution function entities), and supports the full lifecycle management of data.

[0160] Data Processing Function (DPF) entity: responsible for performing data service operations such as data collection / collection / generation / providing, (pre)processing / analysis / fusion / anonymization, storage, forwarding / transmission / distribution, consumption / sharing / access / opening, so as to realize on-demand data flow and on-the-path processing.

[0161] Furthermore, to achieve integrated management of connectivity and data services, some network functions (NFs) are enhanced. For example, eAMF is an enhanced Access and Mobility Management Function (AMF) entity, enabling integrated access and mobility management across multiple elements (the possibility of eAMF being split into multiple network functions is not excluded); eNRF is an enhanced Network Repository Function (NRF) entity, enabling integrated NF management across multiple elements; ePCF is an enhanced Policy Control Function (PCF) entity; and eNEF is an enhanced Network Exposure Function (NEF) entity. Integrated management of multi-element services or business can be implemented using eSMF (i.e., an enhanced Session Management Function (SMF) entity) or SeMF.

[0162] It should be noted that the above network functions may be split (e.g., AMF or eAMF splits access function and mobility management function into two network functions), merged (e.g., the logical functions of DMF and DPF are located in the same network function), reconstructed / reorganized, or have different names (e.g., SeMF can also be a new network function with AI agent or intelligent agent capabilities, DMF can also be DCCF enhancement, NWDAF enhancement, NEF enhancement, etc., and DPF can also be SF, storage function, DCCF enhancement, ADRF enhancement, etc.).

[0163] In Figure 2, RAN refers to the Radio Access Network (RAN) entity, UPF refers to the User Plane Function (UPF) entity, and DN refers to the Data Network (DN).

[0164] It should be noted that this disclosure does not exclude other service implementation possibilities, such as the N4 interface service between UPF and SMF, and the N2 interface service between RAN and AMF.

[0165] In some embodiments, the method further includes:

[0166] Receive broadcast messages sent by candidate access network entities, which contain service capability information of the candidate access network entities or indication information indicating the service capability information of the candidate access network entities.

[0167] Specifically, an access network entity can broadcast its own service capability information or broadcast instructions indicating its own service capability information, so that the terminal can obtain the service capability information of the access network entity based on the broadcast message of the access network entity. Thus, the terminal can select the target access network entity to switch to based on its own service capability requirements and the service capability information of the candidate access network entities.

[0168] In some embodiments, service capability information of an access network entity or indication information indicating the service capability information of an access network entity can be broadcast via system message broadcast, such as via System Information Block (SIB) message broadcast.

[0169] The indication information for indicative of the service capability information of an access network entity is not specifically limited in this disclosure, as long as it can indicate the service capability information of the access network entity. For example, it can be a certain identification information or type information. When the terminal receives the identification information or type information, it can determine the service capability information of the access network entity by combining it with SIM card information, etc. SIM refers to Subscriber Identity Module.

[0170] In some embodiments, the service capability information includes capability information for providing a first service and service scope information for providing the first service. The first service includes at least one of connectivity service, data service, intelligent service / AI service, perception service, and security service.

[0171] For example, service capability information may include the access network entity's ability to provide connection services and data services, as well as the service scope corresponding to the access network entity's connection service capabilities and the service scope corresponding to its data service capabilities.

[0172] For example, service capability information may include multiple parameters: service type (such as connection service, data service, AI service, perception service, etc.); the function type of a service, such as the function type of a data service (such as preprocessing); and the parameters or information of a service, such as the function parameters of a data service (such as AI data cleaning and processing).

[0173] It should be noted that intelligent services / AI services may also include other service elements such as AI-related models, computing power, and data.

[0174] In some embodiments, the decision to switch messages may also include indications that allow split access and mobility management functions to be implemented.

[0175] Specifically, a split access and mobility management function entity refers to an access and mobility management function entity that has some of the functions of an access and mobility management function entity, such as being able to receive messages from an access network entity, but does not have mobility management functions. This split access and mobility management function entity needs to send mobility management-related information to a fully functional access and mobility management function entity for processing.

[0176] In this embodiment of the present disclosure, the terminal may include indication information in the handover decision message indicating that the split access and mobility management function entity is allowed. The source access network entity may indicate to the source access and mobility management function entity that the split access and mobility management function entity is allowed in the subsequent handover process, indicating that the source access and mobility management function entity can select the split access and mobility management function entity as the target access and mobility management function entity.

[0177] In some embodiments, if the target access and mobility management function entity is a split access and mobility management function entity, the target access and mobility management function entity may send mobility management-related information to the source access and mobility management function entity for processing.

[0178] For example, when a terminal is handing over to another network node, the source access and mobility management function entity is a fully functional access and mobility management function entity located at the source network node. An I-AMF is inserted at the target network node. This I-AMF is a split access and mobility management function entity. The I-AMF serves as the core network control plane anchor point and is responsible for receiving N1 and N2 messages from the target access network entity and sending mobility management-related information to the source access and mobility management function entity.

[0179] Figure 3 is a second flowchart of the handover method provided in this embodiment of the present disclosure. The method is applied to the source access network entity. As shown in Figure 3, the method includes the following step 301.

[0180] Step 301: Send a handover request message to the source access and mobility management function entity, the handover request message containing the terminal's connection session information and the terminal's data service management information; or, send a first handover request message to the target access network entity, the first handover request message containing information on the data service capabilities that the target access network entity needs to have or execute.

[0181] Specifically, in this embodiment of the disclosure, the handover request message sent by the source access network entity to the source access and mobility management function entity is expanded to include terminal data service management information. This data service management information refers to information related to the data service bearer path associated with the terminal. For example, when the terminal provides sensing data, it may include the data transmission topology, data transmission interface, data transmission protocol, and Quality of Service (QoS) configuration of the data bearer path between the terminal and the base station and core network functions (such as DPF, Sensing Function (SF)). Based on this data service management information, the source access and mobility management function entity can select a target access and mobility management function entity that supports the corresponding data service capabilities.

[0182] Connection session information refers to session-related information of the connection service, such as the session identifier of the connection service.

[0183] For handovers where the access and mobility management functions remain unchanged (such as Xn handover), the source access network entity can send a first handover request message to the target access network entity. This first handover request message contains information about the data service capabilities that the target access network entity needs to have or perform. The target access network entity can perform admission control based on the information contained in the first handover request message.

[0184] The handover method provided in this embodiment allows the source access network entity to send a handover request message to the source access and mobility management function entity. The handover request message includes the terminal's connection session information and the terminal's data service management information. Alternatively, it can send a first handover request message to the target access network entity. The first handover request message includes information on the data service capabilities that the target access network entity needs to possess or execute. This better meets the terminal's needs for multi-element services and improves the applicability of the handover mechanism in multi-element service scenarios.

[0185] In some embodiments, the method further includes:

[0186] The receiving terminal sends a handover decision message, which contains the identification information of the target access network entity and the service capability information of the target access network entity.

[0187] In this embodiment of the disclosure, after the terminal decides to switch and selects the target access network entity to switch to, it can send a decision to switch message to the source access network entity. The decision to switch message contains the identification information of the target access network entity and the service capability information of the target access network entity.

[0188] In some embodiments, the source access network entity may determine the target access network entity based on the identification information of the target access network entity contained in the decision handover message, and send a first handover request message to the target access network entity based on the service capability information of the target access network entity.

[0189] In some embodiments, after the terminal sends a handover decision message to the source access network entity, the source access network entity may also include the identification information and service capability information of the target access network entity in the handover request message sent to the source access and mobility management function entity. This is used by the source access and mobility management function entity to select a suitable target access and mobility management function entity. Subsequently, the data management and control function entity may also select a suitable data execution function entity based on the service capability information of the target access network entity.

[0190] In some embodiments, the method further includes:

[0191] Based on the terminal's service capability requirements and the service capability information of candidate access network entities, the target access network entity is selected.

[0192] In this embodiment of the disclosure, when the source access network entity selects the target access network entity, the selection can be made based on the terminal's service capability requirements and the service capability information of the candidate access network entities, so that the target access network entity can meet the terminal's needs for multi-element services as much as possible.

[0193] In some embodiments, the decision to switch messages may also include indications that allow split access and mobility management functions to be implemented.

[0194] In some embodiments, the handover request message also includes indication information that allows split access and mobility management function entities to be permitted.

[0195] In this embodiment of the present disclosure, the terminal may include indication information in the handover decision message indicating that the split access and mobility management function entity is allowed. The source access network entity may indicate to the source access and mobility management function entity that the split access and mobility management function entity is allowed in the subsequent handover process, indicating that the source access and mobility management function entity can select the split access and mobility management function entity as the target access and mobility management function entity.

[0196] Figure 4 is a flowchart of the third embodiment of the handover method provided in this disclosure. The method is applied to the source access and mobility management function entity. As shown in Figure 4, the method includes the following steps 401, 402 and 403.

[0197] Step 401: Receive the handover request message sent by the source access network entity. The handover request message contains the terminal's connection session information and the terminal's data service management information.

[0198] Step 402: Based on the handover request message and the terminal's mobility restriction information, select the target access and mobility management function entity.

[0199] Step 403: Send a Create UE Context Request message to the target access and mobility management function entity. The Create UE Context Request message contains connection session information, data service management information, and mobility restriction information.

[0200] Specifically, in this embodiment of the disclosure, the handover request message sent by the source access network entity to the source access and mobility management function entity is extended with the terminal's data service management information. This data service management information refers to information related to the data service bearer path associated with the terminal. For example, it may be the data transmission topology, data transmission protocol, and Quality of Service (QoS) configuration of the data bearer path between the terminal and the base station and core network functions (such as DPF, Sensing Function (SF)) when the terminal provides sensing data.

[0201] The source access and mobility management function entity can select the target access and mobility management function entity based on various information contained in the handover request message and the terminal's mobility restriction information, in order to better meet the terminal's needs for multi-element services.

[0202] After selecting the target access and mobility management function entity, the source access and mobility management function entity can include connection session information, data service management information, and mobility restriction information in the Create UE Context Request (such as Namf_Communication_CreateUEContext Request) message sent to the target access and mobility management function entity. The target access and mobility management function entity can determine the services that the terminal can use after the handover and / or the services that the terminal can provide after the handover based on the mobility restriction information, and send context update requests based on the connection session information and data service management information, such as service context update requests, connection session context update requests, and data service management context update requests.

[0203] The handover method provided in this disclosure allows the source access and mobility management function entity to select the target access and mobility management function entity based on the handover request message sent by the source access network entity and the terminal's mobility restriction information. The UE context creation request message sent to the target access and mobility management function entity includes connection session information, data service management information, and mobility restriction information, thereby better meeting the terminal's needs for multi-element services, improving the applicability of the handover mechanism in multi-element service scenarios, and supporting mobility management in multi-element service scenarios.

[0204] In some embodiments, the UE context creation request message may further include information about at least one network element among the service management function entity, session management function entity, and data management control function entity of the serving terminal.

[0205] For example, the management function of multi-element services is implemented through a service management function entity, and the UE context creation request message may include information about the service management function entity of the serving terminal. Alternatively, the management function of multi-element services is implemented through an enhanced session management function entity, and the UE context creation request message may not include information about the service management function entity, but may include information about the enhanced session management function entity and the data management control function entity.

[0206] In some embodiments, the handover request message may also include the identification information of the target access network entity and the service capability information of the target access network entity.

[0207] In some embodiments, the UE context creation request message also includes service capability information of the source access network entity and the target access network entity, so that the target access and mobility management function entity can understand whether there are differences between the service capability information of the source access network entity and the service capability information of the target access network entity, so as to make subsequent decisions that can better meet the multi-element service needs of the terminal.

[0208] In some embodiments, the Create UE Context Request message may also include indication information indicating whether the service capability information of the source access network entity and the service capability information of the target access network entity are consistent or inconsistent.

[0209] In some embodiments, mobility restriction information includes restriction information on the terminal's use of a first service provided by the network and / or restriction information on the terminal's provision of a first service to the network, wherein the first service includes at least one of connectivity service, data service, intelligent service, sensing service, and security service.

[0210] In this embodiment of the disclosure, for multi-element service scenarios, the mobility restriction information of the terminal includes restriction information on the terminal's use of a first service provided by the network and / or restriction information on the terminal's provision of a first service to the network. The first service is at least one of the multi-element services such as connection service, data service, intelligent service, sensing service, and security service, thereby expanding the terminal mobility restriction mechanism for multi-element service scenarios.

[0211] For example, in 5G systems, mobility restrictions limit the mobility processing or service access of terminals. Terminal mobility management for 6G can, on the one hand, extend the service area of ​​data capabilities beyond the service range of network-side connectivity (including access network and core network), defining which terminals can use the data services provided by the network in which areas (terminals can use different data service capabilities provided by the network in different areas); on the other hand, terminal mobility management includes not only the mobility management of terminals maintaining network connectivity during movement, but also the mobility management of providing data service capabilities during movement, defining which areas terminals can provide their data services to the network internally or externally (terminals can provide / open different data service capabilities in different areas).

[0212] In some embodiments, mobility restriction information includes RAT restriction information, prohibited area restriction information, service area restriction information, and network type restriction information.

[0213] The Radio Access Technology (RAT) restriction information refers to the relevant restrictions imposed by the RAT. For example, in a restricted RAT, a contract-based terminal is not allowed to access the public land mobile network (PLMN). Alternatively, access to the PLMN or distributed network nodes may be permitted, but the use or provision of certain services (such as data services) is not allowed under this access technology.

[0214] Prohibited area restriction information refers to the relevant restrictions imposed on prohibited areas. For example, within a prohibited area, a contract-based terminal is not allowed to initiate any communication with the PLMN network or distributed network nodes. The terminal's behavior in cell selection, RAT selection, and PLMN selection depends on the network response that notified the terminal of the prohibited area.

[0215] Service area restriction information refers to the relevant restriction information of the service area, such as defining the area in which a terminal can or cannot initiate communication with the network, which can specifically include licensed areas and unlicensed areas.

[0216] Permitted Area: Within the permitted area, the terminal is allowed to initiate communication with the network that is permitted by the contract (including permission to use one or more services, or permission to provide one or more services; or permission to use a specific service function under a certain type of service, such as a preprocessing function corresponding to a data service type; or permission to use a very specific service function under a certain type of service, such as an AI data collection function, or a perception data collection function, etc. That is, there can be different levels of granularity).

[0217] Unlicensed Areas: In unlicensed areas, the terminal is subject to the contracted service area restrictions. Under service area restrictions, the terminal is not allowed to initiate service requests to the network (a fine distinction is made between services and usage / providance; on the one hand, a service request can be one or more of the aforementioned services, and on the other hand, unlicensed means that usage or provision is not allowed), and is not allowed to make any connection requests for user plane data, control plane data, abnormal data reports, session management (SM) signaling, or data plane data to obtain user services unrelated to mobility.

[0218] Network type restriction information refers to the restrictions related to the network type. For example, it defines whether a terminal is allowed to connect only to the 5G core network, only to the Evolved Packet Core (EPC), or simultaneously to both the 5G core network and the EPC for this PLMN. Alternatively, for 6G distributed networking, it defines whether a terminal is allowed to connect to network nodes that provide one or more services for this PLMN (distributed network nodes can be the core network, or include both the access network and the core network).

[0219] In some embodiments, the method further includes:

[0220] Based on the service area restriction information and the service capability openness information of the terminal in the terminal's contract data, the service area restriction information of the terminal is determined.

[0221] The service area restriction information in the terminal's contract data may include service area restriction information after the extension of multi-element services.

[0222] The terminal's service capability openness information can include information on the service capabilities that the terminal can open, as well as the areas where these service capabilities are permitted to be opened. For example, the areas where the terminal's data service capabilities are permitted to be opened refer to the areas where the terminal can provide that data service capability. The terminal's service capability openness information can be located in the subscribed data or can be reported by the terminal to the network, such as when the terminal reports its data service capability openness information to the Access and Mobility Management Functional Entity or the Data Management and Control Functional Entity.

[0223] In some embodiments, the service area restriction information includes a tracking area identifier associated with the service; or, the service area restriction information includes a tracking area identifier and service information.

[0224] In 5G mechanisms, a Service Area Restriction can contain one or more complete Tracking Areas (TAs), or it can be set to unlimited (i.e., including all TAs of the PLMN). A TA can contain one or more cells, and is defined as an area where the terminal can move freely without needing to update location services. TAI stands for Tracking Area Identity, which is composed of the PLMN and TAC (Tracking Area Code).

[0225] For multi-element service scenarios, a TA can be a region where the connection service remains unchanged, while other services such as data services may change in that region; or a TA can be a region where the connection service and other multi-element services such as data services remain unchanged.

[0226] For example, the tracking area identifier can be composed of a PLMN, a TAC, a service element type (such as connectivity, data, intelligence, security, etc.), and a service provision type (using the service / providing the service). Alternatively, it can be a redefined TAC, where the tracking area identifier consists of a PLMN and a redefined TAC generated based on the original TAC and information about the service element type and service provision type. The tracking area identifier can also be service-independent, using the original TAC, where service information (i.e., information related to multi-element services) can be determined through contract data and information from network element interactions.

[0227] In some embodiments, multiple TAs form a TA List and are simultaneously assigned to a terminal. When the terminal moves within this TA List, it does not need to perform a TA update, thus reducing frequent interactions with the network. When the terminal enters a new TA area that is not in its registered TA List, a TA update is required, and a new set of TAs is assigned to the terminal.

[0228] Unified Data Management (UDM) stores service area restriction information for a terminal as part of the terminal's subscription data. The service area restrictions included in the terminal subscription data in UDM may include licensed or unlicensed regions.

[0229] During the registration process, the Access and Mobility Management (AMM) entity determines the service area restriction information of the terminal based on the service area restriction information in the subscription data of the UDM and the terminal's service capability openness information, and provides the service area restriction information to the terminal in the form of TA (or TA connection area and service element information). The TA may be a subset of the complete list stored in the terminal's subscription data, or it may be provided by the Policy Control (PCC) entity. The licensed areas included in the service area restrictions can be pre-configured and / or dynamically allocated by the AMM entity.

[0230] Policy control entities within the service network can adjust service area restrictions for terminals, such as expanding permitted areas, reducing unpermitted areas, or increasing the maximum number of permitted tracking areas. If a network data analytics entity is deployed, the policy control entity can use terminal mobility analytics data from the network data analytics entity to adjust service area restrictions. The policy control entity can also adjust service area restrictions based on information such as the data service capability status reported / updated by the terminal. For example, when a terminal 1 adjusts the open status (allowed / disallowed) or area range of its own data service capabilities, the policy control entity needs to update the service area restrictions of terminals associated with that capability (e.g., terminal 1 itself, or other terminals using the services provided by terminal 1) based on this information.

[0231] In some embodiments, the handover request message also includes indication information that allows split access and mobility management function entities to be permitted.

[0232] In this embodiment of the disclosure, the source access network entity may indicate to the source access and mobility management function entity that it is allowed to split access and mobility management function entity, indicating that the source access and mobility management function entity may select the split access and mobility management function entity as the target access and mobility management function entity.

[0233] In some embodiments, the target access and mobility management function entity is a split access and mobility management function entity. In this case, the target access and mobility management function entity can send mobility management-related information to the source access and mobility management function entity for processing.

[0234] Figure 5 is a flowchart of the fourth embodiment of the handover method provided in this disclosure. The method is applied to the target access and mobility management function entity. As shown in Figure 5, the method includes the following steps 501 and 502.

[0235] Step 501: Receive the Create UE Context Request message sent by the Source Access and Mobility Management Function Entity. The Create UE Context Request message contains the terminal's connection session information, the terminal's data service management information, and the terminal's mobility restriction information.

[0236] Step 502: Based on mobility restriction information, determine the services that the terminal can use after handover and / or the services that the terminal can provide after handover, and perform any of the following operations based on connection session information and data service management information: send a service context update request message to the service management function entity or the session management function entity; or, send a connection session context update request message to the session management function entity and a data service management context update request message to the data management control function entity.

[0237] Specifically, in this embodiment of the disclosure, after the source access and mobility management function entity selects the target access and mobility management function entity, it may include connection session information, data service management information, and mobility restriction information in the Create UE Context Request message sent to the target access and mobility management function entity. The target access and mobility management function entity may determine the services that the terminal can use after the handover and / or the services that the terminal can provide after the handover based on the mobility restriction information.

[0238] For example, after receiving a message from the source access and mobility management entity, the target access and mobility management entity determines, based on the terminal's mobility restriction information, whether the terminal can continue to use or provide the original service at the new location after the handover. If the terminal's presence in the new area may cause one or more of the multi-element services to disappear in that area, the session corresponding to that service needs to be released. If a new service provided by the network appears in the new area, allowing the terminal to use it, an indication message (including a new service indication, service type, service area, service duration, and other service parameters) can be sent to the terminal. The terminal can then initiate a new service request immediately or in the future based on this indication message.

[0239] In some embodiments, the management functions of multi-element services are implemented through a service management function entity or an enhanced session management function entity. The target access and mobility management function entity can send a service context update request message to the service management function entity or the session management function entity to request an update of the service context.

[0240] In some embodiments, the service management function entity that receives the service context update request message sends a connection session context update request message to the session management function entity and a data service management context update request message to the data management control function entity.

[0241] In some embodiments, the session management function entity that receives the service context update request message performs a connection session context update and sends a data service management context update request message to the data management control function entity.

[0242] The Connection Session Context Update Request message is used to request an update to the Connection Session Context, and the Data Service Management Context Update Request message is used to request an update to the Data Service Management Context.

[0243] The handover method provided in this disclosure allows the source access and mobility management function entity to include connection session information, data service management information, and mobility restriction information in the Create UE Context Request message sent to the target access and mobility management function entity. This enables the target access and mobility management function entity to determine the services that the terminal can use and / or the services that the terminal can provide after the handover based on the mobility restriction information, and to send a context update request based on the connection session information and data service management information. This better meets the terminal's needs for multi-element services, improves the applicability of the handover mechanism in multi-element service scenarios, and supports mobility management in multi-element service scenarios.

[0244] In some embodiments, the method further includes:

[0245] Receive a service context update response message from a service management entity or a session management entity. This service context update response message contains user plane path information for the target user plane entity and data plane path information for the target data execution entity; or...

[0246] It receives a connection session context update response message sent by the session management function entity and a data service management context update response message sent by the data management control function entity. The connection session context update response message contains the user plane path information of the target user plane function entity, and the data service management context update response message contains the data plane path information of the target data execution function entity.

[0247] In this embodiment of the disclosure, the switching process involves not only the establishment of the user plane path for the connection service, but also the establishment of the data plane path for the data service.

[0248] In some embodiments, the user plane path information of the target user plane function entity may be the tunnel information of the target user plane function entity in the user plane path between the target access network entity and the target user plane function entity, such as the tunnel endpoint identifier.

[0249] In some embodiments, the data plane path information of the target data execution function entity may be the Uniform Resource Locator (URL) address of the target data execution function entity in the data plane path between the target access network entity and the target data execution function entity, that is, the address used to support the target access network entity to forward the corresponding uplink data to the target data execution function entity.

[0250] The user plane path is established through the interaction between the session management function entity and the target user plane function entity. During the interaction, the session management function entity obtains the user plane path information of the target user plane function entity and then sends it to the service management function entity or the target access and mobility management function entity.

[0251] The data plane path is established through the interaction between the data management and control function entity and the target data execution function entity. During the interaction, the data management and control function entity obtains the data plane path information of the target data execution function entity and then sends it to the service management function entity or the target access and mobility management function entity.

[0252] In some embodiments, the method further includes:

[0253] Send a second handover request message to the target access network entity. The second handover request message contains the user plane path information of the target user plane function entity and the data plane path information of the target data execution function entity.

[0254] Receive a handover request confirmation message sent by the target access network entity. The handover request confirmation message contains the connection session handover result and the data service management handover result.

[0255] Specifically, after receiving the user plane path information of the target user plane function entity and the data plane path information of the target data execution function entity, the target access and mobility management function entity can send a second handover request message to the target access network entity, requesting the target access network entity to perform a handover related to connection session and data service management. The second handover request message contains the user plane path information of the target user plane function entity and the data plane path information of the target data execution function entity.

[0256] The target access network entity sends a handover request confirmation message to the target access and mobility management function entity based on the handover permission status. The handover request confirmation message contains the connection session handover result and the data service management handover result, allowing partial handover success.

[0257] In some embodiments, the handover request confirmation message may further include user plane path information and / or data plane path information of the target access network entity.

[0258] Specifically, depending on whether handover is permitted, the target access network entity may also include its user plane path information and / or data plane path information in the handover request confirmation message. The user plane path information may be the tunnel information of the target access network entity within the user plane path between the target access network entity and the target user plane function entity; the data plane path information may be the URL address of the target access network entity within the data plane path between the target access network entity and the target data execution function entity, i.e., the address used to support the target data execution function entity in forwarding corresponding downlink data to the target access network entity.

[0259] In some embodiments, the Create UE Context Request message also includes service capability information of the source access network entity and service capability information of the target access network entity.

[0260] The method also includes:

[0261] If the service capability information of the source access network entity is inconsistent with the service capability information of the target access network entity, send any one of the following information to the service management function entity, session management function entity, or data management and control function entity:

[0262] Indication information indicating that the service capability information of the source access network entity is inconsistent with the service capability information of the target access network entity;

[0263] Service capability information of the source access network entity and service capability information of the target access network entity;

[0264] Deviation information between the service capability information of the source access network entity and the service capability information of the target access network entity.

[0265] For ease of description, the aforementioned "indication information indicating inconsistency between the service capability information of the source access network entity and the service capability information of the target access network entity; or deviation information between the service capability information of the source access network entity and the service capability information of the target access network entity; or deviation information between the service capability information of the source access network entity and the service capability information of the target access network entity" can be referred to as the first information. In some embodiments, upon receiving the first information, the data management and control function entity can select a target data execution function entity based on the first information. The selected target data execution function entity needs to be able to compensate for the functions that the target access network entity cannot perform as much as possible and meet the service capability requirements of the terminal to ensure a consistent service experience for the terminal.

[0266] If a target data execution function entity that meets the requirements cannot be selected, the requirements can be met through the access network entity. For example, when the core network element cannot perform certain functions that can only be performed by the access network; or in some cases, the terminal can complete the functions that the target access network entity cannot complete by renegotiation and configuration; or certain functions can be completed through the collaboration of the terminal, the access network entity, and the data execution function entity.

[0267] The methods provided in the various embodiments of this disclosure are based on the same technical concept, so the implementation of each method can be referred to each other, and repeated parts will not be described again.

[0268] The methods provided in the above embodiments of this disclosure are illustrated by specific examples below.

[0269] It should be noted that in the following examples, S-RAN refers to the source access network entity, T-RAN refers to the target access network entity, S-AMF refers to the source access and mobility management function entity, T-AMF refers to the target access and mobility management function entity, T-UPF refers to the target user plane function entity, S-UPF refers to the source user plane function entity, T-DPF refers to the target data execution function entity, and S-DPF refers to the source data execution function entity.

[0270] Example 1: Integrated switching of connectivity and data.

[0271] The capabilities of 6G networks will expand beyond connectivity to include data capabilities, intelligence, and security. Handover will also evolve from a simple connectivity switch to an integrated switch encompassing connectivity, data, intelligence, and security. For example, during Xn handover, not only is a new connection channel between the T-RAN and UPF established, but a new data channel between the T-RAN and DPF also needs to be created; similarly, during N2 handover, not only is a switch from S-UPF to T-UPF required, but also a switch from S-DPF to T-DPF, and so on.

[0272] Example 1.1: N2 switching.

[0273] Figure 6 is an example flowchart of the N2 handover preparation stage provided in this embodiment of the disclosure. As shown in Figure 6, its main processes include:

[0274] Step 1-0: The UE decides to switch and interacts with the S-RAN.

[0275] Step 1-1: The handover request message sent by S-RAN to S-AMF includes additional information related to multi-factor services (e.g., data service management information).

[0276] Steps 1-2: Based on the UE or the service elements of the session on the UE (e.g., data services), the S-AMF selects the T-AMF that supports the corresponding element capabilities.

[0277] Steps 1-3: The message from S-AMF to T-AMF (Create UE Context Request Message) includes network element information such as SeMF, SMF, and DMF for the UE, connection session information, data service management information, and service area restriction information after merging data services.

[0278] After receiving a message from the S-AMF, the T-AMF determines, based on mobility restriction information, whether the UE can continue to use or provide the original service at the new location after the handover. If the UE's presence in the new area may cause one or more services (connectivity or data) to disappear in that area, the session corresponding to those services needs to be released. If a new service provided by the network appears in the new area, allowing the UE to use it, an indication message (including service parameters such as new service appearance indication, service type, service area, and service duration) can be sent to the UE. The UE can then initiate a new service request immediately or in the future based on this indication message. Changes in the UE's ability to provide services to the network due to UE movement are explained in the final section of Example 2.

[0279] Steps 1-4: If a new service management function SeMF corresponding to a multi-element is added, the T-AMF requests an update to the service context from the SeMF. If the eSMF is enhanced to be responsible for multi-element service management, this step is skipped and step 1-5.b is initiated by the eSMF (represented by SMF in the figure). If multi-element service management is not introduced, the T-AMF initiates a connection session context update request and a data service management context update request to the SMF and DMF respectively.

[0280] Steps 1-5: When the UE involves connection services and data services, the SeMF requests the SMF and DMF to update the connection session context (step 1-5.a) and the data service management context (step 1-5.b) respectively; or the enhanced SMF requests the DMF to update the data service management context.

[0281] Steps 1-6 to 1-8: In addition to establishing the user plane path for the connection service, the data plane path for the data service is also established.

[0282] If the S-DPF cannot connect to the T-RAN and therefore cannot serve the UE due to a change in the base station the UE is accessing, a T-DPF with the same capabilities as the S-DPF, or with higher functionality / performance than the S-DPF, needs to be selected to serve the UE. Alternatively, a T-DPF supporting data plane protocol forwarding can be inserted between the T-RAN and the S-DPF to connect them. Changes in RAN capabilities before and after the handover are explained in Example 2.

[0283] Steps 1-9 to 1-10: Connection Session and Data Service Management Context Update Response. The response message includes user plane path information and data plane path information provided to T-RAN for establishing the connection between T-RAN and T-UPF / T-DPF.

[0284] For data plane path information, it can be the data service URL address of the T-DPF, which is used to support T-RAN to forward the uplink data corresponding to the data service to the T-DPF.

[0285] Steps 1-11: Response monitoring.

[0286] Steps 1-12: T-AMF requests T-RAN to perform handover related to connection session and data service management.

[0287] Steps 1-13: The handover request confirmation message sent by T-RAN to T-AMF includes the connection session handover result and the data service management handover result, allowing for partial handover success.

[0288] Steps 1-14: For services that can be successfully switched over, T-RAN provides the corresponding information to the corresponding SMF, UPF, DMF, and DPF. In addition to the user plane path information of T-RAN, the information corresponding to T-RAN may also include the data plane path information of T-RAN, such as the data service URL address of T-RAN, which is used by T-DPF to forward the downlink data corresponding to the data service to T-RAN.

[0289] Note 1: The user plane path supports bidirectional uplink and downlink transmission between UE and UPF by default, and handover involves simultaneous switching and establishment of both uplink and downlink paths. The data plane path may differ depending on the data service. For example, a certain data service may only require the establishment of an uplink path between UE and RAN or UE and RAN and DPF (e.g., UE-aware data reporting), while another data service may only require the establishment of a downlink path between DPF and RAN and UE or RAN and UE. In other words, the main differences include: 1) Only one of the uplink or downlink paths may be switched; 2) The data plane handover path may only involve UE and RAN.

[0290] Note 2: The above process is based on the independent deployment of UPF and DPF. If DPF is implemented by enhancing UPF, it may be necessary to select a new eUPF network element that meets both UPF and DPF capabilities.

[0291] Note 3: When the user plane path and the data plane path are related, refer to the relevant technologies and consider them together when switching between T-UPF and T-DPF. It may even be necessary to build the user plane path on the basis of the data plane path, or modify a certain path to meet the joint consideration factors.

[0292] Note 4: In scenarios where connectivity services and data services are integrated, the user plane path and data plane path may change simultaneously, as mentioned above. Alternatively, only one path may need to be changed, in which case the other path can remain unchanged. For example, after the switchover, data service management remains unchanged on the network side, only the data service management resources at the air interface are disconnected.

[0293] The N2 handover execution phase involves not only connectivity handover but also data handover. Therefore, the UE's cell and the multi-element service capabilities provided by that area are related. Session release includes connectivity session and data service management, and also involves data service management context updates and data plane modifications. The mobility registration update process also involves updating the data service capability status. The release of existing resources also includes the release of data and other resources. Note: This resource release process is performed after the handover is complete. If the handover fails, the original resources are retained unless the UE is outside the RAN's service range, rendering the resources unusable.

[0294] Furthermore, the data plane path differs from the user plane path. Since the data plane path does not involve issues like the N6 interface anchoring between UPF and DN, the anchor DPF can be changed during the handover phase. Therefore, the data flow process can be determined based on the Session and Service Continuity (SSC) mode defined by relevant technologies. Data may not involve forwarding processes between S-DPF and T-DPF, but rather flow directly between T-DPF and T-RAN. For downlink data plane data during the handover process, if delayed forwarding is allowed, it can be cached in the S-DPF, then forwarded to the T-DPF, and then forwarded downlink. If delayed forwarding is not allowed, it may first be forwarded to the S-RAN, then directly forwarded between S-RAN and T-RAN, or indirectly forwarded via S-RAN->S-DPF->T-DPF->T-RAN.

[0295] Figure 7 is an example flowchart of the N2 handover execution phase provided in this embodiment of the disclosure. As shown in Figure 7, its main process includes:

[0296] Step 2-1: The S-AMF sends a handover command to the S-RAN, indicating that the handover should begin.

[0297] Step 2-2: The S-RAN sends a handover command to the UE to perform the handover of the relevant air interface resources.

[0298] Steps 2-3: During the handover process, existing downlink data is transferred from S-UPF to S-RAN, and then transmitted to T-RAN via either direct data forwarding or indirect data forwarding.

[0299] Steps 2-4: The UE sends a handover confirmation message to the T-RAN.

[0300] Once the UE decides to switch to T-RAN, downlink data is transmitted from T-RAN to the UE.

[0301] When the UE switches to T-RAN, it transmits the uplink user plane path through the new user plane path (i.e., UE to T-RAN to T-UPF to S-UPF).

[0302] Note: Here, S-UPF is used as the anchor point UPF.

[0303] Unlike the user plane, the data plane can be divided into two transmission paths, Mode 1 and Mode 2, depending on whether the anchor point DPF needs to remain unchanged.

[0304] Steps 2-5: T-RAN sends a handover notification to T-AMF.

[0305] Steps 2-6: T-AMF and S-AMF exchange handover notifications, triggering the update of the old PDU session and data service management information before the handover, that is, re-establishing the user plane path and data plane path between T-RAN and core network functions T-UPF and T-DPF.

[0306] Downlink data is transmitted via the updated path.

[0307] Example 1.2: Xn switching.

[0308] Xn handover is similar to N2 handover, involving SeMF, DMF, DPF, and related data service capability information exchange and data resource release.

[0309] Figure 8 is a flowchart of an example of Xn switching provided in this embodiment of the disclosure. As shown in Figure 8, its main process includes:

[0310] During the switchover preparation phase, the interaction includes information on relevant service capabilities, including data.

[0311] There is an Xn interface between S-RAN and T-RAN, and data is forwarded through the Xn interface.

[0312] Step 3-1: S-RAN reports the RAN-side data information to AMF, and T-RAN requests to switch the N2 path between RAN and AMF.

[0313] Step 3-2: AMF requests SeMF to update the user plane path and data plane path.

[0314] Steps 3-3 to 3-4: SeMF interacts with SMF and DMF respectively to request updates to the user plane path and data plane path.

[0315] Steps 3-5: After the UPF has forwarded the last existing message, it sends an End Marker notification message.

[0316] Steps 3-6: Update the user plane path and data plane path using SeMF.

[0317] Steps 3-7: AMF notifies T-RAN N2 that the path switchover is complete.

[0318] Steps 3-8: T-RAN notifies S-RAN to release resources for related connectivity and data services.

[0319] The switchover preparation phase mainly includes:

[0320] Step 4-1: S-RAN configures the UE to perform UE measurements, and the UE measures and reports the status of connection and data-related services.

[0321] Step 4-2: Based on the UE's measurement report results, the S-RAN determines and decides to switch to a certain T-RAN when a certain condition is met. The selection of the T-RAN should meet the UE's needs in terms of both connectivity and data as much as possible.

[0322] Step 4-3: The S-RAN sends a handover request message to the T-RAN, which includes information on the data service capabilities that the T-RAN needs to have or perform.

[0323] Step 4-4: T-RAN performs admission control based on the handover request message sent by S-RAN.

[0324] Example 2: The RAN capabilities are inconsistent before and after the handover.

[0325] When the capabilities provided by T-RAN to the UE or a UE session are inconsistent with those of S-RAN due to UE handover, the relevant functions performed by the UE or network are readjusted to share some of the RAN's capabilities (i.e., the T-RAN cannot cover the deviation of the original capabilities or functions of S-RAN).

[0326] Figure 9 is a flowchart of Example 2 provided in the embodiments of this disclosure. As shown in Figure 9, its main process includes:

[0327] Step 5-0: When the UE decides to switch to T-RAN, the interaction message with S-RAN carries T-RAN identification information and service capability information that T-RAN can provide to the UE (e.g., service type: connectivity service, data service; data service function type: preprocessing; data service function parameters: AI data cleaning and processing).

[0328] Before deciding to switch to T-RAN, the UE may receive broadcast signals from multiple base stations (e.g., via SIB messages) based on the UE's mobility. The broadcast signals may include the service capability information of the T-RAN (e.g., it can provide connectivity services and data services). The UE selects a suitable T-RAN based on the service capabilities required by its own services.

[0329] Step 5-1: S-RAN sends a handover request message to S-AMF, which carries T-RAN identification information and service capability information that T-RAN can provide to UE.

[0330] Step 5-2: S-AMF selects T-AMF that supports multi-element capabilities.

[0331] Step 5-3: The UE Context Creation Request message sent by S-AMF to T-AMF carries information about the service capabilities provided by S-RAN for the UE, service, or session, such as the data function corresponding to the data service being preprocessing—AI data cleaning processing, etc., as well as information about the service capabilities that T-RAN can provide for the UE, service, or session. In some implementations, it may carry an indication of whether the service capabilities provided by S-RAN and T-RAN are consistent.

[0332] Step 5-4: If a new service management function SeMF corresponding to a multi-element is added, the T-AMF requests the SeMF to update the service context. If the eSMF is enhanced to be responsible for multi-element service management, this step is skipped and step 5-5.b is initiated by the eSMF (represented by SMF in the figure). If multi-element service management is not introduced, the T-AMF initiates a connection session context update request and a data service management context update request to the SMF and DMF respectively.

[0333] Step 5-5: When the UE involves connection services and data services, the SeMF requests the SMF and DMF to update the connection session context (step 5-5.a) and the data service management context (step 5-5.b) respectively; or the enhanced SMF requests the DMF to update the data service management context.

[0334] When the capabilities of S-RAN and T-RAN are inconsistent, the information received by DMF includes an indication of whether the service capabilities provided by S-RAN and T-RAN are consistent, or detailed service capability information of S-RAN and T-RAN, or deviation information of the inconsistency of service capabilities provided by S-RAN and T-RAN. This facilitates DMF in selecting T-DPF. That is, the selected T-DPF needs to make up for the functions that T-RAN cannot perform, while meeting the UE's performance requirements for services.

[0335] When a DPF that meets the requirements cannot be selected, the requirements can be met through RAN relay. For example, when the core network element cannot perform certain functions that can only be performed by the access network; or in some cases, it is necessary to re-negotiate the configuration so that the UE can complete the functions that T-RAN cannot; or the UE, RAN and DPF can work together to complete the task.

[0336] Steps 5-6 to 5-8: In addition to establishing the user plane path for the connection service, the data plane path for the data service also needs to be established. Based on the rearrangement of the data service, DMF issues configuration commands to the relevant DPFs to meet the user's data service requirements.

[0337] Note: When a UE handover causes changes in the capabilities that the UE can provide (including the UE being able to provide new services or changes in service status parameters at a new location, or the UE losing a certain service or changes in service status parameters at a new location), the network can rearrange and control data services based on the UE service status. This requires the terminal, base station, network, and other components to work together to ensure a consistent service experience for the user.

[0338] Steps 5-9 to 5-10: Connection Session and Data Service Management Context Update Response. The response message includes user plane path information and data plane path information provided to T-RAN for establishing the connection between T-RAN and T-UPF / T-DPF.

[0339] For data plane path information, it can be the data service URL address of the T-DPF, which is used to support T-RAN to forward the uplink data corresponding to the data service to the T-DPF.

[0340] Steps 5-11: Response monitoring.

[0341] Steps 5-12: T-AMF requests T-RAN to perform handover related to connection session and data service management.

[0342] Step 5-13: The handover request confirmation message sent by T-RAN to T-AMF includes the connection session handover result and the data service management handover result, allowing for partial handover success.

[0343] Steps 5-14: For services that can be successfully switched over, T-RAN provides the corresponding information to the corresponding SMF, UPF, DMF, and DPF. In addition to the user plane path information of T-RAN, the information corresponding to T-RAN may also include the data plane path information of T-RAN, such as the data service URL address of T-RAN, which is used by T-DPF to forward the downlink data corresponding to the data service to T-RAN.

[0344] Example 3: Distributed networking.

[0345] Figure 10 is a network architecture diagram of introducing I-AMF provided in an embodiment of this disclosure. As shown in Figure 10, a split AMF (Split AMF) can be introduced as the I-AMF (intermediate AMF). When the UE hands over across network nodes, the AMF is still located at the source network node, and the I-AMF is inserted at the target network node. The I-AMF acts as the core network control plane anchor point, responsible for receiving N1 and N2 messages from the T-RAN and sending mobility management information to the AMF. In Figure 10, I-PCF refers to the intermediate PCF, I-SMF refers to the intermediate SMF, I-UPF refers to the intermediate UPF, AUSF refers to the Authentication Server Function (AUSF) entity, and NG3, N9, NG9', NG6, NG4, NG101, NG38, NG11, NG7, NG5, NG15, NG24, NG10, and NG13 are interfaces between different network elements.

[0346] Corresponding to the processes in Example 1 and Example 2, that is, the T-AMF mentioned above is used as I-AMF, the difference is:

[0347] Step 6-0: When the UE decides to switch to T-RAN, the interaction message with S-RAN can carry an indication message that allows split AMF.

[0348] Step 6-1: The S-RAN sends a handover request message to the S-AMF, which carries an indication that the AMF can be split.

[0349] Step 6-2: S-AMF first selects the target network node, and then selects I-AMF. I-AMF does not need to have multi-factor related functions (corresponding to the situation in step 6-3 where AMF interacts with SeMF, SMF, DMF, etc.).

[0350] Step 6-3: The message from S-AMF to I-AMF may carry network element identification information such as SeMF, SMF, and DMF. Whether or not it is carried depends on the function performed by I-AMF. If I-AMF interacts directly with SeMF, SMF, and DMF, it will carry the information. If I-AMF forwards the message to AMF, and AMF interacts with SeMF, SMF, and DMF, it will not carry the information.

[0351] Figure 11 is a schematic diagram of the structure of a terminal provided in an embodiment of this disclosure. As shown in Figure 11, the terminal includes a memory 1120, a transceiver 1110, and a processor 1100; wherein the processor 1100 and the memory 1120 may also be physically arranged separately.

[0352] The memory 1120 is used to store computer programs; the transceiver 1110 is used to send and receive data under the control of the processor 1100.

[0353] In Figure 11, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 1100 and memory represented by memory 1120. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described in detail herein. The bus interface provides an interface. Transceiver 1110 may be multiple components, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, etc. For different user equipment, user interface 1130 may also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.

[0354] The processor 1100 is responsible for managing the bus architecture and general processing, and the memory 1120 can store the data used by the processor 1100 when performing operations.

[0355] The processor 1100 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0356] The processor 1100 executes any of the terminal-side methods provided in this disclosure embodiment by calling a computer program stored in the memory 1120, according to the obtained executable instructions.

[0357] Figure 12 is a schematic diagram of the structure of the source access network entity, source access and mobility management function entity or target access and mobility management function entity provided in the embodiments of this disclosure. As shown in Figure 12, the source access network entity, source access and mobility management function entity or target access and mobility management function entity includes a memory 1220, a transceiver 1210 and a processor 1200; wherein, the processor 1200 and the memory 1220 may also be physically arranged separately.

[0358] The memory 1220 is used to store computer programs; the transceiver 1210 is used to send and receive data under the control of the processor 1200.

[0359] In Figure 12, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 1200 and memory represented by memory 1220. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described in detail herein. A bus interface provides an interface. Transceiver 1210 may be multiple elements, including transmitters and receivers, providing units for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, and other transmission media.

[0360] The processor 1200 is responsible for managing the bus architecture and general processing, while the memory 1220 can store the data used by the processor 1200 when performing operations.

[0361] The processor 1200 can be a CPU, ASIC, FPGA or CPLD, and the processor can also adopt a multi-core architecture.

[0362] The processor 1200 executes any of the methods described in the embodiments of this disclosure, namely the source access network entity side, the source access and mobility management function entity side, or the target access and mobility management function entity side, according to the obtained executable instructions by calling the computer program stored in the memory 1220.

[0363] It should be noted that the terminal, source access network entity, source access and mobility management function entity, and target access and mobility management function entity provided in the embodiments of this disclosure can implement all the method steps implemented in the above method embodiments and can achieve the same technical effect. Therefore, the parts that are the same as those in the method embodiments and the beneficial effects will not be described in detail here.

[0364] The switching device provided in the embodiments of this disclosure is described below. The switching device described below can be referred to in correspondence with the switching method described above.

[0365] Figure 13 is a schematic diagram of one of the switching devices provided in this embodiment of the present disclosure. As shown in Figure 13, the device includes:

[0366] The first selection unit 1310 is used to select the target access network entity for handover based on the service capability requirements of the terminal and the service capability information of the candidate access network entities.

[0367] The first sending unit 1320 is used to send a decision handover message to the source access network entity. The decision handover message contains the identification information of the target access network entity and the service capability information of the target access network entity.

[0368] In some embodiments, the device further includes:

[0369] The first receiving unit is used to receive a broadcast message sent by a candidate access network entity. The broadcast message contains service capability information of the candidate access network entity, or contains indication information indicating the service capability information of the candidate access network entity.

[0370] In some embodiments, the service capability information includes capability information for providing a first service and service scope information for providing the first service. The first service includes at least one of connectivity service, data service, intelligent service, sensing service, and security service.

[0371] In some embodiments, the decision to switch messages may also include indications that allow split access and mobility management functions to be implemented.

[0372] Figure 14 is a second structural schematic diagram of the switching device provided in this embodiment of the present disclosure. As shown in Figure 14, the device includes:

[0373] The second sending unit 1410 is configured to send a handover request message to the source access and mobility management function entity, the handover request message containing the terminal's connection session information and the terminal's data service management information; or, to send a first handover request message to the target access network entity, the first handover request message containing information on the data service capabilities that the target access network entity needs to possess or execute.

[0374] In some embodiments, the device further includes:

[0375] The second receiving unit is used to receive a handover decision message sent by the terminal. The handover decision message contains the identification information of the target access network entity and the service capability information of the target access network entity.

[0376] In some embodiments, the handover request message may also include the identification information of the target access network entity and the service capability information of the target access network entity.

[0377] In some embodiments, the device further includes:

[0378] The second selection unit is used to select the target access network entity based on the terminal's service capability requirements and the service capability information of the candidate access network entities.

[0379] In some embodiments, the decision to switch messages may also include indications that allow split access and mobility management functions to be implemented.

[0380] In some embodiments, the handover request message also includes indication information that allows split access and mobility management function entities to be permitted.

[0381] Figure 15 is a third schematic diagram of the switching device provided in this embodiment of the present disclosure. As shown in Figure 15, the device includes:

[0382] The third receiving unit 1510 is used to receive a handover request message sent by the source access network entity. The handover request message contains the terminal's connection session information and the terminal's data service management information.

[0383] The third selection unit 1520 is used to select a target access and mobility management function entity based on the handover request message and the terminal's mobility restriction information.

[0384] The third sending unit 1530 is used to send a UE context creation request message to the target access and mobility management function entity. The UE context creation request message contains connection session information, data service management information and mobility restriction information.

[0385] In some embodiments, the UE context creation request message may further include information about at least one network element among the service management function entity, session management function entity, and data management control function entity of the serving terminal.

[0386] In some embodiments, the handover request message may also include the identification information of the target access network entity and the service capability information of the target access network entity.

[0387] In some embodiments, the Create UE Context Request message may also include service capability information of the source access network entity and service capability information of the target access network entity.

[0388] In some embodiments, mobility restriction information includes restriction information on the terminal's use of a first service provided by the network and / or restriction information on the terminal's provision of a first service to the network, wherein the first service includes at least one of connectivity service, data service, intelligent service, sensing service, and security service.

[0389] In some embodiments, mobility restriction information includes RAT restriction information, prohibited area restriction information, service area restriction information, and network type restriction information.

[0390] In some embodiments, the device further includes:

[0391] The determining unit is used to determine the service area restriction information of the terminal based on the service area restriction information and the service capability openness information of the terminal in the terminal's contract data.

[0392] In some embodiments, the service area restriction information includes a tracking area identifier associated with the service; or, the service area restriction information includes a tracking area identifier and service information.

[0393] In some embodiments, the handover request message also includes indication information that allows split access and mobility management function entities to be permitted.

[0394] In some embodiments, the target access and mobility management function entity is a split access and mobility management function entity.

[0395] Figure 16 is a fourth structural schematic diagram of the switching device provided in this embodiment of the present disclosure. As shown in Figure 16, the device includes:

[0396] The fourth receiving unit 1610 is used to receive a UE context creation request message sent by the source access and mobility management function entity. The UE context creation request message contains the terminal's connection session information, the terminal's data service management information, and the terminal's mobility restriction information.

[0397] The first processing unit 1620 is configured to determine, based on mobility restriction information, the services that the terminal can use after handover and / or the services that the terminal can provide after handover, and to perform any of the following operations based on connection session information and data service management information:

[0398] Send a service context update request message to the service management entity or session management entity;

[0399] Send a connection session context update request message to the session management function entity and a data service management context update request message to the data management control function entity.

[0400] In some embodiments, the fourth receiving unit 1610 is further configured to:

[0401] Receive a service context update response message from a service management entity or a session management entity. This service context update response message contains user plane path information for the target user plane entity and data plane path information for the target data execution entity; or...

[0402] It receives a connection session context update response message sent by the session management function entity and a data service management context update response message sent by the data management control function entity. The connection session context update response message contains the user plane path information of the target user plane function entity, and the data service management context update response message contains the data plane path information of the target data execution function entity.

[0403] In some embodiments, the device further includes a second processing unit for:

[0404] Send a second handover request message to the target access network entity. The second handover request message contains the user plane path information of the target user plane function entity and the data plane path information of the target data execution function entity.

[0405] Receive a handover request confirmation message sent by the target access network entity. The handover request confirmation message contains the connection session handover result and the data service management handover result.

[0406] In some embodiments, the handover request confirmation message may further include user plane path information and / or data plane path information of the target access network entity.

[0407] In some embodiments, the Create UE Context Request message also includes service capability information of the source access network entity and service capability information of the target access network entity.

[0408] The device also includes a third processing unit for:

[0409] If the service capability information of the source access network entity is inconsistent with the service capability information of the target access network entity, send any one of the following information to the service management function entity, session management function entity, or data management and control function entity:

[0410] Indication information indicating that the service capability information of the source access network entity is inconsistent with the service capability information of the target access network entity;

[0411] Service capability information of the source access network entity and service capability information of the target access network entity;

[0412] Deviation information between the service capability information of the source access network entity and the service capability information of the target access network entity.

[0413] It should be noted that the switching device provided in this embodiment can implement all the method steps implemented in the above method embodiment and achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0414] It should be noted that the division of units in the embodiments of this disclosure is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0415] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to related technologies, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0416] On the other hand, embodiments of this disclosure also provide a processor-readable storage medium storing a program for causing a processor to execute the switching methods provided in the above embodiments.

[0417] It should be noted that the processor-readable storage medium provided in this embodiment can implement all the method steps implemented in the above method embodiments and achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiments will not be described in detail here.

[0418] The processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0419] The technical solutions provided in this disclosure can be applied to a variety of systems. For example, applicable systems may include Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Long Term Evolution Advanced (LTE-A) systems, Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5G New Radio (NR) systems and their evolved communication systems, and 6G (sixth generation mobile communication technology) systems. These systems may include terminal equipment and network equipment. The systems may also include a core network component, such as an Evolved Packet Core (EPC), a 5G core network (5GC), or a 6G core network.

[0420] The terminals disclosed in this embodiment can be devices that provide voice and / or data connectivity to users, handheld devices with wireless connectivity, or other processing devices connected to a wireless modem. The names of the terminals may differ in different systems; for example, in a 5G system, a terminal may be called User Equipment (UE). Wireless terminal devices can communicate with one or more core networks (CNs) via a Radio Access Network (RAN). Wireless terminal devices can be mobile terminal devices, such as mobile phones (or "cellular" phones) and computers with mobile terminal devices, for example, portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices that exchange voice and / or data with the RAN. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). Wireless terminal equipment can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, or user device, but is not limited to these terms in the embodiments disclosed herein.

[0421] The access network entity involved in this disclosure can be a base station, which may include multiple cells providing services to terminals. Depending on the specific application, the base station may also be called an access point, or a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The access network entity can be used to exchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The access network entity can also coordinate the attribute management of the air interface. For example, the access network entity involved in this disclosure can be a Base Transceiver Station (BTS) in a Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), a base station (NodeB) in Wide-band Code Division Multiple Access (WCDMA), an evolved Node B (eNB or e-NodeB) in a long term evolution (LTE) system, a 5G base station (gNB) in a next generation system, a Home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in this disclosure. In some network structures, the access network entity may include centralized unit (CU) nodes and distributed unit (DU) nodes, and the centralized unit and distributed unit may be geographically separated.

[0422] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, systems, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0423] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more flowchart illustrations and / or one or more block diagrams.

[0424] These processor-executable instructions may also be stored in a processor-readable memory that can instruct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0425] These processor-executable instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0426] Obviously, those skilled in the art can make various modifications and variations to this disclosure without departing from its spirit and scope. Therefore, if such modifications and variations fall within the scope of the claims of this disclosure and their equivalents, this disclosure is also intended to include such modifications and variations.

Claims

1. A switching method, applied to a terminal, comprising: Based on the service capability requirements of the terminal and the service capability information of the candidate access network entities, the target access network entity for switching is selected. A decision to switch is sent to the source access network entity. The decision to switch includes the identification information of the target access network entity and the service capability information of the target access network entity.

2. The handover method of claim 1, wherein, The method further includes: Receive a broadcast message sent by the candidate access network entity, the broadcast message containing the service capability information of the candidate access network entity, or containing indication information indicating the service capability information of the candidate access network entity.

3. The handover method according to claim 1 or 2, wherein, The service capability information includes the capability information for providing the first service and the service scope information for providing the first service. The first service includes at least one of the following: connectivity service, data service, intelligent service, sensing service, and security service.

4. The handover method of claim 1, wherein, The decision to switch also includes instructions to allow split access and mobility management functions.

5. A handover method applied to a source access network entity, comprising: A handover request message is sent to the source access and mobility management function entity, the handover request message containing the terminal's connection session information and the terminal's data service management information; or, A first handover request message is sent to the target access network entity, the first handover request message containing information on the data service capabilities that the target access network entity needs to have or perform.

6. The handover method of claim 5, wherein, The method further includes: The terminal sends a decision to switch, the decision to switch containing the identification information of the target access network entity and the service capability information of the target access network entity.

7. The handover method of claim 6, wherein, The handover request message also includes the identification information of the target access network entity and the service capability information of the target access network entity.

8. The handover method of claim 5, wherein, The method further includes: The target access network entity is selected based on the terminal's service capability requirements and the service capability information of the candidate access network entities.

9. The handover method of claim 6, wherein, The decision to switch also includes instructions to allow split access and mobility management functions.

10. The handover method of claim 9, wherein, The handover request message also includes instructions indicating permission for split access and mobility management function entities.

11. A handover method applied to a source access and mobility management function entity, comprising: Receive a handover request message sent by a source access network entity, wherein the handover request message contains the terminal's connection session information and the terminal's data service management information; Based on the handover request message and the terminal's mobility restriction information, select the target access and mobility management function entity; A Create UE Context Request message is sent to the target access and mobility management function entity. The Create UE Context Request message contains the connection session information, the data service management information, and the mobility restriction information.

12. The handover method of claim 11, wherein, The UE context creation request message also includes information about at least one network element among the service management function entity, session management function entity, and data management control function entity that serve the terminal.

13. The handover method of claim 11, wherein, The handover request message also includes the identification information of the target access network entity and the service capability information of the target access network entity.

14. The handover method of claim 13, wherein, The UE context creation request message also includes the service capability information of the source access network entity and the service capability information of the target access network entity.

15. The handover method of claim 11, wherein, The mobility restriction information includes restriction information on the terminal's use of a first service provided by the network and / or restriction information on the terminal's provision of a first service to the network, wherein the first service includes at least one of connectivity service, data service, intelligent service, sensing service, and security service.

16. The handover method of claim 15, wherein, The mobility restriction information includes RAT restriction information, prohibited area restriction information, service area restriction information, and network type restriction information.

17. The handover method of claim 16, wherein, The method further includes: Based on the service area restriction information in the terminal's contract data and the terminal's service capability openness information, the service area restriction information of the terminal is determined.

18. The handover method of claim 16, wherein, The service area restriction information includes a tracking area identifier related to the service; or, the service area restriction information includes a tracking area identifier and service information.

19. The handover method of claim 11, wherein, The handover request message also includes instructions indicating permission for split access and mobility management function entities.

20. The handover method of claim 19, wherein, The target access and mobility management function entity is a split access and mobility management function entity.

21. A handover method applied to a target access and mobility management function entity, comprising: The system receives a Create UE Context Request message sent by the Source Access and Mobility Management Function Entity. The Create UE Context Request message contains the terminal's connection session information, the terminal's data service management information, and the terminal's mobility restriction information. Based on the mobility restriction information, determine the services that the terminal can use after the handover and / or the services that the terminal can provide after the handover, and perform any of the following operations based on the connection session information and the data service management information: Send a service context update request message to the service management entity or session management entity; Send a connection session context update request message to the session management function entity and a data service management context update request message to the data management control function entity.

22. The handover method of claim 21, wherein, The method further includes: Receive a service context update response message sent by the service management function entity or session management function entity, wherein the service context update response message contains user plane path information of the target user plane function entity and data plane path information of the target data execution function entity; or... The system receives a connection session context update response message sent by the session management function entity and a data service management context update response message sent by the data management control function entity. The connection session context update response message contains user plane path information of the target user plane function entity, and the data service management context update response message contains data plane path information of the target data execution function entity.

23. The handover method of claim 22, wherein, The method further includes: Send a second handover request message to the target access network entity. The second handover request message contains the user plane path information of the target user plane function entity and the data plane path information of the target data execution function entity. The system receives a handover request confirmation message sent by the target access network entity. The handover request confirmation message includes the connection session handover result and the data service management handover result.

24. The handover method of claim 23, wherein, The handover request confirmation message also includes the user plane path information and / or the data plane path information of the target access network entity.

25. The handover method of claim 21, wherein, The UE context creation request message also includes the service capability information of the source access network entity and the service capability information of the target access network entity. The method further includes: If the service capability information of the source access network entity is inconsistent with the service capability information of the target access network entity, send any one of the following information to the service management function entity, session management function entity, or data management and control function entity: Indication information indicating that the service capability information of the source access network entity is inconsistent with the service capability information of the target access network entity; The service capability information of the source access network entity and the service capability information of the target access network entity; The deviation information between the service capability information of the source access network entity and the service capability information of the target access network entity.

26. A terminal, comprising a memory, a transceiver, and a processor; Memory, used to store computer programs; Transceiver, used to send and receive data under the control of the processor; Processor, configured to read the computer program in the memory and perform the following operations: Based on the service capability requirements of the terminal and the service capability information of the candidate access network entities, the target access network entity for switching is selected. A decision to switch is sent to the source access network entity. The decision to switch includes the identification information of the target access network entity and the service capability information of the target access network entity.

27. A source access network entity, comprising a memory, a transceiver, and a processor; Memory, used to store computer programs; Transceiver, used to send and receive data under the control of the processor; Processor, configured to read the computer program in the memory and perform the following operations: Send a handover request message to the source access and mobility management function entity, the handover request message containing the terminal's connection session information and the terminal's data service management information; or, A first handover request message is sent to the target access network entity, the first handover request message containing information on the data service capabilities that the target access network entity needs to have or perform.

28. A source access and mobility management function entity, comprising a memory, a transceiver, and a processor; Memory, used to store computer programs; Transceiver, used to send and receive data under the control of the processor; Processor, configured to read the computer program in the memory and perform the following operations: Receive a handover request message sent by a source access network entity, wherein the handover request message contains the terminal's connection session information and the terminal's data service management information; Based on the handover request message and the terminal's mobility restriction information, select the target access and mobility management function entity; A Create UE Context Request message is sent to the target access and mobility management function entity. The Create UE Context Request message contains the connection session information, the data service management information, and the mobility restriction information.

29. A target access and mobility management function entity, comprising a memory, a transceiver, and a processor; Memory, used to store computer programs; Transceiver, used to send and receive data under the control of the processor; Processor, configured to read the computer program in the memory and perform the following operations: The system receives a Create UE Context Request message sent by the Source Access and Mobility Management Function Entity. The Create UE Context Request message contains the terminal's connection session information, the terminal's data service management information, and the terminal's mobility restriction information. Based on the mobility restriction information, determine the services that the terminal can use after the handover and / or the services that the terminal can provide after the handover, and perform any of the following operations based on the connection session information and the data service management information: Send a service context update request message to the service management entity or session management entity; Send a connection session context update request message to the session management function entity and a data service management context update request message to the data management control function entity.

30. A processor-readable storage medium storing a program for causing a processor to perform the method of any one of claims 1 to 4, or the method of any one of claims 5 to 10, or the method of any one of claims 11 to 20, or the method of any one of claims 21 to 25.

Images