WO2021062845A1 - 通信方法和通信装置 - Google Patents

通信方法和通信装置 Download PDF

Info

Publication number
WO2021062845A1
WO2021062845A1 PCT/CN2019/109774 CN2019109774W WO2021062845A1 WO 2021062845 A1 WO2021062845 A1 WO 2021062845A1 CN 2019109774 W CN2019109774 W CN 2019109774W WO 2021062845 A1 WO2021062845 A1 WO 2021062845A1
Authority
WO
WIPO (PCT)
Prior art keywords
cell
cho
configuration information
candidate
rrc message
Prior art date
Application number
PCT/CN2019/109774
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 PCT/CN2019/109774 priority Critical patent/WO2021062845A1/zh
Publication of WO2021062845A1 publication Critical patent/WO2021062845A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements

Definitions

  • the present application relates to the field of wireless communication, and more specifically, to a communication method and communication device in the field of wireless communication.
  • the network device can send a handover message to the terminal device to indicate the target cell that can be handed over, as well as configuration information related to the handover and subsequent communication.
  • the terminal device may first evaluate whether it can comply with (or comply with) the configuration information in the handover message. When it is determined that it can be complied with, the terminal device can perform subsequent handover procedures, such as a random access procedure with the target cell. In the case where it is determined that it cannot be complied with, the terminal device can initiate a re-establishment procedure.
  • LTE long term evolution
  • 5G fifth generation
  • a network device can configure one or more candidate cells for a terminal device, and provide a handover execution condition (or trigger condition) for each candidate cell.
  • the terminal device may try to switch to a candidate cell when the execution condition of the handover of a certain candidate cell is satisfied.
  • This switching mechanism can be called conditional handover (CHO), and the corresponding execution condition can be called CHO execution condition.
  • the network device may also indicate the parameters corresponding to the one or more candidate cells to the terminal device, so that the terminal device can switch to a certain candidate cell and can communicate normally in the candidate cell.
  • the terminal device may not necessarily be able to comply with the CHO execution conditions and parameters of all candidate cells configured by the network device. Therefore, in the case that the terminal device cannot comply with the CHO execution conditions and/or parameters of some candidate cells configured by the network device, how the terminal device should deal with is a technical problem to be solved urgently.
  • the present application provides a communication method and communication device, in order to provide a reasonable operation process for the terminal equipment in the case that the terminal equipment cannot comply with the CHO execution conditions and/or parameters of some candidate cells, so as to reduce the handover as much as possible.
  • the duration of communication interruption improves the user experience.
  • a communication method includes: receiving a first radio resource control (radio resource control, RRC) message, where the first RRC message includes conditional handover CHO of one or more candidate cells Configuration information, the CHO configuration information of the one or more candidate cells includes CHO execution conditions and parameters corresponding to each candidate cell; if the CHO configuration information of some candidate cells of the one or more candidate cells cannot be complied with In this case, it is determined whether there is a cell that meets the CHO execution condition among the candidate cells to which the CHO configuration information can be complied with.
  • RRC radio resource control
  • the terminal device may not initiate a re-establishment procedure, but preferentially try handover when it is determined that it cannot comply with the CHO configuration information of some candidate cells.
  • the terminal device can try to find a cell that satisfies the CHO execution condition in the part of candidate cells where the CHO configuration information can be complied with, and try to switch to that cell. Therefore, the delay and complexity caused by the re-establishment process can be avoided, and the impact of a long-term communication interruption on the user experience can be avoided, which is beneficial to improve system reliability, ensure system performance, and improve user experience.
  • the method further includes: if there is the cell that meets the CHO execution condition among the candidate cells for which the CHO configuration information can be complied with, attempting to switch to the A cell that meets the execution conditions of CHO.
  • the terminal device can find a cell that satisfies the CHO execution condition from among the candidate cells to which the CHO configuration information can be complied with, to try to switch to the cell.
  • the terminal device can perform this step once, such as successfully switching through a switching process, or failing to switch through a switching process, but not performing this step; or, the terminal device can also perform this step multiple times, such as through If a cell is successfully accessed through multiple handover procedures, or if no handover is successful through multiple handover procedures, then this step is not executed again. This application does not limit this.
  • the method further includes: if there is no cell that meets the CHO execution condition among the candidate cells for which the CHO configuration information can be complied with, or if it is tried The process of switching to the cell that meets the CHO execution condition fails, and the re-establishment process is initiated.
  • the terminal device can initiate Re-establish the process.
  • a communication method includes: receiving a first RRC message, the first RRC message including conditional handover CHO configuration information of one or more candidate cells, and
  • the CHO configuration information includes CHO execution conditions and parameters corresponding to each candidate cell; in the case that the CHO configuration information of some candidate cells among the one or more candidate cells cannot be complied with, determine the first cell that satisfies the S criterion; It is determined whether the first cell is included in a candidate cell whose CHO configuration information can be complied with.
  • the terminal device may not initiate a re-establishment procedure, but preferentially try handover when it is determined that it cannot comply with the CHO configuration information of some candidate cells.
  • the terminal equipment can determine a cell that satisfies the S criterion through cell selection, so it can find a cell suitable for handover from more dimensions. In this way, the delay and complexity caused by the re-establishment process can be avoided, and the impact of a long communication interruption on the user experience can be avoided, which is conducive to improving system reliability, ensuring system performance, and improving user experience.
  • the method further includes: if the first cell is included in the candidate cell for which the CHO configuration information can be complied with, attempting to switch to the first Community.
  • the terminal device may try to switch to the cell in the case where the cell that meets the S criterion determined above is included in the candidate cell whose CHO configuration information can be complied with.
  • the terminal device can perform this step once, such as a successful handover through a handover process, or a handover process that is not successful but does not perform this step again, or no other cells that meet the S criterion are found to be included in the CHO configuration information Among the candidate cells that can be followed; or, the terminal device can also perform this step multiple times, such as successfully accessing a cell through multiple handover procedures, or if handover is unsuccessful through multiple handover procedures, it will no longer be performed The step.
  • the method further includes: if the first cell is not included in the candidate cell for which the CHO configuration information can be complied with, or if an attempt is made to switch to The process of the first cell fails, and a re-establishment process is initiated.
  • the terminal device may initiate a re-establishment procedure when the determined cell satisfying the S criterion is not included in the candidate cell whose CHO configuration information can be complied with, or when it is not successfully handed over to the first cell.
  • a communication method includes: receiving a first RRC message, the first RRC message including conditional handover CHO configuration information of one or more candidate cells, and
  • the CHO configuration information includes the CHO execution conditions and the parameters corresponding to each candidate cell; in the case that the CHO execution conditions of some of the one or more candidate cells cannot be complied with, determine the one or more candidate cells There is at least one first candidate cell that meets the CHO execution condition in some candidate cells that can be complied with the CHO execution condition; it is determined whether there is a cell whose parameters corresponding to the CHO configuration information can be complied with in the at least one first candidate cell.
  • the terminal device may not initiate a re-establishment procedure, but preferentially try handover when it is determined that it cannot comply with the CHO execution conditions of some candidate cells.
  • the terminal device can determine the cell that meets the CHO execution condition from the candidate cells where the CHO execution condition is complied with, and then determine the cell to which the corresponding parameter in the CHO configuration information can be complied with from the determined cells that meet the CHO execution condition. To try to switch. Therefore, the delay and complexity caused by the re-establishment process can be avoided, and the impact of a long-term communication interruption on the user experience can be avoided, which is beneficial to improve system reliability, ensure system performance, and improve user experience.
  • the terminal device since the terminal device only needs to evaluate whether the CHO execution conditions of each candidate cell can be evaluated after receiving the first RRC message, after determining the cells that meet the CHO execution conditions, it evaluates whether the parameters in the CHO configuration information of these cells Being able to be complied with can reduce the number of candidate cells to be evaluated, reduce the workload of the terminal equipment, and reduce the complexity of implementation.
  • the method further includes: if there is a cell whose parameters in the CHO configuration information can be complied with in the at least one first candidate cell, try to switch to The cell to which the corresponding parameter in the CHO configuration information can be complied with.
  • the terminal device can find a cell whose corresponding parameter can be complied with from the cells satisfying the CHO execution condition to try to handover.
  • the terminal device can perform this step once, such as successfully switching through a switching process, or failing to switch through a switching process, but not performing this step; or, the terminal device can also perform this step multiple times, such as through If a cell is successfully accessed through multiple handover procedures, or if no handover is successful through multiple handover procedures, then this step is not executed again. This application does not limit this.
  • the method further includes: if the at least one first candidate cell does not have a cell with which the parameter corresponding to the CHO configuration information can be complied with, or If the process of attempting to switch to a cell to which the parameters corresponding to the CHO configuration information can be complied with fails, a re-establishment process is initiated.
  • the terminal device can initiate the re-establishment process.
  • the method further includes: receiving a second RRC message, but the integrity protection check of the second RRC message fails, so The second RRC message is a message received after the first RRC message is received; a cell that satisfies the S criterion is determined; the cell that satisfies the S criterion is included in the candidate cells to which the CHO configuration information can be complied with In the case of, try to switch to the cell that satisfies the S criterion.
  • the terminal device may select a cell that satisfies the S criterion through cell selection, and try to handover when the cell is included in a candidate cell whose CHO configuration information can be complied with.
  • the terminal device can perform this step once or multiple times, which is not limited in this application. As a result, the terminal device can switch to a certain candidate cell with a greater probability and avoid the execution of the re-establishment procedure to a greater extent.
  • the parameters corresponding to the candidate cell in the CHO configuration information include one or more of the following: the candidate cell allocates the cell wireless for the terminal device Temporary network identification C-RNTI, random access channel RACH resource of the candidate cell, cell global identification CGI of the candidate cell, physical cell identification PCI of the candidate cell, absolute frequency of the synchronization signal block SSB corresponding to the candidate cell, reference resource block The absolute frequency, frequency bandwidth list, subcarrier spacing SCS specific carrier list, physical layer configuration parameters of candidate cells, media access control MAC layer configuration parameters of candidate cells, radio link control RLC layer configuration parameters of candidate cells, grouping Data convergence layer protocol PDCP layer configuration parameters, service data adaptive protocol SDAP layer configuration parameters, RRC layer configuration parameters, and bearer configuration information.
  • a communication method comprising: receiving a first RRC message, the first RRC message including CHO configuration information of one or more candidate cells, and CHO configuration of the one or more candidate cells
  • the information includes CHO execution conditions and parameters corresponding to each candidate cell; a third RRC message is received, and the third RRC message includes CHO configuration information of one or more candidate cells; one or more of the third RRC messages
  • the CHO configuration information of the candidate cell is used to update the CHO configuration information of one or more candidate cells in the first RRC message; according to the first RRC message and the third RRC message, in the non-compliant part
  • the CHO configuration information of the candidate cell it is determined whether there is a cell that satisfies the CHO execution condition among the candidate cells to which the CHO configuration information can be complied with.
  • the terminal device can reconfigure/update the candidate cell based on the received third RRC message.
  • the terminal device may not initiate a re-establishment procedure, but preferentially try handover when it is determined that it cannot comply with the CHO configuration information of some candidate cells.
  • the terminal device can try to find a cell that satisfies the CHO execution condition in the part of candidate cells where the CHO configuration information can be complied with, and try to switch to that cell. Therefore, the delay and complexity caused by the re-establishment process can be avoided, and the impact of a long-term communication interruption on the user experience can be avoided, which is beneficial to improve system reliability, ensure system performance, and improve user experience.
  • the CHO configuration information may be the CHO configuration information obtained after the candidate cell is reconfigured based on the third RRC message.
  • it may be the CHO configuration information determined jointly according to the first RRC message and the third RRC message, or may be based on CHO configuration information determined by the third RRC message.
  • the CHO execution condition may be the CHO execution condition in the CHO configuration information obtained after the candidate cell is reconfigured.
  • the method further includes: if there is the cell that meets the CHO execution condition among the candidate cells for which the CHO configuration information can be complied with, attempting to switch to the A cell that meets the execution conditions of CHO.
  • the terminal device can find a cell that satisfies the CHO execution condition from among the candidate cells to which the CHO configuration information can be complied with, to try to switch to the cell.
  • the terminal device can perform this step once, such as successfully switching through a switching process, or failing to switch through a switching process, but not performing this step; or, the terminal device can also perform this step multiple times, such as through If a cell is successfully accessed through multiple handover procedures, or if no handover is successful through multiple handover procedures, then this step is not executed again. This application does not limit this.
  • the method further includes: if the CHO configuration information can be complied with candidate cells, there is no cell that meets the CHO execution condition, or if it is tried The process of handover to the cell that meets the CHO execution conditions fails, and the second cell that meets the S criterion is determined; if the second cell is included in the candidate cells that can be complied with the CHO configuration information, try to handover to the first cell. Second cell.
  • the terminal device can execute Cell selection to find a suitable cell for handover. If the cell determined by the terminal device through cell selection is included in the candidate cell to which the CHO configuration information can be complied with, it can try to switch to that cell.
  • the method further includes: if the CHO configuration information can be complied with candidate cells, there is no cell that meets the CHO execution condition, or if it is tried The process of handover to the cell meeting the CHO execution condition fails, and the second cell meeting the S criterion is determined; if the second cell is not included in the candidate cell whose CHO configuration information can be complied with, a re-establishment process is initiated.
  • the terminal device can execute Cell selection to find a suitable cell for handover. If the cell determined by the terminal device through cell selection is not included in the candidate cell to which the CHO configuration information can be followed, the re-establishment procedure can be initiated.
  • the method further includes: if the CHO configuration information can be complied with candidate cells, there is no cell that meets the CHO execution condition, or if it is tried The process of switching to the cell that meets the CHO execution condition fails, and the re-establishment process is initiated.
  • the terminal device can initiate Re-establish the process.
  • a communication method comprising: receiving a first RRC message, the first RRC message including CHO configuration information of one or more candidate cells, and CHO configuration of the one or more candidate cells
  • the information includes CHO execution conditions and parameters corresponding to each candidate cell; a third RRC message is received, and the third RRC message includes CHO configuration information of one or more candidate cells; one or more of the third RRC messages
  • the CHO configuration information of the candidate cell is used to update the CHO configuration information of one or more candidate cells in the first RRC message; according to the first RRC message and the third RRC message, in the non-compliant part
  • determine the third cell that satisfies the S criterion determine whether the third cell is included in the candidate cell to which the CHO configuration information can be complied with.
  • the terminal device can reconfigure/update the candidate cell based on the received third RRC message.
  • the terminal device may not initiate a re-establishment procedure, but preferentially try handover when it is determined that it cannot comply with the CHO configuration information of some candidate cells.
  • the terminal equipment can determine a cell that satisfies the S criterion through cell selection, so it can find a cell suitable for handover from more dimensions. In this way, the delay and complexity caused by the re-establishment process can be avoided, and the impact of a long communication interruption on the user experience can be avoided, which is conducive to improving system reliability, ensuring system performance, and improving user experience.
  • the CHO configuration information may be the CHO configuration information obtained after the candidate cell is reconfigured based on the third RRC message.
  • it may be the CHO configuration information determined jointly according to the first RRC message and the third RRC message, or may be based on CHO configuration information determined by the third RRC message.
  • the method further includes: if the third cell is included in the candidate cell for which the CHO configuration information can be complied with, attempting to switch to the third Community.
  • the terminal device may try to switch to the cell in the case where the cell that meets the S criterion determined above is included in the candidate cell whose CHO configuration information can be complied with.
  • the terminal device can perform this step once, such as a successful handover through a handover process, or a handover process that is not successful but does not perform this step again, or no other cells that meet the S criterion are found to be included in the CHO configuration information Among the candidate cells that can be followed; or, the terminal device can also perform this step multiple times, such as successfully accessing a cell through multiple handover procedures, or if handover is unsuccessful through multiple handover procedures, it will no longer be performed The step.
  • the method further includes: if the third cell is not included in the candidate cell for which the CHO configuration information can be complied with, or if an attempt is made to switch to The process of the third cell fails, and a re-establishment process is initiated.
  • the terminal device may initiate a re-establishment procedure when the determined cell satisfying the S criterion is not included in the candidate cell whose CHO configuration information can be complied with, or when it is not successfully handed over to the first cell.
  • a communication method includes: receiving a first radio resource control RRC message, where the first RRC message includes conditional handover CHO configuration information of one or more candidate cells, and the one or more The CHO configuration information of the candidate cell includes the CHO execution conditions and the parameters corresponding to each candidate cell; the third RRC message is received, and the third RRC message includes the CHO configuration information of one or more candidate cells; The CHO configuration information of one or more candidate cells is used to update the CHO configuration information of one or more candidate cells in the first RRC message; In the case of the CHO configuration information of the cell, it is determined that there is at least one second candidate cell that meets the CHO execution condition among the candidate cells for which the CHO execution condition can be complied with; and it is determined whether the at least one second candidate cell contains the CHO configuration information. The cell to which the corresponding parameter can be complied with.
  • the terminal device can reconfigure/update the candidate cell based on the received third RRC message.
  • the terminal device may not initiate a re-establishment procedure, but preferentially try handover when it is determined that it cannot comply with the CHO execution conditions of some candidate cells.
  • the terminal device can determine the cell that meets the CHO execution condition from the candidate cells where the CHO execution condition is complied with, and then determine the cell to which the corresponding parameter in the CHO configuration information can be complied with from the determined cells that meet the CHO execution condition. To try to switch. Therefore, the delay and complexity caused by the re-establishment process can be avoided, and the impact of a long-term communication interruption on the user experience can be avoided, which is beneficial to improve system reliability, ensure system performance, and improve user experience.
  • the terminal device after receiving the first RRC message and the third RRC message, the terminal device only needs to evaluate whether the CHO execution conditions of each candidate cell can be evaluated. After determining the cells that meet the CHO execution conditions, the CHO of these cells is evaluated. Whether the parameters in the configuration information can be complied with can reduce the number of candidate cells to be evaluated, reduce the workload of the terminal equipment, and reduce the complexity of implementation.
  • the CHO configuration information may be the CHO configuration information obtained after the candidate cell is reconfigured based on the third RRC message.
  • it may be the CHO configuration information determined jointly according to the first RRC message and the third RRC message, or may be based on CHO configuration information determined by the third RRC message.
  • the CHO execution condition may be the CHO execution condition in the CHO configuration information obtained after the candidate cell is reconfigured.
  • the method further includes: if there is a cell whose parameters in the CHO configuration information can be complied with in the at least one second candidate cell, trying to switch to The cell to which the corresponding parameter in the CHO configuration information can be complied with.
  • the terminal device can find a cell whose corresponding parameter can be complied with from the cells satisfying the CHO execution condition to try to handover.
  • the terminal device can perform this step once, such as successfully switching through a switching process, or failing to switch through a switching process, but not performing this step; or, the terminal device can also perform this step multiple times, such as through If a cell is successfully accessed through multiple handover procedures, or if no handover is successful through multiple handover procedures, then this step is not executed again. This application does not limit this.
  • the method further includes: if the at least one fourth candidate cell does not have a cell with which the parameter corresponding to the CHO configuration information can be complied with, or, If the handover fails, initiate a re-establishment process.
  • the terminal device can initiate a re-establishment process.
  • the parameter corresponding to the candidate cell is configured by the CHO configuration information in the first RRC message and the CHO configuration in the third RRC message
  • the information is determined, or determined by the CHO configuration information in the third RRC message
  • the parameters corresponding to the candidate cell include: the cell radio network temporary identifier C-RNTI allocated by the candidate cell to the terminal device, and the access candidate cell’s Random access channel RACH resource, cell global identification CGI of candidate cell, physical cell identification PCI of candidate cell, absolute frequency of synchronization signal block SSB corresponding to candidate cell, absolute frequency of reference resource block, frequency bandwidth list, subcarrier spacing SCS Specific carrier list, physical layer configuration parameters of candidate cells, medium access control MAC layer configuration parameters of candidate cells, radio link control RLC layer configuration parameters of candidate cells, packet data convergence layer protocol PDCP layer configuration parameters, service data self Adapt to the protocol SDAP layer configuration parameters, RRC layer configuration parameters, and bearer configuration information, etc.
  • a communication device which includes various modules or units for executing the method in any one of the possible implementation manners of the first aspect to the sixth aspect.
  • a communication device including a processor.
  • the processor is coupled with the memory and can be used to execute instructions or data in the memory to implement the method in any one of the possible implementation manners of the first aspect to the sixth aspect.
  • the communication device further includes a memory.
  • the communication device further includes a communication interface, and the processor is coupled with the communication interface.
  • the communication device is a terminal device.
  • the communication interface may be a transceiver, or an input/output interface.
  • the communication device is a chip configured in a terminal device.
  • the communication interface may be an input/output interface.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • a processor including: an input circuit, an output circuit, and a processing circuit.
  • the processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method in any one of the possible implementation manners of the first aspect to the sixth aspect.
  • the above-mentioned processor can be one or more chips
  • the input circuit can be an input pin
  • the output circuit can be an output pin
  • the processing circuit can be a transistor, a gate circuit, a flip-flop, and various logic circuits, etc.
  • the input signal received by the input circuit may be received and input by, for example, but not limited to, a receiver
  • the signal output by the output circuit may be, for example, but not limited to, output to the transmitter and transmitted by the transmitter
  • the circuit can be the same circuit, which is used as an input circuit and an output circuit at different times.
  • the embodiments of the present application do not limit the specific implementation manners of the processor and various circuits.
  • a processing device including a processor and a memory.
  • the processor is used to read instructions stored in the memory, and can receive signals through a receiver, and transmit signals through a transmitter, so as to execute the method in any one of the possible implementation manners of the first aspect to the sixth aspect.
  • processors there are one or more processors and one or more memories.
  • the memory may be integrated with the processor, or the memory and the processor may be provided separately.
  • the memory can be a non-transitory (non-transitory) memory, such as a read only memory (ROM), which can be integrated with the processor on the same chip, or can be set in different On the chip, the embodiment of the present application does not limit the type of the memory and the setting mode of the memory and the processor.
  • ROM read only memory
  • sending instruction information may be a process of outputting instruction information from the processor
  • receiving capability information may be a process of the processor receiving input capability information.
  • the data output by the processor can be output to the transmitter, and the input data received by the processor can come from the receiver.
  • the transmitter and receiver can be collectively referred to as a transceiver.
  • the processing device in the above tenth aspect may be one or more chips.
  • the processor in the processing device can be implemented by hardware or software.
  • the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor may be a general-purpose processor, which is implemented by reading the software code stored in the memory, and the memory may Integrated in the processor, can be located outside the processor, and exist independently.
  • a computer program product includes: a computer program (also called code, or instruction), which when the computer program is executed, causes the computer to execute the first aspect to the The method in any possible implementation of the sixth aspect.
  • a computer program also called code, or instruction
  • a computer-readable medium stores a computer program (also called code, or instruction) when it runs on a computer, so that the computer executes the above-mentioned first aspect to The method in any possible implementation of the sixth aspect.
  • a computer program also called code, or instruction
  • a communication system including the aforementioned network equipment and terminal equipment.
  • FIG. 1 is a schematic diagram of a communication system suitable for the communication method provided by an embodiment of the present application
  • FIG. 10 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a terminal device provided by an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a network device provided by an embodiment of the present application.
  • LTE long term evolution
  • FDD frequency division duplex
  • UMTS time division duplex
  • WiMAX worldwide interoperability for microwave access
  • 5G future 5th generation
  • NR new wireless
  • V2X can include vehicle-to-network (V2N), vehicle-to-vehicle (V2V), and vehicle-to-infrastructure (vehicle to infrastructure, V2I), vehicle to pedestrian (V2P), etc.
  • V2X can include vehicle-to-network (V2N), vehicle-to-vehicle (V2V), and vehicle-to-infrastructure (vehicle to infrastructure, V2I), vehicle to pedestrian (V2P), etc.
  • LTE-V long term evolution-vehicle
  • MTC machine type communication
  • M2M machine to machine
  • the network device may be any device with a wireless transceiver function.
  • Network equipment includes, but is not limited to: evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC) , Base transceiver station (BTS), home base station (for example, home evolved Node B, or home Node B, HNB), baseband unit (BBU), wireless fidelity (WIFI) system
  • eNB evolved Node B
  • RNC radio network controller
  • NB Node B
  • BSC base station controller
  • BTS Base transceiver station
  • home base station for example, home evolved Node B, or home Node B, HNB
  • BBU baseband unit
  • WIFI wireless fidelity
  • the access point (AP), wireless relay node, wireless backhaul node, transmission point (TP), or transmission and reception point (TRP), etc. can also be 5G (such as NR).
  • the gNB or transmission point (TRP or TP) in the system or one or a group of antenna panels (including multiple antenna panels) of the base station in the 5G system, or it can also be a network node that constitutes a gNB or transmission point, Such as baseband unit (BBU), or distributed unit (DU), etc.
  • BBU baseband unit
  • DU distributed unit
  • the gNB may include a centralized unit (CU) and a DU.
  • the gNB may also include an active antenna unit (AAU).
  • CU implements some functions of gNB, and DU implements some functions of gNB.
  • CU is responsible for processing non-real-time protocols and services, implementing radio resource control (RRC), and packet data convergence protocol (PDCP) The function of the layer.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • the DU is responsible for processing physical layer protocols and real-time services, and implements the functions of the radio link control (RLC) layer, medium access control (MAC) layer, and physical (physical, PHY) layer.
  • RLC radio link control
  • MAC medium access control
  • PHY physical layer
  • the network device may be a device that includes one or more of a CU node, a DU node, and an AAU node.
  • the CU may be divided into an access network device or a core network (core network, CN) device, which is not limited in this application.
  • core network core network, CN
  • the CU is divided into access network equipment.
  • the network equipment provides services for the cell, and the terminal equipment communicates with the cell through transmission resources (for example, frequency domain resources, or spectrum resources) allocated by the network equipment.
  • the cell may belong to a macro base station (for example, a macro eNB or a macro gNB, etc.), and may also belong to a base station corresponding to a small cell (small cell).
  • the small cells here may include: metro cells, micro cells, pico cells, femto cells, and so on. These small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-rate data transmission services.
  • terminal equipment may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal, Terminal, wireless communication equipment, user agent or user device.
  • the terminal device in the embodiment of the present application may be a mobile phone (mobile phone), a tablet computer (pad), a computer with a wireless transceiver function, a virtual reality (VR) terminal device, and an augmented reality (AR) terminal Equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, transportation safety ( Wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home (smart home), cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local Loop (wireless local loop, WLL) stations, personal digital assistants (personal digital assistants, PDAs), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wear
  • SIP session
  • wearable devices can also be called wearable smart devices, which are the general term for using wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories.
  • Wearable devices are not only a kind of hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, and need to cooperate with other devices such as smart phones.
  • the terminal device may also be a terminal device in the Internet of Things (IoT) system.
  • IoT Internet of Things
  • Its main technical feature is to connect objects to the network through communication technology, so as to realize the intelligent network of human-machine interconnection and interconnection of things.
  • This application does not limit the specific form of the terminal device.
  • the communication system 100 may include at least two network devices, such as the network device 110 and the network device 120 shown in FIG. 1; the communication system 100 may also include at least one terminal device, such as the one shown in FIG. Terminal equipment 130. Wherein, the terminal device 130 may be mobile or fixed.
  • the network device 110 and the network device 120 are both devices that can communicate with the terminal device 130 via a wireless link, such as a base station or a base station controller. Each network device can provide communication coverage for a specific geographic area, and can communicate with terminal devices located in the coverage area (cell).
  • Fig. 1 exemplarily shows two network devices and one terminal device, but this should not constitute any limitation to this application.
  • the communication system 100 may include more network devices, and the coverage of each network device may include other numbers of terminal devices.
  • the communication system 100 may also include one or more core network devices. The embodiments of this application do not limit this.
  • Each of the aforementioned communication devices may be configured with multiple antennas.
  • the plurality of antennas may include at least one transmitting antenna for transmitting signals and at least one receiving antenna for receiving signals.
  • each communication device additionally includes a transmitter chain and a receiver chain.
  • Those of ordinary skill in the art can understand that they can include multiple components related to signal transmission and reception (such as processors, modulators, multiplexers , Demodulator, demultiplexer or antenna, etc.). Therefore, multiple antenna technology can be used to communicate between network devices and terminal devices.
  • the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity, and the embodiment of the present application is not limited thereto.
  • each network device can be divided into one or more cells, and each cell can correspond to one or more frequency points, or in other words, each cell can be regarded as the coverage area of one or more frequency points.
  • the area of formation can be divided into one or more cells, and each cell can correspond to one or more frequency points, or in other words, each cell can be regarded as the coverage area of one or more frequency points.
  • the cell may be an area within the coverage of the wireless network of the network device.
  • different cells may correspond to the same or different network devices.
  • the network equipment to which cell #1 belongs and the network equipment to which cell #2 belongs may be different network equipment, such as a base station. That is, cell #1 and cell #2 can be managed by different base stations.
  • the network equipment that manages cell #1 and the network equipment that manages cell #2 may also be different radio frequency processing units of the same base station, for example, a radio remote unit (RRU), that is, Cell #1 and cell #2 can be managed by the same base station, have the same baseband processing unit and intermediate frequency processing unit, but have different radio frequency processing units.
  • RRU radio remote unit
  • the network device to which cell #1 belongs and the network device to which cell #2 belongs may be the same network device, such as a base station. That is to say, cell #1 and cell #2 can be managed by the same base station, in this case, it can be said that cell #1 and cell #2 are co-sited. This application does not specifically limit this.
  • gNB may include CU and DU in some possible deployments.
  • cell #1 and cell #2 can be managed by the same CU and the same DU, that is, share CU and share DU; cell #1 and cell #2 can be managed by the same CU and different DUs, That is, they share CU but do not share DU; cell #1 and cell #2 may also be managed by different CUs and different DUs, that is, do not share CU and do not share DU.
  • Handover In a wireless communication system, when a terminal device moves/closes from one cell to another cell, in order to keep the communication of the terminal device uninterrupted, a handover is required.
  • the source cell refers to a cell that provides services for the terminal device before handover
  • the target cell refers to a cell that provides services for the terminal device after the handover.
  • Relevant information of the target cell can be indicated by a handover message, which is the source cell It is sent to the terminal device by its own network device (that is, the source network device).
  • the handover can be intra-station handover or inter-station handover.
  • In-site handover means that the source cell and target cell belong to the same network equipment (such as a base station), where the source cell and target cell can be the same cell or different cells;
  • inter-site handover means that the source cell and the target cell belong to different Network equipment (such as base stations). This application does not limit this.
  • the cell is the coverage area of the network equipment
  • the source cell corresponds to the source network equipment (for example, the source base station)
  • the target cell corresponds to the target network equipment (for example, the target base station).
  • the mobility management of the terminal equipment is controlled by the network equipment. That is, the network device instructs the terminal device to switch to which cell and how to switch by sending a handover message.
  • the source network device sends a handover message to the terminal device to control the terminal device to switch from the source cell to the target cell.
  • the handover message may be an RRC message.
  • the RRC message may be an RRC connection reconfiguration message carrying mobility control information (mobility control info); in an NR system, the RRC message may be a synchronization reconfiguration information element (reconfiguration with reconfiguration information). sync) RRC reconfiguration message.
  • the handover message contains the parameters required by the target network device (that is, the network device to which the target cell belongs) configured for the terminal device to access the target cell. For example, it contains the information of the target cell (such as the physical cell identifier of the target cell). identifier, PCI) and the frequency information corresponding to the target cell, the C-RNTI allocated by the target network device to the terminal device), and the random access channel (RACH) resource information required to access the target cell (e.g., dedicated RACH) Resources and/or public RACH resources), etc.
  • the terminal device initiates a random access procedure to the target network device according to the content contained in the handover message.
  • the target network device can consider the beam characteristics when configuring the RACH resource information required to access the target cell. For example, when configuring RACH resources, the target network device may configure RACH resources associated with beams (such as SSB or CSI-RS) under the target cell.
  • RACH resources associated with beams such as SSB or CSI-RS
  • the handover message and the foregoing RRC message for indicating handover are described from different perspectives.
  • the handover message is described from a functional point of view, and aims to express that the message is used to instruct the terminal device to switch.
  • the RRC message is described from the perspective of message type, and aims to express that the message is high-level signaling.
  • the RRC reconfiguration message is an enumeration of RRC messages. In other words, the handover message is sent to the terminal device through high-level signaling.
  • RRC messages are listed above, such as the RRC connection reconfiguration message in LTE, the RRC reconfiguration message in NR, etc. These messages are only examples for ease of understanding and should not constitute any limitation to this application. This application does not limit the specific name of the RRC message used to instruct the terminal device to initiate the handover procedure.
  • the target cell involved in the embodiment of the present application is not necessarily a cell configured based on a traditional handover procedure.
  • the terminal device can also perform handover based on the conditional handover mechanism described below.
  • the terminal device can determine one or more cells, the CHO configuration information corresponding to the one or more cells can be complied with, and the one or more cells can be complied with. If each cell meets the CHO execution condition (or CHO trigger condition), the terminal device can determine the target cell in the one or more cells.
  • This application does not limit this. Among them, the related content of CHO configuration information and CHO execution conditions will be described in detail below, and will not be described in detail here.
  • the target cell may be, for example, a cell whose CHO configuration information can be complied with and meets CHO execution conditions, or a cell that satisfies the S criterion and whose CHO configuration information can be complied with. This application does not limit this.
  • the target cell is only for the convenience of communicating with other candidate cells (such as candidate cells whose CHO configuration information cannot be complied with and/or does not meet the CHO execution conditions) or other cells (such as those that meet the S criterion but whose CHO configuration information cannot be complied with).
  • Cells are distinguished and named, where the CHO configuration information cannot be complied with may mean that the CHO execution condition cannot be complied with and/or the parameters corresponding to the candidate cell cannot be complied with, which shall not constitute any limitation to this application. This application does not exclude the possibility of defining other names to express the same or similar meanings in future agreements.
  • Conditional handover In the traditional handover process, the network device indicates the target cell to be handed over to the terminal device through a handover message.
  • communication systems such as LTE or NR
  • the rapid attenuation of channel quality, the rapid movement of terminal equipment, and the occlusion of objects, measurement, and the long duration of handover preparation make the handover message transmission fail, resulting in handover failure.
  • terminal devices often need to perform a re-establishment process to resume communication. This may lead to longer communication interruptions and affect user experience.
  • Conditional handover is proposed based on the above problems, in order to improve the success rate of handover, avoid long-term communication interruption, and improve user experience.
  • network equipment can configure one or more candidate cells for terminal equipment through high-level signaling, such as RRC messages.
  • the network device may indicate the CHO configuration information of one or more candidate cells to the terminal device through one RRC message or multiple RRC messages. It should be understood that the number of RRC messages described herein does not necessarily have a one-to-one correspondence with the number of candidate cells.
  • the network device may indicate the CHO configuration information of one or more candidate cells through one RRC message, and may also indicate the CHO configuration information of multiple candidate cells through multiple RRC messages, which is not limited in this application.
  • the CHO configuration information of the candidate cell may include CHO execution conditions (or CHO trigger conditions) and parameters corresponding to the candidate cell.
  • the CHO execution condition can be understood as a trigger condition for the terminal device to switch.
  • the terminal device determines that a certain candidate cell configured by the network device satisfies the CHO execution condition, it may consider switching to the candidate cell.
  • meeting the CHO execution condition is only one of the conditions for the terminal device to perform handover, and does not mean that a certain candidate cell meets the CHO execution condition, and it will definitely be handed over to the candidate cell.
  • the CHO execution condition can be shared by one or more candidate cells. That is, in a case where there are multiple candidate cells, the multiple candidate cells may correspond to the same CHO execution condition.
  • CHO execution conditions can also be cell-level. In other words, when there are multiple candidate cells, multiple candidate cells may have corresponding CHO execution conditions.
  • the candidate cell mentioned below satisfies the CHO execution condition, or the CHO execution condition is satisfied, which may mean that the signal quality of the candidate cell and/or the signal quality of the source cell meets the CHO execution condition corresponding to the candidate cell, the CHO
  • the execution condition may be a CHO execution condition shared with other candidate cells, or may be a CHO execution condition corresponding only to the candidate cell. This application does not limit this. For the sake of brevity, the description of the same or similar situations will be omitted in the following text.
  • the CHO execution condition may specifically include the type of the CHO execution event (or trigger event) and its corresponding threshold value.
  • the CHO execution event types include, but are not limited to, event A3, event A4, event A5, event B1, event B2, for example.
  • event A3 may specifically be that the cell signal quality of the candidate cell is higher than the cell signal quality of the serving cell by a preset first threshold value.
  • Event A5 may specifically be that the cell signal quality of the candidate cell is higher than the preset second threshold value, and the cell signal quality of the serving cell is lower than the preset third threshold value.
  • the signal quality may include, for example, one or more of the following: reference signal receiving power (RSRP), reference signal receiving quality (RSRQ), signal to interference plus noise ratio (signal to interference) plus noise ratio, SINR).
  • RSRP reference signal receiving power
  • RSRQ reference signal receiving quality
  • SINR signal to interference plus noise ratio
  • the CHO execution condition may include the indication of the above-mentioned CHO execution event type and the indication of the corresponding threshold value.
  • the parameters corresponding to the candidate cell in the CHO configuration information may specifically include parameters for the terminal device to switch to the candidate cell and parameters for the terminal device to communicate in the candidate cell.
  • the parameters corresponding to the candidate cell in the CHO configuration information may include related parameters required for the terminal to switch to/access the candidate cell.
  • the parameters corresponding to the candidate cell may include, but are not limited to, the cell-radio network temporary identifier (C-RNTI) allocated to the terminal device by the candidate cell, and radio resource information for accessing the candidate cell, Such as random access channel (RACH) resource information, candidate cell identification information, candidate cell frequency information, etc.
  • C-RNTI cell-radio network temporary identifier
  • RACH random access channel
  • candidate cell identification information candidate cell frequency information
  • the above-mentioned parameter corresponding to the candidate cell further includes measurement related information, such as a measurement identifier (measID), a measurement frequency point, and the like.
  • the identification information of the candidate cell may include, but is not limited to, the cell global identifier (CGI) of the candidate cell and the physical cell identifier (PCI) of the candidate cell, for example.
  • CGI cell global identifier
  • PCI physical cell identifier
  • the frequency information of the candidate cell may include, but is not limited to, the absolute frequency of a synchronization signal block (synchronization signal block, SSB), and the absolute frequency position of a reference resource block (resource block, RB), for example.
  • the absolute frequency of the SSB may be, for example, the cell "absolute frequency SSB (absolute frequency SSB)".
  • the reference RB may be, for example, a common resource block (CRB) No. 0, which is denoted as CRB 0, for example.
  • the absolute frequency position of the reference RB may include, for example, information elements "absolute frequency point A (absolute frequency point A)", “frequency Band List (frequency Band List)”, and “subcarrier space (SCS) specific carrier list (scs-SpecificCarrierList). )"Wait.
  • each carrier frequency is divided into RBs in the frequency domain according to the unit of 12 consecutive subcarriers, and the RB division is "point A" as the common reference point of.
  • the CRB number can start from 0, for example, it is recorded as CRB 0.
  • Subcarrier 0 in CRB 0 can correspond to point A in the midpoint of the frequency domain.
  • Point A can be configured by the network device for the terminal device.
  • the parameters used for terminal devices to communicate in candidate cells may include, but are not limited to, physical layer configuration parameters, medium access control (MAC) layer configuration parameters, and radio link control (RLC), for example.
  • Layer configuration parameters packet data convergence protocol (PDCP) layer configuration parameters, service data adaptation protocol (service data adaptation protocol, SDAP) layer configuration parameters, radio resource control (radio resource control, RRC) layer configuration Parameters, and bearer configuration information, etc.
  • PDCP packet data convergence protocol
  • SDAP service data adaptation protocol
  • RRC radio resource control
  • the network device can add or modify the CHO configuration information of the candidate cell by using the cell structure of the addition change list (such as ToAddMod list) in the RRC message, and use the release list (such as ToRelease list) or mobile
  • the cell structure of the list (ToRemoveList) deletes the CHO configuration information of the candidate cell.
  • the RRC message may be, for example, a newly defined RRC message, such as a conditional handover RRC reconfiguration (CondRRCReconfiguration) or other named RRC messages.
  • the RRC message may also be a multiplexing of an existing RRC message, such as an RRC reconfiguration message. This application does not limit the specific name of the RRC message used to carry the CHO configuration information.
  • the terminal device may determine the candidate cell to which the CHO configuration information can be complied with based on the CHO configuration of one or more candidate cells configured by the network device. Further, if there are candidate cells to which the CHO configuration information can be complied with, there is a cell that satisfies the CHO execution condition, or if a cell determined by cell selection (for example, a cell that satisfies the S criterion determined by cell selection) is included in the CHO Among the candidate cells whose configuration information can be complied with, the terminal device can determine the target cell.
  • the target cell can refer to one of the candidate cells that can be complied with CHO configuration information and meet the CHO execution conditions, or it can also be a cell that satisfies the S criterion and is included in the candidate cells that can be complied with CHO configuration information.
  • the CHO configuration information can be complied with may mean that the CHO execution condition can be complied with and the parameters corresponding to the candidate cell can be complied with.
  • the terminal device usually selects a cell as the target cell, and then tries to switch to the target cell.
  • the target cell may refer to a cell whose CHO configuration information can be complied with and meet the CHO execution condition; or, it can also be a cell that satisfies the S criterion, and the cell is a candidate cell whose CHO configuration information can be complied with.
  • the terminal device may determine a target cell and try to switch to the target cell.
  • the terminal device can also re-determine a target cell and try to handover to the newly determined target cell.
  • the terminal device may try the handover process for each candidate cell that can be complied with CHO configuration information and meet the CHO execution conditions, or may have tried the handover process for some of the candidate cells, which is not limited in this application.
  • the terminal device may try to switch to the cell.
  • the terminal device can also perform cell selection again to determine another cell that meets the S criterion. If the cell is included in the candidate cell whose CHO configuration information can be complied with, it can be determined as a new target Community. The terminal device can try to switch to the newly determined target cell.
  • the terminal device can perform cell selection multiple times, or perform cell selection only once, which is not limited in this application.
  • the process of attempting to handover to the target cell described above may be, for example, the process of performing random access with the target cell described below, or performing RACH-less handover (RACH-less handover, RACH) with the target cell. -less HO) process.
  • the RRC connection/data transmission can be maintained between the source network device and the terminal device.
  • the terminal device before the terminal device is successfully handed over to a target cell (for example, before the terminal device sends an RRC reconfiguration complete message to the successfully accessed target cell), the terminal device can maintain normal transmission with the source network device.
  • the terminal device before the terminal device releases the RRC connection/data transmission with the source network device (for example, the source network device or the target network device instructs the terminal device to release the RRC connection/data transmission with the source network device; or, the terminal device Release the RRC connection/data transmission with the source network device based on the timer mechanism, for example, the source network device or the target network device sends timer 1 related information (such as the effective duration of timer 1) to the terminal device, or protocol agreement After receiving the RRC message containing the CHO configuration information, the terminal device starts timer 1 and the protocol stipulates the effective duration of timer 1. When timer 1 expires, the terminal device releases the RRC connection with the source network device/data transmission release/stops ), the terminal device can maintain normal transmission with the source network device.
  • the source network device or the target network device instructs the terminal device to release the RRC connection/data transmission with the source network device; or, the terminal device Release the RRC connection/data transmission with the source network device based on the timer mechanism, for example, the source
  • the source network device After the source network device sends an RRC message containing the CHO configuration information of one or more candidate cells to the terminal device for the first time, it can subsequently send an RRC message to the terminal device to respond to the one or more previously received RRC messages.
  • the CHO configuration information of the candidate cell is updated; or, after the source network device sends an RRC message containing the CHO configuration information of one or more candidate cells to the terminal device for the first time, it can subsequently send a handover message to the terminal device. Notify the terminal device to perform traditional handover; or, after the source network device first sends an RRC message containing the CHO configuration information of one or more candidate cells to the terminal device, it can subsequently send the terminal device RRC for other purposes. Message, this embodiment does not limit this.
  • Random access is the process from when the terminal device starts to send a random access preamble to the network device trying to access, until the terminal device and the network device establish a connection.
  • the random access procedure may occur during handover, RRC re-establishment and other procedures, for example.
  • Random access can be divided into contention based random access (CBRA) and non-competitive random access (contention free random access, CFRA).
  • the resources used by CFRA are CFRA resources, and CFRA resources are dedicated RACH resources.
  • the CFRA resources may specifically include preamble index and time-frequency resources.
  • CFRA resources may be CFRA resources associated with a certain beam of a cell. If the network device configures the CFRA resource for the terminal device, the terminal device can use the CFRA resource to initiate a CFRA process. If CFRA fails or CFRA resources are not configured, the terminal device can initiate CBRA.
  • CBRA resources can be understood as public resources, and terminal devices can use CBRA resources to initiate a CBRA process in a competitive manner.
  • the random access procedure mentioned in the following embodiments can mean that the terminal device performs the CFRA procedure, it can also mean that the terminal device performs the CBRA procedure, or it can also mean that the terminal device performs the CBRA procedure after performing CFRA. .
  • the contention-based random access procedure may specifically include steps one to four described below.
  • Step 1 The terminal device sends a random access preamble to the network device through a physical random access channel (PRACH).
  • PRACH physical random access channel
  • Step 2 The network device sends a random access response (RAR) to the terminal device.
  • the random access response may include timing advance (TA) information, uplink grant (UL grant) information, and temporary C-RNTI (temporary cell-radio network temporary identifier, TC-RNTI), etc.
  • TA timing advance
  • UL grant uplink grant
  • C-RNTI temporary cell-radio network temporary identifier
  • Step 3 Based on the received random access response, the terminal device sends a message or data on the UL grant resource allocated by the network device, for example, sending an RRC establishment request message, which may include the identification information of the terminal device.
  • the identification information may be the aforementioned TC-RNTI, for example.
  • Step 4 After the network device receives the message or data sent by the terminal device on the allocated UL grant resource, if there is no conflict (or no competition), the network device sends a contention resolution message to the terminal device, for example, the network device to the terminal device Send RRC setup message. After that, the terminal device can communicate with the network device.
  • the CFRA process can specifically include steps (1) to (2) described below.
  • Step (1) The terminal device sends a random access preamble to the network device through PRACH.
  • the network device allocates/transmits the random access preamble index to the terminal device in advance.
  • the random access preamble index is dedicated.
  • the terminal device sends the random access preamble to the network device.
  • Step (2) The network device sends a random access response to the terminal device.
  • the random access response may include TA information, UL grant information, and so on.
  • UL grant information is used to indicate UL grant.
  • the UL grant may specifically include at least one of the following: time-frequency resources, modulation coding scheme (MCS), new data indicator (NDI), and the time at which uplink transmission is initiated (such as a subframe or slot (slot) )) and the interval of uplink scheduling.
  • MCS modulation coding scheme
  • NDI new data indicator
  • the time-frequency resource included in the UL grant may specifically refer to the time-frequency position of the uplink resource scheduled through the UL grant.
  • the uplink resources scheduled by the UL grant may be PUSCH resources, for example.
  • RACH-less handover In order to reduce the delay caused by the random access procedure, the terminal device can skip (or say not to execute) the random access procedure with the target cell. After determining the target cell, the terminal device sends an RRC reconfiguration complete message to the network device to which the target cell belongs based on the RACH-less handover related information (such as TA information, UL grant information, etc.) configured by the network device.
  • the foregoing RRC message used to indicate the CHO configuration information of one or more candidate cells may include indication information, and the indication information may be used to instruct the terminal device to perform RACH-less handover.
  • RACH-less handover may also fail. For example, if there is no beam with a signal quality higher than a preset threshold (the RRC message used to indicate the CHO configuration information of one or more candidate cells may include the preset threshold) in the beams associated with the UL grant configured by the target cell, Or, if there is no beam associated with the UL grant and the signal quality is higher than the preset threshold in the target cell, the RACH-less handover initiated by the terminal device to the target cell fails.
  • a preset threshold the RRC message used to indicate the CHO configuration information of one or more candidate cells may include the preset threshold
  • RRC re-establishment When a terminal device fails to switch, RLF, or RRC reconfiguration fails, the terminal device can initiate an RRC re-establishment process.
  • the RRC re-establishment procedure initiated by the terminal device may also be referred to as the terminal device initiated re-establishment procedure.
  • the RRC re-establishment process may include the following steps, for example:
  • Step 1 The terminal device sends an RRC re-establishment request message to the re-established cell (or the network device to which the cell belongs);
  • Step 2 Re-establish the cell to allow the terminal device's request, then send an RRC re-establishment message to the terminal device;
  • Step 3 The terminal device sends an RRC re-establishment complete message to the re-established cell.
  • the re-established cell may be a cell determined by the terminal device through cell search or detection.
  • the re-established cell may be a cell that meets a predetermined criterion, such as the cell selection S criterion in the NR protocol TS38.304-f30.
  • a predetermined criterion such as the cell selection S criterion in the NR protocol TS38.304-f30.
  • the terminal device can determine the cell in which it can camp according to the S criterion.
  • the S criterion may be, for example, that the received power in the cell search is greater than 0 dB, and the received signal quality in the cell search is greater than 0 dB.
  • the received power in the cell search can be determined according to the RSRP value of the searched/measured cell, the minimum reception level of the cell, and the minimum reception level offset of the cell.
  • the received signal quality in the cell search can be determined according to the searched/measured RSRQ value, the minimum received signal quality, and the minimum received signal received quality offset value.
  • the specific content of the S criterion please refer to the NR agreement. For the sake of brevity, it will not be detailed here.
  • the configuration information that the terminal device complies with may include one or more of the following: when the terminal device receives the configuration information, it can parse the configuration information, understand the configuration information, and be able to use the configuration information.
  • the terminal device cannot comply with the CHO configuration information of a certain candidate cell, it can be understood that the terminal device cannot comply with the CHO execution condition corresponding to the candidate cell and/or the parameters corresponding to the candidate cell, or the corresponding parameter of the candidate cell.
  • the CHO execution conditions and/or the corresponding parameters of the candidate cell are invalid for the terminal device.
  • the traditional handover is taken as an example for description.
  • the terminal device may first evaluate whether it can comply with the configuration information contained in the RRC message.
  • the RRC message contains configuration information for handover.
  • it can include handover-related parameters and communication-related parameters, specifically, such as information about the target cell and the terminal device accessing the target cell. Required related configuration parameters, etc.
  • the terminal device needs to determine (or evaluate or judge) whether it can comply with the configuration information carried in the RRC message. If the terminal device can comply with the configuration information contained in the RRC message, it can perform subsequent handover procedures.
  • the terminal device can perform the subsequent handover procedure according to the parameters contained in the RRC message (such as physical layer configuration parameters corresponding to the target cell, MAC layer configuration parameters). , RLC layer configuration parameters, PDCP layer configuration parameters, SDAP layer configuration parameters, RRC layer configuration parameters, and bearer configuration information, etc., PCI and frequency information of the target cell, RACH resource information, etc.), random access procedures with the target cell, And follow-up communication. If the terminal device cannot comply with some or all of the configuration parameters included in the RRC message, the terminal device can initiate a re-establishment procedure.
  • the network device can provide the terminal device with the CHO configuration information of one or more candidate cells through the RRC message, and the terminal device determines the target cell to be handed over to. Before determining the target cell, the terminal device also needs to determine (or evaluate or judge) whether it can comply with the information carried in the RRC message (such as the CHO configuration information of the candidate cell).
  • the terminal device determining whether it can comply with the CHO configuration information of the candidate cell may include the terminal device determining whether it can comply with the CHO execution condition, and the terminal device determining whether it can comply with the parameter corresponding to the candidate cell.
  • the terminal device may not be able to comply with some or all of the information carried in the RRC message.
  • the terminal device may not be able to comply with the CHO configuration information of all configured candidate cells, or the terminal device may not be able to comply with the configuration CHO configuration information corresponding to some of the candidate cells. If the terminal device initiates a re-establishment just because the CHO configuration information of some candidate cells cannot be complied with, this may cause a long communication interruption time and a poor user experience.
  • the present application provides a method in order to provide a reasonable operation process for the terminal device, so as to reduce the communication interruption time as much as possible, thereby improving the user experience.
  • "used to indicate” may include used for direct indication and used for indirect indication, and may also include explicit indication and implicit indication.
  • the information indicated by a certain piece of information is called information to be indicated.
  • the information to be indicated can be directly indicated, such as the information to be indicated or the information to be indicated.
  • the information to be indicated can also be indicated indirectly by indicating other information, where there is an association relationship between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while other parts of the information to be indicated are known or agreed in advance. For example, it is also possible to use a pre-arranged (for example, protocol stipulation) whether there is a certain cell to indicate the information to be indicated, so as to reduce the indication overhead to a certain extent.
  • a pre-arranged for example, protocol stipulation
  • the first, second, and various numerical numbers are only for easy distinction for description, and are not used to limit the scope of the embodiments of the present application. For example, distinguish different indication information, different time intervals, and so on.
  • “pre-defined” or “pre-configured” can be realized by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in the equipment (for example, including terminal equipment and network equipment).
  • the specific implementation is not limited.
  • "saving” may refer to storing in one or more memories.
  • the one or more memories may be provided separately, or integrated in an encoder or decoder, a processor, or a communication device.
  • the one or more memories may also be partly provided separately, and partly integrated in a decoder, a processor, or a communication device.
  • the type of the memory can be any form of storage medium, which is not limited in this application.
  • the “protocols” involved in the embodiments of the present application may refer to standard protocols in the communication field, for example, may include LTE protocol, NR protocol, and related protocols applied to future communication systems, which are not limited in this application.
  • At least one refers to one or more, and “multiple” refers to two or more.
  • And/or describes the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated objects before and after are in an “or” relationship.
  • "The following at least one item (a)” or similar expressions refers to any combination of these items, including any combination of a single item (a) or a plurality of items (a).
  • At least one of a, b, and c can mean: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a , B, and c.
  • a, b, and c can be single or multiple.
  • the message names involved are all message names in the NR. However, it is understandable that these message names are only examples for ease of understanding, and should not constitute any limitation to this application. This application does not exclude the possibility of defining other message names in future agreements to replace the message names listed in this application to achieve the same or similar functions.
  • the message name in the NR is taken as an example to illustrate the embodiments of the present application, which should not constitute any limitation to the applicable scenarios of the method provided in the present application. For example, the method provided in this application can also be applied to the LTE system.
  • the terminal device shown in the following embodiments can be replaced with a component (such as a chip or a circuit) configured in the terminal device.
  • the network devices shown in the following embodiments can also be replaced with components (such as chips or circuits) configured in the network devices.
  • the embodiments shown below do not specifically limit the specific structure of the execution body of the method provided in the embodiments of the application, as long as the program can be run and recorded with the code of the method provided in the embodiments of the application to provide the method according to the embodiments of the application.
  • the execution subject of the method provided in the embodiments of the present application may be a terminal device or a network device, or a functional module in the terminal device or the network device that can call and execute the program.
  • FIG. 2 is a schematic flowchart of a communication method 200 according to an embodiment of the present application, shown from the perspective of device interaction. As shown in FIG. 2, the method 200 may include step 210 to step 290. The steps in the method 200 are described in detail below.
  • FIG. 2 is a schematic flowchart of a communication method 200 according to an embodiment of the present application, shown from the perspective of device interaction. As shown in FIG. 2, the method 200 may include step 210 to step 290. The steps in the method 200 are described in detail below.
  • the terminal device receives a first RRC message, the first RRC message including CHO configuration information of one or more candidate cells.
  • the first RRC message may be sent by the source network device, for example.
  • the RRC message used to configure the CHO configuration information of one or more candidate cells is recorded as the first RRC message.
  • the first RRC message may be one or multiple, which is not limited in this application.
  • the CHO configuration information of the candidate cell may include CHO execution conditions. As mentioned earlier, some candidate cells may all correspond to the same CHO execution condition, or each candidate cell may have its own corresponding CHO execution condition. Therefore, the first RRC message may carry only one CHO execution condition or multiple CHO execution conditions, which is not limited in this application.
  • the terminal device receives a first RRC message that includes related information of multiple candidate cells and a CHO execution condition
  • the CHO execution condition may be multiple candidates configured in the first RRC message.
  • the terminal device receives a first RRC message that includes related information of multiple candidate cells and multiple CHO execution conditions, then the multiple CHO execution conditions may be related to the first RRC message.
  • the configured multiple candidate cells correspond to multiple CHO execution conditions, and the multiple candidate cells may correspond to multiple CHO execution conditions one-to-one, or some candidate cells of the multiple candidate cells may correspond to the same CHO execution condition. Another part of the candidate cells can correspond to another CHO execution condition. This application does not limit the correspondence between CHO execution conditions and candidate cells.
  • the terminal device receives multiple first RRC messages, and each first RRC message includes CHO configuration information of a candidate cell, that is, it may include related information of a candidate cell and corresponding CHO execution conditions.
  • This application does not limit the correspondence between the number of RRC messages and the number of candidate cells. This application also does not limit the correspondence between CHO execution conditions and candidate cells.
  • the terminal device may determine the CHO configuration information of one or more candidate cells according to the multiple first RRC messages. For example, the terminal device receives two first RRC messages, RRC message #1 and RRC message #2.
  • the RRC message #1 includes the CHO configuration information of 2 candidate cells, such as the CHO configuration information of cell #1 and the CHO configuration information of cell #2; the RRC message #2 includes 1 candidate cell, such as the CHO configuration information of cell #3. CHO configuration information.
  • the terminal device may determine one or more candidate cells according to the two first RRC messages, including cell #1, cell #2, and cell #3, and the terminal device may further determine the CHO configuration information and cell #1 of cell #1.
  • this application does not limit the receiving time of the multiple first RRC messages.
  • the multiple first RRC messages may be received at the same time, or may be received at different times.
  • step 220 the terminal device determines that it cannot comply with the CHO configuration information of some candidate cells among one or more candidate cells.
  • the terminal device may determine whether it can comply with the CHO configuration information of the candidate cell according to the first RRC message received in step 210. In the case of multiple candidate cells, the terminal device can determine whether it can comply with the CHO configuration information of each candidate cell. Exemplarily, the terminal device may determine whether the CHO configuration information of each candidate cell can be complied with sequentially or randomly according to the configuration sequence of multiple candidate cells, which is not limited in this embodiment.
  • the terminal device can determine that the CHO configuration information of some of the multiple candidate cells cannot be complied with . Or, it is understood that if the CHO configuration information of at least one candidate cell among the multiple candidate cells configured in the first RRC message cannot be complied with, the terminal device determines that the CHO configuration information of some of the multiple candidate cells cannot be complied with. Configuration information.
  • the terminal device determines that the CHO configuration information of some candidate cells among the one or more candidate cells cannot be complied with, that is, the terminal device determines the CHO configuration information of the remaining candidate cells among the one or more candidate cells. Can be obeyed.
  • the terminal device determines that the CHO configuration information of some candidate cells (such as candidate cell #1) of one or more candidate cells cannot be complied with, then the terminal device ignores the partial candidate cells (such as ignoring the CHO configuration of the candidate cell #1) information).
  • the terminal device notifies the source network device to release/delete the part of the candidate cells (for example, the terminal device sends a message a to the source network device, and the message a may contain the identification information of the candidate cell #1.
  • the representative information of the candidate cell #1 For example, it may include one or more of the following: the PCI of the candidate cell #1, the frequency information of the candidate cell #1, the CGI of the candidate cell #1, and the measurement identifier corresponding to the candidate cell #1.
  • the device After receiving the message a, the device releases or deletes the CHO configuration information of the candidate cell #1).
  • the source network device notifies the network device to which the candidate cell #1 belongs to release/delete the corresponding candidate cell.
  • the source network device sends a message b to the network device to which the candidate cell #1 belongs, and the message b contains the identification information of the candidate cell to be deleted/released.
  • the candidate cell to be deleted/released may include, but is not limited to, candidate cell #1.
  • the network device to which candidate cell #1 belongs deletes/releases the CHO configuration information of the candidate cell to be deleted/released. .
  • the terminal device When the terminal device determines that the CHO configuration information of some candidate cells can be complied with, it can save the CHO configuration information of the candidate cells, and continue to execute the subsequent process according to the saved CHO configuration information of the candidate cells.
  • step 230 the terminal device determines whether there is a cell that satisfies the CHO execution condition among the candidate cells to which the CHO configuration information can be complied with.
  • the terminal device when the terminal device determines that the CHO configuration information of some candidate cells cannot be complied with, it may not initiate a re-establishment procedure, but instead determines whether there is a satisfying CHO configuration information from the candidate cells whose CHO configuration information can be complied with.
  • CHO execution condition of the cell For example, three candidate cells are configured in the first RRC message, cell #1, cell #2, and cell #3, but the terminal device determines that it cannot comply with the CHO configuration information of cell #2. In cell #3, it is determined whether there is a cell that satisfies the CHO execution condition.
  • the terminal device can perform different operations.
  • the terminal device may perform step 240 to try to switch to the cell that meets the CHO execution condition, or in other words, try to switch to the cell where the CHO execution condition can be met/satisfied. It can be understood that the cell that meets the CHO execution condition described here is the target cell.
  • the terminal device may perform random access with the target cell. If the random access is successful, the terminal device can send an RRC reconfiguration complete message to the target cell; or, if the first RRC message contains information about the RACH-less handover corresponding to the target cell, the terminal device can also skip random In the access process, an RRC reconfiguration complete message is sent to the target cell according to the relevant information of the RACH-less handover.
  • the terminal device can determine the target cell from the candidate cells.
  • the target cell may be one or multiple, which may depend on the execution conditions of CHO and the cell signal quality of each candidate cell. However, it can be understood that the time when the multiple target cells are determined may be different.
  • the terminal device can continue to find a new target cell to try to handover. This is done until it is successfully connected to a certain target cell. Therefore, the terminal device may successively try the handover procedure for one or more target cells before successfully accessing.
  • the terminal device determines, according to the first RRC message, that the candidate cell satisfying the CHO execution condition among the candidate cells whose CHO configuration information can be complied with is cell #1, and cell #1 is the target cell.
  • the terminal device can try to switch to cell #1.
  • the terminal device performs cell selection to determine a cell that satisfies the S criterion, and may further execute step 260 to determine whether the cell that satisfies the S criterion is included in a candidate cell whose CHO configuration information can be complied with.
  • step 270 may be performed, and the terminal device attempts to switch to the cell that satisfies the S criterion. If the terminal device successfully switches to the cell that meets the S criterion, it is considered that the current round of the CHO process is successful.
  • step 280 may be performed, and the terminal device initiates a re-establishment process .
  • the terminal device may perform cell selection again, determine another cell that satisfies the S criterion, and determine whether the other cell that satisfies the S criterion is included in the CHO Among the candidate cells whose configuration information can be complied with, if so, the terminal device can try to switch to the cell again. Repeat this until it is successfully connected to a cell, and then perform step 290 to communicate with the cell that has been successfully handed over; or until the timer maintained by the terminal equipment (for example, recorded as the first timer) expires, perform step 280, and the terminal The device initiates the re-establishment process.
  • the first timer may be started when the terminal device receives the first RRC message in step 210, or it may be started when the terminal device starts to perform step 240 after determining the target cell.
  • This application does not limit this.
  • the duration of the first timer may be predefined, such as a protocol, or the first RRC message may include related information of the first timer, such as the effective duration of the first timer. This application does not limit this.
  • the terminal device determines, according to the first RRC message, that the candidate cell that meets the CHO execution condition among the candidate cells whose CHO configuration information can be complied with is cell #1, and cell #1 is the target cell.
  • the terminal device can try to switch to cell #1. If the terminal device is successfully handed over to cell #1, it is considered that the current round of CHO process is successful; if the terminal device fails to hand over to cell #1 successfully, the terminal device will then perform assessment and evaluation according to the first RRC message and the channel status at this time, etc. Judgment, try to re-determine the cell that meets the CHO execution condition from the candidate cells whose CHO configuration information can be complied with as the new target cell.
  • step 280 may be executed, and the terminal device initiates a re-establishment procedure.
  • the terminal device may perform handover in all cells whose CHO configuration information can be complied with and meet the CHO execution conditions in the candidate cells configured in the first RRC message, but after the handover fails, perform step 250 to perform cell selection , Determine a cell that satisfies the S criterion, and perform step 260 to determine whether the cell that satisfies the S criterion is included in the candidate cells for which the CHO configuration information can be complied with. If yes, step 270 is executed, and the terminal device attempts to switch to the cell that meets the S criterion. If the handover is successful, the current round of CHO process is successful.
  • step 280 may be performed, and the terminal device initiates a re-establishment process.
  • step 270 the terminal device can also perform step 250 to step 270 again until it successfully accesses In a certain cell, this round of the CHO process is successful; or, if the first timer expires, step 280 may be executed, and the terminal device initiates a re-establishment process.
  • the terminal device determines in step 230 that there is no cell that satisfies the CHO execution condition among the candidate cells whose CHO configuration information can be satisfied, or in other words, if there is no such cell among the candidate cells whose CHO configuration information can be satisfied, its corresponding If the CHO execution condition can be met/satisfied, the terminal device can execute the above-mentioned step 250 to determine whether the cell that meets the S criterion is included in the candidate cell to which the CHO configuration information can be followed.
  • step 270 may be performed, and the terminal device attempts to switch to the cell that satisfies the S criterion. If the terminal device successfully switches to the cell that meets the S criterion, it is considered that the current round of the CHO process is successful.
  • step 280 may be performed, and the terminal device initiates a re-establishment process .
  • the terminal device may directly execute step 280 to initiate a re-establishment process when it is determined that there is no cell that meets the CHO execution condition among the candidate cells that can be satisfied with the CHO configuration information.
  • the specific process of the terminal device initiating the re-establishment process has been described in detail above, and for brevity, it is not repeated here.
  • step 290 can be executed to communicate with the cell where the handover is successful.
  • FIG. 2 shows a variety of different implementations of the terminal device.
  • different branches in the same step are distinguished by solid lines and dashed lines.
  • FIG. 2 does not show all the above solutions.
  • the process shown in Figure 2 should not constitute any limitation to this application.
  • the terminal device may not initiate a re-establishment procedure, but preferentially try handover when it is determined that it cannot comply with the CHO configuration information of some candidate cells.
  • the terminal device can try to find a cell that meets the CHO execution conditions among the candidate cells where the CHO configuration information can be complied with, and try to switch to that cell; or it can also determine a terminal device that meets the S criterion through cell selection. Successfully handover to a cell that satisfies the CHO execution condition, or if a cell that satisfies the CHO execution condition cannot be found among the candidate cells whose CHO configuration information can be followed, a cell suitable for handover can still be selected based on the S criterion to try handover.
  • the terminal device searches for cells suitable for handover based on different dimensions, and is not limited to cells that meet the execution conditions of CHO. This is beneficial for the terminal equipment to find a suitable cell more likely to try handover, and avoid the delay and complexity caused by the re-establishment procedure to a greater extent. Avoiding the impact of long-term communication interruption on user experience is conducive to improving system reliability, ensuring system performance, and improving user experience.
  • the method further includes: if the terminal device cannot comply with the CHO configuration information of all candidate cells in the first RRC message, then the terminal device remains in the source cell.
  • the terminal device cannot comply with the CHO configuration information of all candidate cells in the first RRC message. It can be understood that the CHO execution conditions and/or parameters corresponding to all candidate cells in the first RRC message cannot be complied with, or, in the first RRC message The CHO execution conditions and/or parameters corresponding to all candidate cells are invalid.
  • the terminal device can remain in the source cell, that is, maintain the RRC connection/data transmission with the source cell.
  • the terminal device may also discard the CHO configuration information of one or more candidate cells in the first RRC message.
  • the method further includes: the terminal device sends an RRC reconfiguration failure message to the network device to which the source cell belongs (hereinafter referred to as the source network device for short).
  • the source network device may send a message to the network device to which each candidate cell belongs to which the CHO configuration information cannot be complied with, so as to notify the network device to which each candidate cell belongs to modify the CHO configuration information.
  • the terminal device may also receive other RRC messages while maintaining the RRC connection with the source network device.
  • the method 200 further includes: the terminal device receives the second RRC message.
  • the second RRC message is sent by the source network device, for example.
  • the source network device may first send the first RRC message to the terminal device. Before the terminal device completes the CHO process according to the first RRC message, for example, before the terminal device determines the target cell that satisfies the CHO trigger condition according to the first RRC message, or before the terminal device successfully accesses the determined target cell, or Before the terminal device sends the RRC reconfiguration complete message to the determined target cell, the source network device may send a second RRC message to the terminal device.
  • the second RRC message may be used to reconfigure (also may be simply referred to as reconfiguration) candidate cells.
  • the second RRC message can be used to modify or release the candidate cell configured in the first RRC message, and/or to add a new cell (for example, the new cell is not included in the candidate cell configured in the first RRC message ) As a candidate cell.
  • the second RRC message may also be used to instruct the terminal device to perform traditional handover.
  • the second RRC message may also be used for other purposes, which is not limited in the embodiment of the present application.
  • the terminal device can learn how to use the first RRC message and/or a specific identifier optionally included in the first RRC message and/or the second RRC message. The second RRC message undergoes subsequent processing.
  • the specific identifier may be, for example, a certain predefined information element, such as "candidate cell reconfiguration". For example, if the second RRC message received by the terminal device carries the "candidate cell reconfiguration" identifier, it can be considered that the second RRC message can be used to reconfigure the CHO configuration information of the candidate cell that has been configured in the first RRC message. Configuration.
  • the specific process of reconfiguring candidate cells will be described in detail later, and will not be described in detail here.
  • the terminal device may determine the role of the second RRC message according to the specific information content respectively contained in the first RRC message and the second RRC message. For example, judging whether the second RRC message is used to reconfigure the CHO configuration information of the candidate cell that has been configured in the first RRC message, or judging whether the second RRC message is a traditional handover message, etc., in this embodiment Not limited.
  • the RRC message used to reconfigure the candidate cell is recorded as the third RRC message. It can be understood that the third RRC message is a type of the second RRC message.
  • FIG. 3 is a schematic flowchart of a communication method 300 provided by another embodiment of the present application. As shown in FIG. 3, the method 300 may include step 310 to step 370. The steps in the method 300 are described in detail below.
  • the terminal device receives a first RRC message, the first RRC message including CHO configuration information of one or more candidate cells.
  • the first RRC message may be sent by the source network device, for example.
  • step 310 please refer to the detailed description of step 210 in the method 200 above. For brevity, it will not be repeated here.
  • the terminal device receives a third RRC message, which is used to reconfigure candidate cells.
  • the third RRC message may also be sent by the source network device, for example.
  • the third RRC message may also include CHO configuration information of one or more candidate cells, so as to reconfigure the candidate cells.
  • the third RRC message can be used to modify or release the candidate cell configured in the first RRC message, and/or to add a new cell (for example, the new cell is not included in the candidate cell configured in the first RRC message ) As a candidate cell.
  • the third RRC message may be one or multiple, which is not limited in this application.
  • the third RRC message may be, for example, one or more newly defined messages, or may reuse existing messages (such as reusing RRC reconfiguration messages), which is not limited in this application.
  • this application does not limit the correspondence between the number of third RRC messages and the number of candidate cells configured in the third RRC message or the first RRC message.
  • This application also does not limit the correspondence between CHO execution conditions and candidate cells.
  • the terminal device determines whether the received RRC message is the third RRC message has been described in detail above. For brevity, it will not be repeated here. If the terminal device receives the third RRC message and the integrity protection check of the third RRC message succeeds, the terminal device can parse out the CHO configuration information of one or more candidate cells included in the third RRC message . As mentioned above, the third RRC message is used to reconfigure candidate cells. Therefore, one or more candidate cells in the third RRC message may be the same or different from one or more candidate cells in the first RRC message. Make a limit.
  • the reconfiguration of the candidate cell may include one or more of the following: adding the CHO configuration information corresponding to the new candidate cell (for example, the new candidate cell is not included in the candidate cell configured in the first RRC message), Modify the CHO configuration information of some or all of the candidate cells that have been configured, and delete the CHO configuration information of some or all of the candidate cells that have been configured.
  • the above-mentioned reconfiguration of the candidate cell may include one or more of the modification and deletion of the CHO configuration information of the candidate cell that has been configured, and the addition of the CHO configuration information corresponding to the new candidate cell.
  • reconfiguring the candidate cell may also be referred to as updating the candidate cell.
  • the third RRC message can be used to update the CHO configuration information of one or more candidate lower regions in the first RRC message.
  • the update may include one or more of the above-mentioned modification, deletion, and addition.
  • the third RRC message may include delta configuration information or full configuration information corresponding to the candidate cell.
  • the delta configuration information can be understood as the changed part of the configuration information after this update compared to the configuration information after the most recent last update (that is, the latest configuration information before this update).
  • the full configuration information can be understood as the configuration information after this update.
  • the reconfigured candidate cell and its CHO configuration information can be determined jointly according to the first RRC message and the third RRC message. For example, before reconfiguring the candidate cell, the CHO configuration information corresponding to each candidate cell in the first candidate cell set is determined according to the first RRC message, and after the candidate cell is reconfigured, according to the first RRC message and the third RRC message, or According to the third RRC message, the CHO configuration information corresponding to each candidate cell in the second candidate cell set is determined. The CHO configuration information corresponding to each candidate cell in the second candidate cell set is relative to each candidate cell in the first candidate cell set.
  • the changed part of the CHO configuration information corresponding to the candidate cell may include at least one of the following situations: the cells included in the first candidate cell set and the second candidate cell set are the same, but the corresponding configuration information of the same cell is different, for example, the first RRC message
  • the configuration information contained in includes the bearer configuration information 1 of cell 1, and the configuration information contained in the third RRC message includes the bearer configuration information 2 of cell 1; or, the first candidate cell set and the second candidate cell set include different cells,
  • the configuration information contained in the first RRC message includes the bearer configuration information 1 of cell 1
  • the configuration information contained in the third RRC message includes the bearer configuration information 2 of cell 2; or, the first candidate cell set and the second candidate cell
  • the configuration information corresponding to the same cells included in the set is different, and the second candidate cell includes candidate cells that are not included in the first candidate cell.
  • the configuration information included in the first RRC message includes the bearer configuration information 1 of cell 1, and the third The configuration information contained in the RRC message includes the bearer configuration information 2 of cell 1 and the bearer configuration information 3 corresponding to cell 2; or, the third RRC message includes configuration information corresponding to some cells in the first RRC message, for example, the first The configuration information contained in the RRC message includes the bearer configuration information 1 of cell 1, and the bearer configuration information 1 of cell 2, and the configuration information contained in the third RRC message includes measurement configuration information 1 of cell 1. .
  • the first RRC message includes the CHO configuration information of cell #1, cell #2, and cell #3
  • the third RRC message includes the CHO configuration information of cell #2, cell #4, and cell #5
  • the CHO configuration information of cell #1, cell #2, cell #3, cell #4, and cell #5 can be obtained.
  • the CHO configuration information of cell #2 may be determined based on the CHO configuration information of cell #2 in the first RRC message and the CHO configuration information of cell #2 in the second RRC message.
  • the terminal device can add a new candidate cell, including adding a CHO execution condition corresponding to the new candidate cell and/or adding a new candidate cell. Parameters corresponding to the cell. If the third RRC message is used to modify the CHO configuration information of one or more candidate cells that have already been configured, the terminal device can modify the CHO configuration information according to the first RRC message and the third RRC message, or according to the third RRC message.
  • the configured CHO configuration information of one or more candidate cells may be modified, for example, the CHO execution conditions and/or corresponding parameters corresponding to the candidate cell may be modified.
  • the terminal device may delete the CHO execution conditions and corresponding parameters of the one or more candidate cells that have been configured. That is, after the candidate cell is reconfigured, the terminal device will no longer determine whether the CHO execution condition is satisfied for the deleted candidate cell, and will not switch to the candidate cell. It should be noted that when the deleted candidate cell and the non-deleted candidate cell share the same CHO execution condition, the terminal device may retain the CHO execution condition.
  • the reconfigured candidate cell and its CHO configuration information can be determined according to the third RRC message.
  • the obtained CHO configuration information of the candidate cell may include the configuration in the third RRC message CHO configuration information of one or more candidate cells, but does not necessarily include the CHO configuration information of one or more candidate cells configured in the first RRC message.
  • performing full configuration is equivalent to using the CHO configuration information of one or more candidate cells contained in the third RRC message to cover/replace the CHO configuration information of one or more candidate cells originally configured in the first RRC message.
  • the CHO configuration information obtained by the terminal device no longer contains the CHO configuration information of the candidate cell. If the CHO configuration information of a certain candidate cell contained in the first RRC message is inconsistent with the CHO configuration information of the candidate cell contained in the third RRC message, after performing the full configuration, the CHO configuration information obtained by the terminal device contains The CHO configuration information of the candidate cell included in the third RRC message does not include the CHO configuration information of the candidate cell included in the first RRC message.
  • the first RRC message includes the CHO configuration information of cell #1, cell #2, and cell #3
  • the third RRC message includes the CHO configuration information of cell #2, cell #4, and cell #5
  • the obtained configuration information of the candidate cells is the CHO configuration information of the cell #2, the cell #4, and the cell #5.
  • the CHO configuration information of the cell #2 may be determined based on the CHO configuration information of the cell #2 included in the third RRC message, rather than the CHO configuration information of the cell #2 included in the first RRC message.
  • step 330 the terminal device determines that it cannot comply with the CHO configuration information of some candidate cells.
  • partial candidate cells may refer to partial candidate cells among the candidate cells obtained after the terminal device performs candidate cell reconfiguration.
  • the operations performed by the terminal device may also be different based on different ways of reconfiguration.
  • the terminal device may determine one or more candidate cells obtained after reconfiguration according to the third RRC message, or according to the first RRC message and the third RRC message, and may further determine one or more candidate cells obtained after the reconfiguration. Whether there are cells in which the CHO configuration information of some candidate cells cannot be complied with.
  • the time when the terminal device receives the third RRC message is not fixed. As mentioned above, the terminal device receives the third RRC message at different times, and the operations performed may be different.
  • the terminal device may further determine one of the third RRC messages Or whether there is a candidate cell whose CHO configuration information cannot be complied with among multiple candidate cells.
  • the candidate cell in the first RRC message and the candidate cell in the third RRC message are not necessarily the same.
  • the CHO configuration information of the candidate cell in the third RRC message can be regarded as the CHO configuration information of the added candidate cell.
  • the terminal device can determine whether it can comply with the CHO configuration information of each candidate cell included in the third RRC message.
  • the third RRC message is used to add a new candidate cell.
  • the first RRC message includes CHO configuration information of cell #1 and cell #2
  • the third RRC message includes CHO configuration information of cell #3. It is assumed that the terminal device has determined that it cannot comply with the CHO configuration information of cell #1 before receiving the third RRC message. After receiving the third RRC message, the terminal device can determine whether it can comply with the CHO configuration information of cell #3.
  • the third RRC message modifies the CHO configuration information of the repeated candidate cell.
  • the terminal device can determine whether it can comply with the updated CHO configuration information corresponding to the repeated candidate cell.
  • the third RRC message may also include CHO configuration information of other candidate cells other than the candidate cell configured in the first RRC message.
  • the CHO configuration information of the other candidate cells may be considered to be passed through the third RRC message.
  • CHO configuration information corresponding to the added candidate cell may further determine whether it can comply with the CHO configuration information of the candidate cell that it wants to add through the third RRC message.
  • the first RRC message includes the CHO configuration information of cell #1 and cell #2
  • the third RRC message includes the CHO configuration information of cell #1 and cell #3, that is, the third RRC message has configured cell # 1 Perform reconfiguration and add a new candidate cell #3.
  • the terminal device determines that it cannot comply with the CHO configuration information of cell #1.
  • the terminal device can determine whether it can comply with the CHO configuration information of cell #3 included in the third RRC message. In this case, the terminal device does not need to determine whether it can comply with the CHO configuration information of cell #1 included in the third RRC message.
  • the terminal device can perform subsequent steps, such as step 230 to determine whether the CHO configuration information can be complied with among the candidate cells There is a cell that satisfies the CHO execution condition (ie, the target cell), or step 240 attempts to handover to the target cell.
  • the terminal device may stop/interrupt the above operation, and determine the CHO of the candidate cell after reconfiguration according to the third RRC message, or according to the first RRC message and the third RRC message. Whether the configuration information can be complied with.
  • the second RRC message contains the configuration information corresponding to the candidate cell that needs to be added, or the third RRC message contains the candidate cell configured through the first RRC message (that is, the candidate cell is also included in the first RRC message).
  • the CHO configuration information corresponding to the candidate cell needs to be updated, or the third RRC message deletes at least one candidate cell, and the deleted at least one candidate cell happens to fall into the candidate cell configured by the first RRC message , That is, the third RRC message deletes one or some candidate cells included in the first RRC message, and the CHO configuration information corresponding to the deleted at least one candidate cell included in the third RRC message can be complied with, and many more.
  • the terminal device can first determine the CHO configuration information of each candidate cell obtained after reconfiguration/update based on the method described above, according to the first RRC message and the third RRC message, or according to the third RRC message , And then determine whether the CHO configuration information of each candidate cell can be complied with.
  • the terminal device After determining that the CHO configuration information corresponding to some of the candidate cells obtained after the update cannot be complied with, or in other words, after determining that the CHO configuration information corresponding to some of the candidate cells obtained after the update can be complied with, The terminal device can continue to execute the subsequent process.
  • the terminal device determines whether the CHO configuration information of some candidate cells cannot be complied with in one or more candidate cells obtained after reconfiguration is not necessarily limited to the above-listed specific implementations.
  • This application is for the terminal device The specific implementation of is not limited.
  • the terminal device determines whether the CHO configuration information of each candidate cell can be complied with.
  • the candidate cells to which the CHO configuration information determined by the terminal device can be complied with may include one or more of the following:
  • the candidate cell is included in the first RRC message but not included in the third RRC message, and the CHO configuration information corresponding to the candidate cell included in the first RRC message can be complied with;
  • the candidate cell is included in the third RRC message but not included in the first RRC message, and the CHO configuration information corresponding to the candidate cell included in the third RRC message can be complied with;
  • the candidate cell is contained in the first RRC message and the third RRC message, and the CHO configuration information corresponding to the candidate cell contained in the first RRC message can be complied with, and the candidate cell contained in the third RRC message corresponds to The CHO configuration information can be followed.
  • the terminal device can determine one or more candidate cells obtained after reconfiguration according to the third RRC message, and can further determine whether there are CHO configurations of some candidate cells among the one or more candidate cells obtained after the reconfiguration. Cells whose information cannot be followed.
  • the terminal device can delete the stored CHO configuration information of the candidate cell (for example, the CHO configuration information corresponding to the candidate cell that can be complied by the terminal device included in the first RRC message).
  • the terminal device may determine whether it can comply with the CHO configuration information of each candidate cell in the third RRC message according to the third RRC message. And when it is determined that the CHO configuration information of some candidate cells cannot be complied with, or in other words, when it is determined that the CHO configuration information of some candidate cells can be complied with, the subsequent process is continued.
  • the candidate cell to which the CHO configuration information determined by the terminal device can be complied is included in the third RRC message.
  • the CHO configuration information corresponding to the candidate cell contained in the third RRC message can be complied with.
  • the terminal device determines whether there is a cell that satisfies the CHO execution condition among the candidate cells to which the CHO configuration information can be complied with.
  • step 340 For the specific process of the terminal device performing step 340, reference may be made to the related description of step 230 in the method 200 above. For brevity, it is not repeated here.
  • the candidate cell to which the CHO configuration information can be complied with in step 340 may be the candidate cell determined based on the foregoing step 330.
  • the CHO execution condition in step 340 may be an updated CHO execution condition.
  • the updated CHO execution condition may be determined based on the first RRC message and the third RRC message (for example, when the delta configuration information contained in the third RRC message When the delta parameter corresponding to the CHO execution condition is included in), it may also be the CHO execution condition of the candidate cell included in the third RRC message. This corresponds to the delta configuration and the full configuration described above, respectively. Since the CHO execution condition is included in the CHO configuration information, the specific process of the candidate cell reselection configuration/update has been described above in combination with the delta configuration and the full configuration. For the sake of brevity, it will not be repeated here.
  • the terminal device determines the candidate cell to which the CHO configuration information can be complied with according to the method described above, and then determines that the CHO configuration information can be complied with Is there a cell that satisfies the CHO execution condition among the candidate cells?
  • the cell that meets the CHO execution condition determined by the terminal device may include one or more of the following listed:
  • the cell is included in the first RRC message but not included in the third RRC message, and the CHO execution condition corresponding to the cell included in the first RRC message is met/satisfied;
  • the cell is included in the third RRC message but not included in the first RRC message, and the corresponding CHO execution condition of the cell included in the third RRC message is reached/satisfied;
  • the cell is included in the first RRC message and the third RRC message, and the corresponding CHO execution condition of the cell determined according to the first RRC message and the third RRC message is reached/satisfied.
  • the terminal device determines the candidate cell to which the CHO configuration information can be complied with according to the method described above, and then , Determine whether there is a cell that meets the CHO execution condition among the candidate cells for which the CHO configuration information can be complied with. Specifically, the cell that meets the CHO execution condition determined by the terminal device is included in the second RRC message, and the third RRC message The cell contained in the corresponding CHO execution condition is reached/satisfied.
  • the terminal device can perform different operations when there is or does not exist among the candidate cells to which the CHO configuration information can be complied with that meets the CHO execution condition. Similar to the method 200, if there are cells satisfying the CHO execution condition among the candidate cells for which the CHO configuration information can be complied with, the terminal device can execute the subsequent process according to the CHO configuration information of these cells. For example, perform step 350 to try to switch to the cell that meets the CHO execution condition; if the terminal device successfully switches to the cell that meets the CHO execution condition, the terminal device can perform step 360 to communicate with the cell that has been successfully handed over, or in other words, Communication in the cell where the handover is successful.
  • the terminal device may execute step 370 to initiate a re-establishment process.
  • the specific process from steps 350 to 370 is similar to the specific process from steps 240 to 260 in the method 200, and is not repeated here for brevity. It should be noted that the parameters used by the terminal device during the handover attempt and the parameters used for communication after the handover may be the latest parameters obtained after the candidate cell is reconfigured/updated.
  • the process of the terminal device trying to switch to a cell that meets the CHO execution condition in step 350 fails, or if the terminal device determines that there is no candidate cell that meets the CHO execution condition for the CHO configuration information to be complied with.
  • Candidate cells the terminal device can perform cell selection. If a cell that meets the S criterion determined by cell selection is included in a candidate cell whose CHO configuration information can be complied with, it can try to switch to that cell.
  • step 370 can be executed to initiate the re-establishment process.
  • process A in the method 200 above for example.
  • no detailed description is given here.
  • the terminal device can perform cell selection again, determine another cell that meets the S criterion, and determine whether the other cell that meets the S criterion is included in the CHO Among the candidate cells whose configuration information can be complied with, if so, the terminal device can try to switch to the cell again. This is repeated until it successfully accesses a certain cell and communicates with the cell that has been successfully handed over; or until the second timer maintained by the terminal device times out, step 370 is executed, and the terminal device initiates a re-establishment procedure.
  • step 370 is executed, and the terminal device initiates a re-establishment procedure.
  • the second timer can be started when the terminal device receives the first RRC message in step 310, it can also be started when the terminal device receives the third RRC message in step 320, or it can be determined by the terminal device. It starts when the target cell starts to perform step 340.
  • the duration of the second timer may be predefined, such as a protocol, or the first RRC message may contain related information about the second timer, such as the effective duration of the second timer, or the third The RRC message may contain related information of the second timer, such as the effective duration of the second timer. This application does not limit this.
  • the terminal device may then follow the first RRC message and/or the third RRC message, and the channel at this time. Evaluate and judge the status, etc., and try to re-determine the cell that meets the CHO execution conditions from the candidate cells whose CHO configuration information can be complied with as the new target cell.
  • the terminal device can try to switch to the new target cell, and repeat the process until all candidate cells whose CHO configuration information can be complied with have been judged whether to meet the CHO execution conditions, or until the CHO configuration information can be complied with and the CHO execution conditions are satisfied.
  • step 370 may be executed, and the terminal device initiates a re-establishment procedure.
  • the duration of the third timer may be predefined, such as predefined by the protocol, or the first RRC message may contain related information of the third timer, such as the effective duration of the third timer, or the third The RRC message may contain related information of the third timer, such as the effective duration of the third timer.
  • This application does not limit this.
  • the terminal device may try to handover all the cells whose CHO configuration information can be complied with and meet the CHO execution conditions in the configured candidate cells, but after the handover fails, perform cell selection, determine the cell that meets the S criterion, and It is determined whether the cell that satisfies the S criterion is included in the candidate cell for which the CHO configuration information can be complied with. If so, the terminal device attempts to switch to the cell that meets the S criterion. If the handover is successful, the current round of CHO process is successful.
  • step 370 may be performed, and the terminal device initiates a reset. Establish a process. For this implementation manner, for example, reference may be made to the process C in the method 200 above. For the sake of brevity, no detailed description is given here.
  • step 370 may be executed, and the terminal device initiates a re-establishment procedure.
  • the terminal device initiates a re-establishment procedure.
  • the terminal device determines in step 340 that there is no cell that meets the CHO execution condition among the candidate cells whose CHO configuration information can be satisfied, or in other words, if there is no such cell among the candidate cells whose CHO configuration information can be satisfied, its corresponding If the CHO execution condition can be reached/satisfied, the terminal device can perform cell selection, determine a cell that meets the S criterion, and then determine whether the cell that satisfies the S criterion is included in a candidate cell whose CHO configuration information can be complied with.
  • the terminal device may try to switch to the cell that satisfies the S criterion. If the terminal device successfully switches to the cell that meets the S criterion, it is considered that the current round of the CHO process is successful.
  • step 370 may be performed, and the terminal device initiates a re-establishment process .
  • the terminal device may directly perform step 370 to initiate a re-establishment process when it is determined that there is no cell that meets the CHO execution condition among the candidate cells that can be satisfied with the CHO configuration information.
  • the specific process of the terminal device initiating the re-establishment process has been described in detail above, and for brevity, it is not repeated here.
  • the terminal device can perform step 360 to communicate with the cell where the handover is successful when the current round of the CHO process is successful.
  • the terminal device performs step 320, that is, the time for receiving the third RRC message is not fixed.
  • the terminal device may have determined part of the candidate cells to which the CHO configuration information can be complied with according to the first RRC message, but after receiving the third RRC message, it needs to be further based on the first RRC message.
  • the third RRC message, or according to the third RRC message obtain the latest CHO configuration information corresponding to the candidate cell after reconfiguration/update, and then determine whether the latest CHO configuration information can be complied with.
  • the terminal device may also have determined the target cell that meets the CHO execution condition according to the first RRC message before performing step 320.
  • the terminal device may ignore/delete the third RRC message and try to switch to The determined target cell, or the terminal device needs to further determine whether the latest CHO configuration information can be complied with according to the latest CHO configuration information corresponding to the reconfiguration/update of the candidate cell, and then determine whether the CHO configuration information can be complied with Whether there is a cell that meets the CHO execution conditions among the candidate cells to try to handover.
  • the terminal device may even have determined the target cell before performing step 320 and is trying to switch to the target cell.
  • the terminal device can ignore/delete the third RRC message and continue to try to switch to the target cell, or the terminal device needs to further reconfigure/update the latest CHO configuration according to the candidate cell.
  • the information determines whether the latest CHO configuration information can be complied with, and then determines whether there is a cell that meets the CHO execution condition among the candidate cells for which the CHO configuration information can be complied with, in order to try handover.
  • the process in FIG. 3 is only an example, and the foregoing process is not shown.
  • CHO execution condition may specifically refer to the CHO execution condition in the CHO configuration information obtained after reconfiguration based on the received third RRC message.
  • the CHO execution condition may be the same as the CHO execution condition contained in the first RRC message, or may be different from the CHO execution condition contained in the first RRC message, which is not limited in this application.
  • step 330 when the terminal device performs step 330, it is possible that before step 320, it has determined a part of the candidate cells to which the CHO configuration information can be complied with.
  • the terminal device can determine the third RRC message, or the first RRC message and the first RRC message.
  • the third RRC message (for example, when the third RRC message is used to add a new candidate cell and/or modify the candidate cell that has been configured in the first RRC message), the candidate cell to which the CHO configuration information can be complied is determined again. For the sake of brevity, I will not list them all here.
  • the terminal device determines that it cannot comply with the CHO configuration information of all candidate cells in the first RRC message and/or the third RRC message, the terminal device discards the CHO configuration information corresponding to all the candidate cells that cannot be followed, and the terminal The device can remain in the source network device (that is, the terminal device maintains the RRC connection/data transmission with the source network device).
  • the terminal device sends an RRC message to the source network device to notify the RRC reconfiguration failure.
  • the message contains information about candidate cells that cannot be followed (such as PCI, frequency point information, measurement identification, etc.);
  • the terminal device can perform cell selection, for example, and determine a cell that satisfies the S criterion. If the cell that meets the S criterion determined by the terminal device is a candidate cell configured in the third RRC message, and the corresponding CHO configuration information can also be complied with, the terminal device can try to switch to the cell. If the terminal device is successfully handed over to the cell, it can communicate in the cell; otherwise, it can initiate a re-establishment procedure or execute the above-mentioned procedure A, which will not be repeated here.
  • the process of the terminal device trying to handover can refer to the relevant description in step 270 to step 290 in the method 200 above, and for brevity, it will not be repeated here.
  • the terminal device can reconfigure/update the candidate cell based on the received third RRC message.
  • the re-establishment process is not initiated, and the candidate cells whose CHO configuration information can be complied with are preferred to try to find a cell that meets the CHO execution conditions, and then try to switch to The cell; or it can be determined by cell selection that a terminal device that meets the S criterion cannot be successfully handed over to a cell that meets the CHO execution condition, or, among the candidate cells whose CHO configuration information can be complied with, the CHO execution condition cannot be found In the cell, you can still choose a cell suitable for handover based on the S criterion to try handover.
  • the terminal device searches for cells suitable for handover based on different dimensions, and is not limited to cells that meet the execution conditions of CHO. This will help the terminal equipment to find a suitable cell more likely to try to handover, avoid the delay and complexity caused by the re-establishment process to a greater extent, avoid the impact of a long communication interruption on the user experience, and help improve System reliability, guarantee system performance, and help improve user experience.
  • the processing method of the terminal device in the case of determining that it cannot comply with the CHO configuration information of some candidate cells is not limited to the method provided in the above method 200.
  • the following describes in detail the processing manner of the terminal device in the case where it is determined that the CHO configuration information of some candidate cells cannot be complied with in conjunction with another embodiment.
  • FIG. 4 is a schematic flowchart of a communication method 400 provided by another embodiment of the present application. As shown in FIG. 4, the method 400 may include step 410 to step 470. The steps in the method 400 are described in detail below.
  • the terminal device receives a first RRC message, the first RRC message including CHO configuration information of one or more candidate cells.
  • the first RRC message may be sent by the source network device, for example.
  • step 420 the terminal device determines that it cannot comply with the CHO configuration information of some candidate cells among the one or more candidate cells.
  • step 410 and step 420 please refer to the detailed description of step 210 and step 220 in the method 200 above. For the sake of brevity, it will not be repeated here.
  • step 430 the terminal device determines the first cell that satisfies the S criterion.
  • the cell that meets the S criterion is recorded as the first cell.
  • the first cell may be, for example, a cell selected by the terminal device through cell selection. It is understandable that the first cell may be a cell among the candidate cells configured in the first RRC message, or may not be a cell among the candidate cells configured in the first RRC message; the first cell may be that the CHO configuration information can be The satisfied candidate cell may also be a candidate cell whose CHO configuration information cannot be satisfied.
  • the terminal device can perform cell selection. For example, the terminal device can perform cell selection to select The first cell of the S criterion.
  • the specific process for the terminal device to perform cell selection can refer to the prior art. For brevity, it will not be described in detail here.
  • step 440 the terminal device determines whether the first cell is included in a candidate cell for which the CHO configuration information can be complied with.
  • the terminal device has determined in step 420 that the CHO configuration information of some candidate cells cannot be complied with, that is, the CHO configuration information of some candidate cells can be complied with.
  • the terminal device may determine whether the first cell determined in step 430 is included in the candidate cell for which the CHO configuration information can be complied with.
  • the first cell can be determined as the target cell, and step 450 can be performed to try to switch to the first cell, for example, the terminal device and the first cell
  • the cell performs the random access process.
  • the terminal device sends an RRC reconfiguration complete message to the first cell; or, if the first RRC message contains information about the RACH-less handover corresponding to the first cell , The terminal device skips the RACH process, and sends an RRC reconfiguration complete message to the first cell according to the relevant information of the RACH-less handover; and after the handover is successful, executes step 460 to communicate with the successfully handover cell (for example, the first cell).
  • step 470 may be executed to initiate a re-establishment procedure.
  • step 470 can also be replaced with the following process:
  • the terminal device can perform cell selection again. For example, the terminal device determines another cell that satisfies the S criterion, and if the cell is included in the candidate cell that can be complied with, it attempts to handover, and repeats this until the handover is successful or until the fourth timer If it times out, step 470 is executed to initiate a re-establishment process.
  • the fourth timer may be started when the terminal device receives the first RRC message in step 410, or it may be started when the terminal device starts to perform step 450 after determining the first cell. This application does not limit this.
  • the duration of the fourth timer may be predefined, such as a protocol, or the first RRC message may include related information of the fourth timer, such as the effective duration of the fourth timer. This application does not limit this.
  • the terminal device can save the CHO configuration information of these candidate cells for use in subsequent procedures.
  • the terminal device may also save the CHO configuration information of the first cell when it is determined that the first cell that satisfies the S criterion is included in the candidate cell whose CHO configuration information can be complied with; the CHO configuration information of the first cell is not included in the CHO configuration information.
  • the compliant candidate cell the CHO configuration information of each candidate cell in the first RRC message is not saved.
  • the terminal device only needs to save the CHO configuration information of the first cell, which can reduce the occupation of the storage space of the terminal device.
  • the terminal device may not initiate a re-establishment procedure, but preferentially try handover when it is determined that it cannot comply with the CHO configuration information of some candidate cells.
  • the terminal device can determine a cell that satisfies the S criterion through cell selection, and try to switch to the cell if the cell contains a candidate cell whose CHO configuration information can be complied with. In this way, the delay and complexity caused by the re-establishment process can be avoided, and the impact of a long communication interruption on the user experience can be avoided, which is conducive to improving system reliability, ensuring system performance, and improving user experience.
  • the terminal device may also receive other RRC messages while maintaining the RRC connection with the source network device.
  • the following describes in detail the specific process in the case where the terminal device successfully receives the third RRC message for reconfiguration in conjunction with specific embodiments.
  • FIG. 5 is a schematic flowchart of a communication method 500 provided by still another embodiment of the present application. As shown in FIG. 5, the method 500 may include step 510 to step 580. The steps in the method 500 are described in detail below.
  • the terminal device receives a first RRC message, the first RRC message including CHO configuration information of one or more candidate cells.
  • the first RRC message may be sent by the source network device, for example.
  • step 510 please refer to the detailed description of step 210 in the above method 200. For the sake of brevity, it will not be repeated here.
  • the terminal device receives a third RRC message, which is used to reconfigure candidate cells.
  • the third RRC message may also be sent by the source network device, for example.
  • the third RRC message may also include CHO configuration information of one or more candidate cells, so as to reconfigure the candidate cells.
  • the third RRC message can be used to modify or release the candidate cell configured in the first RRC message, and/or to add a new cell (for example, the new cell is not included in the candidate cell configured in the first RRC message ) As a candidate cell.
  • the terminal device If the terminal device successfully verifies the integrity protection of the third RRC message, it can parse out the CHO configuration information of one or more candidate cells included in the third RRC message.
  • the third RRC message is used to reconfigure candidate cells. Therefore, one or more candidate cells in the third RRC message may be the same or different from one or more candidate cells in the first RRC message.
  • the application embodiment does not limit this. Since step 320 in the above method 300 has combined multiple examples to describe the update method and process in detail, for the sake of brevity, it will not be repeated here.
  • step 530 the terminal device determines that it cannot comply with the CHO configuration information of some candidate cells.
  • the third RRC message is used to reconfigure the candidate cell (for example, to modify or release the candidate cell configured in the first RRC message, and/or to add a new cell (for example, the The new cell is not included in the candidate cells configured in the first RRC message). Therefore, the part of the candidate cells in step 530 may be included in the updated candidate cells.
  • the CHO of the part of the candidate cells The configuration information may be included in the latest CHO configuration information corresponding to the candidate cell obtained after reconfiguration/update.
  • the third RRC message when used to reconfigure candidate cells, the third RRC message may include but is not limited to delta configuration information, or the third RRC message may include, but is not limited to, full configuration information. Or it can be understood that when reconfiguring candidate cells, a delta configuration or a full configuration method can be used. In this embodiment, based on different methods, the operations performed by the terminal device may be different.
  • the third RRC message contains delta configuration information
  • the terminal device performs step 530, that is, the terminal device can determine that some candidate cells cannot be complied with according to the first RRC message and the third RRC message, or according to the third RRC message CHO configuration information.
  • the third RRC message contains full configuration information
  • the terminal device executes step 530, that is, the terminal device can directly determine that the CHO configuration information of some candidate cells cannot be complied with according to the third RRC message.
  • step 530 The specific process of the terminal device performing step 530 is related to the description of step 330 in the method 300 above. Since the above method 300 has combined the delta configuration and the full configuration to separately describe the specific implementation of the terminal device in detail, for the sake of brevity, it will not be repeated here.
  • step 540 the terminal device determines a third cell that satisfies the S criterion.
  • the cell that meets the S criterion is recorded as the third cell.
  • the third cell may be, for example, a cell selected by the terminal device through cell selection. It is understandable that the third cell may be one of the candidate cells configured in the first RRC message, or may not be one of the candidate cells configured in the first RRC message; the third cell may be that the CHO configuration information can be The satisfied candidate cell may also be a candidate cell whose CHO configuration information cannot be satisfied.
  • the terminal device may perform cell selection. For example, the terminal device may determine a third cell that satisfies the S criterion by performing cell selection.
  • the specific process for the terminal device to perform cell selection can refer to the prior art. For brevity, it will not be described in detail here.
  • step 550 the terminal device determines whether the third cell is included in the candidate cell for which the CHO configuration information can be complied with.
  • the terminal device has determined in step 530 that the CHO configuration information of some candidate cells cannot be complied with, that is, the CHO configuration information of some candidate cells can be complied with.
  • the terminal device may determine whether the third cell determined in step 540 is included in the candidate cell to which the CHO configuration information can be complied with.
  • the third cell can be determined as the target cell, and step 560 can be performed to try to switch to the third cell; and after the handover is successful, perform step 570.
  • Communicate with the third cell or in other words, communicate in the third cell.
  • step 580 can be executed to initiate a re-establishment process.
  • step 580 can also be replaced with the following process:
  • the terminal device determines the fourth cell that satisfies the S criterion, and may further determine whether the fourth cell is included in the candidate cell for which the CHO configuration information can be complied with. If the fourth cell is included in the candidate cells to which the CHO configuration information can be complied with, the fourth cell is a new target cell, and the terminal device can try to switch to the fourth cell. If the handover is successful, the terminal device can communicate with the fourth cell, or in other words, communicate in the fourth cell. If the fourth cell is not included in the candidate cell for which the CHO configuration information can be complied with, or if the terminal device fails to switch to the fourth cell, the terminal device performs cell selection again.
  • step 580 may be executed to initiate the re-establishment process.
  • the fifth timer may be started when the terminal device receives the first RRC message in step 510, or, the fifth timer may be started when the terminal device receives the third RRC message in step 520, or, It may also be started after the terminal device determines the third cell, or it may also be started after the terminal device determines the fourth cell. This application does not limit this.
  • the duration of the fifth timer may be predefined, such as a protocol, or the first RRC message may contain related information about the fifth timer, such as the effective duration of the fifth timer, or the third RRC The message may contain related information about the fifth timer, such as the effective duration of the fifth timer. This application does not limit this.
  • step 450 in the above method 400 has also exemplified the process in which the terminal device attempts to switch to a certain cell. For the sake of brevity, it will not be repeated here.
  • the terminal device can save the CHO configuration information of these candidate cells for use in subsequent procedures.
  • the terminal device may also save the CHO configuration information of the third cell when it is determined that the third cell that satisfies the S criterion is included in the candidate cell whose CHO configuration information can be complied with; when it is determined that the third cell that satisfies the S criterion is not In the case of candidate cells whose CHO configuration information can be complied with, the updated CHO configuration information of each candidate cell is not saved.
  • the terminal device only needs to save the CHO configuration information of the third cell, which can reduce the occupation of the storage space of the terminal device.
  • the terminal device performs step 520, that is, the time for receiving the third RRC message is not fixed.
  • the terminal device may have determined part of the candidate cells to which the CHO configuration information can be complied with according to the first RRC message, but after receiving the third RRC message, it needs to be further based on the first RRC message.
  • the third RRC message, or according to the third RRC message obtain the latest CHO configuration information corresponding to the candidate cell after reconfiguration/update, and then determine whether the latest CHO configuration information can be complied with.
  • the terminal device Before performing step 520, the terminal device may also have determined that the first cell that satisfies the S criterion is included in the candidate cell that the CHO configuration information can be complied with (for example, before step 520, the terminal device has performed step 410- in method 400). Step 440), but after receiving the third RRC message, the terminal device can ignore/delete the third RRC message, and continue to complete the process that was in progress before receiving the third RRC message; or, the terminal device needs to further follow the candidate cell
  • the latest CHO configuration information corresponding to the reconfiguration/update determines whether the latest CHO configuration information can be complied with.
  • the terminal device determines the third cell that satisfies the S criterion, and confirms whether the latest CHO configuration information can be complied with.
  • the third cell is included in the candidate cells obtained after the update, an attempt is made to switch to the third cell.
  • the process in FIG. 5 is only an example, showing the process from step 510 to step 580 above, and does not show the other optional processes mentioned above.
  • each step is shown in sequence in FIG. 5, this should not constitute any limitation to the present application.
  • the terminal device may determine the third RRC message according to the third RRC message, or the first RRC message and the first RRC message.
  • the third RRC message (for example, when the third RRC message is used to add a new candidate cell and/or modify the candidate cell that has been configured in the first RRC message), the candidate cell to which the CHO configuration information can be complied is determined again.
  • I will not list them all here.
  • the terminal device can reconfigure/update the candidate cell based on the received third RRC message.
  • the re-establishment procedure is not initiated, and handover is tried first.
  • the terminal device can determine a cell that satisfies the S criterion through cell selection, and try to switch to the cell if the cell contains a candidate cell whose CHO configuration information can be complied with. In this way, the delay and complexity caused by the re-establishment process can be avoided, and the impact of a long communication interruption on the user experience can be avoided, which is conducive to improving system reliability, ensuring system performance, and improving user experience.
  • the terminal device determines that the CHO configuration information of some candidate cells cannot be complied with, since the CHO configuration information includes the CHO execution conditions and the parameters corresponding to each candidate cell, the CHO configuration information for each candidate cell
  • the CHO configuration information of the cell is evaluated, which may bring a larger workload. Therefore, another method is provided below, which can further reduce the workload of the terminal device on the basis of avoiding the re-establishment process.
  • FIG. 6 is a schematic flowchart of a communication method provided by another embodiment of the present application. As shown in FIG. 6, the method 600 may include step 610 to step 660. The steps in the method 600 are described in detail below.
  • the terminal device receives a first RRC message, the first RRC message including CHO configuration information of one or more candidate cells.
  • the first RRC message may be sent by the source network device, for example.
  • step 610 For the detailed description of step 610, reference may be made to the detailed description of step 210 in the above method 200. For brevity, it will not be repeated here.
  • step 620 if the terminal device cannot comply with the CHO execution condition of some candidate cells in the one or more candidate cells, it determines that there are some candidate cells in the one or more candidate cells whose CHO execution conditions can be complied with. At least one first candidate cell that meets the CHO execution condition.
  • the CHO configuration information of the candidate cell may include CHO execution conditions and parameters corresponding to the candidate cell.
  • the terminal device may first determine whether it can comply with the CHO execution conditions of each candidate cell, but it is temporarily uncertain whether it can comply with the parameters corresponding to each candidate cell.
  • the terminal device since the terminal device only needs to determine whether to comply with the CHO execution conditions of each candidate cell, compared to determining whether to comply with the CHO configuration information of each candidate cell, the workload of the terminal device is reduced and the processing time is shortened; on the other hand; Since there may be multiple candidate cells sharing the CHO execution conditions, the workload of the terminal equipment can be further reduced.
  • the terminal device determines that it cannot comply with the CHO execution conditions of some of the one or more candidate cells, that is, the terminal device can comply with the other remaining one or more of the one or more candidate cells. CHO execution conditions of candidate cells.
  • the terminal device may further determine whether there is a candidate cell that satisfies the CHO execution condition from among one or more candidate cells to which the CHO execution condition can be complied with.
  • the candidate cell that meets the CHO execution condition among one or more candidate cells that can be complied with the CHO execution condition is recorded as the first candidate cell. If the terminal device can determine at least one first candidate cell in step 620, it can continue to perform step 630 to determine whether the parameter corresponding to the CHO configuration information exists in the at least one first candidate cell (that is, the CHO configuration information contains The parameter corresponding to the candidate cell) can be the cell that can be complied with.
  • step 630 may specifically refer to determining whether there is a target cell in the at least one first candidate cell, and the parameters included in the CHO configuration information corresponding to the target cell can be complied with.
  • step 640 can be performed to try handover To the cell to which the corresponding parameter in the CHO configuration information can be complied with. That is, the terminal device determines that the target cell exists in at least one of the first candidate cells, and then attempts to switch to the target cell.
  • the number of target cells may be one or multiple.
  • the terminal device trying to switch to the target cell it can try to switch to each target cell at different times in sequence, and finally access to one of them.
  • the specific process of the terminal device trying to switch to the target cell is described in detail in step 240 in the method 200 above, and for brevity, it will not be repeated here.
  • the terminal device may save the CHO configuration information corresponding to the cell in the case of determining that there is a cell that can be complied with in the CHO configuration information in the at least one first candidate cell, for use in subsequent procedures.
  • step 650 may be performed to communicate with the cell where the handover is successful, or in other words, to communicate in the cell where the handover is successful. If the handover of the terminal device fails, or if the terminal device determines that there is no cell in which the parameters corresponding to the CHO configuration information can be complied with in the at least one first candidate cell, step 660 may be performed to initiate a re-establishment process.
  • the terminal device fails in step 640 when it tries to switch to a cell to which the corresponding parameter in the CHO configuration information can be complied with, or if the terminal device determines in step 630 that at least one of the first candidate cells If there is no candidate cell whose corresponding parameters can be complied with, the terminal device can perform cell selection. If the cell that meets the S criterion determined by cell selection is included in the candidate cell whose CHO configuration information can be complied with, it can try to switch to The cell.
  • step 660 can be executed to initiate a re-establishment process.
  • the terminal device can perform cell selection again, determine another cell that meets the S criterion, and determine whether the other cell that meets the S criterion is included in the CHO Among the candidate cells whose configuration information can be complied with, if so, the terminal device can try to switch to the cell again. Repeat this until it successfully accesses a cell and communicates with the cell that has been successfully handed over; or until the sixth timer maintained by the terminal device expires, step 660 is executed, and the terminal device initiates a re-establishment process.
  • the sixth timer may be started when the terminal device receives the first RRC message in step 610, or it may be started when the terminal device starts to perform step 640 after determining the target cell. This application does not limit this.
  • the duration of the sixth timer may be, for example, predefined, such as protocol predefined, or the first RRC message may include related information of the sixth timer, such as the effective duration of the sixth timer. This application does not limit this.
  • the terminal device can then follow the first RRC message, the channel status at this time, etc. , Evaluate and judge, try to re-determine the cell that meets the CHO execution condition from the candidate cells where the CHO execution condition can be complied with. If it can be determined, then judge whether the parameters corresponding to the determined cell can be complied with, if If it can be complied with, it will be used as a new target cell.
  • the terminal device can try to switch to a new target cell, and repeat the process until all candidate cells whose CHO execution conditions can be complied with have been judged whether they meet the CHO execution conditions, or until all candidate cells whose CHO execution conditions can be complied with All of the cells that can meet the CHO execution conditions have been judged whether their corresponding parameters can be complied with, or until all candidate cells that meet the CHO execution conditions and the corresponding parameters can be complied with have been tried to handover, or Until the seventh timer on the terminal device side expires, step 660 can be performed, and the terminal device initiates a re-establishment procedure.
  • the duration of the seventh timer may be predefined, such as a protocol, or the first RRC message may include related information of the seventh timer, such as the effective duration of the seventh timer.
  • the terminal device starts the seventh timer after receiving the first RRC message, or starts the seventh timer when step 640 is executed. This application does not limit this.
  • the terminal device may try to handover all the cells whose CHO configuration information can be complied with and meet the CHO execution conditions in the configured candidate cells, but after the handover fails, perform cell selection, determine the cell that meets the S criterion, and It is determined whether the cell that satisfies the S criterion is included in the candidate cell for which the CHO configuration information can be complied with. If so, the terminal device attempts to switch to the cell that meets the S criterion. If the handover is successful, the current round of CHO process is successful.
  • step 660 may be performed, and the terminal device initiates a reset. Establish a process.
  • the terminal device can perform cell selection again , Repeat the execution until a certain cell is successfully accessed, then the current round of the CHO process is successful; or, if the seventh timer expires, then step 660 can be performed, and the terminal device initiates a re-establishment process.
  • the terminal device may perform cell selection, determine a cell that meets the S criterion, and then determine the cell that meets the S criterion Whether it is included in the candidate cell to which the CHO configuration information can be complied with. If the cell that satisfies the S criterion is included in the candidate cells whose CHO configuration information can be complied with, and the cell that satisfies the S criterion is the target cell, the terminal device may try to switch to the cell that satisfies the S criterion.
  • step 660 may be performed, and the terminal device initiates a re-establishment process .
  • the terminal device may also directly execute step 660 to initiate a re-establishment process when it is determined that there is no candidate cell whose corresponding parameter can be complied with in the at least one first candidate cell.
  • the terminal device may perform step 650 to communicate with the cell that has been successfully handed over if the current round of the CHO process is successful.
  • the terminal device may not initiate a re-establishment procedure, but preferentially try handover when it is determined that it cannot comply with the CHO execution conditions of some candidate cells.
  • the terminal device can determine the cell that meets the CHO execution condition from the candidate cells where the CHO execution condition is complied with, and then determine the cell to which the corresponding parameter in the CHO configuration information can be complied with from the determined cells that meet the CHO execution condition.
  • cell selection can be used to determine if a terminal device that satisfies the S criterion fails to switch to a cell that meets the CHO execution conditions, or to find a candidate cell whose CHO configuration information can be complied with.
  • a cell suitable for handover can still be selected based on the S criterion to try handover.
  • the terminal device searches for cells suitable for handover based on different dimensions, and is not limited to cells that meet the execution conditions of CHO. This will help the terminal equipment to find a suitable cell more likely to try to handover, avoid the delay and complexity caused by the re-establishment process to a greater extent, avoid the impact of a long communication interruption on the user experience, and help improve System reliability, guarantee system performance, and help improve user experience.
  • the terminal device since the terminal device only needs to evaluate whether the CHO execution conditions of each candidate cell can be evaluated after receiving the first RRC message, after determining the cells that meet the CHO execution conditions, it evaluates whether the parameters in the CHO configuration information of these cells Being able to be complied with can reduce the number of candidate cells to be evaluated, reduce the workload of the terminal equipment, and reduce the complexity of implementation.
  • the terminal device may also receive other RRC messages while maintaining the RRC connection with the source network device.
  • the following describes in detail the specific process in the case where the terminal device successfully receives the third RRC message for reconfiguration in conjunction with specific embodiments.
  • FIG. 7 is a schematic flowchart of a communication method 700 provided by still another embodiment of the present application. As shown in FIG. 7, the method 700 may include step 710 to step 770. The steps in the method 700 are described in detail below.
  • the terminal device receives a first RRC message, where the first RRC message includes CHO configuration information of one or more candidate cells.
  • the first RRC message may be sent by the source network device, for example.
  • step 710 please refer to the detailed description of step 210 in the method 200 above. For the sake of brevity, it will not be repeated here.
  • the terminal device receives a third RRC message, which is used to reconfigure the candidate cell.
  • the third RRC message may also be sent by the source network device, for example.
  • the third RRC message may also include CHO configuration information of one or more candidate cells, so as to reconfigure the candidate cells.
  • the third RRC message can be used to modify or release the candidate cell configured in the first RRC message, and/or to add a new cell (for example, the new cell is not included in the candidate cell configured in the first RRC message ) As a candidate cell.
  • the terminal device If the terminal device successfully verifies the integrity protection of the third RRC message, it can parse out the CHO configuration information of one or more candidate cells included in the third RRC message.
  • the third RRC message is used to reconfigure candidate cells. Therefore, one or more candidate cells in the third RRC message may be the same or different from one or more candidate cells in the first RRC message.
  • the application embodiment does not limit this. Since step 320 in the above method 300 has combined multiple examples to describe the update method and process in detail, for the sake of brevity, it will not be repeated here.
  • step 730 in the case that the CHO execution condition of some candidate cells among one or more candidate cells cannot be complied with, the terminal device determines that there is at least one that satisfies the CHO execution condition in the partial candidate cells whose CHO execution condition can be complied with. A second candidate cell.
  • the one or more candidate cells in step 730 may be candidate cells obtained after reconfiguration.
  • the CHO execution condition may be a CHO execution condition obtained after reconfiguration.
  • the CHO execution condition may be the CHO execution condition in the CHO configuration information obtained after reconfiguration. Therefore, the CHO execution condition may not be updated or may be updated, which is not limited in this application.
  • the cell that meets the CHO execution condition among the partial candidate cells that can be complied with the CHO execution condition is recorded as the second candidate cell.
  • the terminal device may determine at least one second candidate cell in step 730.
  • the third RRC message when used to reconfigure candidate cells, the third RRC message may include but is not limited to delta configuration information, or the third RRC message may include, but is not limited to, full configuration information. Or it can be understood that when reconfiguring candidate cells, a delta configuration or a full configuration method can be used. In this embodiment, based on different methods, the operations performed by the terminal device may be different.
  • the third RRC message contains delta configuration information
  • the terminal device performs step 730, that is, the terminal device can determine whether it can comply with the CHO of the candidate cell according to the first RRC message and the third RRC message, or according to the third RRC message.
  • the execution condition and in the case that the CHO execution condition of some candidate cells cannot be complied with, the second candidate cell that satisfies the CHO execution condition is determined from another part of the candidate cells for which the CHO execution condition can be complied with.
  • the terminal device executes step 730, that is, the terminal device can determine whether it can comply with the CHO execution condition of the candidate cell according to the third RRC message, and if it cannot comply with part of the candidate cell In the case of the CHO execution condition, the second candidate cell that satisfies the CHO execution condition is determined from another part of the candidate cells that can be complied with the CHO execution condition.
  • the time when the terminal device receives the third RRC message is not fixed. Based on the difference in the timing of receiving the third RRC message by the terminal device, the operation of the terminal device may be different.
  • the terminal device may determine, according to the CHO configuration information of each candidate cell in the first RRC message, that it cannot comply with the CHO execution condition of some candidate cells configured in the first RRC message. After receiving the third RRC message, the terminal device may need to further determine whether it can comply with the CHO execution condition of the candidate cell obtained after the update based on the CHO configuration information of the candidate cell obtained after the update.
  • the specific implementation of the terminal device may be different. Since step 330 in the above method 300 has combined different situations to describe in detail the specific method for the terminal device to determine whether it can comply with the CHO configuration information of the candidate cell obtained after reconfiguration/update, the terminal device determines that it can comply with the updated CHO configuration information.
  • the specific method of the CHO execution condition is similar to it, for the sake of brevity, it will not be repeated here.
  • the terminal device obtains the reconfiguration/update according to the first RRC message and the third RRC message, or according to the third RRC message After the CHO configuration information of each candidate cell, the terminal device determines whether it can comply with the CHO execution condition of each candidate cell.
  • the candidate cells for which the CHO execution condition determined by the terminal device can be complied with may include one or more of the following listed:
  • the candidate cell is included in the first RRC message but not included in the third RRC message, and the CHO execution condition corresponding to the candidate cell included in the first RRC message can be complied with;
  • the candidate cell is included in the third RRC message but not included in the first RRC message, and the CHO execution condition corresponding to the candidate cell included in the third RRC message can be complied with;
  • the candidate cell is contained in the first RRC message and the third RRC message, and the CHO execution condition corresponding to the candidate cell contained in the first RRC message can be complied with, and the candidate cell contained in the third RRC message corresponds to The CHO execution conditions can be complied with.
  • the second candidate cell that meets the CHO execution condition determined by the terminal device from the candidate cells that the CHO execution condition can comply with may include one or more of the following listed:
  • the second candidate cell is included in the first RRC message but not included in the third RRC message, and the CHO execution condition corresponding to the second candidate cell included in the first RRC message is met/satisfied;
  • the second candidate cell is included in the third RRC message but not included in the first RRC message, and the CHO execution condition corresponding to the second candidate cell included in the third RRC message is met/satisfied;
  • the second candidate cell is included in the first RRC message and the third RRC message, and the CHO execution condition corresponding to the second candidate cell obtained according to the first RRC message and the third RRC message is reached/satisfied.
  • the terminal device determines the candidate cell to which the CHO execution condition can be complied with according to the method described above, and then , Determine whether there is a cell that satisfies the CHO execution condition among the candidate cells that can be complied with. For example, the cell that meets the CHO execution condition determined by the terminal device is included in the third RRC message, and the corresponding CHO execution condition of the cell included in the third RRC message is reached/satisfied.
  • step 740 the terminal device determines whether the at least one second candidate cell has a cell with which the parameter corresponding to the CHO configuration information can be complied with.
  • the terminal device determines “the at least one second Whether there is a cell that can be complied with in the CHO configuration information in the candidate cell”.
  • the terminal device in the case of delta configuration, in the process of performing step 740, can determine whether the corresponding parameter in the CHO configuration information can be detected in at least one second candidate cell according to the first RRC message and the third RRC message. Compliant cell. In the case of full configuration, the terminal device may determine, according to the third RRC message, whether there is a cell with which the parameter corresponding to the CHO configuration information can be complied with in the at least one second candidate cell.
  • the terminal device determines that there is a cell whose parameters in the CHO configuration information can be complied with in the at least one second candidate cell, then the cell whose parameters corresponding to the at least one second candidate cell can be complied with is the target cell.
  • step 770 is executed to initiate re-establishment Process.
  • the specific process of the foregoing steps 750 to 770 is similar to the specific process of steps 640 to 660 in the method 600, and is not repeated here for brevity. It should be noted that the parameters used by the terminal device during the handover attempt and the parameters used for communication after the handover may be parameters obtained after reconfiguration/update.
  • the terminal device when the terminal device attempts to switch to a cell in which the corresponding parameters in the CHO configuration information can be complied with in 750, or if the terminal device determines in step 740 that at least one of the second candidate cells is not If there is a candidate cell whose corresponding parameters can be complied with, the terminal device can perform cell selection. If the cell that meets the S criterion determined by cell selection is included in the candidate cell whose CHO configuration information can be complied with, it can try to switch to that cell. Community.
  • step 770 can be executed to initiate the re-establishment process.
  • process A in the method 200 above for example.
  • no detailed description is given here.
  • the terminal device can perform cell selection again, determine another cell that meets the S criterion, and determine whether the other cell that meets the S criterion is included in the CHO Among the candidate cells whose configuration information can be complied with, if so, the terminal device can try to switch to the cell again. Repeat this until it successfully accesses a certain cell and communicates with the cell that has been successfully handed over; or until the eighth timer maintained by the terminal device expires, execute step 770, and the terminal device initiates a re-establishment process.
  • the eighth timer may be started when the terminal device receives the first RRC message in step 710, it may also be started when the terminal device receives the second RRC message in step 720, or it may be determined by the terminal device. It starts when the target cell starts to execute step 750.
  • the duration of the eighth timer may be predefined, such as predefined by the protocol, or the first RRC message may contain related information about the eighth timer, such as the effective duration of the eighth timer, or the third The RRC message may include related information of the eighth timer, such as the effective duration of the eighth timer. This application does not limit this.
  • the terminal device may then follow the first RRC message and/or the third RRC message , The channel state at this time, etc., evaluate and judge, try to re-determine the cell that meets the CHO execution condition from the candidate cells that the CHO execution condition can be complied with. If it can be determined, then judge the cell corresponding to the determined cell Whether the parameter can be complied with, and if it can be complied with, it will be regarded as the new target cell.
  • the terminal device can try to switch to a new target cell, and repeat the process until all candidate cells whose CHO execution conditions can be complied with have been judged whether they meet the CHO execution conditions, or until all candidate cells whose CHO execution conditions can be complied with All of the cells that can meet the CHO execution conditions have been judged whether their corresponding parameters can be complied with, or until all candidate cells that meet the CHO execution conditions and the corresponding parameters can be complied with have been tried to handover, or Until the ninth timer on the terminal device side expires, step 770 may be executed, and the terminal device initiates a re-establishment procedure.
  • the duration of the ninth timer may be predefined, such as predefined by the protocol, or the first RRC message may contain related information about the ninth timer, such as the effective duration of the ninth timer, or the third The RRC message may contain related information about the ninth timer, such as the effective duration of the ninth timer. This application does not limit this.
  • the terminal device may try to handover all the cells whose CHO configuration information can be complied with and meet the CHO execution conditions in the configured candidate cells, but after the handover fails, perform cell selection, determine the cell that meets the S criterion, and It is determined whether the cell that satisfies the S criterion is included in the candidate cell for which the CHO configuration information can be complied with. If so, the terminal device attempts to switch to the cell that meets the S criterion. If the handover is successful, the current round of CHO process is successful.
  • step 770 may be executed, and the terminal device initiates a reset. Establish a process.
  • the terminal device can perform cell selection again , Repeat the execution until a certain cell is successfully accessed, then the current round of CHO process is successful; or, if the ninth timer expires, then step 660 may be performed, and the terminal device initiates a re-establishment process.
  • the terminal device can perform cell selection, determine a cell that meets the S criterion, and then determine the cell that meets the S criterion Whether it is included in the candidate cell to which the CHO configuration information can be complied with. If the cell that satisfies the S criterion is included in the candidate cells whose CHO configuration information can be complied with, and the cell that satisfies the S criterion is the target cell, the terminal device may try to switch to the cell that satisfies the S criterion.
  • step 770 may be performed, and the terminal device initiates a re-establishment procedure .
  • the terminal device may also directly execute step 770 to initiate a re-establishment process when it is determined that there is no candidate cell whose corresponding parameter can be complied with in the at least one first candidate cell.
  • the terminal device can perform step 760 to communicate with the cell where the handover is successful if the current round of the CHO process is successful.
  • the terminal device may have determined part of the candidate cells whose CHO execution conditions can be complied with according to the CHO configuration information of the candidate cells in the first RRC message, but after receiving the third RRC message, it still needs
  • the candidate cell to which the CHO execution condition obtained after the update can be complied with is further determined according to the CHO configuration information of the candidate cell obtained after the update.
  • the terminal device may have determined the target cell that meets the CHO execution condition according to the first RRC message before performing step 720.
  • the terminal device may ignore/delete the third RRC message and try Switch to the determined target cell, or the terminal device needs to further determine whether the CHO execution condition contained in the latest CHO configuration information can be complied with according to the latest CHO configuration information corresponding to the reconfiguration/update of the candidate cell, Then determine whether there is a cell that meets the CHO execution condition among the candidate cells for which the CHO execution condition can be complied with. If so, determine the parameters corresponding to the cell that meets the CHO execution condition (that is, the cell corresponding to the cell is included in the latest CHO configuration information The parameters in) can be complied with.
  • the terminal device may even have determined the target cell before performing step 720, and is trying to switch to the target cell. But after receiving the third RRC message, the terminal device can ignore/delete the third RRC message and continue to switch to the determined target cell, or the terminal device needs to further reconfigure/update the corresponding candidate cell according to the candidate cell.
  • the latest CHO configuration information determines whether the CHO execution condition contained in the latest CHO configuration information can be complied with, and then it is determined whether there is a cell that meets the CHO execution condition among the candidate cells whose CHO execution condition can be complied with. If so, it is determined whether the parameters corresponding to the cell that meets the CHO execution condition (that is, the parameters included in the latest CHO configuration information corresponding to the cell) can be complied with.
  • step 730 when the terminal device performs step 730, it is possible that before step 720, a part of candidate cells that can be complied with the CHO execution condition may be determined.
  • the terminal device may determine the third RRC message according to the third RRC message, or the first RRC message and the first The third RRC message (for example, when the third RRC message is used to add a new candidate cell and/or modify the candidate cell that has been configured in the first RRC message), the candidate cell to which the CHO execution condition can be complied is re-determined. For the sake of brevity, I will not list them all here.
  • the terminal device can reconfigure/update the candidate cell based on the received third RRC message.
  • the re-establishment procedure is not initiated, and handover is tried first.
  • the terminal device can judge whether there is a cell that meets the CHO execution condition from the candidate cells that the CHO execution condition can be complied with, and if so, then judge the parameter corresponding to the cell (that is, the cell corresponding to the CHO configuration obtained after the update) Whether the parameter in the information can be complied with, and if it can be complied with, try to switch to the cell.
  • the delay and complexity caused by the re-establishment process can be avoided, and the impact of a long communication interruption on the user experience can be avoided, which is conducive to improving system reliability, ensuring system performance, and improving user experience.
  • the terminal device since the terminal device only needs to evaluate whether the CHO execution conditions of each candidate cell can be evaluated after receiving the first RRC message, after determining the cells that meet the CHO execution conditions, it evaluates whether the parameters in the CHO configuration information of these cells Being able to be complied with can reduce the number of candidate cells to be evaluated, reduce the workload of the terminal equipment, and reduce the complexity of implementation.
  • the communication method provided by the embodiment of the present application has been described in detail with reference to FIG. 2 to FIG. 7.
  • the operation procedures of the terminal device are described on the assumption that the RRC message (such as the first RRC message, the third RRC message, etc.) sent to the source network device is successfully received.
  • the terminal device fails the integrity protection check of the received RRC message (such as the second RRC message described above).
  • the terminal device determines that the integrity protection check of the second RRC message fails, it does not initiate a re-establishment procedure, but still based on the CHO configuration information of one or more candidate cells in the first RRC message Continue the switching process.
  • FIG. 8 is a schematic flowchart of a communication method 800 provided by still another embodiment of the present application. As shown in FIG. 8, the method 800 may include step 810 to step 870. The steps in the method 800 are described in detail below.
  • the terminal device receives a first RRC message, where the first RRC message includes CHO configuration information of one or more candidate cells.
  • the first RRC message may be sent by the source network device, for example.
  • step 810 please refer to the detailed description of step 210 in the method 200 above. For the sake of brevity, it will not be repeated here.
  • step 820 the terminal device receives the second RRC message, but the integrity protection check of the second RRC message fails.
  • the terminal device may also receive other RRC messages, that is, the second RRC message.
  • the second RRC message may be used to reconfigure candidate cells.
  • the second RRC message may be the third RRC message described above.
  • the second RRC message may also be used to instruct the terminal device to perform traditional handover; or, the second RRC message may also be used for other purposes.
  • the embodiment of the application does not limit this.
  • the terminal device may discard the second RRC message, and perform step 830, perform cell selection, and determine a cell that meets the S criterion.
  • the cell that meets the S criterion is recorded as the fifth cell.
  • step 840 the terminal device determines whether the fifth cell is included in a candidate cell for which the CHO configuration information can be complied with.
  • the terminal device can still determine whether the fifth cell is a candidate for the first RRC message configuration based on the CHO configuration information of one or more candidate cells in the first RRC message Whether the cell and the corresponding CHO configuration information can be complied with.
  • step 850 may be performed, and the terminal device attempts to switch to the fifth cell. If the terminal device is successfully handed over to the fifth cell, step 860 may be performed to communicate with the fifth cell, in other words, communicate in the fifth cell.
  • step 870 can be executed to initiate the RRC re-establishment process.
  • step 870 can also be replaced with the following process:
  • the terminal device performs cell selection again. For example, if the terminal device determines another cell that meets the S criterion, if the cell is included in the candidate cells that can be followed, it tries to handover, and repeats this process until the handover is successful, and the handover is successful. Communication, in other words, communication with the cell where the handover is successful; or, if the tenth timer expires and the handover fails, step 870 is executed to initiate a re-establishment procedure.
  • the tenth timer can be started when the terminal device receives the first RRC message in step 810, it can also be started when the terminal device receives the third RRC message in step 820, or it can be determined by the terminal device.
  • the duration of the tenth timer may be predefined, such as predefined by the protocol, or the first RRC message may contain related information about the tenth timer, such as the effective duration of the tenth timer, or the third The RRC message may contain related information of the tenth timer, such as the effective duration of the tenth timer. This application does not limit this.
  • the above steps 830 to 870 can be replaced with some or all of the steps 220 to 290 in the above method 200, or can also be replaced with some or all of the steps 420 to 470 in the above method 400 Or, alternatively, it can be replaced by some or all of the steps in step 620 to step 660 in the above method 600, or alternatively, it can also be replaced by the steps performed in other implementation manners listed in the above methods 200 to 700.
  • the terminal device may discard the second RRC message, and continue to perform the process performed before receiving the second RRC message. For example, if a terminal device receives a second RRC message when executing a step in the above method 200, method 400, or method 600, but the integrity protection check of the second RRC message fails, the terminal device may continue to perform the received Steps performed before the second RRC message.
  • the terminal device may discard the received second RRC message, and continue to perform step 440 and subsequent steps. Process.
  • the terminal device before receiving the second RRC message, the terminal device is performing step 440 in the above method 400, that is, before receiving the second RRC message, the terminal device has determined the target cell (that is, the first cell ), is trying to switch to the target cell. The terminal device may discard the received second RRC message, and continue to perform step 440 and subsequent procedures.
  • the terminal device when the terminal device receives the second RRC message but fails the integrity protection check of the second RRC message, it does not immediately initiate the RRC re-establishment process, but preferentially considers handover.
  • the terminal device can determine the target cell in different ways and try to switch to the target cell, or it can continue to perform the current operation. Therefore, the delay and complexity caused by the re-establishment process can be avoided to a large extent, and the impact of a long communication interruption on the user experience can be avoided, which is beneficial to improving system reliability, ensuring system performance, and improving user experience.
  • the terminal device can finally access a cell through handover or re-establishment, and resume normal communication.
  • the communication method provided by the embodiments of the present application will be described below from the perspective of device interaction with reference to the accompanying drawings.
  • FIG. 9 is a schematic flowchart of a communication method 900 provided by still another embodiment of the present application. As shown in FIG. 9, the method 900 may include step 910 to step 950. The steps in the method 900 are described in detail below.
  • the terminal device receives a first RRC message, the first RRC message including CHO configuration information of one or more candidate cells.
  • the first RRC message may be sent by the source network device, for example.
  • step 910 please refer to the detailed description of step 210 in the method 200 above. For the sake of brevity, it will not be repeated here.
  • step 920 the terminal device accesses a certain cell through handover or re-establishment, for example, denoted as the sixth cell.
  • Step 920 may be implemented, for example, by executing the method provided in any one of the above method 200, method 400, method 600, and method 800. Therefore, the sixth cell may be, for example, the target cell described in method 200, method 400, method 600, or method 800, or it may be the target cell described in method 200, method 400, method 600, or method 800 through a re-establishment process. Re-establish the cell. This application does not limit this. Since the specific operation flow of the terminal device has been described in detail above in conjunction with the various embodiments, for the sake of brevity, it will not be repeated here.
  • the network device to which the sixth cell belongs may be recorded as the first network device, for example.
  • the first network device may be a network device to which the target cell belongs, or a network device to which the re-established cell belongs, depending on whether the cell accessed by the terminal device is the target cell or the re-established cell.
  • the method further includes step 930, receiving a third RRC message, where the third RRC message is used to reconfigure the candidate cell.
  • the third RRC message may also be sent by the source network device, for example.
  • step 920 may be implemented, for example, by executing the method provided in any one of the above method 300, method 500, or method 700.
  • the fourth cell may be, for example, the target cell described in method 300, method 500, or method 700, or may also be a re-established cell accessed through a re-establishment procedure in method 300, method 500, or method 700. This application does not limit this. Since the specific operation flow of the terminal device has been described in detail above in conjunction with the various embodiments, for the sake of brevity, it will not be repeated here.
  • step 940 the terminal device sends access failure information.
  • the source network device sends the first RRC message to the terminal device without sending the third RRC message, or, in another case, the source network device sends the first RRC message and the third RRC message to the terminal device, but The integrity check of the third RRC message by the terminal device fails.
  • the terminal device may be able to determine the candidate cell that has not successfully accessed. For the convenience of distinction and description, for example, it is recorded as the seventh cell.
  • the seventh cell may refer to a candidate cell that is configured by the source network device (for example, configured by the first RRC message) but has not been successfully handed over, or may be configured by the source network device (for example, configured by the first RRC message) but CHO
  • the configuration information cannot be complied with for example, the CHO execution condition cannot be complied with and/or the parameter corresponding to the candidate cell cannot be complied with
  • the access failure information includes, for example, related information of the seventh cell.
  • related information of the seventh cell includes one or more of the following: the cell identity of the seventh cell (such as CGI, PCI, etc.), the frequency information of the seventh cell (such as the absolute frequency of the SSB, the absolute frequency position of the reference resource block, etc.), and the seventh cell Measurement identification, etc.
  • the terminal device receives the first RRC message and the third RRC message, and successfully parses the information in the third RRC message, the terminal device may be able to determine the candidate cell that has not successfully accessed. If the candidate cell that is not successfully accessed is still recorded as the seventh cell, the seventh cell may refer to a cell configured through the third RRC message, or through the first RRC message and the third RRC message but not successfully accessed.
  • the source network device such as the third RRC message configuration, or the first RRC message and the third RRC message configuration
  • the CHO configuration information cannot be complied with
  • the number of the seventh cell is not necessarily one. For the sake of brevity, I will not list them all here.
  • the seventh cell is a cell.
  • the network device to which the seventh cell belongs is, for example, recorded as the second network device. It can be understood that when there are multiple seventh cells, the network equipment to which each seventh cell belongs may be the same network equipment or different network equipment, which is not limited in this application.
  • step 940 may include: step 9401, the terminal device sends the access failure information to the first network device; step 9402, the first network device forwards the access failure information to the source network device; step 9403 , The source network device forwards the access instruction information to the second network device.
  • step 940 may include: 9404, the terminal device may send the access failure information to the source network device; step 9405, the source network device may forward the access failure information to the second network device.
  • the second network device may be a network device to which the seventh cell belongs.
  • the terminal device may send the access failure information based on a request from a network device (such as any one of the aforementioned first network device, second network device, or source network device or other network devices).
  • a network device such as any one of the aforementioned first network device, second network device, or source network device or other network devices.
  • the figure shows the process of steps 9401-9403 that the terminal device sends the access failure information to the second network device through the first network device and the source network device, and steps 9404-9405 the terminal device sends the access failure information to the second network device through the source network device.
  • steps 9404-9405 the terminal device sends the access failure information to the second network device through the source network device.
  • steps 9304-9405 are shown in dashed lines. It should be understood that the steps shown in the figure are only examples, and do not represent all the steps shown in the figure performed by the terminal device. In addition, this application does not limit the specific manner in which the terminal device sends the access failure information to the second network device.
  • step 950 the second network device adjusts the CHO configuration information according to the access failure information.
  • the second network device can make adjustments to the CHO configuration information.
  • the second network device may provide the adjusted CHO configuration information to the terminal device in order to obtain a higher handover success rate.
  • the terminal device can report the candidate cells whose CHO configuration information cannot be complied with and the candidate cells whose handover fails to the network equipment to which these candidate cells belong through handover failure information, so as to adjust the CHO configuration information, which can be beneficial to the following When it is determined as a candidate cell once, a higher handover success rate is obtained. Therefore, on the whole, system reliability can be improved and system performance guaranteed.
  • the size of the sequence number of each process does not mean the order of execution.
  • the execution order of each process should be determined by its function and internal logic, and should not constitute any implementation process of the embodiments of this application. limited.
  • FIG. 10 is a schematic block diagram of a communication device 10 provided by an embodiment of the present application. As shown in FIG. 10, the communication device 10 may include a processing unit 11 and a transceiving unit 12.
  • the communication device 10 can implement the operations corresponding to the terminal device in the above method embodiment.
  • the communication device may be a terminal device, or a component configured in the terminal device, such as a chip or Circuit.
  • the terminal device 10 can implement the corresponding operations of the terminal device in the method embodiments shown in FIG. 2 to FIG. 9.
  • the communication device 10 may include a unit for executing the method executed by the terminal device in the method embodiments shown in FIG. 2 to FIG. 9.
  • each unit in the communication device 10 and other operations and/or functions described above are used to implement the corresponding processes in the method embodiments shown in FIGS. 2 to 9 respectively.
  • the transceiver unit 12 may be used to receive a first radio resource control RRC message, the first RRC message including conditional handover CHO configuration information of one or more candidate cells, and
  • the CHO configuration information includes CHO execution conditions and parameters corresponding to each candidate cell; the processing unit 11 can be used to determine the CHO configuration information when the CHO configuration information of some candidate cells among the one or more candidate cells cannot be complied with. Whether there is a cell that satisfies the CHO execution condition among the candidate cells that can be followed.
  • the processing unit 11 is further configured to try to switch to the cell that meets the CHO execution condition if there is the cell that meets the CHO execution condition among the candidate cells for which the CHO configuration information can be complied with.
  • the processing unit 11 is further configured to: if the cell that satisfies the CHO execution condition does not exist among the candidate cells for which the CHO configuration information can be complied with, or if the attempt to switch to the process that satisfies the CHO execution condition fails , Initiate the re-establishment process.
  • the transceiver unit 12 is further configured to receive a second RRC message, but the integrity protection check of the second RRC message fails, and the second RRC message is after receiving the first RRC message
  • the processing unit 11 is also used to determine a cell that satisfies the S criterion; and is used to try to switch to all the cells if the cell that satisfies the S criterion is included in the candidate cell to which the CHO configuration information can be complied with Describe the cell that meets the S criterion.
  • the transceiver unit 12 may be configured to receive a first radio resource control RRC message, the first RRC message including conditional handover CHO configuration information of one or more candidate cells, and the one or more candidate cells
  • the CHO configuration information includes CHO execution conditions and parameters corresponding to each candidate cell; the processing unit 11 can be used to determine that S is satisfied when the CHO configuration information of some candidate cells among the one or more candidate cells cannot be complied with.
  • the first cell of the criterion and can be used to determine whether the first cell is included in a candidate cell for which the CHO configuration information can be complied with.
  • the processing unit 11 is further configured to, if the first cell is included in the candidate cells to which the CHO configuration information can be complied with, try to switch to the first cell.
  • the processing unit 11 is further configured to, if the first cell is not included in the candidate cell for which the CHO configuration information can be complied with, or if the process of attempting to handover to the first cell fails, initiate a restart Establish a process.
  • the receiving unit 12 is further configured to receive a second RRC message, but the integrity protection check of the second RRC message fails, and the second RRC message is after receiving the first RRC message The received message; the processing unit 11 is further configured to determine a cell that satisfies the S criterion; and is configured to try to switch to a case where the cell that satisfies the S criterion is included in a candidate cell to which the CHO configuration information can be complied with The cell that satisfies the S criterion.
  • the receiving unit 12 may be configured to receive a first radio resource control RRC message, the first RRC message including conditional handover CHO configuration information of one or more candidate cells, and
  • the CHO configuration information includes CHO execution conditions and parameters corresponding to each candidate cell;
  • the processing unit 11 may be used to determine the one or more candidate cells when the CHO execution conditions of some of the one or more candidate cells cannot be complied with.
  • the processing unit 11 is further configured to, if there is a cell that can be complied with the parameter corresponding to the CHO configuration information in the at least one first candidate cell, try to switch to the parameter corresponding to the CHO configuration information.
  • the cell to be complied with is further configured to, if there is a cell that can be complied with the parameter corresponding to the CHO configuration information in the at least one first candidate cell, try to switch to the parameter corresponding to the CHO configuration information.
  • the cell to be complied with is further configured to, if there is a cell that can be complied with the parameter corresponding to the CHO configuration information in the at least one first candidate cell, try to switch to the parameter corresponding to the CHO configuration information. The cell to be complied with.
  • the processing unit 11 is further configured to: in the at least one first candidate cell, if there is no cell in which the parameter corresponding to the CHO configuration information can be complied with, or if it is attempted to switch to the CHO configuration information The process of the cell to which the corresponding parameter can be followed fails, and the re-establishment process is initiated.
  • the parameters corresponding to the candidate cell in the CHO configuration information include one or more of the following: the cell radio network temporary identifier C-RNTI allocated by the candidate cell to the terminal device, and the access candidate The random access channel RACH resource of the cell, the cell global identification CGI of the candidate cell, the physical cell identification PCI of the candidate cell, the absolute frequency of the synchronization signal block SSB corresponding to the candidate cell, the absolute frequency of the reference resource block, the frequency bandwidth list, and the subcarrier Interval SCS specific carrier list, physical layer configuration parameters of candidate cells, media access control MAC layer configuration parameters of candidate cells, radio link control RLC layer configuration parameters of candidate cells, packet data convergence layer protocol PDCP layer configuration parameters, services Data adaptation protocol SDAP layer configuration parameters, RRC layer configuration parameters, and bearer configuration information.
  • the cell radio network temporary identifier C-RNTI allocated by the candidate cell to the terminal device
  • the access candidate The random access channel RACH resource of the cell, the cell global identification CGI of the candidate cell, the physical cell identification PCI of the candidate cell
  • the transceiver unit 12 may be configured to receive a first radio resource control RRC message, the first RRC message including CHO configuration information of one or more candidate cells, and CHO configuration of the one or more candidate cells
  • the information includes CHO execution conditions and parameters corresponding to each candidate cell; and can be used to receive a third RRC message that includes the CHO configuration information of one or more candidate cells; the third RRC message is used to re- Configure candidate cells; the processing unit 11 may be configured to determine the candidate cells whose CHO configuration information can be complied with in the case that the CHO configuration information of some candidate cells cannot be complied with according to the first RRC message and the third RRC message Whether there is a cell that meets the execution conditions of CHO.
  • the processing unit 11 is further configured to, if the first cell is included in the candidate cells to which the CHO configuration information can be complied with, try to switch to the first cell.
  • the processing unit 11 is further configured to, if the first cell is not included in the candidate cell for which the CHO configuration information can be complied with, or if the process of attempting to handover to the first cell fails, initiate a restart Establish a process.
  • the transceiver unit 12 is further configured to receive a second RRC message, but the integrity protection check of the second RRC message fails, and the second RRC message is after receiving the first RRC message
  • the processing unit 11 is also used to determine a cell that satisfies the S criterion; and is used to try to switch to all the cells if the cell that satisfies the S criterion is included in the candidate cell to which the CHO configuration information can be complied with Describe the cell that meets the S criterion.
  • the transceiver unit 12 may be configured to receive a first radio resource control RRC message, the first RRC message including the CHO configuration information of one or more candidate cells, and the CHO configuration of the one or more candidate cells
  • the information includes CHO execution conditions and parameters corresponding to each candidate cell; and can be used to receive a third RRC message that includes the CHO configuration information of one or more candidate cells; the third RRC message is used to re- Configure candidate cells;
  • the processing unit 11 may be configured to determine the candidate cells whose CHO configuration information can be complied with in the case that the CHO configuration information of some candidate cells cannot be complied with according to the first RRC message and the third RRC message Whether there is a cell that meets the execution conditions of CHO.
  • the processing unit 11 is further configured to try to switch to the cell that meets the CHO execution condition if there is the cell that meets the CHO execution condition among the candidate cells for which the CHO configuration information can be complied with.
  • the processing unit 11 is further configured to: if the cell that meets the CHO execution condition does not exist among the candidate cells to which the CHO configuration information can be followed, or if it tries to switch to the cell that meets the CHO execution condition The process fails, and the second cell that meets the S criterion is determined; and it is also used to try to switch to the second cell if the second cell is included in the candidate cells that can be complied with the CHO configuration information.
  • the processing unit 11 is further configured to: if the cell that meets the CHO execution condition does not exist among the candidate cells to which the CHO configuration information can be followed, or if it tries to switch to the cell that meets the CHO execution condition If the process fails, the second cell that meets the S criterion is determined; and it is also used to initiate a re-establishment process if the second cell is not included in the candidate cells for which the CHO configuration information can be complied with.
  • the processing unit 11 is further configured to: if the cell that meets the CHO execution condition does not exist among the candidate cells to which the CHO configuration information can be followed, or if it tries to switch to the cell that meets the CHO execution condition The process fails, and the re-establishment process is initiated.
  • the transceiver unit 12 may be configured to receive a first RRC message, where the first RRC message includes CHO configuration information of one or more candidate cells, and the CHO configuration information of one or more candidate cells includes CHO. Execution conditions and parameters corresponding to each candidate cell; and can be used to receive a third RRC message that includes the CHO configuration information of one or more candidate cells; the third RRC message is used to reconfigure candidate cells
  • the processing unit 11 may be configured to, in the case of not being able to comply with the CHO configuration information of part of the candidate cells in the one or more candidate cells, determine that there are at least one of the candidate cells for which the CHO execution condition can be complied with that satisfies the CHO execution condition A second candidate cell; and can be used to determine whether the at least one second candidate cell has a cell that can be complied with corresponding to the parameters in the CHO configuration information.
  • the processing unit 11 is further configured to, if there is a cell to which the parameter corresponding to the CHO configuration information can be complied with in the at least one second candidate cell, try to switch to the parameter corresponding to the CHO configuration information.
  • the cell to be complied with is further configured to, if there is a cell to which the parameter corresponding to the CHO configuration information can be complied with in the at least one second candidate cell, try to switch to the parameter corresponding to the CHO configuration information.
  • the cell to be complied with is further configured to, if there is a cell to which the parameter corresponding to the CHO configuration information can be complied with in the at least one second candidate cell.
  • the processing unit 11 is further configured to, if the at least one second candidate cell does not have a cell to which the parameter corresponding to the CHO configuration information can be complied with, or if the handover fails, initiate a re-establishment procedure.
  • the parameter corresponding to the candidate cell is determined by the CHO configuration information in the first RRC message and the CHO configuration information in the third RRC message, or by the third The CHO configuration information in the RRC message is determined;
  • the parameters corresponding to the candidate cell include: the cell radio network temporary identification C-RNTI allocated by the candidate cell to the terminal device, the random access channel RACH resource for accessing the candidate cell, and the candidate cell's Cell global identification CGI, physical cell identification PCI of the candidate cell, absolute frequency of the synchronization signal block SSB corresponding to the candidate cell, absolute frequency of the reference resource block, frequency bandwidth list, subcarrier spacing SCS specific carrier list, and physical layer of the candidate cell Configuration parameters, media access control MAC layer configuration parameters of candidate cells, radio link control RLC layer configuration parameters of candidate cells, packet data convergence layer protocol PDCP layer configuration parameters, service data adaptation protocol SDAP layer configuration parameters, and RRC layer Configuration parameters, and bearer configuration information.
  • the communication device 10 may further include a storage unit, the storage unit may be used to store instructions or data, and the processing unit may call the instructions or data stored in the storage unit to implement corresponding operations.
  • the transceiver unit 12 in the communication device 10 may be implemented by a transceiver or a communication interface, for example, may correspond to the transceiver 2020 in the terminal device 3000 shown in FIG. 11.
  • the processing unit 11 in the communication device 10 may be implemented by at least one processor, for example, may correspond to the processor 2010 in the terminal device 3000 shown in FIG. 11.
  • FIG. 11 is a schematic structural diagram of a terminal device 2000 provided by an embodiment of the present application.
  • the terminal device 2000 can be applied to the system shown in FIG. 1 to perform the functions of the terminal device in the foregoing method embodiment.
  • the terminal device 3000 includes a processor 2010 and a transceiver 2020.
  • the terminal device 3000 further includes a memory 2030.
  • the processor 2010, the transceiver 3002, and the memory 2030 can communicate with each other through an internal connection path to transfer control and/or data signals.
  • the memory 2030 is used for storing computer programs, and the processor 2010 is used for downloading from the memory 2030. Call and run the computer program to control the transceiver 2020 to send and receive signals.
  • the terminal device 3000 may further include an antenna 2040 for transmitting the uplink data or uplink control signaling output by the transceiver 2020 through a wireless signal.
  • the above-mentioned processor 2010 and the memory 2030 may be combined into a processing device, and the processor 2010 is configured to execute the program code stored in the memory 2030 to realize the above-mentioned functions.
  • the memory 2030 may also be integrated in the processor 2010 or independent of the processor 2010.
  • the processor 2010 may correspond to the processing unit 11 in FIG. 11.
  • the aforementioned transceiver 2020 may correspond to the transceiver unit 12 in FIG. 11.
  • the transceiver 2020 may include a receiver (or receiver, receiving circuit) and a transmitter (or transmitter, transmitting circuit). Among them, the receiver is used to receive signals, and the transmitter is used to transmit signals.
  • the terminal device 2000 shown in FIG. 11 can implement various processes involving the terminal device in the method embodiments shown in FIGS. 2 to 9.
  • the operations and/or functions of the various modules in the terminal device 2000 are respectively for implementing the corresponding processes in the foregoing method embodiments.
  • the above-mentioned processor 2010 can be used to execute the actions described in the previous method embodiments implemented by the terminal device, and the transceiver 2020 can be used to execute the terminal device described in the previous method embodiments to send to or receive from the network device. action.
  • the transceiver 2020 can be used to execute the terminal device described in the previous method embodiments to send to or receive from the network device. action.
  • the aforementioned terminal device 2000 may further include a power supply 2050 for providing power to various devices or circuits in the terminal device.
  • the terminal device 3000 may also include one or more of the input unit 2060, the display unit 2070, the audio circuit 2080, the camera 2090, and the sensor 2100.
  • the audio circuit may also include a speaker 2082, a microphone 2084, and so on.
  • FIG. 12 is a schematic structural diagram of a network device provided by an embodiment of the present application, and may be, for example, a schematic structural diagram of a base station.
  • the base station 3000 can be applied to the system shown in FIG. 1 to perform the functions of the network equipment in the foregoing method embodiment.
  • the base station 3000 may include one or more radio frequency units, such as a remote radio unit (RRU) 3100 and one or more baseband units (BBU) (also known as distributed unit (DU) )) 3300.
  • RRU 3100 may be called a transceiver unit, which corresponds to the transceiver unit 12 in FIG. 11.
  • the transceiver unit 3100 may also be called a transceiver, a transceiver circuit, or a transceiver, etc., and it may include at least one antenna 3101 and a radio frequency unit 3102.
  • the transceiver unit 3100 may include a receiving unit and a transmitting unit, the receiving unit may correspond to a receiver (or receiver, receiving circuit), and the transmitting unit may correspond to a transmitter (or transmitter or transmitting circuit).
  • the RRU 3100 part is mainly used for sending and receiving of radio frequency signals and conversion of radio frequency signals and baseband signals, for example, for sending instruction information to terminal equipment.
  • the 3300 part of the BBU is mainly used to perform baseband processing, control the base station, and so on.
  • the RRU 3100 and the BBU 3300 may be physically set together, or may be physically separated, that is, a distributed base station.
  • the BBU 3300 is the control center of the base station, and may also be called a processing unit, which may correspond to the processing unit 11 in FIG. 11, and is mainly used to complete baseband processing functions, such as channel coding, multiplexing, modulation, and spreading.
  • the BBU processing unit
  • the BBU may be used to control the base station to execute the operation procedure of the network device in the foregoing method embodiment, for example, to generate the foregoing indication information.
  • the BBU 3300 may be composed of one or more single boards, and multiple single boards may jointly support a wireless access network (such as an LTE network) of a single access standard, or can support different access standards. Wireless access network (such as LTE network, 5G network or other networks).
  • the BBU 3300 further includes a memory 3201 and a processor 3202.
  • the memory 3201 is used to store necessary instructions and data.
  • the processor 3202 is used to control the base station to perform necessary actions, for example, to control the base station to execute the operation flow of the network device in the above method embodiment.
  • the memory 3201 and the processor 3202 may serve one or more single boards. In other words, the memory and the processor can be set separately on each board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits can be provided on each board.
  • the base station 3000 shown in FIG. 12 can implement each process involving the target network device in the method embodiments shown in FIG. 2 to FIG. 9.
  • the operations and/or functions of the various modules in the base station 3000 are respectively for implementing the corresponding procedures in the foregoing method embodiments.
  • the above-mentioned BBU 3300 can be used to perform the actions described in the previous method embodiments implemented by the network device, and the RRU 3100 can be used to perform the actions described in the previous method embodiments that the network device sends to or receives from the terminal device.
  • the RRU 3100 can be used to perform the actions described in the previous method embodiments that the network device sends to or receives from the terminal device.
  • the base station 3000 shown in FIG. 12 is only a possible architecture of network equipment, and should not constitute any limitation to this application.
  • the method provided in this application can be applied to network devices of other architectures.
  • network equipment including CU, DU, and active antenna unit (AAU). This application does not limit the specific architecture of the network device.
  • An embodiment of the present application also provides a processing device, including a processor and an interface; the processor is configured to execute the method in any of the foregoing method embodiments.
  • the aforementioned processing device may be one or more chips.
  • the processing device may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), or It is a central processor unit (CPU), it can also be a network processor (NP), it can also be a digital signal processing circuit (digital signal processor, DSP), or it can be a microcontroller (microcontroller unit). , MCU), it can also be a programmable logic device (PLD) or other integrated chips.
  • FPGA field programmable gate array
  • ASIC application specific integrated circuit
  • SoC system on chip
  • CPU central processor unit
  • NP network processor
  • DSP digital signal processing circuit
  • microcontroller unit microcontroller unit
  • MCU programmable logic device
  • PLD programmable logic device
  • each step of the above method can be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.
  • the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components .
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • static random access memory static random access memory
  • dynamic RAM dynamic RAM
  • DRAM dynamic random access memory
  • synchronous dynamic random access memory synchronous DRAM, SDRAM
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous connection dynamic random access memory serial DRAM, SLDRAM
  • direct rambus RAM direct rambus RAM
  • the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code is run on a computer, the computer executes the steps shown in FIGS. 2 to 9 The method of any one of the embodiments is shown.
  • the present application also provides a computer-readable storage medium, the computer-readable storage medium stores a program code, and when the program code runs on a computer, the computer executes FIGS. 2 to The method executed by the terminal device in any one of the embodiments shown in 9.
  • the present application also provides a system, which includes the aforementioned one or more terminal devices and one or more network devices.
  • the network equipment in each of the above-mentioned device embodiments corresponds completely to the network equipment or terminal equipment in the terminal equipment and method embodiments, and the corresponding modules or units execute the corresponding steps.
  • the communication unit executes the receiving or the terminal equipment in the method embodiments.
  • the processing unit executes the functions of specific units, refer to the corresponding method embodiments. Among them, there may be one or more processors.
  • component used in this specification are used to denote computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution.
  • the component may be, but is not limited to, a process, a processor, an object, an executable file, an execution thread, a program, and/or a computer running on a processor.
  • the application running on the computing device and the computing device can be components.
  • One or more components may reside in processes and/or threads of execution, and components may be located on one computer and/or distributed among two or more computers.
  • these components can be executed from various computer readable media having various data structures stored thereon.
  • the component can be based on, for example, a signal having one or more data packets (e.g. data from two components interacting with another component in a local system, a distributed system, and/or a network, such as the Internet that interacts with other systems through a signal) Communicate through local and/or remote processes.
  • a signal having one or more data packets (e.g. data from two components interacting with another component in a local system, a distributed system, and/or a network, such as the Internet that interacts with other systems through a signal) Communicate through local and/or remote processes.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • each functional unit may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software When implemented by software, it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions (programs).
  • programs When the computer program instructions (programs) are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server, or data center via 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 data center integrated with one or more available media.
  • the usable medium may be a magnetic medium, (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state disk, SSD)) etc.
  • a magnetic medium for example, a floppy disk, a hard disk, and a magnetic tape
  • an optical medium for example, a high-density digital video disc (digital video disc, DVD)
  • a semiconductor medium for example, a solid state disk, SSD
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disks or optical disks and other media that can store program codes. .

Landscapes

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

Abstract

本申请提供了一种通信方法和通信装置。该方法包括：终端设备接收RRC消息，该RRC消息包括一个或多个候选小区的CHO配置信息，在不遵从该一个或多个候选小区中部分候选小区的CHO配置信息的情况下，暂不发起重建立流程，而是优先考虑从CHO配置信息能够被遵从的部分候选小区中确定满足CHO执行条件的小区，并尝试切换至该小区。在从CHO配合信息能够被遵从的部分候选小区中未确定出满足CHO执行条件的小区或切换失败的情况下，才发起重建立流程。从而可以尽可能地避免重建立流程带来的较大时延和复杂度。有利于提高系统可靠性，保证系统性能，有利于提高用户体验。

Description

通信方法和通信装置 技术领域
本申请涉及无线通信领域，并且更具体地，涉及一种无线通信领域中的通信方法和通信装置。
背景技术
在传统的切换流程中，网络设备可以向终端设备发送切换消息，以指示可以切换的目标小区，以及与切换和后续通信相关的配置信息。终端设备在接收到该切换消息后，可以先评估是否能够遵从(或者说，遵循，comply with)该切换消息中的配置信息。在确定能够遵从的情况下，终端设备可以执行后续的切换流程，如，与目标小区进行随机接入流程等。而在确定不能够遵从的情况下，终端设备可以发起重建立流程。
然而，某些通信系统中，比如长期演进(long term evolution，LTE)或第五代(the 5 th generation，5G)通信系统中，由于信道质量的快速衰减、或终端设备的高速移动等原因，切换消息可能会发送失败，进而导致切换失败。
目前，已知一种方法，网络设备可以为终端设备配置一个或多个候选小区，并为各候选小区提供切换的执行条件(或者说，触发条件)。终端设备可以在某一候选小区的切换的执行条件被满足的情况下，尝试切换到该候选小区。这种切换机制可以称为条件切换(conditional handover，CHO)，与之对应的执行条件可以称为CHO执行条件。此外，网络设备还可以向终端设备指示与上述一个或多个候选小区对应的参数，以便终端设备切换至某一候选小区，并能够在该候选小区中正常通信。然而，终端设备并不一定能够遵从网络设备所配置的所有候选小区的CHO执行条件以及参数。因此在终端设备不能够遵从网络设备所配置的部分候选小区的CHO执行条件和/或参数的情况下，终端设备该如何处理是一项亟待解决的技术问题。
发明内容
本申请提供一种通信方法和通信装置，以期在终端设备不能够遵从部分候选小区的CHO执行条件和/或参数的情况下，为终端设备提供合理的操作流程，尽可能地减少切换带来的通信中断时长，从而提高用户体验。
第一方面，提供了一种通信方法，该方法包括：接收第一无线资源控制无线资源控制(radio resource control，RRC)消息，所述第一RRC消息包括一个或多个候选小区的条件切换CHO配置信息，所述一个或多个候选小区的CHO配置信息包括CHO执行条件以及与各候选小区对应的参数；在不能够遵从所述一个或多个候选小区中的部分候选小区的CHO配置信息的情况下，确定CHO配置信息能够被遵从的候选小区中是否存在满足CHO执行条件的小区。
基于上述技术方案，终端设备可以在确定不能够遵从部分候选小区的CHO配置信息 的情况下，不发起重建立流程，而是优先尝试切换。终端设备可以在CHO配置信息能够被遵从的那部分候选小区中尝试寻找一个满足CHO执行条件的小区，并尝试切换到该小区。因此，可以避免重建立流程造成的时延、复杂度，避免较长时间的通信中断对用户体验的影响，有利于提高系统可靠性，保证系统性能，有利于提高用户体验。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：若所述CHO配置信息能够被遵从的候选小区中存在所述满足CHO执行条件的小区，尝试切换至所述满足CHO执行条件的小区。
即，终端设备可以从CHO配置信息能够被遵从的候选小区中找出满足CHO执行条件的小区，以尝试切换至该小区。终端设备可以对该步骤执行一次，比如通过一次切换流程就成功切换，或者，通过一次切换流程未成功切换，但不再执行该步骤；或者，终端设备对该步骤也可以执行多次，比如通过多次切换流程成功接入某一小区，或者，通过多次切换流程均未成功切换，则不再执行该步骤。本申请对此不作限定。
结合第一方面，在第一方面的某些实现方式中,所述方法还包括：若所述CHO配置信息能够被遵从的候选小区中不存在所述满足CHO执行条件的小区，或，若尝试切换至所述满足CHO执行条件的小区的流程失败，发起重建立流程。
即，如果网络设备通过第一RRC消息配置的所有候选小区都不满足CHO执行条件，或，若终端设备确定尝试切换的流程失败，比如一次或多次尝试切换的流程失败，则终端设备可以发起重建立流程。
第二方面，提供了一种通信方法，该方法包括：接收第一RRC消息，所述第一RRC消息包括一个或多个候选小区的条件切换CHO配置信息，所述一个或多个候选小区的CHO配置信息包括CHO执行条件以及与各候选小区对应的参数；在不能够遵从所述一个或多个候选小区中的部分候选小区的CHO配置信息的情况下，确定满足S准则的第一小区；确定所述第一小区是否包含在CHO配置信息能够被遵从的候选小区中。
基于上述技术方案，终端设备可以在确定不能够遵从部分候选小区的CHO配置信息的情况下，不发起重建立流程，而是优先尝试切换。终端设备可以通过小区选择，确定一个满足S准则的小区，因此可以从更多的维度来寻找适合切换的小区。由此可以避免重建立流程造成的时延、复杂度，避免较长时间的通信中断对用户体验的影响，有利于提高系统可靠性，保证系统性能，有利于提高用户体验。
结合第二方面，在第二方面的某些实现方式中，所述方法还包括：若所述第一小区包含在所述CHO配置信息能够被遵从的候选小区中，尝试切换至所述第一小区。
即，终端设备可以在上述确定的满足S准则的小区包含在CHO配置信息能够被遵从的候选小区的情况下，尝试切换至该小区。终端设备可以对该步骤执行一次，比如通过一次切换流程就成功切换，或者，通过一次切换流程未成功切换，但不再执行该步骤，或者没有再找到其他满足S准则的小区包含在CHO配置信息能够被遵从的候选小区中；或者，终端设备对该步骤也可以执行多次，比如通过多次切换流程成功接入某一小区，或者，通过多次切换流程均未成功切换，则不再执行该步骤。
结合第二方面，在第二方面的某些实现方式中，所述方法还包括：若所述第一小区不包含在所述CHO配置信息能够被遵从的候选小区中，或，若尝试切换至所述第一小区的流程失败，发起重建立流程。
即，终端设备可以在上述确定的满足S准则的小区不包含在CHO配置信息能够被遵从的候选小区的情况下，或者，未成功切换到第一小区的情况下，发起重建立流程。
第三方面，提供了一种通信方法，该方法包括：接收第一RRC消息，所述第一RRC消息包括一个或多个候选小区的条件切换CHO配置信息，所述一个或多个候选小区的CHO配置信息包括CHO执行条件以及各候选小区对应的参数；在不能够遵从所述一个或多个候选小区中的部分候选小区的CHO执行条件的情况下，确定所述一个或多个候选小区中CHO执行条件能够被遵从的部分候选小区中存在满足CHO执行条件的至少一个第一候选小区；确定至少一个第一候选小区中是否存在CHO配置信息中所对应的参数能够被遵从的小区。
基于上述技术方案，终端设备可以在确定出不能够遵从部分候选小区的CHO执行条件的情况下，不发起重建立流程，而是优先尝试切换。终端设备可以从CHO执行条件被遵从的候选小区中确定出满足CHO执行条件的小区，进而再从确定出的满足CHO执行条件的小区中确定出CHO配置信息中所对应的参数能够被遵从的小区，以尝试切换。因此，可以避免重建立流程造成的时延、复杂度，避免较长时间的通信中断对用户体验的影响，有利于提高系统可靠性，保证系统性能，有利于提高用户体验。
另一方面，由于终端设备在接收到第一RRC消息后仅需评估是否能够各候选小区的CHO执行条件，在确定出满足CHO执行条件的小区之后，评估这些小区的CHO配置信息中的参数是否能够被遵从，可以减小评估的候选小区的数量，减小终端设备的工作量，降低实现复杂度。
结合第三方面，在第三方面的某些实现方式中，所述方法还包括：若所述至少一个第一候选小区中存在CHO配置信息中所对应的参数能够被遵从的小区，尝试切换至所述CHO配置信息中所对应的参数能够被遵从的小区。
即，终端设备可以从满足CHO执行条件的小区中找出所对应的参数能够被遵从的小区，以尝试切换。终端设备可以对该步骤执行一次，比如通过一次切换流程就成功切换，或者，通过一次切换流程未成功切换，但不再执行该步骤；或者，终端设备对该步骤也可以执行多次，比如通过多次切换流程成功接入某一小区，或者，通过多次切换流程均未成功切换，则不再执行该步骤。本申请对此不作限定。
结合第三方面，在第三方面的某些实现方式中，所述方法还包括：在若所述至少一个第一候选小区中不存在CHO配置信息中所对应的参数能够被遵从的小区，或，若尝试切换至所述CHO配置信息中所对应的参数能够被遵从的小区的流程失败，发起重建立流程。
即，如果网络设备通过第一RRC消息配置的所有满足CHO执行条件的小区的参数都不能被遵从，或，若终端设备确定尝试切换的流程失败，比如一次或多次尝试切换的流程失败，则终端设备可以发起重建立流程。
结合第一方面至第三方面中的任意一个方面，在某些实现方式中，所述方法还包括：接收第二RRC消息，但对所述第二RRC消息的完整性保护校验失败，所述第二RRC消息是在接收到所述第一RRC消息之后接收到的消息；确定满足S准则的小区；在所述满足S准则的小区包含在所述CHO配置信息能够被遵从的候选小区中的情况下，尝试切换至所述满足S准则的小区。
因此，终端设备可以在接收到第二RRC消息但完整性保护校验失败的情况下，忽略 该第二RRC消息，继续尝试切换流程。在一种实现方式中，终端设备可以通过小区选择选择满足S准则的小区，并在该小区包含在CHO配置信息能够被遵从的候选小区中时，尝试切换。终端设备可以对该步骤执行一次，也可以执行多次，本申请对此不做限定。由此，终端设备可以更大几率地切换到某一候选小区中，而较大程度地避免重建立流程的执行。
结合第一方面至第三方面中的任意一个方面，在某些实现方式中，所述CHO配置信息中与候选小区对应的参数包括以下一项或多项：候选小区为终端设备分配的小区无线网络临时标识C-RNTI、接入候选小区的随机接入信道RACH资源、候选小区的小区全球标识CGI、候选小区的物理小区标识PCI、候选小区对应的同步信号块SSB的绝对频率、参考资源块的绝对频率、频率带宽列表、子载波间隔SCS特定的载波列表、候选小区的物理层配置参数、候选小区的媒体接入控制MAC层配置参数、候选小区的无线链路控制RLC层配置参数、分组数据汇聚层协议PDCP层配置参数、业务数据自适应协议SDAP层配置参数、RRC层配置参数、以及承载配置信息。
第四方面，提供了一种通信方法，该方法包括：接收第一RRC消息，所述第一RRC消息包括一个或多个候选小区的CHO配置信息，所述一个或多个候选小区的CHO配置信息包括CHO执行条件以及与各候选小区对应的参数；接收第三RRC消息，所述第三RRC消息包括一个或多个候选小区的CHO配置信息；所述第三RRC消息中的一个或多个候选小区的CHO配置信息用于对所述第一RRC消息中的一个或多个候选小区的CHO配置信息进行更新；根据所述第一RRC消息和所述第三RRC消息，在不能够遵从部分候选小区的CHO配置信息的情况下，确定CHO配置信息能够被遵从的候选小区中是否存在满足CHO执行条件的小区。
基于上述技术方案，终端设备可以基于接收到的第三RRC消息进行候选小区的重新配置/更新。终端设备可以在确定不能够遵从部分候选小区的CHO配置信息的情况下，不发起重建立流程，而是优先尝试切换。终端设备可以在CHO配置信息能够被遵从的那部分候选小区中尝试寻找一个满足CHO执行条件的小区，并尝试切换到该小区。因此，可以避免重建立流程造成的时延、复杂度，避免较长时间的通信中断对用户体验的影响，有利于提高系统可靠性，保证系统性能，有利于提高用户体验。
应理解，所述CHO配置信息可以是基于第三RRC消息重新配置候选小区后所得到的CHO配置信息，例如可以是根据第一RRC和第三RRC消息共同确定的CHO配置信息，也可以是根据第三RRC消息确定的CHO配置信息。所述CHO执行条件可以是重新配置候选小区后所得到的CHO配置信息中的CHO执行条件。
结合第四方面，在第四方面的某些实现方式中，所述方法还包括：若所述CHO配置信息能够被遵从的候选小区中存在所述满足CHO执行条件的小区，尝试切换至所述满足CHO执行条件的小区。
即，终端设备可以从CHO配置信息能够被遵从的候选小区中找出满足CHO执行条件的小区，以尝试切换至该小区。终端设备可以对该步骤执行一次，比如通过一次切换流程就成功切换，或者，通过一次切换流程未成功切换，但不再执行该步骤；或者，终端设备对该步骤也可以执行多次，比如通过多次切换流程成功接入某一小区，或者，通过多次切换流程均未成功切换，则不再执行该步骤。本申请对此不作限定。
结合第四方面，在第四方面的某些实现方式中，所述方法还包括：若所述CHO配置信息能够被遵从的候选小区中不存在所述满足CHO执行条件的小区，或，若尝试切换至所述满足CHO执行条件的小区的流程失败，确定满足S准则的第二小区；若所述第二小区包含在所述CHO配置信息能够被遵从的候选小区中，尝试切换至所述第二小区。
即，如果网络设备通过第一RRC消息配置的所有候选小区都不满足CHO执行条件，或，若终端设备确定尝试切换的流程失败，比如一次或多次尝试切换的流程失败，则终端设备可以执行小区选择，以寻找适合切换的小区。若终端设备通过小区选择确定的小区包含在CHO配置信息能够被遵从的候选小区中，则可以尝试切换至该小区。
结合第四方面，在第四方面的某些实现方式中，所述方法还包括：若所述CHO配置信息能够被遵从的候选小区中不存在所述满足CHO执行条件的小区，或，若尝试切换至所述满足CHO执行条件的小区的流程失败，确定满足S准则的第二小区；若所述第二小区不包含在所述CHO配置信息能够被遵从的候选小区中，发起重建立流程。
即，如果网络设备通过第一RRC消息配置的所有候选小区都不满足CHO执行条件，或，若终端设备确定尝试切换的流程失败，比如一次或多次尝试切换的流程失败，则终端设备可以执行小区选择，以寻找适合切换的小区。若终端设备通过小区选择确定的小区不包含在CHO配置信息能够被遵从的候选小区中，则可以发起重建立流程。
结合第四方面，在第四方面的某些实现方式中，所述方法还包括：若所述CHO配置信息能够被遵从的候选小区中不存在所述满足CHO执行条件的小区，或，若尝试切换至所述满足CHO执行条件的小区的流程失败，发起重建立流程。
即，如果网络设备通过第一RRC消息配置的所有候选小区都不满足CHO执行条件，或，若终端设备确定尝试切换的流程失败，比如一次或多次尝试切换的流程失败，则终端设备可以发起重建立流程。
第五方面，提供了一种通信方法，该方法包括：接收第一RRC消息，所述第一RRC消息包括一个或多个候选小区的CHO配置信息，所述一个或多个候选小区的CHO配置信息包括CHO执行条件以及与各候选小区对应的参数；接收第三RRC消息，所述第三RRC消息包括一个或多个候选小区的CHO配置信息；所述第三RRC消息中的一个或多个候选小区的CHO配置信息用于对所述第一RRC消息中的一个或多个候选小区的CHO配置信息进行更新；根据所述第一RRC消息和所述第三RRC消息，在不能够遵从部分候选小区的CHO配置信息的情况下，确定满足S准则的第三小区；确定所述第三小区是否包含在CHO配置信息能够被遵从的候选小区中。
基于上述技术方案，终端设备可以基于接收到的第三RRC消息进行候选小区的重新配置/更新。终端设备可以在确定不能够遵从部分候选小区的CHO配置信息的情况下，不发起重建立流程，而是优先尝试切换。终端设备可以通过小区选择，确定一个满足S准则的小区，因此可以从更多的维度来寻找适合切换的小区。由此可以避免重建立流程造成的时延、复杂度，避免较长时间的通信中断对用户体验的影响，有利于提高系统可靠性，保证系统性能，有利于提高用户体验。
应理解，所述CHO配置信息可以是基于第三RRC消息重新配置候选小区后所得到的CHO配置信息，例如可以是根据第一RRC和第三RRC消息共同确定的CHO配置信息，也可以是根据第三RRC消息确定的CHO配置信息。
结合第五方面，在第五方面的某些实现方式中，所述方法还包括：若所述第三小区包含在所述CHO配置信息能够被遵从的候选小区中，尝试切换至所述第三小区。
即，终端设备可以在上述确定的满足S准则的小区包含在CHO配置信息能够被遵从的候选小区的情况下，尝试切换至该小区。终端设备可以对该步骤执行一次，比如通过一次切换流程就成功切换，或者，通过一次切换流程未成功切换，但不再执行该步骤，或者没有再找到其他满足S准则的小区包含在CHO配置信息能够被遵从的候选小区中；或者，终端设备对该步骤也可以执行多次，比如通过多次切换流程成功接入某一小区，或者，通过多次切换流程均未成功切换，则不再执行该步骤。
结合第五方面，在第五方面的某些实现方式中，所述方法还包括：若所述第三小区不包含在所述CHO配置信息能够被遵从的候选小区中，或，若尝试切换至所述第三小区的流程失败，发起重建立流程。
即，终端设备可以在上述确定的满足S准则的小区不包含在CHO配置信息能够被遵从的候选小区的情况下，或者，未成功切换到第一小区的情况下，发起重建立流程。
第六方面，提供了一种通信方法，该方法包括：接收第一无线资源控制RRC消息，所述第一RRC消息包括一个或多个候选小区的条件切换CHO配置信息，所述一个或多个候选小区的CHO配置信息包括CHO执行条件以及各候选小区对应的参数；接收第三RRC消息，所述第三RRC消息包括一个或多个候选小区的CHO配置信息；所述第三RRC消息中的一个或多个候选小区的CHO配置信息用于对所述第一RRC消息中的一个或多个候选小区的CHO配置信息进行更新；在不能够遵从所述一个或多个候选小区中的部分候选小区的CHO配置信息的情况下，确定CHO执行条件能够被遵从的候选小区中存在满足CHO执行条件的至少一个第二候选小区；确定所述至少一个第二候选小区中是否存在CHO配置信息中所对应的参数能够被遵从的小区。
基于上述技术方案，终端设备可以基于接收到的第三RRC消息进行候选小区的重新配置/更新。终端设备可以在确定出不能够遵从部分候选小区的CHO执行条件的情况下，不发起重建立流程，而是优先尝试切换。终端设备可以从CHO执行条件被遵从的候选小区中确定出满足CHO执行条件的小区，进而再从确定出的满足CHO执行条件的小区中确定出CHO配置信息中所对应的参数能够被遵从的小区，以尝试切换。因此，可以避免重建立流程造成的时延、复杂度，避免较长时间的通信中断对用户体验的影响，有利于提高系统可靠性，保证系统性能，有利于提高用户体验。
另一方面，由于终端设备在接收到第一RRC消息和第三RRC消息后，仅需评估是否能够各候选小区的CHO执行条件，在确定出满足CHO执行条件的小区之后，评估这些小区的CHO配置信息中的参数是否能够被遵从，可以减小评估的候选小区的数量，减小终端设备的工作量，降低实现复杂度。
应理解，所述CHO配置信息可以是基于第三RRC消息重新配置候选小区后所得到的CHO配置信息，例如可以是根据第一RRC和第三RRC消息共同确定的CHO配置信息，也可以是根据第三RRC消息确定的CHO配置信息。所述CHO执行条件可以是重新配置候选小区后所得到的CHO配置信息中的CHO执行条件。
结合第六方面，在第六方面的某些实现方式中，所述方法还包括：若所述至少一个第二候选小区中存在CHO配置信息中所对应的参数能够被遵从的小区，尝试切换至所述 CHO配置信息中所对应的参数能够被遵从的小区。
即，终端设备可以从满足CHO执行条件的小区中找出所对应的参数能够被遵从的小区，以尝试切换。终端设备可以对该步骤执行一次，比如通过一次切换流程就成功切换，或者，通过一次切换流程未成功切换，但不再执行该步骤；或者，终端设备对该步骤也可以执行多次，比如通过多次切换流程成功接入某一小区，或者，通过多次切换流程均未成功切换，则不再执行该步骤。本申请对此不作限定。
结合第六方面，在第六方面的某些实现方式中，所述方法还包括：若所述至少一个第四候选小区中不存在CHO配置信息中所对应的参数能够被遵从的小区，或，若切换失败，发起重建立流程。
即，如果网络设备通过第一RRC和第三RRC消息或通过第三RRC消息配置的所有满足CHO执行条件的小区的参数都不能被遵从，或，若终端设备确定尝试切换的流程失败，比如一次或多次尝试切换的流程失败，则终端设备可以发起重建立流程。
结合第四方面至第六方面中的任意一个方面，在某些实现方式中，所述与候选小区对应的参数由所述第一RRC消息中的CHO配置信息和第三RRC消息中的CHO配置信息确定，或，由所述第三RRC消息中的CHO配置信息确定；所述与候选小区对应的参数包括：候选小区为终端设备分配的小区无线网络临时标识C-RNTI、接入候选小区的随机接入信道RACH资源、候选小区的小区全球标识CGI、候选小区的物理小区标识PCI、候选小区对应的同步信号块SSB的绝对频率、参考资源块的绝对频率、频率带宽列表、子载波间隔SCS特定的载波列表、候选小区的物理层配置参数、候选小区的媒体接入控制MAC层配置参数、候选小区的无线链路控制RLC层配置参数、分组数据汇聚层协议PDCP层配置参数、业务数据自适应协议SDAP层配置参数、RRC层配置参数、以及承载配置信息等。
应理解，上述各方面所述的方法均可以由终端设备执行，或者，也可以由配置在终端设备中的部件(例如芯片或电路)执行。本申请对此不作限定。
第七方面，提供了一种通信装置，包括用于执行第一方面至第六方面任一种可能实现方式中的方法的各个模块或单元。
第八方面，提供了一种通信装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令或者数据，以实现上述第一方面至第六方面任一种可能实现方式中的方法。可选地，该通信装置还包括存储器。可选地，该通信装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该通信装置为终端设备。当该通信装置为终端设备时，所述通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该通信装置为配置于终端设备中的芯片。当该通信装置为配置于终端设备中的芯片时，所述通信接口可以是输入/输出接口。
可选地，所述收发器可以为收发电路。可选地，所述输入/输出接口可以为输入/输出电路。
第九方面，提供了一种处理器，包括：输入电路、输出电路和处理电路。所述处理电路用于通过所述输入电路接收信号，并通过所述输出电路发射信号，使得所述处理器执行第一方面至第六方面中任一种可能实现方式中的方法。
在具体实现过程中，上述处理器可以为一个或多个芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于接收器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
第十方面，提供了一种处理装置，包括处理器和存储器。该处理器用于读取存储器中存储的指令，并可通过接收器接收信号，通过发射器发射信号，以执行第一方面至第六方面任一种可能实现方式中的方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
应理解，相关的数据交互过程例如发送指示信息可以为从处理器输出指示信息的过程，接收能力信息可以为处理器接收输入能力信息的过程。具体地，处理器输出的数据可以输出给发射器，处理器接收的输入数据可以来自接收器。其中，发射器和接收器可以统称为收发器。
上述第十方面中的处理装置可以是一个或多个芯片。该处理装置中的处理器可以通过硬件来实现也可以通过软件来实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于该处理器之外，独立存在。
第十一方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得计算机执行上述第一方面至第六方面中任一种可能实现方式中的方法。
第十二方面，提供了一种计算机可读介质，所述计算机可读介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述第一方面至第六方面中任一种可能实现方式中的方法。
第十三方面，提供了一种通信系统，包括前述的网络设备和终端设备。
附图说明
图1是适用于本申请实施例提供的通信方法的通信系统的示意图；
图2至图9是本申请实施例提供的通信方法的示意性流程图；
图10是本申请实施例提供的通信装置的示意性框图；
图11是本申请实施例提供的终端设备的结构示意图；
图12是本申请实施例提供的网络设备的结构示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、未来的第五代(5th generation，5G)系统或新无线(new radio，NR)，车到其它设备(vehicle-to-X V2X)，其中V2X可以包括车到互联网(vehicle to network，V2N)、车到车(vehicle to-vehicle，V2V)、车到基础设施(vehicle to infrastructure，V2I)、车到行人(vehicle to pedestrian，V2P)等、车间通信长期演进技术(long term evolution-vehicle，LTE-V)、车联网、机器类通信(machine type communication，MTC)、物联网(Internet of Things，IoT)、机器间通信长期演进技术(long term evolution-machine，LTE-M)，机器到机器(machine to machine，M2M)等。
本申请实施例中，网络设备可以是任意一种具有无线收发功能的设备。网络设备包括但不限于：演进型节点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)，无线保真(wireless fidelity，WIFI)系统中的接入点(access point，AP)、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G(如NR)系统中的gNB或传输点(TRP或TP)，或者，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(BBU)，或，分布式单元(distributed unit，DU)等。
在一些部署中，gNB可以包括集中式单元(centralized unit，CU)和DU。gNB还可以包括有源天线单元(active antenna unit，AAU)。CU实现gNB的部分功能，DU实现gNB的部分功能，比如，CU负责处理非实时协议和服务，实现无线资源控制(radio resource control，RRC)，分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能。DU负责处理物理层协议和实时服务，实现无线链路控制(radio link control，RLC)层、介质接入控制(medium access control，MAC)层和物理(physical，PHY)层的功能。AAU实现部分物理层处理功能、射频处理及有源天线的相关功能。由于RRC层的信息最终会变成PHY层的信息，或者，由PHY层的信息转变而来，因而，在这种架构下，高层信令，如RRC层信令，也可以认为是由DU发送的，或者，由DU+AAU发送的。可以理解的是，网络设备可以为包括CU节点、DU节点、AAU节点中一项或多项的设备。
需要说明的是，CU可以被划分为接入网设备，也可以被划分为核心网(core network，CN)设备，本申请对此不做限定。在本申请实施例中，为便于理解和说明，将CU划分为接入网设备。
网络设备为小区提供服务，终端设备通过网络设备分配的传输资源(例如，频域资源，或者说，频谱资源)与小区进行通信。该小区可以属于宏基站(例如，宏eNB或宏gNB等)，也可以属于小小区(small cell)对应的基站。这里的小小区可以包括：城市小区(metro  cell)、微小区(micro cell)、微微小区(pico cell)、毫微微小区(femto cell)等。这些小小区具有覆盖范围小、发射功率低的特点，适用于提供高速率的数据传输服务。
在本申请实施例中，终端设备也可以称为用户设备(user equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。本申请的实施例中的终端设备可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的终端设备、未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备或者非公共网络中的终端设备等。
其中，可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
此外，终端设备还可以是物联网(Internet of things，IoT)系统中的终端设备。IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。
本申请对于终端设备的具体形式不作限定。
为便于理解本申请实施例，首先结合图1详细说明适用于本申请实施例的通信系统。图1示出了适用于本申请实施例的通信方法和通信装置的通信系统的示意图。如图1所示，该通信系统100可以包括至少两个网络设备，例如图1所示的网络设备110和网络设备120；该通信系统100还可以包括至少一个终端设备，例如图1所示的终端设备130。其中，该终端设备130可以是移动的或固定的。网络设备110和网络设备120均为可以通过无线链路与终端设备130通信的设备，如基站或基站控制器等。每个网络设备可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域(小区)内的终端设备进行通信。
图1示例性地示出了两个网络设备和一个终端设备，但这不应对本申请构成任何限定。可选地，该通信系统100可以包括更多个网络设备，并且每个网络设备的覆盖范围内可以包括其它数量的终端设备。可选地，该通信系统100还可以包括一个或多个核心网设备。本申请实施例对此不做限定。
上述各个通信设备，如图1中的网络设备110、网络设备120或终端设备130，可以配置多个天线。该多个天线可以包括至少一个用于发送信号的发射天线和至少一个用于接 收信号的接收天线。另外，各通信设备还附加地包括发射机链和接收机链，本领域普通技术人员可以理解，它们均可包括与信号发送和接收相关的多个部件(例如处理器、调制器、复用器、解调器、解复用器或天线等)。因此，网络设备与终端设备之间可通过多天线技术通信。
可选地，该无线通信系统100还可以包括网络控制器、移动管理实体等其他网络实体，本申请实施例不限于此。
为便于理解本申请实施例，首先对本申请中涉及到的术语作简单说明。
1、小区(cell)：小区是高层从资源管理或移动性管理或服务单元的角度来描述的。每个网络设备的覆盖范围可以被划分为一个或多个小区，且每个小区可以对应一个或多个频点，或者说，每个小区可以看成是一个或多个频点的覆盖范围所形成的区域。
需要说明的是，小区可以是网络设备的无线网络的覆盖范围内的区域。在本申请实施例中，不同的小区可以对应相同或者不同的网络设备。例如，小区#1所属的网络设备和小区#2所属的网络设备可以是不同的网络设备，如，基站。也就是说，小区#1和小区#2可以由不同的基站来管理。或者，又例如，管理小区#1的网络设备和管理小区#2的网络设备也可以是同一基站的不同的射频处理单元，例如，射频拉远单元(radio remote unit，RRU)，也就是说，小区#1和小区#2可以由同一基站管理，具有相同的基带处理单元和中频处理单元，但具有不同的射频处理单元。或者，再例如，小区#1所属的网络设备和小区#2所属的网络设备可以是同一个网络设备，如，基站。也就是说，小区#1和小区#2可以由相同的基站来管理，这种情况下，可以称为小区#1和小区#2共站。本申请对此不做特别限定。
如前所述，gNB在一些可能的部署中，可以包括CU和DU。在这种部署下，小区#1和小区#2可以由同一个CU和同一个DU管理，即，共CU且共DU；小区#1和小区#2可以由同一个CU和不同的DU管理，即，共CU但不共DU；小区#1和小区#2也可以由不同的CU和不同的DU管理，即，不共CU且不共DU。
2、切换(handover，HO)：在无线通信系统中，当终端设备从一个小区向另一个小区移动/靠近时，为了保持终端设备的通信不中断，需要进行切换。在本申请实施例中，源小区表示切换前为终端设备提供服务的小区，目标小区表示切换后为终端设备提供服务的小区。目标小区的相关信息(如目标小区的物理小区标识、频率信息、切换至目标小区所需的无线资源信息，如随机接入资源信息等)，可以通过切换消息来指示，该切换消息是源小区所属的网络设备(即源网络设备)向终端设备发送的。
切换可以是站内切换或站间切换。站内切换，可以指源小区与目标小区属于同一个网络设备(如基站)，其中，源小区、目标小区可以是同一个小区或者不同的小区；站间切换，指源小区与目标小区属于不同的网络设备(如基站)。本申请对此不做限定。
应理解，小区即为网络设备的覆盖区域，源小区对应源网络设备(例如源基站)，目标小区对应目标网络设备(例如目标基站)。
传统的切换流程中，终端设备的移动性管理是由网络设备控制的。即，网络设备通过发送切换消息指示终端设备切换到哪个小区以及如何进行切换。例如，源网络设备向终端设备发送切换消息以控制终端设备从源小区切换到目标小区。该切换消息可以是RRC消息。例如，在LTE系统中，该RRC消息可以是携带移动性控制信息信元(mobility control  info)的RRC连接重配置消息；在NR系统中，该RRC消息可以是携带同步重配置信元(reconfiguration with sync)的RRC重配置消息。切换消息中包含目标网络设备(即目标小区所属的网络设备)为该终端设备配置的接入目标小区所需的参数，例如，包含目标小区的信息(如，目标小区的物理小区标识(physical cell identifier，PCI)以及目标小区对应的频率信息、目标网络设备为终端设备分配的C-RNTI)、接入目标小区所需的随机接入信道(random access channel，RACH)资源信息(如，专用RACH资源和/或公共RACH资源)等。终端设备在接收到该切换消息后，根据切换消息中包含的内容，向目标网络设备发起随机接入过程。NR引入波束特性，目标网络设备在配置接入目标小区所需的RACH资源信息时，可以考虑波束特性。例如，在配置RACH资源时，目标网络设备可以配置与目标小区下的波束(如SSB或CSI-RS)关联的RACH资源。后文会结合随机接入的不同方式详细说明RACH资源，这里暂且不作详述。
应理解，切换消息和上述用于指示切换的RRC消息是从不同的角度来描述的。切换消息从功能的角度来描述，旨在表达该消息是用于指示终端设备进行切换。RRC消息从消息类型的角度来描述，旨在表达该消息是高层信令。其中RRC重配置消息是对RRC消息的列举。换句话说，该切换消息是通过高层信令下发给终端设备的。
还应理解，上文中列举了不同的RRC消息，如LTE中的RRC连接重配置消息、NR中的RRC重配置消息等，这些消息仅为便于理解而示例，不应对本申请构成任何限定。本申请对于用于指示终端设备发起切换流程的RRC消息的具体名称不作限定。
需要说明的是，本申请实施例中所涉及的目标小区并不一定是基于传统的切换流程而配置的小区。终端设备例如还可以基于下文所述的条件切换机制进行切换，在切换前终端设备可以确定出一个或多个小区，该一个或多个小区对应的CHO配置信息能够被遵从，且该一个或多个小区满足CHO执行条件(或CHO触发条件)，终端设备可以在该一个或多个小区中确定出目标小区。本申请对此不作限定。其中，关于CHO配置信息和CHO执行条件的相关内容在下文会做详细说明，这里暂且不作详述。
在本申请实施例中，目标小区例如可以是CHO配置信息能够被遵从且满足CHO执行条件的小区，也可以是满足S准则且CHO配置信息能够被遵从的小区。本申请对此不作限定。
应理解，目标小区只是为了便于与其他候选小区(比如CHO配置信息不能够被遵从和/或不满足CHO执行条件的候选小区)或其他小区(比如满足S准则但CHO配置信息不能够被遵从的小区)区分而命名，这里CHO配置信息不能够被遵从可以指CHO执行条件不能被遵从和/或候选小区对应的参数不能被遵从，不应对本申请构成任何限定。本申请并不排除在未来的协议中对其定义其他命名以表达相同或相似含义的可能。
3、条件切换(CHO)：在传统切换流程中，网络设备通过切换消息向终端设备指示需要切换至的目标小区。但由于在通信系统中，如LTE或NR中，信道质量的快速衰减、终端设备的快速移动以及物体的遮挡、测量、切换准备的持续时间较长等因素，使得切换消息发送失败，导致切换失败，降低切换成功率，降低系统可靠性。另外，终端设备往往需要通过执行重建立流程来恢复通信。这可能导致通信中断时间较长，影响用户体验。
条件切换基于上述问题而被提出，以期提升切换成功率，避免长时间的通信中断，提高用户体验。
在条件切换中，网络设备可以通过高层信令，如RRC消息，为终端设备配置一个或多个候选小区。示例性地，网络设备可以通过一条RRC消息或多条RRC消息向终端设备指示一个或多个候选小区的CHO配置信息。应理解，这里所述的RRC消息的数量与候选小区的数量并不一定具有一一对应关系。网络设备可以通过一条RRC消息指示一个或多个候选小区的CHO配置信息，也可以通过多条RRC消息指示多个候选小区的CHO配置信息，本申请对此不作限定。
候选小区的CHO配置信息中可以包括CHO执行条件(或者称，CHO触发条件)和与候选小区对应的参数。
其中，CHO执行条件可以理解为终端设备进行切换的触发条件。当终端设备确定网络设备配置的某一候选小区满足CHO执行条件，则可以考虑切换到该候选小区。当然，满足CHO执行条件只是终端设备进行切换的条件之一，并不代表某一候选小区满足CHO执行条件，就一定会切换到该候选小区。
CHO执行条件可以是一个或多个候选小区共用的。也就是说，在候选小区为多个的情况下，该多个候选小区可以对应相同的CHO执行条件。CHO执行条件也可以是小区级的。也就是说，在候选小区为多个的情况下，多个候选小区可以有各自对应的CHO执行条件。
下文中所提及的候选小区满足CHO执行条件，或者，CHO执行条件被满足，可以是指，候选小区的信号质量和/或源小区的信号质量满足该候选小区对应的CHO执行条件，该CHO执行条件可以是与其他候选小区共用的CHO执行条件，也可以是仅与该候选小区对应的CHO执行条件。本申请对此不作限定。为了简洁，后文中省略对相同或相似情况的说明。
CHO执行条件具体可以包括CHO执行事件(或触发事件)类型及其相应的门限值。
作为示例而非限定，CHO执行事件类型例如包括但不限于，事件A3、事件A4、事件A5、事件B1、事件B2。其中，事件A3具体可以是候选小区的小区信号质量比服务小区的小区信号质量高出预设的第一门限值。事件A5具体可以是，候选小区的小区信号质量高于预设的第二门限值，且服务小区的小区信号质量低于预设的第三门限值。各事件的具体说明可以参考现有技术，为了简洁，这里不一一详述。
其中，信号质量例如可以包括以下一项或多项：参考信号接收功率(reference signal receiving power，RSRP)、参考信号接收质量(reference signal receiving quality，RSRQ)、信号与干扰加噪声比(signal to interference plus noise ratio，SINR)。
CHO执行条件可以包括上述CHO执行事件类型的指示和相应的门限值的指示。
CHO配置信息中与候选小区对应的参数具体可以包括用于终端设备切换到该候选小区的参数、用于终端设备在该候选小区中进行通信的参数。换句话说，CHO配置信息中与候选小区对应的参数，可以包括终端切换至/接入至该候选小区所需的相关参数。
其中，候选小区对应的参数例如可以包括但不限于，该候选小区为终端设备分配的小区无线网络临时标识(cell-radio network temporary identifier，C-RNTI)，接入该候选小区的无线资源信息，如随机接入信道(random access channel，RACH)资源信息，候选小区的标识信息、候选小区的频率信息等。可选地，上述与候选小区对应的参数还包括测量相关信息，如，测量标识(measID)、测量频点等。
候选小区的标识信息例如可以包括但不限于，候选小区的小区全球标识(cell global indentifier，CGI)和候选小区的物理小区标识(physical cell identifier，PCI)。
候选小区的频率信息例如可以包括但不限于，同步信号块(synchronization signal block，SSB)的绝对频率、参考资源块(resource block，RB)的绝对频率位置。其中，SSB的绝对频率例如可以是信元“绝对频率SSB(absoluteFrequencySSB)”。参考RB例如可以是0号公共RB(common resource block，CRB)，例如记为CRB 0。参考RB的绝对频率位置例如可以包括信元“绝对频率点A(absoluteFrequencyPoint A)”、“频率带宽列表(frequency BandList)”、“子载波间隔(subcarrier space，SCS)特定的载波列表(scs-SpecificCarrierList)”等。
其中，关于绝对频率点A的相关说明如下：每个载频上，在频域上按照12个连续子载波为单位划分成RB，RB的划分是“点A(point A)”作为公共参考点的。CRB编号可以从0开始，例如记作CRB 0。CRB 0中的子载波0在频域的中点可对应point A。point A可以是由网络设备为终端设备配置的。
用于终端设备在候选小区中进行通信的参数例如可以包括但不限于，物理层配置参数、介质接入控制(medium access control，MAC)层配置参数、无线链路控制(radio link control，RLC)层配置参数、分组数据汇聚层协议(packet data convergence protocol，PDCP)层配置参数、业务数据自适应协议(service data adaption protocol，SDAP)层配置参数、无线资源控制(radio resource control，RRC)层配置参数、以及承载配置信息等等。
应理解，上文对CHO配置信息与候选小区对应的参数的列举仅为示例，不应对本申请构成任何限定。本申请并不排除在CHO配置信息中包含除上述列举之外的其他与候选小区对应的参数的可能。
在一种实现方式中，网络设备可以在RRC消息中采用增加改变列表(如ToAddMod list)的信元结构进行候选小区的CHO配置信息的添加或修改，并采用释放列表(如ToRelease list)或移动列表(ToRemoveList)的信元结构进行候选小区的CHO配置信息的删除。
该RRC消息例如可以是新定义的一条RRC消息，比如条件切换RRC重配置(CondRRCReconfiguration)或者其他命名的RRC消息，该RRC消息也可以是复用已有的RRC消息，比如RRC重配置消息等。本申请对于用于携带CHO配置信息的RRC消息的具体名称不作限定。
在本申请实施例中，终端设备可以基于网络设备所配置的一个或多个候选小区的CHO配置，确定CHO配置信息能够被遵从的候选小区。进一步地，如果该CHO配置信息能够被遵从的候选小区中存在小区满足CHO执行条件，或者，如果通过小区选择所确定小区(例如，通过小区选择所确定出的满足S准则的小区)包含在CHO配置信息能够被遵从的候选小区中，则终端设备可以确定出目标小区。
因此，目标小区可以是指CHO配置信息能够被遵从且满足CHO执行条件的候选小区中的一个小区，或者，也可以是满足S准则且包含在CHO配置信息能够被遵从的候选小区中的一个小区。这里，CHO配置信息能够被遵从可以指CHO执行条件能被遵从、候选小区对应的参数能被遵从。
可以理解，终端设备确定出的CHO配置信息能够被遵从的候选小区可以为一个，也 可以为多个。并且，该CHO配置信息能够被遵从的候选小区中可能存在一个或多个小区满足CHO执行条件。本申请对此并不限定。
需要说明的是，终端设备通常选择一个小区作为目标小区，进而尝试切换到目标小区。其中，目标小区可以是指CHO配置信息能够被遵从且满足CHO执行条件的一个小区；或者，也可以是满足S准则的小区，且该小区属于CHO配置信息能够被遵从的候选小区。
例如，在上述终端设备确定出的CHO配置信息能够被遵从且满足CHO执行条件的候选小区为多个的情况下，终端设备可以确定出一个目标小区，尝试切换到该目标小区。在切换失败的情况下，终端设备还可以重新确定出一个目标小区，尝试切换到新确定的目标小区。以此类推，终端设备可能对CHO配置信息能够被遵从且满足CHO执行条件的每个候选小区都尝试了切换流程，也可能对其中的部分候选小区尝试了切换流程，本申请对此不作限定。
又例如，如果终端设备通过小区选择确定出满足S准则的一个小区包含在CHO配置信息能够被遵从的候选小区中，则终端设备可以尝试切换到该小区。在切换失败的情况下，终端设备还可以再次执行小区选择，确定出满足S准则的另一个小区，若该小区包含在CHO配置信息能够被遵从的候选小区中，则可以被确定为新的目标小区。终端设备可以尝试切换至新确定的目标小区。以此类推，终端设备可以执行多次小区选择，也可以仅执行一次小区选择，本申请对此不作限定。
另外，上文所述的尝试切换到目标小区的流程例如可以是下文所述的与目标小区进行随机接入的流程，或，与目标小区进行无随机接入信道切换(RACH-less handover，RACH-less HO)的流程。
需要说明的是，在CHO机制中，源网络设备与终端设备之间可以保持RRC连接/数据传输。换句话说，终端设备在成功切换至某目标小区之前(比如在终端设备给成功接入的目标小区发送RRC重配置完成消息之前)，终端设备可以保持与源网络设备之间的正常传输。或者，在终端设备释放与源网络设备之间的RRC连接/数据传输之前(例如，源网络设备或目标网络设备指示终端设备释放与源网络设备之间的RRC连接/数据传输；或者，终端设备基于定时器机制释放与源网络设备之间的RRC连接/数据传输，例如，源网络设备或目标网络设备向终端设备发送定时器1的相关信息(如定时器1的有效时长)，或协议约定终端设备接收到包含CHO配置信息的RRC消息后启动定时器1且协议约定定时器1的有效时长，当定时器1超时，终端设备释放与源网络设备之间的RRC连接/数据传输释放/停止)，终端设备可以保持与源网络设备之间的正常传输。因此，源网络设备在首次给终端设备发送了包含有一个或多个候选小区的CHO配置信息的RRC消息后，后续还可以再给终端设备发送RRC消息，以对此前接收到的一个或多个候选小区的CHO配置信息进行更新；或者，源网络设备在首次给终端设备发送了包含有一个或多个候选小区的CHO配置信息的RRC消息后，后续还可以再给终端设备发送切换消息，以通知终端设备进行传统切换；或者，源网络设备在首次给终端设备发送了包含有一个或多个候选小区的CHO配置信息的RRC消息后，后续还可以再给终端设备发送用于其他目的的RRC消息，本实施例对此不做限定。
4、随机接入：随机接入是终端设备开始向尝试接入的网络设备发送随机接入前导码(preamble)，至终端设备与网络设备间建立起连接的这段过程。随机接入流程例如可能 在切换、RRC重建立等流程中发生。
随机接入可以分为基于竞争的随机接入(contention based random access，CBRA)和非竞争的随机接入(contention free random access，CFRA)。其中CFRA使用的资源为CFRA资源，CFRA资源是专用RACH资源。CFRA资源具体可以包括前导码索引和时频资源。在NR中，CFRA资源可以是与小区的某个波束关联的CFRA资源。若网络设备为终端设备配置了CFRA资源，则终端设备可以使用该CFRA资源发起CFRA流程。如果CFRA失败或未配置CFRA资源，终端设备可以发起CBRA。CBRA资源可理解为公共资源，终端设备可以通过竞争的方式使用CBRA资源发起CBRA流程。在下文实施例中所提及的随机接入流程，可以是指终端设备进行CFRA流程，也可以是指终端设备进行CBRA流程，或者，还可以是指终端设备在进行了CFRA之后又进行CBRA流程。
下面简单说明基于竞争的随机接入流程。基于竞争的随机接入流程具体可以包括下文所述的步骤一至步骤四。
步骤一：终端设备通过物理随机接入信道(physical random access channel，PRACH)向网络设备发送随机接入前导码。
步骤二：网络设备向终端设备发送随机接入响应(random access response，RAR)。该随机接入响应中可以包含定时提前量(timing advance，TA)信息、上行授权(uplink grant，UL grant)信息和临时C-RNTI(temporary cell-radio network temporary identifier，TC-RNTI)等。
步骤三：终端设备基于接收到的随机接入响应，在网络设备分配的UL grant资源上发送消息或数据，例如，发送RRC建立请求消息，该RRC建立请求消息中可以包含终端设备的标识信息。该标识信息例如可以是上文所述的TC-RNTI。
步骤四：网络设备接收到终端设备在分配的UL grant资源上发送的消息或数据后，若无冲突(或无竞争)，则网络设备给终端设备发送竞争解决消息，例如，网络设备向终端设备发送RRC建立消息。此后，终端设备可以与网络设备通信。
CFRA流程具体可以包括下文所述的步骤(1)至步骤(2)。
步骤(1)：终端设备通过PRACH向网络设备发送随机接入前导码。在非竞争的随机接入流程中，网络设备提前给终端设备分配/发送随机接入前导码索引。换句话说，该随机接入前导码索引是专用的。根据该随机接入前导码索引，终端设备向网络设备发送随机接入前导码。
步骤(2)：网络设备向终端设备发送随机接入响应。该随机接入响应中可以包含TA信息、UL grant信息等。
需要说明的是，UL grant信息用于指示UL grant。UL grant具体可以包括以下至少一项：时频资源、调制编码方式(modulation coding scheme，MCS)、新数据指示(new data indicator，NDI)、发起上行传输的时刻(如子帧或时隙(slot))以及上行调度的间隔等。其中，UL grant中包含的时频资源具体可以是指通过该UL grant调度的上行资源的时频位置。该UL grant调度的上行资源例如可以是PUSCH资源。
应理解，UL grant中包含的具体内容可以参考现有技术。本申请对于UL grant中包含的具体内容不作限定。
5、RACH-less切换：为了减少因随机接入流程带来的时延，终端设备可以跳过(或 者说不执行)与目标小区的随机接入流程。终端设备在确定出目标小区之后，基于网络设备配置的RACH-less切换相关信息(如TA信息、UL grant信息等)向目标小区所属的网络设备发送RRC重配置完成消息。可选地，上述用于指示一个或多个候选小区的CHO配置信息的RRC消息可以包括指示信息，该指示信息可用于指示终端设备执行RACH-less切换。
应理解，RACH-less切换也可能失败。例如，若目标小区配置的关联有UL grant的波束中不存在信号质量高于预设门限(用于指示一个或多个候选小区的CHO配置信息的RRC消息可以包括该预设门限)的波束，或者，若目标小区中不存在关联了UL grant且信号质量高于预设门限的波束，则终端设备向该目标小区发起的RACH-less切换失败。
6、RRC重建立：当终端设备发生切换失败、RLF、RRC重配置失败等情况时，终端设备可以发起RRC重建立流程。终端设备发起RRC重建立流程也可以简称为终端设备发起重建立流程。
RRC重建立流程例如可以包括以下几个步骤：
步骤1、终端设备向重建立小区(或者说该小区所属的网络设备)发送RRC重建立请求消息；
步骤2、重建立小区允许终端设备的请求，则给终端设备发送RRC重建立消息；
步骤3、终端设备向重建立小区发送RRC重建立完成消息。
这里，重建立小区可以是终端设备经过小区搜索或检测所确定的小区。该重建立小区可以是满足预定准则的小区，如NR协议TS38.304-f30中的小区选择S准则。为了简洁，这里不作详细说明。关于RRC重建立流程以及终端设备确定重建立小区的具体过程可以参考现有技术，为了简洁，这里不作详细说明。
7、小区选择：当终端设备开机或从盲区进入覆盖区时，将寻找公共陆地移动网络(public land mobile network，PLMN)允许的所有频段，并选择合适的小区驻留。
在一种实现方式中，终端设备可以根据S准则确定可以驻留的小区。该S准则可以是例如可以是小区搜索中的接收功率大于0dB，且小区搜索中的接收的信号质量大于0dB。其中，小区搜索中的接收功率可以根据搜索到/测量到的小区的RSRP值、小区最低接收电平和小区最低接收电平偏置等确定。小区搜索中的接收的信号质量可以根据搜索到/测量到的RSRQ值、最小接收信号质量和最小接收信号接收质量偏置值确定。关于S准则的具体内容可以参看NR协议，为了简洁，这里不作详述。
8、遵从(comply with)：或者称遵循。终端设备遵从配置信息，可以包括以下一项或多项：终端设备在接收到该配置信息时能够解析该配置信息，能够理解该配置信息，以及能够使用该配置信息。
因此，当终端设备不能遵从某一候选小区的CHO配置信息，可以理解为，终端设备不能够遵从该候选小区对应的CHO执行条件和/或该候选小区对应的参数，或者，该候选小区对应的CHO执行条件和/或该候选小区对应参数对与该终端设备来说是无效的。
为便于理解，这里以传统切换为例进行说明。终端设备在接收到用于指示终端设备进行切换的RRC消息后，可以先评估是否能够遵从该RRC消息中包含的配置信息。传统切换中，RRC消息中包含了用于切换的配置信息，例如，可以包括与切换相关的参数和与通信相关的参数，具体的，比如目标小区的相关信息，以及终端设备接入该目标小区所需 的相关配置参数等。终端设备需要确定(或者说，评估或判断)是否能够遵从该RRC消息中携带的配置信息。如果终端设备能够遵从该RRC消息中包含的配置信息，则可以执行后续的切换流程，如，终端设备可以根据该RRC消息中包含的参数(如目标小区对应的物理层配置参数、MAC层配置参数、RLC层配置参数、PDCP层配置参数、SDAP层配置参数、RRC层配置参数、以及承载配置信息等，目标小区的PCI和频率信息，RACH资源信息等)，与目标小区进行随机接入流程、以及后续的通信。如果终端设备不能够遵从该RRC消息中包含的部分或全部的配置参数，则终端设备可以发起重建立流程。
如前所述，在传统切换流程中，当终端设备不能够遵从该RRC消息中的配置信息时，则发起重建立流程。而在CHO切换中，网络设备可以通过RRC消息给终端设备提供一个或多个候选小区的CHO配置信息，由终端设备自行确定出需要切换至的目标小区。在确定出该目标小区之前，终端设备也需要确定(或者说，评估或判断)是否能够遵从该RRC消息中携带的信息(如候选小区的CHO配置信息)。终端设备确定是否能够遵从候选小区的CHO配置信息可以包括，终端设备确定是否能够遵从CHO执行条件，以及终端设备确定是否能够遵从与候选小区对应的参数。
一种可能的情况，终端设备可能不能够遵从RRC消息中携带的部分或全部的信息，例如，终端设备可能不能够遵从所有配置的候选小区的CHO配置信息，或者，终端设备可能不能够遵从配置的部分候选小区对应的CHO配置信息。如果终端设备只是因为某些候选小区的CHO配置信息不能够遵从就发起重建立，这可能带来较长的通信中断时间，用户体验不佳。
鉴于此，本申请提供一种方法，以期为终端设备提供合理的操作流程，以尽可能地减少通信中断时长，从而提高用户体验。
为了便于理解本申请实施例，在介绍本申请实施例之前，先作出以下几点说明。
第一，在本申请实施例中，“用于指示”可以包括用于直接指示和用于间接指示，也可以包括显式指示和隐式指示。将某一信息所指示的信息称为待指示信息，则具体实现过程中，对待指示信息进行指示的方式有很多种，例如但不限于，可以直接指示待指示信息，如待指示信息本身或者该待指示信息的索引等。也可以通过指示其他信息来间接指示待指示信息，其中该其他信息与待指示信息之间存在关联关系。还可以仅仅指示待指示信息的一部分，而待指示信息的其他部分则是已知的或者提前约定的。例如，还可以借助预先约定(例如协议规定)是否存在某个信元来实现对待指示信息的指示，从而在一定程度上降低指示开销。
第二，在下文示出的实施例中，第一、第二以及各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围。例如，区分不同的指示信息、不同的时间间隔等。
第三，“预定义”或“预配置”可以通过在设备(例如，包括终端设备和网络设备)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不做限定。其中，“保存”可以是指，保存在一个或者多个存储器中。所述一个或者多个存储器可以是单独的设置，也可以是集成在编码器或者译码器，处理器、或通信装置中。所述一个或者多个存储器也可以是一部分单独设置，一部分集成在译码器、处理器、或通信装置中。存储器的类型可以是任意形式的存储介质，本申请并不对此限定。
第四，本申请实施例中涉及的“协议”可以是指通信领域的标准协议，例如可以包括 LTE协议、NR协议以及应用于未来的通信系统中的相关协议，本申请对此不做限定。
第五，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，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分别可以是单个，也可以是多个。
第六，在本申请实施例中，“当……时”、“在……的情况下”、“若”以及“如果”等描述均指在某种客观情况下设备(如，终端设备或者网络设备)会做出相应的处理，并非是限定时间，且也不要求设备(如，终端设备或者网络设备)在实现时一定要有判断的动作，也不意味着存在其它限定。
第七，为方便说明本申请实施例，在未作出特别说明的情况下，所涉及到的消息名称均为NR中的消息名称。但可以理解的是，这些消息名称仅为便于理解而示例，不应对本申请构成任何限定。本申请并不排除在未来的协议中定义其他的消息名称来替代本申请中所列举的消息名称以实现相同或相似功能的可能。此外，以NR中的消息名称为例来说明本申请实施例，并不应对本申请提供的方法所适用的场景构成任何限定。比如，本申请提供的方法同样也可以适用于LTE系统中。当本申请提供的方法应用于LTE系统时，下文实施例中的“RRC重配置”、“RRC重建立”等可以分别替换为“RRC连接重配置”、“RRC连接重建立”等。为了简洁，这里不一一列举。
第八，下文结合多个流程图详细描述了多个实施例，但应理解，这些流程图及其相应的实施例的相关描述仅为便于理解而示例，不应对本申请构成任何限定。各流程图中的每一个步骤并不一定是必须要执行的，例如有些步骤是可以跳过的。并且，各个步骤的执行顺序也不是固定不变的，也不限于图中所示，各个步骤的执行顺序应以其功能和内在逻辑确定。
下面结合附图详细说明本申请实施例提供的方法。
应理解，下文仅为便于理解和说明，以终端设备与网络设备之间的交互为例详细说明本申请实施例提供的方法。但这不应对本申请提供的方法的执行主体构成任何限定。例如，下文实施例示出的终端设备可以替换为配置于终端设备中的部件(如芯片或电路)等。下文实施例示出的网络设备也可以替换为配置于网络设备中的部件(如芯片或电路)等。
下文示出的实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可，例如，本申请实施例提供的方法的执行主体可以是终端设备或网络设备，或者，是终端设备或网络设备中能够调用程序并执行程序的功能模块。
图2是从设备交互的角度示出的本申请实施例提供的通信方法200的示意性流程图。如图2所示，该方法200可以包括步骤210至步骤290。下面详细说明方法200中的各步骤。
图2是从设备交互的角度示出的本申请实施例提供的通信方法200的示意性流程图。如图2所示，该方法200可以包括步骤210至步骤290。下面详细说明方法200中的各步 骤。
在步骤210中，终端设备接收第一RRC消息，该第一RRC消息包括一个或多个候选小区的CHO配置信息。该第一RRC消息例如可以是源网络设备发送的。
为便于与后文所述的RRC消息区分，这里将用于配置一个或多个候选小区的CHO配置信息的RRC消息记为第一RRC消息。该第一RRC消息可以是一条，也可以是多条，本申请对此不作限定。
候选小区的CHO配置信息可以包括CHO执行条件。如前所述，部分候选小区可以均对应同一个CHO执行条件，也可以每个候选小区有各自对应的CHO执行条件。因此，该第一RRC消息中可以仅携带一个CHO执行条件，也可以携带多个CHO执行条件，本申请对此不作限定。
例如，终端设备接收到一条第一RRC消息，该第一RRC消息中包括多个候选小区的相关信息和一个CHO执行条件，则该CHO执行条件可以是该第一RRC消息所配置的多个候选小区所共用的CHO执行条件。
又例如，终端设备接收到一条第一RRC消息，该第一RRC消息中包括多个候选小区的相关信息和多个CHO执行条件，则该多个CHO执行条件可以是与该第一RRC消息所配置的多个候选小区对应的多个CHO执行条件，该多个候选小区可以与多个CHO执行条件一一对应，或者，该多个候选小区中的部分候选小区可以对应同一个CHO执行条件，另一部分候选小区可以对应另一个CHO执行条件。本申请对于CHO执行条件与候选小区之间的对应关系不作限定。
再例如，终端设备接收到多条第一RRC消息，每条第一RRC消息中包括一个候选小区的CHO配置信息，即，可以包括一个候选小区的相关信息和对应的CHO执行条件。
本申请对于RRC消息的数量与候选小区的数量的对应关系不做限定。本申请对于CHO执行条件与候选小区间的对应关系也不做限定。
需要说明的是，若终端设备接收到多条第一RRC消息，终端设备可以根据该多条第一RRC消息确定一个或多个候选小区的CHO配置信息。例如，终端设备接收到两条第一RRC消息，RRC消息#1和RRC消息#2。该RRC消息#1中包括2个候选小区的CHO配置信息，如小区#1的CHO配置信息和小区#2的CHO配置信息；该RRC消息#2中包括1个候选小区，如小区#3的CHO配置信息。则终端设备可以根据该两条第一RRC消息，确定出的一个或多个候选小区可以包括小区#1、小区#2和小区#3，终端设备可以进一步确定小区#1的CHO配置信息、小区#2的CHO配置信息和小区#3的CHO配置信息。
还需要说明的是，本申请对于该多条第一RRC消息的接收时间不作限定。该多条第一RRC消息可以是同时接收到的，也可以是在不同的时刻接收到的。
在步骤220中，终端设备确定出不能够遵从一个或多个候选小区中的部分候选小区的CHO配置信息。
终端设备可以根据在步骤210中接收到的第一RRC消息，确定是否能够遵从候选小区的CHO配置信息。在候选小区为多个的情况下，终端设备可以确定是否能够遵从每个候选小区的CHO配置信息。示例性地，终端设备可以按照多个候选小区的配置顺序，按序或随机地，来确定每个候选小区的CHO配置信息是否能够被遵从，本实施例对此不做限定。
若第一RRC消息所配置的多个候选小区中至少有一个候选小区的CHO配置信息不能够被遵从，则终端设备可以确定该多个候选小区中的部分候选小区的CHO配置信息不能够被遵从。或者，理解为，若第一RRC消息所配置的多个候选小区中至少有一个候选小区的CHO配置信息不能够被遵从，终端设备确定不能够遵从该多个候选小区中的部分候选小区的CHO配置信息。
应理解，终端设备确定一个或多个候选小区中的部分候选小区的CHO配置信息不能够被遵从，也就是，终端设备确定一个或多个候选小区中的剩下部分的候选小区的CHO配置信息能够被遵从。
终端设备确定一个或多个候选小区中的部分候选小区(如候选小区#1)的CHO配置信息不能够被遵从，则，终端设备忽视该部分候选小区(如忽视该候选小区#1的CHO配置信息)。可选地，终端设备通知源网络设备释放/删除该部分候选小区(如终端设备向源网络设备发送消息a，消息a中可以包含候选小区#1的标识信息。该候选小区#1的表示信息例如可以包括以下一项或多项：该候选小区#1的PCI，该候选小区#1的频点信息，该候选小区#1的CGI，以及该候选小区#1对应的测量标识等。源网络设备在接收到消息a后，释放或删除该候选小区#1的CHO配置信息)。可选地，源网络设备通知该候选小区#1所属的网络设备释放/删除相应的候选小区。例如，源网络设备向该候选小区#1所属的网络设备发送消息b，消息b中包含要删除/释放的候选小区的标识信息。其中，要删除/释放的候选小区例如可以包括但不限于候选小区#1，该候选小区#1所属的网络设备在接收到消息b后，删除/释放要删除/释放的候选小区的CHO配置信息。
终端设备在确定出部分候选小区的CHO配置信息能够被遵从的情况下，可以保存该部分候选小区的CHO配置信息，并根据所保存的该部分候选小区的CHO配置信息，继续执行后续的流程。
在步骤230中，终端设备确定CHO配置信息能够被遵从的候选小区中是否存在满足CHO执行条件的小区。
在本申请实施例中，终端设备在确定对于部分候选小区的CHO配置信息不能够遵从的情况下，可以不发起重建立流程，而是从CHO配置信息能够被遵从的候选小区中确定是否存在满足CHO执行条件的小区。比如，第一RRC消息中配置了三个候选小区，小区#1、小区#2和小区#3，但终端设备确定不能够遵从小区#2的CHO配置信息，则终端设备可以从小区#1和小区#3中确定是否存在满足CHO执行条件的小区。
当CHO配置信息能够被遵从的候选小区中存在或不存在满足CHO执行条件的小区时，终端设备可以执行不同的操作。
例如，若CHO配置信息能够被满足的候选小区中存在满足CHO执行条件的小区，或者说，若CHO配置信息能够被满足的候选小区中存在这样的小区，其对应的CHO执行条件能够达到/满足，终端设备可以执行步骤240，尝试切换到该满足CHO执行条件的小区，或者说，尝试切换到CHO执行条件能够达到/满足的小区。可以理解，这里所述的该满足CHO执行条件的小区即为目标小区。
示例性地，在步骤240中，终端设备可以与该目标小区进行随机接入。若随机接入成功，终端设备可以向该目标小区发送RRC重配置完成消息；或者，如果第一RRC消息中包含该目标小区对应的RACH-less切换的相关信息，则终端设备也可以跳过随机接入流 程，根据RACH-less切换的相关信息，向目标小区发送RRC重配置完成消息。
若终端设备确定CHO配置信息能够被满足的候选小区中存在满足CHO执行条件的小区，则终端设备从候选小区中能够确定出目标小区。该目标小区可以是一个，也可以是多个，这可能取决于CHO执行条件和各候选小区的小区信号质量。但可以理解，该多个目标小区被确定出的时刻可能是不同的。当针对某一目标小区的切换失败，终端设备可以继续寻找新的目标小区，以尝试切换。如此执行，直到成功接入至某一目标小区中。因此，终端设备在成功接入之前，可能先后尝试了针对一个或多个目标小区的切换流程。
在一个示例中，终端设备根据第一RRC消息确定出CHO配置信息能够被遵从的候选小区中满足CHO执行条件的候选小区为小区#1，则小区#1为目标小区。终端设备可以尝试切换至小区#1。如果终端设备未成功切换至小区#1，或者，若终端设备根据第一RRC消息确定出的CHO配置信息能够被遵从的候选小区中，并不存在小区满足CHO执行条件的候选小区，则可以执行步骤250，终端设备执行小区选择，确定满足S准则的小区，并可进一步执行步骤260，确定该满足S准则的小区是否包含在CHO配置信息能够被遵从的候选小区中。若该满足S准则的小区包含在CHO配置信息能够被遵从的候选小区中，该满足S准则的小区为目标小区，可以执行步骤270，终端设备尝试切换至该满足S准则的小区。如果终端设备成功切换至该满足S准则的小区，则认为本轮CHO流程成功。若该满足S准则的小区未包含在CHO配置信息能够被遵从的候选小区中，或者，若终端设备未能成功切换至该满足S准则的小区，则可以执行步骤280，终端设备发起重建立流程。
或者，若终端设备未能成功切换至该满足S准则的小区，该终端设备还可以再次执行小区选择，确定满足S准则的另一小区，并确定该满足S准则的另一小区是否包含在CHO配置信息能够被遵从的候选小区中，若是，终端设备可以再次尝试切换至该小区。如此重复执行，直到成功接入到某一小区中，执行步骤290，与切换成功的小区进行通信；或直至终端设备维护的定时器(例如记作第一定时器)超时，执行步骤280，终端设备发起重建立流程。
其中，该第一定时器可以是终端设备在步骤210中接收到第一RRC消息时启动，也可以是在终端设备确定出目标小区后开始执行步骤240时启动。本申请对此不作限定。该第一定时器的时长例如可以是预定义的，如协议预定义，或者，第一RRC消息中可以包含第一定时器的相关信息，如第一定时器的有效时长等。本申请对此不作限定。
在另一种实现方式中，终端设备根据第一RRC消息确定出CHO配置信息能够被遵从的候选小区中满足CHO执行条件的候选小区为小区#1，则小区#1为目标小区。终端设备可以尝试切换至小区#1。如果终端设备成功切换至小区#1，则认为本轮CHO流程成功；如果终端设备未能成功切换至小区#1，则终端设备再根据第一RRC消息、此时的信道状态等，进行评估、判断，尝试从CHO配置信息能被遵从的候选小区中再次确定出满足CHO执行条件的小区作为新的目标小区。若终端设备确定出CHO配置信息能够被遵从的候选小区中满足CHO执行条件的另一候选小区为小区#3，则小区#3为目标小区。终端设备可以尝试切换至小区#3。如果终端设备成功切换至小区#3，则认为本轮CHO流程成功；如果终端设备未能成功切换至小区#3，则终端设备可以继续尝试寻找满足CHO执行条件的小区，如此重复执行，直至所有的CHO配置信息能够被遵从的候选小区都被判断过是否满足CHO执行条件，或直至CHO配置信息能够被遵从且CHO执行条件被满足的所有的 候选小区都被尝试切换过，或直至终端设备侧的第一定时器超时，可以执行步骤280，终端设备发起重建立流程。
又或者，终端设备可以在将第一RRC消息中配置的候选小区中CHO配置信息能够被遵从且满足CHO执行条件的所有小区都尝试了切换，但均切换失败之后，执行步骤250，进行小区选择，确定满足S准则的小区，并执行步骤260，确定该满足S准则的小区是否包含在CHO配置信息能够被遵从的候选小区中。若是，执行步骤270，终端设备尝试切换到该满足S准则的小区中。若切换成功，则本轮CHO流程成功。若该满足S准则的小区不包含在CHO配置信息能够被遵从的候选小区中，或者，若终端设备执行步骤270失败，则可以执行步骤280，终端设备发起重建立流程。
或者，若该满足S准则的小区不包含在CHO配置信息能够被遵从的候选小区中，或者，若终端设备执行步骤270失败，终端设备也可以再次执行步骤250至步骤270，直至成功接入到某一小区，则本轮CHO流程成功；或，第一定时器超时，则可以执行步骤280，终端设备发起重建立流程。
若终端设备在步骤230中确定CHO配置信息能够被满足的候选小区中不存在满足CHO执行条件的小区，或者说，若CHO配置信息能够被满足的候选小区中不存在这样的小区，其对应的CHO执行条件能够达到/满足，终端设备可以执行上述步骤250，进而确定该满足S准则的小区是否包含在CHO配置信息能够被遵从的候选小区中。若该满足S准则的小区包含在CHO配置信息能够被遵从的候选小区中，该满足S准则的小区为目标小区，可以执行步骤270，终端设备尝试切换至该满足S准则的小区。如果终端设备成功切换至该满足S准则的小区，则认为本轮CHO流程成功。若该满足S准则的小区未包含在CHO配置信息能够被遵从的候选小区中，或者，若终端设备未能成功切换至该满足S准则的小区，则可以执行步骤280，终端设备发起重建立流程。或者，终端设备也可以在确定CHO配置信息能够被满足的候选小区中不存在满足CHO执行条件的小区时，直接执行步骤280，发起重建立流程。终端设备发起重建立流程的具体过程在上文已经做了详述，为了简洁，这里不再重复。
在上述流程中，若终端设备在步骤240中切换成功或在步骤270中切换成功，则本轮CHO流程成功，可以执行步骤290，与切换成功的小区进行通信。
图2为了便于理解，示出了终端设备多种不同的实现方式，为便于区分，将同一步骤下的不同分支通过实线和虚线区分。但应理解，图2并未将上述方案全部示出。图2所示的流程不应对本申请构成任何限定。
基于上述技术方案，终端设备可以在确定不能够遵从部分候选小区的CHO配置信息的情况下，不发起重建立流程，而是优先尝试切换。终端设备可以在CHO配置信息能够被遵从的那部分候选小区中尝试寻找一个满足CHO执行条件的小区，并尝试切换到该小区；或者也可以通过小区选择确定一个满足S准则的终端设备如果未能成功切换至满足CHO执行条件的小区，或者，在CHO配置信息能够被遵从的候选小区中找不出满足CHO执行条件的小区，仍然可以基于S准则来选择一个适合切换的小区来尝试切换。终端设备基于不同的维度来寻找适合切换的小区，而不限于满足CHO执行条件的小区。从而有利于终端设备更大几率地寻找到合适的小区来尝试切换，更大程度地避免重建立流程造成的时延、复杂度。避免较长时间的通信中断对用户体验的影响，有利于提高系统可靠性，保 证系统性能，有利于提高用户体验。
可选地，该方法还包括：若终端设备不能够遵从第一RRC消息中所有候选小区的CHO配置信息，则终端设备保留在源小区。
终端设备不能够遵从第一RRC消息中所有候选小区的CHO配置信息，可以理解为，第一RRC消息中所有候选小区对应的CHO执行条件和/或参数不能被遵从，或者，第一RRC消息中所有候选小区对应的CHO执行条件和/或参数均无效。
此情况下，终端设备可以保留在源小区，即，维持与源小区的RRC连接/数据传输。此外，终端设备还可以丢弃该第一RRC消息中一个或多个候选小区的CHO配置信息。
可选地，该方法还包括：终端设备向源小区所属的网络设备(下文简称为源网络设备)发送RRC重配置失败消息。可选地，源网络设备可以向CHO配置信息不能够被遵从的各候选小区所属的网络设备发送消息，以用于通知各候选小区所属的网络设备进行CHO配置信息的修改。
如前所述，终端设备在保持着与源网络设备之间的RRC连接的情况下，还可能接收到其他RRC消息。可选地，该方法200还包括：终端设备接收第二RRC消息。该第二RRC消息例如是由源网络设备发送的。
例如，源网络设备可以先给终端设备发送第一RRC消息。在终端设备根据第一RRC消息完成CHO流程前，比如，终端设备根据第一RRC消息确定出满足CHO触发条件的目标小区之前，或者，在终端设备成功接入到确定出的目标小区之前，或者，在终端设备向确定出的目标小区发送RRC重配置完成消息之前，源网络设备可以向终端设备发送第二RRC消息。该第二RRC消息可以用于重新配置(也可简称为重配)候选小区。例如，该第二RRC消息可用于修改或释放第一RRC消息中配置过的候选小区，和/或，添加新的小区(如该新的小区不包含在第一RRC消息配置过的候选小区中)作为候选小区。或者，该第二RRC消息也可用于指示终端设备进行传统切换。或者，该第二RRC消息也可用于其他目的，本申请实施例对此不做限定。可选地，如果第二RRC消息用于重新配置候选小区，则终端设备可以根据第一RRC消息和/或第二RRC消息中可选包含的某一特定标识来得知如何根据第一RRC消息、第二RRC消息进行后续处理。该特定标识例如可以是某一预定义的信元，例如“候选小区重新配置”。比如终端设备接收到的第二RRC消息中携带有该“候选小区重新配置”的标识，则可以认为该第二RRC消息可用于对第一RRC消息中已经配置的候选小区的CHO配置信息进行重新配置。关于对重新配置候选小区的具体过程会在后文中详细说明，这里暂且不作详述。
或者，终端设备可以根据第一RRC消息、第二RRC消息中分别包含的具体的信息内容，判断第二RRC消息的作用。例如，判断第二RRC消息是否是用于对第一RRC消息中已经配置的候选小区的CHO配置信息进行重新配置，或者，判断第二RRC消息是否是传统的切换消息等，本实施例对此不做限定。
在本申请实施例中，为便于区分和说明，将用于重新配置候选小区的RRC消息记为第三RRC消息。可以理解，第三RRC消息是第二RRC消息的一种。
下面将结合具体的实施例详细说明终端设备在成功接收到第三RRC消息的情况下流程。图3是本申请另一实施例提供的通信方法300的示意性流程图。如图3所示，该方法300可以包括步骤310至步骤370。下面详细说明方法300中的各步骤。
在步骤310中，终端设备接收第一RRC消息，该第一RRC消息包括一个或多个候选小区的CHO配置信息。该第一RRC消息例如可以是源网络设备发送的。
关于步骤310的详细说明可以参考上文方法200中步骤210的详细说明，为了简洁，这里不再重复。
在步骤320中，终端设备接收第三RRC消息，该第三RRC消息用于重新配置候选小区。该第三RRC消息例如也可以是由源网络设备发送的。
与第一RRC消息相似，该第三RRC消息也可以包括一个或多个候选小区的CHO配置信息，以用于重新配置候选小区。例如，该第三RRC消息可用于修改或释放第一RRC消息中配置过的候选小区，和/或，添加新的小区(如该新的小区不包含在第一RRC消息配置过的候选小区中)作为候选小区。
与第一RRC消息相似地，第三RRC消息可以为一条，也可以多条，本申请对此不作限定。第三RRC消息例如可以是新定义的一条或多条消息，也可以是复用已有的消息(如重用RRC重配置消息)，本申请对此不作限定。此外，本申请对于第三RRC消息的数量与第三RRC消息或者第一RRC消息中所配置的候选小区的数量的对应关系不作限定。本申请对于CHO执行条件与候选小区间的对应关系也不做限定。
上文已经对终端设备判断接收到的RRC消息是否为第三RRC消息的具体方法作了详细说明，为了简洁，这里不再重复。若终端设备接收到该第三RRC消息，且对该第三RRC消息的完整性保护校验成功，则终端设备可以解析出该第三RRC消息中包括的一个或多个候选小区的CHO配置信息。如前所述，该第三RRC消息用于重新配置候选小区，故，第三RRC消息中的一个或多个候选小区与第一RRC消息中的一个或多个候选小区可以相同或不同，不做限定。
这里，对候选小区进行重新配置可以包括以下一项或多项：添加新的候选小区(如该新的候选小区不包含在第一RRC消息配置过的候选小区中)所对应的CHO配置信息，对已经配置的候选小区中的部分或全部候选小区的CHO配置信息进行修改，以及删除已经配置的候选小区中的部分或全部候选小区的CHO配置信息。简单来说，上述对候选小区的重新配置可以包括对已经配置的候选小区的CHO配置信息的修改、删除以及添加新的候选小区所对应的CHO配置信息中的一项或多项。在本申请实施例中，对候选小区进行重新配置，也可以称为，对候选小区进行更新。换句话说，该第三RRC消息可用于对第一RRC消息中一个或多个候选下区的CHO配置信息进行更新。其中，更新可以包括上述修改、删除和添加中的一项或多项。
第三RRC消息中可以包含候选小区对应的delta配置信息或全配置信息。示例性地，delta配置信息可以理解为本次更新后的配置信息相比于最近的上一次更新后的配置信息(即本次更新前最新的配置信息)的变化部分。全配置信息可以理解为本次更新后的配置信息。
若第三RRC消息中包含候选小区对应的delta配置信息，则重新配置后的候选小区及其CHO配置信息可以根据第一RRC消息和第三RRC消息共同确定。例如，重新配置候选小区之前，根据第一RRC消息确定出的是第一候选小区集合中各候选小区对应的CHO配置信息，重新配置候选小区之后，根据第一RRC消息和第三RRC消息，或根据第三RRC消息，确定出的是第二候选小区集合中各候选小区对应的CHO配置信息，其中，第 二候选小区集合中各候选小区对应的CHO配置信息相对于第一候选小区集合中各候选小区对应的CHO配置信息的变化部分可以包括以下至少一种情况：第一候选小区集合和第二候选小区集合包括的小区相同，但是相同小区的对应的配置信息不同，例如，第一RRC消息中包含的配置信息包括小区1的承载配置信息1，第三RRC消息中包含的配置信息包括小区1的承载配置信息2；或者，第一候选小区集合和第二候选小区集合包括的小区不同，例如，第一RRC消息中包含的配置信息包括小区1的承载配置信息1，第三RRC消息中包含的配置信息包括小区2的承载配置信息2；或者，第一候选小区集合和第二候选小区集合包括的相同小区对应的配置信息不同，且第二候选小区包括第一候选小区中不包括的候选小区，例如，第一RRC消息中包含的配置信息包括小区1的承载配置信息1，第三RRC消息中包含的配置信息包括小区1的承载配置信息2、以及小区2对应的承载配置信息3；或者，第三RRC消息包括第一RRC消息中的部分小区对应的配置信息，例如，第一RRC消息中包含的配置信息包括小区1的承载配置信息1，小区2的承载配置信息1，第三RRC消息中包含的配置信息包括小区1的测量配置信息1。。
在一个示例中，第一RRC消息中包括小区#1、小区#2和小区#3的CHO配置信息，第三RRC消息中包括小区#2、小区#4和小区#5的CHO配置信息，则重新配置候选小区(或者说执行delta配置)之后，可以得到小区#1、小区#2、小区#3、小区#4和小区#5的CHO配置信息。其中小区#2的CHO配置信息可以是基于第一RRC消息中小区#2的CHO配置信息和第二RRC消息中小区#2的CHO配置信息共同确定。
在另一示例中，如果第三RRC消息用于添加新的候选小区，则终端设备可以进行新的候选小区的添加，包括添加新的候选小区对应的CHO执行条件和/或添加与新的候选小区对应的参数。如果第三RRC消息用于对已经配置过的某一个或多个候选小区进行CHO配置信息的修改，则终端设备可以根据第一RRC消息和第三RRC消息，或根据第三RRC消息，对已经配置过的上述一个或多个候选小区的CHO配置信息进行修改，比如可以修改与该候选小区对应的CHO执行条件和/或对应的参数。如果第三RRC消息用于对已经配置过的某一个或多个候选小区进行删除，则终端设备可以删除已经配置过的该一个或多个候选小区的CHO执行条件和对应的参数。即，重新配置候选小区之后，终端设备不会再对该删除了的候选小区进行CHO执行条件是否满足的判断，也不会切换至该候选小区。需要说明的是，当被删除的候选小区与未被删除的候选小区共用同一CHO执行条件时，终端设备可以保留该CHO执行条件。
若第三RRC消息用于进行全配置，或者说，若第三RRC消息中包含候选小区对应的全配置信息，则重新配置后的候选小区及其CHO配置信息可以根据第三RRC消息确定。
根据包含全配置信息的第三RRC消息重新配置候选小区后(或者说，根据包含全配置信息的第三RRC消息执行全配置)，得到的候选小区的CHO配置信息可以包括第三RRC消息中配置的一个或多个候选小区的CHO配置信息，但并不一定包括第一RRC消息中配置的一个或多个候选小区的CHO配置信息。事实上，执行全配置相当于用第三RRC消息中包含的一个或多个候选小区的CHO配置信息来覆盖/替代第一RRC消息原本已经配置的一个或多个候选小区的CHO配置信息。因此，若第一RRC消息中包含的某一候选小区未包含在第三RRC消息中，执行全配置之后，终端设备获取到的CHO配置信息中便不再包含该候选小区的CHO配置信息。若第一RRC消息中包含的某一候选小区的CHO 配置信息与第三RRC消息中包含的该候选小区的CHO配置信息不一致，执行全配置之后，终端设备获取到的CHO配置信息中包含的是第三RRC消息中包含的该候选小区的CHO配置信息，而不再包含第一RRC消息中包含的该候选小区的CHO配置信息。
在一个示例中，第一RRC消息中包括小区#1、小区#2和小区#3的CHO配置信息，第三RRC消息中包括小区#2、小区#4和小区#5的CHO配置信息，则执行全配置之后，获取到的候选小区的配置信息是小区#2、小区#4和小区#5的CHO配置信息。其中，小区#2的CHO配置信息可以是基于第三RRC消息中包含的小区#2的CHO配置信息确定，而不是基于第一RRC消息中包含的小区#2的CHO配置信息确定。
应理解，上文仅为便于理解，举例说明了执行delta配置和执行全配置之后得到的CHO配置信息，但这些示例不应对本申请构成任何限定。此外，第三RRC消息对候选小区进行重新配置的方法也不仅限于上文所列举的delta配置和全配置，本申请对此不作限定。
在步骤330中，终端设备确定出不能够遵从部分候选小区的CHO配置信息。
可以理解，上述部分候选小区可以是指，终端设备进行了候选小区重配之后，获取到的候选小区中的部分候选小区。但应注意，终端设备在执行步骤330时，基于重配的不同方式，终端设备所执行的操作也可能会有差异。
下面将针对delta配置和全配置两种方式分别说明终端设备在接收到第三RRC消息后执行步骤330的具体过程。
1、delta配置
终端设备可以根据第三RRC消息，或者根据第一RRC消息和第三RRC消息，确定出重配之后获取到的一个或多个候选小区，并可进一步确定该重配之后获取到的一个或多个候选小区中是否存在部分候选小区的CHO配置信息不能够被遵从的小区。
终端设备接收到第三RRC消息的时间并不是固定的。如前所述，终端设备在不同的时机接收到该第三RRC消息，所执行的操作可能会有差异。
假设终端设备在确定不能够遵从第一RRC消息中一个或多个候选小区中的部分候选小区的CHO配置信息之后，接收到该第三RRC消息，则终端设备可以进一步确定第三RRC消息中一个或多个候选小区中是否存在CHO配置信息不能够被遵从的候选小区。
第一RRC消息中的候选小区和第三RRC消息中的候选小区并不一定相同。
若通过第一RRC消息和第三RRC消息分别配置的候选小区不同，则可以认为该第三RRC消息中的候选小区的CHO配置信息是添加的候选小区的CHO配置信息。终端设备可以确定是否能够遵从该第三RRC消息中包含的各候选小区的CHO配置信息。
一种示例，第三RRC消息用于添加新的候选小区，比如，第一RRC消息中包括小区#1和小区#2的CHO配置信息，第三RRC消息中包括小区#3的CHO配置信息。假设终端设备在接收到第三RRC消息之前就已确定不能够遵从小区#1的CHO配置信息。在接收到第三RRC消息之后，终端设备可以确定是否能够遵从小区#3的CHO配置信息。
若第一RRC消息和第三RRC消息配置的候选小区有重复，则可以认为该第三RRC消息对该重复的候选小区的CHO配置信息进行了修改。终端设备可以判断是否能够遵从该重复的候选小区对应的更新后的CHO配置信息。此外，第三RRC消息还可能包括出第一RRC消息所配置的候选小区之外的其他候选小区的CHO配置信息，所述其他候选小区的CHO配置信息可以认为是想要通过该第三RRC消息添加的候选小区对应的CHO配置 信息。终端设备可以进一步确定是否能够遵从想要通过第三RRC消息添加的候选小区的CHO配置信息。
比如，第一RRC消息中包括小区#1和小区#2的CHO配置信息，第三RRC消息中包括小区#1和小区#3的CHO配置信息，即第三RRC消息对已经配置过的小区#1进行重配且添加新的候选小区#3。假设终端设备在接收到第一RRC消息之后，确定出不能够遵从小区#1的CHO配置信息。在接收到第三RRC消息之后，终端设备可以判断是否能够遵从第三RRC消息中包含的小区#3的CHO配置信息。此情况下，终端设备无需判断是否能够遵从第三RRC消息中包含的小区#1的CHO配置信息。
在方法200中已经说明，终端设备在基于第一RRC消息确定了部分候选小区的CHO配置信息能够被遵从之后，便可以执行后续步骤，比如步骤230确定CHO配置信息能够被遵从的候选小区中是否存在满足CHO执行条件的小区(即，目标小区)，或者，步骤240尝试切换至目标小区。但若在执行过程中接收到第三RRC消息，则终端设备可能会停止/中断上述操作，根据第三RRC消息，或根据第一RRC消息和第三RRC消息确定重配后的候选小区的CHO配置信息是否能够被遵从。
比如，第二RRC消息包含需要添加的候选小区对应的配置信息，或者，第三RRC消息中包含通过第一RRC消息配置了的候选小区(即该候选小区也包含在第一RRC消息中)对应的配置信息，但该候选小区对应的CHO配置信息需要更新，或者，第三RRC消息删除了至少一个候选小区，而被删除的该至少一个候选小区正好落在第一RRC消息配置的候选小区中，即第三RRC消息删除了第一RRC消息中包含的某个或某些候选小区，且包含在第三RRC消息中的该被删除的至少一个候选小区所对应的CHO配置信息能够被遵从，等等。
此情况下，终端设备可以先基于上文所述的方法，根据第一RRC消息和第三RRC消息，或者根据第三RRC消息，确定重配/更新后获取到的各候选小区的CHO配置信息，然后确定是否可以遵从各候选小区的CHO配置信息。
在确定不能够遵从更新后获取到的候选小区中的部分候选小区对应的CHO配置信息之后，或者说，在确定能够遵从更新后获取到的候选小区中的部分候选小区对应的CHO配置信息之后，终端设备可以继续执行后续流程。
应理解，终端设备确定重配之后获取到的一个或多个候选小区中是否存在部分候选小区的CHO配置信息不能够被遵从的具体实现方式并不一定限于上文所列举，本申请对于终端设备的具体实现方式不作限定。
可以理解的是，如果第三RRC消息用于重新配置候选小区，且第三RRC消息中包含的是delta配置信息，终端设备根据第一RRC消息和第三RRC消息，或者根据第三RRC消息，获取到重配后的各候选小区的CHO配置信息，然后，终端设备确定是否可以遵从该各候选小区的CHO配置信息。终端设备所确定出的CHO配置信息能够被遵从的候选小区可能包括下文所列举的一种或多种：
i)该候选小区包含在第一RRC消息中但未包含在第三RRC消息中，且第一RRC消息中包含的该候选小区对应的CHO配置信息能够被遵从；
ii)该候选小区包含在第三RRC消息中但未包含在第一RRC消息中，且第三RRC消息中包含的该候选小区对应的CHO配置信息能够被遵从；以及
iii)该候选小区包含在第一RRC消息和第三RRC消息中，且第一RRC消息中包含的该候选小区对应的CHO配置信息能够被遵从，且第三RRC消息中包含的该候选小区对应的CHO配置信息能够被遵从。
2、全配置
终端设备可以根据第三RRC消息，确定出重配之后获取到的一个或多个候选小区，并可进一步确定该重配之后获取到的一个或多个候选小区中是否存在部分候选小区的CHO配置信息不能够被遵从的小区。
在全配置的情况下，由于第三RRC消息中包含的一个或多个候选小区的CHO配置信息可以用于覆盖/替代第一RRC消息中包含的一个或多个候选小区的CHO配置信息，即，通过第三RRC消息进行重配/更新后，获取到的各候选小区的CHO配置信息即为第三RRC消息中包含的一个或多个候选小区的CHO配置信息。因此终端设备在接收到该第三RRC消息之后，可以将已经保存的候选小区的CHO配置信息(如第一RRC消息中包含的能够被终端设备遵从的候选小区所对应的CHO配置信息)删除。在这种情况下，终端设备可以根据第三RRC消息确定是否能够遵从第三RRC消息中的各候选小区的CHO配置信息。并在确定不能够遵从部分候选小区的CHO配置信息的情况下，或者说，在确定能够遵从部分候选小区的CHO配置信息的情况下，继续执行后续流程。
可以理解的是，若第三RRC消息用于重新配置候选小区，且第三RRC消息中包含的是全配置信息，则终端设备所确定出的CHO配置信息能够被遵从的候选小区包含在第三RRC消息中，且第三RRC消息中包含的该候选小区对应的CHO配置信息能够被遵从。在步骤340中，终端设备确定CHO配置信息能够被遵从的候选小区中是否存在满足CHO执行条件的小区。
终端设备执行步骤340的具体过程可以参考上文方法200中步骤230的相关描述，为了简洁，这里不再重复。
需要注意的是，由于终端设备在步骤340之前可能接收到第三RRC消息，则步骤340中所述CHO配置信息能够被遵从的候选小区可以是基于上述步骤330所确定出的候选小区。步骤340中所述CHO执行条件可以是更新后的CHO执行条件。正如上文中对CHO配置信息更新的具体方式中所述，更新后的CHO执行条件可能是基于第一RRC消息和第三RRC消息共同确定出的(例如，当第三RRC消息包含的delta配置信息中包含了CHO执行条件对应的delta参数时)，也可能是第三RRC消息中包含的候选小区的CHO执行条件。这分别对应于上文所述的delta配置和全配置的情况。由于CHO执行条件是包含在CHO配置信息中，上文中已经结合delta配置和全配置两种情况对候选小区重选配置/更新的具体过程做了说明，为了简洁，这里不再赘述。
但可以理解的是，与上文CHO配置信息能够被遵从的候选小区相对应，如果第三RRC消息用于重新配置候选小区，且第三RRC消息中包含的是delta配置信息，且第三RRC消息包含的delta配置信息中包含了CHO执行条件对应的delta参数，则，终端设备按上文所述的方法确定出CHO配置信息能够被遵从的候选小区后，然后，判断CHO配置信息能够被遵从的候选小区中是否存在满足CHO执行条件的小区。示例性地，终端设备从中所确定出的满足CHO执行条件的小区可以包括下文所列举的一种或多种：
i)该小区包含在第一RRC消息中但未包含在第三RRC消息中，且第一RRC消息中 包含的该小区对应CHO执行条件达到/满足；
ii)该小区包含在第三RRC消息中但未包含在第一RRC消息中，且第三RRC消息中包含的该小区对应CHO执行条件达到/满足；以及
iii)该小区包含在第一RRC消息和第三RRC消息中，且根据第一RRC消息和第三RRC消息确定出的该小区对应CHO执行条件达到/满足。
如果第三RRC消息用于重新配置候选小区，且第三RRC消息中包含的是全配置信息，则，终端设备按上文所述的方法确定出CHO配置信息能够被遵从的候选小区后，然后，判断CHO配置信息能够被遵从的候选小区中是否存在满足CHO执行条件的小区，具体的，终端设备从中所确定出的满足CHO执行条件的小区包含在第二RRC消息中，且第三RRC消息中包含的该小区对应CHO执行条件达到/满足。
终端设备可以在CHO配置信息能够被遵从的候选小区中存在或不存在满足CHO执行条件的小区时执行不同的操作。与方法200相似，若CHO配置信息能够被遵从的候选小区中存在满足CHO执行条件的小区，终端设备可以根据这些小区的CHO配置信息执行后续流程。例如执行步骤350，尝试切换到该满足CHO执行条件的小区；若终端设备成功切换到上述满足CHO执行条件的小区，则终端设备可以执行步骤360，与切换成功的小区进行通信，或者说，在切换成功的小区中通信。若CHO配置信息能够被满足的候选小区中不存在满足CHO执行条件的小区，或，尝试切换到上述满足CHO执行条件的小区失败，终端设备可以执行步骤370，发起重建立流程。
应理解，上述步骤350至370的具体过程与方法200中步骤240至260的具体过程相似，为了简洁，这里不再重复。需要注意的是，终端设备在尝试切换的过程中所使用的参数以及切换后通信所使用的参数均可以是候选小区重新配置/更新后所得到的最新的参数。
在另一种实现方式中，终端设备在步骤350中尝试切换到满足CHO执行条件的小区的流程失败，或者，若终端设备确定CHO配置信息能够被遵从的候选小区中不存在满足CHO执行条件的候选小区，则终端设备可以执行小区选择，若通过小区选择确定的满足S准则的小区包含在CHO配置信息能够被遵从的候选小区中，则可以尝试切换至该小区。若切换成功，则认为本轮CHO流程成功；若该满足S准则的小区未包含在CHO配置信息能够被遵从的候选小区中，或者，若终端设备未能成功切换至该满足S准则的小区，则可以执行步骤370，发起重建立流程。该实现方式例如可参考上文方法200中的流程A。为了简洁，这里不作详细说明。
或者，若终端设备未能成功切换至上述满足S准则的小区，该终端设备还可以再次执行小区选择，确定满足S准则的另一小区，并确定该满足S准则的另一小区是否包含在CHO配置信息能够被遵从的候选小区中，若是，终端设备可以再次尝试切换至该小区。如此重复执行，直到成功接入到某一小区中，与切换成功的小区进行通信；或直至终端设备维护的第二定时器超时，执行步骤370，终端设备发起重建立流程。该实现方式例如可以参考上文访法200中的流程A’。为了简洁，这里不作详细说明。
其中，该第二定时器可以是终端设备在步骤310中接收到第一RRC消息时启动，也可以是终端设备在步骤320中接收到第三RRC消息时启动，也可以是在终端设备确定出目标小区后开始执行步骤340时启动。本申请对此不作限定。该第二定时器的时长例如可 以是预定义的，如协议预定义，或者，第一RRC消息中可以包含第二定时器的相关信息，如第二定时器的有效时长等，或者，第三RRC消息中可以包含第二定时器的相关信息，如第二定时器的有效时长等。本申请对此不作限定。
在另一种实现方式中，若终端设备在步骤350中尝试切换到满足CHO执行条件的小区的流程失败，则终端设备可以再根据第一RRC消息和/或第三RRC消息、此时的信道状态等，进行评估、判断，尝试从CHO配置信息能被遵从的候选小区中再次确定出满足CHO执行条件的小区作为新的目标小区。终端设备可以尝试切换至新的目标小区，如此重复执行，直至所有的CHO配置信息能够被遵从的候选小区都被判断过是否满足CHO执行条件，或直至CHO配置信息能够被遵从且CHO执行条件被满足的所有的候选小区都被尝试切换过，或直至终端设备侧的第三定时器超时，可以执行步骤370，终端设备发起重建立流程。该第三定时器的时长例如可以是预定义的，如协议预定义，或者，第一RRC消息中可以包含第三定时器的相关信息，如第三定时器的有效时长等，或者，第三RRC消息中可以包含第三定时器的相关信息，如第三定时器的有效时长等。本申请对此不作限定。该实现方式例如可以参考上文访法200中的流程B。为了简洁，这里不作详细说明。
又或者，终端设备可以在对配置的候选小区中CHO配置信息能够被遵从且满足CHO执行条件的所有小区都尝试了切换，但均切换失败之后，进行小区选择，确定满足S准则的小区，并确定该满足S准则的小区是否包含在CHO配置信息能够被遵从的候选小区中。若是，终端设备尝试切换到该满足S准则的小区中。若切换成功，则本轮CHO流程成功。若该满足S准则的小区不包含在CHO配置信息能够被遵从的候选小区中，或者，若终端设备尝试切换到该满足S准则的小区中的流程失败，则可以执行步骤370，终端设备发起重建立流程。该实现方式例如可以参考上文方法200中的流程C。为了简洁，这里不作详细说明。
或者，若该满足S准则的小区不包含在CHO配置信息能够被遵从的候选小区中，或者，若终端设备尝试切换到该满足S准则的小区中的流程失败，则终端设备可以再次执行小区选择，如此重复执行，直至成功接入到某一小区，则本轮CHO流程成功；或直至第三定时器超时，则可以执行步骤370，终端设备发起重建立流程。该实现方式例如可以参考上文访法200中的流程C’。为了简洁，这里不作详细说明。
若终端设备在步骤340中确定CHO配置信息能够被满足的候选小区中不存在满足CHO执行条件的小区，或者说，若CHO配置信息能够被满足的候选小区中不存在这样的小区，其对应的CHO执行条件能够达到/满足，终端设备可以执行小区选择，确定满足S准则的小区，进而确定该满足S准则的小区是否包含在CHO配置信息能够被遵从的候选小区中。若该满足S准则的小区包含在CHO配置信息能够被遵从的候选小区中，该满足S准则的小区为目标小区，终端设备可以尝试切换至该满足S准则的小区。如果终端设备成功切换至该满足S准则的小区，则认为本轮CHO流程成功。若该满足S准则的小区未包含在CHO配置信息能够被遵从的候选小区中，或者，若终端设备未能成功切换至该满足S准则的小区，则可以执行步骤370，终端设备发起重建立流程。或者，终端设备也可以在确定CHO配置信息能够被满足的候选小区中不存在满足CHO执行条件的小区时，直接执行步骤370，发起重建立流程。终端设备发起重建立流程的具体过程在上文已经做了详述，为了简洁，这里不再重复。
终端设备发起重建立流程的具体过程在上文已经做了详述，为了简洁，这里不再重复。
在上述流程中，终端设备可以在本轮CHO流程成功的情况下，可以执行步骤360，与切换成功的小区进行通信。
应理解，终端设备执行小区选择并尝试切换及其后续流程可以参考上文方法200中的步骤的相关说明，为了简洁，这里不再赘述。
需要说明的是，终端设备执行步骤320，即接收第三RRC消息的时间并不固定。终端设备可能在接收到第三RRC消息之前，已经根据第一RRC消息确定出了CHO配置信息能够被遵从的部分候选小区，但在接收到第三RRC消息后，还需要进一步根据第一RRC消息和第三RRC消息，或根据第三RRC消息，获取到候选小区重新配置/更新后所对应的最新的CHO配置信息，然后，判断该最新的CHO配置信息是否能够被遵从。终端设备在执行步骤320之前也可能已经根据第一RRC消息确定出了满足CHO执行条件的目标小区，在接收到第三RRC消息后，终端设备可以忽略/删除该第三RRC消息，尝试切换至该已经确定出的目标小区，或者，终端设备需要进一步根据候选小区重新配置/更新后所对应的最新的CHO配置信息确定该最新的CHO配置信息是否能够被遵从，进而确定CHO配置信息能被遵从的候选小区中是否存在满足CHO执行条件的小区，以尝试切换。终端设备甚至还可以在执行步骤320之前已经确定出目标小区，并正在尝试切换到该目标小区。在接收到第三RRC消息后，终端设备可以忽略/删除该第三RRC消息，继续尝试切换至该目标小区，或者，终端设备需要进一步根据候选小区重新配置/更新后所对应的最新的CHO配置信息确定该最新的CHO配置信息是否能够被遵从，进而确定CHO配置信息能被遵从的候选小区中是否存在满足CHO执行条件的小区，以尝试切换。图3中的流程仅为示例，并未对上述流程予以示出。
应理解，上述CHO执行条件具体可以是指基于接收到的第三RRC消息重配后获得的CHO配置信息中的CHO执行条件。该CHO执行条件可能与之前在第一RRC消息中包含的CHO执行条件相同，也可能与在第一RRC消息中包含的CHO执行条件不同，本申请对此不作限定。
另外，虽然图中将各个步骤按照先后顺序示出，但这不应对本申请构成任何限定。比如终端设备在执行步骤330时，有可能在步骤320之前确定出了一部分CHO配置信息能够被遵从的候选小区，在步骤320之后，终端设备可以根据第三RRC消息，或第一RRC消息和第三RRC消息(如，当第三RRC消息用于添加新的候选小区，和/或修改第一RRC消息中已经配置过的候选小区时)，重新确定出CHO配置信息能够被遵从的候选小区。诸如此类，为了简洁，这里不一一列举说明。
此外，若终端设备确定不能够遵从第一RRC消息和/或第三RRC消息中的全部候选小区的CHO配置信息，则终端设备丢弃所有的不能遵循的候选小区所分别对应的CHO配置信息，终端设备可以保持在源网络设备(即终端设备维持与源网络设备的RRC连接/数据传输)，可选地，终端设备给源网络设备发送一条RRC消息，以通知RRC重配置失败，可选地，该消息中包含不能遵循的候选小区的信息(如PCI、频点信息、测量标识等)；
另外，如果第三RRC消息中携带全配置信息，且第三RRC消息中的部分候选小区的CHO配置信息不能够被遵从。在这种情况下，终端设备例如可以执行小区选择，确定出 满足S准则的小区。若终端设备所确定出的满足S准则的小区是第三RRC消息中配置的候选小区，且其对应的CHO配置信息也能够被遵从，则终端设备可以尝试切换到该小区。若终端设备成功切换到该小区，则可以在该小区中通信；否则，可以发起重建立流程，或执行上述流程A，这里不做赘述。
应理解，当终端设备基于小区选择确定出的满足S准则的小区属于第三RRC消息中的CHO配置信息能被遵从的候选小区时，或当终端设备基于小区选择确定出的满足S准则的小区属于第一RRC消息中的CHO配置信息能被遵从的候选小区时，或当终端设备基于小区选择确定出的满足S准则的小区属于第一RRC消息和第三RRC消息中的CHO配置信息能被遵从的候选小区时，终端设备尝试切换的过程可以参考上文方法200中步骤270至步骤290中的相关描述，为了简洁，这里不再重复。
基于上述技术方案，终端设备可以基于接收到的第三RRC消息进行候选小区的重新配置/更新。在确定不能够遵从部分候选小区的CHO配置信息的情况下，不发起重建立流程，优先在CHO配置信息能够被遵从的那部分候选小区中尝试寻找一个满足CHO执行条件的小区，并尝试切换到该小区；或者也可以通过小区选择确定一个满足S准则的终端设备如果未能成功切换至满足CHO执行条件的小区，或者，在CHO配置信息能够被遵从的候选小区中找不出满足CHO执行条件的小区，仍然可以基于S准则来选择一个适合切换的小区来尝试切换。终端设备基于不同的维度来寻找适合切换的小区，而不限于满足CHO执行条件的小区。从而有利于终端设备更大几率地寻找到合适的小区来尝试切换，更大程度地避免重建立流程造成的时延、复杂度，避免较长时间的通信中断对用户体验的影响，有利于提高系统可靠性，保证系统性能，有利于提高用户体验。
当然，终端设备在确定不能够遵从部分候选小区的CHO配置信息的情况下的处理方式并不限于上述方法200中所提供的方法。下文结合另一实施例详细说明终端设备在确定不能够遵从部分候选小区的CHO配置信息的情况下的处理方式。
图4是本申请另一实施例提供的通信方法400的示意性流程图。如图4所示，该方法400可以包括步骤410至步骤470。下面详细说明方法400中的各个步骤。
在步骤410中，终端设备接收第一RRC消息，该第一RRC消息包括一个或多个候选小区的CHO配置信息。该第一RRC消息例如可以是源网络设备发送的。
在步骤420中，终端设备确定不能够遵从该一个或多个候选小区中部分候选小区的CHO配置信息。
关于步骤410和步骤420的详细说明可以参考上文方法200中步骤210和步骤220的详细说明，为了简洁，这里不再重复。
在步骤430中，终端设备确定满足S准则的第一小区。
这里，为便于区分和说明，将满足S准则的小区记为第一小区。该第一小区例如可以是由终端设备通过小区选择而选择出来的小区。可以理解的是，该第一小区可能是第一RRC消息所配置的候选小区中的小区，也可能不是第一RRC消息所配置的候选小区中的小区；第一小区可能是CHO配置信息能够被满足的候选小区，也可能是CHO配置信息不能够被满足的候选小区。
当终端设备确定一个或多个候选小区中的部分候选小区的CHO配置信息不能够被遵从时，即步骤420后，终端设备可以执行小区选择，例如，终端设备可以通过执行小区选 择来选择出满足S准则的第一小区。终端设备执行小区选择的具体过程可以参考现有技术，为了简洁，这里不做详述。
在步骤440中，终端设备确定第一小区是否包含在CHO配置信息能够被遵从的候选小区中。
终端设备在步骤420中已经确定有部分候选小区的CHO配置信息不能够被遵从，也就是说，还有部分候选小区的CHO配置信息是能够被遵从的。终端设备可以确定上述步骤430中所确定的第一小区是否包含在CHO配置信息能够被遵从的候选小区中。
若该第一小区包含在CHO配置信息能够被遵从的候选小区中，则该第一小区可以确定为目标小区，可以执行步骤450，尝试切换到该第一小区，例如，终端设备与该第一小区进行随机接入过程，当随机接入过程成功，终端设备向该第一小区发送RRC重配置完成消息；或者，如果第一RRC消息中包含该第一小区对应的RACH-less切换的相关信息，则终端设备跳过RACH过程，根据RACH-less切换的相关信息，向该第一小区发送RRC重配置完成消息；并在切换成功后，执行步骤460，与成功切换的小区(例如第一小区)进行通信，或者说，在成功切换的小区中通信。若该第一小区未包含在CHO配置信息能够被遵从的候选小区中(例如，第一小区未包含在第一RRC消息中，或者，第一小区包含在第一RRC消息中但其对应的CHO配置信息不能被遵从)，或，若终端设备尝试切换到第一小区失败，则可以执行步骤470，发起重建立流程。
在另一种实现方式中，上述步骤470也可以被替换为如下流程：
终端设备可以再次进行小区选择，如终端设备确定满足S准则的另一小区，若该小区包含在能够被遵从的候选小区中，尝试切换，如此重复执行，直至切换成功或，直至第四定时器超时，执行步骤470，发起重建立流程。其中，该第四定时器可以是终端设备在步骤410中接收到第一RRC消息时启动，也可以是在终端设备确定出该第一小区后开始执行步骤450时启动。本申请对此不作限定。该第四定时器的时长例如可以是预定义的，如协议预定义，或者，第一RRC消息中可以包含第四定时器的相关信息，如第四定时器的有效时长。本申请对此不作限定。
此外，终端设备在确定了CHO配置信息能够被遵从的候选小区之后，可以保存这些候选小区的CHO配置信息，以备后续流程使用。终端设备也可以在确定上述满足S准则的第一小区包含在CHO配置信息能够被遵从的候选小区的情况下，保存该第一小区的CHO配置信息；在第一小区不包含在CHO配置信息能够被遵从的候选小区的情况下，不保存该第一RRC消息中的各候选小区的CHO配置信息。相比于前一种方法而言，终端设备仅需保存第一小区的CHO配置信息，可以减小对终端设备的存储空间的占用。
基于上述技术方案，终端设备可以在确定不能够遵从部分候选小区的CHO配置信息的情况下，不发起重建立流程，而是优先尝试切换。终端设备可以通过小区选择，确定一个满足S准则的小区，并在该小区包含在CHO配置信息能够被遵从的候选小区的情况下，尝试切换至该小区。由此可以避免重建立流程造成的时延、复杂度，避免较长时间的通信中断对用户体验的影响，有利于提高系统可靠性，保证系统性能，有利于提高用户体验。
如前所述，终端设备在保持着与源网络设备之间的RRC连接的情况下，还可能接收到其他RRC消息。下面结合具体实施例详细说明终端设备成功接收到用于重新配置的第三RRC消息的情况下的具体流程。
图5是本申请再一实施例提供的通信方法500的示意性流程图。如图5所示，该方法500可以包括步骤510至步骤580。下面详细说明方法500中的各步骤。
在步骤510中，终端设备接收第一RRC消息，该第一RRC消息包括一个或多个候选小区的CHO配置信息。该第一RRC消息例如可以是源网络设备发送的。
关于步骤510的详细说明可以参考上文方法200中步骤210的详细说明，为了简洁，这里不再重复。
在步骤520中，终端设备接收第三RRC消息，该第三RRC消息用于重新配置候选小区。该第三RRC消息例如也可以是由源网络设备发送的。
与第一RRC消息相似，该第三RRC消息也可以包括一个或多个候选小区的CHO配置信息，以用于重新配置候选小区。例如，该第三RRC消息可用于修改或释放第一RRC消息中配置过的候选小区，和/或，添加新的小区(如该新的小区不包含在第一RRC消息配置过的候选小区中)作为候选小区。
关于第三RRC消息的相关说明可以参考上文方法300中步骤320的相关说明，为了简洁，这里不再重复。
若终端设备对该第三RRC消息的完整性保护校验成功，则可以解析出该第三RRC消息中包括的一个或多个候选小区的CHO配置信息。如前所述，该第三RRC消息用于重新配置候选小区，故，第三RRC消息中的一个或多个候选小区与第一RRC消息中的一个或多个候选小区可以相同或不同，本申请实施例对此不做限定。由于上文方法300中的步骤320中已经结合多个示例对更新的方式和过程做了详细说明，为了简洁，这里不再重复。
在步骤530中，终端设备确定出不能够遵从部分候选小区的CHO配置信息。
在本实施例中，由于第三RRC消息用于重新配置候选小区(例如，用于修改或释放第一RRC消息中配置过的候选小区，和/或，用于添加新的小区(如，该新的小区不包含在第一RRC消息配置过的候选小区中)作为候选小区)，故步骤530中的所述部分候选小区可以包含在更新后得到的候选小区中，所述部分候选小区的CHO配置信息可以包含在重配/更新后得到的候选小区所对应的最新的CHO配置信息中。
如前所述，第三RRC消息用于重新配置候选小区时，第三RRC消息中可以包含但不限于delta配置信息，或者，第三RRC消息中可以包含但不限于全配置信息。或者理解为，重新配置候选小区时，可以使用delta配置或全配置的方法。在本实施例中，基于不同的方式，终端设备执行的操作可能会有所差异。
比如，第三RRC消息中包含的是delta配置信息，终端设备执行步骤530，即终端设备可以根据第一RRC消息和第三RRC消息，或根据第三RRC消息，确定出不能够遵从部分候选小区的CHO配置信息。
或比如，第三RRC消息中包含的是全配置信息，终端设备执行步骤530，即终端设备可以直接根据第三RRC消息，确定出不能够遵从部分候选小区的CHO配置信息。
终端设备执行步骤530的具体过程与上文方法300中的步骤330的相关说明。由于上文方法300中已经结合delta配置和全配置分别对终端设备的具体实现方式做了详细说明，为了简洁，这里不再重复。
在步骤540中，终端设备确定满足S准则的第三小区。
这里，为便于区分和说明，将满足S准则的小区记为第三小区。该第三小区例如可以 是由终端设备通过小区选择而选择出来的小区。可以理解的是，该第三小区可能是第一RRC消息所配置的候选小区中的小区，也可能不是第一RRC消息所配置的候选小区中的小区；第三小区可能是CHO配置信息能够被满足的候选小区，也可能是CHO配置信息不能够被满足的候选小区。
步骤530后，终端设备可以执行小区选择，例如，终端设备可以通过执行小区选择来确定出满足S准则的第三小区。终端设备执行小区选择的具体过程可以参考现有技术，为了简洁，这里不做详述。
在步骤550中，终端设备确定第三小区是否包含在CHO配置信息能够被遵从的候选小区中。
终端设备在步骤530中已经确定有部分候选小区的CHO配置信息不能够被遵从，也就是说，还有部分候选小区的CHO配置信息是能够被遵从的。终端设备可以确定上述步骤540中所确定出的第三小区是否包含在CHO配置信息能够被遵从的候选小区中。
若该第三小区包含在CHO配置信息能够被遵从的候选小区中，则该第三小区可以确定为目标小区，可以执行步骤560，尝试切换到该第三小区；并在切换成功后，执行步骤570，与第三小区进行通信，或者说，在第三小区中通信。若该第三小区未包含在CHO配置信息能够被遵从的候选小区中(例如，第三小区未包含在第一RRC消息中，或者，第三小区包含在第一RRC消息中但其对应的CHO配置信息不能被遵从)，或，若终端设备未能成功切换到第三小区，或者说，切换失败，则可以执行步骤580，发起重建立流程。
在另一种实现方式中，上述步骤580也可以被替换为如下流程：
终端设备确定满足S准则的第四小区，并可以进一步确定第四小区是否包含在CHO配置信息能够被遵从的候选小区中。若该第四小区包含在CHO配置信息能够被遵从的候选小区中，则该第四小区为新的目标小区，终端设备可以尝试切换到该第四小区。若切换成功，则终端设备可以与第四小区进行通信，或者说，在第四小区中通信。若该第四小区未包含在CHO配置信息能够被遵从的候选小区中，或，若终端设备尝试切换到第四小区失败，则，终端设备再次进行小区选择，如终端设备确定满足S准则的又一小区，如此重复执行，直至切换成功或，直至第五定时器超时，则可以执行步骤580，发起重建立过程。其中，该第五定时器可以是终端设备在步骤510中接收到第一RRC消息时启动，或，该第五定时器可以是终端设备在步骤520中接收到第三RRC消息时启动，或，也可以是在终端设备确定出第三小区后启动，或，也可以是在终端设备确定出该第四小区后启动。本申请对此不作限定。该第五定时器的时长例如可以是预定义的，如协议预定义，或者，第一RRC消息中可以包含第五定时器的相关信息，如第五定时器的有效时长，或者，第三RRC消息中可以包含第五定时器的相关信息，如第五定时器的有效时长。本申请对此不作限定。
终端设备尝试切换到该满足S准则的某一小区(如上述第三小区、第四小区等)的具体过程可以与现有技术相同。并且上文方法400中的步骤450也已经举例说明了终端设备尝试切换到某一小区的过程，为了简洁，这里不再重复。
此外，终端设备在确定了CHO配置信息能够被遵从的候选小区之后，可以保存这些候选小区的CHO配置信息，以备后续流程使用。终端设备也可以在确定上述满足S准则的第三小区包含在CHO配置信息能够被遵从的候选小区的情况下，保存该第三小区的 CHO配置信息；在确定上述满足S准则的第三小区不包含在CHO配置信息能够被遵从的候选小区的情况下，不保存更新后得到的各候选小区的CHO配置信息。相比于前一种方法而言，终端设备仅需保存第三小区的CHO配置信息，可以减小对终端设备的存储空间的占用。
需要说明的是，终端设备执行步骤520，即接收第三RRC消息的时间并不固定。终端设备可能在接收到第三RRC消息之前，已经根据第一RRC消息确定出了CHO配置信息能够被遵从的部分候选小区，但在接收到第三RRC消息后，还需要进一步根据第一RRC消息和第三RRC消息，或根据第三RRC消息，获取到候选小区重新配置/更新后所对应的最新CHO配置信息，然后，判断该最新的CHO配置信息是否能够被遵从。终端设备在执行步骤520之前也可能已经确定出满足S准则的第一小区包含在CHO配置信息能够被遵从的候选小区中(如在步骤520前，终端设备已经执行了方法400中的步骤410-步骤440)，但在接收到第三RRC消息之后，终端设备可以忽略/删除该第三RRC消息，继续完成在接收到第三RRC消息前在进行的流程；或者，终端设备需要进一步根据候选小区重新配置/更新后所对应的最新的CHO配置信息确定该最新的CHO配置信息是否能够被遵从，若最新的CHO配置信息部分不能被遵从，则终端设备确定满足S准则的第三小区，并当第三小区包含在更新后得到的候选小区中时，尝试切换到该第三小区。图5中的流程仅为示例，示出了上文步骤510至步骤580的流程，而并未对上述其他可选的流程予以示出。
另外，虽然图5中将各个步骤按照先后顺序示出，但这不应对本申请构成任何限定。比如终端设备在执行步骤530时，有可能在步骤520之前确定出了一部分CHO配置信息能够被遵从的候选小区，在步骤520之后，终端设备可以根据第三RRC消息，或第一RRC消息和第三RRC消息(如，当第三RRC消息用于添加新的候选小区，和/或修改第一RRC消息中已经配置过的候选小区时)，重新确定出CHO配置信息能够被遵从的候选小区。诸如此类，为了简洁，这里不一一列举说明。
基于上述技术方案，终端设备可以基于接收到的第三RRC消息进行候选小区的重新配置/更新。在确定不能够遵从部分候选小区的CHO配置信息的情况下，不发起重建立流程，而是优先尝试切换。终端设备可以通过小区选择，确定一个满足S准则的小区，并在该小区包含在CHO配置信息能够被遵从的候选小区的情况下，尝试切换至该小区。由此可以避免重建立流程造成的时延、复杂度，避免较长时间的通信中断对用户体验的影响，有利于提高系统可靠性，保证系统性能，有利于提高用户体验。
在上文所示的各实施例中，终端设备在确定出部分候选小区的CHO配置信息不能够被遵从的时候，由于CHO配置信息包含CHO执行条件和各候选小区对应的参数，对每一个候选小区的CHO配置信息都进行评估，可能会带来较大的工作量。因此，下文中另提供一种方法，可以在避免重建立流程的基础上，进一步减小终端设备的工作量。
图6是本申请又一实施例提供的通信方法的示意性流程图。如图6所示，该方法600可以包括步骤610至步骤660。下面详细说明方法600中的各步骤。
在步骤610中，终端设备接收第一RRC消息，该第一RRC消息包括一个或多个候选小区的CHO配置信息。该第一RRC消息例如可以是源网络设备发送的。
关于步骤610的详细说明可以参考上文方法200中步骤210的详细说明，为了简洁， 这里不再重复。
在步骤620中，终端设备在不能够遵从该一个或多个候选小区中部分候选小区的CHO执行条件的情况下，确定一个或多个候选小区中CHO执行条件能够被遵从的部分候选小区中存在满足CHO执行条件的至少一个第一候选小区。
如前所述，候选小区的CHO配置信息可以包括CHO执行条件和该候选小区对应的参数。在本实施例中，终端设备可以先确定是否能够遵从各候选小区的CHO执行条件，而暂不确定是否能够遵从各候选小区对应的参数。
一方面，由于终端设备仅需确定是否遵从各候选小区的CHO执行条件，相比于确定是否遵从各候选小区的CHO配置信息而言，终端设备的工作量减小，处理时间缩短；另一方面，由于可能存在多个候选小区共用CHO执行条件的情况，可以进一步减小终端设备的工作量。
可以理解，终端设备确定不能够遵从该一个或多个候选小区中的部分候选小区的CHO执行条件，也就是，终端设备能够遵从该一个或多个候选小区中的其他剩下的一个或多个候选小区的CHO执行条件。
终端设备可以进一步从上述CHO执行条件能够被遵从的一个或多个候选小区中确定是否存在满足CHO执行条件的候选小区。下文中为便于区分和说明，将CHO执行条件能够被遵从的一个或多个候选小区中满足CHO执行条件的候选小区记为第一候选小区。若终端设备在步骤620中可以确定出至少一个第一候选小区，则可以继续执行步骤630，确定该至少一个第一候选小区中是否存在CHO配置信息中所对应的参数(即CHO配置信息中包含的候选小区对应的参数)能够被遵从的小区。
这里，确定该至少一个第一候选小区中是否存在CHO配置信息中所对应的参数能够被遵从的小区可以这样理解：从该至少一个第一候选小区中寻找这样一个小区，该小区所对应的参数(即包含在CHO配置信息中的该小区所对应的参数)能够被遵从。基于上文对目标小区的定义，该小区可以被定义为目标小区。换句话说，步骤630具体可以是指，确定该至少一个第一候选小区中是否存在目标小区，该目标小区所对应的包含在CHO配置信息中的参数能够被遵从。
若终端设备确定该至少一个第一候选小区中存在所对应的参数能够被遵从的小区，则该第一候选小区中所对应的参数能够被遵从的小区为目标小区，可以执行步骤640，尝试切换到CHO配置信息中所对应的参数能够被遵从的小区。即，终端设备确定至少一个第一候选小区中存在目标小区，则尝试切换至目标小区。
可以理解的是，目标小区的数量可能为一个，也可能为多个。终端设备在尝试切换至目标小区的过程中，可以依次在不同的时刻尝试切换至各个目标小区，最终接入至其中的一个。终端设备尝试切换至目标小区的具体过程在上文方法200中的步骤240中做了详细说明，为了简洁，这里不再重复。
此外，终端设备在确定上述至少一个第一候选小区中存在CHO配置信息中所对应的参数能够被遵从的小区的情况下，可以保存该小区对应的CHO配置信息，以备后续流程使用。
若终端设备切换成功，则可以执行步骤650，与切换成功的小区进行通信，或者说，在切换成功的小区中通信。若终端设备切换失败，或，若终端设备确定上述至少一个第一 候选小区中不存在CHO配置信息中所对应的参数能够被遵从的小区，则可以执行步骤660，发起重建立流程。
在另一种实现方式中，若终端设备在步骤640中尝试切换到CHO配置信息中所对应的参数能够被遵从的小区失败，或者，若终端设备在步骤630中确定至少一个第一候选小区中不存在所对应的参数能够被遵从的候选小区，则终端设备可以执行小区选择，若通过小区选择确定的满足S准则的小区包含在CHO配置信息能够被遵从的候选小区中，则可以尝试切换至该小区。若切换成功，则认为本轮CHO流程成功；若该满足S准则的小区未包含在CHO配置信息能够被遵从的候选小区中，或者，若终端设备未能成功切换至该满足S准则的小区，则可以执行步骤660，发起重建立流程。
或者，若终端设备未能成功切换至上述满足S准则的小区，该终端设备还可以再次执行小区选择，确定满足S准则的另一小区，并确定该满足S准则的另一小区是否包含在CHO配置信息能够被遵从的候选小区中，若是，终端设备可以再次尝试切换至该小区。如此重复执行，直到成功接入到某一小区中，与切换成功的小区进行通信；或直至终端设备维护的第六定时器超时，执行步骤660，终端设备发起重建立流程。
其中，该第六定时器可以是终端设备在步骤610中接收到第一RRC消息时启动，也可以是在终端设备确定出目标小区后开始执行步骤640时启动。本申请对此不作限定。该第六定时器的时长例如可以是预定义的，如协议预定义，或者，第一RRC消息中可以包含第六定时器的相关信息，如第六定时器的有效时长等。本申请对此不作限定。
在另一种实现方式中，若终端设备在步骤640中尝试切换到CHO配置信息中所对应的参数能够被遵从的小区失败，则终端设备可以再根据第一RRC消息、此时的信道状态等，进行评估、判断，尝试从CHO执行条件能被遵从的候选小区中再次确定出满足CHO执行条件的小区，如能确定出，再判断确定出的该小区所对应的参数是否能被遵从，若能够被遵从，则将其作为新的目标小区。终端设备可以尝试切换至新的目标小区，如此重复执行，直至所有的CHO执行条件能够被遵从的候选小区都被判断过是否满足CHO执行条件，或直至所有CHO执行条件能够被遵从的候选小区中的能满足CHO执行条件的小区都被判断过其相对应的参数是否能被遵从，或直至满足CHO执行条件的候选小区中所对应的参数能够被遵从的所有候选小区都被尝试切换过，或直至终端设备侧的第七定时器超时，可以执行步骤660，终端设备发起重建立流程。该第七定时器的时长例如可以是预定义的，如协议预定义，或者，第一RRC消息中可以包含第七定时器的相关信息，如第七定时器的有效时长等。终端设备接收到第一RRC消息后启动第七定时器，或者，执行步骤640时启动第七定时器。本申请对此不作限定。
又或者，终端设备可以在对配置的候选小区中CHO配置信息能够被遵从且满足CHO执行条件的所有小区都尝试了切换，但均切换失败之后，进行小区选择，确定满足S准则的小区，并确定该满足S准则的小区是否包含在CHO配置信息能够被遵从的候选小区中。若是，终端设备尝试切换到该满足S准则的小区中。若切换成功，则本轮CHO流程成功。若该满足S准则的小区不包含在CHO配置信息能够被遵从的候选小区中，或者，若终端设备尝试切换到该满足S准则的小区中的流程失败，则可以执行步骤660，终端设备发起重建立流程。
或者，若该满足S准则的小区不包含在CHO配置信息能够被遵从的候选小区中，或 者，若终端设备尝试切换到该满足S准则的小区中的流程失败，则终端设备可以再次执行小区选择，如此重复执行，直至成功接入到某一小区，则本轮CHO流程成功；或，第七定时器超时，则可以执行步骤660，终端设备发起重建立流程。
若终端设备在步骤630中确定至少一个第一候选小区中不存在所对应的参数能够被遵从的候选小区，终端设备可以执行小区选择，确定满足S准则的小区，进而确定该满足S准则的小区是否包含在CHO配置信息能够被遵从的候选小区中。若该满足S准则的小区包含在CHO配置信息能够被遵从的候选小区中，该满足S准则的小区为目标小区，终端设备可以尝试切换至该满足S准则的小区。如果终端设备成功切换至该满足S准则的小区，则认为本轮CHO流程成功。若该满足S准则的小区未包含在CHO配置信息能够被遵从的候选小区中，或者，若终端设备未能成功切换至该满足S准则的小区，则可以执行步骤660，终端设备发起重建立流程。或者，终端设备也可以在确定至少一个第一候选小区中不存在所对应的参数能够被遵从的候选小区时，直接执行步骤660，发起重建立流程。终端设备发起重建立流程的具体过程在上文已经做了详述，为了简洁，这里不再重复。
终端设备发起重建立流程的具体过程在上文已经做了详述，为了简洁，这里不再重复。
在上述流程中，终端设备可以在本轮CHO流程成功的情况下，可以执行步骤650，与切换成功的小区进行通信。
基于上述技术方案，终端设备可以在确定出不能够遵从部分候选小区的CHO执行条件的情况下，不发起重建立流程，而是优先尝试切换。终端设备可以从CHO执行条件被遵从的候选小区中确定出满足CHO执行条件的小区，进而再从确定出的满足CHO执行条件的小区中确定出CHO配置信息中所对应的参数能够被遵从的小区，以尝试切换至该小区；或者，也可以通过小区选择确定一个满足S准则的终端设备如果未能成功切换至满足CHO执行条件的小区，或者，在CHO配置信息能够被遵从的候选小区中找不出满足CHO执行条件的小区，仍然可以基于S准则来选择一个适合切换的小区来尝试切换。终端设备基于不同的维度来寻找适合切换的小区，而不限于满足CHO执行条件的小区。从而有利于终端设备更大几率地寻找到合适的小区来尝试切换，更大程度地避免重建立流程造成的时延、复杂度，避免较长时间的通信中断对用户体验的影响，有利于提高系统可靠性，保证系统性能，有利于提高用户体验。
另一方面，由于终端设备在接收到第一RRC消息后仅需评估是否能够各候选小区的CHO执行条件，在确定出满足CHO执行条件的小区之后，评估这些小区的CHO配置信息中的参数是否能够被遵从，可以减小评估的候选小区的数量，减小终端设备的工作量，降低实现复杂度。
如前所述，终端设备在保持着与源网络设备之间的RRC连接的情况下，还可能接收到其他RRC消息。下面结合具体实施例详细说明终端设备成功接收到用于重新配置的第三RRC消息的情况下的具体流程。
图7是本申请再一实施例提供的通信方法700的示意性流程图。如图7所示，该方法700可以包括步骤710至步骤770。下面详细说明方法700中的各步骤。
在步骤710中，终端设备接收第一RRC消息，该第一RRC消息包括一个或多个候选小区的CHO配置信息。该第一RRC消息例如可以是源网络设备发送的。
关于步骤710的详细说明可以参考上文方法200中步骤210的详细说明，为了简洁， 这里不再重复。
在步骤720中，终端设备接收第三RRC消息，该第三RRC消息用于重新配置候选小区。该第三RRC消息例如也可以是由源网络设备发送的。
与第一RRC消息相似，该第三RRC消息也可以包括一个或多个候选小区的CHO配置信息，以用于重新配置候选小区。例如，该第三RRC消息可用于修改或释放第一RRC消息中配置过的候选小区，和/或，添加新的小区(如该新的小区不包含在第一RRC消息配置过的候选小区中)作为候选小区。
关于第三RRC消息的相关说明可以参考上文方法300中步骤320的相关说明，为了简洁，这里不再重复。
若终端设备对该第三RRC消息的完整性保护校验成功，则可以解析出该第三RRC消息中包括的一个或多个候选小区的CHO配置信息。如前所述，该第三RRC消息用于重新配置候选小区，故，第三RRC消息中的一个或多个候选小区与第一RRC消息中的一个或多个候选小区可以相同或不同，本申请实施例对此不做限定。由于上文方法300中的步骤320中已经结合多个示例对更新的方式和过程做了详细说明，为了简洁，这里不再重复。
在步骤730中，终端设备在一个或多个候选小区中的部分候选小区的CHO执行条件不能够被遵从的情况下，确定CHO执行条件能够被遵从的部分候选小区中存在满足CHO执行条件的至少一个第二候选小区。
在本实施例中，由于第三RRC消息用于重新配置候选小区，故步骤730中的所述一个或多个候选小区可以是重新配置后得到的候选小区。可选地，所述CHO执行条件可以是重新配置后得到的CHO执行条件。具体来说，该CHO执行条件可以是重新配置后得到的CHO配置信息中的CHO执行条件，故，该CHO执行条件可能未做更新，也可能做了更新，本申请对此不作限定。
为了便于区分和说明，本实施例中将CHO执行条件能够被遵从的部分候选小区中满足CHO执行条件的小区记为第二候选小区。终端设备在步骤730中可能确定出至少一个第二候选小区。
如前所述，第三RRC消息用于重新配置候选小区时，第三RRC消息中可以包含但不限于delta配置信息，或者，第三RRC消息中可以包含但不限于全配置信息。或者理解为，重新配置候选小区时，可以使用delta配置或全配置的方法。在本实施例中，基于不同的方式，终端设备执行的操作可能会有所差异。
比如，第三RRC消息中包含的是delta配置信息，终端设备执行步骤730，即终端设备可以根据第一RRC消息和第三RRC消息，或根据第三RRC消息，确定是否能够遵从候选小区的CHO执行条件，并在不能够遵从部分候选小区的CHO执行条件的情况下，从CHO执行条件能够被遵从的另一部分候选小区中确定满足CHO执行条件的第二候选小区。
或比如，第三RRC消息中包含的是全配置信息，终端设备执行步骤730，即终端设备可以根据第三RRC消息，确定是否能够遵从候选小区的CHO执行条件，并在不能够遵从部分候选小区的CHO执行条件的情况下，从CHO执行条件能够被遵从的另一部分候选小区中确定满足CHO执行条件的第二候选小区。
可以理解的是，由于终端设备接收到该第三RRC消息的时间并不是固定的。基于该 终端设备对该第三RRC消息的接收时机的不同，终端设备的操作可能会有差异。
比如，终端设备可能在接收到第三RRC消息之前，根据第一RRC消息中各候选小区的CHO配置信息，确定不能够遵从第一RRC消息配置的部分候选小区的CHO执行条件。在接收到第三RRC消息之后，终端设备可能需要进一步基于更新后得到的候选小区的CHO配置信息确定是否能够遵从更新后得到的候选小区的CHO执行条件。
基于第三RRC消息是进行候选小区的修改、删除，还是添加新的候选小区，终端设备的具体实现可能会有所差别。由于上文方法300中的步骤330中已经结合不同的情况详细说明了终端设备确定是否能够遵从重配/更新后获取到的候选小区的CHO配置信息的具体方法，终端设备确定能够遵从更新后得到的CHO执行条件的具体方法与之相似，为了简洁，这里不再重复。
如果第三RRC消息用于重新配置候选小区，且第二消息中包含的是delta配置信息，终端设备根据第一RRC消息和第三RRC消息，或者根据第三RRC消息，获取到重配/更新后的各候选小区的CHO配置信息，然后，终端设备确定是否可以遵从各候选小区的CHO执行条件。终端设备所确定出的CHO执行条件能够被遵从的候选小区可能包括下文列举的一种或多种：
i)该候选小区包含在第一RRC消息中但未包含在第三RRC消息中，且第一RRC消息中包含的该候选小区对应的CHO执行条件能够被遵从；
ii)该候选小区包含在第三RRC消息中但未包含在第一RRC消息中，且第三RRC消息中包含的该候选小区对应的CHO执行条件能够被遵从；以及
iii)该候选小区包含在第一RRC消息和第三RRC消息中，且第一RRC消息中包含的该候选小区对应的CHO执行条件能够被遵从，且第三RRC消息中包含的该候选小区对应的CHO执行条件能够被遵从。
与之相应，终端设备从CHO执行条件能够被遵从的候选小区中所确定出的满足CHO执行条件的第二候选小区可能包括下文列举的一种或多种：
i)该第二候选小区包含在第一RRC消息中但未包含在第三RRC消息中，且第一RRC消息中包含的该第二候选小区对应的CHO执行条件达到/满足；
ii)该第二候选小区包含在第三RRC消息中但未包含在第一RRC消息中，且第三RRC消息中包含的该第二候选小区对应的CHO执行条件达到/满足；以及
iii)该第二候选小区包含在第一RRC消息和第三RRC消息中，且根据第一RRC消息以及第三RRC消息得到的该第二候选小区对应的CHO执行条件达到/满足。
如果第三RRC消息用于重新配置候选小区，且第三RRC消息中包含的是全配置信息，则，终端设备按上文所述的方法确定出CHO执行条件能够被遵从的候选小区后，然后，判断CHO执行条件能够被遵从的候选小区中是否存在满足CHO执行条件的小区。例如，终端设备确定出的满足CHO执行条件的小区包含在第三RRC消息中，且第三RRC消息中包含的该小区对应CHO执行条件达到/满足。
在步骤740中，终端设备确定该至少一个第二候选小区中是否存在CHO配置信息中所对应的参数能够被遵从的小区。
与步骤730相对应，由于第三RRC消息对第一RRC消息进行重配/更新，步骤740 中，终端设备根据重配/更新后获取到的候选小区对应的参数来判断“该至少一个第二候选小区中是否存在CHO配置信息中所对应的参数能够被遵从的小区”。
比如，在delta配置的情况下，终端设备执行步骤740的过程中，可以根据第一RRC消息和第三RRC消息，确定至少一个第二候选小区中是否存在CHO配置信息中所对应的参数能够被遵从的小区。在全配置的情况下，终端设备可以根据第三RRC消息，确定至少一个第二候选小区中是否存在CHO配置信息中所对应的参数能够被遵从的小区。
若终端设备确定该至少一个第二候选小区中存在CHO配置信息中所对应的参数能够被遵从的小区，则该至少一个第二候选小区中所对应的参数能够被遵从的小区为目标小区，可以执行步骤750，尝试切换至该CHO配置信息中所对应的参数能够被遵从的小区；并在切换成功的情况下，执行步骤760，与切换成功的小区进行通信，或者说，在切换成功的小区中通信。
若终端设备确定该至少一个第二候选小区中不存在CHO配置信息中所对应的参数能够被遵从的小区，或，若终端设备切换失败(如步骤750失败)，则执行步骤770，发起重建立流程。
应理解，上述步骤750至770的具体过程与方法600中的步骤640至660的具体过程相似，为了简洁，这里不再重复。需要注意的是，终端设备在尝试切换的过程中所使用的参数以及切换后通信所使用的参数均可以是重配/更新后得到的参数。
在另一种实现方式中，当终端设备在750中尝试切换到CHO配置信息中所对应的参数能够被遵从的小区失败，或者，若终端设备在步骤740中确定至少一个第二候选小区中不存在所对应的参数能够被遵从的候选小区，则终端设备可以执行小区选择，若通过小区选择确定的满足S准则的小区包含在CHO配置信息能够被遵从的候选小区中，则可以尝试切换至该小区。若切换成功，则认为本轮CHO流程成功；若该满足S准则的小区未包含在CHO配置信息能够被遵从的候选小区中，或者，若终端设备未能成功切换至该满足S准则的小区，则可以执行步骤770，发起重建立流程。该实现方式例如可参考上文方法200中的流程A。为了简洁，这里不作详细说明。
或者，若终端设备未能成功切换至上述满足S准则的小区，该终端设备还可以再次执行小区选择，确定满足S准则的另一小区，并确定该满足S准则的另一小区是否包含在CHO配置信息能够被遵从的候选小区中，若是，终端设备可以再次尝试切换至该小区。如此重复执行，直到成功接入到某一小区中，与切换成功的小区进行通信；或直至终端设备维护的第八定时器超时，执行步骤770，终端设备发起重建立流程。
其中，该第八定时器可以是终端设备在步骤710中接收到第一RRC消息时启动，也可以是终端设备在步骤720中接收到第二RRC消息时启动，还可以是在终端设备确定出目标小区后开始执行步骤750时启动。本申请对此不作限定。该第八定时器的时长例如可以是预定义的，如协议预定义，或者，第一RRC消息中可以包含第八定时器的相关信息，如第八定时器的有效时长等，或者，第三RRC消息中可以包含第八定时器的相关信息，如第八定时器的有效时长等。本申请对此不作限定。
在另一种实现方式中，若终端设备在步骤750中尝试切换到CHO配置信息中所对应的参数能够被遵从的小区失败，则终端设备可以再根据第一RRC消息和/或第三RRC消息、此时的信道状态等，进行评估、判断，尝试从CHO执行条件能被遵从的候选小区中 再次确定出满足CHO执行条件的小区，如能确定出，再判断确定出的该小区所对应的参数是否能被遵从，若能够被遵从，则将其作为新的目标小区。终端设备可以尝试切换至新的目标小区，如此重复执行，直至所有的CHO执行条件能够被遵从的候选小区都被判断过是否满足CHO执行条件，或直至所有CHO执行条件能够被遵从的候选小区中的能满足CHO执行条件的小区都被判断过其相对应的参数是否能被遵从，或直至满足CHO执行条件的候选小区中所对应的参数能够被遵从的所有候选小区都被尝试切换过，或直至终端设备侧的第九定时器超时，可以执行步骤770，终端设备发起重建立流程。该第九定时器的时长例如可以是预定义的，如协议预定义，或者，第一RRC消息中可以包含第九定时器的相关信息，如第九定时器的有效时长等，或者，第三RRC消息中可以包含第九定时器的相关信息，如第九定时器的有效时长等。本申请对此不作限定。
又或者，终端设备可以在对配置的候选小区中CHO配置信息能够被遵从且满足CHO执行条件的所有小区都尝试了切换，但均切换失败之后，进行小区选择，确定满足S准则的小区，并确定该满足S准则的小区是否包含在CHO配置信息能够被遵从的候选小区中。若是，终端设备尝试切换到该满足S准则的小区中。若切换成功，则本轮CHO流程成功。若该满足S准则的小区不包含在CHO配置信息能够被遵从的候选小区中，或者，若终端设备尝试切换到该满足S准则的小区中的流程失败，则可以执行步骤770，终端设备发起重建立流程。
或者，若该满足S准则的小区不包含在CHO配置信息能够被遵从的候选小区中，或者，若终端设备尝试切换到该满足S准则的小区中的流程失败，则终端设备可以再次执行小区选择，如此重复执行，直至成功接入到某一小区，则本轮CHO流程成功；或，第九定时器超时，则可以执行步骤660，终端设备发起重建立流程。
若终端设备在步骤740中确定至少一个第二候选小区中不存在所对应的参数能够被遵从的候选小区，终端设备可以执行小区选择，确定满足S准则的小区，进而确定该满足S准则的小区是否包含在CHO配置信息能够被遵从的候选小区中。若该满足S准则的小区包含在CHO配置信息能够被遵从的候选小区中，该满足S准则的小区为目标小区，终端设备可以尝试切换至该满足S准则的小区。如果终端设备成功切换至该满足S准则的小区，则认为本轮CHO流程成功。若该满足S准则的小区未包含在CHO配置信息能够被遵从的候选小区中，或者，若终端设备未能成功切换至该满足S准则的小区，则可以执行步骤770，终端设备发起重建立流程。或者，终端设备也可以在确定至少一个第一候选小区中不存在所对应的参数能够被遵从的候选小区时，直接执行步骤770，发起重建立流程。终端设备发起重建立流程的具体过程在上文已经做了详述，为了简洁，这里不再重复。
终端设备发起重建立流程的具体过程在上文已经做了详述，为了简洁，这里不再重复。
在上述流程中，终端设备可以在本轮CHO流程成功的情况下，可以执行步骤760，与切换成功的小区进行通信。
需要说明的是，终端设备执行步骤720接收第三RRC消息的时间并不固定。终端设备可能在接收到第三RRC消息之前，已经根据第一RRC消息中候选小区的CHO配置信息确定了CHO执行条件能够被遵从的部分候选小区，但在接收到第三RRC消息后，还需要进一步根据更新后得到的候选小区的CHO配置信息确定更新后得到的CHO执行条件能够被遵从的候选小区。
或者，终端设备在执行步骤720之前也可能已经根据第一RRC消息确定出了满足CHO执行条件的目标小区，在接收到第三RRC消息后，终端设备可以忽略/删除该第三RRC消息，尝试切换至该已经确定出的目标小区，或者，终端设备需要进一步根据候选小区重新配置/更新后所对应的最新的CHO配置信息确定该最新的CHO配置信息中包含的CHO执行条件是否能够被遵从，进而确定CHO执行条件能被遵从的候选小区中是否存在满足CHO执行条件的小区，若存在，再判断该满足CHO执行条件的小区所对应的参数(即该小区对应的包含在最新的CHO配置信息中的参数)是否能被遵从。
或者，终端设备甚至还可以在执行步骤720之前已经确定出目标小区，并正在尝试切换到该目标小区。但在接收到第三RRC消息后，终端设备可以忽略/删除该第三RRC消息，继续切换至该已经确定出的目标小区，或者，终端设备需要进一步根据候选小区重新配置/更新后所对应的最新的CHO配置信息确定该最新的CHO配置信息中包含的CHO执行条件是否能够被遵从，进而确定CHO执行条件能够被遵从的候选小区中是否存在满足CHO执行条件的小区。若存在，再判断该满足CHO执行条件的小区所对应的参数(即该小区对应的包含在最新的CHO配置信息中的参数)是否能被遵从。
应理解，图7中的流程仅为示例，并未对上述流程予以示出。但这不应对本申请构成任何限定。
另外，虽然图中将各个步骤按照先后顺序示出，但这不应对本申请构成任何限定。比如终端设备在执行步骤730时，有可能在步骤720之前确定出了一部分CHO执行条件能够被遵从的候选小区，在步骤720之后，终端设备可以根据第三RRC消息，或第一RRC消息和第三RRC消息(如，当第三RRC消息用于添加新的候选小区，和/或修改第一RRC消息中已经配置过的候选小区时)，重新确定出CHO执行条件能够被遵从的候选小区。诸如此类，为了简洁，这里不一一列举说明。
基于上述技术方案，终端设备可以基于接收到的第三RRC消息进行候选小区的重新配置/更新。在确定不能够遵从部分候选小区的CHO执行条件的情况下，不发起重建立流程，而是优先尝试切换。终端设备可以从CHO执行条件能被遵从的候选小区中，判断是否存在满足CHO执行条件的小区，若存在，再判断该小区所对应的参数(即该小区对应的包含在更新后得到的CHO配置信息中的参数)是否能够被遵从，若能遵从，则尝试切换至该小区。由此可以避免重建立流程造成的时延、复杂度，避免较长时间的通信中断对用户体验的影响，有利于提高系统可靠性，保证系统性能，有利于提高用户体验。
另一方面，由于终端设备在接收到第一RRC消息后仅需评估是否能够各候选小区的CHO执行条件，在确定出满足CHO执行条件的小区之后，评估这些小区的CHO配置信息中的参数是否能够被遵从，可以减小评估的候选小区的数量，减小终端设备的工作量，降低实现复杂度。
以上，结合图2至图7详细说明了本申请实施例提供的通信方法。但上述实施例中都是在假设对源网络设备发送的RRC消息(如第一RRC消息、第三RRC消息等)成功接收的基础上所描述的终端设备的操作流程。然而，在某些情况下，终端设备对接收到的RRC消息(如上文所述的第二RRC消息)的完整性保护校验失败。在本申请实施例中，终端设备一旦确定出对第二RRC消息的完整性保护校验失败，不发起重建立流程，而仍然基于第一RRC消息中的一个或多个候选小区的CHO配置信息继续进行切换流程。
下面结合图8详细说明终端设备对第二RRC消息的完整性保护校验失败的情况下的具体流程。
图8是本申请再一实施例提供的通信方法800的示意性流程图。如图8所示，该方法800可以包括步骤810至步骤870。下面详细说明方法800中的各步骤。
在步骤810中，该终端设备接收第一RRC消息，该第一RRC消息包括一个或多个候选小区的CHO配置信息。该第一RRC消息例如可以是源网络设备发送的。
关于步骤810的详细说明可以参考上文方法200中步骤210的详细说明，为了简洁，这里不再重复。
在步骤820中，终端设备接收第二RRC消息，但对第二RRC消息的完整性保护校验失败。
如前所述，终端设备在保持着与源网络设备之间的RRC连接的情况下，还可能接收到其他RRC消息，即，第二RRC消息。该第二RRC消息可以用于重新配置候选小区，此情况下，该第二RRC消息可以是上文所述的第三RRC消息。或者，该第二RRC消息也可用于指示终端设备进行传统切换；又或者，该第二RRC消息也可用于其他。本申请实施例对此不作限定。
如果终端设备对第二RRC消息的完整性保护校验失败，终端设备则无法成功解析出该第二RRC消息中携带的信息。则终端设备可以丢弃该第二RRC消息，并执行步骤830，执行小区选择，确定满足S准则的小区。为便于区分和说明，将该满足S准则的小区记作第五小区。
终端设备执行小区选择的具体过程可以参考现有技术，为了简洁，这里不作详述。
在步骤840中，终端设备确定该第五小区是否包含在CHO配置信息能够被遵从的候选小区中。
由于终端设备未成功解析出第二RRC消息中的信息，故终端设备可以仍然基于第一RRC消息中一个或多个候选小区的CHO配置信息，确定第五小区是否属于第一RRC消息配置的候选小区以及所对应的CHO配置信息是否能够被遵从。
若终端设备能够遵从该第五小区的CHO配置信息，则可以执行步骤850，终端设备尝试切换至第五小区中。若终端设备成功切换至第五小区，则可以执行步骤860，与第五小区进行通信，或者说，在第五小区中通信。
若第五小区未包含在第一RRC消息所配置的候选小区中，或，若第五小区包含在第一RRC消息所配置的候选小区中，但终端设备不能够遵从该第五小区的CHO配置信息，则可以执行步骤870，发起RRC重建立流程。
在另一种实现方式中，上述步骤870也可以被替换为以下流程：
终端设备再次执行小区选择，如终端设备确定出满足S准则的另一小区，若该小区包含在能够被遵从的候选小区中，尝试切换，如此重复执行，直至切换成功，与切换成功的小区进行通信，或者说，与切换成功的小区中通信；或，若第十定时器超时，切换失败，执行步骤870，发起重建立流程。其中，该第十定时器可以是终端设备在步骤810中接收到第一RRC消息时启动，也可以是终端设备在步骤820中接收到第三RRC消息时启动，也可以是在终端设备确定出目标小区后开始执行步骤850时启动。本申请对此不作限定。该第十定时器的时长例如可以是预定义的，如协议预定义，或者，第一RRC消息中可以 包含第十定时器的相关信息，如第十定时器的有效时长等，或者，第三RRC消息中可以包含第十定时器的相关信息，如第十定时器的有效时长等。本申请对此不作限定。
或者，上述步骤830至870可以替换为上文方法200中步骤220至步骤290中的部分或全部步骤，或者，也可以替换为上文方法400中的步骤420至步骤470中的部分或全部步骤，或者，还可以替换为上文方法600中的步骤620至步骤660中的部分或全部步骤，或者，还可以替换为上文方法200至700中列举的其他实现方式中所执行的步骤。
由于上文方法200、方法400和方法600中分别对各步骤做了详细说明，为了简洁，这里不作详述。
在又一种实现方式中，终端设备可以丢弃第二RRC消息，继续执行接收到该第二RRC消息之前所执行的流程。例如，终端设备执行上文方法200、方法400或方法600中的某一步骤时接收到第二RRC消息，但对第二RRC消息的完整性保护校验失败，则终端设备可以继续执行接收到第二RRC消息之前执行的步骤。
比如，终端设备在接收到第二RRC消息之前，刚好执行完步骤430，确定出了满足S准则的第一小区，则终端设备可以丢弃接收到的第二RRC消息，继续执行步骤440及其后续流程。
又比如，终端设备在接收到第二RRC消息之前，正在执行上述方法400中的步骤440，也就是说，终端设备在接收到第二RRC消息之前，已经确定出目标小区(即上述第一小区)，正在尝试切换至该目标小区。终端设备可以丢弃接收到的第二RRC消息，继续执行步骤440及其后续流程。
诸如此类，为了简洁，这里不一一举例说明。
基于上述技术方案，终端设备在接收到第二RRC消息但对第二RRC消息的完整性保护校验失败的情况下，并不立刻发起RRC重建来流程，而是优先考虑切换。终端设备可以通过不同的方式确定出目标小区，并尝试切换至该目标小区，或者，也可以继续执行当前操作。因此可以较大程度地避免重建立流程造成的时延、复杂度，避免较长时间的通信中断对用户体验的影响，有利于提高系统可靠性，保证系统性能，有利于提高用户体验。
上文中结合多个实施例详细说明了终端设备在确定不能够遵从部分候选小区的CHO执行条件的情况下的操作。基于上文各实施例所提供的方法，终端设备最终可以通过切换或重建立的方式接入到一个小区中，恢复正常通信。下面将结合附图从设备交互的角度说明本申请实施例提供的通信方法。
图9是本申请再一实施例提供的通信方法900的示意性流程图。如图9所示，该方法900可以包括步骤910至步骤950。下面详细说明方法900中的各步骤。
在步骤910中，终端设备接收第一RRC消息，该第一RRC消息包括一个或多个候选小区的CHO配置信息。该第一RRC消息例如可以是由源网络设备发送的。
关于步骤910的详细说明可以参考上文方法200中步骤210的详细说明，为了简洁，这里不再重复。
在步骤920中，终端设备通过切换或重建立的方式，接入到某一小区中，例如记作第六小区。
步骤920例如可以通过执行上文方法200、方法400、方法600和方法800中任意一个实施例所提供的方法来实现。因此该第六小区例如可以是方法200、方法400、方法600 或方法800中所述的目标小区，或者也可以是方法200、方法400、方法600或方法800中通过重建立流程所接入的重建立小区。本申请对此不作限定。由于上文已经结合各实施例详细说明了终端设备的具体操作流程，为了简洁，这里不再赘述。
在本实施例中，该第六小区所属的网络设备例如可以记作第一网络设备。可以理解，该第一网络设备可能是目标小区所属的网络设备，也可能是重建立小区所属的网络设备，这取决于终端设备接入的小区是目标小区还是重建立小区。
可选地，在步骤920之前，该方法还包括步骤930，接收第三RRC消息，该第三RRC消息用于重新配置候选小区。该第三RRC消息例如也可以是由源网络设备发送的。
在此情况下，步骤920例如可以通过执行上文方法300、方法500或方法700中任意一个实施例所提供的方法来实现。因此该第四小区例如可以是方法300、方法500或方法700中所述的目标小区，或者也可以是方法300、方法500或方法700中通过重建立流程所接入的重建立小区。本申请对此不作限定。由于上文已经结合各实施例详细说明了终端设备的具体操作流程，为了简洁，这里不再赘述。
在步骤940中，终端设备发送接入失败信息。
一种情况，源网络设备向终端设备发送了第一RRC消息而未发送第三RRC消息，或者，另一种情况，源网络设备向终端设备发送了第一RRC消息和第三RRC消息，但终端设备对第三RRC消息的完整性校验失败。在上述的任一情况下，终端设备可能可以确定未成功接入的候选小区。为便于区分和说明，例如记作第七小区。该第七小区可以是指被源网络设备配置(例如通过第一RRC消息配置)的但未成功切换过去的候选小区，也可以是指被源网络设备配置(例如第一RRC消息配置)但CHO配置信息不能够被遵从(例如包括CHO执行条件不能够被遵从和/或候选小区对应的参数不能够被遵从)，还可以是指不满足CHO执行条件的候选小区，等等。本申请对此不作限定。可以理解，第七小区的数量并不一定为一个。在第一RRC消息中配置了多个候选小区的情况下，可能存在终端设备未能成功接入的一个或多个候选小区。
该接入失败信息例如包括第七小区的相关信息。例如包括以下一项或多项：第七小区的小区标识(如CGI、PCI等)，第七小区的频率信息(如SSB的绝对频率、参考资源块的绝对频率位置等)，和第七小区的测量标识等。
另一种情况，终端设备接收到第一RRC消息、以及第三RRC消息，且成功解析出第三RRC消息中的信息，终端设备可能可以确定未成功接入的候选小区。若仍将未成功接入的候选小区记作第七小区，该第七小区可以是指通过第三RRC消息，或通过第一RRC消息和第三RRC消息配置的但未成功接入的小区。例如可以是被源网络设备配置(例如第三RRC消息配置、或第一RRC消息和第三RRC消息配置)但CHO配置信息不能够被遵从，或者，也可以是不满足CHO执行条件的候选小区，或者，还可以是源网络设备配置(例如第三RRC消息配置、或第一RRC消息和第三RRC消息配置)但未成功切换过去的候选小区。如前所述，该第七小区的数量并不一定为一个。为了简洁，这里不一一列举说明。
在本实施例中，为方便说明，假设第七小区为一个小区。第七小区所属的网络设备例如记作第二网络设备。可以理解，在第七小区为多个的情况下，各第七小区所属的网络设备可能是同一网络设备，也可能是不同网络设备，本申请对此不作限定。
在一种实现方式中，步骤940可以包括：步骤9401，终端设备向第一网络设备发送该接入失败信息；步骤9402，第一网络设备将该接入失败信息转发给源网络设备；步骤9403，源网络设备将该接入指示信息转发给第二网络设备。
在另一种实现方式中，步骤940可以包括：9404，终端设备可以向源网络设备发送该接入失败信息；步骤9405，该源网络设备可以将该接入失败信息转发给第二网络设备。第二网络设备可以是第七小区所属的网络设备。
可选地，终端设备可以基于来自网络设备(如上述第一网络设备、第二网络设备或源网络设备中的任意一个或其他网络设备)的请求，发送该接入失败信息。
图中示出了步骤9401-9403终端设备通过第一网络设备和源网络设备向第二网络设备发送该接入失败信息的流程，以及步骤9404-9405终端设备通过源网络设备向第二网络设备发送接入失败信息的流程。为便于区分，将步骤9304-9405以虚线示出。应理解，图中所示的步骤仅为示例，并不代表终端设备所执行图中示出的所有步骤。此外，本申请对于终端设备向第二网络设备发送接入失败信息的具体方式不作限定。
在步骤950中，第二网络设备根据该接入失败信息调整CHO配置信息。
基于上述接入失败信息，第二网络设备可以对CHO配置信息作出调整。在下一次被确定为候选网络设备的情况下，第二网络设备可以将调整后的CHO配置信息提供给终端设备，以期获得较高的切换成功率。
基于上述技术方案，终端设备可以将CHO配置信息不能够被遵从的候选小区以及切换失败的候选小区通过切换失败信息上报给这些候选小区所属的网络设备，以便调整CHO配置信息，从而可以有利于在下一次被确定为候选小区时，获得较高的切换成功率。因此从整体上说，可以提高系统可靠性，保证系统性能。
还应理解，上述实施例中，各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
以上，结合图2至图9详细说明了本申请实施例提供的方法。以下，结合图10至图12详细说明本申请实施例提供的装置。
图10是本申请实施例提供的通信装置10的示意性框图。如图10所示，该通信装置10可以包括处理单元11和收发单元12。
在一种可能的设计中，该通信装置10可实现上文方法实施例中的对应于终端设备的操作，例如，该通信装置可以为终端设备，或者配置于终端设备中的部件，如芯片或电路。
该终端设备10可实现图2至图9所示方法实施例中终端设备的相应操作。该通信装置10可以包括用于执行图2至图9所示方法实施例中终端设备执行的方法的单元。并且，该通信装置10中的各单元和上述其他操作和/或功能分别为了实现图2至图9所示的方法实施例中的相应流程。
在一个实施例中，该收发单元12可用于接收第一无线资源控制RRC消息，所述第一RRC消息包括一个或多个候选小区的条件切换CHO配置信息，所述一个或多个候选小区的CHO配置信息包括CHO执行条件以及与各候选小区对应的参数；处理单元11可用于在不能够遵从所述一个或多个候选小区中的部分候选小区的CHO配置信息的情况下，确定CHO配置信息能够被遵从的候选小区中是否存在满足CHO执行条件的小区。
可选地，处理单元11还用于，若所述CHO配置信息能够被遵从的候选小区中存在所述满足CHO执行条件的小区，尝试切换至所述满足CHO执行条件的小区。
可选地，处理单元11还用于，若所述CHO配置信息能够被遵从的候选小区中不存在所述满足CHO执行条件的小区，或，若尝试切换至所述满足CHO执行条件的流程失败，发起重建立流程。
可选地，收发单元12还用于，接收第二RRC消息，但对所述第二RRC消息的完整性保护校验失败，所述第二RRC消息是在接收到所述第一RRC消息之后接收到的消息；处理单元11还用于确定满足S准则的小区；并用于在所述满足S准则的小区包含在所述CHO配置信息能够被遵从的候选小区中的情况下，尝试切换至所述满足S准则的小区。
在另一个实施例中，该收发单元12可用于接收第一无线资源控制RRC消息，所述第一RRC消息包括一个或多个候选小区的条件切换CHO配置信息，所述一个或多个候选小区的CHO配置信息包括CHO执行条件以及与各候选小区对应的参数；处理单元11可用于在不能够遵从所述一个或多个候选小区中的部分候选小区的CHO配置信息的情况下，确定满足S准则的第一小区；并可用于确定所述第一小区是否包含在CHO配置信息能够被遵从的候选小区中。
可选地，处理单元11还用于，若所述第一小区包含在所述CHO配置信息能够被遵从的候选小区中，尝试切换至所述第一小区。
可选地，处理单元11还用于，若所述第一小区不包含在所述CHO配置信息能够被遵从的候选小区中，或，若尝试切换至所述第一小区的流程失败，发起重建立流程。
可选地，接收单元12还用于，接收第二RRC消息，但对所述第二RRC消息的完整性保护校验失败，所述第二RRC消息是在接收到所述第一RRC消息之后接收到的消息；处理单元11还用于，确定满足S准则的小区；并用于在所述满足S准则的小区包含在所述CHO配置信息能够被遵从的候选小区中的情况下，尝试切换至所述满足S准则的小区。
在又一个实施例中，接收单元12可用于接收第一无线资源控制RRC消息，所述第一RRC消息包括一个或多个候选小区的条件切换CHO配置信息，所述一个或多个候选小区的CHO配置信息包括CHO执行条件以及各候选小区对应的参数；处理单元11可用于在不能够遵从所述一个或多个候选小区中的部分候选小区的CHO执行条件的情况下，确定所述一个或多个候选小区中CHO执行条件能够被遵从的部分候选小区中存在满足CHO执行条件的至少一个第一候选小区；并可用于确定至少一个第一候选小区中是否存在CHO配置信息中所对应的参数能够被遵从的小区。
可选地，处理单元11还用于，若所述至少一个第一候选小区中存在CHO配置信息中所对应的参数能够被遵从的小区，尝试切换至所述CHO配置信息中所对应的参数能够被遵从的小区。
可选地，处理单元11还用于，在若所述至少一个第一候选小区中不存在CHO配置信息中所对应的参数能够被遵从的小区，或，若尝试切换至所述CHO配置信息中所对应的参数能够被遵从的小区的流程失败，发起重建立流程。
在上述各实施例中，可选地，所述CHO配置信息中与候选小区对应的参数包括以下一项或多项：候选小区为终端设备分配的小区无线网络临时标识C-RNTI、接入候选小区的随机接入信道RACH资源、候选小区的小区全球标识CGI、候选小区的物理小区标识 PCI、候选小区对应的同步信号块SSB的绝对频率、参考资源块的绝对频率、频率带宽列表、子载波间隔SCS特定的载波列表、候选小区的物理层配置参数、候选小区的媒体接入控制MAC层配置参数、候选小区的无线链路控制RLC层配置参数、分组数据汇聚层协议PDCP层配置参数、业务数据自适应协议SDAP层配置参数、RRC层配置参数、以及承载配置信息。
在另一个实施例中，收发单元12可用于接收第一无线资源控制RRC消息，所述第一RRC消息包括一个或多个候选小区的CHO配置信息，所述一个或多个候选小区的CHO配置信息包括CHO执行条件以及与各候选小区对应的参数；并可用于接收第三RRC消息，所述第三RRC消息包括一个或多个候选小区的CHO配置信息；所述第三RRC消息用于重新配置候选小区；处理单元11可用于根据所述第一RRC消息和所述第三RRC消息，在不能够遵从部分候选小区的CHO配置信息的情况下，确定CHO配置信息能够被遵从的候选小区中是否存在满足CHO执行条件的小区。
可选地，处理单元11还用于，若所述第一小区包含在所述CHO配置信息能够被遵从的候选小区中，尝试切换至所述第一小区。
可选地，处理单元11还用于，若所述第一小区不包含在所述CHO配置信息能够被遵从的候选小区中，或，若尝试切换至所述第一小区的流程失败，发起重建立流程。
可选地，收发单元12还用于，接收第二RRC消息，但对所述第二RRC消息的完整性保护校验失败，所述第二RRC消息是在接收到所述第一RRC消息之后接收到的消息；处理单元11还用于确定满足S准则的小区；并用于在所述满足S准则的小区包含在所述CHO配置信息能够被遵从的候选小区中的情况下，尝试切换至所述满足S准则的小区。
在又一个实施例中，收发单元12可用于接收第一无线资源控制RRC消息，所述第一RRC消息包括一个或多个候选小区的CHO配置信息，所述一个或多个候选小区的CHO配置信息包括CHO执行条件以及与各候选小区对应的参数；并可用于接收第三RRC消息，所述第三RRC消息包括一个或多个候选小区的CHO配置信息；所述第三RRC消息用于重新配置候选小区；处理单元11可用于根据所述第一RRC消息和所述第三RRC消息，在不能够遵从部分候选小区的CHO配置信息的情况下，确定CHO配置信息能够被遵从的候选小区中是否存在满足CHO执行条件的小区。
可选地，处理单元11还用于，若所述CHO配置信息能够被遵从的候选小区中存在所述满足CHO执行条件的小区，尝试切换至所述满足CHO执行条件的小区。
可选地，处理单元11还用于，若所述CHO配置信息能够被遵从的候选小区中不存在所述满足CHO执行条件的小区，或，若尝试切换至所述满足CHO执行条件的小区的流程失败，确定满足S准则的第二小区；还用于，若所述第二小区包含在所述CHO配置信息能够被遵从的候选小区中，尝试切换至所述第二小区。
可选地，处理单元11还用于，若所述CHO配置信息能够被遵从的候选小区中不存在所述满足CHO执行条件的小区，或，若尝试切换至所述满足CHO执行条件的小区的流程失败，确定满足S准则的第二小区；还用于，若所述第二小区不包含在所述CHO配置信息能够被遵从的候选小区中，发起重建立流程。
可选地，处理单元11还用于，若所述CHO配置信息能够被遵从的候选小区中不存在所述满足CHO执行条件的小区，或，若尝试切换至所述满足CHO执行条件的小区的流程 失败，发起重建立流程。
在另一个实施例中，收发单元12可用于接收第一RRC消息，所述第一RRC消息包括一个或多个候选小区的CHO配置信息，所述一个或多个候选小区的CHO配置信息包括CHO执行条件以及与各候选小区对应的参数；并可用于接收第三RRC消息，所述第三RRC消息包括一个或多个候选小区的CHO配置信息；所述第三RRC消息用于重新配置候选小区；处理单元11可用于，在不能够遵从所述一个或多个候选小区中的部分候选小区的CHO配置信息的情况下，确定CHO执行条件能够被遵从的候选小区中存在满足CHO执行条件的至少一个第二候选小区；并可用于确定所述至少一个第二候选小区中是否存在CHO配置信息中所对应的参数能够被遵从的小区。
可选地，处理单元11还用于，若所述至少一个第二候选小区中存在CHO配置信息中所对应的参数能够被遵从的小区，尝试切换至所述CHO配置信息中所对应的参数能够被遵从的小区。
可选地，处理单元11还用于，若所述至少一个第二候选小区中不存在CHO配置信息中所对应的参数能够被遵从的小区，或，若切换失败，发起重建立流程。
结合上述各实施例中，可选地，所述与候选小区对应的参数由所述第一RRC消息中的CHO配置信息和第三RRC消息中的CHO配置信息确定，或，由所述第三RRC消息中的CHO配置信息确定；所述与候选小区对应的参数包括：候选小区为终端设备分配的小区无线网络临时标识C-RNTI、接入候选小区的随机接入信道RACH资源、候选小区的小区全球标识CGI、候选小区的物理小区标识PCI、候选小区对应的同步信号块SSB的绝对频率、参考资源块的绝对频率、频率带宽列表、子载波间隔SCS特定的载波列表、候选小区的物理层配置参数、候选小区的媒体接入控制MAC层配置参数、候选小区的无线链路控制RLC层配置参数、分组数据汇聚层协议PDCP层配置参数、业务数据自适应协议SDAP层配置参数以及、RRC层配置参数、以及承载配置信息。
进一步可选地，通信装置10还可以包括存储单元，该存储单元可以用于存储指令或者数据，处理单元可以调用该存储单元中存储的指令或者数据，以实现相应的操作。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
还应理解，该通信装置10中的收发单元12可以通过收发器或者通信接口实现，例如可对应于图11中示出的终端设备3000中的收发器2020。该通信装置10中的处理单元11可以通过至少一个处理器实现，例如可对应于图11中示出的终端设备3000中的处理器2010。
图11是本申请实施例提供的终端设备2000的结构示意图。该终端设备2000可应用于如图1所示的系统中，执行上述方法实施例中终端设备的功能。如图所示，该终端设备3000包括处理器2010和收发器2020。可选地，该终端设备3000还包括存储器2030。其中，处理器2010、收发器3002和存储器2030之间可以通过内部连接通路互相通信，传递控制和/或数据信号，该存储器2030用于存储计算机程序，该处理器2010用于从该存储器2030中调用并运行该计算机程序，以控制该收发器2020收发信号。可选地，终端设备3000还可以包括天线2040，用于将收发器2020输出的上行数据或上行控制信令通过无线信号发送出去。
上述处理器2010可以和存储器2030可以合成一个处理装置，处理器2010用于执行存储器2030中存储的程序代码来实现上述功能。具体实现时，该存储器2030也可以集成在处理器2010中，或者独立于处理器2010。该处理器2010可以与图11中的处理单元11对应。
上述收发器2020可以与图11中的收发单元12对应。收发器2020可以包括接收器(或称接收机、接收电路)和发射器(或称发射机、发射电路)。其中，接收器用于接收信号，发射器用于发射信号。
应理解，图11所示的终端设备2000能够实现图2至图9所示方法实施例中涉及终端设备的各个过程。终端设备2000中的各个模块的操作和/或功能，分别为了实现上述方法实施例中的相应流程。具体可参见上述方法实施例中的描述，为避免重复，此处适当省略详细描述。
上述处理器2010可以用于执行前面方法实施例中描述的由终端设备内部实现的动作，而收发器2020可以用于执行前面方法实施例中描述的终端设备向网络设备发送或从网络设备接收的动作。具体请见前面方法实施例中的描述，此处不再赘述。
可选地，上述终端设备2000还可以包括电源2050，用于给终端设备中的各种器件或电路提供电源。
除此之外，为了使得终端设备的功能更加完善，该终端设备3000还可以包括输入单元2060、显示单元2070、音频电路2080、摄像头2090和传感器2100等中的一个或多个，所述音频电路还可以包括扬声器2082、麦克风2084等。
图12是本申请实施例提供的网络设备的结构示意图，例如可以为基站的结构示意图。该基站3000可应用于如图1所示的系统中，执行上述方法实施例中网络设备的功能。如图所示，该基站3000可以包括一个或多个射频单元，如远端射频单元(remote radio unit，RRU)3100和一个或多个基带单元(BBU)(也可称为分布式单元(DU))3300。所述RRU 3100可以称为收发单元，与图11中的收发单元12对应。可选地，该收发单元3100还可以称为收发机、收发电路、或者收发器等等，其可以包括至少一个天线3101和射频单元3102。可选地，收发单元3100可以包括接收单元和发送单元，接收单元可以对应于接收器(或称接收机、接收电路)，发送单元可以对应于发射器(或称发射机、发射电路)。所述RRU 3100部分主要用于射频信号的收发以及射频信号与基带信号的转换，例如用于向终端设备发送指示信息。所述BBU 3300部分主要用于进行基带处理，对基站进行控制等。所述RRU 3100与BBU 3300可以是物理上设置在一起，也可以物理上分离设置的，即分布式基站。
所述BBU 3300为基站的控制中心，也可以称为处理单元，可以与图11中的处理单元11对应，主要用于完成基带处理功能，如信道编码，复用，调制，扩频等等。例如所述BBU(处理单元)可以用于控制基站执行上述方法实施例中关于网络设备的操作流程，例如，生成上述指示信息等。
在一个示例中，所述BBU 3300可以由一个或多个单板构成，多个单板可以共同支持单一接入制式的无线接入网(如LTE网)，也可以分别支持不同接入制式的无线接入网(如LTE网，5G网或其他网)。所述BBU 3300还包括存储器3201和处理器3202。所述存储器3201用以存储必要的指令和数据。所述处理器3202用于控制基站进行必要的动 作，例如用于控制基站执行上述方法实施例中关于网络设备的操作流程。所述存储器3201和处理器3202可以服务于一个或多个单板。也就是说，可以每个单板上单独设置存储器和处理器。也可以是多个单板共用相同的存储器和处理器。此外每个单板上还可以设置有必要的电路。
应理解，图12所示的基站3000能够实现图2至图9所示方法实施例中涉及目标网络设备的各个过程。基站3000中的各个模块的操作和/或功能，分别为了实现上述方法实施例中的相应流程。具体可参见上述方法实施例中的描述，为避免重复，此处适当省略详细描述。
上述BBU 3300可以用于执行前面方法实施例中描述的由网络设备内部实现的动作，而RRU 3100可以用于执行前面方法实施例中描述的网络设备向终端设备发送或从终端设备接收的动作。具体请见前面方法实施例中的描述，此处不再赘述。
应理解，图12所示出的基站3000仅为网络设备的一种可能的架构，而不应对本申请构成任何限定。本申请所提供的方法可适用于其他架构的网络设备。例如，包含CU、DU和有源天线单元(active antenna unit，AAU)的网络设备等。本申请对于网络设备的具体架构不作限定。
本申请实施例还提供了一种处理装置，包括处理器和接口；所述处理器用于执行上述任一方法实施例中的方法。
应理解，上述处理装置可以是一个或多个芯片。例如，该处理装置可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是专用集成芯片(application specific integrated circuit，ASIC)，还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质 中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
根据本申请实施例提供的方法，本申请还提供一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行图2至图9所示实施例中任一实施例的方法。
根据本申请实施例提供的方法，本申请还提供一种计算机可读存储介质，该计算机可读存储介质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行图2至图9所示实施例中任一实施例终端设备执行的方法。
根据本申请实施例提供的方法，本申请还提供一种系统，其包括前述的一个或多个终端设备以及一个或多个网络设备。
上述各个装置实施例中网络设备与终端设备和方法实施例中的网络设备或终端设备完全对应，由相应的模块或单元执行相应的步骤，例如通信单元(收发器)执行方法实施例中接收或发送的步骤，除发送、接收外的其它步骤可以由处理单元(处理器)执行。具体单元的功能可以参考相应的方法实施例。其中，处理器可以为一个或多个。
在本说明书中使用的术语“部件”、“模块”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中，部件可位于一个计算机上和/或分布在2个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地系统、分布式系统和/或网络间的另一部件交互的二个部件的数据，例如通过信号与其它系统交互的互联网)的信号通过本地和/或远程进程来通信。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各种说明性逻辑块(illustrative logical block)和步骤(step)，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的 功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，各功能单元的功能可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令(程序)。在计算机上加载和执行所述计算机程序指令(程序)时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (22)

  1. 一种通信方法，其特征在于，包括：
    接收第一无线资源控制RRC消息，所述第一RRC消息包括一个或多个候选小区的条件切换CHO配置信息，所述一个或多个候选小区的CHO配置信息包括CHO执行条件以及与各候选小区对应的参数；
    在不能够遵从所述一个或多个候选小区中的部分候选小区的CHO配置信息的情况下，确定CHO配置信息能够被遵从的候选小区中是否存在满足CHO执行条件的小区。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    若所述CHO配置信息能够被遵从的候选小区中存在所述满足CHO执行条件的小区，尝试切换至所述满足CHO执行条件的小区。
  3. 如权利要求1或2所述的方法，其特征在于，所述方法还包括：
    若所述CHO配置信息能够被遵从的候选小区中不存在所述满足CHO执行条件的小区，或，若尝试切换至所述满足CHO执行条件的流程失败，发起重建立流程。
  4. 如权利要求1至3中任一项所述的方法，其特征在于，所述方法还包括：
    接收第二RRC消息，但对所述第二RRC消息的完整性保护校验失败，所述第二RRC消息是在接收到所述第一RRC消息之后接收到的消息；
    确定满足S准则的小区；
    在所述满足S准则的小区包含在所述CHO配置信息能够被遵从的候选小区中的情况下，尝试切换至所述满足S准则的小区。
  5. 如权利要求1至4中任一项所述的方法，其特征在于，所述CHO配置信息中与候选小区对应的参数包括以下一项或多项：
    候选小区为终端设备分配的小区无线网络临时标识C-RNTI、接入候选小区的随机接入信道RACH资源、候选小区的小区全球标识CGI、候选小区的物理小区标识PCI、候选小区对应的同步信号块SSB的绝对频率、参考资源块的绝对频率、频率带宽列表、子载波间隔SCS特定的载波列表、候选小区的物理层配置参数、候选小区的媒体接入控制MAC层配置参数、候选小区的无线链路控制RLC层配置参数、分组数据汇聚层协议PDCP层配置参数、业务数据自适应协议SDAP层配置参数、RRC层配置参数、以及承载配置信息。
  6. 一种通信方法，其特征在于，包括：
    接收第一无线资源控制RRC消息，所述第一RRC消息包括一个或多个候选小区的条件切换CHO配置信息，所述一个或多个候选小区的CHO配置信息包括CHO执行条件以及与各候选小区对应的参数；
    在不能够遵从所述一个或多个候选小区中的部分候选小区的CHO配置信息的情况下，确定满足S准则的第一小区；
    确定所述第一小区是否包含在CHO配置信息能够被遵从的候选小区中。
  7. 如权利要求6所述的方法，其特征在于，所述方法还包括：
    若所述第一小区包含在所述CHO配置信息能够被遵从的候选小区中，尝试切换至所 述第一小区。
  8. 如权利要求6或7所述的方法，其特征在于，所述方法还包括：
    若所述第一小区不包含在所述CHO配置信息能够被遵从的候选小区中，或，若尝试切换至所述第一小区的流程失败，发起重建立流程。
  9. 如权利要求6至8中任一项所述的方法，其特征在于，所述方法还包括：
    接收第二RRC消息，但对所述第二RRC消息的完整性保护校验失败，所述第二RRC消息是在接收到所述第一RRC消息之后接收到的消息；
    确定满足S准则的小区；
    在所述满足S准则的小区包含在所述CHO配置信息能够被遵从的候选小区中的情况下，尝试切换至所述满足S准则的小区。
  10. 如权利要求6至9中任一项所述的方法，其特征在于，所述CHO配置信息中与候选小区对应的参数包括：
    候选小区为终端设备分配的小区无线网络临时标识C-RNTI、接入候选小区的随机接入信道RACH资源、候选小区的小区全球标识CGI、候选小区的物理小区标识PCI、候选小区对应的同步信号块SSB的绝对频率、参考资源块的绝对频率、频率带宽列表、子载波间隔SCS特定的载波列表、候选小区的物理层配置参数、候选小区的媒体接入控制MAC层配置参数、候选小区的无线链路控制RLC层配置参数、分组数据汇聚层协议PDCP层配置参数、业务数据自适应协议SDAP层配置参数、RRC层配置参数、以及承载配置信息。
  11. 一种通信方法，其特征在于，包括：
    接收第一无线资源控制RRC消息，所述第一RRC消息包括一个或多个候选小区的CHO配置信息，所述一个或多个候选小区的CHO配置信息包括CHO执行条件以及与各候选小区对应的参数；
    接收第三RRC消息，所述第三RRC消息包括一个或多个候选小区的CHO配置信息；所述第三RRC消息用于重新配置候选小区；
    根据所述第一RRC消息和所述第三RRC消息，在不能够遵从部分候选小区的CHO配置信息的情况下，确定CHO配置信息能够被遵从的候选小区中是否存在满足CHO执行条件的小区。
  12. 如权利要求11所述的方法，其特征在于，所述方法还包括：
    若所述CHO配置信息能够被遵从的候选小区中存在所述满足CHO执行条件的小区，尝试切换至所述满足CHO执行条件的小区。
  13. 如权利要求11或12所述的方法，其特征在于，所述方法还包括：
    若所述CHO配置信息能够被遵从的候选小区中不存在所述满足CHO执行条件的小区，或，若尝试切换至所述满足CHO执行条件的小区的流程失败，确定满足S准则的第二小区；
    若所述第二小区包含在所述CHO配置信息能够被遵从的候选小区中，尝试切换至所述第二小区，或，
    若所述第二小区不包含在所述CHO配置信息能够被遵从的候选小区中，发起重建立流程。
  14. 如权利要求11或12所述的方法，其特征在于，所述方法还包括：
    若所述CHO配置信息能够被遵从的候选小区中不存在所述满足CHO执行条件的小区，或，若尝试切换至所述满足CHO执行条件的小区的流程失败，发起重建立流程。
  15. 如权利要求11至14中任一项所述的方法，其特征在于，所述与候选小区对应的参数由所述第一RRC消息中的CHO配置信息和第三RRC消息中的CHO配置信息确定，所述与候选小区对应的参数包括：
    候选小区为终端设备分配的小区无线网络临时标识C-RNTI、接入候选小区的随机接入信道RACH资源、候选小区的小区全球标识CGI、候选小区的物理小区标识PCI、候选小区对应的同步信号块SSB的绝对频率、参考资源块的绝对频率、频率带宽列表、子载波间隔SCS特定的载波列表、候选小区的物理层配置参数、候选小区的媒体接入控制MAC层配置参数、候选小区的无线链路控制RLC层配置参数、分组数据汇聚层协议PDCP层配置参数、业务数据自适应协议SDAP层配置参数、RRC层配置参数、以及承载配置信息。
  16. 一种通信方法，其特征在于，包括：
    接收第一无线资源控制RRC消息，所述第一RRC消息包括一个或多个候选小区的CHO配置信息，所述一个或多个候选小区的CHO配置信息包括CHO执行条件以及与各候选小区对应的参数；
    接收第三RRC消息，所述第三RRC消息包括一个或多个候选小区的CHO配置信息；所述第三RRC消息中的一个或多个候选小区的CHO配置信息用于对所述第一RRC消息中的一个或多个候选小区的CHO配置信息进行更新；
    根据所述第一RRC消息和所述第三RRC消息，在不能够遵从部分候选小区的CHO配置信息的情况下，确定满足S准则的第三小区；
    确定所述第三小区是否包含在CHO配置信息能够被遵从的候选小区中。
  17. 如权利要求16所述的方法，其特征在于，所述方法还包括：
    若所述第三小区包含在所述CHO配置信息能够被遵从的候选小区中，尝试切换至所述第三小区。
  18. 如权利要求16或17所述的方法，其特征在于，所述方法还包括：
    若所述第三小区不包含在所述CHO配置信息能够被遵从的候选小区中，或，若尝试切换至所述第三小区的流程失败，发起重建立流程。
  19. 如权利要求16至18中任一项所述的方法，其特征在于，所述与候选小区对应的参数由所述第一RRC消息中的CHO配置信息和第三RRC消息中的CHO配置信息确定，所述与候选小区对应的参数包括：
    候选小区为终端设备分配的小区无线网络临时标识C-RNTI、接入候选小区的随机接入信道RACH资源、候选小区的小区全球标识CGI、候选小区的物理小区标识PCI、候选小区对应的同步信号块SSB的绝对频率、参考资源块的绝对频率、频率带宽列表、子载波间隔SCS特定的载波列表、候选小区的物理层配置参数、候选小区的媒体接入控制MAC层配置参数、候选小区的无线链路控制RLC层配置参数、分组数据汇聚层协议PDCP层配置参数、业务数据自适应协议SDAP层配置参数、RRC层配置参数、以及承载配置信息。
  20. 一种通信装置，其特征在于，包括用于实现如权利要求1至19中任一项所述的方法的单元。
  21. 一种通信装置，其特征在于，包括：
    处理器，用于执行存储器中存储的计算机指令，以使得所述装置执行：如权利要求1至19中任一项所述的方法。
  22. 一种计算机存储介质，其特征在于，其上存储有计算机程序，所述计算机程序被计算机执行时，以使得实现如权利要求1至19中任一项所述的方法。
PCT/CN2019/109774 2019-09-30 2019-09-30 通信方法和通信装置 WO2021062845A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/109774 WO2021062845A1 (zh) 2019-09-30 2019-09-30 通信方法和通信装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/109774 WO2021062845A1 (zh) 2019-09-30 2019-09-30 通信方法和通信装置

Publications (1)

Publication Number Publication Date
WO2021062845A1 true WO2021062845A1 (zh) 2021-04-08

Family

ID=75337683

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/109774 WO2021062845A1 (zh) 2019-09-30 2019-09-30 通信方法和通信装置

Country Status (1)

Country Link
WO (1) WO2021062845A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023141837A1 (en) * 2022-01-26 2023-08-03 Nec Corporation Method, device and computer storage medium of communication

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180279193A1 (en) * 2017-03-22 2018-09-27 Ofinno Technologies, Llc Conditional Handover Execution
CN108632926A (zh) * 2017-03-24 2018-10-09 华为技术有限公司 通信方法、网络设备和终端
CN109392039A (zh) * 2017-08-11 2019-02-26 捷开通讯(深圳)有限公司 通信切换方法及装置
WO2019134163A1 (en) * 2018-01-08 2019-07-11 Lenovo (Beijing) Limited Method and apparatus for ue handover
US20190223057A1 (en) * 2018-01-16 2019-07-18 Electronics And Telecommunications Research Institute Method and apparatus for conditional handover in communication system
WO2019154480A1 (en) * 2018-02-06 2019-08-15 Nokia Technologies Oy Further access attempts in conditional handover

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180279193A1 (en) * 2017-03-22 2018-09-27 Ofinno Technologies, Llc Conditional Handover Execution
CN108632926A (zh) * 2017-03-24 2018-10-09 华为技术有限公司 通信方法、网络设备和终端
CN109392039A (zh) * 2017-08-11 2019-02-26 捷开通讯(深圳)有限公司 通信切换方法及装置
WO2019134163A1 (en) * 2018-01-08 2019-07-11 Lenovo (Beijing) Limited Method and apparatus for ue handover
US20190223057A1 (en) * 2018-01-16 2019-07-18 Electronics And Telecommunications Research Institute Method and apparatus for conditional handover in communication system
WO2019154480A1 (en) * 2018-02-06 2019-08-15 Nokia Technologies Oy Further access attempts in conditional handover

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Conditional Handover", 3GPP DRAFT; R2-1803336 - CONDITIONAL HANDOVER, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Athens, Greece; 20180226 - 20180302, 16 February 2018 (2018-02-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051400471 *
VIVO: "Signaling procedure for conditional handover", 3GPP DRAFT; R2-1905965_SIGNALING PROCEDURE FOR CONDITIONAL HANDOVER, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, USA; 20190513 - 20190517, 13 May 2019 (2019-05-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051729456 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023141837A1 (en) * 2022-01-26 2023-08-03 Nec Corporation Method, device and computer storage medium of communication

Similar Documents

Publication Publication Date Title
CN108924949B (zh) 无线网络中的通信方法、装置和系统
JP2022520966A (ja) 情報送信方法および装置
CN114451063B (zh) 通信方法和通信装置
EP3668182B1 (en) Communication method and device
WO2021027683A1 (zh) 切换方法、通信装置和终端设备
WO2021018283A1 (zh) 通信方法和通信装置
JP7047913B2 (ja) 上りリンク信号送信方法、上りリンク信号受信方法、装置及びシステム
WO2020087509A1 (zh) 无线通信方法、终端设备和网络设备
WO2021164720A1 (zh) 重建立的方法和通信装置
CN116097702A (zh) 发送成功切换报告的方法、终端设备和网络设备
WO2021087929A1 (zh) 一种随机接入的方法和装置
US20220386187A1 (en) Communication method and communication apparatus
WO2022011500A1 (zh) 配置方法和装置
CN113519183A (zh) 无线通信方法和终端设备
JP2023545801A (ja) 信号の送受信方法、装置及び通信システム
WO2021027907A1 (zh) 通信方法和通信装置
WO2021027660A1 (zh) 无线通信的方法和通信装置
WO2021062845A1 (zh) 通信方法和通信装置
CN116057998A (zh) 一种通信方法、设备和装置
KR20240036073A (ko) 경로 전환 및 핸드오버를 처리하기 위한 단말 장치, 네트워크 노드 및 그 방법
CN116438845A (zh) 通信方法和通信装置
WO2021102841A1 (zh) 一种基于网络切片的数据传输方法、装置和系统
JP7413349B2 (ja) ランダムアクセス方法、データ受信方法及びその装置、通信システム
CN114616862A (zh) 通信方法、装置及系统
CN117729596B (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: 19947617

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19947617

Country of ref document: EP

Kind code of ref document: A1