WO2023011612A1 - 移动性管理的方法及通信装置 - Google Patents

移动性管理的方法及通信装置 Download PDF

Info

Publication number
WO2023011612A1
WO2023011612A1 PCT/CN2022/110420 CN2022110420W WO2023011612A1 WO 2023011612 A1 WO2023011612 A1 WO 2023011612A1 CN 2022110420 W CN2022110420 W CN 2022110420W WO 2023011612 A1 WO2023011612 A1 WO 2023011612A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
cho
mobility
terminal device
conditional handover
Prior art date
Application number
PCT/CN2022/110420
Other languages
English (en)
French (fr)
Inventor
耿婷婷
郑午阳
陈君
奥鲁佛松亨里克
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP22852323.9A priority Critical patent/EP4380236A1/en
Publication of WO2023011612A1 publication Critical patent/WO2023011612A1/zh
Priority to US18/434,174 priority patent/US20240179605A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/36—Reselection control by user or terminal equipment
    • H04W36/362—Conditional handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0079—Transmission or use of information for re-establishing the radio link in case of hand-off failure or rejection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00833—Handover statistics
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00837—Determination of triggering parameters for hand-off
    • H04W36/008375—Determination of triggering parameters for hand-off based on historical data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H04W36/324—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by mobility data, e.g. speed data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/36—Reselection control by user or terminal equipment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment

Definitions

  • the present application relates to the field of communication technologies, and in particular to a mobility management method and a communication device.
  • Mobility scenarios in wireless communication systems include handover scenarios.
  • the terminal device can send a radio link failure report to the network side for the network side to obtain the reason for the connection failure, which can further be used for mobility management.
  • One handover scenario is conditional handover. In this scenario, even if the terminal device successfully completes the conditional handover, there is still a potential problem that the wireless link fails soon after the conditional handover is completed, or the handover is successful. How to make the network equipment in such a scenario Obtaining the mobility parameters that need to be optimized is an urgent problem to be solved.
  • Embodiments of the present application provide a mobility management method and device, so that network equipment can obtain mobility parameters that need to be optimized, further, so as to perform reasonable mobility management, improve mobility robustness, and improve user experience .
  • the first aspect provides a mobility management method. It can be understood that the method of the first aspect can be executed by a first device, and the first device can be a first network device or be able to support the first network device to implement the method A communication device for the desired function, such as a chip or a circuit or a system-on-a-chip. Taking the implementation of the method by the first network device as an example, the method may include:
  • the first network device sends the conditional handover configuration information of the terminal device to the second network device, and after obtaining the mobility report, the first network device requests the second network device for the conditional handover configuration information of the terminal device through a first message , the first network device receives a corresponding response message from the second network device.
  • the network device can obtain the mobility parameters that need to be optimized, and further, it can perform reasonable mobility management, improve mobility robustness, and improve user experience.
  • the first network device before the first network device sends conditional handover configuration information of the terminal device to the second network device, the first network device receives a handover success message from the second network device, The handover success message indicates that the terminal device successfully completes the conditional handover and accesses the second network device.
  • conditional handover configuration information of the terminal device is stored on the second network device, or the second network device can obtain the conditional handover configuration information of the terminal device through other means
  • the first network device may receive conditional handover configuration information from the second network device, and further, may use the received conditional handover configuration information for optimization of mobility parameters. If the conditional switching configuration information of the terminal device is not stored or cannot be obtained on the second network device, then the first network device will receive information indicating that the conditional switching configuration information request fails from the second network device. Optionally, the first The network device can discard the received mobility report, which can save the storage space of the terminal device.
  • the second aspect further provides a mobility management method, the method of the second aspect can be executed by a second device, and the second device can be a second network device or be able to support the second network device to implement the functions required by the method communication devices, such as chips or circuits or chip systems.
  • the method may include:
  • the second network device receives the conditional switching configuration information of the terminal device from the first network device, the second network device receives a first message from the first network device, the first message requests the conditional switching configuration information of the terminal device, the The second network device sends a response message to the first message to the first network device.
  • the network device can obtain the mobility parameters that need to be optimized, and further, it can perform reasonable mobility management, improve mobility robustness, and improve user experience.
  • the second network device before the second network device receives the conditional handover configuration information of the terminal device sent by the first network device, the second network device sends a handover success message to the first network device , the handover success message indicates that the terminal device successfully completes the conditional handover and accesses the second network device.
  • conditional handover configuration information of the terminal device is stored on the second network device, or the second network device can obtain the conditional handover configuration information of the terminal device through other means, then The second network device may send conditional handover configuration information to the first network device, and further, the first network device may use the received conditional handover configuration information for optimization of mobility parameters. If the conditional switching configuration information of the terminal device is not stored or cannot be obtained on the second network device, then the second network device will send information indicating that the conditional switching configuration information request fails to the first network device. Optionally, the first network The device can discard the received mobility report, which can save the storage space of the terminal device.
  • the conditional handover configuration information includes the conditional handover information of one or more candidate cells configured by the first network device for the terminal device; or, the conditional handover configuration information includes Mobility information, where the mobility information is used to indicate the mobility identifier or index corresponding to the conditional handover mobility parameter of the cell configured for the terminal device, so that the indication of CHO configuration information can be simplified and the efficiency can be improved. It can be understood that the conditional handover configuration information may not be limited to the method in the first or second aspect.
  • the above-mentioned first message carries the identification information of the terminal device, or the identification information of the terminal device and time information related to the conditional handover, so that it can be used by the target network device according to The above information determines the correct terminal device, and then determines the corresponding CHO configuration information.
  • the time information related to the conditional handover indicates the time information when the terminal device completes the conditional handover, and/or, the information of at least one message related to the execution of the conditional handover between the first network device and the second network device time information.
  • a third aspect further provides a mobility management method, the method of the third aspect can be executed by a third device, and the third device can be a third network device or be able to support the third network device to implement the functions required by the method communication device, such as a chip or a circuit or a chip system, wherein the third network device may be a source network device or other network devices.
  • the method may include: receiving a mobility report from the terminal device, identifying the target network device for which the terminal device has successfully completed conditional handover according to the received mobility report, and forcing the target network device to Send received mobility reports.
  • a fourth aspect further provides a mobility management method, the method of the fourth aspect can be executed by a third device, and the third device can be a third network device or be able to support the third network device to implement the functions required by the method communication device, such as a chip or a circuit or a chip system, wherein the third network device may be a source network device or other network devices.
  • the method may include receiving a mobility report from the terminal device, and sending the mobility report to the conditional handover target network where a second connection failure occurs and the connection failure type is a wireless link failure equipment.
  • some possible implementations further include receiving a mobility report from the terminal device and information indicating forwarding cells, where the mobility report is in the encoding format of the first system or standard, The cell where the terminal equipment is located when receiving the mobility report belongs to the second system or standard.
  • information indicating the priority order of forwarding cells may also be received from the terminal device.
  • the foregoing mobility report is carried in the message in the form of a container.
  • the information of the forwarding cell and the indication information of the priority order of the forwarding cell may be outside the container in the above message. It can be understood that, the above scheme of indicating the information of the forwarding cell and/or the information indicating the priority order of the forwarding cell is not limited to the method applicable to the third aspect or the fourth aspect.
  • the method of the third aspect or the fourth aspect above defines a forwarding mechanism of the mobility report between the receiving network device and the target network device, so that the mobility report must be forwarded by the receiving network device to the conditional handover target network device, so that the condition
  • the handover target network device may have the opportunity to send conditional handover configuration information to the source network device, so that the source network device can obtain the corresponding conditional handover configuration information, so as to perform reasonable mobility management, improve mobility robustness, and improve user experience.
  • a mobility management method is also provided, and the method provides a storage mechanism for conditional handover configuration information.
  • the method in the fifth aspect may be executed by a first device, and the first device may be a first network device or a communication device capable of supporting the first network device to implement functions required by the method, such as a chip or a circuit or a chip system.
  • the method may include: first determining that no handover success message has been received from the second network device, or determining that receiving a notification from the second network device indicating that the terminal device has stored mobility
  • the instruction information of the report saves the condition configuration information of the terminal device.
  • a mobility management method is also provided, and the method provides a storage mechanism for conditional handover configuration information.
  • the method in the sixth aspect may be performed by a first device, and the first device may be a first network device or a communication device capable of supporting the first network device to implement functions required by the method, such as a chip or a circuit or a chip system.
  • the method may include: receiving instruction information from the second network device, the instruction information indicating to save the conditional handover configuration information of the terminal device and the instruction information is that the second network device is in the first If it is detected that the connection with the conditional handover target cell fails within the running time of the timer, then the conditional handover configuration information of the terminal device is saved.
  • a mobility management method is also provided, and the method provides a storage mechanism for conditional handover configuration information.
  • the method in the seventh aspect may be executed by the first device, and the first device may be the first network device or a communication device capable of supporting the first network device to implement the functions required by the method, such as a chip or a circuit or a chip system.
  • the method may include: determining that the conditional handover of the terminal device fails, and saving the conditional handover configuration information of the terminal device.
  • a mobility management method which provides a storage mechanism for conditional handover configuration information.
  • the method in the eighth aspect may be performed by the first device, and the first device may be the first network device or a communication device capable of supporting the first network device to implement the functions required by the method, such as a chip or a circuit or a chip system.
  • the method may include: after receiving the handover success message from the second network device, starting a second timer, if the second timer expires, no message from the second network device is received The context release message of the terminal device saves the conditional switching configuration information of the terminal device.
  • an indication message is received from the second network device indicating that the terminal device side stores a mobility report, or an indication information is received from the second network device indicating that the terminal device and the second network
  • the indication information of connection failure between devices saves the conditional switching configuration information of the terminal device.
  • an indication message is received from the second network device indicating that the terminal device side stores a mobility report, or an indication information is received from the second network device indicating that the terminal device and the second The second timer may be stopped for the indication information of connection failure between network devices.
  • a mobility management method is also provided, and the method provides a storage mechanism for conditional handover configuration information.
  • the method in the ninth aspect may be executed by a first device, and the first device may be a first network device or a communication device capable of supporting the first network device to implement functions required by the method, such as a chip or a circuit or a chip system.
  • the method may include: after receiving the terminal device context release message from the second network device, starting a third timer, if the third timer is running within the running time, receiving the message from the second network device.
  • the network device indicates that the terminal device side stores the indication information of the mobility report, or receives the indication information from the second network device indicating that the connection between the terminal device and the second network device fails, and saves the conditional handover configuration information of the terminal device.
  • an indication message is received from the second network device indicating that the terminal device side stores a mobility report, or an indication information is received from the second network device indicating that the terminal device and the second
  • the third timer may be stopped for the indication information of connection failure between network devices.
  • a mobility management method is also provided, the method in the tenth aspect can be executed by a second device, and the second device can be a second network device or be able to support the second network device to implement the functions required by the method communication devices, such as chips or circuits or chip systems.
  • the method may include: starting the first timer after the terminal device successfully completes the conditional handover.
  • the connection between the terminal device and the serving cell fails, send to the first network device information indicating that the first network device saves the conditional handover configuration information; or, If it is determined that within the running time of the first timer, a connection failure between the terminal device and the serving cell (conditional handover target cell) is detected, no handover success message or terminal device context release message is sent to the first network device.
  • a handover success message or a terminal device context release message may be sent to the first network device.
  • failure of the terminal device and the serving cell is detected, and the second network device stops the first timer.
  • a mobility management method is also provided, the method in the eleventh aspect can be executed by a communication device, and the communication device can be a terminal device or a device capable of supporting the terminal device to implement the functions required by the method, For example a chip or a circuit or a system on a chip.
  • the method may include: the terminal device sends a mobility report and information indicating forwarding cell information to a receiving network device, wherein the mobility report is in a coding format of the first system or standard, and sending the The cell where the terminal device is located at the time of the mobility report belongs to the second system or standard.
  • the receiving network device can be assisted to better forward the mobility report.
  • the terminal device may also indicate to the receiving network device the information of the priority order of the cells to be forwarded.
  • the mobility report may be carried in a message in the form of a container and sent to the receiving network device.
  • the information of the forwarding cell and the indication information of the priority order of the forwarding cell may be outside the container in the above message.
  • a communication device in a twelfth aspect, has a function of implementing the actions or steps in any one of the methods from the first aspect to the tenth aspect above.
  • the communication device may be a network device or a component (such as a chip or a circuit) applicable to a network device.
  • the functions may be implemented by hardware, or may be implemented by executing corresponding software through hardware.
  • Hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • a communication device in a thirteenth aspect, has the function of implementing the actions or steps in the method of the eleventh aspect above.
  • the communication device may be a terminal device or a component (such as a chip or a circuit) applicable to a terminal device.
  • the functions may be implemented by hardware, or may be implemented by executing corresponding software through hardware.
  • Hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • a communication device in a fourteenth aspect, is provided, and the communication device may be a communication device that implements any one method in the first aspect to the eleventh aspect above.
  • the communications device includes a processor and memory.
  • the memory is used to store computer programs or instructions or data
  • the processor is coupled to the memory, and when the processor reads the computer programs or instructions or data, the communication device is made to execute the method in any aspect.
  • the communication device may further include a communication interface.
  • the communication interface may be a transceiver in the communication device.
  • the transceiver can be used for the communication device to communicate with other devices.
  • the embodiment of the present application provides a chip system, the chip system includes a processor, configured to implement any method in the first aspect to the eleventh aspect.
  • the chip system further includes a memory for storing program instructions and/or data.
  • the system-on-a-chip may consist of chips, or may include chips and other discrete devices.
  • the embodiment of the present application provides a communication system, where the system includes at least one of a first network device, a second network device, a third network device, and a terminal device.
  • a computer program product includes: computer program code, when the computer program code is executed, any method in the above aspects is executed.
  • the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, any method in the above-mentioned aspects is implemented.
  • FIG. 1 is an application scenario of an embodiment of the present application
  • FIG. 2 is a schematic flow diagram of a source network device obtaining conditional switching configuration information according to an embodiment of the present application
  • FIG. 3 is a schematic flowchart of an example of a mobility management method according to an embodiment of the present application.
  • FIG. 4 is a flowchart of another example of a mobility management method according to an embodiment of the present application.
  • FIG. 5 is a flowchart of another example of a mobility management method according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a communication device according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of another communication device according to an embodiment of the present application.
  • At least one means one or more, and “multiple” means two or more.
  • “And/or” describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the contextual objects are an “or” relationship.
  • “At least one (item) of the following” or similar expressions refer to any combination of these items, including any combination of single item(s) or plural item(s).
  • At least one item (unit) of a, b or c can represent: a, b, c, a and b, a and c, b and c, or a, b and c, wherein a, b, c
  • Each of the can be itself an element, or a collection containing one or more elements.
  • transmit may include sending and/or receiving and may be a noun or a verb.
  • the terminal device is a device with a wireless transceiver function, which may be called a terminal (terminal), user equipment (user equipment, UE), mobile station (mobile station, MS), mobile terminal (mobile terminal, MT) ), access terminal equipment, vehicle terminal equipment, industrial control terminal equipment, UE unit, UE station, mobile station, remote station, remote terminal equipment, mobile equipment, UE terminal equipment, wireless communication equipment, UE agent or UE device, etc.
  • Terminal equipment can be fixed or mobile.
  • the terminal device may support at least one wireless communication technology, such as LTE, NR, wideband code division multiple access (wideband code division multiple access, WCDMA), and the like.
  • the terminal device may be a mobile phone (mobile phone), a tablet computer (pad), a desktop computer, a notebook computer, an all-in-one computer, a vehicle terminal, a virtual reality (virtual reality, VR) terminal device, an augmented reality (augmented reality, AR) terminal Equipment, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, wireless terminals in smart grid, transportation safety Wireless terminals in (transportation safety), wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless Local loop (wireless local loop, WLL) stations, personal digital assistants (personal digital assistant, PDA), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, wearable devices, future mobile communications
  • the terminal may also be a device capable of transmitting
  • the network device in the embodiment of the present application is a device that provides a wireless communication function for a terminal device, and may also be referred to as an access network device, a radio access network (radio access network, RAN) device, or the like.
  • an access network device a radio access network (radio access network, RAN) device, or the like.
  • RAN radio access network
  • the network equipment includes but is not limited to: a next-generation base station (generation nodeB, gNB), an evolved node B (evolved node B, eNB) in a fifth-generation mobile communication system (5th-generation, 5G), a wireless network control radio network controller (RNC), node B (node B, NB), base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved node B, or home node B, HNB), baseband unit (baseband unit, BBU), transmitting and receiving point (transmitting and receiving point, TRP), transmitting point (transmitting point, TP), mobile switching center, etc.
  • generation nodeB generation nodeB, gNB
  • an evolved node B evolved node B
  • eNB evolved node B
  • 5th-generation 5G
  • 5G fifth-generation mobile communication system
  • RNC wireless network control radio network controller
  • node B node B
  • the network device can also be a wireless controller, a centralized unit (centralized unit, CU) and/or a distributed unit (distributed unit, DU) in a cloud radio access network (cloud radio access network, CRAN) scenario, or the network device can be Relay stations, access points, vehicle-mounted devices, terminal devices, wearable devices, and network devices in future mobile communications or network devices in future evolved PLMNs, etc.
  • the network device may also be an apparatus having a wireless communication function for the terminal device, such as a chip system.
  • the system-on-a-chip may include a chip, and may also include other discrete devices.
  • CU and DU can be physically separated or deployed together. Multiple DUs can share one CU. One DU can also be connected to multiple CUs. The CU and the DU may be connected through an interface, such as an F1 interface. CU and DU can be divided according to the protocol layer of the wireless network. For example, one of the possible division methods is: CU is used to execute the radio resource control (Radio Resource Control, RRC) layer, service data adaptation protocol (service data adaptation protocol, SDAP) layer and packet data convergence layer protocol (packet data convergence) Protocol, PDCP) layer functions, and DU is used to perform functions such as radio link control (radio link control, RLC) layer, media access control (media access control, MAC) layer, physical (physical) layer, etc.
  • RRC Radio Resource Control
  • SDAP service data adaptation protocol
  • packet data convergence layer protocol packet data convergence layer protocol
  • PDCP packet data convergence protocol
  • DU is used to perform functions such as radio link control (radio link control, RLC) layer, media access control (media access
  • a CU or DU can be divided into functions with more protocol layers.
  • a CU or DU can also be divided into some processing functions having a protocol layer.
  • some functions of the RLC layer and functions of the protocol layers above the RLC layer are set in the CU, and the remaining functions of the RLC layer and functions of the protocol layers below the RLC layer are set in the DU.
  • the functions of the CU or DU may also be divided according to service types or other system requirements.
  • the functions whose processing time needs to meet the delay requirement are set in the DU, and the functions that do not need to meet the delay requirement are set in the CU.
  • the network architecture shown in the above figure can be applied to the 5G communication system, and it can also share one or more components or resources with the LTE system.
  • the CU may also have one or more functions of the core network.
  • One or more CUs can be set centrally or separately.
  • the CU can be set on the network side to facilitate centralized management.
  • the DU can have multiple radio functions, or the radio functions can be set remotely.
  • the functions of the CU can be implemented by one entity or by different entities.
  • the functions of the CU can be further divided, for example, the control plane (control panel, CP) and the user plane (user panel, UP) are separated, that is, the control plane (CU-CP) of the CU and the user plane (CU-CP) of the CU -UP).
  • the CU-CP and CU-UP can be implemented by different functional entities, and the CU-CP and CU-UP can be coupled with the DU to jointly complete the functions of the access network device.
  • a terminal device can communicate with access network devices of different technologies. For example, a terminal device can communicate with an access network device supporting long term evolution (LTE), or with an access network device supporting 5G. It can communicate with access network equipment supporting LTE and access network equipment supporting 5G at the same time.
  • LTE long term evolution
  • 5G access network device supporting 5G
  • the embodiment of this application is not limited.
  • a core network device may refer to a device in a core network (core network, CN) that provides service support for a terminal.
  • core network core network
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • AMF entities may also be referred to as AMF network elements or AMF functional entities
  • SMF entities may also be referred to as SMF network elements or SMF functions entity etc.
  • the handover scenarios involved in the embodiments of the present application can be divided into common handover (also called traditional handover), conditional handover (conditional handover, CHO) and dual active protocol stack (dual active protocol stack, DAPS) handover.
  • common handover also called traditional handover
  • conditional handover conditional handover
  • dual active protocol stack dual active protocol stack
  • normal handover refers to the process in which the terminal device receives the configuration delivered by the source network device, completes reconfiguration on the target network device, accesses the target base station, and disconnects from the source network device.
  • DAPS handover means that the terminal device still maintains the connection with the source network device after receiving the handover command, and at the same time tries to establish a connection with the target network device. Therefore, it can be considered that in the DAPS handover scenario, the terminal device establishes connections with the source network device and the target network device respectively until the target network device instructs the terminal device to disconnect from the source network device. From the perspective of process, it can be divided into Xn based handover (Xn based handover) and NG based handover (NG based handover).
  • the Xn-based handover is an interactive handover request between the source network device and the target network device
  • the NG-based handover is that the source network device sends a handover request to the authorization management field (authentication management field, AMF), and the AMF sends a handover request to the target network device.
  • AMF authentication management field
  • the source network device sends CHO configuration information to the terminal device.
  • the terminal device judges whether each CHO candidate cell satisfies the handover trigger condition according to the CHO configuration information, and selects the CHO candidate cells that meet the handover trigger condition As the target cell, then perform a random access process with the determined target cell.
  • the terminal device sends an RRC message (such as an RRC reconfiguration complete message) to the network device to which the target cell belongs (ie, the target network device). , to notify the target network device that the conditional switching is completed.
  • RRC message such as an RRC reconfiguration complete message
  • the MRO Mobility Robustness Optimization, mobile robustness optimization
  • the existing MRO mechanism records the parameters in the mobility process by introducing the terminal, records the corresponding mobility report, and sends the above report to the network device , so that the network device can better adjust the parameters related to the mobility.
  • the mobility report includes a successful mobility report (including various successful mobility reports, such as a successful ordinary handover report, a successful CHO report, or any one or more of other successful reports), a failure report ( At least one report including any one or more of RLF report or other failure reports), random access report, connection failure report, etc.
  • the process of the terminal device recording the RLF report and sending the RLF report, and forwarding the RLF report between network devices can be, for example, as follows:
  • the terminal device detects the RLF, records the RLF report, and sends the RLF report to the connected network device (such as the third gNB); the third gNB sends the RLF report to the network device corresponding to the cell where the wireless link fails (such as the target gNB), the target gNB determines whether it needs to forward the RLF report to the network device corresponding to the source cell (such as the source gNB), if it needs to forward the RLF report to the source gNB, the target gNB sends a handover report (HO Report) message to the source gNB, HO Report
  • the message can carry RLF report and at least one of the mobility information of the source gNB.
  • the mobility information may be sent by the source gNB to the target gNB in a handover request message.
  • the RLF report can include at least one kind of information:
  • Failed PCell ID the terminal device detects RLF or timer expired (expired) primary cell information, or HOF target primary cell information.
  • the timer may be, for example, a timer started after the terminal device sends a measurement report. If the terminal device has not received a switching command after the timer expires, it may be considered that a connection failure has occurred.
  • the timer may be T312, for example.
  • the failed primary cell identifier may not be included in the connection failure information, but the failed cell identifier (failedCellId) may be included.
  • the failed cell identifier refers to the information of the cell where the terminal device detects link failure or the timer expires, or the information of the target cell where the handover fails, which is not limited in this embodiment of the present application.
  • connection failure may be RLF or HOF or expiration of a timer (such as T312) or competition failure (such as failure of listen before talk (LBT)).
  • T312 timer
  • competition failure such as failure of listen before talk (LBT)
  • the connection failure type may also be simply referred to as the failure type.
  • Previous primary cell identifier information of the previous primary cell that the terminal device received a handover command last time.
  • connection failure information may not include the previous Pcell ID (previousPcellId), but include the previous cell ID (previousCellId).
  • the previous cell identifier is the information of the previous cell that the terminal device received the handover command last time, which is not limited in this embodiment of the present application.
  • Reestablishment cell identifier information about the cell that attempts to reestablish after the connection fails.
  • Connection failure time the length of time from the last (or most recent) receipt of a switching command (or reconfiguration message) to the connection failure.
  • Time since failure the length of time to start recording when the connection fails. Generally refers to the length of time from connection failure to reporting failure report.
  • Reasons for connection failure may include HOF, RLF, reconfiguration synchronization failure, NR switching failure to other systems, integrity check failure (integrity check failure) or RRC connection reconnection Configuration failed.
  • Location information information about the location where the terminal device fails to connect.
  • Random access information (ra-InformationCommon): information about random access performed by the terminal equipment in the target primary cell.
  • Measurement result it may be a measurement result of a cell and/or a beam, and the measurement result may include a measurement result of a serving cell and/or a neighboring cell.
  • Time information (timeCHOcfgExe) from receiving CHO configuration to triggering CHO execution.
  • CHO cell information cell information used to indicate that the UE has successfully completed CHO.
  • Handover type CHO.
  • Reconnection cell information cell information used to instruct the terminal device to return to the connected state after connection failure or reestablishment failure. Understandably, if the reconstruction is successful, the terminal device may not record the information.
  • the terminal device may record a mobility report.
  • the terminal device may also record the mobility report.
  • the mobility reports recorded in the above situations can all be referred to as mobility reports related to CHO.
  • the source network device may determine whether to optimize the corresponding mobility parameters based on the corresponding CHO configuration information (ie, the source network device configures the terminal device to perform this CHO configuration information).
  • Figure 1 is an application scenario of the embodiment of this application.
  • the terminal device moves from the coverage area of the network device 1 to the coverage area of the network device 2 .
  • the terminal device is handed over from cell 1 of network device 1 to cell 2 of network device 2 .
  • network device 1 may be called a source network device, and cell 1 may be called a source cell.
  • the network device 2 may be called a target network device, and the cell 2 may be called a target cell.
  • This application scenario is applicable to various wireless communication systems, such as: long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), Worldwide interoperability for microwave access (WiMAX) communication system, 5G system or new radio (new radio, NR), or future evolution system, etc.
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD time division duplex
  • WiMAX Worldwide interoperability for microwave access
  • the terminal device and/or the network device may perform some or all of the steps in the embodiment of the present application, these steps or operations are only examples, and the embodiment of the present application may also perform other operations or various Operational deformation.
  • each step may be performed in a different order presented in the embodiment of the present application, and it may not be necessary to perform all operations in the embodiment of the present application.
  • the source network device receives the After the handover success (HO SUCCESS) message of the incoming target network equipment (called CHO network equipment), send the stored CHO configuration information to the CHO target network equipment, and the CHO target network equipment saves the received CHO configuration information.
  • HO SUCCESS handover success
  • the CHO target network device When the CHO target network device receives a mobility report (such as an RLF report) from a terminal device or other network device (such as a third network device), the CHO target network device sends the saved CHO configuration information to the source network device, such as
  • the above CHO configuration information may be carried in the HO report sent by the CHO target network device to the source network device, and the embodiment of the present application does not limit the manner in which the CHO target network device sends the CHO configuration information to the source network device.
  • the CHO target network device may not receive the CHO-related mobility report of the terminal device. Since the terminal can perform a CHO re-establishment after detecting the connection failure, there may be a terminal device detecting the first connection failure in the source cell (the failure type is RLF) or the first connection between the terminal device and the first CHO target cell After the failure (the failure type is HOF), the terminal device successfully performs CHO re-establishment or a second connection failure (failure type is RLF) occurs soon after the terminal device successfully performs CHO re-establishment.
  • the failure type is RLF
  • the failure type is HOF
  • the network device receiving the RLF report may send a mobility report (such as an RLF report) to the source network device instead of sending a mobility report to the CHO target network device.
  • a mobility management method is provided, which may include:
  • the terminal device successfully completes the CHO and accesses the CHO target cell.
  • the method of "the terminal device successfully completes CHO and accesses the CHO target cell” can be: the terminal device successfully completes CHO and accesses the CHO target cell in a conditional handover manner, for example, the terminal device determines that the trigger condition corresponding to the CHO candidate cell is met and Successfully execute CHO and access the CHO target cell by means of conditional handover; or, the terminal device can successfully complete CHO and access the CHO target cell by means of reconstruction, for example, the terminal device detects that the connection fails, executes cell selection, and determines After the CHO candidate cell becomes the target cell, the CHO is successfully executed, and the CHO target cell is accessed in a reestablishment manner.
  • the terminal device successfully completes the CHO and accesses the CHO target cell can also mean “the terminal device successfully completes the CHO and accesses the CHO target network device”.
  • the CHO target network device refers to the network device to which the terminal device successfully completes CHO access.
  • the terminal device After receiving the CHO configuration information sent by the source network device, judge whether each CHO candidate cell meets the handover trigger condition according to the CHO configuration information, and use the CHO candidate cell that meets the handover trigger condition as the target cell, or after the terminal device detects that the connection fails Perform cell selection, determine the CHO candidate cell as the target cell, and then perform a random access process with the determined target cell.
  • the terminal device sends an RRC message (such as an RRC reconfiguration complete message) to the network device to which the target cell belongs (ie, the CHO target network device) to notify the CHO target network device that the conditional handover is completed.
  • an RRC message such as an RRC reconfiguration complete message
  • the source network device may further include: a preparation process for conditional handover between the source network device and at least one candidate target network device.
  • the preparation process may include, for example: the source network device determines at least one candidate target cell (for example, according to a measurement report), the source network device sends a handover request to at least one candidate target network device corresponding to the at least one candidate target cell, and the at least one candidate target cell.
  • the network device executes the admission control process, allowing the candidate target network device to be accessed by the terminal device to send a handover request response message to the source network device, and the source network device determines CHO configuration information according to the handover request response message.
  • the source network device receives a handover success message sent by the CHO target network device.
  • the CHO target network device may send a handover success (HO SUCCESS) message to the source network device.
  • the handover success message is used to indicate to the source network device that the terminal device successfully completes the CHO and accesses the CHO target network device.
  • the handover success message is used as an example for the message name, and the embodiment of the present application does not limit the name of the message indicating the handover success.
  • the source network device sends conditional handover (CHO) configuration information to the CHO target network device.
  • CHO conditional handover
  • the CHO configuration information is CHO configuration information related to the terminal device.
  • the source network device releases (or clears or discards) the CHO configuration information, for example, the source network device sends the CHO configuration information to the CHO target network device.
  • the source network device receives the terminal device context release message sent by the CHO target network device, and the source network device releases (or clears or discards) the CHO configuration information.
  • the source network device can also release part of the CHO configuration information or release the CHO configuration information at other times.
  • the source network device configures the CHO after sending the CHO configuration information to the CHO target network device.
  • the processing method of the information is not limited.
  • the CHO target network device may save the CHO configuration information.
  • the CHO configuration information may include CHO information of one or more candidate cells configured by the source network device for the terminal device.
  • the CHO information of the candidate cell may include information indicating the identity information of the candidate cell and one or more corresponding handover trigger conditions (or also called execution conditions).
  • the information used to indicate the identity information of the candidate cell may be a CHO configuration identity or CHO candidate cell information.
  • the cell information can be cell global identifier (CGI), physical cell identifier (PCI) and frequency point, cell identifier (cell ID), non-public network identifier (non-public network ID) of the cell.
  • CGI may include public land mobile network (public land mobile network, PLMN ID) and cell ID.
  • the information of the cell may also include a tracking area code (tracking area code, TAC) and/or identification information of a network device to which the cell belongs, such as a global network device identification.
  • TAC tracking area code
  • CHO information of the candidate cell may also be referred to as a CHO mobility parameter.
  • the CHO configuration information may be at least one piece of mobility information configured by the source network device for the terminal device.
  • the mobility information may be a mobility identifier or index corresponding to the CHO mobility parameters of the cell.
  • the mobility information may be in the form of a list (list), or in other forms, which is not limited in this embodiment of the present application.
  • the source network device may save the CHO mobility parameters corresponding to each cell of at least one cell, and the CHO mobility parameters of each cell correspond to the mobility information, that is to say, the corresponding cell can be determined or indexed through the mobility information CHO mobility parameters.
  • the mobility information may be a cell identity, or the mobility information may also be an index of a CHO mobility parameter.
  • the source network device may store the CHO mobility parameters and corresponding mobility information of each cell all the time or within a period of time, so that the corresponding CHO mobility parameters may be subsequently determined through the mobility information.
  • the indication of the CHO configuration information can be simplified, the storage overhead of the CHO configuration information on the network device can be reduced, and the efficiency can be improved.
  • conditional handover configuration information may include conditional handover information of one or more candidate cells configured by the first network device for the terminal device and at least one of the conditional handover information configured by the source network device for the terminal device. mobility information.
  • the CHO configuration information may also be referred to as CHO context information.
  • the CHO configuration information described here can also be applied to the process of the embodiment shown in FIG. 2 , that is, the source network device can send the stored CHO configuration information to the CHO target network device.
  • the CHO configuration information sent by the source network device to the terminal device may also be the CHO configuration information described above.
  • S304. The source network device acquires a mobility report.
  • the source network device may obtain the mobility report from a network device different from the CHO target network device, and the network device different from the CHO target network device may be a third network device different from the source network device device, which can also be a source network device. After the source network device determines that the mobility report is a mobility report related to CHO, S305 and subsequent steps may be executed.
  • the source network device sends a first message to the CHO target network device, requesting CHO configuration information corresponding to the terminal device.
  • the first message may be a CHO configuration information request message, and the CHO configuration information of the terminal device may be requested from the CHO target network device through the first message.
  • the embodiment of the present application does not limit the message name and/or information element structure of the first message.
  • the first message carries information for the CHO target network device to determine the terminal device.
  • the first message may include identification information of the terminal device, or identification information of the terminal device and time information related to the CHO.
  • the identification information of the terminal device includes at least one of the following: the cell radio network temporary identifier (C-RNTI) of the terminal device in the source cell, and the C-RNTI of the CHO target cell where the terminal device successfully completes CHO access.
  • C-RNTI cell radio network temporary identifier
  • RNT target C-RNTI
  • the identifier Source NG-RAN node UE XnAP ID
  • the CHO target network device is all
  • the above CHO-related time information may indicate the time information of the terminal device completing CHO in the target cell, and/or the time information of at least one message related to the execution of CHO between the source network device and the CHO target network device, such as the source network device Send the time information of the CHO request (handover request) to the CHO target network device, the source network device receives the time information of the CHO request confirmation (handover request acknowledge) message from the CHO target network device, and the source network device receives the handover from the CHO target network device
  • the first message may also indicate the type of time information indicated above, for the CHO target network device to determine a message corresponding to the time information.
  • the CHO target network device After receiving the identification information of the terminal device, or the identification information of the terminal device and the time information related to CHO, the CHO target network device can determine the Whether the CHO configuration information of the corresponding terminal device is stored or can be acquired, that is, the above information can be used by the target network device to determine the correct terminal device, and then determine the corresponding CHO configuration information. For example, the CHO target network device compares the identification information of the terminal device from the source network device with the identification information of the terminal device corresponding to the stored CHO configuration information. If they are consistent, the CHO target network device determines that the corresponding terminal device has or can obtain CHO configuration information.
  • the CHO target network device After the CHO target network device receives the identification information of the terminal device from the source network device and the time information related to CHO, the CHO target network device compares the above information with the identification information of the terminal device corresponding to the stored CHO configuration information and Whether the time information related to the CHO is consistent or related, if consistent or related, the CHO target network device determines that the CHO configuration information of the corresponding terminal device is stored or can be obtained.
  • a possible situation of association may be, for example, that the CHO target network device determines that the received CHO-related time information and the stored CHO-related time information belong to the same range or overlap in range.
  • step S306a can be executed, if the terminal is not stored on the CHO target network device or cannot be obtained.
  • step S306b can be executed. It can be understood that both S306a and S306b can be understood as a step of the CHO target network device sending a response message to the first message.
  • the CHO target network device sends the CHO configuration information of the terminal device to the source network device.
  • the source network device receives the CHO configuration information from the CHO target network device, so that it can be used for optimization of mobility parameters.
  • the source network device may determine that the CHO handover trigger condition of one or some cells needs to be adjusted in combination with the mobility report acquired in S304. It can be seen that in the embodiment of the present application, the source network device can obtain the corresponding CHO configuration information, so as to perform reasonable mobility management, improve mobility robustness, and improve user experience.
  • the CHO target network device may send the CHO configuration information of the terminal device to the terminal device through a CHO configuration request confirmation message.
  • the CHO target network device indicates to the source network device that the CHO configuration information request fails.
  • the second message may be used to indicate to the source network device that the CHO configuration information request fails.
  • the second message may be a CHO configuration request failure message, or other messages, and the embodiment of the present application does not limit the name and information element structure of the second message.
  • the second message may carry a failure cause (failure cause).
  • the failure reason may be "no context (no UE context)", “no CHO configuration (no CHO configuration)", “invalid UE ID (invalid UE ID)” or other information.
  • the source network device learns that the request for CHO configuration information has failed, that is to say, the CHO configuration information of the terminal device cannot be obtained from the CHO target network device.
  • the device can discard the received mobility report, which can save the storage space of the terminal device.
  • the embodiment of the present application also provides a mobility management method.
  • the CHO target network device may not receive the CHO-related mobility report of the terminal device.
  • the transmission path of the mobility report is further optimized, that is, as long as the terminal device and the CHO target network device successfully complete CHO, no matter whether the terminal device detects a connection failure, the network device that receives the mobility report (referred to as the receiving network device for short) ) all send a mobility report to the target network device that has successfully completed the CHO.
  • the receiving network device may be a third network device, or may be a source network device.
  • FIG. 4 another embodiment of the present application provides a mobility management method, which may include:
  • the terminal device successfully completes the CHO and accesses the CHO target cell.
  • the source network device receives a handover success message sent by the CHO target network device.
  • the source network device sends CHO configuration information to the CHO target network device.
  • the receiving network device receives the mobility report from the terminal device.
  • the receiving network device After receiving the mobility report sent by the terminal device, the receiving network device can identify the CHO target network device on which the terminal device has successfully completed the CHO, and executes S405.
  • a possible scenario is that the terminal device detects the first connection failure (the first connection failure can be RLF between the terminal device and the source cell, or HOF between the terminal device and the first CHO target cell that satisfies the CHO trigger condition) , select the CHO target cell as the target cell, the terminal device successfully performs CHO reconstruction, and accesses the CHO target cell; or, another possible scenario is that the terminal device does not detect any connection failure, the terminal device performs CHO handover, and accesses the CHO target cell. CHO target cells that meet the CHO triggering conditions.
  • the terminal device may not detect the RLF with the CHO target cell, or may detect the RLF with the CHO target cell.
  • the receiving network device can use the CHO target cell information in the mobility report (such as the failed primary cell identifier), the failure type (RLF, this failure type is used to indicate that the UE has successfully completed the CHO to the primary cell and the RLF), receiving at least one of the time information from CHO configuration to triggering CHO execution (used to determine that the way the UE accesses the CHO target cell is CHO handover), and determining the CHO target network device corresponding to the CHO target cell; for example, receiving According to the CHO cell information, the network device determines the cell information of the terminal device successfully completing the CHO, thereby determining the CHO target network device corresponding to the CHO target cell; for another example, the receiving network device according to the re-establishment cell identity and handover type in the mobility report ( CHO) and the "reconnection cell information" in the mobility report determine that the re-established cell is the CHO target cell where the terminal device successfully performs CHO re-establishment, thereby determining the
  • “mandatory” means that the receiving network device determines that there is a CHO target cell that has successfully completed CHO according to the mobility report, and no matter whether the terminal device detects a radio link failure with the CHO target cell or not, it will report to the CHO target network device Send received mobility reports.
  • the receiving network device here may be a source network device or a third network device.
  • the CHO target network device sends the saved CHO configuration information to the source network device.
  • the CHO target network device may send the saved CHO configuration information to the source network device, or the CHO configuration information and the mobility report, or the CHO configuration information and the analysis information obtained based on the mobility report.
  • the CHO target network device may carry the above CHO configuration information in the HO report message sent to the source network device, and the embodiment of the present application does not limit the manner in which the CHO target network device sends the CHO configuration information to the source network device.
  • the mandatory forwarding mechanism of the mobility report between the receiving network device and the CHO target network device is introduced, so that the mobility report must be forwarded by the receiving network device to the CHO target network device, so that the CHO target network device can have Opportunity sends CHO configuration information to the source network device, so that the source network device can obtain the corresponding CHO configuration information, so as to perform reasonable mobility management, improve mobility robustness, and improve user experience.
  • the receiving network device may send the mobility report to the CHO target network device whose connection failure occurs for the second time and the connection failure type is RLF.
  • the possible scenario is: the terminal device detects the first Connection failure (the first connection failure can be RLF between the terminal device and the source cell, or HOF between the terminal device and the first CHO target cell that meets the CHO trigger conditions), perform cell selection, and select the CHO target cell as the target cell, after the terminal device successfully performs CHO re-establishment, the terminal device detects that the radio link with the CHO target cell fails. . That is, in S404, the receiving network device determines that the terminal device has detected two connection failures according to the information in the mobility report.
  • the HOF between the CHO target cells that trigger the condition, and the second connection failure is the RLF between the terminal device and the CHO target cell determined by the cell selection, the receiving network device determines to send to the CHO target cell corresponding to the second connection failure
  • the aforementioned CHO target network device sends a mobility report.
  • S405 may be replaced by the receiving network device sending a mobility report to the CHO target network device described in the CHO target cell corresponding to the second connection failure.
  • the terminal device considering cross-system or cross-standard mobility scenarios, if the mobility report generated by the terminal device is in the encoding format of the first system/standard, the terminal device will be in the second system/standard
  • the cell under the standard sends the mobility report to the receiving network device, and the terminal device can send the mobility report to the receiving network device in the form of a container.
  • the terminal device may also indicate the information of the forwarding target cell (referred to as the forwarding cell) outside the container.
  • the forwarding cell may be a source cell, a CHO target cell that successfully completes CHO, a CHO target cell that detects a second connection failure and the connection failure type is RLF, or at least one of a target cell that successfully completes CHO handover but detects RLF. It can be understood that, if the number of forwarding cells is greater than or equal to two, the terminal device may also indicate the priority order of the cells for forwarding the mobility report.
  • the terminal device when the terminal device detects the RLF with the source cell and successfully completes the CHO to the CHO target cell, the terminal device can instruct the receiving network device to first forward the mobility report to the CHO target network device to which the CHO target cell belongs, so that the mobility report can be forwarded to CHO target network device, the CHO target network device can determine the CHO configuration information of the terminal device according to the identification information of the terminal device in the mobility report, or the identification information of the terminal device and the time information related to CHO, and the CHO target network device can send the source The network device sends the CHO configuration information, and the mobility report or the analysis information based on the mobility report, so that the source network device can optimize the CHO configuration information according to the mobility report or the analysis information based on the mobility report, and improve Robustness of subsequent mobility management.
  • a mechanism for the source network device to save CHO configuration information is provided.
  • the source network device determines that it has not received the HANDOVER SUCCESS sent by the CHO target network device, or if the source network device determines that it has received the indication information from the CHO target network device indicating that the terminal device side stores a mobility report, the source network device saves the CHO configuration Information, that is to say, the source network device does not release the CHO configuration information or temporarily does not release the CHO configuration information. For example, the source network device can save the CHO configuration information for a period of time, such as 48h.
  • the It may include: a preparation process for conditional handover between the source network device and at least one candidate target network device, the source network device sends CHO configuration information to the terminal device, and the terminal device successfully completes CHO access to the CHO target cell according to the CHO configuration information.
  • the CHO target network device can start the first timer, and if the first timer is running, the CHO target network device detects that the terminal device The connection with the CHO target cell (that is, the current serving cell) fails (for example, the CHO target network device cannot receive the feedback information of the scheduled downlink data of the terminal device, or receives the failure indication information sent by other network devices, It is used to instruct the terminal device to rebuild on other network devices, etc.), the CHO target network device sends instruction information to the source network device, instructing the source network device to save the CHO configuration information of the terminal device, that is to say, the source network device does not release the CHO configuration information In other words, the CHO configuration information is not released temporarily.
  • the CHO target network device detects that the connection between the terminal device and the CHO target cell fails within the running time of the first timer, and the CHO target network device does not send a HANDOVER SUCCESS message or a UE Context Release message to the source network device, then The source network device will consider that the CHO fails, and the source network device saves the CHO configuration information of the terminal device, that is to say, the source network device does not release the CHO configuration information or temporarily does not release the CHO configuration information.
  • the CHO target network device may send a HANDOVER SUCCESS message or a UE Context Release message to the source network device. After receiving UE Context Release, the source network device releases the CHO configuration information of the terminal device.
  • the CHO target network device stops the first timer.
  • the source network device after the source network device receives the HANDOVER SUCCESS message from the CHO target network device, the source network device starts a second timer. If the second timer expires, the source network device does not receive the HANDOVER SUCCESS message from the CHO target network device. For the UE Context Release message of the network device, the source network device saves the CHO configuration information of the terminal device, that is to say, the source network device does not release the CHO configuration information or temporarily does not release the CHO configuration information.
  • the source network device receives indication information from the CHO target network device indicating that the terminal device side stores a mobility report, or the source network device receives an indication from the CHO target network device Indication information of connection failure between the terminal device and the CHO target network device, the source network device saves the CHO configuration information of the terminal device, that is to say, the source network device does not release the CHO configuration information or temporarily does not release the CHO configuration information.
  • the source network device receives indication information from the CHO target network device indicating that the terminal device side stores a mobility report, or the source network device receives a notification from the CHO target network device
  • the source network device may stop the second timer for the indication information indicating that the connection between the terminal device and the CHO target network device fails.
  • the source network device After the source network device receives the UE Context Release message sent by the CHO target network device, the source network device starts the third timer, and if the third timer is running, the source network device receives the UE Context Release message from the CHO target network device.
  • the target network device indicates that the terminal device side stores the indication information of the mobility report, or the source network device receives the indication information from the CHO target network device indicating that the connection between the terminal device and the CHO target network device fails, and the source network device saves the terminal device
  • the CHO configuration information that is to say, the source network device does not release the CHO configuration information or temporarily does not release the CHO configuration information.
  • the source network device receives indication information from the CHO target network device indicating that the terminal device side stores a mobility report, or the source network device receives a notification from the CHO target network device
  • the source network device may stop the third timer for the indication information indicating that the connection between the terminal device and the CHO target network device fails.
  • the above-mentioned running durations of the first timer, the second timer and the third timer may be configured by the network device, or may be predefined by the protocol. It can be understood that configuration manners of the first timer, the second timer and the third timer may be the same or different. Optionally, the running durations of the first timer, the second timer and the third timer may be the same or different. This embodiment of the present application does not limit it. In addition, Mode 3 or Mode 4 may also be implemented in combination with Mode 1 or Mode 2.
  • the network device can only save the CHO configuration information in the scenario of a connection failure or a potential connection failure during the mobility process, reducing the storage overhead of the network device .
  • the terminal device successfully completes the CHO and accesses the CHO target cell.
  • the CHO target network device starts a first timer.
  • the CHO target network device sends instruction information to the source network device, instructing the source network device to save the CHO configuration information of the terminal device.
  • the CHO target network device detects that the connection between the terminal device and the CHO target cell fails, and therefore executes S503.
  • the indication information may be an explicit indication whether to save the CHO configuration information of the terminal device, or an implicit indication that within the running time of the first timer, the CHO target network device detects a communication between the terminal device and the CHO target cell. The connection fails, so the source network device determines to save the CHO configuration information according to the instruction information.
  • the source network device saves the CHO configuration information.
  • the source network device after receiving the above indication information, the source network device does not release the CHO configuration information or temporarily does not release the CHO configuration information.
  • the source network device may further perform mobility management according to the mobility report and saved CHO configuration information.
  • the mobility report may be received by the source network device from the terminal device or other network devices or core network devices, which is not limited in this embodiment of the present application.
  • the source network device can determine whether to adjust the subsequent CHO configuration based on the saved CHO configuration information, so as to perform reasonable mobility management, improve mobility robustness, and improve user experience.
  • the interaction between network devices may be direct interaction or indirect interaction. That is to say, the source network device, the CHO target network device, and the third network device can be directly (for example, through the interface between the base station and the base station, such as the X2, Xn interface) or indirectly (for example, through the interface between the base station and the core network device) interface, such as S1 or NG interface) to complete the interaction.
  • the name of the message may be different, which is not limited in this embodiment of the present application.
  • Figure 3 illustrates that network devices can interact with each other as an example.
  • the source network device can pass the core network device Each message or information is sent to the CHO target network device.
  • the source network device sends the first message to the core network device through an interface with the core network device.
  • the source network device sends the first message to the core network device through the S1 or NG interface, and the core network device forwards the first message received from the source network device or the content in the first message to the CHO target network device.
  • the source network device may send the first message or the content in the first message to the CHO target network device through one of the following messages on the S1/NG interface: CHO configuration request message, uplink RAN configuration transmission (UPLINK RAN CONFIGURATION TRANSFER) message, base station configuration transmission (eNB CONFIGURATION TRANSFER) message or other messages.
  • the CHO target network device can send a response message to the core network device through one of the following messages: CHO configuration request confirmation message, CHO configuration request failure message, uplink RAN configuration transfer (UPLINK RAN CONFIGURATION TRANSFER) message, base station configuration transfer (eNB CONFIGURATION TRANSFER) message or other messages.
  • the source network device can receive the response message from the CHO target network device through one of the following messages on the S1/NG/N2 interface: CHO configuration request confirmation message, CHO configuration request failure message, downlink RAN configuration transmission (DOWNLIKN RAN CONFIGURATION TRANSFER) message, core network equipment configuration transfer (MME CONFIGURATION TRANSFER) message or other messages.
  • the source network device and the target network device may be connected to the same core network device, or may be connected to different core network devices respectively.
  • the connected core network devices may belong to the same standard or different standards.
  • the core network device connected to the source network device is AMF (access and mobility management function, access mobility management function), and the target network
  • the core network device to which the device is connected may be an MME (mobility management entity, mobile management module).
  • the source network device in each of the foregoing embodiments may also be called a first network device, and the CHO target network device may be called a second network device.
  • each network element or device may include a hardware structure and/or a software module, and realize the above-mentioned functions in the form of a hardware structure, a software module, or a hardware structure plus a software module .
  • FIG. 6 is a schematic block diagram of a communication device 600 provided by an embodiment of the present application.
  • the communication device 600 can correspondingly implement the functions or steps implemented by the terminal device or the source network device or the CHO target network device or the receiving network device in the above method embodiments shown in FIGS. 2-5 .
  • the communication device 600 may be a network device or a component (such as a chip or a circuit) that may be applicable to the network device, or the communication device 600 may be a chip system.
  • the system-on-a-chip may be composed of chips, or may include chips and other discrete devices.
  • the communication device 600 includes a transceiver module 601 and a processing module 602 .
  • the communication device may further include a storage module.
  • the storage module can be used to store one or more of data, information and instructions.
  • the communication device 600 when used to implement the above functions of the source network device:
  • the transceiver module 601 is configured to send the CHO configuration information of the terminal device to the second network device.
  • the processing module 602 may send the CHO configuration information of the terminal device to the second network device in the transceiver module 601 After that, the CHO configuration information is released. Further, after the communication device 600 obtains the mobility report, the transceiver module 601 sends a first message to the second network device, requests CHO configuration information of the terminal device, and receives the first message from the second network device response message.
  • the transceiver module 601 may also be configured to, before sending the CHO configuration information of the terminal device to the second network device, after the terminal device successfully completes conditional handover and access to the second network device, from the second network device to The second network device receives the handover success message.
  • the processing module 602 determines that the HANDOVER SUCCESS sent by the second network device has not been received, or the processing module 602 determines that the transceiver module 601 has received a message from the second network device indicating that the terminal device side stores a mobility report
  • the indication information of the terminal device is triggered by the processing module 602 to save the CHO configuration information of the terminal device.
  • the processing module 602 may save the CHO configuration information by itself, or the processing module 602 may notify or instruct the storage module to save the CHO configuration information.
  • the transceiver module 601 is configured to receive indication information from the second network device, the indication information indicating to save the CHO configuration information of the terminal device and the indication information is that the second network device runs on the first timer If it is detected that the connection with the CHO target cell fails within the specified time, the processing module 602 triggers to save the CHO configuration information of the terminal device.
  • the processing module 602 is configured to determine that the CHO of the terminal device fails, and trigger saving of the CHO configuration information of the terminal device. Wherein, the processing module 602 may determine that the CHO fails when it is determined that the transceiver module 601 has not received the HANDOVER SUCCESS message or the UE Context Release message.
  • the transceiver module 601 is configured to receive a handover success message from the second network device, and the processing module 602 starts the second timer after the transceiver module 601 receives the handover success message. If the second timer expires, the transceiver module 601 does not receive the UE Context Release message from the second network device, and the processing module 602 triggers to save the CHO configuration information of the terminal device.
  • the transceiver module 601 receives indication information from the second network device indicating that the terminal device side stores a mobility report, or the transceiver module 601 receives an indication from the second network device
  • the processing module 602 triggers saving of CHO configuration information of the terminal device.
  • the transceiver module 601 receives indication information from the second network device indicating that the terminal device side stores a mobility report, or the transceiver module 601 receives a message from the second network device
  • the processing module 602 may stop the second timer.
  • the transceiver module 601 is configured to receive the UE Context Release message sent by the second network device, and the processing module 602 starts the third timer after the transceiver module 601 receives the UE Context Release message. If within the running time of the third timer, the transceiving module 601 receives indication information from the second network device indicating that the terminal device side stores a mobility report, or the transceiving module 601 receives an indication information from the second network device indicating that the terminal device and the first For the indication information of connection failure between two network devices, the processing module 602 triggers to save the CHO configuration information of the terminal device.
  • the transceiving module 601 receives indication information from the second network device indicating that the terminal device side stores a mobility report, or the transceiving module 601 receives a message from the second network device
  • the processing module 602 may stop the third timer.
  • the transceiver module 601 is configured to receive conditional handover configuration information of the terminal device from the first network device, receive a first message from the first network device, and send the first message to the first network device. Respond to the message.
  • the processing module 602 may be configured to determine whether the communication apparatus 600 stores the CHO configuration information of the terminal device, or whether the CHO configuration information of the terminal device can be acquired in other ways. Therefore, the transceiver module 601 can send different response messages according to the determination result of the processing module 602 .
  • the processing module 602 starts the first timer after the terminal device successfully completes the CHO. If the processing module 602 determines that the connection failure between the terminal device and the serving cell is detected within the running time of the first timer, the transceiver module 601 is configured to send to the first network device information indicating that the first network device saves the CHO configuration information; or If the processing module 602 determines that the connection between the terminal device and the serving cell fails within the running time of the first timer, the transceiver module 601 does not send a HANDOVER SUCCESS message or a UE Context Release message to the first network device.
  • the transceiver module 601 may send a HANDOVER SUCCESS message or a UE Context Release message to the first network device.
  • the communication device 600 when used to implement the above functions of the receiving network device:
  • the transceiving module 601 is configured to receive a mobility report from a terminal device.
  • the processing module 602 may identify the CHO target network device on which the terminal device successfully completes the CHO according to the received mobility report, and force the transceiving module 601 to send the received mobility report to the CHO target network device.
  • the processing module 602 may be to trigger sending the mobility report to the CHO target network device where the connection failure occurs for the second time and the connection failure type is RLF.
  • the transceiver module 601 is configured to receive a mobility report from the terminal device and information indicating a cell to be forwarded, where the mobility report is in a coding format of the first system or standard, and when receiving the mobility report The cell where the terminal device is located belongs to the second system or standard.
  • the transceiving module 601 may also receive information indicating the priority order of forwarding cells from the terminal device.
  • the processing module 602 realizes the forwarding of the mobility report according to the information received by the transceiver module 601 .
  • the transceiver module 601 is configured to send a mobility report and information indicating forwarding cell information to the receiving network device, where the mobility report is in the encoding format of the first system or standard, and the mobility report is sent At this time, the cell where the terminal device is located belongs to the second system or standard.
  • the transceiving module 601 may also indicate to the receiving network device information about the priority order of forwarding cells.
  • the transceiving module 601 is configured to receive the CHO configuration information as described in S303 from the source network device.
  • the processing module 602 in this embodiment of the present application may be implemented by at least one processor or a processor-related circuit component
  • the transceiver module 601 may be implemented by a transceiver or a transceiver-related circuit component or a communication interface
  • the storage module can be realized by at least one memory.
  • the foregoing modules may be separated or integrated, which is not limited in this embodiment of the present application.
  • the embodiment of the present application also provides a communication device 700 that can be used to implement or support the communication device 700 to realize the functions of the network device or the terminal device in the methods provided by various embodiments of the present application.
  • the communication device 700 includes at least one processor 710 and at least one memory 720 for storing program instructions and/or data and/or information.
  • the memory 720 is coupled to the processor 710 .
  • the coupling in the embodiments of the present application is an indirect coupling or a communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • Processor 710 may cooperate with memory 720 .
  • the processor 710 may read program instructions and/or data and/or information stored in the memory 720, so that the communication device 700 implements a corresponding method.
  • at least one of the at least one memory may be included in the processor.
  • the communication device 700 may further include a communication interface 730 for communicating with other devices through a transmission medium, so that devices used in the communication device 700 can communicate with other devices.
  • a specific connection medium among the communication interface 730, the processor 710, and the memory 720 is not limited.
  • the memory 720 , the processor 710 and the communication interface 730 are connected through a bus in FIG. 7 , which is only for schematic illustration and not limited thereto.
  • the bus can be divided into address bus, data bus, control bus and so on.
  • the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may realize or execute Various methods, steps and logic block diagrams disclosed in the embodiments of the present application.
  • a general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the methods disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor.
  • the memory may be a non-volatile memory, such as a hard disk (hard disk drive, HDD) or a solid-state drive (solid-state drive, SSD), etc., or a volatile memory (volatile memory), such as random Access memory (random-access memory, RAM).
  • a memory is, but is not limited to, any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • the memory in the embodiment of the present application may also be a circuit or any other device capable of implementing a storage function, and is used for storing program instructions and/or data.
  • the embodiment of the present application also provides a communication system, which is used to implement all or part of the steps in the foregoing method embodiments.
  • the communication system may include one or more of the foregoing first network device, second network device, receiving network device, and terminal device.
  • An embodiment of the present application further provides a computer-readable storage medium, including instructions, which, when run on a computer, cause the method performed by the terminal device in the embodiments shown in FIGS. 2-5 to be executed.
  • An embodiment of the present application further provides a computer-readable storage medium, including instructions, which, when run on a computer, cause the method performed by the network device in the embodiments shown in FIGS. 2-5 to be executed.
  • the network device here may be one of the first network device, the second network device, and the receiving network device.
  • An embodiment of the present application further provides a computer program product, including instructions, which, when run on a computer, cause the method performed by the network device or the terminal device in the embodiments shown in FIGS. 2-5 to be executed.
  • each functional module in each embodiment of the present application can be integrated in In one processor, it may also exist separately physically, or two or more modules may be integrated into one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules.
  • the above-mentioned modules may also be referred to as units.
  • the methods provided in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present invention will be generated in whole or in part.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, network equipment, user equipment or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, a digital video disc (digital video disc, DVD for short)), or a semiconductor medium (for example, SSD).
  • a magnetic medium for example, a floppy disk, a hard disk, or a magnetic tape
  • an optical medium for example, a digital video disc (digital video disc, DVD for short)
  • a semiconductor medium for example, SSD

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供了移动性管理的方法和装置。该方法包括：第一网络设备向第二网络设备发送终端设备的条件切换配置信息；所述第一网络设备在获取到移动性报告后，向所述第二网络设备发送第一消息，请求所述终端设备的条件切换配置信息；所述第一网络设备从所述第二网络设备接收所述第一消息的响应消息。本实施例的方法和装置，可以使得网络设备能获取需要优化的移动性参数，进一步的，从而可以进行合理的移动性管理，提高移动性鲁棒性，提升用户体验。

Description

移动性管理的方法及通信装置 技术领域
本申请涉及通信技术领域，特别涉及一种移动性管理的方法及通信装置。
背景技术
无线通信***中的移动性场景包括切换场景。在切换过程中发生连接失败时，终端设备可以向网络侧发送无线链路失败报告用于网络侧获取连接失败的原因，进一步的可以用于移动性管理。一种切换场景是条件切换，该场景中，即便终端设备成功完成条件切换，仍然存在完成条件切换后很快发生无线链路失败，或者存在切换成功的潜在问题如何在这样的场景下使得网络设备能获取需要优化的移动性参数是亟需解决的问题。
发明内容
本申请实施例提供了一种移动性管理的方法和装置，使得网络设备能获取需要优化的移动性参数，进一步的，从而可以进行合理的移动性管理，提高移动性鲁棒性，提升用户体验。
本申请实施例具体可以通过如下技术方案实现：
第一方面，提供了一种移动性管理的方法，可以理解的是，该第一方面的方法可由第一装置执行，第一装置可以是第一网络设备或能够支持第一网络设备实现该方法所需的功能的通信装置，例如芯片或者电路或者芯片***。以第一网络设备实现该方法为例，该方法可以包括：
第一网络设备向第二网络设备发送终端设备的条件切换配置信息，该第一网络设备在获取到移动性报告后，通过第一消息向第二网络设备请求所述终端设备的条件切换配置信息，该第一网络设备从该第二网络设备接收相应的响应消息。
通过本申请实施例的方法，使得网络设备能获取需要优化的移动性参数，进一步的，从而可以进行合理的移动性管理，提高移动性鲁棒性，提升用户体验。
结合第一方面，一些可能的实现方式中，在该第一网络设备向该第二网络设备发送终端设备的条件切换配置信息之前，该第一网络设备从该第二网络设备接收切换成功消息，该切换成功消息指示终端设备成功完成条件切换，接入到第二网络设备。
结合第一方面，一些可能的实现方式中，如果第二网络设备上存储有该终端设备的条件切换配置信息，或者第二网络设备可以通过其他方式获取到该终端设备的条件切换配置信息，那么第一网络设备可以从第二网络设备接收到条件切换配置信息，进一步的，可以将接收到的条件切换配置信息用于移动性参数的优化。如果第二网络设备上没有存储或者不能获取到该终端设备的条件切换配置信息，那么第一网络设备会从第二网络设备接收到指示条件切换配置信息请求失败的信息，可选的，第一网络设备可以丢弃接收到的移动性报告，可以节约终端设备的存储空间。
第二方面，又提供了一种移动性管理的方法，该第二方面的方法可由第二装置执行，第二装置可以是第二网络设备或能够支持第二网络设备实现该方法所需的功能的通信装置，例如芯片或者电路或者芯片***。以第二网络设备实现该方法为例，该方法可以包括：
第二网络设备从第一网络设备接收终端设备的条件切换配置信息，该第二网络设备从该第一网络设备接收第一消息，该第一消息请求所述终端设备的条件切换配置信息，该第二网络设备向第一网络设备发送所述第一消息的响应消息。
通过本申请实施例的方法，使得网络设备能获取需要优化的移动性参数，进一步的，从而可以进行合理的移动性管理，提高移动性鲁棒性，提升用户体验。
结合第二方面，一些可能的实现方式中，在该第二网络设备接收该第一网络设备发送的终端设备的条件切换配置信息之前，该第二网络设备向该第一网络设备发送切换成功消息，该切换成功消息指示终端设备成功完成条件切换，接入到第二网络设备。
结合第二方面，一些可能的实现方式中，如果第二网络设备上存储有该终端设备的条件切换配置信息，或者第二网络设备可以通过其他方式获取到该终端设备的条件切换配置信息，那么第二网络设备可以向第一网络设备发送条件切换配置信息，进一步的，第一网络设备可以将接收到的条件切换配置信息用于移动性参数的优化。如果第二网络设备上没有存储或者不能获取到该终端设备的条件切换配置信息，那么第二网络设备会向第一网络设备发送指示条件切换配置信息请求失败的信息，可选的，第一网络设备可以丢弃接收到的移动性报告，可以节约终端设备的存储空间。
结合第一方面或者第二方面，一些可能的实现方式中，条件切换配置信息包括该第一网络设备为终端设备配置的一个或多个候选小区的条件切换信息；或者，该条件切换配置信息包括移动性信息，所述移动性信息用于指示为所述终端设备配置的小区的条件切换移动性参数对应的移动性标识或者索引，从而可以简化CHO配置信息的指示，提高效率。可以理解的是，该条件切换配置信息也可以不仅限用于第一或者第二方面的方法。
结合第一方面或者第二方面，一些可能的实现方式中，上述第一消息携带终端设备的标识信息，或者终端设备的标识信息和与条件切换相关的时间信息，从而可以用于目标网络设备根据上述信息确定正确的终端设备，进而确定对应的CHO配置信息。示例性的，上述条件切换相关的时间信息指示终端设备在完成所述条件切换的时间信息，和/或，该第一网络设备和该第二网络设备间与执行条件切换相关的至少一个消息的时间信息。
第三方面，还提供了一种移动性管理的方法，该第三方面的方法可由第三装置执行，第三装置可以是第三网络设备或能够支持第三网络设备实现该方法所需的功能的通信装置，例如芯片或者电路或者芯片***，其中，该第三网络设备可以是源网络设备或者其他网络设备。以第三网络设备实现该方法为例，该方法可以包括：从终端设备接收移动性报告，根据接收到的移动性报告识别出终端设备成功完成条件切换的目标网络设备，强制向该目标网络设备发送接收到的移动性报告。
第四方面，还提供了一种移动性管理的方法，该第四方面的方法可由第三装置执行，第三装置可以是第三网络设备或能够支持第三网络设备实现该方法所需的功能的通信装置，例如芯片或者电路或者芯片***，其中，该第三网络设备可以是源网络设备或者其他网络设备。以第三网络设备实现该方法为例，该方法可以包括从终端设备接收移动性报告，将该移动性报告发送给第二次发生连接失败且连接失败类型为无线链路失败的条件切换目标网络设备。
结合第三方面或者第四方面的方法，一些可能的实现方式中，还包括从终端设备接收移动性报告以及指示转发小区的信息，其中，该移动性报告为第一***或者制式的编码格式，接收该移动性报告时终端设备所在的小区属于第二***或者制式。可选的，还可以从终端设备接收指示转发小区的优先顺序的信息。可选的，上述移动性报告以容器的形式携带在消息中。转发小区的信息和转发小区优先顺序的指示信息可以在上述消息中的该容器之外。可以 理解的是，上述指示转发小区的信息和/或指示转发小区的优先顺序的信息的方案不仅限于适用于第三方面或者第四方面的方法。
上述第三方面或者第四方面的方法，定义了接收网络设备和目标网络设备间的的移动性报告的转发机制，使得移动性报告必须由接收网络设备转发给条件切换目标网络设备，从而使得条件切换目标网络设备可以有机会向源网络设备发送条件切换配置信息，使得源网络设备可以获取对应的条件切换配置信息，从而进行合理的移动性管理，提高移动性鲁棒性，提升用户体验。
第五方面，还提供了一种移动性管理的方法，该方法提供了条件切换配置信息的保存机制。该第五方面的方法可由第一装置执行，第一装置可以是第一网络设备或能够支持第一网络设备实现该方法所需的功能的通信装置，例如芯片或者电路或者芯片***。以第一网络设备实现该方法为例，该方法可以包括：第一确定没有收到来自第二网络设备的切换成功消息，或者确定收到来自第二网络设备的指示终端设备侧存储有移动性报告的指示信息，保存该终端设备的条件配置信息。
第六方面，还提供了一种移动性管理的方法，该方法提供了条件切换配置信息的保存机制。该第六方面的方法可由第一装置执行，第一装置可以是第一网络设备或能够支持第一网络设备实现该方法所需的功能的通信装置，例如芯片或者电路或者芯片***。以第一网络设备实现该方法为例，该方法可以包括：从第二网络设备接收指示信息，该指示信息指示保存终端设备的条件切换配置信息且是该指示信息该第二网络设备在第一定时器运行时间内检测到和条件切换目标小区间的连接失败的情况下发送的，那么保存该终端设备的条件切换配置信息。
第七方面，还提供了一种移动性管理的方法，该方法提供了条件切换配置信息的保存机制。该第七方面的方法可由第一装置执行，第一装置可以是第一网络设备或能够支持第一网络设备实现该方法所需的功能的通信装置，例如芯片或者电路或者芯片***。以第一网络设备实现该方法为例，该方法可以包括：确定终端设备的条件切换失败，保存该终端设备的条件切换配置信息。可选的，可以是在没有接收到切换成功消息或者终端设备上下文释放消息的情况下，确定条件切换失败。
第八方面，还提供了一种移动性管理的方法，该方法提供了条件切换配置信息的保存机制。该第八方面的方法可由第一装置执行，第一装置可以是第一网络设备或能够支持第一网络设备实现该方法所需的功能的通信装置，例如芯片或者电路或者芯片***。以第一网络设备实现该方法为例，该方法可以包括：用于从第二网络设备接收切换成功消息后，启动第二定时器，若第二定时器超期，没有收到来自第二网络设备的终端设备上下文释放消息，保存终端设备的条件切换配置信息。或者可以是，若第二定时器运行时间内，接收到来自第二网络设备的指示终端设备侧存储有移动性报告的指示信息，或者接收到来自第二网络设备的指示终端设备和第二网络设备间连接失败的指示信息保存终端设备的条件切换配置信息。可选的，如果在第二定时器运行时间内，接收到来自第二网络设备的指示终端设备侧存储有移动性报告的指示信息，或者接收到来自第二网络设备的指示终端设备和第二网络设备间连接失败的指示信息，可以停止第二定时器。
第九方面，还提供了一种移动性管理的方法，该方法提供了条件切换配置信息的保存机制。该第九方面的方法可由第一装置执行，第一装置可以是第一网络设备或能够支持第一网络设备实现该方法所需的功能的通信装置，例如芯片或者电路或者芯片***。以第一网络设备实现该方法为例，该方法可以包括：接收来自第二网络设备的终端设备上下文释放消息后， 启动第三定时器，若第三定时器运行时间内，接收到来自第二网络设备的指示终端设备侧存储有移动性报告的指示信息，或者接收到来自第二网络设备的指示终端设备和第二网络设备间连接失败的指示信息，保存终端设备的条件切换配置信息。可选的，如果在第三定时器运行时间内，接收到来自第二网络设备的指示终端设备侧存储有移动性报告的指示信息，或者接收到来自第二网络设备的指示终端设备和第二网络设备间连接失败的指示信息，可以停止第三定时器。
第十方面，还提供了一种移动性管理的方法，该第十方面的方法可由第二装置执行，第二装置可以是第二网络设备或能够支持第二网络设备实现该方法所需的功能的通信装置，例如芯片或者电路或者芯片***。以第二网络设备实现该方法为例，该方法可以包括：在终端设备成功完成条件切换后，启动第一定时器。若确定在第一定时器运行时间内，检测到终端设备和服务小区(条件切换目标小区)的连接失败，向第一网络设备发送指示第一网络设备保存条件切换配置信息的信息；或者是，若确定在第一定时器运行时间内，检测到终端设备和服务小区(条件切换目标小区)的连接失败，不向第一网络设备发送切换成功消息或者终端设备上下文释放消息。可选的，若第一定时器超期，还没有检测到终端设备和服务小区(条件切换目标小区)的连接失败，可以向第一网络设备发送切换成功消息或者终端设备上下文释放消息。可选的，在第一定时器运行时间内，检测到终端设备和服务小区的失败，第二网络设备停止第一定时器。
第十一方面，还提供了一种移动性管理的方法，该第十一方面的方法可由通信装置执行，该通信装置可以是终端设备或能够支持终端设备实现该方法所需的功能的装置，例如芯片或者电路或者芯片***。以终端设备实现该方法为例，该方法可以包括：终端设备向接收网络设备发送移动性报告以及指示转发小区信息的信息，其中，该移动性报告为第一***或者制式的编码格式，发送该移动性报告时该终端设备所在的小区属于第二***或者制式。通过该方法，可以辅助该接收网络设备更好的进行该移动性报告的转发。可选的，终端设备还可以向接收网络设备指示转发小区的优先顺序的信息。可选的，该移动性报告可以以容器的形式携带在消息中发送给接收网络设备。转发小区的信息和转发小区优先顺序的指示信息可以在上述消息中的该容器之外。
第十二方面，提供了一种通信装置，该通信装置具有实现上述第一方面至第十方面任一的方法中的行为或者步骤的功能。该通信装置可以为网络设备或者可用于网络设备的部件(例如芯片或者电路)。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块。
第十三方面，提供了一种通信装置，该通信装置具有实现上述第十一方面的方法中的行为或者步骤的功能。该通信装置可以为终端设备或者可用于终端设备的部件(例如芯片或者电路)。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块。
第十四方面，提供了一种通信装置，该通信装置可以为实现上述第一方面至第十一方面中任何一个方法的通信装置。该通信装置包括处理器和存储器。其中，该存储器用于存储计算机程序或指令或者数据，处理器与存储器耦合，当处理器读取计算机程序或指令或数据时，使通信装置执行任一方面的方法。可选的，该通信装置还可以包括通信接口。
示例性的，该通信接口可以是通信装置中的收发器。该收发器可以用于该通信装置与其它设备进行通信。
第十五方面，本申请实施例提供了一种芯片***，该芯片***包括处理器，用于实现第 一方面至第十一方面中的任一方法。在一种可能的设计中，该芯片***还包括存储器，用于保存程序指令和/或数据。该芯片***可以由芯片构成，也可以包含芯片和其他分立器件。
第十六方面，本申请实施例提供了一种通信***，该***包括第一网络设备、第二网络设备、第三网络设备和终端设备中的至少一个。
第十七方面，提供了一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码并运行时，使得上述各方面中任一方法被执行。
第十八方面，本申请提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，当该计算机程序被运行时，使得上述各方面任一方法被实现。
附图说明
图1为本申请实施例的一种应用场景；
图2为本申请实施例的一种源网络设备获取条件切换配置信息的流程示意图；
图3为本申请实施例的移动性管理的方法的一种示例的流程示意图；
图4为本申请实施例的移动性管理的方法的又一种示例的流程图；
图5为本申请实施例的移动性管理的方法的又一种示例的流程图；
图6为本申请实施例的一种通信装置示意图；
图7为本申请实施例的另一种通信装置示意图。
具体实施方式
本申请实施例中“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A、B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一(项)个”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a、b或c中的至少一项(个)，可以表示：a，b，c，a和b，a和c，b和c，或a、b和c，其中a、b、c中的每一个本身可以是元素，也可以是包含一个或多个元素的集合。
在本申请实施例中，“示例的”“在一些实施例中”“在另一实施例中”“作为一种实现方式”等用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
本申请实施例中通信、传输有时可以混用，应当指出的是，在不强调区别时，其所表达的含义是一致的。例如传输可以包括发送和/或接收，可以为名词，也可以是动词。
需要指出的是，本申请实施例中涉及的“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。本申请实施例中涉及的等于可以与大于连用，适用于大于时所采用的技术方案，也可以与小于连用，适用于与小于时所采用的技术方案，需要说明的是，当等于与大于连用时，不与小于连用；当等于与小于连用时，不与大于连用。
以下对本申请实施例中的部分用语进行说明。
1、终端设备。本申请实施例中终端设备是一种具有无线收发功能的设备，可以称为终端(terminal)、用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile  terminal，MT)、接入终端设备、车载终端设备、工业控制终端设备、UE单元、UE站、移动站、远方站、远程终端设备、移动设备、UE终端设备、无线通信设备、UE代理或UE装置等。终端设备可以是固定的或者移动的。需要说明的是，终端设备可以支持至少一种无线通信技术，例如LTE、NR、宽带码分多址(wideband code division multiple access，WCDMA)等。例如，终端设备可以是手机(mobile phone)、平板电脑(pad)、台式机、笔记本电脑、一体机、车载终端、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、可穿戴设备、未来移动通信网络中的终端设备或者未来演进的公共移动陆地网络(public land mobile network，PLMN)中的终端设备等。在本申请的一些实施例中，终端还可以是具有收发功能的装置，例如芯片***。其中，芯片***可以包括芯片，还可以包括其它分立器件。
2、网络设备。本申请实施例中网络设备是一种为终端设备提供无线通信功能的设备，也可称之为接入网设备、无线接入网(radio access network，RAN)设备等。示例的，网络设备包括但不限于：第五代移动通信***(5th-generation，5G)中的下一代基站(generation nodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved node B、或home node B，HNB)、基带单元(baseband unit，BBU)、收发点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等。网络设备还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器、集中单元(centralized unit，CU)和/或分布单元(distributed unit，DU)，或者网络设备可以为中继站、接入点、车载设备、终端设备、可穿戴设备以及未来移动通信中的网络设备或者未来演进的PLMN中的网络设备等。在一些实施例中，网络设备还可以为具有为终端设备提供无线通信功能的装置，例如芯片***。示例的，芯片***可以包括芯片，还可以包括其它分立器件。
CU和DU在物理上可以是分离的也可以部署在一起。多个DU可以共用一个CU。一个DU也可以连接多个CU。CU和DU之间可以通过接口相连，例如可以是F1接口。CU和DU可以根据无线网络的协议层划分。例如其中一种可能的划分方式是：CU用于执行无线资源控制(Radio Resouce Control,RRC)层、业务数据适配协议(service data adaptation protocol，SDAP)层以及分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能，而DU用于执行无线链路控制(radio link control，RLC)层，媒体接入控制(media access control，MAC)层，物理(physical)层等的功能。可以理解对CU和DU处理功能按照这种协议层的划分仅仅是一种举例，也可以按照其他的方式进行划分。例如可以将CU或者DU划分为具有更多协议层的功能。例如，CU或DU还可以划分为具有协议层的部分处理功能。在一设计中，将RLC层的部分功能和RLC层以上的协议层的功能设置在CU，将RLC层的剩余功能和RLC层以下的协议层的功能设置在DU。在另一种设计中，还可以按照业务类型或者其他***需求对CU或者DU的功能进行划分。例如按时延划分，将处理时间需要满足时延要求的功能 设置在DU，不需要满足该时延要求的功能设置在CU。上图所示的网络架构可以应用于5G通信***，其也可以与LTE***共享一个或多个部件或资源。在另一种设计中，CU也可以具有核心网的一个或多个功能。一个或者多个CU可以集中设置，也分离设置。例如CU可以设置在网络侧方便集中管理。DU可以具有多个射频功能，也可以将射频功能拉远设置。
CU的功能可以由一个实体来实现也可以由不同的实体实现。例如，可以对CU的功能进行进一步切分，例如，将控制面(control panel，CP)和用户面(user panel，UP)分离，即CU的控制面(CU-CP)和CU用户面(CU-UP)。例如，CU-CP和CU-UP可以由不同的功能实体来实现，所述CU-CP和CU-UP可以与DU相耦合，共同完成接入网设备的功能。
终端设备可以与不同技术的接入网设备进行通信，例如，终端设备可以与支持长期演进(long term evolution，LTE)的接入网设备通信，也可以与支持5G的接入网设备通信，还可以同时与支持LTE的接入网设备以及支持5G的接入网设备进行通信。本申请实施例并不限定。
3.核心网设备
核心网设备可以是指为终端提供业务支持的核心网(core network，CN)中的设备。目前，一些核心网设备的举例为：接入和移动性管理功能(access and mobility management function，AMF)实体、会话管理功能(session management function，SMF)实体、用户面功能(user plane function，UPF)实体等等，此处不一一列举。其中，所述AMF实体可以负责终端的接入管理和移动性管理；所述SMF实体可以负责会话管理，如用户的会话建立等；所述UPF实体可以是用户面的功能实体，主要负责连接外部网络。需要说明的是，本申请中实体也可以称为网元或功能实体，例如，AMF实体也可以称为AMF网元或AMF功能实体，又例如，SMF实体也可以称为SMF网元或SMF功能实体等。
4.切换
本申请实施例所涉及的切换场景，可以分为普通切换(也可以称为传统切换)、条件切换(conditional handover，CHO)和双激活协议栈(dual active protocol stack，DAPS)切换。
其中，普通切换是指终端设备接收到源网络设备下发的配置，在目标网络设备完成重配，并接入目标基站，断开与源网络设备链接的过程。
DAPS切换是指终端设备在接收到切换命令之后依然保持和源网络设备的连接，同时尝试与目标网络设备建立连接。因此可以认为，在DAPS切换场景下，终端设备和源网络设备和目标网络设备分别建立连接直至目标网络设备指示终端设备断开和源网络设备的链接。从流程的角度，可以分为基于Xn的切换(Xn based handover)和基于NG的切换(NG based handover)。其中，基于Xn的切换是由源网络设备和目标网络设备交互切换请求，而基于NG的切换是由源网络设备向授权管理区域(authentication management field，AMF)发送切换请求、AMF再向目标网络设备发送切换命令。
CHO中，源网络设备向终端设备发送CHO配置信息，终端设备在接收到该CHO配置信息后，根据该CHO配置信息判断各CHO候选小区是否满足切换触发条件，将满足切换触发条件的CHO候选小区作为目标小区，然后与确定出的目标小区进行随机接入过程，当随机接入成功完成，终端设备给目标小区所属的网络设备(即目标网络设备)发送RRC消息(如RRC重配置完成消息)，通知目标网络设备条件切换完成。
5.无线链路失败(radio link failure，RLF)报告(report)
通信网络中，引入了MRO(Mobility Robustness Optimisation，移动鲁棒性优化)机制，现有的MRO机制通过引入终端记录移动性过程中的参数，记录对应的移动性报告，并发送 上述报告给网络设备，使得网络设备可以更好的调整移动性的相关参数。移动性报告包括成功移动性报告successful mobility report(包括各种成功的移动性报告，比如成功的普通切换报告、成功的CHO报告或者其他成功报告的任意一种或多种)、失败报告failure report(包括RLF report或者其他失败报告的任意一种或多种)、随机接入报告、连接失败报告等的至少一种报告。
以终端设备完成切换后在目标小区发生RLF为例，终端设备记录RLF report和发送RLF report，以及RLF report在网络设备间的转发的流程例如可以为：
终端设备检测到RLF，记录RLF report，并向接入的网络设备(例如第三gNB)发送RLF report；该第三gNB把RLF report发送给发生无线链路失败的小区对应的网络设备(比如目标gNB)，目标gNB确定是否需要转发RLF report给源小区对应的网络设备(比如源gNB)，若需要转发RLF report给源gNB，则目标gNB发送切换报告(HO Report)消息给source gNB，HO Report消息可以携带RLF report，以及源gNB的移动性信息的至少一种。可选的，该移动性信息可以由源gNB在切换请求消息中发送给目标gNB。
示例性的，RLF report可以包括至少一种信息：
1)失败主小区标识(failedPCellId)：终端设备检测到RLF或者定时器超期(到期)的主小区信息，或者HOF的目标主小区信息。该定时器例如可以是终端设备发送测量报告后启动的定时器，如果该定时器超时后终端设备还没有收到切换命令，可以认为发生连接失败，该定时器例如可以是T312。
可选的，连接失败信息中也可以不包括失败主小区标识(failedPCellId)，而是包括失败小区标识(failedCellId)。其中，失败小区标识即终端设备检测到链路失败或者定时器超期的小区信息，或者切换失败的目标小区信息，本申请实施例对此不作限定。
2)连接失败类型(connectionFailureType)。
作为示例，连接失败类型可以为RLF或者HOF或者定时器(例如T312)到期或者竞争失败(比如先听后说(listen before talk，LBT)失败)。连接失败类型也可以简称为失败类型。
3)之前的主小区标识(previousPCellId)：终端设备上一次收到切换命令的前主小区信息。
可选的，连接失败信息中也可以不包括之前的主小区标识(previousPcellId)，而是包括之前的小区标识(previousCellId)。其中，之前的小区标识即终端设备上一次收到切换命令的前小区信息，本申请实施例对此不作限定。
4)重建立小区标识(reestablishmentCellId)：连接失败后尝试重建立的小区信息。
5)连接失败时间(timeConnFailure)：最后(或者说最近)一次收到切换命令(或者重配置消息)到连接失败的时间长度。
6)失败后的时间(timeSinceFailure)：连接失败时开始记录的时间长度。一般指连接失败到上报失败报告的时间长度。
7)连接失败的原因(rlf-Cause)：其中，连接失败的原因可以包括HOF、RLF、重配同步失败、NR向其他***切换失败、完整性校验失败(integrity check failure)或者RRC连接重配置失败。
8)位置信息(locationInfo)：终端设备发生连接失败的位置的信息。
9)随机接入信息(ra-InformationCommon)：终端设备在目标主小区进行随机接入的信息。
9)测量结果：可以为小区和/或波束的测量结果，该测量结果可以包括服务小区和/或邻区的测量结果。
10)收到CHO配置到触发CHO执行的时间信息(timeCHOcfgExe)。
11)CHO小区信息：用于指示UE成功完成CHO的小区信息。12)切换类型：CHO。
13)重连接小区信息(reconnectCellId)：用于指示终端设备在连接失败或者重建失败后回到连接态的小区信息。可以理解的，若重建成功，终端设备可以不记录该信息。
在CHO切换流程中，可能会发生至少一次连接失败或者说差点发生连接失败，该情况下，终端设备可以记录移动性报告。此外，在完成CHO的不久的时间内，可能会很快发生至少一次连接失败或者差点发生连接失败，在该情况下，终端设备也可以记录移动性报告。上述各种情况下记录的移动性报告，都可以被称为与CHO相关的移动性报告。源网络设备在收到与CHO相关的移动性报告后，可以基于对应的CHO配置信息(即源网络设备配置终端设备执行此次CHO的配置信息)，确定是否优化对应的移动性参数。
如图1是本申请实施例的一种应用场景。终端设备从网络设备1的覆盖范围移动至网络设备2的覆盖范围。为了保持通信的连续性，终端设备从网络设备1的小区1切换至网络设备2的小区2。其中，网络设备1可以称为源网络设备、小区1可以称为源小区。对应的，网络设备2可以称为目标网络设备、小区2可以称为目标小区。该应用场景适用于各种无线通信***，例如：长期演进(long term evolution，LTE)***、LTE频分双工(frequency division duplex，FDD)***、LTE时分双工(time division duplex，TDD)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信***、5G***或新无线(new radio，NR)、或者未来的演进***等。
可以理解的，本申请实施例中，终端设备和/或网络设备可以执行本申请实施例中的部分或全部步骤，这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者各种操作的变形。此外，各个步骤可以按照本申请实施例呈现的不同的顺序来执行，并且有可能并非要执行本申请实施例中的全部操作。
对于CHO场景下，对于源网络设备如何获取与CHO相关的移动性报告所对应的CHO配置信息，一种可能的方案如下：以图2为例，源网络设备在收到终端设备通过CHO成功接入的目标网络设备(称为CHO网络设备)的切换成功(HO SUCCESS)消息后，向该CHO目标网络设备发送所存储的CHO配置信息，该CHO目标网络设备保存收到的CHO配置信息。当该CHO目标网络设备从终端设备或者其他网络设备(例如第三网络设备)收到移动性报告(例如RLF report)时，该CHO目标网络设备向源网络设备发送所保存的CHO配置信息，例如可以在CHO目标网络设备向源网络设备发送的HO report中携带上述CHO配置信息，本申请实施例对于CHO目标网络设备向源网络设备发送CHO配置信息的方式不做限制。
可以理解的是，一些情况下，CHO目标网络设备可能并没有收到终端设备的与CHO相关的移动性报告。由于终端检测到连接失败后，可以执行一次CHO重建，那么可能存在终端设备在源小区检测到第一次连接失败(失败类型是RLF)或者终端设备和第一次CHO目标小区间发生第一连接失败(失败类型是HOF)后，终端设备成功执行CHO重建或者终端设备成功执行CHO重建后很快发生第二次连接失败(失败类型为RLF)的场景。上述各个场景下，接收到RLF report的网络设备可能会向源网络设备发送移动性报告(例如RLF report)，而不是给CHO目标网络设备发送移动性报告。如图3所示，提供了一种移动性管理的方法，该方法可以包括：
S301，终端设备成功完成CHO，接入到CHO目标小区。
“终端设备成功完成CHO，接入到CHO目标小区”的方式可以是：终端设备成功完成CHO，以条件切换的方式接入到CHO目标小区，比如终端设备确定CHO候选小区对应的触 发条件满足并成功执行CHO，以条件切换的方式接入该CHO目标小区；或者，也可以终端设备成功完成CHO，以重建的方式接入到CHO目标小区，比如终端设备检测到连接失败，执行小区选择，确定该CHO候选小区为目标小区后，成功执行CHO，以重建的方式接入该CHO目标小区。“终端设备成功完成CHO，接入到CHO目标小区”也可以说“终端设备成功完成CHO，接入到CHO目标网络设备”。CHO目标网络设备是指终端设备成功完成CHO接入的网络设备。
在接收到源网络设备发送的CHO配置信息后，根据该CHO配置信息判断各CHO候选小区是否满足切换触发条件，将满足切换触发条件的CHO候选小区作为目标小区，或者终端设备检测到连接失败后执行小区选择，确定该CHO候选小区为目标小区，然后与确定出的目标小区进行随机接入过程。当随机接入成功完成，终端设备给目标小区所属的网络设备(即CHO目标网络设备)发送RRC消息(如RRC重配置完成消息)，通知CHO目标网络设备条件切换完成。
可以理解的是，在源网络设备向终端设备发送CHO配置信息之前，还可以包括：源网络设备和至少一个候选目标网络设备之间进行条件切换的准备流程。该准备流程例如可以包括：源网络设备(比如根据测量报告)确定至少一个候选目标小区，源网络设备向该至少一个候选目标小区对应的至少一个候选目标网络设备发送切换请求，该至少一个候选目标网络设备执行接纳控制流程，允许终端设备接入的候选目标网络设备向源网络设备发送切换请求响应消息，源网络设备根据切换请求响应消息确定CHO配置信息。
S302，源网络设备接收CHO目标网络设备发送的切换成功消息。
在终端设备成功完成CHO，接入到CHO目标网络设备后，CHO目标网络设备可以向源网络设备发送切换成功(HO SUCCESS)消息。该切换成功消息用于向源网络设备指示终端设备成功完成CHO，接入到CHO目标网络设备。
可以理解的是，此处以切换成功消息为消息名称进行举例，本申请实施例对该指示切换成功的消息名称不做限定，
S303，源网络设备向CHO目标网络设备发送条件切换(CHO)配置信息。
该CHO配置信息是该终端设备相关的CHO配置信息。
作为一种可能的实现方式，在源网络设备向CHO目标网络设备发送该CHO配置信息后，源网络设备释放(也可以是清除或者丢弃)该CHO配置信息，比如在源网络设备源网络设备向CHO目标网络设备发送该CHO配置信息后，源网络设备收到CHO目标网络设备发送的终端设备上下文释放消息，源网络设备释放(也可以是清除或者丢弃)该CHO配置信息。可以理解的是，源网络设备也可以是释放部分CHO配置信息或者说是在其他的时机释放CHO配置信息，本申请实施例对源网络设备在向CHO目标网络设备发送CHO配置信息后对CHO配置信息的处理方式不做限定。
CHO目标网络设备在接收到CHO配置信息后，可以保存该CHO配置信息。
示例性的，该CHO配置信息可以包括源网络设备为该终端设备配置的一个或多个候选小区的CHO信息。候选小区的CHO信息可以包括用于指示候选小区的标识信息的信息以及对应的一个或多个切换触发条件(或者也可以叫执行条件)。用于指示候选小区的标识信息的信息可以为CHO配置标识或者CHO候选小区信息。小区信息可以为小区的小区全局标识(cell global identifier，CGI)、物理小区标识(physical cell identifier，PCI)和频点、小区标识(cell identifier，cell ID)、非公网标识(non-public network identifier,NPN ID)、非陆地网络标识(non-terrestrial network identifier,NTN ID)或者其它小区标识中的至少一种。CGI可以包括 公共陆地移动网络(public land mobile network，PLMN ID)和cell ID。可选的，小区的信息还可以包括跟踪区码(tracking area code，TAC)和/或小区所属的网络设备的标识信息，比如全局网络设备标识。
可以理解的是，也可以将上述候选小区的CHO信息称为CHO移动性参数。
可选的，该CHO配置信息或者可以是源网络设备为该终端设备配置的至少一个移动性信息。移动性信息可以是和小区的CHO移动性参数对应的移动性标识或者索引。该移动性信息可以是列表(list)的形式，也可以是其他形式，本申请实施例对此不做限定。例如，源网络设备可以保存至少一个小区的各个小区对应的CHO移动性参数，每个小区的CHO移动性参数和移动性信息对应，也就是说通过移动性信息可以确定到或者索引到对应的小区的CHO移动性参数。一些可能的实现方式中，该移动性信息可以是小区标识,或者，该移动性信息也可以是CHO移动性参数的索引。一些可能的方式中，源网络设备可以一直保存或者在一段时间内保存各个小区的CHO移动性参数以及对应的移动性信息，从而后续可以通过移动性信息确定对应的CHO移动性参数。通过该方式，可以简化CHO配置信息的指示，减少CHO配置信息在网络设备上的存储开销，提高效率。
又一种可能的实现方式中，条件切换配置信息可以包括所述第一网络设备为所述终端设备配置的一个或多个候选小区的条件切换信息和源网络设备为该终端设备配置的至少一个移动性信息。可选的，本申请实施例中，也可以将CHO配置信息称为CHO上下文信息。
可以理解的是，此处所描述的CHO配置信息也可以适用于图2所示实施例的流程，也就是说，源网络设备向该CHO目标网络设备发送所存储的CHO配置信息可以是源网络设备为该终端设备配置的一个或多个候选小区的CHO信息，和/或至少一个移动性信息。此外，源网络设备给终端设备发送的CHO配置信息也可以是上述所描述的CHO配置信息。S304，源网络设备获取移动性报告。
一种可能的实现方式中，可以是源网络设备从不同于CHO目标网络设备的网络设备处获取移动性报告，该不同于CHO目标网络设备的网络设备可以是不同于源网络设备的第三网络设备，也可以是源网络设备。在源网络设备确定该移动性报告是与CHO相关的移动性报告后，可以执行S305以及后续步骤。
S305,源网络设备向CHO目标网络设备发送第一消息，请求与该终端设备对应的CHO配置信息。
示例性的，第一消息为可以为CHO配置信息请求消息，可以通过第一消息向CHO目标网络设备请求该终端设备的CHO配置信息。本申请实施例对于第一消息的消息名称和/或信元结构不做限定。
一些可能的实现方式中，第一消息携带用于CHO目标网络设备确定终端设备的信息。比如，第一消息可以包括终端设备的标识信息，或者终端设备的标识信息和与CHO相关的时间信息。
终端设备的的标识信息包括如下至少一种：终端设备在源小区的小区无线网络临时标识(cell radio network temporary identifier,C-RNTI)，终端设备在成功完成CHO接入的CHO目标小区的C-RNT(target C-RNTI)，源网络设备为该终端设备分配的用于在网络设备间的接口上识别所述终端设备的标识(Source NG-RAN node UE XnAP ID)，CHO目标网络设备为所述终端设备分配的用于在网络设备间的接口上识别所述终端设备的标识(target NG-RAN node UE XnAP ID)，源小区信息，目标小区信息。
上述与CHO相关的时间信息可以指示上述终端设备在目标小区完成CHO的时间信息， 和/或，源网络设备和CHO目标网络设备间与执行CHO相关的至少一个消息的时间信息，比如源网络设备向CHO目标网络设备发送CHO请求(handover request)的时间信息，源网络设备接收来自CHO目标网络设备的CHO请求确认(handover request acknowledge)消息的时间信息，源网络设备接收来自CHO目标网络设备的切换成功(handover success)消息的时间信息，源网络设备向CHO目标网络设备发送序列号状态转发(sn status transfer)消息的时间信息，或者源网络设备接收来自CHO目标网络设备的终端设备的上下文释放(UE context release)消息的时间信息的至少一种。可选的，第一消息还可以指示上述指示一个时间信息的类型，用于CHO目标网络设备确定与时间信息对应的消息。
CHO目标网络设备在接收到终端设备的标识信息，或者终端设备的标识信息和与CHO相关的时间信息后，可以根据终端设备的标识信息，或者终端设备的标识信息和与CHO相关的时间信息确定是否存储有或者是否能获取到对应终端设备的CHO配置信息，也就是说，上述信息可以用于目标网络设备确定正确的终端设备，进而确定对应的CHO配置信息。例如，CHO目标网络设备对比来自源网络设备的终端设备的标识信息和其存储的CHO配置信息对应的终端设备的标识信息，若一致，CHO目标网络设备确定存储有或者能获取到对应终端设备的CHO配置信息。又例如，CHO目标网络设备接收来自源网络设备的终端设备的标识信息和与CHO相关的时间信息后，CHO目标网络设备对比上述信息和和其存储的CHO配置信息对应的终端设备的标识信息和与CHO相关的时间信息是否一致或者存在关联，若一致或者存在关联，CHO目标网络设备确定存储有或者能获取到对应终端设备的CHO配置信息。存在关联的一种可能情况例如可以是CHO目标网络设备确定接收到的与CHO相关的时间信息和其存储的与CHO相关的时间信息属于相同的范围或者范围上有重合。
若确定CHO目标网络设备上存储有该终端设备的CHO配置信息，或者可以通过其他方式获取到该终端设备的CHO配置信息，可以执行S306a，如果CHO目标网络设备上没有存储或者不能获取到该终端设备的CHO配置信息，可以执行步骤S306b。可以理解的是，S306a和S306b均可以理解为是CHO目标网络设备发送对第一消息的响应消息的步骤。
S306a，CHO目标网络设备向源网络设备发送该终端设备的CHO配置信息。
相应的，源网络设备接收来自CHO目标网络设备的CHO配置信息，从而可以用于移动性参数的优化。例如，源网络设备可以结合S304中所获取的移动性报告确定某个或者某些小区的CHO切换触发条件需要进行调整。可见，本申请实施例中，可以使得源网络设备能够获取到对应的CHO配置信息，从而进行合理的移动性管理，提高移动性鲁棒性，提升用户体验。
一种可能的实现方式中，CHO目标网络设备可以通过CHO配置请求确认消息将该终端设备的CHO配置信息发送给终端设备。
S306b,CHO目标网络设备向源网络设备指示CHO配置信息请求失败。
一些可能的实现方式中，可以通过第二消息向源网络设备指示CHO配置信息请求失败。该第二消息可以是CHO配置请求失败消息，或者也可以是其他消息，本申请实施例对第二消息的名称和信元结构不做限定。
可选的，该第二消息可以携带失败原因(failure cause)。作为一种示例，失败原因可以为“无上下文(no UE context)”，“无CHO配置(no CHO configuration)”,“无效UE标识(invalid UE ID)”或者其他信息。
源网络设备在接收到第二消息后，获知CHO配置信息请求失败，也就是说无法从CHO目标网络设备获取到该终端设备的CHO配置信息，那么由于无法确定需要优化的CHO配置信息，源网络设备可以丢弃接收到的移动性报告，可以节约终端设备的存储空间。
此外，本申请实施例还提供了一种移动性管理的方法，在该方法中，考虑到按照传统的流程，CHO目标网络设备可能并没有收到终端设备的与CHO相关的移动性报告的情况，对移动性报告的传输路径进行了进一步的优化，即只要终端设备和CHO目标网络设备成功完成CHO，无论终端设备是否检测到连接失败，接收到移动性报告的网络设备(简称为接收网络设备)都把移动性报告发送给该成功完成CHO的目标网络设备。。例如，该接收网络设备可以是第三网络设备，也可以是源网络设备。
那么如图4所示，本申请又一实施例提供了一种移动性的管理方法，可以包括：
S401，终端设备成功完成CHO，接入到CHO目标小区。
S402，源网络设备接收CHO目标网络设备发送的切换成功消息。
S403，源网络设备向CHO目标网络设备发送CHO配置信息。
其中，关于S401-S403可以进一步参考图3所示实施例中S301-S303的相应描述，此处不再赘述。
S404，接收网络设备从终端设备接收到移动性报告。
接收网络设备在接收到终端设备发送的移动性报告后，可以识别出终端设备成功完成CHO的CHO目标网络设备，执行S405。
可能的场景为终端设备检测到第一次连接失败(第一连接失败可以为终端设备和源小区之间的RLF，或者终端设备和满足CHO触发条件的第一个CHO目标小区之间的HOF)，选择CHO目标小区为目标小区，终端设备成功执行CHO重建，接入该CHO目标小区；或者，又一种可能的场景为终端设备未检测到任何的连接失败，终端设备执行CHO切换，接入满足CHO触发条件的CHO目标小区。可选的，终端设备可以未检测到和该CHO目标小区之间的RLF，也可以检测到和该CHO目标小区之间的RLF。作为一种实现方式，接收网络设备可以根据移动性报告中的CHO目标小区信息(比如失败主小区标识)，失败类型(RLF，该失败类型用于指示UE成功完成CHO到该主小区后发生了RLF)，收到CHO配置到触发CHO执行的时间信息(用于确定UE接入CHO目标小区的方式为CHO切换)的至少一种，确定CHO目标小区对应的CHO目标网络设备；又比如，接收网络设备根据CHO小区信息，确定终端设备成功完成CHO的小区信息，从而确定该CHO目标小区对应的CHO目标网络设备；又比如，接收网络设备根据移动性报告中的重建立小区标识和切换类型(CHO)以及移动性报告中“重连接小区信息”确定该重建立小区为终端设备成功执行CHO重建的CHO目标小区，从而确定该CHO目标小区对应的CHO目标网络设备。在确定出移动性报告对应的CHO目标网络设备后，可以执行S405。
S405，强制接收网络设备向CHO目标网络设备发送接收到的移动性报告。
此处，“强制”是指接收网络设备根据移动性报告确定存在成功完成CHO的CHO目标小区，无论终端设备是否检测到和该CHO目标小区之间的无线链路失败，均向CHO目标网络设备发送接收到的移动性报告。
此处的接收网络设备可以是源网络设备，也可以是第三网络设备。
S406，CHO目标网络设备向源网络设备发送所保存的CHO配置信息。
CHO目标网络设备在接收到移动性报告后，可以向源网络设备发送所保存的CHO配置信息，或者是CHO配置信息和移动性报告，或者是CHO配置信息和基于移动性报告得到的分析信息。
例如，CHO目标网络设备可以在向源网络设备发送的HO report消息中携带上述CHO配置信息，本申请实施例对于CHO目标网络设备向源网络设备发送CHO配置信息的方式不做 限制。
可见，通过上述方案，引入接收网络设备和CHO目标网络设备间的的移动性报告的强制转发机制，使得移动性报告必须由接收网络设备转发给CHO目标网络设备，从而使得CHO目标网络设备可以有机会向源网络设备发送CHO配置信息，使得源网络设备可以获取对应的CHO配置信息，从而进行合理的移动性管理，提高移动性鲁棒性，提升用户体验。
又一种可能的实现方式中，接收网络设备可以是把移动性报告发送给第二次发生连接失败且连接失败类型为RLF的CHO目标网络设备，可能的场景为：终端设备检测到第一次连接失败(第一连接失败可以为终端设备和源小区之间的RLF，或者终端设备和满足CHO触发条件的第一个CHO目标小区之间的HOF)，执行小区选择，选择CHO目标小区为目标小区，终端设备成功执行CHO重建后，终端设备检测到和该CHO目标小区之间的无线链路失败。。也就是S404中，接收网络设备根据移动性报告中信息，确定终端设备检测到了两次连接失败，第一次连接失败为终端设备和源小区之间的RLF或者为终端设备和第一个满足CHO触发条件的CHO目标小区之间的HOF，且第二次连接失败为终端设备和小区选择确定的CHO目标小区之间的RLF，接收网络设备确定向该第二次连接失败对应的CHO目标小区所述的CHO目标网络设备发送移动性报告。那么S405可以替换为接收网络设备向该第二次连接失败对应的CHO目标小区所述的CHO目标网络设备发送移动性报告。
可选的，又一种可能的实现方式中，考虑到跨***或者跨制式的移动性场景，若终端设备生成的移动性报告为第一***/制式的编码格式，终端设备在第二***/制式下的小区向接收网络设备发送该移动性报告，终端设备可以用容器(container)的方式向该接收网络设备发送该移动性报告。为了辅助该接收网络设备更好的进行该移动性报告的转发，终端设备在该容器外，还可以指示转发的目的小区(简称转发小区)信息的信息。转发小区可以为源小区，成功完成CHO的CHO目标小区，检测到第二次连接失败且连接失败类型为RLF的CHO目标小区，成功完成CHO切换但是检测到RLF的目标小区的至少一个。可以理解的，若转发小区的数量大于或等于两个，终端设备还可以指示转发移动性报告的小区优先顺序。比如在终端设备检测到和源小区的RLF并成功完成CHO到CHO目标小区，终端设备可以指示接收网络设备先向CHO目标小区所属的CHO目标网络设备转发移动性报告，这样移动性报告可以转发到CHO目标网络设备，CHO目标网络设备可以根据移动性报告中的终端设备的标识信息，或者终端设备的标识信息和与CHO相关的时间信息确定终端设备的CHO配置信息，CHO目标网络设备可以向源网络设备发送该CHO配置信息，和，移动性报告或者基于移动性报告的分析信息，从而使得源网络设备可以根据移动性报告或者基于移动性报告的分析信息，对该CHO配置信息进行优化，提升后续移动性管理的鲁棒性。可以理解的，本段落中所描述的跨***或者跨制式的移动性场景下的移动性报告的发送机制可以适用于图4所示实施例的流程，也可以适用于其他流程，例如图2或者图3所示流程或者现有技术中的其他涉及到移动性报告转发的流程，本申请实施例对此不做限定。
本申请又一实施例的移动性管理的方法中，提供了源网络设备保存CHO配置信息的机制。
方式一：
若源网络设备确定没有收到CHO目标网络设备发送的HANDOVER SUCCESS，或者若源网络设备确定收到CHO目标网络设备发送的指示终端设备侧存储有移动性报告的指示信息，源网络设备保存CHO配置信息，也就是说源网络设备不释放CHO配置信息或者说暂时不释放CHO配置信息，比如源网络设备可以保存该CHO配置信息一段时间，比如48h。
可以理解的是，在源网络设备确定没有收到CHO目标网络设备发送的HANDOVER SUCCESS，或者源网络设备确定收到CHO目标网络设备发送的指示终端设备侧存储有移动性报告的指示信息之前，还可以包括：源网络设备和至少一个候选目标网络设备之间进行条件切换的准备流程，源网络设备向终端设备发送CHO配置信息，终端设备根据CHO配置信息成功完成CHO接入到CHO目标小区。
方式二：
在又一种可能的实现方式中，终端设备和CHO目标网络设备成功完成CHO后，CHO目标网络设备可以启动第一定时器，若第一定时器运行时间内，CHO目标网络设备检测到终端设备和CHO目标小区(也就是当前服务小区)间的连接失败(比如，CHO目标网络设备收不到调度的该终端设备的下行数据的反馈信息，或者，接收到其它网络设备发送的失败指示信息，用于指示终端设备在其它网络设备重建等其它方式)，CHO目标网络设备向源网络设备发送指示信息，指示源网络设备保存终端设备的CHO配置信息，也就是说源网络设备不释放CHO配置信息或者说暂时不释放CHO配置信息。
或者可以是，若第一定时器运行时间内，CHO目标网络设备检测到终端设备和CHO目标小区间的连接失败，CHO目标网络设备不向源网络设备发送HANDOVER SUCCESS消息或者UE Context Release消息，那么源网络设备会认为CHO失败，源网络设备保存终端设备的CHO配置信息，也就是说源网络设备不释放CHO配置信息或者说暂时不释放CHO配置信息。可选的，若第一定时器超期，CHO目标网络设备没有检测到终端设备和CHO目标网络设备的连接失败，CHO目标网络设备可以向源网络设备发送HANDOVER SUCCESS消息或者UE Context Release消息。源网络设备在接收到UE Context Release后，释放该终端设备的CHO配置信息。可选的，在第一定时器运行时间内，若检测到终端设备和服务小区的失败，CHO目标网络设备停止第一定时器。
方式三：
在又一种可能的实现方式中，源网络设备接收到CHO目标网络设备的HANDOVER SUCCESS消息后，源网络设备启动第二定时器，若第二定时器超期，源网络设备没有收到来自CHO目标网络设备的UE Context Release消息，源网络设备保存终端设备的CHO配置信息，也就是说源网络设备不释放CHO配置信息或者说暂时不释放CHO配置信息。或者可以是，若第二定时器运行时间内，源网络设备收到来自CHO目标网络设备的指示终端设备侧存储有移动性报告的指示信息，或者源网络设备收到来自CHO目标网络设备的指示终端设备和CHO目标网络设备间连接失败的指示信息，源网络设备保存终端设备的CHO配置信息，也就是说源网络设备不释放CHO配置信息或者说暂时不释放CHO配置信息。可选的，如果在第二定时器运行时间内，源网络设备收到来自CHO目标网络设备的指示终端设备侧存储有移动性报告的指示信息，或者源网络设备收到来自CHO目标网络设备的指示终端设备和CHO目标网络设备间连接失败的指示信息，源网络设备可以停止第二定时器。
方式四：
又一种可能的方式中，源网络设备接收到CHO目标网络设备发送的UE Context Release消息后，源网络设备启动第三定时器，若第三定时器运行时间内，源网络设备收到来自CHO目标网络设备的指示终端设备侧存储有移动性报告的指示信息，或者源网络设备收到来自CHO目标网络设备的指示终端设备和CHO目标网络设备间连接失败的指示信息，源网络设备保存终端设备的CHO配置信息，也就是说源网络设备不释放CHO配置信息或者说暂时不释放CHO配置信息。可选的，如果在第三定时器运行时间内，源网络设备收到来自CHO目 标网络设备的指示终端设备侧存储有移动性报告的指示信息，或者源网络设备收到来自CHO目标网络设备的指示终端设备和CHO目标网络设备间连接失败的指示信息，源网络设备可以停止第三定时器。
可以理解的是，上述第一定时器，第二定时器和第三定时器的运行时长可以是网络设备配置的，也可以是协议预定义的。可以理解的，第一定时器，第二定时器和第三定时器的配置方式可以相同，也可以不同。可选的，第一定时，第二定时器和第三定时器的运行时长可以相同，也可以不同。本申请实施例对此不做限定。此外，方式三或者方式四也可以和方式一或者方式二结合实现。
可以理解的，通过上述方式一至方式四的至少一种实现方式，可以使得网络设备在移动性过程中出现连接失败或者潜在连接失败的场景下，才保存CHO配置信息，减少了网络设备的存储开销。
需要说明的是，以上源网络设备保存CHO配置信息的机制可以结合图2-4所示实施例实现，也可以通过其他流程实现。以方式二为例，一种可能的流程可以如图5所示，包括：
S501，终端设备成功完成CHO，接入到CHO目标小区。
其中，关于S501可以参考S301处的描述，此处不再赘述。
S502，CHO目标网络设备启动第一定时器。
S503，CHO目标网络设备向源网络设备发送指示信息，指示源网络设备保存终端设备的CHO配置信息。
可选的，在第一定时器运行时间内，CHO目标网络设备检测到终端设备和CHO目标小区间的连接失败，因此执行S503。
其中，该指示信息可以是显式的指示是否保存终端设备的CHO配置信息，也可以是隐式的指示在第一定时器运行时间内，CHO目标网络设备检测到终端设备和CHO目标小区间的连接失败，从而源网络设备根据指示信息确定要保存CHO配置信息。
S504，源网络设备保存CHO配置信息。
也就是说在接收到上述指示信息后，源网络设备不释放CHO配置信息或者说暂时不释放CHO配置信息。
可选的，源网络设备可以进一步根据移动性报告和保存的CHO配置信息进行移动性管理。
移动性报告可以是源网络设备从终端设备或者其他网络设备或者核心网设备接收的，本申请实施例对此不做限定。
源网络设备可以基于保存的CHO配置信息确定是否需要调整后续的CHO配置，从而可以进行合理的移动性管理，提高移动性鲁棒性，提升用户体验。
可以理解的是，在以上方式所提供的机制的基础上进行相应的移动性管理方法流程的应用，可能有不同的变化或者调整，本申请实施例对于其他方式的移动性管理方法流程不一一举例说明。
需要说明的是，以上图2-图5所示实施例中，网络设备之间的交互，可以是直接的交互也可以是间接的交互。也就是说，源网络设备、CHO目标网络设备、第三网络设备两两之间可以直接(例如通过基站和基站间的接口，比如X2，Xn接口)或间接(例如通过基站和核心网设备的接口，比如S1或NG接口)完成交互。不同的接口传输的情况下，消息名称可能有所不同，本申请实施例对此不做限定。
以图3所示方法流程为例，图3是以网络设备之间可以交互为例说明的，在源网络设备 和CHO目标网络设备之间没有接口的场景下，源网络设备可以通过核心网设备向CHO目标网络设备发送各个消息或者信息。例如，通过源网络设备通过和核心网设备间的接口向核心网设备发送第一消息。示例性地，源网络设备通过S1或NG接口向核心网设备发送第一消息，由核心网设备向CHO目标网络设备转发从源网络设备接收到的第一消息或者第一消息中的内容。一些可能的实现方式中，源网络设备可以通过S1/NG接口上的以下消息中的一种向CHO目标网络设备发送第一消息或者第一消息中的内容：CHO配置请求消息、上行RAN配置传输(UPLINK RAN CONFIGURATION TRANSFER)消息、基站配置传输(eNB CONFIGURATION TRANSFER)消息或其它消息。对应的，CHO目标网络设备可以通过如下消息中的一种向核心网设备发送响应消息：CHO配置请求确认消息、CHO配置请求失败消息、上行RAN配置传输(UPLINK RAN CONFIGURATION TRANSFER)消息、基站配置传输(eNB CONFIGURATION TRANSFER)消息或其它消息。进一步的，源网络设备可以通过S1/NG/N2接口上的以下消息中的一种接收来自CHO目标网络设备的响应消息：CHO配置请求确认消息、CHO配置请求失败消息、下行RAN配置传输(DOWNLIKN RAN CONFIGURATION TRANSFER)消息、核心网设备配置传输(MME CONFIGURATION TRANSFER)消息或其它消息。此外，源网络设备和目标网络设备可以连接相同的核心网设备，也可以分别连接不同的核心网设备。可选的，其连接的核心网设备可以属于相同的制式，也可以属于不同的制式，比如源网络设备连接的核心网设备是AMF(access and mobility management function，接入移动管理功能)，目标网络设备连接的核心网设备可以为MME(mobility management entity，移动管理模块)。
需要说明的是，上述各个实施例中的源网络设备也可以称为第一网络设备，CHO目标网络设备可以称为第二网络设备。
下面结合附图介绍本申请实施例中用来实现上述方法的装置。因此，上文中的内容均可以用于后续实施例中，重复的内容不再赘述。为了实现上述本申请实施例提供的方法中的各功能，各网元或者装置可以包括硬件结构和/或软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。
图6为本申请实施例提供的通信装置600的示意性框图。该通信装置600可以对应实现上述图2-图5所示方法实施例中由终端设备或者源网络设备或者CHO目标网络设备或者接收网络设备实现的功能或者步骤。该通信装置600可以为网络设备或者可以适用于该网络设备的部件(例如芯片或者电路等)或者，该通信装置600可以为芯片***。本申请实施例中，芯片***可以由芯片构成，也可以包含芯片和其他分立器件。
如图6所示，该通信装置600包括收发模块601和处理模块602。可选的，该通信装置还可以包括存储模块。该存储模块可以用于存储数据、信息、指令中的一种或者多种。
一些示例中，通信装置600用于实现上述源网络设备的功能时：
一种可能的实现方式中，收发模块601用于向第二网络设备发送终端设备的CHO配置信息，可选的，处理模块602可以在收发模块601向第二网络设备发送终端设备的CHO配置信息后，释放该CHO配置信息。进一步的，在通信装置600获取到移动性报告后，收发模块601向该第二网络设备发送第一消息，请求该终端设备的CHO配置信息，并从该第二网络设备接收所述第一消息的响应消息。可选的，收发模块601还可以用于在向所述第二网络设备发送该终端设备的CHO配置信息之前，在该终端设备成功完成条件切换接入到该第二网络设备后，从该第二网络设备接收切换成功消息。
又一种可能的实现方式中，处理模块602确定没有收到第二网络设备发送的HANDOVER  SUCCESS，或者处理模块602确定收发模块601收到第二网络设备发送的指示终端设备侧存储有移动性报告的指示信息，处理模块602触发保存该终端设备的CHO配置信息。其中，可以是处理模块602自身实现CHO配置信息的保存，也可以是处理模块602通知或者指令存储模块保存CHO配置信息。
又一种可能的实现方式中，收发模块601用于从第二网络设备接收指示信息，该指示信息指示保存终端设备的CHO配置信息且该指示信息是该第二网络设备在第一定时器运行时间内检测到和CHO目标小区间的连接失败的情况下发送的，那么处理模块602触发保存该终端设备的CHO配置信息。
又一种可能的实现方式中，处理模块602用于确定终端设备的CHO失败，触发保存该终端设备的CHO配置信息。其中，处理模块602可以是在确定收发模块601没有接收到HANDOVER SUCCESS消息或者UE Context Release消息的情况下，确定CHO失败。
又一种可能的实现方式中，收发模块601用于从第二网络设备接收切换成功消息，处理模块602在收发模块601接收到切换成功消息后，启动第二定时器。若第二定时器超期，收发模块601没有收到来自第二网络设备的UE Context Release消息，处理模块602触发保存终端设备的CHO配置信息。或者可以是，若第二定时器运行时间内，收发模块601接收到来自第二网络设备的指示终端设备侧存储有移动性报告的指示信息，或者收发模块601接收到来自第二网络设备的指示终端设备和第二网络设备间连接失败的指示信息，处理模块602触发保存终端设备的CHO配置信息。可选的，如果在第二定时器运行时间内，收发模块601接收到来自第二网络设备的指示终端设备侧存储有移动性报告的指示信息，或者收发模块601接收到来自第二网络设备的指示终端设备和第二网络设备间连接失败的指示信息，处理模块602可以停止第二定时器。
又一种可能的实现方式中，收发模块601用于接收第二网络设备发送的UE Context Release消息，处理模块602在收发模块601接收到UE Context Release消息后，启动第三定时器。若第三定时器运行时间内，收发模块601接收到来自第二网络设备的指示终端设备侧存储有移动性报告的指示信息，或者收发模块601接收到来自第二网络设备的指示终端设备和第二网络设备间连接失败的指示信息，处理模块602触发保存终端设备的CHO配置信息。可选的，如果在第三定时器运行时间内，收发模块601接收到来自第二网络设备的指示终端设备侧存储有移动性报告的指示信息，或者收发模块601接收到来自第二网络设备的指示终端设备和第二网络设备间连接失败的指示信息，处理模块602可以停止第三定时器。
又一些示例中，通信装置600用于实现上述CHO目标网络设备的功能时：
一种可能的实现方式中，收发模块601用于从第一网络设备接收终端设备的条件切换配置信息，从所述第一网络设备接收第一消息，以及向第一网络设备发送第一消息的响应消息。其中，处理模块602可以用于确定通信装置600是否存储有该终端设备的CHO配置信息，或者是否可以通过其他方式获取到该终端设备的CHO配置信息。从而收发模块601可以根据处理模块602的确定结果发送不同的响应消息。
又一种可能的实现方式中，处理模块602在终端设备成功完成CHO后，启动第一定时器。若处理模块602确定在第一定时器运行时间内，检测到终端设备和服务小区的连接失败，收发模块601用于向第一网络设备发送指示第一网络设备保存CHO配置信息的信息；或者是，若处理模块602确定在第一定时器运行时间内，检测到终端设备和服务小区的连接失败，收发模块601不向第一网络设备发送HANDOVER SUCCESS消息或者UE Context Release消息。可选的，若第一定时器超期，若没有检测到终端设备和CHO目标小区的连接失败，收发模块 601可以向第一网络设备发送HANDOVER SUCCESS消息或者UE Context Release消息。
又一些示例中，通信装置600用于实现上述接收网络设备的功能时：
一种可能的实现方式中，收发模块601用于从终端设备接收移动性报告。
可选的，处理模块602可以根据接收到的移动性报告识别出终端设备成功完成CHO的CHO目标网络设备，强制收发模块601向该CHO目标网络设备发送接收到的移动性报告。
或者是，处理模块602可以是触发将移动性报告发送给第二次发生连接失败且连接失败类型为RLF的CHO目标网络设备。
又一种可能的实现方式中，收发模块601用于从终端设备接收移动性报告以及指示转发小区的信息，其中，该移动性报告为第一***或者制式的编码格式，接收该移动性报告时终端设备所在的小区属于第二***或者制式。可选的，收发模块601还可以从终端设备接收指示转发小区的优先顺序的信息。处理模块602根据收发模块601接收到的信息实现移动性报告的转发。
又一些示例中，通信装置600用于实现上述终端设备的功能时：
一种可能的实现方式中，收发模块601用于向接收网络设备发送移动性报告以及指示转发小区信息的信息，其中，该移动性报告为第一***或者制式的编码格式，发送该移动性报告时终端设备所在的小区属于第二***或者制式。可选的，收发模块601还可以向接收网络设备指示转发小区的优先顺序的信息。
又一种可能的实现方式中，收发模块601用于从源网络设备接收如S303处描述的CHO配置信息。
可以理解的是，关于通信装置600各个模块之间的耦合以及具体实现可以参考方法实施例中的描述，此处不再赘述。
应理解，本申请实施例中的处理模块602可以由至少一个处理器或处理器相关电路组件实现，收发模块601可以由收发器或收发器相关电路组件或者通信接口实现。存储模块可以通过至少一个存储器实现。此外，上述各个模块可以分离也可以集成，本申请实施例对此不做限定。
如图7所示，本申请实施例还提供了一种通信装置700，可以用于实现或用于支持通信装置700实现本申请各个实施例提供的方法中网络设备或终端设备的功能。该通信装置700包括至少一个处理器710和至少一个存储器720，用于存储程序指令和/或数据和/或信息。存储器720和处理器710耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器710可能和存储器720协同操作。处理器710可能读取存储器720中存储的程序指令和/或数据和/或信息，以使得通信装置700实现相应的方法。可选的，所述至少一个存储器中的至少一个可以包括于处理器中。
通信装置700还可以包括通信接口730，用于通过传输介质和其它设备进行通信，从而用于通信装置700中的装置可以和其它设备进行通信。
本申请实施例中不限定上述通信接口730、处理器710以及存储器720之间的具体连接介质。示例性的，本申请实施例在图7中以存储器720、处理器710以及通信接口730之间通过总线连接，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。
本申请实施例中，处理器可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实 现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
本申请实施例中，存储器可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。本申请实施例中的存储器还可以是电路或者其它任意能够实现存储功能的装置，用于存储程序指令和/或数据。
本申请实施例还提供一种通信***，用于实现上述方法实施例的全部或者部分步骤。例如，该通信***可以包括上述第一网络设备、第二网络设备、接收网络设备和终端设备中的一个或者多个。
本申请实施例中还提供一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得图2-图5所示实施例中终端设备执行的方法被执行。
本申请实施例中还提供一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得图2-图5所示实施例中网络设备执行的方法被执行。此处的网络设备可以是第一网络设备、第二网络设备、接收网络设备中的一种。
本申请实施例中还提供一种计算机程序产品，包括指令，当其在计算机上运行时，使得图2-图5所示实施例中网络设备或终端设备执行的方法被执行。
本申请上述各个实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。上述模块也可以称为单元。
本申请实施例提供的方法中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、用户设备或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，简称DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机可以存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，数字视频光盘(digital video disc，简称DVD))、或者半导体介质(例如,SSD)等。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (21)

  1. 一种移动性管理的方法，其特征在于，包括：
    第一网络设备从第二网络设备接收条件切换成功消息，所述第二网络设备为目标小区所属的网络设备，所述目标小区属于所述第一网络设备为终端设备配置的条件切换候选小区；
    所述第一网络设备向所述第二网络设备发送所述终端设备的条件切换相关的移动性信息，其中，所述条件切换的移动性信息用于指示为所述终端设备配置的小区的条件切换移动性参数对应的移动性标识或者索引。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备释放所述条件切换相关的移动性信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备从所述第二网络设备接收所述条件切换相关的移动性信息。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备从所述第二网络设备接收移动性报告，所述移动性报告来自所述终端设备。
  5. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备从所述第二网络设备接收基于移动性报告得到的分析信息，所述移动性报告来自所述终端设备。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，在所述终端设备从所述第一网络设备成功完成条件切换接入到所述第二网络设备后，所述第一网络设备从所述第二网络设备接收所述条件切换成功消息。
  7. 根据权利要求1至6任一所述的方法，其特征在于，在所述终端设备未检测到和所述条件切换目标小区之间的无线链路失败或者所述终端设备检测到和所述条件切换目标小区之间的无线链路失败的情况下，所述第一网络设备从所述第二网络设备接收所述条件切换相关的移动性信息。
  8. 一种移动性管理的方法，其特征在于，包括：
    第二网络设备向第一网络设备发送条件切换成功消息，所述第二网络设备为目标小区所属的网络设备，所述目标小区属于所述第一网络设备为终端设备配置的条件切换候选小区；
    所述第二网络设备从所述第一网络设备接收所述终端设备的条件切换相关的移动性信息，其中，所述条件切换的移动性信息用于指示为所述终端设备配置的小区的条件切换移动性参数对应的移动性标识或者索引。
  9. 根据权利要求8所述的方法，其特征在于，在所述终端设备从所述第一网络设备成功完成条件切换接入到所述第二网络设备后，所述第二网络设备向所述第一网络设备发送切换成功消息。
  10. 根据权利要求8或9所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备从接收网络设备接收所述终端设备的移动性报告，所述接收网络设备为从终端设备接收移动性报告的网络设备。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备向所述第一网络设备发送所述条件切换相关的移动性信息。
  12. 根据权利要求11所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备向所述第一网络设备发送所述移动性报告。
  13. 根据权利要求11所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备向所述第一网络设备发送基于所述移动性报告得到的分析信息，所述移动性报告来自所述终端设备。
  14. 根据权利要求8-13任一项所述的方法，其特征在于，在所述终端设备未检测到和所述条件切换目标小区之间的无线链路失败或者所述终端设备检测到和所述条件切换目标小区之间的无线链路失败的情况下，所述第二网络设备向所述第一网络设备发送所述条件切换相关的移动性信息。
  15. 一种通信方法，其特征在于，包括：
    接收网络设备从终端设备接收移动性报告；
    所述接收网络设备根据接收到的移动性报告识别出终端设备成功完成条件切换的目标网络设备，强制向所述目标网络设备发送接收到的移动性报告。
  16. 一种通信装置，其特征在于，所述装置包括用于实现如权利要求1-7任一项所述的方法的至少一个模块。
  17. 一种通信装置，其特征在于，所述装置包括用于实现如权利要求8-14任一项所述的方法的至少一个模块。
  18. 一种通信装置，其特征在于，所述装置包括用于实现如权利要求15所述的方法的至少一个模块。
  19. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有指令，当所述指令被运行时，使得如权利要求1至15任一项所述的方法被执行。
  20. 一种通信***，其特征在于，包括如权利要求16所述的通信装置和如权利要求17所述的通信装置。
  21. 根据权利要求20所述的***，其特征在于，还包括如权利要求18所述的通信装置。
PCT/CN2022/110420 2021-08-06 2022-08-05 移动性管理的方法及通信装置 WO2023011612A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP22852323.9A EP4380236A1 (en) 2021-08-06 2022-08-05 Mobility management method and communication apparatus
US18/434,174 US20240179605A1 (en) 2021-08-06 2024-02-06 Mobility management method and communication apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110900350.3A CN115706963A (zh) 2021-08-06 2021-08-06 移动性管理的方法及通信装置
CN202110900350.3 2021-08-06

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/434,174 Continuation US20240179605A1 (en) 2021-08-06 2024-02-06 Mobility management method and communication apparatus

Publications (1)

Publication Number Publication Date
WO2023011612A1 true WO2023011612A1 (zh) 2023-02-09

Family

ID=85155319

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/110420 WO2023011612A1 (zh) 2021-08-06 2022-08-05 移动性管理的方法及通信装置

Country Status (4)

Country Link
US (1) US20240179605A1 (zh)
EP (1) EP4380236A1 (zh)
CN (1) CN115706963A (zh)
WO (1) WO2023011612A1 (zh)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020122797A1 (en) * 2018-12-14 2020-06-18 Telefonaktiebolaget Lm Ericsson (Publ) Conditional mobility
TW202033049A (zh) * 2019-02-01 2020-09-01 美商高通公司 用於傳送行動性資訊的技術
CN112243273A (zh) * 2019-07-16 2021-01-19 夏普株式会社 信息上报方法及对应的用户设备
CN113056934A (zh) * 2018-09-18 2021-06-29 诺基亚技术有限公司 使用条件切换的通信连接控制
CN113141667A (zh) * 2020-01-17 2021-07-20 ***通信有限公司研究院 随机接入方法、信息处理方法、装置、终端及网络侧设备
CN113170368A (zh) * 2018-12-18 2021-07-23 瑞典爱立信有限公司 有条件移动性选择
WO2021150054A1 (en) * 2020-01-23 2021-07-29 Lg Electronics Inc. Method and apparatus for mobility handling in wireless communication system

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113056934A (zh) * 2018-09-18 2021-06-29 诺基亚技术有限公司 使用条件切换的通信连接控制
WO2020122797A1 (en) * 2018-12-14 2020-06-18 Telefonaktiebolaget Lm Ericsson (Publ) Conditional mobility
CN113170368A (zh) * 2018-12-18 2021-07-23 瑞典爱立信有限公司 有条件移动性选择
TW202033049A (zh) * 2019-02-01 2020-09-01 美商高通公司 用於傳送行動性資訊的技術
CN112243273A (zh) * 2019-07-16 2021-01-19 夏普株式会社 信息上报方法及对应的用户设备
CN113141667A (zh) * 2020-01-17 2021-07-20 ***通信有限公司研究院 随机接入方法、信息处理方法、装置、终端及网络侧设备
WO2021150054A1 (en) * 2020-01-23 2021-07-29 Lg Electronics Inc. Method and apparatus for mobility handling in wireless communication system

Also Published As

Publication number Publication date
EP4380236A1 (en) 2024-06-05
CN115706963A (zh) 2023-02-17
US20240179605A1 (en) 2024-05-30

Similar Documents

Publication Publication Date Title
US20230345312A1 (en) User mobility method and device
US20200396652A1 (en) Method, apparatus, computer program product and computer program for conditional handover
RU2763519C2 (ru) Способ передачи обслуживания, терминальное устройство и сетевое устройство
US11665601B2 (en) Method for handover report and terminal device
WO2021088270A1 (zh) 移动性优化方法及相关装置
US20210251032A1 (en) Communication method, apparatus, and system
WO2020199992A1 (zh) 一种通信方法及装置
US20220191755A1 (en) Optional Sending of Complete Message in Conditional Handover
US20230262567A1 (en) Communication Method and Communication Apparatus
WO2022152220A1 (zh) 连接失败信息的处理方法、装置和***
WO2022083469A1 (zh) 一种mro临界场景的判定方法、装置及设备
US20230262545A1 (en) Link recovery via cells prepared with information for handovers including cho and daps
WO2023011612A1 (zh) 移动性管理的方法及通信装置
KR102345904B1 (ko) 기지국장치 및 기지국장치의 무선모듈 간 핸드오버 방법
WO2019140561A1 (zh) 一种切换方法及装置、计算机存储介质
WO2022227841A1 (zh) 一种优化移动性能的方法及通信装置
WO2023011077A1 (zh) 通信方法及装置
WO2024093931A1 (zh) 一种通信方法及装置
WO2023179736A1 (zh) 通信方法和通信装置
WO2023231929A1 (zh) 通信方法和装置
WO2023131280A1 (zh) 信息记录方法、通信装置、以及计算机存储介质
US20230388873A1 (en) Method and apparatus for determining daps handover failure type
WO2024016938A1 (zh) 一种通信方法及装置
WO2023024384A1 (zh) 小区切换、配置方法及装置、计算机可读存储介质、用户设备、网络设备
WO2023207229A1 (zh) 一种会话建立方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22852323

Country of ref document: EP

Kind code of ref document: A1

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112024002310

Country of ref document: BR

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022852323

Country of ref document: EP

Effective date: 20240301

ENP Entry into the national phase

Ref document number: 112024002310

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20240205