Patent Description:
In the existing conditional handover (Conditional Handover, CHO) procedure, a trigger event is configured by a source node. After being determined by a target node, configuration of candidate cells is transmitted to a terminal transparently through the source node. The terminal measures all candidate cells, and according to a handover command configured by the network and the trigger event, selects a target cell from the candidate cells for performing handover, in a case that a corresponding trigger condition is met. However, a success rate of the existing conditional handover is low.

Document <NPL>, is a 3GPP paper, discussing general principles and concepts of CHO in <NUM> like CHO call flow, trigger configurations, involved entities, used RRC messages etc..

Document <NPL>, is another 3GPP contribution discussing follow ups for CHO issues that seemed to converge during a previous email discussion, thereby addressing inter-alia the encoding of CHO configurations in RRC messages (ASN1) as concrete proposals for TP <NUM>.

Document <NPL>, is another 3GPP contribution discussing configuration of the triggering condition to be monitored for conditional handover thereby proposing inter-alia the basis of triggering conditions (A3, A5, measured parameters RSRP, RSRQ, resources to be measured, SSB, CSI-RS).

All embodiments of the present disclosure provide a conditional handover method, a configuration method, a terminal and a network device, to resolve a problem of low success rate of the existing handover manner.

The present invention defines conditional handover method performed by a terminal according to independent claim <NUM>, a corresponding conditional handover configuration method performed by the inter-related network device according to independent claim <NUM>, a corresponding terminal according to independent claim <NUM>, and a corresponding network device according to independent claim <NUM>.

To describe the technical solutions in the embodiments of the present disclosure more clearly, the following briefly describes the accompanying drawings required for describing the embodiments of the present disclosure. Apparently, the accompanying drawings in the following description show merely some embodiments of the present disclosure, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts.

The technologies described herein are not limited to long term evolution (Long Term Evolution, LTE)/LTE-Advanced (LTE-Advanced, LTE-A) systems, and may also be used in various wireless communications systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single-carrier frequency-division multiple access (Single-carrier Frequency-Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" are often used interchangeably. The CDMA system can implement radio technologies such as CDMA2000 and universal terrestrial radio access (Universal Terrestrial Radio Access, UTRA). UTRA includes wideband CDMA (Wideband Code Division Multiple Access, WCDMA) and other CDMA variants. The TDMA system can implement radio technologies such as global system for mobile communications (Global System for Mobile Communication, GSM). The OFDMA system may implement radio technologies such as ultra mobile broadband (Ultra Mobile Broadband, UMB), evolved UTRA (Evolution-UTRA, E-UTRA), IEEE <NUM> (Wi-Fi), IEEE <NUM> (WiMAX), IEEE <NUM>, and Flash-OFDM. UTRA and E-UTRA are part of the universal mobile telecommunications system (Universal Mobile Telecommunications System, UMTS). LTE and more advanced LTEs (such as LTE-A) are new releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3rd Generation Partnership Project, 3GPP). The technologies described herein are applicable not only to the above-mentioned systems and radio technologies, but also to other systems and radio technologies such as a new radio (New Radio, NR) system.

A wireless communications system in the embodiments of the present disclosure includes a terminal and a network device. The terminal may also be referred to as a terminal device or user equipment (User Equipment, UE). The terminal may be a terminal side device such as a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a personal digital assistant (Personal Digital Assistant, PDA), a mobile Internet device (Mobile Internet Device, MID), a wearable device (Wearable Device), or an in-vehicle device. It should be noted that the specific type of the terminal is not limited in the embodiments of the present disclosure. The network device may be a base station or a core network. The base station may be a <NUM> base station or a base station of a later release (for example, a gNB or a <NUM> NR NB), or a base stations in other communications systems (for example, an eNB, a WLAN access point, or other access points). The base station may be referred to as a NodeB, an evolved NodeB, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a NodeB, an evolved NodeB (eNB), a home NodeB, a home evolved NodeB, a WLAN access point, a Wi-Fi node, or other applicable terms in the art. As long as a same technical effect is achieved, the base station is not limited to any specific technical term.

In this embodiment of the present disclosure, optionally, a dual connectivity (Dual Connectivity, DC) architecture may be used for a terminal, and the DC architecture includes two cell groups: a master cell group (Master Cell Group, MCG) and a secondary cell group (Secondary Cell Group, SCG). The MCG corresponds to a network-side master node (Master Node, MN), and the SCG corresponds to a network-side secondary node (secondary node, SN). The MCG includes a primary cell (Primary Cell, PCell) and a secondary cell (Secondary Cell, SCell). The SCG includes a primary secondary cell (Primary Secondary Cell, PSCell) and a SCell. Both the PCell and the PSCell may also be referred to as special cells (Special Cell, SpCell).

Optionally, the terminal may use carrier aggregation (Carrier Aggregation, CA) technology. With the CA technology, a cell corresponding to the terminal may be divided into a primary cell (PCell) and a secondary cell (SCell).

The present disclosure is described below with reference to the embodiments and the accompanying drawings.

Referring to <FIG> is a flowchart of a handover method according to an embodiment of the present disclosure. The method is applied to a terminal.

Step <NUM>: Determine, based on a measurement result of a first cell, whether a trigger condition is met.

If it is determined that the trigger condition is met, step <NUM> is performed. If the trigger condition is not met, step <NUM> is performed.

Optionally, the first cell may be a candidate cell. Alternatively, the first cell is associated with the trigger condition. It should be noted that in a case that the first cell is associated with the trigger condition, the first cell may be a candidate cell, or may not be a candidate cell, but is only a neighboring cell associated with the trigger condition.

In addition, because the trigger condition may be related to a servicing cell, for example, the trigger condition is that the trigger condition is met only when the first cell has a power higher than that of the servicing cell by specified decibels. Therefore, when step <NUM> is being performed, whether the trigger condition is met may be alternatively determined based on the measurement result of the first cell and a measurement result of the servicing cell.

The measurement result in step <NUM> may include but is not limited to at least one of the following: reference signal receiving power (Reference Signal Receiving Power, RSRP), reference signal received quality (Reference Signal Received Quality, RSRQ), a signal to interference plus noise ratio (Signal to Interference plus Noise Ratio, SINR), or a channel quality indicator (Channel Quality Indicator, CQI). Measurement corresponding to the measurement result may include cell measurement, and/or beam measurement. The beam measurement may include measurement of at least one of the following: a synchronization signal and PBCH block (Synchronization Signal and PBCH block, SSB), a demodulation reference signal (Demodulation Reference Signal, DMRS), or other reference signals.

Step <NUM>: Hand over to the first cell.

Optionally, if the trigger condition is met, the terminal may hand over to the first cell, and may further skip performing measurement reporting, thereby saving resources and reducing signaling overheads.

In addition, if it is determined that the trigger condition is met in step <NUM>, but a corresponding condition handover is not configured, the terminal may perform the measurement reporting.

Step <NUM>: Perform at least one of the following: skipping handing over to the first cell; or performing measurement reporting or skipping performing measurement reporting.

It should be noted that in a case that the first cell is a candidate cell, if the trigger condition is not met, the terminal performs the measurement reporting, so that the network device can obtain the network status. In a case that the first cell is associated with the trigger condition, if the trigger condition is not met, the terminal skips performing the measurement reporting, to save resources and reduce signaling overheads.

The handover method in this embodiment of the present disclosure can detect, based on the measurement result of the first cell, whether the trigger condition is met, and hand over to the first cell in a case that the trigger condition is met. In this way, the success rate of the handover can be increased, to ensure a high success rate of the handover and low latency.

In this embodiment of the present disclosure, the trigger condition may be associated with a plurality of cells. Alternatively, in a case that the first cell is associated with the trigger condition, the first cell may be a primary cell (PCell) associated with the trigger condition. It can be understood that in this case, the terminal may use the CA technology.

Alternatively, in a case that the first cell is associated with the trigger condition, the first cell may be a special cell (SpCell) associated with the trigger condition. It can be understood that in this case, the terminal may use a DC architecture.

In this way, the success rate of the handover can be increased by selecting a PCell or SpCell to trigger the handover.

In this embodiment of the present disclosure, to ensure the handover process (such as a conditional handover process), the terminal may receive handover-related configuration information from a network device (such as a source base station). The handover-related configuration information may include but is not limited to at least one of the following:.

In all embodiments of the present invention, the terminal may receive configuration information from the network device before performing step <NUM>. For example, the network device is a source base station. The configuration information may include at least one of the following:.

Alternatively, the association involved in (<NUM>) may be: that the trigger event is associated with the candidate cell, or that the trigger event index is associated with the candidate cell.

In an embodiment, the configured trigger event or trigger event index is associated with one candidate cell.

Optionally, the candidate cell is the same as a PCell or Spcell indicated by a first message. The first message may be any one of the following: an RRC reconfiguration message, an RRC synchronization reconfiguration message, a handover command, mobile control information, or the like.

In an embodiment, the candidate cell is the same as a PCell or SpCell indicated by the RRC reconfiguration message.

It should be noted that, that a trigger event is associated with a candidate cell may include any one of the following association manners: <NUM>) the trigger event being in one-to-one correspondence to the candidate cell, for example, the trigger event being in one-to-one correspondence to the candidate cell through configuration; <NUM>) in an RRC message configured with the trigger event, an information element (Information Element, IE) corresponding to the candidate cell identifier being configured; and <NUM>) in an RRC message configured with the candidate cell, an IE of the RRC message corresponding to the trigger event being configured.

That a trigger event index is associated with a candidate cell may include any of the following association manners: <NUM>) the trigger event index being in one-to-one correspondence to the candidate cell, for example, the trigger event index being in one-to-one correspondence to the candidate cell through configuration; <NUM>) in an RRC message configured with the trigger event index, an IE corresponding to the candidate cell identifier being configured; and <NUM>) in an RRC message configured with the candidate cell, an IE corresponding to the trigger event index being configured.

(<NUM>) that a trigger event or a trigger event index (index) is associated with a candidate cell identifier.

Alternatively, the association involved in (<NUM>) may be: the trigger event being associated with the candidate cell identifier, or the trigger event index being associated with the candidate cell identifier;
In an embodiment, the configured trigger event or trigger event index is associated with one candidate cell identifier.

Optionally, the candidate cell identifier may be the same as a PCell identifier or SpCell identifier in a first message. The first message may be any one of the following: an RRC reconfiguration message, an RRC synchronization reconfiguration message, a handover command, mobile control information, or the like.

In an embodiment, the candidate cell identifier is the same as a PCell identifier or SpCell identifier in the RRC reconfiguration message.

It should be noted that, that the trigger event is associated with the candidate cell identifier may include any one of the following association manners: <NUM>) the trigger event being in one-to-one correspondence to the candidate cell identifier, for example, the trigger event being in one-to-one correspondence to the candidate cell identifier through configuration; <NUM>) in an RRC message configured with the trigger event, an IE corresponding to the candidate cell identifier being configured; and <NUM>) in an RRC message corresponding to the configured candidate cell identifier, an IE of the RRC message corresponding to the trigger event being configured.

The trigger event index being associated with the candidate cell identifier may include any one of the following association manners: <NUM>) the trigger event index being in one-to-one correspondence to the candidate cell identifier, for example, the trigger event index being in one-to-one correspondence to the candidate cell identifier through configuration; <NUM>) in an RRC message configured with the trigger event index, an IE corresponding to the candidate cell identifier being configured; and <NUM>) in an RRC message configured with the candidate cell identifier, an IE corresponding to the trigger event index being configured.

(<NUM>) that a trigger event is associated with a first message.

In an embodiment, the configured trigger event is associated with one first message.

Optionally, the first message in (<NUM>) may be any one of the following: an RRC reconfiguration message, an RRC synchronization reconfiguration message, a handover command, mobile control information, or the like.

Optionally, that a trigger event is associated with a first message may include any one of the following:.

For example, assuming that the first message is an RRC reconfiguration message, the association relationship involved in (<NUM>) may include any one of the following: <NUM>) the trigger event index being associated with one RRC reconfiguration message index; <NUM>) the trigger event index being associated with one RRC reconfiguration message; and <NUM>) the trigger event being associated with one RRC reconfiguration message index.

It should be noted that a trigger event index being associated with a first-message index may include any one of the following association manners: <NUM>) the trigger event being in one-to-one correspondence to the first message, for example, the trigger event being in one-to-one correspondence to the first message through configuration; <NUM>) in an RRC message configured with the trigger event, an IE of the first message being configured; and <NUM>) in the first message, an IE of the RRC message corresponding to the trigger event being configured.

(<NUM>) that a trigger event is associated with a PCell identifier or SpCell identifier in a first message.

It should be understood that the association involved in (<NUM>) may be any one of the following: <NUM>) the trigger event index being associated with the PCell identifier or SpCell identifier in the first message; <NUM>) the trigger event index being associated with the PCell or SpCell indicated by the first message; and <NUM>) the trigger event being associated with the PCell identifier or SpCell identifier in the first message.

It should be noted that the trigger event index being associated with the PCell identifier or SpCell identifier in the first message may include any one of the following association manners: <NUM>) the trigger event index being in one-to-one correspondence to the PCell identifier or SpCell identifier in the first message, for example, the trigger event index being in one-to-one correspondence to the PCell identifier the first message through configuration; <NUM>) in an RRC message configured with the trigger event, an IE of the first message being configured; and <NUM>) in the first message, an IE corresponding to the trigger event index being configured.

The trigger event index being associated with the PCell or SpCell indicated by the first message may include any one of the following association manners: <NUM>) the trigger event index being in one-to-one correspondence to the PCell or SpCell indicated by the first message, for example, the trigger event index being in one-to-one correspondence to the PCell or SpCell indicated by the first message through configuration; <NUM>) in an RRC message configured with the trigger event index, an IE of the first message being configured; and <NUM>) in the first message, an IE corresponding to the trigger event index being configured.

The trigger event being associated with the PCell identifier or SpCell identifier in the first message may include any one of the following association manners: <NUM>) the trigger event being in one-to-one correspondence to the PCell identifier or SpCell identifier in the first message, for example, the trigger event being in one-to-one correspondence to the PCell identifier or SpCell identifier in the first message through configuration; <NUM>) in an RRC message configured with the trigger event, an IE of the first message being configured; and <NUM>) in the first message, an IE of the RRC message corresponding to the trigger event being configured.

It is to be noted, that the association manner in all embodiments of the present invention comprises the candidate cell being in one-to-one correspondence to the trigger condition, wherein the candidate cell is a primary cell, PCell, associated with the trigger condition; or the first cell is a special cell, SpCell, associated with the trigger condition.

In addition, it should be noted that the trigger event in this embodiment of the present disclosure may be an existing trigger event or a newly defined trigger event. For example, when the trigger event is an existing trigger event, it may be event A1, event A2, event A3, event A4, event A5, event B1, event B2, event B3, event B4, event B5, event C1, event C2, event C3, or the like. Event A1 is that a cell measurement result of a serving cell is better than a first absolute threshold. Event A2 is that the cell measurement result of the serving cell is worse than a second absolute threshold. Event A3 is that a cell measurement result of a potential target cell is better than that of the serving cell. Event A4 is that the cell measurement result of the potential target cell is better than a third absolute threshold. Event A5 is that the cell measurement result of the serving cell is worse than a fourth absolute threshold, and that the cell measurement result of the potential target cell is better than a fifth absolute threshold.

Referring to <FIG> is a flowchart of a configuration method according to an embodiment of the present disclosure. The method is applied to a network device. As shown in <FIG>, the method includes the following step.

Step <NUM>: Send configuration information.

The configuration information may include at least one of the following:.

Optionally, the candidate cell is the same as a PCell or Spcell indicated by the first message;
or
the candidate cell identifier is the same as the PCell identifier or SpCell identifier in the first message.

Optionally, that a trigger event is associated with a first message includes any one of the following:.

Optionally, that a trigger event is associated with a first message includes any one of the following association manners:.

Optionally, the first message includes any one of the following:
an RRC reconfiguration message, an RRC synchronization reconfiguration message, a handover command, and mobile control information.

It can be understood that the content of the configuration information in this embodiment may be the same as that described in the embodiment shown in <FIG>.

With the foregoing configuration information, the success rate of the handover performed by the terminal can be increased, thereby ensuring a high success rate of the handover and low latency.

The foregoing embodiments describe the handover method and the configuration method in the present disclosure. The following describes the terminal and network device in the present disclosure with reference to the embodiments and the accompanying drawings.

Referring to <FIG> is a schematic structural diagram of a terminal according to an embodiment of the present disclosure. As shown in <FIG>, the terminal <NUM> includes:.

Optionally, the first cell is a candidate cell; or
the first cell is associated with the trigger condition.

Optionally, in a case that the first cell is associated with the trigger condition,.

Optionally, the processing module <NUM> is further configured to: in a case that the trigger condition is met, skip performing measurement reporting.

Optionally, the processing module <NUM> is further configured to:
in a case that the trigger condition is not met, perform at least one of the following:.

Optionally, the terminal <NUM> further includes:.

The terminal <NUM> in this embodiment of the present disclosure can implement the processes of the method embodiment in <FIG>, with the same beneficial effects achieved. To avoid repetition, details are not described herein again.

Referring to <FIG> is a schematic structural diagram of a network device according to an embodiment of this disclosure. As shown in <FIG>, the network device <NUM> includes:.

An embodiment of the present disclosure further provides a communications device, including a processor, a memory, and a computer program stored in the memory and capable of running on the processor. When the computer program is executed by the processor, the processes of the embodiment shown in <FIG> or the processes of the embodiment shown in <FIG> are implemented, with the same technical effects achieved. To avoid repetition, details are not described herein again. Optionally, the communications device may be a terminal or a network device.

Referring to <FIG> is a schematic diagram of a hardware structure of a terminal for implementing the embodiments of the present disclosure. The terminal <NUM> includes but is not limited to components such as a radio frequency unit <NUM>, a network module <NUM>, an audio output unit <NUM>, an input unit <NUM>, a sensor <NUM>, a display unit <NUM>, a user input unit <NUM>, an interface unit <NUM>, a memory <NUM>, a processor <NUM>, and a power supply <NUM>. A person skilled in the art can understand that the structure of the terminal shown in <FIG> does not constitute any limitation on the terminal, and the terminal may include more or fewer components than those shown in the diagram, or a combination of some components, or the components disposed differently. In this embodiment of the present disclosure, the terminal includes but is not limited to a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a vehicle-mounted terminal, a wearable device, a pedometer, or the like.

The processor <NUM> is configured to determine, based on a measurement result of a first cell, whether a trigger condition is met; and hand over to the first cell when the trigger condition is met.

It should be understood that in this embodiment of the present disclosure, the radio frequency unit <NUM> may be configured to receive and transmit signals in an information reception or transmission or call process. Alternatively, after receiving downlink data from a base station, the radio frequency unit <NUM> transmits the downlink data to the processor <NUM> for processing, and in addition, transmits uplink data to the base station. Generally, the radio frequency unit <NUM> includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit <NUM> may further communicate with a network and other devices via a wireless communications system.

The terminal provides a user with wireless broadband Internet access by using the network module <NUM>, for example, helping the user send or receive an email, browse a web page, access streaming media, and the like.

The audio output unit <NUM> may convert audio data received by the radio frequency unit <NUM> or the network module <NUM> or stored in the memory <NUM> into an audio signal, and output the audio signal as a sound. In addition, the audio output unit <NUM> may further provide audio output (for example, a call signal received tone or a message received tone) that is related to a specific function performed by the terminal <NUM>. The audio output unit <NUM> includes a speaker, a buzzer, a receiver, and the like.

The input unit <NUM> is configured to receive an audio signal or a video signal. The input unit <NUM> may include a graphics processing unit (Graphics Processing Unit, GPU) <NUM> and a microphone <NUM>. The graphics processing unit <NUM> processes image data of a static picture or a video obtained by an image capture apparatus (for example, a camera) in an image capture mode or a video capture mode. A processed image frame may be displayed on the display unit <NUM>. The image frame processed by the graphics processing unit <NUM> may be stored in the memory <NUM> (or another storage medium) or transmitted by using the radio frequency unit <NUM> or the network module <NUM>. The microphone <NUM> is capable of receiving sounds and processing such sounds into audio data. The processed audio data can be converted into a format output that can be transmitted to a mobile communication base station through the radio frequency unit <NUM> in a telephone call mode.

The terminal <NUM> further includes at least one sensor <NUM>, for example, an optical sensor, a motion sensor, and other sensors. Alternatively, the optical sensor includes an ambient light sensor and a proximity sensor. The ambient light sensor may adjust brightness of a display panel <NUM> based on intensity of ambient light. When the terminal <NUM> moves near an ear, the proximity sensor may disable the display panel <NUM> and/or backlight. As a motion sensor, an accelerometer sensor may detect magnitudes of accelerations in various directions (typically three axes), and in a stationary state, may detect the magnitude and direction of gravity, and may be applied to terminal posture recognition (for example, switching between a landscape orientation and a portrait orientation, related gaming, and magnetometer posture calibration), vibration recognition related functions (for example, pedometer and tapping), and the like. The sensor <NUM> may further include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, and the like.

The display unit <NUM> is configured to display information input by the user or information provided to the user.

The user input unit <NUM> may be configured to receive input digit or character information, and generate key signal input that is related to user setting and function control of the terminal. Alternatively, the user input unit <NUM> includes a touch panel <NUM> and other input devices <NUM>. The touch panel <NUM>, also referred to as a touchscreen, may capture a touch operation performed by a user on or near the touch panel (for example, an operation performed by the user on the touch panel <NUM> or near the touch panel <NUM> by using a finger or any appropriate object or accessory such as a stylus). The touch panel <NUM> may include two parts: a touch detection apparatus and a touch controller. The touch detection apparatus detects a touch orientation of the user, detects a signal carried by the touch operation, and transmits the signal to the touch controller. The touch controller receives touch information from the touch detection apparatus, converts the touch information into contact coordinates, transmits the contact coordinates to the processor <NUM>, receives a command transmitted by the processor <NUM>, and executes the command. In addition, the touch panel <NUM> may be implemented in a plurality of forms, for example, as a resistive, capacitive, infrared, or surface acoustic wave touch panel. In addition to the touch panel <NUM>, the user input unit <NUM> may further include other input devices <NUM>. Alternatively, the other input devices <NUM> may include but are not limited to a physical keyboard, a function key (such as a volume control key or an on/off key), a trackball, a mouse, and a joystick.

Further, the touch panel <NUM> may cover the display panel <NUM>. When detecting a touch operation on or near the touch panel <NUM>, the touch panel <NUM> transmits the touch operation to the processor <NUM> to determine a type of a touch event. Then, the processor <NUM> provides a corresponding visual output on the display panel <NUM> based on the type of the touch event. Although the touch panel <NUM> and the display panel <NUM> are used as two separate components to implement input and output functions of the terminal in <FIG>, the touch panel <NUM> and the display panel <NUM> may be integrated to implement the input and output functions of the terminal in some embodiments. This is not specifically limited herein.

The interface unit <NUM> is an interface between an external apparatus and the terminal <NUM>. For example, the external apparatus may include a wired or wireless headphone port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting an apparatus with an identification module, an audio input/output (I/O) port, a video I/O port, or an earphone port. The interface unit <NUM> may be configured to receive an input (for example, data information or power) from the external apparatus and transmit the received input to one or more elements within the terminal <NUM>, or may be configured to transmit data between the terminal <NUM> and the external apparatus.

The memory <NUM> may be configured to store software programs and various data. The memory <NUM> may mainly include a program storage region and a data storage region. The program storage region may store an operating system, an application program required by at least one function (for example, an audio play function or an image play function), and the like. The data storage region may store data (for example, audio data and a phone book) created based on usage of the mobile phone. In addition, the memory <NUM> may include a high-speed random access memory, and may further include a non-volatile memory such as a disk storage device, a flash memory device, or another volatile solid-state storage device.

The processor <NUM> is a control center of the terminal, and is connected to all components of the terminal by using various interfaces and lines. By running or executing software programs and/or modules that are stored in the memory <NUM> and calling data stored in the memory <NUM>, the processor <NUM> executes various functions of the terminal and processes data, so as to perform overall monitoring on the terminal. The processor <NUM> may include one or more processing units. Alternatively, the processor <NUM> may integrate an application processor and a modem processor. The application processor mainly processes an operating system, a user interface, an application program, and the like. The modem processor mainly processes wireless communication. It can be understood that the modem processor may alternatively be not integrated in the processor <NUM>.

The terminal <NUM> may further include a power supply <NUM> (for example, a battery) that supplies power to each component. Alternatively, the power supply <NUM> may be logically connected to the processor <NUM> by using a power management system, so as to implement functions such as charging management, discharging management, and power consumption management by using the power management system.

In addition, the terminal <NUM> may further include some functional modules that are not shown.

Referring to <FIG> is a schematic diagram of a hardware structure of a network device for implementing the embodiments of the present disclosure. The network device <NUM> includes but is not limited to a bus <NUM>, a transceiver <NUM>, an antenna <NUM>, a bus interface <NUM>, a processor <NUM>, and a memory <NUM>.

In this embodiment of the present disclosure, the network device <NUM> further includes a computer program stored in the memory <NUM> and capable of running on the processor <NUM>. Optionally, when the computer program is executed by the processor <NUM>, the following steps are implemented:.

The transceiver <NUM> is configured to transmit and receive data under control of the processor <NUM>.

The network device <NUM> in this embodiment of the present disclosure can implement the processes of the method embodiment in <FIG>, with the same beneficial effects achieved. To avoid repetition, details are not described herein again.

In <FIG>, in a bus architecture (represented by the bus <NUM>), the bus <NUM> may include any quantity of interconnected buses and bridges, and the bus <NUM> connects various circuits that include one or more processors represented by the processor <NUM> and a memory represented by the memory <NUM>. The bus <NUM> may further connect various other circuits, such as a peripheral device, a voltage regulator, and a power management circuit. These are common sense in the art, and therefore are not further described in this specification. The bus interface <NUM> provides an interface between the bus <NUM> and the transceiver <NUM>. The transceiver <NUM> may be one element, or may be a plurality of elements, for example, a plurality of receivers and transmitters, and provides a unit for communicating with various other apparatuses on a transmission medium. Data processed by the processor <NUM> is transmitted on a wireless medium through the antenna <NUM>. Further, the antenna <NUM> receives data and transmits the data to the processor <NUM>.

The processor <NUM> is responsible for managing the bus <NUM> and general processing, and may further provide various functions, including timing, a peripheral interface, voltage regulation, power management, and other control functions. The memory <NUM> may be configured to store data for use by the processor <NUM> when the processor <NUM> performs an operation.

Optionally, the processor <NUM> may be a CPU, an ASIC, an FPGA, or a CPLD.

An embodiment of the present disclosure further provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the processes of the foregoing embodiment shown in <FIG> are implemented, or the processes of the foregoing embodiment shown in <FIG> are implemented, with the same technical effects achieved. To avoid repetition, details are not described herein again. The computer-readable storage medium may be a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk, an optical disc, or the like.

It should be noted that in this specification, the terms "include" and "comprise", or any of their variants are intended to cover a non-exclusive inclusion, such that a process, a method, an article, or an apparatus that includes a list of elements not only includes those elements but also includes other elements that are not expressly listed, or further includes elements inherent to such a process, method, article, or apparatus. In absence of more constraints, an element preceded by "includes a. " does not preclude the existence of other identical elements in the process, method, article, or apparatus that includes the element.

According to the foregoing description of the implementations, a person skilled in the art may clearly understand that the methods in the foregoing embodiments may be implemented by using software in combination with a necessary common hardware platform, and certainly may alternatively be implemented by using hardware. However, in most cases, the former is a preferred implementation. Based on such an understanding, the technical solutions of the present disclosure essentially, or the part contributing to the prior art may be implemented in a form of a software product. The software product is stored in a storage medium (for example, ROM/RAM, a magnetic disk, or an optical disc), and includes several instructions for instructing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, a network device, or the like) to perform the method described in the embodiments of the present disclosure.

Claim 1:
A conditional handover method performed by a terminal, comprising:
receiving configuration information; wherein the configuration information comprises at least one of the following: a trigger event; an index of a trigger event; that a trigger event is associated with a first message; or that that a trigger event is associated with a PCell identifier or SpCell identifier in a first message; and
determining, based on a measurement result of a first cell, whether a trigger condition is met (<NUM>); and
handing over to the first cell in a case that the trigger condition is met (<NUM>), wherein the first cell is associated with the trigger condition, the association manner comprises the first cell being in one-to-one correspondence to the trigger condition,
wherein
the first cell is a primary cell, PCell, associated with the trigger condition; or
the first cell is a special cell, SpCell, associated with the trigger condition.