Handling of conditional mobility timing in wireless communications

Abstract

The invention relates to handling conditional mobility timing in wireless communications. According to one embodiment of the present disclosure, a user equipment (UE) may evaluate an execution condition for CHO and an execution condition for conditional primary and secondary cell (PSCell) mobility, and delay execution of a conditional handover (CHO) for a time period when the execution condition for CHO is satisfied and the execution condition for conditional PSCell mobility is not satisfied.

Description

Technical Field

[0001] This disclosure relates to the handling of conditional mobility timing in wireless communications. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a technology that enables high-speed packet communication. Many proposals have been put forward for LTE objectives, including those aimed at reducing user and vendor costs, improving quality of service, and expanding and improving coverage and system capacity. As upper-layer requirements, 3GPP LTE needs to reduce cost per bit, increase service availability, allow flexible use of frequency bands, have a simple architecture, open interfaces, and appropriate power consumption for terminals.

[0003] The International Telecommunication Union (ITU) and 3GPP have begun developing requirements and specifications for New Radio (NR) systems. 3GPP must identify and develop the technical components needed for the successful standardization of the new RAT (Radio Access Technology) to meet both urgent market demands and the longer-term requirements outlined in the ITU Radiocommunication Sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process. Furthermore, NR should be able to utilize any spectrum band, at least up to 100 GHz, that can be used for wireless communication even in the more distant future.

[0004] The goal of NR is a single technology framework that addresses all use cases, requirements, and deployment scenarios, including enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), ultra-reliable and low-latency communications (URLLC), and more. NR should be inherently backward compatible.

[0005] In wireless communications, user equipment (UE) can perform conditional mobility, where the network configures the UE with multiple candidate cells, and the UE determines the target cell among the candidate cells that meets the mobility execution conditions. Conditional mobility timing can be problematic when evaluating multiple execution conditions. Summary of the Invention

[0006] Technical solution

[0007] One aspect of this disclosure is to provide a method and apparatus for handling conditional mobility timing in a wireless communication system.

[0008] According to embodiments of this disclosure, a method performed by a user equipment (UE) configured to operate in a wireless communication system includes the following steps: receiving from a network a configuration for a conditional handover (CHO) to a target primary cell (PCell), wherein the configuration for the COHO includes execution conditions for the COHO and execution conditions for conditional primary / secondary cell (PSCell) mobility to a first target PSCell, and wherein the configuration for the COHO is related to the configuration for the conditional PSCell mobility; evaluating the execution conditions for the COHO while evaluating the execution conditions for the conditional PSCell mobility; delaying the execution of the COHO for a period of time after the execution conditions for the COHO are met but the execution conditions for the conditional PSCell mobility are not met; and executing the COHO to the target PCell based on the fact that the execution conditions for the conditional PSCell mobility are not met during the period of time.

[0009] According to embodiments of this disclosure, a method performed by a network node configured to operate in a wireless communication system includes: obtaining a configuration for a conditional handover command (CHO) to a target primary cell (PCell), wherein the configuration for the CHO includes execution conditions for the CHO and execution conditions for conditional primary / secondary cell (PSCell) mobility to a first target PSCell, and wherein the configuration for the CHO is related to the configuration for the conditional PSCell mobility; and sending the configuration for the CHO to a user equipment (UE), wherein the UE is configured to perform an operation including: evaluating the execution conditions for the CHO while evaluating the execution conditions for the conditional PSCell mobility; delaying the execution of the CHO for a period of time after the execution conditions for the CHO are met but the execution conditions for the conditional PSCell mobility are not met; and executing the CHO to the target PCell based on the fact that the execution conditions for the conditional PSCell mobility are not met during the period of time.

[0010] According to various embodiments, an apparatus for implementing the above method is provided.

[0011] This disclosure can have various beneficial effects.

[0012] For example, when conditional mobility is performed based on simultaneous evaluation of conditional handover (CHO) conditions and conditional primary / secondary cell (PSCell) mobility conditions, unnecessary signaling and / or disruptions can be prevented.

[0013] The beneficial effects that can be obtained through specific embodiments of this disclosure are not limited to those listed above. For example, there may be various technical effects that can be understood and / or derived from this disclosure by those skilled in the art. Therefore, the specific effects of this disclosure are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this disclosure. Attached Figure Description

[0014] Figure 1 An example of a communication system that applies the implementation of this disclosure is shown.

[0015] Figure 2 An example of a wireless device that applies the implementation of this disclosure is shown.

[0016] Figure 3 An example of a UE that applies the implementation of this disclosure is shown.

[0017] Figure 4 and Figure 5 An example of a protocol stack in a 3GPP-based wireless communication system applying the implementation of this disclosure is shown.

[0018] Figure 6 The frame structure in a 3GPP-based wireless communication system applying the implementation of this disclosure is shown.

[0019] Figure 7 An example of a data flow in a 3GPP NR system applying the implementation of this disclosure is shown.

[0020] Figure 8 An example of a dual-connectivity (DC) architecture to which the technical features of this disclosure can be applied is shown.

[0021] Figure 9 An example of a conditional mobility process according to an embodiment of the present disclosure is shown.

[0022] Figure 10 An example of a method performed by a UE according to an embodiment of this disclosure is shown.

[0023] Figure 11 An example of signal flow between a UE and a network node according to an embodiment of this disclosure is shown.

[0024] Figure 12 A first example of a method for a CHO with concurrent early CPC, according to an embodiment of this disclosure, is shown.

[0025] Figure 13 An example of the evaluation state of CPC execution conditions according to an embodiment of the present disclosure is shown.

[0026] Figure 14 An example of timer-based CPC condition evaluation according to an embodiment of this disclosure is shown.

[0027] Figure 15 A second example of a method for a CHO with concurrent early CPC, according to an embodiment of this disclosure, is shown.

[0028] Figure 16 An example of a method for a CHO with concurrent early CPA is shown according to an embodiment of this disclosure. Detailed Implementation

[0029] The following technologies, devices, and systems can be applied to a variety of wireless multiple access systems. Examples of multiple access systems include Code Division Multiple Access (CDMA) systems, Frequency Division Multiple Access (FDMA) systems, Time Division Multiple Access (TDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Multi-Carrier Frequency Division Multiple Access (MC-FDMA) systems. CDMA can be implemented using radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using radio technologies such as Global System for Mobile Communications (GSM), Universal Packet Radio Service (GPRS), or Enhanced Data Rate Evolution of GSM (EDGE). OFDMA can be implemented using radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). The 3GPP Long Term Evolution (LTE) is part of the Evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). The evolution of 3GPP LTE includes LTE-Advanced (LTE-A), LTE-A Pro, and / or 5G New Radio (NR).

[0030] For ease of description, the implementation of this disclosure is primarily described with respect to 3GPP-based wireless communication systems. However, the technical features of this disclosure are not limited thereto. For example, although the following detailed description is based on a mobile communication system corresponding to a 3GPP-based wireless communication system, the aspects of this disclosure, which are not limited to 3GPP-based wireless communication systems, are applicable to other mobile communication systems.

[0031] For any terms and techniques used in this disclosure that are not specifically described, please refer to wireless communication standards documents published prior to this disclosure.

[0032] In this disclosure, "A or B" may mean "A only", "B only", or "both A and B". In other words, in this disclosure, "A or B" can be interpreted as "A and / or B". For example, in this disclosure, "A, B or C" may mean "A only", "B only", "C only", or "any combination of A, B and C".

[0033] In this disclosure, a forward slash ( / ) or a comma (,) can mean "and / or". For example, "A / B" can mean "A and / or B". Therefore, "A / B" can mean "A only", "B only", or "both A and B". For example, "A, B, C" can mean "A, B, or C".

[0034] In this disclosure, "at least one of A and B" may mean "only A", "only B" or "both A and B". Furthermore, the expressions "at least one of A or B" or "at least one of A and / or B" in this disclosure may be interpreted as the same as "at least one of A and B".

[0035] Additionally, in this disclosure, "at least one of A, B, and C" may mean "A only", "B only", "C only" or "any combination of A, B, and C". Furthermore, "at least one of A, B, or C" or "at least one of A, B, and / or C" may mean "at least one of A, B, and C".

[0036] Furthermore, the brackets used in this disclosure may mean "for example". Specifically, when shown as "Control Information (PDCCH)", "PDCCH" can be cited as an example of "Control Information". In other words, "Control Information" in this disclosure is not limited to "PDCCH", and "PDCCH" can be cited as an example of "Control Information". Additionally, even when shown as "Control Information (i.e., PDCCH)", "PDCCH" can be cited as an example of "Control Information".

[0037] The technical features described individually in a single figure in this disclosure can be implemented individually or simultaneously.

[0038] While not limited thereto, the various descriptions, functions, processes, suggestions, methods and / or operation flowcharts disclosed herein can be applied to various fields requiring wireless communication and / or connectivity between devices (e.g., 5G).

[0039] In the following description, the present disclosure will be described in more detail with reference to the accompanying drawings. Unless otherwise stated, the same reference numerals in the following drawings and / or description may refer to the same and / or corresponding hardware blocks, software blocks and / or functional blocks.

[0040] Figure 1An example of a communication system that applies the implementation of this disclosure is shown.

[0041] Figure 1 The 5G use cases shown are merely illustrative, and the technical features of this disclosure can be applied to... Figure 1 Other 5G use cases not shown.

[0042] The three main demand categories for 5G include: (1) enhanced mobile broadband (eMBB), (2) massive machine-type communications (mMTC), and (3) ultra-reliable and low-latency communications (URLLC).

[0043] Reference Figure 1 The communication system 1 includes wireless devices 100a to 100f, a base station (BS) 200, and a network 300. Although Figure 1 An example of a 5G network as a network of communication system 1 is illustrated, but the implementation of this disclosure is not limited to 5G systems and can be applied to future communication systems other than 5G systems.

[0044] BS200 and Network 300 can be implemented as wireless devices, and a particular wireless device can operate as a BS / network node relative to other wireless devices.

[0045] Wireless devices 100a to 100f represent devices that perform communication using radio access technology (RAT) (e.g., 5G NR or LTE) and may be referred to as communication / radio / 5G devices. Wireless devices 100a to 100f may include, but are not limited to, robots 100a, vehicles 100b-1 and 100b-2, extended reality (XR) devices 100c, handheld devices 100d, home appliances 100e, Internet of Things (IoT) devices 100f, and artificial intelligence (AI) devices / servers 400. For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of communication between vehicles. Vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices and may be implemented in the form of head-mounted displays (HMDs), head-up displays (HUDs) installed in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Handheld devices may include smartphones, smart tablets, wearable devices (e.g., smartwatches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0046] In this disclosure, wireless devices 100a to 100f may be referred to as user equipment (UE). UE may include, for example, cellular phones, smartphones, laptop computers, digital broadcasting terminals, personal digital assistants (PDAs), portable multimedia players (PMPs), navigation systems, tablet PCs, ultrabooks, vehicles, vehicles with autonomous driving capabilities, connected cars, UAVs, AI modules, robots, AR devices, VR devices, MR devices, holographic devices, public safety devices, MTC devices, IoT devices, medical devices, FinTech devices (or financial devices), security devices, weather / environment devices, devices related to 5G services, or devices related to the Fourth Industrial Revolution.

[0047] Wireless devices 100a to 100f can connect to network 300 via BS200. AI technology can be applied to wireless devices 100a to 100f, and wireless devices 100a to 100f can connect to AI server 400 via network 300. Network 300 can be configured using 3G, 4G (e.g., LTE), 5G (e.g., NR), and super 5G networks. While wireless devices 100a to 100f can communicate with each other via BS200 / network 300, wireless devices 100a to 100f can also perform direct communication with each other without going through BS200 / network 300 (e.g., sidelink communication). For example, vehicles 100b-1 and 100b-2 can perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). IoT devices (e.g., sensors) can perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0048] Wireless communication / connections 150a, 150b, and 150c can be established between wireless devices 100a to 100f and / or between wireless devices 100a to 100f and BS200 and / or between BS200. These wireless communication / connections can be established via various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication (or device-to-device (D2D) communication) 150b, and inter-base station communication 150c (e.g., relay, integrated access and backhaul (IAB)). Wireless devices 100a to 100f and BS200 / wireless devices 100a to 100f can transmit / receive radio signals to / from each other via wireless communication / connections 150a, 150b, and 150c. For example, wireless communication / connections 150a, 150b, and 150c can transmit / receive signals via various physical channels. Therefore, at least a portion of various configuration information configuration processes, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and resource allocation processes for transmitting / receiving radio signals can be performed based on various proposals of this disclosure.

[0049] NR supports multiple parameter sets (numerologies) (and / or multiple subcarrier spacings (SCS)) to support a variety of 5G services. For example, if the SCS is 15kHz, wide-area coverage can be supported in traditional cellular bands, while if the SCS is 30kHz / 60kHz, dense urban areas, lower latency, and wider carrier bandwidth can be supported. If the SCS is 60kHz or higher, bandwidths greater than 24.25GHz can be supported to overcome phase noise.

[0050] NR bands can be defined as two types of frequency ranges: frequency range 1 (FR1) and frequency range 2 (FR2). The numerical values ​​of the frequency ranges can vary. For example, the two types (FR1 and FR2) of frequency ranges can be shown in Table 1 below. For ease of explanation, in the frequency ranges used in NR systems, FR1 can represent "the range below 6 GHz," FR2 can represent "the range above 6 GHz," and can be referred to as millimeter wave (mmW).

[0051] [Table 1]

[0052]

[0053]

[0054] As described above, the frequency range of the NR system can be varied. For example, FR1 can include a frequency band from 410MHz to 7125MHz as shown in Table 2 below. That is, FR1 can include a frequency band of 6GHz (or 5850MHz, 5900MHz, 5925MHz, etc.) or higher. For example, the 6GHz (or 5850MHz, 5900MHz, 5925MHz, etc.) or higher frequency band included in FR1 can include unlicensed frequency bands. Unlicensed frequency bands can be used for various purposes, such as for vehicle communications (e.g., autonomous driving).

[0055] [Table 2]

[0056] Frequency range name Corresponding frequency range Subcarrier spacing FR1 410MHz-7125MHz 15, 30, 60kHz FR2 24250MHz-52600MHz 60, 120, 240kHz

[0057] Here, the radio communication technologies implemented in the wireless devices of this disclosure may include narrowband Internet of Things (NB-IoT) technologies for low-power communication and LTE, NR, and 6G. For example, NB-IoT technology may be an example of low-power wide-area network (LPWAN) technology, implemented in specifications such as LTE Cat NB1 and / or LTE Cat NB2, and may not be limited to the names mentioned above. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices of this disclosure may communicate based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as enhanced machine-type communication (eMTC). For example, LTE-M technology may be implemented in at least one of various specifications, such as 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE machine-type communication, and / or 7) LTE M, and may not be limited to the names mentioned above. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices of this disclosure may include at least one of ZigBee, Bluetooth, and / or LPWAN, which take into account low-power communication, and may not be limited to the names mentioned above. For example, ZigBee technology may generate personal area networks (PANs) associated with small / low-power digital communication based on various specifications (such as IEEE 802.15.4) and may be referred to by various names. Figure 2 An example of a wireless device that applies the implementation of this disclosure is shown.

[0058] exist Figure 2 In this context, the first wireless device 100 and / or the second wireless device 200 can be implemented in various forms depending on the usage / service. For example, {the first wireless device 100 and the second wireless device 200} can correspond to... Figure 1The first wireless device 100 and / or the second wireless device 200 may be configured from various elements, devices / components and / or modules.

[0059] The first wireless device 100 may include at least one transceiver (e.g., transceiver 106), at least one processing chip (e.g., processing chip 101), and / or one or more antennas 108.

[0060] The processing chip 101 may include at least one processor (e.g., processor 102) and at least one memory (e.g., memory 104). Additionally and / or alternatively, the memory 104 may be located outside the processing chip 101.

[0061] Processor 102 can control memory 104 and / or transceiver 106, and can be adapted to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts described in this disclosure. For example, processor 102 can process information in memory 104 to generate first information / signal, and then transmit a radio signal including the first information / signal via transceiver 106. Processor 102 can receive a radio signal including a second information / signal via transceiver 106, and then store the information obtained by processing the second information / signal in memory 104.

[0062] Memory 104 may be operatively connected to processor 102. Memory 104 may store various types of information and / or instructions. Memory 104 may store firmware and / or software code 105, which implements code, commands, and / or command sets that, when executed by processor 102, execute the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, firmware and / or software code 105 may implement instructions that, when executed by processor 102, execute the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, firmware and / or software code 105 may control processor 102 to execute one or more protocols. For example, firmware and / or software code 105 may control processor 102 to execute one or more layers of wireless interface protocols.

[0063] In this document, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 106 may be connected to processor 102 and transmit and / or receive radio signals via one or more antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. Transceiver 106 may be used interchangeably with a radio frequency (RF) unit. In this disclosure, first wireless device 100 may represent a communication modem / circuit / chip.

[0064] The second wireless device 200 may include at least one transceiver (e.g., transceiver 206), at least one processing chip (e.g., processing chip 201), and / or one or more antennas 208.

[0065] The processing chip 201 may include at least one processor (e.g., processor 202) and at least one memory (e.g., memory 204). Additionally and / or alternatively, the memory 204 may be located outside the processing chip 201.

[0066] Processor 202 can control memory 204 and / or transceiver 206, and can be adapted to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts described in this disclosure. For example, processor 202 can process information in memory 204 to generate third information / signal, and then transmit a radio signal including the third information / signal via transceiver 206. Processor 202 can receive a radio signal including a fourth information / signal via transceiver 106, and then store the information obtained by processing the fourth information / signal in memory 204.

[0067] Memory 204 may be operatively connected to processor 202. Memory 204 may store various types of information and / or instructions. Memory 204 may store firmware and / or software code 205, which implements code, commands, and / or command sets that, when executed by processor 202, execute the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, firmware and / or software code 205 may implement instructions that, when executed by processor 202, execute the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, firmware and / or software code 205 may control processor 202 to execute one or more protocols. For example, firmware and / or software code 205 may control processor 202 to execute one or more layers of wireless interface protocols.

[0068] In this document, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 206 may be connected to processor 202 and transmit and / or receive radio signals via one or more antennas 208. Each of transceivers 206 may include a transmitter and / or a receiver. Transceivers 206 may be used interchangeably with RF units. In this disclosure, second wireless device 200 may represent a communication modem / circuit / chip.

[0069] The hardware elements of wireless devices 100 and 200 will be described in more detail below. One or more protocol layers may be implemented by, but are not limited to, one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as the Physical (PHY) layer, Media Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC) layer, and Service Data Adaptation Protocol (SDAP) layer). One or more processors 102 and 202 may generate one or more Protocol Data Units (PDUs), one or more Service Data Units (SDUs), messages, control information, data, or information in accordance with the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. One or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information, according to the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure, and provide the generated signals to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive signals (e.g., baseband signals) from one or more transceivers 106 and 206 and obtain PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure.

[0070] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field-programmable gate arrays (FPGAs) may be included in one or more processors 102 and 202. For example, one or more processors 102 and 202 may be configured by a set of communication control processors, application processors (APs), electronic control units (ECUs), central processing units (CPUs), graphics processing units (GPUs), and memory control processors.

[0071] One or more memories 104 and 204 can be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories 104 and 204 can be configured with random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EPROM), flash memory, volatile memory, non-volatile memory, hard disk drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. One or more memories 104 and 204 can be located internally and / or externally to one or more processors 102 and 202. One or more memories 104 and 204 can be connected to one or more processors 102 and 202 via various technologies such as wired or wireless connections.

[0072] One or more transceivers 106 and 206 can transmit user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure to one or more other devices. One or more transceivers 106 and 206 can receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure from one or more other devices. For example, one or more transceivers 106 and 206 can be connected to one or more processors 102 and 202 and transmit and receive radio signals. For example, one or more processors 102 and 202 can perform control to enable one or more transceivers 106 and 206 to transmit user data, control information, or radio signals to one or more other devices. One or more processors 102 and 202 can perform control to enable one or more transceivers 106 and 206 to receive user data, control information, or radio signals from one or more other devices.

[0073] One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208. Additionally or alternatively, one or more transceivers 106 and 206 may include one or more antennas 108 and 208. One or more transceivers 106 and 206 may be adapted to transmit and receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed herein via one or more antennas 108 and 208. In this disclosure, one or more antennas 108 and 208 may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0074] One or more transceivers 106 and 206 can convert received user data, control information, radio signals / channels, etc., from RF band signals to baseband signals, so that the received user data, control information, radio signals / channels, etc., can be processed by one or more processors 102 and 202. One or more transceivers 106 and 206 can also convert user data, control information, radio signals / channels, etc., processed by one or more processors 102 and 202 from baseband signals to RF band signals. For this purpose, one or more transceivers 106 and 206 may include (analog) oscillators and / or filters. For example, one or more transceivers 106 and 206, under the control of one or more processors 102 and 202, can up-convert OFDM baseband signals to OFDM signals using their (analog) oscillators and / or filters and transmit the up-converted OFDM signals at the carrier frequency. One or more transceivers 106 and 206 can receive OFDM signals on a carrier frequency and, under the control of one or more processors 102 and 202, downconvert the OFDM signals to OFDM baseband signals via their (analog) oscillators and / or filters.

[0075] although Figure 2 Not shown, but wireless devices 100 and 200 may also include additional components. The additional components 140 may be configured differently depending on the type of wireless devices 100 and 200. For example, the additional components 140 may include at least one of a power unit / battery, input / output (I / O) devices (e.g., audio I / O ports, video I / O ports), drive devices, and computing devices. The additional components 140 may be coupled to one or more processors 102 and 202 via various technologies such as wired or wireless connections.

[0076] In the implementations of this disclosure, the UE can be used as a transmitting device in the uplink (UL) and a receiving device in the downlink (DL). In the implementations of this disclosure, the BS can be used as a receiving device in the UL and a transmitting device in the DL. Hereinafter, for ease of description, it is primarily assumed that the first wireless device 100 is used as the UE and the second wireless device 200 is used as the BS. For example, a processor 102 connected to, installed on, or started in the first wireless device 100 can be adapted to perform UE actions according to the implementations of this disclosure or to control the transceiver 106 to perform UE actions according to the implementations of this disclosure. A processor 202 connected to, installed on, or started in the second wireless device 200 can be adapted to perform BS actions according to the implementations of this disclosure or to control the transceiver 206 to perform BS actions according to the implementations of this disclosure.

[0077] In this disclosure, BS is also referred to as Node B (NB), eNode B (eNB), or gNB.

[0078] Figure 3 An example of a UE that applies the implementation of this disclosure is shown.

[0079] Reference Figure 3 UE 100 can correspond to Figure 2 The first wireless device 100.

[0080] The UE 100 includes a processor 102, a memory 104, a transceiver 106, one or more antennas 108, a power management module 141, a battery 142, a display 143, a keypad 144, a subscriber identification module (SIM) card 145, a speaker 146, and a microphone 147.

[0081] Processor 102 may be adapted to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. Processor 102 may be adapted to control one or more other components of UE 100 to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. A radio interface protocol layer may be implemented in processor 102. Processor 102 may include an ASIC, other chipsets, logic circuits, and / or data processing means. Processor 102 may be an application processor. Processor 102 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). Examples of processor 102 may be provided in [the following text is missing from the original extract]. Manufacturing SNAPDRAGON TM Series processors EXYNOS manufactured TM Series processors A series of processors manufactured HELIO manufactured TM Series processors Manufactured ATOM TM It can be found in the series of processors or the corresponding next-generation processors.

[0082] Memory 104 is coupled to processor 102 during operation and stores various information to operate processor 102. Memory 104 may include ROM, RAM, flash memory, memory card, storage medium, and / or other storage devices. When the implementation is software-based, the techniques described herein can be implemented using modules (e.g., processes, functions, etc.) that perform the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed herein. These modules may be stored in memory 104 and implemented by processor 102. Memory 104 may be implemented within processor 102 or external to processor 102 (in which case, the memory may be communicatively coupled to processor 102 via various means known in the art).

[0083] Transceiver 106 is coupled to processor 102 during operation and transmits and / or receives radio signals. Transceiver 106 includes a transmitter and a receiver. Transceiver 106 may include baseband circuitry for processing radio frequency signals. Transceiver 106 controls one or more antennas 108 to transmit and / or receive radio signals.

[0084] The power management module 141 manages the power of the processor 102 and / or transceiver 106. The battery 142 supplies power to the power management module 141.

[0085] Display 143 outputs the results processed by processor 102. Keypad 144 receives input that will be used by processor 102. Keypad 144 can be displayed on display 143.

[0086] The SIM 145 is an integrated circuit designed to securely store the International Mobile Subscriber Identity (IMSI) number and its associated keys, used to identify and authenticate subscribers on mobile devices such as mobile phones and computers. Contact information can also be stored on many SIM cards.

[0087] Speaker 146 outputs the sound-related results processed by processor 102. Microphone 147 receives the sound-related inputs that will be used by processor 102.

[0088] Figure 4 and Figure 5 An example of a protocol stack in a 3GPP-based wireless communication system applying the implementation of this disclosure is shown.

[0089] Specifically, Figure 4 An example of the user plane protocol stack for the radio interface between the UE and the BS is shown, and Figure 5 An example of the radio interface control plane protocol stack between the UE and the BS is illustrated. The control plane refers to the path for transmitting control messages used for calls managed by the UE and the network. The user plane refers to the path for transmitting data generated in the application layer (e.g., voice data or Internet packet data). See reference... Figure 4 The user plane protocol stack can be divided into Layer 1 (L1, e.g., the PHY layer) and Layer 2 (L2, e.g., the MAC / RLC / PDCP layer). See [reference needed]. Figure 5 The control plane protocol stack can be divided into Layer 1 (L1, e.g., PHY layer), Layer 2 (L2, e.g., MAC / RLC / PDCP layer), Layer 3 (L3, e.g., RRC layer), and the Non-Access Layer (NAS). Layers 1, 2, and 3 are collectively referred to as the Access Layer (AS).

[0090] In 3GPP LTE systems, Layer 2 is separated into the following sublayers: MAC, RLC, and PDCP. In 3GPP NR systems, Layer 2 is separated into the following sublayers: MAC, RLC, PDCP, and SDAP. The PHY layer provides transport channels to the MAC sublayer, the MAC sublayer provides logical channels to the RLC sublayer, the RLC sublayer provides RLC channels to the PDCP sublayer, and the PDCP sublayer provides radio bearers to the SDAP sublayer. The SDAP sublayer provides Quality of Service (QoS) streams to the 5G core network.

[0091] In the 3GPP NR system, the main services and functions of the MAC sublayer include: mapping between logical channels and transport channels; multiplexing MAC SDUs belonging to one or different logical channels to / from the physical layer delivered to / from the transport channel a transport block (TB); demultiplexing from the TB; scheduling information reporting; error correction via Hybrid Automatic Repeat Request (HARQ) (one HARQ entity per cell in the case of carrier aggregation (CA); priority handling between UEs by means of dynamic scheduling; priority handling between logical channels of a UE by means of logical channel priority ordering; and padding. A single MAC entity can support multiple parameter sets, transmission timings, and cells. Mapping constraints in logical channel priority ordering control which parameter set(s), cell(s), and transmission timing(s) a logical channel(s) can use.

[0092] MAC provides different types of data transmission services. To accommodate these different services, various types of logical channels are defined, each supporting the transmission of a specific type of information. Each logical channel type is defined by the type of information being transmitted. Logical channels are divided into two groups: control channels and traffic channels. Control channels are used only for transmitting control plane information, and traffic channels are used only for transmitting user plane information. The Broadcast Control Channel (BCCH) is a downlink logical channel used for broadcasting system control information. The Paging Control Channel (PCCH) is a downlink logical channel that transmits paging information, system information change notifications, and indications of ongoing Public Warning Service (PWS) broadcasts. The Common Control Channel (CCCH) is a logical channel used to send control information between the UE and the network and is used by UEs without an RRC connection to the network. The Dedicated Control Channel (DCCH) is a point-to-point bidirectional logical channel used by UEs with an RRC connection to send dedicated control information between the UE and the network. The Dedicated Traffic Channel (DTCH) is a point-to-point logical channel dedicated to a single UE, used to transmit user information. DTCHs can exist in both the uplink and downlink. In the downlink, the following connections exist between logical channels and transport channels: BCCH can be mapped to the broadcast channel (BCH); BCCH can be mapped to the downlink shared channel (DL-SCH); PCCH can be mapped to the paging channel (PCH); CCCH can be mapped to DL-SCH; DCCH can be mapped to DL-SCH; and DTCH can be mapped to DL-SCH. In the uplink, the following connections exist between logical channels and transport channels: CCCH can be mapped to the uplink shared channel (UL-SCH); DCCH can be mapped to UL-SCH; and DTCH can be mapped to UL-SCH.

[0093] The RLC sublayer supports three transmission modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). RLC configuration is per logical channel, independent of parameter sets and / or transmission duration. In 3GPP NR systems, the main services and functions of the RLC sublayer depend on the transmission mode and include: transmission of upper-layer PDUs; sequence numbering independent of either PDCP (UM or AM); error correction via ARQ (AM only); RLC SDU segmentation (AM and UM) and resegmentation (AM only); SDU (AM and UM) reassembly; duplicate detection (AM only); RLC SDU discarding (AM and UM); RLC re-establishment; and protocol error detection (AM only).

[0094] In the 3GPP NR system, the main services and functions of the PDCP sublayer for the user plane include: sequence numbering; header compression and decompression using robust header compression (ROHC); transmission of user data; reordering and deduplication detection; in-order delivery; PDCP PDU routing (in the case of separate bearers); retransmission of PDCP SDUs; encryption, decryption, and integrity protection; PDCP SDU discarding; PDCP re-establishment and data recovery for RLC AM; PDCP status reporting for RLC AM; and PDCPPDU deduplication and deduplication indication for lower layers. The main services and functions of the PDCP sublayer for the control plane include: sequence numbering; encryption, decryption, and integrity protection; transmission of control plane data; reordering and deduplication detection; in-order delivery; and PDCPPDU deduplication and deduplication indication for lower layers.

[0095] In the 3GPP NR system, the main services and functions of SDAP include: mapping between QoS flows and data radio bearers; and marking QoS flow IDs (QFIs) in both DL and UL packets. A single SDAP protocol entity is configured for each individual PDU session.

[0096] In the 3GPP NR system, the main services and functions of the RRC sublayer include: broadcasting system information related to AS and NAS; paging initiated by 5GC or NG-RAN; establishment, maintenance, and release of RRC connections between UE and NG-RAN; security functions including key management; establishment, configuration, maintenance, and release of signaling radio bearers (SRB) and data radio bearers (DRB); mobility functions (including: handover and context delivery; UE cell selection and reselection and control of cell selection and reselection; inter-RAT mobility); QoS management functions; control of UE measurement reports and reports; detection and repair of radio link failures; and NAS message transmission from UE to NAS and from NAS to UE.

[0097] Figure 6 The frame structure in a 3GPP-based wireless communication system applying the implementation of this disclosure is shown.

[0098] Figure 6The frame structure shown is merely exemplary, and the number of subframes, the number of time slots, and / or the number of symbols in a frame can vary. In 3GPP-based wireless communication systems, OFDM parameter sets (e.g., subcarrier spacing (SCS), transmission time interval (TTI) durations) can be configured differently across multiple cells aggregated for a UE. For example, if the UE is configured with different SCSs for cells aggregated for cell aggregation, the (absolute time) duration of time resources (e.g., subframes, time slots, or TTIs) comprising the same number of symbols can be different across the aggregated cells. In this document, symbols can include OFDM symbols (or CP-OFDM symbols), SC-FDMA symbols (or Discrete Fourier Transform-Extended-OFDM (DFT-s-OFDM) symbols).

[0099] Reference Figure 6 Downlink and uplink transmissions are organized into frames. Each frame has a T f = 10ms duration. Each frame is divided into two half-frames, each half-frame having a duration of 5ms. Each half-frame consists of 5 subframes, each subframe having a duration T. sf It is 1ms. Each subframe is divided into time slots, and the number of time slots in a subframe depends on the subcarrier spacing. Each time slot includes 14 or 12 OFDM symbols based on the cyclic prefix (CP). In normal CP, each time slot includes 14 OFDM symbols, and in extended CP, each time slot includes 12 OFDM symbols. The parameter set is based on an exponentially scalable subcarrier spacing βf = 2. u *15kHz.

[0100] Table 3 shows the results based on subcarrier spacing βf = 2. u *Number of OFDM symbols N per slot for normal CP at 15kHz slot symb The number of time slots N in each frame frame，u slot And the number of time slots N in each subframe subframe，u slot .

[0101] [Table 3]

[0102] u <![CDATA[N slot symb ]]> <![CDATA[N frame，u slot ]]> <![CDATA[N subframe，u slot ]]> 0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16

[0103] Table 4 shows the results based on subcarrier spacing βf = 2. u *Number of OFDM symbols N per slot for extended CP at 15kHz slot symb The number of time slots N in each frame frame,u slot And the number of time slots N in each subframesubframe，u slot .

[0104] [Table 4]

[0105] u <![CDATA[N slot symb ]]> <![CDATA[N frame，u slot ]]> <![CDATA[N subframe，u slot ]]> 2 12 40 4

[0106] A time slot comprises multiple symbols (e.g., 14 or 12 symbols) in the time domain. For each parameter set (e.g., subcarrier spacing) and carrier, a Common Resource Block (CRB) is defined from the common resource block (CRB) indicated by higher-layer signaling (e.g., RRC signaling). start,u grid The beginning of N size,u grid，x *N RB sc Subcarriers and N subframe，u symb A resource grid of OFDM symbols, where N size,u grid,x N represents the number of resource blocks (RBs) in the resource grid, and the subscript x represents the DL for downlink and the UL for uplink. RB sc N is the number of subcarriers per RB. In 3GPP-based wireless communication systems, N... RB sc Typically 12. For a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL), there exists a resource grid. The carrier bandwidth N of the subcarrier spacing configuration u... size,u grid The parameters are given by higher-level parameters (e.g., RRC parameters). Each element in the resource grid for antenna port p and subcarrier spacing configuration u is called a resource element (RE), and a complex symbol can be mapped to each RE. Each RE in the resource grid is uniquely identified by an index k in the frequency domain and an index 1 in the time domain representing the symbol position relative to a reference point. In 3GPP-based wireless communication systems, RBs are defined by 12 consecutive subcarriers in the frequency domain. Figure 6As shown, with the SCS doubling, the slot length and symbol length are halved. For example, when the SCS is 15kHz, the slot length is 1ms, the same as the subframe length. When the SCS is 30kHz, the slot length is 0.5ms (=500us), and the symbol length is half that of the 15kHz SCS. When the SCS is 60kHz, the slot length is 0.25ms (=250us), and the symbol length is half that of the 30kHz SCS. When the SCS is 120kHz, the slot length is 0.125ms (=125us), and the symbol length is half that of the 60kHz SCS. When the SCS is 240kHz, the slot length is 0.0625ms (=62.5us), and the symbol length is half that of the 120kHz SCS.

[0107] In 3GPP NR systems, Resource Blocks (RBs) are classified into CRBs and Physical Resource Blocks (PRBs). For subcarrier spacing configuration u, CRBs are numbered from 0 upwards in the frequency domain. The center of subcarrier 0 of CRB0 used for subcarrier spacing configuration u coincides with "point A," which serves as the common reference point for the resource block grid. In 3GPP NR systems, PRBs are defined within the Bandwidth Part (BWP) and numbered from 0 to N. size BWP,i -1 is the number, where i is the number of bandwidth segments. The physical resource blocks n within bandwidth segment i are... PRB With public resource block n CRB The relationship between n is as follows: PRB =n CRB +N size BWP,i , where N size BWP，i A BWP is a common resource block, where the bandwidth portion begins relative to CRB0. A BWP comprises multiple consecutive RBs. A carrier can include up to N (e.g., 5) BWPs. A UE can be configured with one or more BWPs on a given component carrier. Only one of the multiple BWPs configured for a UE can be active at a time. The active BWP defines the UE's operating bandwidth within the cell's operating bandwidth.

[0108] In this disclosure, the term "cell" can refer to a geographical area in which one or more nodes provide a communication system or to a radio resource. A "cell" as a geographical area can be understood as the coverage area within which a node can provide services using a carrier, and a "cell" as a radio resource (e.g., a time-frequency resource) is associated with bandwidth as a frequency range configured by a carrier. A "cell" associated with a radio resource is defined by a combination of downlink and uplink resources (e.g., a combination of DL component carriers (CC) and ULCC). A cell can be configured by downlink resources only, or it can be configured by both downlink and uplink resources. Since DL coverage (which is the range within which a node can transmit a valid signal) and UL coverage (which is the range within which a node can receive a valid signal from a UE) depend on the carrier carrying the signal, a node's coverage area can be associated with the coverage area of ​​the "cell" of the radio resources used by the node. Therefore, the term "cell" can sometimes be used to refer to the service coverage area of ​​a node, at other times to a radio resource, or at other times to the range within which a signal using a radio resource can reach with effective strength.

[0109] In CA, two or more CCs are aggregated. A UE can receive or transmit on one or more CCs simultaneously, depending on its capabilities. CA is supported for both continuous and non-continuous CCs. When CA is configured, the UE has only one RRC connection with the network. During RRC connection establishment / re-establishment / handover, one serving cell provides NAS mobility information, and during RRC connection re-establishment / handover, one serving cell provides security input. This cell is called the primary cell (PCell). The PCell is the cell operating on the primary frequency, where the UE performs the initial connection establishment procedure or initiates the connection re-establishment procedure. Depending on the UE's capabilities, secondary cells (SCells) can be configured to form a set of serving cells together with the PCell. An SCell is a cell that provides additional radio resources above a special cell (SpCell). Therefore, the set of serving cells configured for a UE always consists of one PCell and one or more SCells. For dual connectivity (DC) operation, the term SpCell refers to the PCell of the primary cell group (MCG) or the primary SCell (PSCell) of the secondary cell group (SCG). SpCell supports PUCCH transmission and contention-based random access and is always active. MCG is a group of serving cells associated with the primary node, comprising SpCell (PCell) and optionally one or more SCells. For a UE with a DC configured, SCG is a subset of serving cells associated with the secondary node, comprising PSCell and zero or more SCells. For a UE in RRC_CONNECTED without a CA / DC configured, only one serving cell consisting of PCells exists. For a UE in RRC_CONNECTED with a CA / DC configured, the term "serving cell" is used to refer to the set of cells consisting of SpCell and all SCells. In the DC, two MAC entities are configured in the UE: one for the MCG and one for the SCG.

[0110] Figure 7 An example of a data flow in a 3GPP NR system applying the implementation of this disclosure is shown.

[0111] Reference Figure 7 "RB" indicates a radio bearer, and "H" indicates a header. Radio bearers are classified into two groups: DRBs for user plane data and SRBs for control plane data. MAC PDUs are sent / received to / from external devices via the PHY layer using radio resources. MAC PDUs arrive at the PHY layer in the form of transport blocks.

[0112] In the PHY layer, the uplink transport channel UL-SCH and random access channel (RACH) are mapped to their respective physical channels, the Physical Uplink Shared Channel (PUSCH) and the Physical Random Access Channel (PRACH), and the downlink transport channels DL-SCH, BCH, and PCH are mapped to the Physical Downlink Shared Channel (PDSCH), the Physical Broadcast Channel (PBCH), and the PDSCH, respectively. In the PHY layer, uplink control information (UCI) is mapped to the Physical Uplink Control Channel (PUCCH), and downlink control information (DCI) is mapped to the Physical Downlink Control Channel (PDCCH). The UE transmits MAC PDUs related to UL-SCH via PUSCH based on UL grant, and the BS transmits MAC PDUs related to DL-SCH via PDSCH based on DL assignment.

[0113] Figure 8 An example of a dual-connectivity (DC) architecture to which the technical features of this disclosure can be applied is shown.

[0114] Reference Figure 8 Examples include MN 811, SN 821, and UE 830, which communicates with both MN 811 and SN 821. Figure 8 As shown, DC refers to a scheme in which a UE (e.g., UE 830) utilizes radio resources provided by at least two RAN nodes, including an MN (e.g., MN 811) and one or more SNs (e.g., SN 821). In other words, DC refers to a scheme in which the UE connects to and communicates with both the MN and one or more SNs. Since the MN and SN may be in different sites, the backhaul between the MN and SN can be interpreted as a non-ideal backhaul (e.g., relatively large delays between nodes).

[0115] MN (e.g., MN 811) refers to the primary RAN node that provides services to the UE in the DC scenario. SN (e.g., SN 821) refers to an additional RAN node that provides services to the UE using MN in the DC scenario. If a RAN node provides services to the UE, then the RAN node can be MN. If MN exists, then SN can also exist.

[0116] For example, an MN can be associated with a macrocell whose coverage area is relatively larger than that of a small cell. However, an MN does not necessarily have to be associated with a macrocell; that is, an MN can be associated with a small cell. Throughout this disclosure, a RAN node associated with a macrocell can be referred to as a "macrocell node." An MN may include a macrocell node.

[0117] For example, a SN can be associated with a small cell (e.g., a microcell, picocell, femtocell) whose coverage area is relatively smaller than that of a macrocell. However, a SN does not necessarily have to be associated with a small cell—that is, a SN can be associated with a macrocell. Throughout this disclosure, a RAN node associated with a small cell can be referred to as a "small cell node." A SN may include a small cell node.

[0118] A Network Node (MN) can be associated with a Primary Cell Group (MCG). An MCG can refer to a group of serving cells associated with an MN and may include a primary cell (PCell) and one or more optional secondary cells (SCells). User plane data and / or control plane data can be transmitted from the core network to the MN via MCG bearers. An MCG bearer refers to a bearer within the MN that hosts radio protocols for using MN resources. Figure 8 As shown, the radio protocols carried by the MCG may include PDCP, RLC, MAC and / or PHY.

[0119] A Service Node (SN) can be associated with a Secondary Cell Group (SCG). An SCG can refer to a group of serving cells associated with the SN and may include primary and secondary cells (PSCells) and one or more optional SCells. User plane data can be transmitted from the core network to the SN via SCG bearers. An SCG bearer refers to a bearer within the SN that hosts radio protocols for using SN resources. Figure 8 As shown, the radio protocols carried by SCG may include PDCP, RLC, MAC, and PHY.

[0120] User plane data and / or control plane data can be transmitted from the core network to the MN and split / copied within the MN, with at least a portion of the split / copied data being forwarded to the SN via a split bearer. A split bearer refers to a radio protocol residing in both the MN and SN to utilize the resources of both. For example... Figure 8 As shown, the radio protocol for a split bearer located in MN may include PDCP, RLC, MAC, and PHY. The radio protocol for a split bearer located in SN may include RLC, MAC, and PHY.

[0121] According to various implementations, a PDCP anchor point / PDCP anchoring point / PDCP anchoring node refers to a RAN node that includes a PDCP entity that splits and / or replicates data and forwards at least a portion of the split / replicated data to another RAN node via the X2 / Xn interface. Figure 8 In the example, the PDCP anchor node can be MN.

[0122] Depending on the implementation method, the MN for the UE can be changed. This can be referred to as a handover or MN switching.

[0123] According to various implementation methods, the SN can start providing radio resources to the UE, establish a connection with the UE, and / or communicate with the UE (i.e., a new SN can be added for the UE). This can be referred to as SN addition.

[0124] According to various implementation methods, the SN for the UE can be changed while maintaining the MN for the UE. This can be referred to as SN change.

[0125] Depending on the implementation, the DC may include E-UTRAN NR-DC (EN-DC) and / or Multiple Radio Access Technology (RAT)-DC (MR-DC). EN-DC refers to a DC in which the UE utilizes radio resources provided by E-UTRAN nodes and NR RAN nodes. MR-DC refers to a DC in which the UE utilizes radio resources provided by RAN nodes with different RATs.

[0126] The following text describes the topic of mobility.

[0127] Mobility can include PCell changes, PSCell changes (or secondary node (SN) changes) and / or PSCell additions (or SN additions).

[0128] There can be at least two types of mobility: network-controlled mobility (or traditional mobility) and UE-based mobility (or conditional mobility).

[0129] Network-controlled mobility (or traditional mobility) involves the network determining the target cell for mobility and configuring the UE with mobility for that target cell. The network can send an RRCReconfiguration message to the UE that includes the configuration for the target cell. Upon receiving the cell configuration for the target cell, the UE can execute mobility for the target cell / apply the configuration for the target cell.

[0130] UE-based mobility (or conditional mobility) refers to the mobility where the network configures the UE with multiple candidate cells and the UE determines the target cell among the candidate cells that meets the mobility execution conditions. Conditional mobility can include at least one of conditional PCell change / conditional handover (CHO) or conditional PSCell mobility. Conditional PSCell mobility can include conditional PSCell addition / change (CPAC), including conditional PSCell addition (CPA) and / or conditional PSCell change (CPC). The network can send an RRCReconfiguration message to the UE including a ConditionalReconfiguration information element (IE), which includes a list of conditional reconfigurations for multiple candidate cells. Conditional reconfiguration for candidate cells can include a conditional reconfiguration identifier, mobility execution conditions for the candidate cell, and configuration for the candidate cell. The UE can evaluate mobility execution conditions for multiple candidate cells, and when the mobility execution conditions for a candidate cell are met, the UE can treat the candidate cell as the target cell and execute the mobility / application configuration for the target cell.

[0131] According to various implementation methods, a mobility execution condition is considered met / satisfied when an entry condition (or entering condition) is met / satisfied at least within the trigger time (TTT) for the mobility execution condition. An entry condition / entering condition may mean that the mobility execution condition is initially met. Once an entry condition is met, the mobility execution condition is considered met if the entry conditions are met consecutively within the duration TTT.

[0132] In this disclosure, the term “switch (HO)” may mean PCell change, or it may be a broad concept that includes not only PCell change but also PSCell change / addition.

[0133] In this disclosure, the terms “handover”, “mobility” and “cell handover” are used interchangeably.

[0134] In this disclosure, the description of switching can also be applied to other mobility processes (e.g., PSCell change / addition).

[0135] Figure 9 An example of a conditional mobility process according to an embodiment of the present disclosure is shown.

[0136] exist Figure 9 middle:

[0137] - The service BS can be associated with a PCell, and the PCell can be the source PCell for the CHO;

[0138] - A service BS can be an MN associated with a SN in a DC, where the SN can be associated with a source PSCell for a CPC; and

[0139] - The target cell can be a target PCcell for CHO or a target PSCell for CPA / CPC.

[0140] Reference Figure 9 In step S901, the UE can receive an RRCReconfiguration message from the serving BS, which includes a Conditional Reconfiguration Information Element (IE) (i.e., Conditional Reconfiguration). The Conditional Reconfiguration IE may include a list of conditional reconfigurations for candidate cells including the target cell. Each conditional reconfiguration in the list may be associated with a corresponding candidate cell and includes i) an identifier for the corresponding conditional reconfiguration (i.e., condReconfigId), ii) one or more execution conditions for the corresponding candidate cell (i.e., condExecutionCond), and / or iii) an RRC reconfiguration for the corresponding candidate cell including cell configuration for the corresponding candidate cell (i.e., condRRCReconfigi). One or more execution conditions may include CHO execution conditions, CPA execution conditions, and / or CPC execution conditions.

[0141] In step S903, the UE can begin evaluating one or more execution conditions for the candidate cell. Figure 9 In this context, it is assumed that the target cell meets the corresponding execution conditions.

[0142] In step S905, the UE can detach from the source PCell / PSCell (in the case of CHO / CPC), apply an RRC reconfiguration for the target cell including the cell configuration for the target cell, and / or synchronize to the target cell. If timing advance (TA) information for the target cell is available, the UE can skip random access toward the target cell—otherwise, the UE should perform random access toward the target cell (e.g., contention-free random access (CFRA) and / or contention-based random access (CBRA)).

[0143] In step S907, the UE can complete the conditional mobility procedure by sending an RRCReconfigurationComplete message to the target cell.

[0144] In some implementations, the UE can release the conditional reconfiguration after the conditional mobility procedure has been successfully completed.

[0145] The simultaneous evaluation of CHO and CPAC is described below.

[0146] In wireless communication systems, Callable Headquarters (CHOs) can be supported for both target MCGs and target SCGs, and CHO configurations that refer to or include CPC / CPA configurations (intended to be applied together) can also be supported. When a CHO is triggered, the UE can perform CPC / CPA configuration to begin CPC / CPA evaluation. CHO evaluation and CPC / CPA evaluation can be concurrent or sequential.

[0147] As mentioned above, CHOs with SCG configurations are already supported. However, CHOs with SCG configurations are still triggered under normal CHO triggering conditions (e.g., CondEventA3, CondEventA5) based solely on the quality of the target / source PCell. The drawback is that the target SCG (PSCell) is blindly added without considering its quality (or / and the source PSCell). Doing so may result in the addition of SCGs in poor radio conditions, and subsequent SCG failures, SCG failure recovery, and reconfiguration.

[0148] Therefore, a more optimized method also considers the conditions of the target / source PSCell. That is:

[0149] - The UE can be configured with a CHO and an associated SCG, and is configured to consider triggering conditions on the source / target PCell and source / target PSCell; and / or

[0150] - The UE will monitor two trigger conditions and execute the CHO with the associated SCG only if both trigger conditions are met.

[0151] In some scenarios, there may be several candidate PSCells for a specific PCell. This can be achieved by configuring a CHO with an associated SCG for each possible PSCell. However, this is inefficient signaling because the MCG configuration is repeated in each configuration. A better solution is to have CHOs that can utilize / be associated with multiple SCGs, each with its own trigger conditions. For example, a CHO can be associated with multiple SCGs, each with different trigger conditions.

[0152] For example, a UE can be configured with a CHO configuration having two associated SCGs (SCG1 and SCG2). If the trigger condition for PCell and PSCell1 is met, the UE will execute the CHO with SCG1. If the trigger condition for PCell and PSCell2 is met, the UE will execute the CHO with SCG2. Releasing all conditional reconfigurations while performing another conditional reconfiguration would result in unnecessary reconfiguration. Therefore, it is proposed that when a UE executes a CHO with multiple associated SCGs, the UE can be configured to maintain the configurations of the other SCGs associated with those SCGs and continue to monitor their trigger conditions.

[0153] Regarding the design of the RRC signaling structure, there are two main possibilities:

[0154] a) A CHO contains the MCG configuration (and trigger conditions) and the associated SCG configuration (and SCG trigger conditions).

[0155] b) The CHO contains only the MCG configuration (and the PCell change trigger condition), a separate configuration for each SCG (i.e., a CPC with an SCG configuration and a PSCell change trigger condition), and a configuration that associates the CHO with the SCG configuration (e.g., in a similar way to how a measurement object is associated with a measurement report configuration as a measurement ID).

[0156] In other words, at least one of the following structures can be considered for defining a CHO with an associated SCG:

[0157] a) A CHO configuration containing all MCG configurations, SCG configurations, and trigger conditions for PCell and PSCell changes; and / or

[0158] b) Individual CHO and CPAC configurations, and configurations that associate CHO with CPAC configurations.

[0159] According to various implementation methods, the UE can receive a conditional reconfiguration list (i.e., CondReconfigToAddModList IE) from the network. The IE CondReconfigToAddModList contains a list of conditional reconfigurations to be added or modified, where each entry includes a condReconfigId and associated fields, as shown in Table 5 below:

[0160] [Table 5]

[0161]

[0162]

[0163] In Table 5: -condExecutionCond (e.g., the second type of execution condition for the target PSCell) is the execution condition that needs to be met to trigger the conditional reconfiguration execution for CHO, CPA, intra-SN CPC without MN participation, inter-SN CPC initiated by MN, or subsequent intra-SN CPAC initiated by SN without MN participation. When configuring two triggering events (Meas Id) for a candidate cell, the network ensures that both refer to the same measObject. For CHO, if the network configures condEventD1 or condEventT1 for the candidate cell, the network configures a second triggering event condEventA3, condEventA4, or condEventA5 for the same candidate cell. The network does not configure both condEventD1 and condEventT1 for the same candidate cell. For CHO in a terrestrial network, the network does not indicate the MeasId associated with condEventA4. For CPA and inter-SN CPC initiated by MN, the network only indicates the MeasId associated with condEventA4. For CPCs within the SN and subsequent CPACs within the SN, the network only indicates the MeasId associated with condEventA3 or condEventA5;

[0164] -condExecutionCondPSCell (i.e., the first type of execution condition for the target PSCell) is the execution condition that the associated PSCell needs to be met to trigger the execution of a conditional reconfiguration for a CHO with a candidate SCG. The Meas Id refers to the measConfig associated with the MCG. When configuring two trigger events (MeasId) for a candidate cell, the network ensures that both refer to the same measObject. The network only indicates the MeasId associated with condEventA4;

[0165] -condExecutionCondSCG contains the execution conditions that need to be met to trigger the execution of a conditional reconfiguration for an SN-initiated inter-SN CPC, an SN-initiated inter-SN follow-up CPAC, an SN-initiated intra-SN follow-up CPAC with MN participation, or an MN-initiated inter-SN follow-up CPAC. The Meas Id refers to the measConfig associated with the SCG. When configuring two trigger events (Meas Ids) for a candidate cell, the network ensures that both refer to the same measObject. For each condReconfigId, the network always configures either condExecutionCond or condExecutionCondSCG (not both). The network only indicates the MeasId associated with condEventA3 or condEventA5;

[0166] -condRRCReconfig is an RRCReconfiguration message that includes the cell configuration for the corresponding target cell to be applied when the conditions are met. The RRCReconfiguration message included in condRRCReconfig cannot contain the field conditionalReconfiguration or the field daps-Config;

[0167] -scpac-ConfigComplete indicates whether the configuration included in condRRCReconfig for subsequent CPACs is a complete configuration; and

[0168] The `-subsequentCondReconfigi` field contains the execution conditions that need to be met to trigger the execution of subsequent CPACs (e.g., a second type of execution condition for the target PSCell). If this field is configured, configuration for candidate PSCells for subsequent CPACs is supported. When the `RRCReconfiguration` message contained in `condRRCReconfig` has been applied, subsequent execution conditions are used for conditional reconfiguration evaluation of other candidate cells.

[0169] After receiving the conditional reconfiguration list, the UE can perform a conditional reconfiguration evaluation. The UE should:

[0170] 1> For each condReconfigId within VarConditionalReconfig:

[0171] 2> If the RRCReconfiguration within condRRCReconfig includes a masterCellGroup containing reconfigurationWithSync, then:

[0172] 3> If an associated condExecutionCondPSCell is configured, then:

[0173] 4> Cells with physical cell identifiers that match the values ​​indicated in ServingCellConfigCommon included in reconfigurationWithSync within the masterCellGroup of the received condRRCReconfig are considered applicable cells; and

[0174] 4> Cells with physical cell identifiers that match the values ​​indicated in ServingCellConfigCommon included in reconfigurationWithSync within secondaryCellGroup in nr-SCG of the received condRRCReconfig are considered applicable cells;

[0175] 3> Otherwise:

[0176] 4> Cells with physical cell identifiers that match the values ​​indicated in ServingCellConfigCommon included in reconfigurationWithSync within the masterCellGroup in the received condRRCReconfig are considered applicable cells;

[0177] 2> Otherwise, if the RRCReconfiguration within condRRCReconfig includes a secondaryCellGroup containing reconfigurationWithSync:

[0178] 3> If the cell with a physical cell identifier that matches the value indicated in ServingCellConfigCommon included in reconfigurationWithSync within the secondaryCellGroup of the received condRRCReconfig is not a PSCell, then:

[0179] 4> The community is considered an applicable community;

[0180] 2> If condExecutionCondSCG is configured, then:

[0181] 3> In the remainder of this process, each measId indicated in condExecutionCondSCG is treated as a measId in VarMeasConfig associated with SCG measConfig;

[0182] 2> If condExecutionCondPSCell is configured, then:

[0183] 3> In the remainder of this process, each measId indicated in condExecutionCondPSCell is treated as a measId in VarMeasConfig associated with MCG measConfig;

[0184] 2> If condExecutionCond is configured, then:

[0185] 3> If it is configured via SRB3 or via SRB1 within nr-SCG or nr-SecondaryCellGroupConfig, then:

[0186] 4> In the remainder of this process, each measId indicated in condExecutionCond is treated as a measId in VarMeasConfig associated with SCGmeasConfig;

[0187] 3> Otherwise:

[0188] 4> In the remainder of this process, each measId indicated in condExecutionCond is treated as a measId in VarMeasConfig associated with MCGmeasConfig;

[0189] 2> For each measId included in the measIdList within the VarMeasConfig indicated in the condExecutionCond, condExecutionCondSCG, or condExecutionCondPSCell associated with condReconfigId, then:

[0190] 3> If condEventId is associated with condEventT1, and if, for the applicable cell, the entry conditions for the event associated with condReconfigId (i.e., the event corresponding to the condEventId of the corresponding condTriggerConfig within VarConditionalReconfig) are met; or

[0191] 3> If condEventId is associated with condEventD1, and if, during the corresponding timeToTrigger defined in VarConditionalReconfig for the event associated with condReconfigId (i.e., the event corresponding to condEventId of the corresponding condTriggerConfig in VarConditionalReconfig), the entry conditions applicable to the event are met for the applicable cell; or

[0192] 3> If condEventId is associated with condEventA3, condEventA4, or condEventA5, and if, for all measurements performed after Layer 3 filtering during the corresponding timeTotrigger defined in VarConditionalReconfig for this event (i.e., the event corresponding to the condEventId of the corresponding condTriggerConfig in VarConditionalReconfig), the entry conditions applicable to this event are met for the applicable cell, then:

[0193] 4> It is assumed that the event associated with this measId is satisfied;

[0194] 3> If the measId of the event associated with condReconfigId has been modified; or

[0195] 3> If condEventId is associated with condEventT1, and if, for the applicable cell, the departure condition applicable to the event associated with condReconfigId (i.e., the event corresponding to the condEventId of the corresponding condTriggerConfig within VarConditionalReconfig) is met; or

[0196] 3> If condEventId is associated with condEventD1, and if, during the corresponding timeToTrigger defined in VarConditionalReconfig for the event associated with condReconfigId (i.e., the event corresponding to condEventId of the corresponding condTriggerConfig in VarConditionalReconfig), the leave conditions applicable to the event are met for the applicable cell; or

[0197] 3> If condEventId is associated with condEventA3, condEventA4, or condEventA5, and if all measurements following layer 3 filtering performed during the corresponding timeTotrigger defined in VarConditionalReconfig for this event (i.e., the event corresponding to the condEventId of the corresponding condTriggerConfig in VarConditionalReconfig) satisfy the leave conditions applicable to this event for the applicable cell, then:

[0198] 4> The event associated with this measId is not considered to be satisfied;

[0199] 2> If condExecutionCondPSCell is not configured, then:

[0200] 3> If the events associated with all measIds within the condTriggerConfig for the applicable cell are satisfied, then:

[0201] 4> The applicable cell associated with this condReconfigId is considered the triggered cell;

[0202] 4> Initiate conditional reconfiguration execution;

[0203] 2> Otherwise:

[0204] 3> If the events associated with all measIds indicated in condExecutionCond and condExecutionCondPSCell within the stored condRRCReconfig for the target candidate cell are satisfied, then:

[0205] 4> Treat the target candidate PCell associated with the condReconfigId in the stored condRRCReconfig as the triggering PCell;

[0206] 4> Treat the target candidate PSCell associated with the condReconfigId in the stored condRRCReconfig as the triggered PSCell;

[0207] 4> Initiate conditional reconfiguration execution.

[0208] If condExecutionCondPSCell is not configured, up to two MeasIds can be configured for each condReconfigId. The conditional reconfiguration events for the two MeasIds can have the same or different event conditions, trigger amounts, trigger times, and trigger thresholds.

[0209] For a CHO with candidate SCGs, up to two MeasIds can be configured for condExecutionCond, and up to two MeasIds can be configured for condExecutionCondPSCell for each condReconfigId.

[0210] When conditional reconfiguration is performed, the UE should:

[0211] 1> If there are more than one pair of triggered PCells and associated triggered PSCells, then:

[0212] 2> Select either the triggering PCell or the associated triggering PSCell as the selected cell for conditional reconfiguration execution;

[0213] 1> Otherwise, if there is only one pair of triggering PCells and associated triggering PSCells, then:

[0214] 2> Treat the triggered PCell and associated triggered PSCell as the selected cell for conditional reconfiguration execution;

[0215] 1> Otherwise, if there is more than one triggered cell, then:

[0216] 2> Select one of the triggered cells as the selected cell for conditional reconfiguration execution;

[0217] 1> Otherwise:

[0218] 2> Treat the triggered cell as the selected cell for conditional reconfiguration execution;

[0219] 1> For the selected cell where conditional reconfiguration is performed:

[0220] 2> If subsequentCondReconfig is included in the entry of VarConditionalReconfig which contains the RRCReconfiguration message for the selected cell, then:

[0221] 3> Perform subsequent CPAC execution;

[0222] 2> Otherwise:

[0223] 3> Apply the stored condRRCReconfig of the selected cell, and apply the RRCReconfiguration in condRRCReconfig.

[0224] If multiple NR cells are triggered during a conditional reconfiguration execution, the UE can select one of them. For example, the UE can consider beam and / or beam quality to select one of the triggered cells for execution.

[0225] When performing a conditional reconfiguration for a subsequent CPAC, the UE should:

[0226] 1> If the selected subsequent CPAC candidate configuration is stored in MCG VarConditionalReconfig, then:

[0227] 2> Release / clear all current dedicated radio configurations, except for the following:

[0228] -MCG C-RNTI;

[0229] -AS security configuration associated with the master key and the secondary key;

[0230] - For each SRB / DRB in the current UE configuration:

[0231] - Maintain the associated RLC, PDCP, and SDAP entities, their state variables, buffers, and timers;

[0232] -Release all fields related to SRB / DRB configuration except for srb-Identity and drb-Identity;

[0233] -UE variables VarConditionalReconfig and VarServingSecurityCellSetID.

[0234] 2> Release / clear all current public radio configurations;

[0235] 1> Otherwise:

[0236] 2> Release / clear all current dedicated radio configurations associated with the SCG except for the following:

[0237] - AS security configuration associated with the secondary key;

[0238] - For each SRB / DRB in the current UE configuration using the secondary key:

[0239] - Maintain the associated RLC, PDCP, and SDAP entities, their state variables, buffers, and timers;

[0240] -Release all fields related to SRB / DRB configuration except for srb-Identity and drb-Identity;

[0241] -UE variable VarConditionalReconfig

[0242] 2> Release / clear all current public radio configurations associated with the SCG;

[0243] 1> Use the default values ​​for timers T310, T311 and constants N310, N311 for cell groups that trigger subsequent CPAC cell handover processes;

[0244] 1> If securityCellSetId is included in the entry of VarConditionalReconfig containing the RRCReconfiguration message, then:

[0245] 2> If servingSecurityCellSetId is not included in VarServingSecurityCellSetID; or

[0246] 2> If the value of securityCellSetId is not equal to the value of servingSecurityCellSetId within VarServingSecurityCellSetID, then:

[0247] 3> Treat the first sk-counter value in the sk-counterList associated with the securityCellSetId in VarConditionalReconfig as the selected sk-counter value and perform the security key update process;

[0248] 3> Remove the selected sk-Counter value from the sk-CounterList associated with the securityCellSetId within VarConditionalReconfig;

[0249] 3> If the current VarServingSecurityCellSetID includes servingSecurityCellSetId, then:

[0250] 4> Replace the value of servingSecurityCellSetId in VarServingSecurityCellSetID with the value of securityCellSetId associated with the selected cell;

[0251] 3> Otherwise:

[0252] 4> Store the servingSecurityCellSetId in VarServingSecurityCellSetID, where servingSecurityCellSetId has a value of securityCellSetId associated with the selected cell;

[0253] 1> If the selected subsequent CPAC candidate configuration is stored in SCG VarConditionalReconfig, then:

[0254] 2> For the secondary key (SK) indicated by keyToUse as part of the current UE configuration. gNB Each drb-Identity value included in the associated RadioBearerConfig:

[0255] 3> Trigger the AM DRB's PDCP entity to perform PDCP data recovery;

[0256] 3> Reconstruct the corresponding RLC entity;

[0257] 1> Otherwise:

[0258] 2> For each drb-Identity value included in RadioBearerConfig, which is part of the current UE configuration:

[0259] 3> If different keyToUse values ​​are configured; or

[0260] 3> If a new sk-Counter value is selected due to a conditional reconfiguration execution for subsequent CPACs, then:

[0261] 4> Trigger the carried PDCP entity to perform PDCP reconstruction;

[0262] 3> Otherwise:

[0263] 4> Trigger the AM DRB's PDCP entity to perform PDCP data recovery;

[0264] 4> Reconstruct the corresponding RLC entity;

[0265] 1> If scpac-ConfigComplete is not included in VarConditionalReconfig for the selected cell, then:

[0266] 2> If the subsequent CPAC candidate cell configuration is stored in MCG VarConditionalReconfig, then:

[0267] 3> Treat scpac-ReferenceConfiguration in MCG VarConditionalReconfig as the current UE configuration;

[0268] 2> Otherwise:

[0269] 3> Treat scpac-ReferenceConfiguration in SCG VarConditionalReconfig as the current SCG configuration;

[0270] When the UE considers the reference configuration to be the current UE configuration, the UE should store the fields and configurations that are part of the reference configuration, but should not perform any actions or procedures triggered by receiving the RRCReconfiguration message.

[0271] 1> Apply the stored condRRCReconfig of the selected cell and apply the RRCReconfiguration in condRRCReconfig.

[0272] 1> Release radio bearers and associated logical channels that are part of the current UE configuration but not part of the subsequent CPAC candidate configuration or subsequent CPAC reference configuration for the selected cell (in the case that the subsequent CPAC candidate configuration does not include scpac-ConfigComplete).

[0273] When the selected cell does not include scpac-ConfigComplete, the UE implementation can generate and store an RRC reconfiguration message by applying the received subsequent CPAC candidate configuration to the subsequent CPAC reference configuration before subsequent CPAC execution, and the stored RRC reconfiguration message is applied to subsequent CPAC execution.

[0274] In addition, the UE can be configured with a CHO and an SCG to be established for dual connectivity (DC) when the CHO is executed. The UE can also be configured with a CPC configuration, which is applied after the CHO is executed and the SCG is established.

[0275] The UE can then evaluate the CHO execution conditions. If the CHO execution conditions are met, the UE can execute the CHO for PCell handover and then establish an SCG to enable DC. After the SCG is established, the UE can begin evaluating the CPC execution conditions, and if the CPC execution conditions are met, the UE can perform an SCG change (or, PSCell change / SN change) by establishing a new SCG. During the sequence of the process flow, the UE has executed one CHO and performed two SCG establishments. The first SCG establishment is the establishment of SCG1 (i.e., SCG addition), and the second SCG establishment is the replacement of SCG1 with a new one (SCG2) (i.e., SCG change). If the UE can directly establish SCG2 without establishing SCG1, the first SCG establishment for SCG addition can be avoided.

[0276] To achieve direct SCG change during a CHO without performing SCG addition, the UE can be configured to evaluate both the CHO execution condition and the CPC execution condition, allowing the CHO and CPC to be jointly evaluated. Based on the joint evaluation result, the UE can either execute only the CHO or execute both the CHO and CPC jointly. To avoid redundant SCG addition, if a suitable CPC candidate exists simultaneously with the CHO execution, it is desirable to execute the CPC directly without SCG addition. However, since the CHO execution condition and the CPC execution condition are independent, the UE cannot know when or whether the CPC execution condition will be met. This presents a challenge for the UE in determining when / whether to execute only the CHO or both the CHO and CPC at an appropriate timing.

[0277] Therefore, this disclosure provides various implementations for handling when / whether to execute only CHO or to execute CHO and CPC together at an appropriate time.

[0278] Figure 10 An example of a method performed by a UE according to an embodiment of the present disclosure is shown. This method can also be performed by a wireless device.

[0279] Reference Figure 10 In step S1001, the UE can receive the configuration of CHO for the target PCell from the network.

[0280] The configuration for a CHO can include execution conditions for the CHO and execution conditions for conditional PSCell mobility to the first target PSCell.

[0281] The configuration for CHO can be related to the configuration for conditional PSCell mobility.

[0282] In step S1003, the UE can evaluate the execution conditions for CHO at the same time as evaluating the execution conditions for conditional PSCell mobility.

[0283] In step S1005, after the execution conditions for CHO are met but the execution conditions for conditional PSCell mobility are not met, the UE may delay the execution of CHO for a period of time.

[0284] In step S1007, based on the fact that the execution conditions for conditional PSCell mobility are not met during the time period, the UE can execute the CHO to the target PCell.

[0285] According to various implementation methods, based on the fact that the execution conditions for the CHO are met only within a portion of the TTT for the execution conditions for PSCell mobility, and the entry conditions for conditional PSCell mobility are also met, the UE can determine whether to delay the execution of the CHO based on the evaluation state of the execution conditions for conditional PSCell mobility. The evaluation state can be determined based on at least one of the following: the remaining TTT or a threshold of the execution conditions for conditional PSCell mobility after the execution conditions for the CHO are met.

[0286] According to various implementation methods, the UE can execute the CHO based on the remaining TTT being less than a threshold delay for the execution conditions of conditional PSCell mobility.

[0287] According to various implementation methods, based on the fact that the remaining TTT for the execution condition of conditional PSCell mobility is less than a threshold, the UE can start a timer with a timer value. The UE can delay the execution of the CHO while the timer is running.

[0288] According to various implementation methods, the timer value can be set to a time period and be greater than the remaining TTT for the execution conditions of conditional PSCell mobility.

[0289] According to various implementations, based on the fact that the entry condition for conditional PSCell mobility is met after the entry condition for CHO is met, the UE can determine whether to delay the execution of the CHO based on the evaluation state of the execution condition for the CHO. The evaluation state is determined based on at least one of the following: the remaining TTT of the execution condition for the CHO after the entry condition for conditional PSCell mobility is met, or a threshold.

[0290] According to various implementation methods, the UE can delay the execution of the CHO based on the remaining TTT being greater than or equal to a threshold for the execution conditions of the CHO.

[0291] According to various implementation methods, based on the remaining TTT (Time To Live) of the execution condition for the CHO being greater than or equal to a threshold, the UE can start a timer with a timer value. The UE can delay the execution of the CHO while the timer is running.

[0292] According to various implementations, the timer value can be set to a time period and equal to the TTT (Time To Time) for the execution condition of the conditional PSCell mobility. The start time of the timer can be equal to the start time of the TTT for the execution condition of the conditional PSCell mobility.

[0293] According to various implementation methods, the UE can execute a CHO when the timer expires.

[0294] According to various implementation methods, the UE can stop the timer based on the fact that the entry condition for conditional PSCell mobility is not met while the timer is running. The UE can execute a CHO when the timer is stopped.

[0295] According to various implementations, the configuration for CHO can be related to the configuration established for the SCG to the second target PSCell. The configuration for CHO may include RRC reconfiguration for the target PCell. RRC reconfiguration for the target PCell may include the configuration established for the SCG to the second target PSCell. To perform CHO, the UE may apply both the RRC reconfiguration for the target PCell and the configuration established for the SCG to the second target PSCell without applying mobility for the conditional PSCell.

[0296] According to various implementations, conditional PSCell mobility may include at least one of CPC or CPA.

[0297] Figure 11 An example of signal flow between a UE and a network node according to an embodiment of the present disclosure is shown. The network node may include a BS.

[0298] Reference Figure 11 In step S1101, the network node can obtain the configuration of the CHO for the target PCell.

[0299] The configuration for a CHO can include execution conditions for the CHO and execution conditions for conditional PSCell mobility to the first target PSCell. The configuration for a CHO can be related to the configuration for conditional PSCell mobility.

[0300] In step S1103, the network node can send the configuration of CHO for the target PCell to the UE.

[0301] In step S1105, the UE can evaluate the execution conditions for CHO at the same time as evaluating the execution conditions for conditional PSCell mobility.

[0302] In step S1107, after the execution conditions for CHO are met but the execution conditions for conditional PSCell mobility are not met, the UE may delay the execution of CHO for a period of time.

[0303] In step S1109, based on the fact that the execution conditions for conditional PSCell mobility are not met during this time period, the UE can execute the CHO to the target PCell.

[0304] Figure 12 A first example of a method for a CHO having concurrent early CPC, according to an embodiment of the present disclosure, is shown.

[0305] Reference Figure 12 In step S1201, the UE may receive CHO configuration for target PCell A, SCG configuration 1 for target PSCell B1 with SCG change / addition, and CPC configuration including SCG configuration 2 for target PSCell B2.

[0306] The UE can be configured with a CHO configuration for the target PCellA.

[0307] The UE can be configured with SCG configuration 1 for changing / adding SCGs for the target PSCell B1.

[0308] The UE can be configured with a CPC configuration including SCG configuration 2 for the target PSCell B2.

[0309] CHO configurations may include CHO execution conditions for target PCell A and / or CPC execution conditions for target PSCell B2. CPC configurations may include CPC execution conditions for target PSCell B2.

[0310] In step S1203, the UE can evaluate the CHO execution conditions and the CPC execution conditions. The UE can evaluate both the CHO execution conditions and the CPC execution conditions simultaneously. The UE can evaluate the CHO execution conditions while simultaneously evaluating the CPC execution conditions.

[0311] In step S1205, the UE may perform an action based on the evaluation status of the CHO execution condition and / or CPC execution condition.

[0312] For example, if the CHO execution conditions are met but the CPC execution conditions are not met, the UE can determine whether to delay the CHO execution for a period of time based on the evaluation status of the CPC execution conditions.

[0313] If the CPC execution conditions are not met within a short period of time according to the assessment status, the UE can immediately execute the CHO execution to jointly execute the CHO to PCellA according to SCG configuration 1 and establish an SCG for PSCell B1.

[0314] If the CPC execution conditions are expected to be met within a short period of time based on the assessment status, the UE can delay the CHO execution.

[0315] If CHO execution has been delayed but CPC execution conditions are not met within the expected time, the UE can immediately execute CHO execution and establish an SCG for PSCell B1 according to SCG configuration 1.

[0316] If CHO execution has been delayed and CPC execution conditions are met within the expected time, the UE can immediately execute CHO execution and CPC execution according to the CPC configuration (i.e., establish SCG for PSCell B2 according to SCG configuration 2).

[0317] For example, a UE can be configured with an SCG to be used during a CHO, but the UE can decide to delay the establishment of the SCG during a CHO based on the evaluation status of the CPC execution conditions.

[0318] If the assessment status indicates that the CPC execution conditions will not be met in the short term, the UE can immediately execute the CHO to execute the CHO to PCell A and establish an SCG for PSCell B1 during / after the CHO according to SCG configuration 1.

[0319] If the CPC execution conditions are expected to be met within a short period of time based on the assessment status, the UE can immediately execute the CHO for PCell A, instead of immediately establishing an SCG for PSCell B1 during / after the CHO based on SCG configuration 1. In other words, the UE can delay the establishment of the SCG for PSCell B1.

[0320] If the SCG establishment has been delayed, but the CPC execution conditions are not met within the expected time, the UE can establish an SCG for PSCell B1 according to SCG configuration 1 (i.e., perform SCG addition).

[0321] If CHO execution has been delayed and CPC execution conditions are met within the expected time, the UE can perform CPC execution according to CPC configuration (i.e., establish SCG for PSCellB2 according to SCG configuration 2) without establishing / adding SCG for PSCellB1 according to SCG configuration.

[0322] According to various implementation methods, the evaluation status of the execution conditions can indicate:

[0323] - Whether the entry conditions for execution are met;

[0324] - Whether the execution conditions are met; and / or

[0325] - Regarding execution conditions, how long does it take to satisfy the entry condition in TTT, or how short is the remaining duration after the duration of satisfying the entry condition in TTT.

[0326] An evaluation state can be defined in various ways, and examples of evaluation states are provided in... Figure 13 Example in.

[0327] Figure 13 An example of the evaluation state of CPC execution conditions according to an embodiment of the present disclosure is shown.

[0328] Reference Figure 13 The CHO execution condition is satisfied in T_c. Then, the UE can evaluate R calculated as R = T_d - T_c, where T_d is the expected time within TTT for satisfying the CPC execution condition (or the time when the TTT for the CPC execution condition ends).

[0329] If R is less than the threshold (i.e., R < threshold), then:

[0330] - The UE can delay the execution of the CHO for a period of time; or

[0331] - The UE can perform a CHO, but the SCG is not established immediately during / after the CHO (i.e., the UE can delay the establishment of the SCG).

[0332] If R is greater than or equal to the threshold (i.e., R ≥ the threshold), then:

[0333] -UE can execute the CHO immediately; or

[0334] -UE can execute CHO and establish SCG during / after CHO.

[0335] When CHO and / or SCG establishment is delayed, the UE can perform the following actions: Figure 14 The actions shown.

[0336] Figure 14 An example of timer-based CPC condition evaluation according to an embodiment of this disclosure is shown.

[0337] Reference Figure 14The UE can identify whether the CHO execution conditions are met (or, whether the CHO entry conditions are met within the TTT). The UE can then check whether the CPC entry conditions for the CPC have been met. If the CPC entry conditions are met, the UE can start a timer.

[0338] In some implementations, the UE can delay CHO execution when the timer starts and / or when the CPC entry condition and / or CHO execution condition are met. While the timer is running, if the CPC execution condition is met (i.e., the CPC entry condition is met within the TTT), the UE can jointly execute the CHO and CPC. If the timer expires (i.e., the CPC execution condition is not met while the timer is running), the UE can execute the CHO (and the associated SCG establishment) without CPC.

[0339] In some implementations, the UE can execute a CHO when the timer starts and / or when the CPC entry condition and / or CHO execution condition are met. If the timer runs during / after the CHO, the UE does not establish an SCG (i.e., the UE delays SCG establishment). While the timer is running, if the CPC execution condition is met (i.e., the CPC entry condition is met within the TTT), the UE can execute a CPC without SCG addition / establishment (i.e., establishing an SCG with a CPC candidate cell as the PSCell). If the timer expires, the UE can execute SCG addition / establishment (i.e., establishing an SCG according to the SCG configured for the CHO).

[0340] Figure 15 A second example of a method for CHOs with concurrent early stages, according to an embodiment of this disclosure, is shown.

[0341] Reference Figure 15 In step S1501, the UE can apply the configuration for PCell1 and the configuration for SCG1 including PSCell1. That is, the UE can be configured with PCell1 and SCG1 including PSCell1.

[0342] In step S1503, the UE may receive CHO configuration, SCG2 configuration, and CPC configuration.

[0343] The UE can be configured with CHO configuration, which may include configuration for PCell2 (which is a CHO candidate cell), MCG configuration for the CHO candidate cell, and / or CHO execution conditions for the CHO candidate cell.

[0344] The UE can also be configured with a configuration for SCG2 to be established when performing CHO to a CHO candidate cell, wherein the configuration for SCG2 may include the SpCell configuration of PSCell2 associated with SCG2.

[0345] The UE can also be configured with CPC configuration, which may include configuration for PSCell3 as a CPC candidate cell, configuration for SCG3 associated with the CPC candidate cell, and / or CPC execution conditions for the CPC candidate cell.

[0346] In step S1505, the UE can evaluate the CHO execution conditions and the CPC execution conditions. The UE can evaluate the CHO execution conditions and the CPC execution conditions simultaneously. The UE can evaluate the CHO execution conditions while evaluating the CPC execution conditions.

[0347] In step S1507, the UE may perform an action based on the evaluation status of the CHO execution condition and / or CPC execution condition.

[0348] If the entry conditions for CHO execution conditions are met, the UE can begin TTT for CHO execution conditions.

[0349] In some implementations, if the entry conditions for CPC execution conditions are met, the UE can begin TTT for CPC execution conditions.

[0350] When the time-to-time (TTT) for CHO execution conditions expires (i.e., the entry conditions for CHO execution conditions are met within the TTT):

[0351] If the remaining TTT for the CPC execution condition is less than the threshold, the UE can delay the CHO execution and start the first timer. The first timer value can be set to the remaining TTT value, or the remaining TTT value plus a non-negative value.

[0352] Otherwise (i.e., the remaining TTT for CPC execution conditions is greater than or equal to the threshold), the UE can execute CHO execution for CHO candidate cell PCell2 (therefore PCell2 becomes the serving PCell), establish MCG for CHO candidate cell PCell2, and establish SCG according to the configuration for SCG2 (therefore PSCell2 becomes the serving PCell).

[0353] In some implementations, if the entry conditions for CPC execution conditions are met, then:

[0354] - If the remaining time for the TTT under the CHO execution condition is less than a threshold, the UE will not start the TTT under the CPC execution condition; and / or

[0355] - If the remaining time for the TTT for the CHO execution condition is not less than a threshold (i.e., greater than or equal to the threshold), the UE can start the TTT for the CPC execution condition and start a second timer. The second timer value can be set to the TTT for the CPC execution condition, or the TTT for the CPC execution condition plus a non-negative value.

[0356] When the TTT for CHO execution conditions expires (i.e., the entry condition for CHO execution conditions is met within the TTT), if the TTT for CPC is running (or if the second timer is running), the UE may delay CHO execution while the second timer is running.

[0357] If the CPC entry condition is met during the first / second timer run, or the CPC execution condition is met during the first / second timer run (i.e., the CPC entry condition for TTT is met), then the UE can perform CHO execution and CPC execution according to the CPC configuration (i.e., SCG3 is established according to the configuration of SCG3 associated with PSCell3, so PSCell3 becomes the serving PSCell).

[0358] When the first timer / second timer expires (i.e., the CPC execution condition is not met while the first timer / second timer is running), the UE can execute the CHO execution of the CHO candidate cell (therefore PCell2 becomes the serving PCell), establish the MCG of the CHO candidate cell, and establish SCG2 according to the configuration for SCG2 (therefore PSCell2 becomes the serving PSCell).

[0359] If the CPC execution condition / CPC entry condition is no longer met while the first / second timer is running, the UE can stop the first / second timer. Upon stopping the first / second timer, the UE can perform CHO execution for the CHO candidate cell (thus PCell2 becomes the serving PCell), establish the MCG of the CHO candidate cell, and establish SCG2 according to the configuration for SCG2 (thus PSCell2 becomes the serving PSCell).

[0360] In addition, such as Figure 16 As shown, the UE can also delay CHO execution based on the CPA assessment status.

[0361] Figure 16 An example of a method for a CHO having concurrent early CPA is shown according to an embodiment of the present disclosure.

[0362] Reference Figure 16In step S1601, the UE can receive CHO configuration for target PCell A and CPA configuration for target PSCell B.

[0363] The UE can be configured with a CHO configuration that includes CHO execution conditions for target Pcell A. The UE can be configured with a CPA configuration that includes CPA execution conditions and SCG configuration for target PSCell B.

[0364] In step S1603, the UE can evaluate the CHO execution conditions and the CPA execution conditions. The UE can evaluate both the CHO and CPA execution conditions simultaneously. The UE can evaluate the CHO execution conditions while simultaneously evaluating the CPA execution conditions.

[0365] In step S1605, the UE may perform an action based on the evaluation status of the CHO execution condition and / or CPA execution condition.

[0366] For example, if the CHO execution conditions are met but the CPA execution conditions are not met, the UE can determine whether to delay the CHO execution for a period of time based on the evaluation status of the CPA execution conditions.

[0367] If the CPA execution conditions are not met within a short period of time, the UE can immediately execute the CHO of PCell A.

[0368] If the UE expects the CPC execution conditions to be met within a short period of time, it can delay the execution of CHO.

[0369] If CHO execution has been delayed, but CPC execution conditions are not met within the expected time, the UE can execute CHO execution immediately.

[0370] If CHO execution has been delayed and CPC execution conditions are met within the expected time, the UE can immediately execute CHO execution and CPA execution (i.e., establish SCG for PSCell B according to SCG configuration).

[0371] Furthermore, in this disclosure (for example, Figure 10 The method described from the UE's perspective (in Chinese) can be derived from... Figure 2 The first wireless device 100 and / or shown Figure 3 The UE 100 shown is used to execute this.

[0372] More specifically, the UE includes at least one transceiver, at least one processor, and at least one computer memory operatively connected to the at least one processor and storing instructions that perform operations based on execution by the at least one processor.

[0373] The operation includes: receiving from the network a configuration for a conditional handover (CHO) to a target primary cell (PCell), wherein the CHO configuration includes execution conditions for the CHO and execution conditions for conditional PSCell mobility to a first target primary secondary cell (PSCell), and wherein the CHO configuration is related to the configuration for conditional PSCell mobility; evaluating the CHO execution conditions while evaluating the execution conditions for conditional PSCell mobility; delaying the execution of the CHO for a period of time after the execution conditions for the CHO are met but the execution conditions for conditional PSCell mobility are not met; and executing the CHO to the target PCell based on the fact that the execution conditions for conditional PSCell mobility are not met during the period of time.

[0374] Furthermore, in this disclosure (for example, in Figure 10 The method described from the UE's perspective (in Chinese) can be stored in... Figure 2 The software code 105 in the memory 104 included in the first wireless device 100 shown is executed.

[0375] More specifically, at least one computer-readable medium (CRM) stores instructions that perform operations based on execution by at least one processor, the operations including: receiving from a network a configuration for a conditional handover (CHO) to a target primary cell (PCell), wherein the configuration for the CHO includes execution conditions for the CHO and execution conditions for conditional PSCell mobility to a first target primary secondary cell (PSCell), and wherein the configuration for the CHO is related to the configuration for conditional PSCell mobility; evaluating the execution conditions for the CHO while evaluating the execution conditions for conditional PSCell mobility; delaying the execution of the CHO for a period of time after the execution conditions for the CHO are met but the execution conditions for conditional PSCell mobility are not met; and executing the CHO to the target PCell based on the fact that the execution conditions for conditional PSCell mobility are not met during the period of time.

[0376] Furthermore, in this disclosure (for example, in Figure 10 The method described from the UE's perspective (in Chinese) can be... Figure 2 The processor 102 included in the first wireless device 100 shown controls and / or transmits data through... Figure 3 The processor 102 included in the UE 100 shown is used for execution.

[0377] More specifically, an apparatus (e.g., a wireless device / UE) configured / suited for operation in a wireless communication system includes at least one processor and at least one computer memory operatively connectable to the at least one processor. The at least one processor is configured / suited to perform an operation comprising: receiving from a network a configuration for a conditional handover (CHO) to a target primary cell (PCell), wherein the CHO configuration includes execution conditions for the CHO and execution conditions for conditional PSCell mobility to a first target primary secondary cell (PSCell), and wherein the CHO configuration is related to the configuration for conditional PSCell mobility; evaluating the CHO execution conditions while evaluating the execution conditions for conditional PSCell mobility; delaying the execution of the CHO for a period of time after the execution conditions for the CHO are met but the execution conditions for conditional PSCell mobility are not met; and executing the CHO to the target PCell based on the fact that the execution conditions for conditional PSCell mobility are not met during that period of time.

[0378] Furthermore, in this disclosure (for example, Figure 11 The method described from the perspective of network nodes (in Chinese) can be derived from... Figure 2 The second wireless device 200 shown in the figure performs this action.

[0379] More specifically, the network node includes at least one transceiver, at least one processor, and at least one computer memory operatively connected to the at least one processor and storing instructions that perform operations based on execution by the at least one processor.

[0380] The operation includes: obtaining a configuration for a conditional handover (CHO) to a target primary cell (PCell), wherein the CHO configuration includes execution conditions for the CHO and execution conditions for conditional PSCell mobility to a first target primary / secondary cell (PSCell), and wherein the CHO configuration is related to the configuration for conditional PSCell mobility; sending the CHO configuration to a user equipment (UE), wherein the UE is configured to perform operations including: evaluating the execution conditions for the CHO while evaluating the execution conditions for conditional PSCell mobility; delaying the execution of the CHO for a period of time after the execution conditions for the CHO are met but the execution conditions for conditional PSCell mobility are not met; and executing the CHO to the target PCell based on the fact that the execution conditions for conditional PSCell mobility are not met during the period of time.

[0381] This disclosure can have various beneficial effects.

[0382] For example, when conditional mobility is performed based on simultaneous evaluation of conditional handover (CHO) conditions and conditional primary / secondary cell (PSCell) mobility conditions, unnecessary signaling and / or disruptions can be prevented.

[0383] The beneficial effects that can be obtained through specific embodiments of this disclosure are not limited to those listed above. For example, there may be various technical effects that can be understood and / or derived from this disclosure by those skilled in the art. Therefore, the specific effects of this disclosure are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this disclosure.

[0384] The claims in this disclosure can be combined in various ways. For example, the technical features in the method claims of this disclosure can be combined to implement or perform in a device, and the technical features in the device claims can be combined to implement or perform in a method. Furthermore, the technical features in the method claims and device claims can be combined to implement or perform in a device. Other implementations are within the scope of the appended claims.

Claims

1. A method performed by a user equipment (UE) configured to operate in a wireless communication system, the method comprising the following steps: Receive the configuration of the conditional handover CHO for the target primary cell PCell from the network. The configuration for the CHO includes execution conditions for the CHO and execution conditions for conditional primary and secondary cell PSCell mobility to the first target PSCell. The configuration for the CHO is related to the configuration for the conditional PSCell mobility; The execution conditions for the CHO are evaluated simultaneously with the execution conditions for the conditional PSCell mobility. After the execution conditions for the CHO are met but the execution conditions for the conditional PSCell mobility are not met, the execution of the CHO is delayed for a period of time; and The CHO is executed to the target PCell if the execution conditions for the conditional PSCell mobility are not met during the time period.

2. The method according to claim 1, further comprising the following steps: Based on a portion of the trigger time TTT of the execution condition for the conditional PSCell mobility that satisfies the execution condition for the CHO, and the entry condition for the conditional PSCell mobility is satisfied, it is determined whether to delay the execution of the CHO based on the evaluation state of the execution condition for the conditional PSCell mobility. The evaluation status is determined based on at least one of the following: The remaining TTT for the execution conditions of the conditional PSCell mobility after the execution conditions for the CHO are met; or Threshold.

3. The method according to claim 2, wherein, The step of delaying the execution of the CHO includes delaying the execution of the CHO based on the remaining TTT being less than the threshold for the execution condition of the conditional PSCell mobility.

4. The method according to claim 2, further comprising the following steps: Based on the fact that the remaining TTT is less than the threshold according to the execution condition for the conditional PSCell mobility, a timer with a timer value is started. The step of delaying the execution of the CHO includes delaying the execution of the CHO while the timer is running.

5. The method according to claim 4, wherein, The timer value is set to the time period and is greater than the remaining TTT for the execution condition of the conditional PSCell mobility.

6. The method according to claim 1, further comprising the following steps: Based on the assumption that the entry condition for the conditional PSCell mobility is met after the entry condition for the CHO is met, a determination is made as to whether to delay the execution of the CHO based on the evaluation status of the execution condition for the CHO. The evaluation status is determined based on at least one of the following: The remaining trigger time TTT for the execution condition of the CHO after the entry condition for the conditional PSCell mobility is met; or Threshold.

7. The method according to claim 6, wherein, The step of delaying the execution of the CHO includes delaying the execution of the CHO based on the remaining TTT for the execution condition of the CHO being greater than or equal to the threshold.

8. The method according to claim 6, further comprising the following step: Based on the fact that the remaining TTT for the execution conditions of the CHO is greater than or equal to the threshold, a timer with a timer value is started. The step of delaying the execution of the CHO includes delaying the execution of the CHO during the operation of the timer.

9. The method according to claim 8, wherein, The timer value is set to the time period and is equal to the TTT of the execution condition for the conditional PSCell mobility. Wherein, the start time of the timer is equal to the start time of the TTT for the execution condition of the conditional PSCell mobility.

10. The method according to claim 4 or 8, wherein, The steps for performing the CHO include performing the CHO in the following situations: The timer expires; or The timer was stopped, and The timer is stopped based on the fact that the entry condition for the conditional PSCell mobility is not met while the timer is running.

11. The method according to claim 1, wherein, The configuration for the CHO is related to the configuration established for the secondary cell group (SCG) to the second target PSCell. The configuration for the CHO includes a reconfiguration of the Radio Resource Control (RRC) for the target PCell. The RRC reconfiguration for the target PSCell includes the configuration established for the SCG to the second target PSCell, and The step of performing the CHO includes applying the RRC reconfiguration for the target PCell and the configuration established for the SCG to the second target PSCell without applying the configuration for the conditional PSCell mobility.

12. The method according to claim 1, wherein, The conditional PSCell mobility includes at least one of conditional PSCell change CPC or conditional PSCell add CPA.

13. The method according to claim 1, wherein, The UE communicates with at least one of a mobile device, a network, or an autonomous vehicle.

14. A user equipment (UE) configured to operate in a wireless communication system, the UE comprising: At least one transceiver; At least one processor; as well as At least one memory, operatively coupled to the at least one processor and storing instructions that perform operations based on execution by the at least one processor, the operations including: Receive the configuration of the conditional handover CHO for the target primary cell PCell from the network. The configuration for the CHO includes execution conditions for the CHO and execution conditions for conditional primary and secondary cell PSCell mobility to the first target PSCell. The configuration for the CHO is related to the configuration for the conditional PSCell mobility; The execution conditions for the CHO are evaluated simultaneously with the execution conditions for the conditional PSCell mobility. After the execution conditions for the CHO are met but the execution conditions for the conditional PSCell mobility are not met, the execution of the CHO is delayed for a period of time; and The CHO is executed to the target PCell if the execution conditions for the conditional PSCell mobility are not met during the time period.

15. The UE according to claim 14, wherein, The UE is configured to implement the method according to any one of claims 2 to 13.

16. A network node configured to operate in a wireless communication system, the network node comprising: At least one transceiver; At least one processor; as well as At least one memory, operatively coupled to the at least one processor and storing instructions that perform operations based on execution by the at least one processor, the operations including: Obtain the configuration of the conditional handover CHO for the target primary cell PCell. The configuration for the CHO includes execution conditions for the CHO and execution conditions for conditional primary and secondary cell PSCell mobility to the first target PSCell. The configuration for the CHO is related to the configuration for the conditional PSCell mobility; and Send the configuration for the CHO to the target PCell to the user equipment (UE). The UE is configured to perform an operation, the operation including: The execution conditions for the CHO are evaluated simultaneously with the execution conditions for the conditional PSCell mobility. After the execution conditions for the CHO are met but the execution conditions for the conditional PSCell mobility are not met, the execution of the CHO is delayed for a period of time; and The CHO is executed to the target PCell if the execution conditions for the conditional PSCell mobility are not met during the time period.

17. A method performed by a network node configured to operate in a wireless communication system, the method comprising the steps of: Obtain the configuration of the conditional handover CHO for the target primary cell PCell. The configuration for the CHO includes execution conditions for the CHO and execution conditions for conditional primary and secondary cell PSCell mobility to the first target PSCell. The configuration for the CHO is related to the configuration for the conditional PSCell mobility; and Send the configuration for the CHO to the target PCell to the user equipment (UE). The UE is configured to perform an operation, the operation including: The execution conditions for the CHO are evaluated simultaneously with the execution conditions for the conditional PSCell mobility. After the execution conditions for the CHO are met but the execution conditions for the conditional PSCell mobility are not met, the execution of the CHO is delayed for a period of time; and The CHO is executed to the target PCell if the execution conditions for the conditional PSCell mobility are not met during the time period.

18. The method according to claim 17, wherein, The UE is configured to implement the method according to any one of claims 1 to 13.

19. An apparatus suitable for operation in a wireless communication system, the apparatus comprising: At least one processor; as well as At least one memory, operatively coupled to the at least one processor and storing instructions that perform operations based on execution by the at least one processor, the operations including: Receive the configuration of the conditional handover CHO for the target primary cell PCell from the network. The configuration for the CHO includes execution conditions for the CHO and execution conditions for conditional primary and secondary cell PSCell mobility to the first target PSCell. The configuration for the CHO is related to the configuration for the conditional PSCell mobility; The execution conditions for the CHO are evaluated simultaneously with the execution conditions for the conditional PSCell mobility. After the execution conditions for the CHO are met but the execution conditions for the conditional PSCell mobility are not met, the execution of the CHO is delayed for a period of time; and The CHO is executed to the target PCell if the execution conditions for the conditional PSCell mobility are not met during the time period.

20. A non-transitory computer-readable medium (CRM) storing program code implementing instructions that perform operations based on execution by at least one processor, the operations including: Receive the configuration of the conditional handover CHO for the target primary cell PCell from the network. The configuration for the CHO includes execution conditions for the CHO and execution conditions for conditional primary and secondary cell PSCell mobility to the first target PSCell. The configuration for the CHO is related to the configuration for the conditional PSCell mobility; The execution conditions for the CHO are evaluated simultaneously with the execution conditions for the conditional PSCell mobility. After the execution conditions for the CHO are met but the execution conditions for the conditional PSCell mobility are not met, the execution of the CHO is delayed for a period of time; and The CHO is executed to the target PCell if the execution conditions for the conditional PSCell mobility are not met during the time period.

Images