Mobility based on multiple execution conditions

Abstract

The present disclosure is related to mobility based on multiple execution conditions in wireless communications. According to an embodiment of the present disclosure, a method performed by a user equipment (UE) configured to operate in a wireless communication system comprises: receiving a conditional mobility configuration for a candidate cell comprising multiple execution conditions for the candidate cell, and a cell configuration for the candidate cell; receiving valid condition information for a validity of the multiple execution conditions; determining one or more valid execution conditions for the candidate cell among the multiple execution conditions, based on the valid condition information; evaluating the one or more valid execution conditions without evaluating one or more invalid execution conditions for the candidate cell other than the one or more valid execution conditions among the multiple execution conditions; and applying the cell configuration for the candidate cell based on the one or more valid execution conditions being fulfilled.

Description

MOBILITY BASED ON MULTIPLE EXECUTION CONDITIONS

[0001] The present disclosure is related to mobility based on multiple execution conditions in wireless communications.

[0002] 3rd Generation Partnership Project (3GPP) Long-Term Evolution (LTE) is a technology for enabling high-speed packet communications. Many schemes have been proposed for the LTE objective including those that aim to reduce user and provider costs, improve service quality, and expand and improve coverage and system capacity. The 3GPP LTE requires reduced cost per bit, increased service availability, flexible use of a frequency band, a simple structure, an open interface, and adequate power consumption of a terminal as an upper-level requirement.

[0003] Work has started in International Telecommunication Union (ITU) and 3GPP to develop requirements and specifications for New Radio (NR) systems. 3GPP has to identify and develop the technology components needed for successfully standardizing the new RAT timely satisfying both the urgent market needs, and the more long-term requirements set forth by the ITU Radio communication sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process. Further, the NR should be able to use any spectrum band ranging at least up to 100 GHz that may be made available for wireless communications even in a more distant future.

[0004] The NR targets a single technical framework addressing all usage scenarios, requirements and deployment scenarios including enhanced Mobile BroadBand (eMBB), massive Machine Type Communications (mMTC), Ultra-Reliable and Low Latency Communications (URLLC), etc. The NR shall be inherently forward compatible.

[0005] In communication systems, user equipment (UE) mobility between different cells or base stations is a key functionality to ensure continuous service and connectivity. Such mobility has been managed based on predefined events, such as signal strength thresholds or quality metrics of serving and neighboring cells. However, as network architectures and service requirements evolve, more dynamic and adaptive mobility management techniques have been proposed.

[0006] In particular, certain approaches involve condition-based mobility control, in which the decision to trigger a handover or cell reselection is based not only on fixed threshold values, but also on one or more conditions associated with network configurations, UE capabilities, service requirements, or environmental contexts. For example, handover procedures may be conditionally initiated when specific combinations of measurement results and UE states are satisfied.

[0007] Such condition-based mobility techniques aim to enhance flexibility and adaptability in mobility management, allowing for more context-aware and optimized mobility decisions. Nonetheless, the mechanisms for determining, signalling, and evaluating such conditions, as well as for executing mobility procedures accordingly, remain complex and are still under development.

[0008] An aspect of the present disclosure is to provide method and apparatus for mobility based on multiple execution conditions in a wireless communication system.

[0009] According to an embodiment of the present disclosure, a method performed by a user equipment (UE) configured to operate in a wireless communication system comprises: receiving a conditional mobility configuration for a candidate cell comprising multiple execution conditions for the candidate cell, and a cell configuration for the candidate cell; receiving valid condition information for a validity of the multiple execution conditions; determining one or more valid execution conditions for the candidate cell among the multiple execution conditions, based on the valid condition information; evaluating the one or more valid execution conditions without evaluating one or more invalid execution conditions for the candidate cell other than the one or more valid execution conditions among the multiple execution conditions; and applying the cell configuration for the candidate cell based on the one or more valid execution conditions being fulfilled.

[0010] According to an embodiment of the present disclosure, a method performed by a network node configured to operate in a wireless communication system comprises: transmitting, to a user equipment (UE), a conditional mobility configuration for a candidate cell comprising multiple execution conditions for the candidate cell, and a cell configuration for the candidate cell; and transmitting, to the UE, valid condition information for a validity of the multiple execution conditions, wherein the UE is configured to perform operations comprising: determining one or more valid execution conditions for the candidate cell among the multiple execution conditions, based on the valid condition information; evaluating the one or more valid execution conditions without evaluating one or more invalid execution conditions for the candidate cell other than the one or more valid execution conditions among the multiple execution conditions; and applying the cell configuration for the candidate cell based on the one or more valid execution conditions being fulfilled.

[0011] According to various embodiments, apparatuses to implement the above methods are provided.

[0012] The present disclosure may have various advantageous effects.

[0013] For example, the network can provide a single pre-configuration including the L1 execution condition and the L3 execution condition and also indicate which execution condition should be applicable to initiate mobility. Therefore, the UE doesn't need to receive duplicated pre-configuration for the same candidate cell for the L3 execution based conditional mobility and the L1 execution condition based LTM cell switching. Also, the UE doesn't need to receive frequent pre-configuration updates from the network due to execution condition changes for the same candidate cell.

[0014] Advantageous effects which can be obtained through specific embodiments of the present disclosure are not limited to the advantageous effects listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art can understand and / or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that may be understood or derived from the technical features of the present disclosure.

[0015] FIG. 1 shows an example of a communication system to which implementations of the present disclosure is applied.

[0016] FIG. 2 shows an example of wireless devices to which implementations of the present disclosure is applied.

[0017] FIG. 3 shows an example of UE to which implementations of the present disclosure is applied.

[0018] FIGs. 4 and 5 show an example of protocol stacks in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

[0019] FIG. 6 shows a frame structure in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

[0020] FIG. 7 shows a data flow example in the 3GPP NR system to which implementations of the present disclosure is applied.

[0021] FIG. 8 shows an example of a conditional mobility procedure according to an embodiment of the present disclosure.

[0022] FIG. 9 shows an example of a signalling procedure for LTM according to an embodiment of the present disclosure.

[0023] FIG. 10 shows an example of a method performed by a UE for mobility based on multiple execution conditions according to an embodiment of the present disclosure.

[0024] FIG. 11 shows an example of a signal flow between UE and network node for mobility based on multiple execution conditions according to an embodiment of the present disclosure.

[0025] FIG. 12 shows an example of a signal flow for combined L1 and L3 mobility according to an embodiment of the present disclosure.

[0026] The following techniques, apparatuses, and systems may be applied to a variety of wireless multiple access systems. Examples of the multiple access systems include a Code Division Multiple Access (CDMA) system, a Frequency Division Multiple Access (FDMA) system, a Time Division Multiple Access (TDMA) system, an Orthogonal Frequency Division Multiple Access (OFDMA) system, a Single Carrier Frequency Division Multiple Access (SC-FDMA) system, and a Multi Carrier Frequency Division Multiple Access (MC-FDMA) system. CDMA may be embodied through radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA may be embodied through radio technology such as Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data rates for GSM Evolution (EDGE). OFDMA may be embodied through radio technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is a part of a Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long-Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE employs OFDMA in downlink (DL) and SC-FDMA in uplink (UL). Evolution of 3GPP LTE includes LTE-Advanced (LTE-A), LTE-A Pro, and / or 5G New Radio (NR).

[0027] For convenience of description, implementations of the present disclosure are mainly described in regards to a 3GPP based wireless communication system. However, the technical features of the present disclosure are not limited thereto. For example, although the following detailed description is given based on a mobile communication system corresponding to a 3GPP based wireless communication system, aspects of the present disclosure that are not limited to 3GPP based wireless communication system are applicable to other mobile communication systems.

[0028] For terms and technologies which are not specifically described among the terms of and technologies employed in the present disclosure, the wireless communication standard documents published before the present disclosure may be referenced.

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

[0030] In the present disclosure, slash ( / ) or comma (,) may mean "and / or". For example, "A / B" may mean "A and / or B". Accordingly, "A / B" may mean "only A", "only B", or "both A and B". For example, "A, B, C" may mean "A, B or C".

[0031] In the present disclosure, "at least one of A and B" may mean "only A", "only B" or "both A and B". In addition, the expression "at least one of A or B" or "at least one of A and / or B" in the present disclosure may be interpreted as same as "at least one of A and B".

[0032] In addition, in the present disclosure, "at least one of A, B and C" may mean "only A", "only B", "only C", or "any combination of A, B and C". In addition, "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".

[0033] Also, parentheses used in the present disclosure may mean "for example". In detail, when it is shown as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information". In other words, "control information" in the present disclosure is not limited to "PDCCH", and "PDCCH" may be proposed as an example of "control information". In addition, even when shown as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information".

[0034] Technical features that are separately described in one drawing in the present disclosure may be implemented separately or simultaneously.

[0035] Although not limited thereto, various descriptions, functions, procedures, suggestions, methods and / or operational flowcharts of the present disclosure disclosed herein can be applied to various fields requiring wireless communication and / or connection (e.g., 5G) between devices.

[0036] Hereinafter, the present disclosure will be described in more detail with reference to drawings. The same reference numerals in the following drawings and / or descriptions may refer to the same and / or corresponding hardware blocks, software blocks, and / or functional blocks unless otherwise indicated.

[0037] FIG. 1 shows an example of a communication system to which implementations of the present disclosure is applied.

[0038] The 5G usage scenarios shown in FIG. 1 are only exemplary, and the technical features of the present disclosure can be applied to other 5G usage scenarios which are not shown in FIG. 1.

[0039] Three main requirement categories for 5G include (1) a category of enhanced Mobile BroadBand (eMBB), (2) a category of massive Machine Type Communication (mMTC), and (3) a category of Ultra-Reliable and Low Latency Communications (URLLC).

[0040] Referring to FIG. 1, the communication system 1 includes wireless devices 100a to 100f, Base Stations (BSs) 200, and a network 300. Although FIG. 1 illustrates a 5G network as an example of the network of the communication system 1, the implementations of the present disclosure are not limited to the 5G system, and can be applied to the future communication system beyond the 5G system.

[0041] The BSs 200 and the network 300 may be implemented as wireless devices and a specific wireless device may operate as a BS / network node with respect to other wireless devices.

[0042] The wireless devices 100a to 100f represent devices performing communication using Radio Access Technology (RAT) (e.g., 5G NR or LTE) and may be referred to as communication / radio / 5G devices. The wireless devices 100a to 100f may include, without being limited to, a robot 100a, vehicles 100b-1 and 100b-2, an eXtended Reality (XR) device 100c, a hand-held device 100d, a home appliance 100e, an Internet-of-Things (IoT) device 100f, and an Artificial Intelligence (AI) device / server 400. For example, the vehicles may include a vehicle having a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. The vehicles may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). The XR device may include an Augmented Reality (AR) / Virtual Reality (VR) / Mixed Reality (MR) device and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), and a computer (e.g., a notebook). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include a sensor and a smartmeter.

[0043] In the present disclosure, the wireless devices 100a to 100f may be called User Equipments (UEs). A UE may include, for example, a cellular phone, a smartphone, a laptop computer, a digital broadcast terminal, a Personal Digital Assistant (PDA), a Portable Multimedia Player (PMP), a navigation system, a slate Personal Computer (PC), a tablet PC, an ultrabook, a vehicle, a vehicle having an autonomous traveling function, a connected car, an UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a FinTech device (or a financial device), a security device, a weather / environment device, a device related to a 5G service, or a device related to a fourth industrial revolution field.

[0044] The wireless devices 100a to 100f may be connected to the network 300 via the BSs 200. An AI technology may be applied to the wireless devices 100a to 100f and the wireless devices 100a to 100f may be connected to the AI server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a beyond-5G network. Although the wireless devices 100a to 100f may communicate with each other through the BSs 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., sidelink communication) with each other without passing through the BSs 200 / network 300. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., Vehicle-to-Vehicle (V2V) / Vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0045] Wireless communication / connections 150a, 150b and 150c may be established between the wireless devices 100a to 100f and / or between wireless device 100a to 100f and BS 200 and / or between BSs 200. Herein, the wireless communication / connections may be established through various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication (or Device-to-Device (D2D) communication) 150b, inter-base station communication 150c (e.g., relay, Integrated Access and Backhaul (IAB)), etc. The wireless devices 100a to 100f and the BSs 200 / the wireless devices 100a to 100f may transmit / receive radio signals to / from each other through the wireless communication / connections 150a, 150b and 150c. For example, the wireless communication / connections 150a, 150b and 150c may transmit / receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, and resource mapping / de-mapping), and resource allocating processes, for transmitting / receiving radio signals, may be performed based on the various proposals of the present disclosure.

[0046] NR supports multiples numerologies (and / or multiple Sub-Carrier Spacings (SCS)) to support various 5G services. For example, if SCS is 15 kHz, wide area can be supported in traditional cellular bands, and if SCS is 30 kHz / 60 kHz, dense-urban, lower latency, and wider carrier bandwidth can be supported. If SCS is 60 kHz or higher, bandwidths greater than 24.25 GHz can be supported to overcome phase noise.

[0047] The NR frequency band may be defined as two types of frequency range, i.e., Frequency Range 1 (FR1) and Frequency Range 2 (FR2). The numerical value of the frequency range may be changed. For example, the frequency ranges of the two types (FR1 and FR2) may be as shown in Table 1 below. For ease of explanation, in the frequency ranges used in the NR system, FR1 may mean "sub 6 GHz range", FR2 may mean "above 6 GHz range," and may be referred to as millimeter Wave (mmW).

[0048] Frequency Range designationCorresponding frequency rangeSubcarrier SpacingFR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0049] As mentioned above, the numerical value of the frequency range of the NR system may be changed. For example, FR1 may include a frequency band of 410MHz to 7125MHz as shown in Table 2 below. That is, FR1 may include a frequency band of 6GHz (or 5850, 5900, 5925 MHz, etc.) or more. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or more included in FR1 may include an unlicensed band. Unlicensed bands may be used for a variety of purposes, for example for communication for vehicles (e.g., autonomous driving).

[0050] Frequency Range designationCorresponding frequency rangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0051] Here, the radio communication technologies implemented in the wireless devices in the present disclosure may include NarrowBand IoT (NB-IoT) technology for low-power communication as well as LTE, NR and 6G. For example, NB-IoT technology may be an example of Low Power Wide Area Network (LPWAN) technology, may be implemented in specifications such as LTE Cat NB1 and / or LTE Cat NB2, and may not be limited to the above-mentioned names. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices in the present disclosure may communicate based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and be called by various names such as enhanced MTC (eMTC). For example, LTE-M technology may be implemented in at least one of the 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 above-mentioned names. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices in the present 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 above-mentioned names. 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 called various names.FIG. 2 shows an example of wireless devices to which implementations of the present disclosure is applied.

[0052] In FIG. 2, The first wireless device 100 and / or the second wireless device 200 may be implemented in various forms according to use cases / services. For example, {the first wireless device 100 and the second wireless device 200} may correspond to at least one of {the wireless device 100a to 100f and the BS 200}, {the wireless device 100a to 100f and the wireless device 100a to 100f} and / or {the BS 200 and the BS 200} of FIG. 1. The first wireless device 100 and / or the second wireless device 200 may be configured by various elements, devices / parts, and / or modules.

[0053] The first wireless device 100 may include at least one transceiver, such as a transceiver 106, at least one processing chip, such as a processing chip 101, and / or one or more antennas 108.

[0054] The processing chip 101 may include at least one processor, such a processor 102, and at least one memory, such as a memory 104. Additional and / or alternatively, the memory 104 may be placed outside of the processing chip 101.

[0055] The processor 102 may control the memory 104 and / or the transceiver 106 and may be adapted to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts described in the present disclosure. For example, the processor 102 may process information within the memory 104 to generate first information / signals and then transmit radio signals including the first information / signals through the transceiver 106. The processor 102 may receive radio signals including second information / signals through the transceiver 106 and then store information obtained by processing the second information / signals in the memory 104.

[0056] The memory 104 may be operably connectable to the processor 102. The memory 104 may store various types of information and / or instructions. The memory 104 may store a firmware and / or a software code 105 which implements codes, commands, and / or a set of commands that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or the software code 105 may implement instructions that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or the software code 105 may control the processor 102 to perform one or more protocols. For example, the firmware and / or the software code 105 may control the processor 102 to perform one or more layers of the radio interface protocol.

[0057] Herein, the processor 102 and the memory 104 may be a part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and transmit and / or receive radio signals through one or more antennas 108. Each of the transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be interchangeably used with Radio Frequency (RF) unit(s). In the present disclosure, the first wireless device 100 may represent a communication modem / circuit / chip.

[0058] The second wireless device 200 may include at least one transceiver, such as a transceiver 206, at least one processing chip, such as a processing chip 201, and / or one or more antennas 208.

[0059] The processing chip 201 may include at least one processor, such a processor 202, and at least one memory, such as a memory 204. Additional and / or alternatively, the memory 204 may be placed outside of the processing chip 201.

[0060] The processor 202 may control the memory 204 and / or the transceiver 206 and may be adapted to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts described in the present disclosure. For example, the processor 202 may process information within the memory 204 to generate third information / signals and then transmit radio signals including the third information / signals through the transceiver 206. The processor 202 may receive radio signals including fourth information / signals through the transceiver 106 and then store information obtained by processing the fourth information / signals in the memory 204.

[0061] The memory 204 may be operably connectable to the processor 202. The memory 204 may store various types of information and / or instructions. The memory 204 may store a firmware and / or a software code 205 which implements codes, commands, and / or a set of commands that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or the software code 205 may implement instructions that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or the software code 205 may control the processor 202 to perform one or more protocols. For example, the firmware and / or the software code 205 may control the processor 202 to perform one or more layers of the radio interface protocol.

[0062] Herein, the processor 202 and the memory 204 may be a part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and transmit and / or receive radio signals through one or more antennas 208. Each of the transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be interchangeably used with RF unit. In the present disclosure, the second wireless device 200 may represent a communication modem / circuit / chip.

[0063] Hereinafter, hardware elements of the wireless devices 100 and 200 will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or more processors 102 and 202. For example, the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as 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). The one or more processors 102 and 202 may generate one or more Protocol Data Units (PDUs), one or more Service Data Unit (SDUs), messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The 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, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive the signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure.

[0064] The one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The 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 the one or more processors 102 and 202. For example, the one or more processors 102 and 202 may be configured by a set of a communication control processor, an Application Processor (AP), an Electronic Control Unit (ECU), a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), and a memory control processor.

[0065] The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and / or commands. The one or more memories 104 and 204 may be configured by 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 drive, register, cash memory, computer-readable storage medium, and / or combinations thereof. The one or more memories 104 and 204 may be located at the interior and / or exterior of the one or more processors 102 and 202. The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 through various technologies such as wired or wireless connection.

[0066] The one or more transceivers 106 and 206 may transmit user data, control information, and / or radio signals / channels, mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure, to one or more other devices. The one or more transceivers 106 and 206 may receive user data, control information, and / or radio signals / channels, mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure, from one or more other devices. For example, the one or more transceivers 106 and 206 may be connected to the one or more processors 102 and 202 and transmit and receive radio signals. For example, the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. The one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices.

[0067] The one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208. Additionally and / or alternatively, the one or more transceivers 106 and 206 may include one or more antennas 108 and 208. The 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, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure, through the one or more antennas 108 and 208. In the present disclosure, the one or more antennas 108 and 208 may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

[0068] The one or more transceivers 106 and 206 may convert received user data, control information, radio signals / channels, etc., from RF band signals into baseband signals in order to process received user data, control information, radio signals / channels, etc., using the one or more processors 102 and 202. The one or more transceivers 106 and 206 may convert the user data, control information, radio signals / channels, etc., processed using the one or more processors 102 and 202 from the base band signals into the RF band signals. To this end, the one or more transceivers 106 and 206 may include (analog) oscillators and / or filters. For example, the one or more transceivers 106 and 206 can up-convert OFDM baseband signals to OFDM signals by their (analog) oscillators and / or filters under the control of the one or more processors 102 and 202 and transmit the up-converted OFDM signals at the carrier frequency. The one or more transceivers 106 and 206 may receive OFDM signals at a carrier frequency and down-convert the OFDM signals into OFDM baseband signals by their (analog) oscillators and / or filters under the control of the one or more processors 102 and 202.

[0069] Although not shown in FIG. 2, the wireless devices 100 and 200 may further include additional components. The additional components 140 may be variously configured according to types of the wireless devices 100 and 200. For example, the additional components 140 may include at least one of a power unit / battery, an Input / Output (I / O) device (e.g., audio I / O port, video I / O port), a driving device, and a computing device. The additional components 140 may be coupled to the one or more processors 102 and 202 via various technologies, such as a wired or wireless connection.

[0070] In the implementations of the present disclosure, a UE may operate as a transmitting device in Uplink (UL) and as a receiving device in Downlink (DL). In the implementations of the present disclosure, a BS may operate as a receiving device in UL and as a transmitting device in DL. Hereinafter, for convenience of description, it is mainly assumed that the first wireless device 100 acts as the UE, and the second wireless device 200 acts as the BS. For example, the processor(s) 102 connected to, mounted on or launched in the first wireless device 100 may be adapted to perform the UE behavior according to an implementation of the present disclosure or control the transceiver(s) 106 to perform the UE behavior according to an implementation of the present disclosure. The processor(s) 202 connected to, mounted on or launched in the second wireless device 200 may be adapted to perform the BS behavior according to an implementation of the present disclosure or control the transceiver(s) 206 to perform the BS behavior according to an implementation of the present disclosure.

[0071] In the present disclosure, a BS is also referred to as a node B (NB), an eNode B (eNB), or a gNB.

[0072] FIG. 3 shows an example of UE to which implementations of the present disclosure is applied.

[0073] Referring to FIG. 3, a UE 100 may correspond to the first wireless device 100 of FIG. 2.

[0074] A 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.

[0075] The processor 102 may be adapted to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The processor 102 may be adapted to control one or more other components of the UE 100 to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. Layers of the radio interface protocol may be implemented in the processor 102. The processor 102 may include ASIC, other chipset, logic circuit and / or data processing device. The processor 102 may be an application processor. The processor 102 may include at least one of DSP, CPU, GPU, a modem (modulator and demodulator). An example of the processor 102 may be found in SNAPDRAGONTMseries of processors made by Qualcomm®, EXYNOSTMseries of processors made by Samsung®, A series of processors made by Apple®, HELIOTMseries of processors made by MediaTek®, ATOMTMseries of processors made by Intel®or a corresponding next generation processor.

[0076] The memory 104 is operatively coupled with the processor 102 and stores a variety of information to operate the processor 102. The memory 104 may include ROM, RAM, flash memory, memory card, storage medium and / or other storage device. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The modules can be stored in the memory 104 and executed by the processor 102. The memory 104 can be implemented within the processor 102 or external to the processor 102 in which case those can be communicatively coupled to the processor 102 via various means as is known in the art.

[0077] The transceiver 106 is operatively coupled with the processor 102, and transmits and / or receives a radio signal. The transceiver 106 includes a transmitter and a receiver. The transceiver 106 may include baseband circuitry to process radio frequency signals. The transceiver 106 controls the one or more antennas 108 to transmit and / or receive a radio signal.

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

[0079] The display 143 outputs results processed by the processor 102. The keypad 144 receives inputs to be used by the processor 102. The keypad 144 may be shown on the display 143.

[0080] The SIM card 145 is an　integrated circuit　that is intended to　securely store the　International Mobile Subscriber Identity　(IMSI) number and its related　key, which are used to identify and authenticate subscribers on　mobile telephony　devices (such as　mobile phones　and　computers). It is also possible to store contact information on many SIM cards.

[0081] The speaker 146 outputs sound-related results processed by the processor 102. The microphone 147 receives sound-related inputs to be used by the processor 102.

[0082] FIGs. 4 and 5 show an example of protocol stacks in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

[0083] In particular, FIG. 4 illustrates an example of a radio interface user plane protocol stack between a UE and a BS and FIG. 5 illustrates an example of a radio interface control plane protocol stack between a UE and a BS. The control plane refers to a path through which control messages used to manage call by a UE and a network are transported. The user plane refers to a path through which data generated in an application layer, for example, voice data or Internet packet data are transported. Referring to FIG. 4, the user plane protocol stack may be divided into Layer 1 (L1, for example PHY layer) and Layer 2 (L2, for example MAC / RLC / PDCP layer). Referring to FIG. 5, the control plane protocol stack may be divided into Layer 1 (L1, for example PHY layer), Layer 2 (L2, for example MAC / RLC / PDCP layer), Layer 3 (L3, for example an RRC layer), and a non-access stratum (NAS) layer. Layer 1, Layer 2 and Layer 3 are referred to as an access stratum (AS).

[0084] In the 3GPP LTE system, the Layer 2 is split into the following sublayers: MAC, RLC, and PDCP. In the 3GPP NR system, the Layer 2 is split into the following sublayers: MAC, RLC, PDCP and SDAP. The PHY layer offers to the MAC sublayer transport channels, the MAC sublayer offers to the RLC sublayer logical channels, the RLC sublayer offers to the PDCP sublayer RLC channels, the PDCP sublayer offers to the SDAP sublayer radio bearers. The SDAP sublayer offers to 5G core network quality of service (QoS) flows.

[0085] In the 3GPP NR system, the main services and functions of the MAC sublayer include: mapping between logical channels and transport channels; multiplexing / de-multiplexing of MAC SDUs belonging to one or different logical channels into / from transport blocks (TB) delivered to / from the physical layer on transport channels; scheduling information reporting; error correction through hybrid automatic repeat request (HARQ) (one HARQ entity per cell in case of carrier aggregation (CA)); priority handling between UEs by means of dynamic scheduling; priority handling between logical channels of one UE by means of logical channel prioritization; padding. A single MAC entity may support multiple numerologies, transmission timings and cells. Mapping restrictions in logical channel prioritization control which numerology(ies), cell(s), and transmission timing(s) a logical channel can use.

[0086] Different kinds of data transfer services are offered by MAC. To accommodate different kinds of data transfer services, multiple types of logical channels are defined, i.e., each supporting transfer of a particular type of information. Each logical channel type is defined by what type of information is transferred. Logical channels are classified into two groups: control channels and traffic channels. Control channels are used for the transfer of control plane information only, and traffic channels are used for the transfer of user plane information only. Broadcast control channel (BCCH) is a downlink logical channel for broadcasting system control information, paging control channel (PCCH) is a downlink logical channel that transfers paging information, system information change notifications and indications of ongoing public warning service (PWS) broadcasts, common control channel (CCCH) is a logical channel for transmitting control information between UEs and network and used for UEs having no RRC connection with the network, and dedicated control channel (DCCH) is a point-to-point bi-directional logical channel that transmits dedicated control information between a UE and the network and used by UEs having an RRC connection. Dedicated traffic channel (DTCH) is a point-to-point logical channel, dedicated to one UE, for the transfer of user information. A DTCH can exist in both uplink and downlink. In downlink, the following connections between logical channels and transport channels exist: BCCH can be mapped to broadcast channel (BCH); BCCH can be mapped to downlink shared channel (DL-SCH); PCCH can be mapped to 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 uplink, the following connections between logical channels and transport channels exist: CCCH can be mapped to uplink shared channel (UL-SCH); DCCH can be mapped to UL-SCH; and DTCH can be mapped to UL-SCH.

[0087] The RLC sublayer supports three transmission modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged node (AM). The RLC configuration is per logical channel with no dependency on numerologies and / or transmission durations. In the 3GPP NR system, the main services and functions of the RLC sublayer depend on the transmission mode and include: transfer of upper layer PDUs; sequence numbering independent of the one in PDCP (UM and AM); error correction through ARQ (AM only); segmentation (AM and UM) and re-segmentation (AM only) of RLC SDUs; reassembly of SDU (AM and UM); duplicate detection (AM only); RLC SDU discard (AM and UM); RLC re-establishment; protocol error detection (AM only).

[0088] 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); transfer of user data; reordering and duplicate detection; in-order delivery; PDCP PDU routing (in case of split bearers); retransmission of PDCP SDUs; ciphering, deciphering and integrity protection; PDCP SDU discard; PDCP re-establishment and data recovery for RLC AM; PDCP status reporting for RLC AM; duplication of PDCP PDUs and duplicate discard indication to lower layers. The main services and functions of the PDCP sublayer for the control plane include: sequence numbering; ciphering, deciphering and integrity protection; transfer of control plane data; reordering and duplicate detection; in-order delivery; duplication of PDCP PDUs and duplicate discard indication to lower layers.

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

[0090] In the 3GPP NR system, the main services and functions of the RRC sublayer include: broadcast of system information related to AS and NAS; paging initiated by 5GC or NG-RAN; establishment, maintenance and release of an RRC connection between the UE and NG-RAN; security functions including key management; establishment, configuration, maintenance and release of signalling radio bearers (SRBs) and data radio bearers (DRBs); mobility functions (including: handover and context transfer, UE cell selection and reselection and control of cell selection and reselection, inter-RAT mobility); QoS management functions; UE measurement reporting and control of the reporting; detection of and recovery from radio link failure; NAS message transfer to / from NAS from / to UE.

[0091] FIG. 6 shows a frame structure in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

[0092] The frame structure shown in FIG. 6 is purely exemplary and the number of subframes, the number of slots, and / or the number of symbols in a frame may be variously changed. In the 3GPP based wireless communication system, OFDM numerologies (e.g., subcarrier spacing (SCS), transmission time interval (TTI) duration) may be differently configured between a plurality of cells aggregated for one UE. For example, if a UE is configured with different SCSs for cells aggregated for the cell, an (absolute time) duration of a time resource (e.g., a subframe, a slot, or a TTI) including the same number of symbols may be different among the aggregated cells. Herein, symbols may include OFDM symbols (or CP-OFDM symbols), SC-FDMA symbols (or discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbols).

[0093] Referring to FIG. 6, downlink and uplink transmissions are organized into frames. Each frame has Tf= 10ms duration. Each frame is divided into two half-frames, where each of the half-frames has 5ms duration. Each half-frame consists of 5 subframes, where the duration Tsfper subframe is 1ms. Each subframe is divided into slots and the number of slots in a subframe depends on a subcarrier spacing. Each slot includes 14 or 12 OFDM symbols based on a cyclic prefix (CP). In a normal CP, each slot includes 14 OFDM symbols and, in an extended CP, each slot includes 12 OFDM symbols. The numerology is based on exponentially scalable subcarrier spacing βf = 2u*15 kHz.

[0094] Table 3 shows the number of OFDM symbols per slot Nslotsymb, the number of slots per frameNframe,uslot, and the number of slots per subframe Nsubframe,uslotfor the normal CP, according to the subcarrier spacing βf = 2u*15 kHz.

[0095] uNslotsymbNframe,uslotNsubframe,uslot01410111420221440431480841416016

[0096] Table 4 shows the number of OFDM symbols per slot Nslotsymb, the number of slots per frameNframe,uslot, and the number of slots per subframe Nsubframe,uslotfor the extended CP, according to the subcarrier spacing βf = 2u*15 kHz.

[0097] uNslotsymbNframe,uslotNsubframe,uslot212404

[0098] A slot includes plural symbols (e.g., 14 or 12 symbols) in the time domain. For each numerology (e.g., subcarrier spacing) and carrier, a resource grid ofNsize,ugrid,x*NRBscsubcarriers andNsubframe,usymbOFDM symbols is defined, starting at common resource block (CRB)Nstart,ugridindicated by higher-layer signalling (e.g., RRC signalling), whereNsize,ugrid,xis the number of resource blocks (RBs) in the resource grid and the subscript x is DL for downlink and UL for uplink.NRBscis the number of subcarriers per RB. In the 3GPP based wireless communication system,NRBscis 12 generally. There is one resource grid for a given antenna portp, subcarrier spacing configurationu, and transmission direction (DL or UL). The carrier bandwidthNsize,ugridfor subcarrier spacing configurationuis given by the higher-layer parameter (e.g., RRC parameter). Each element in the resource grid for the antenna portpand the subcarrier spacing configurationuis referred to as a resource element (RE) and one complex symbol may be mapped to each RE. Each RE in the resource grid is uniquely identified by an indexkin the frequency domain and an indexlrepresenting a symbol location relative to a reference point in the time domain. In the 3GPP based wireless communication system, an RB is defined by 12 consecutive subcarriers in the frequency domain. As shown in FIG. 6, as SCS doubles, the slot length and symbol length are halved. For example, when SCS is 15kHz, the slot length is 1ms, which is the same as the subframe length. When SCS is 30kHz, the slot length is 0.5ms (=500us), and the symbol length is half of that when the SCS is 15kHz. When SCS is 60kHz, the slot length is 0.25ms (=250us), and the symbol length is half of that when the SCS is 30kHz. When SCS is 120kHz, the slot length is 0.125ms (=125us), and the symbol length is half of that when the SCS is 60kHz. When SCS is 240kHz, the slot length is 0.0625ms (=62.5us), and the symbol length is half of that when the SCS is 120kHz.

[0099] In the 3GPP NR system, RBs are classified into CRBs and physical resource blocks (PRBs). CRBs are numbered from 0 and upwards in the frequency domain for subcarrier spacing configurationu. The center of subcarrier 0 of CRB 0 for subcarrier spacing configurationucoincides with 'point A' which serves as a common reference point for resource block grids. In the 3GPP NR system, PRBs are defined within a bandwidth part (BWP) and numbered from 0 toNsizeBWP,i-1, where i is the number of the bandwidth part. The relation between the physical resource block nPRBin the bandwidth part i and the common resource block nCRBis as follows: nPRB= nCRB+NsizeBWP,i, whereNsizeBWP,iis the common resource block where bandwidth part starts relative to CRB 0. The BWP includes a plurality of consecutive RBs. A carrier may include a maximum of N (e.g., 5) BWPs. A UE may be configured with one or more BWPs on a given component carrier. Only one BWP among BWPs configured to the UE can active at a time. The active BWP defines the UE's operating bandwidth within the cell's operating bandwidth.

[0100] In the present disclosure, the term "cell" may refer to a geographic area to which one or more nodes provide a communication system, or refer to radio resources. A "cell" as a geographic area may be understood as coverage within which a node can provide service using a carrier and a "cell" as radio resources (e.g., time-frequency resources) is associated with bandwidth which is a frequency range configured by the carrier. The "cell" associated with the radio resources is defined by a combination of downlink resources and uplink resources, for example, a combination of a DL component carrier (CC) and a UL CC. The cell may be configured by downlink resources only, or may be configured by downlink resources and uplink resources. Since DL coverage, which is a range within which the node is capable of transmitting a valid signal, and UL coverage, which is a range within which the node is capable of receiving the valid signal from the UE, depends upon a carrier carrying the signal, the coverage of the node may be associated with coverage of the "cell" of radio resources used by the node. Accordingly, the term "cell" may be used to represent service coverage of the node sometimes, radio resources at other times, or a range that signals using the radio resources can reach with valid strength at other times.

[0101] In CA, two or more CCs are aggregated. A UE may simultaneously receive or transmit on one or multiple CCs depending on its capabilities. CA is supported for both contiguous and non-contiguous CCs. When CA is configured, the UE only has one RRC connection with the network. At RRC connection establishment / re-establishment / handover, one serving cell provides the NAS mobility information, and at RRC connection re-establishment / handover, one serving cell provides the security input. This cell is referred to as the primary cell (PCell). The PCell is a cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. Depending on UE capabilities, secondary cells (SCells) can be configured to form together with the PCell a set of serving cells. An SCell is a cell providing additional radio resources on top of special cell (SpCell). The configured set of serving cells for a UE therefore always consists of one PCell and one or more SCells. For dual connectivity (DC) operation, the term SpCell refers to the PCell of the master cell group (MCG) or the primary SCell (PSCell) of the secondary cell group (SCG). An SpCell supports PUCCH transmission and contention-based random access, and is always activated. The MCG is a group of serving cells associated with a master node, comprised of the SpCell (PCell) and optionally one or more SCells. The SCG is the subset of serving cells associated with a secondary node, comprised of the PSCell and zero or more SCells, for a UE configured with DC. For a UE in RRC_CONNECTED not configured with CA / DC, there is only one serving cell comprised of the PCell. For a UE in RRC_CONNECTED configured with CA / DC, the term "serving cells" is used to denote the set of cells comprised of the SpCell(s) and all SCells. In DC, two MAC entities are configured in a UE: one for the MCG and one for the SCG.

[0102] FIG. 7 shows a data flow example in the 3GPP NR system to which implementations of the present disclosure is applied.

[0103] Referring to FIG. 7, "RB" denotes a radio bearer, and "H" denotes a header. Radio bearers are categorized into two groups: DRBs for user plane data and SRBs for control plane data. The MAC PDU is transmitted / received using radio resources through the PHY layer to / from an external device. The MAC PDU arrives to the PHY layer in the form of a transport block.

[0104] In the PHY layer, the uplink transport channels UL-SCH and random access channel (RACH) are mapped to their physical channels physical uplink shared channel (PUSCH) and physical random access channel (PRACH), respectively, and the downlink transport channels DL-SCH, BCH and PCH are mapped to physical downlink shared channel (PDSCH), physical broadcast channel (PBCH) and PDSCH, respectively. In the PHY layer, uplink control information (UCI) is mapped to physical uplink control channel (PUCCH), and downlink control information (DCI) is mapped to physical downlink control channel (PDCCH). A MAC PDU related to UL-SCH is transmitted by a UE via a PUSCH based on an UL grant, and a MAC PDU related to DL-SCH is transmitted by a BS via a PDSCH based on a DL assignment.

[0105] Hereinafter, a description will be given of mobility.

[0106] The mobility may comprise PCell change, PSCell change (or, secondary node (SN) change), and / or PSCell addition (or, SN addition).

[0107] In the present disclosure, the term "handover (HO)" may mean PCell change, or may be a broad concept that includes not only PCell change but also PSCell change / addition.

[0108] In the present disclosure, the terms "handover" and "mobility" can be used interchangeably.

[0109] In the present disclosure, the description regarding handover can also be applied to other mobility procedures (e.g., PSCell change / addition).

[0110] There may be at least two types of mobility: network-controlled mobility (or, legacy mobility) and UE-based mobility (or, conditional mobility).

[0111] The network-controlled mobility (or, legacy mobility) is a mobility where the network determines a target cell for mobility, and configures UE with the target cell. The network may transmit, to the UE, anRRCReconfigurationmessage comprising a configuration of the target cell. The UE may execute a mobility to the target cell and / or apply the configuration of the target cell, upon receiving the configuration of the target cell.

[0112] The UE-based mobility (or, conditional mobility) is a mobility where the network configures the UE with a plurality of candidate cells, and the UE determines a target cell which satisfies a mobility execution condition among the plurality of candidate cells. The conditional mobility may comprise at least one of a conditional PCell change / conditional handover (CHO) or a conditional PSCell mobility. The conditional PSCell mobility may comprise conditional PSCell addition / change (CPAC), including conditional PSCell addition (CPA) and / or conditional PSCell change (CPC). The network may transmit, to the UE, anRRCReconfigurationmessage comprisingConditionalReconfigurationinformation element (IE)(or, conditional mobility configuration), which comprises a list of candidate configurations for conditional mobility related to the plurality of candidate cells. A candidate configuration for conditional mobility may comprise an identifier of the candidate configuration, a mobility execution condition for the related candidate cell, and a configuration of the related candidate cell. The UE may evaluate the mobility execution conditions for the plurality of candidate cells, and when a mobility execution condition for a candidate cell is satisfied, the UE may consider the candidate cell as a target cell, and execute a mobility to the target cell and / or apply the configuration of the target cell.

[0113] According to various embodiments, the mobility execution condition may be satisfied / met when an entry condition (or, entering condition) for the mobility execution condition is satisfied / met for at least a time-to-trigger (TTT) for the mobility execution condition. The entry condition / entering condition may mean that the mobility execution condition is initially met. Once the entry condition is met, the mobility execution condition will be considered to be met if the entry condition is met for time duration TTT continuously.

[0114] In the present disclosure, subsequent mobility (e.g., subsequent CHO, subsequent CPAC (SCPAC)) is described. The subsequent mobility may refer to a mobility that is done by repeating a mobility execution / completion after each mobility execution / completion based on a corresponding candidate configuration without releasing other candidate configurations. That is, the subsequent mobility may refer to a mobility that is performed without reconfiguration and / or re-initialization on the mobility preparation from a network after a previous mobility. For example, when a UE has received a plurality of candidate configurations, after the UE performs a mobility based on a corresponding candidate configuration, the UE does not release other candidate configurations, and may perform a subsequent mobility based on a corresponding candidate configuration among the already received plurality of candidate configurations without reconfiguration and / or re-initialization on the mobility preparation from the network (or, without receiving new candidate configurations from the network). This results in a reduction of the signalling overhead and / or interrupting time for mobility.

[0115] FIG. 8 shows an example of a conditional mobility procedure according to an embodiment of the present disclosure.

[0116] In FIG. 8:

[0117] - the serving BS may be related to a PCell, which may be a source PCell for CHO;

[0118] - the serving BS may be an MN associated with an SN in DC, where the SN may be related to a source PSCell for CPC; and

[0119] - the target cell may be a target PCell for CHO, or a target PSCell for CPA / CPC.

[0120] Referring to FIG. 8, in step S801, UE may receive, from the serving BS, anRRCReconfigurationmessage comprising a conditional reconfiguration information element (IE) (i.e.,CondidtionalReconfiguration). The conditional reconfiguration IE may comprise a list of candidate configurations for conditional mobility related to candidate cells including the target cell. Each candidate configuration in the list may be related to the corresponding candidate cell, and comprises i) an identifier of the corresponding candidate configuration (i.e.,condReconfigId), ii) one or more execution conditions for the related candidate cell (i.e.,condExecutionCond), and / or iii) RRC reconfiguration for the related candidate cell (i.e.,condRRCReconfig) including a configuration of the related candidate cell. The one or more execution conditions may comprise CHO execution condition(s), CPA execution condition(s), and / or CPC execution condition(s).

[0121] The IEs in theConditionalReconfigurationare shown in table 5:

[0122] ConditionalReconfiguration-r16 ::= SEQUENCE {attemptCondReconfig-r16 ENUMERATED {true} OPTIONAL, -- Cond CHOcondReconfigToRemoveList-r16 CondReconfigToRemoveList-r16 OPTIONAL, -- Need NcondReconfigToAddModList-r16 CondReconfigToAddModList-r16 OPTIONAL, -- Need N...,[[scpac-ReferenceConfiguration-r18 SetupRelease {ReferenceConfiguration-r18} OPTIONAL, -- Need MservingSecurityCellSetId-r18 SecurityCellSetId-r18 OPTIONAL, -- Need Msk-CounterConfiguration-r18 SK-CounterConfiguration-r18 OPTIONAL -- Need M]]}CondReconfigToRemoveList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigId-r16SK-CounterConfiguration-r18 ::= SEQUENCE {sk-CounterConfigToReleaseList-r18 SEQUENCE (SIZE (1..maxSecurityCellSet-r18)) OF SecurityCellSetId-r18 OPTIONAL, -- Need Nsk-CounterConfigToAddModList-r18 SEQUENCE (SIZE (1..maxSecurityCellSet-r18)) OF SK-CounterConfig-r18 OPTIONAL -- Need N}SK-CounterConfig-r18 ::= SEQUENCE {securityCellSetId-r18 SecurityCellSetId-r18,sk-CounterList-r18 SEQUENCE (SIZE (1..maxSK-Counter-r18)) OF SK-Counter}SecurityCellSetId-r18 ::= INTEGER (1.. maxSecurityCellSet-r18)

[0123] In table 5:-attemptCondReconfig: if present, the UE shall perform conditional reconfiguration if selected cell is a target candidate cell and it is the first cell selection after failure;

[0124] -condReconfigToAddModList: list of the configuration of candidate SpCells to be added or modified for CHO, CPA or CPC;

[0125] -condReconfigToRemoveList: list of the configuration of candidate SpCells to be removed;

[0126] -scpac-ReferenceConfiguration: includes the reference configuration for the candidate supporting subsequent CPAC;

[0127] -servingSecurityCellSetId: this field identifies the security cell set for serving PSCell. The network does not provide this field for the conditional reconfiguration(s) generated by the SN; and

[0128] -sk-counterConfiguration: includes a list ofsk-Counterfrom which the UE should selectthe sk-counterused to derive S-KgNB for inter-SN subsequent CPAC. The network does not provide this field for the conditional reconfiguration(s) generated by the SN.

[0129] The IEs in thecondReconfigToAddModListare shown in table 6:

[0130] CondReconfigToAddModList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigToAddMod-r16CondReconfigToAddMod-r16 ::= SEQUENCE {condReconfigId-r16 CondReconfigId-r16,condExecutionCond-r16 SEQUENCE (SIZE (1..2)) OF MeasId OPTIONAL, -- Need McondRRCReconfig-r16 OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, -- Cond condReconfigAdd...,[[condExecutionCondSCG-r17 OCTET STRING (CONTAINING CondReconfigExecCondSCG-r17) OPTIONAL -- Need M]],[[condExecutionCondPSCell-r18 SEQUENCE (SIZE (1..2)) OF MeasId OPTIONAL, -- Cond condReconfigCHO-WithSCGsubsequentCondReconfig-r18 SubsequentCondReconfig-r18 OPTIONAL, -- Need MsecurityCellSetId-r18 SecurityCellSetId-r18 OPTIONAL, -- Need Mscpac-ConfigComplete-r18 ENUMERATED {true} OPTIONAL -- Cond CPAC]]}CondReconfigExecCondSCG-r17 ::= SEQUENCE (SIZE (1..2)) OF MeasIdSubsequentCondReconfig-r18 ::= SEQUENCE {condExecutionCondToReleaseList-r18 CondExecutionCondToReleaseList-r18 condExecutionCondToAddModList-r18 CondExecutionCondToAddModList-r18 ...OPTIONAL, -- Need NOPTIONAL, -- Need N}CondExecutionCondToAddModList-r18 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondExecutionCondToAddMod-r18CondExecutionCondToAddMod-r18 ::= SEQUENCE {subsequentCondReconfigId-r18 CondReconfigId-r16,subsequentCondExecutionCond-r18 SEQUENCE (SIZE (1..2)) OF MeasId OPTIONAL, -- Need MsubsequentCondExecutionCondSCG-r18 OCTET STRING (CONTAINING CondReconfigExecCondSCG-r17) OPTIONAL, -- Need M...}CondExecutionCondToReleaseList-r18 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigId-r16

[0131] In table 6:-condExecutionCond: the execution condition that needs to be fulfilled in order to trigger the execution of a conditional reconfiguration for CHO, CPA, intra-SN CPC without MN involvement, MN initiated inter-SN CPC, MN initiated subsequent CPAC, or SN initiated intra-SN subsequent CPAC without MN involvement. When configuring 2 triggering events (MeasIds) for a candidate cell, the network ensures that both refer to the samemeasObject. The network configures at most one fromcondEventD1,condEventD2orcondEventT1for the same candidate cell. For CPA, MN-initiated inter-SN CPC, and for MN initiated subsequent CPAC, the network only indicatesMeasId(s) associated withcondEventA4. For intra-SN CPC and for SN initiated intra-SN subsequent CPAC without MN involvement, the network only indicatesMeasId(s) associated withcondEventA3orcondEventA5;

[0132] -condExecutionCondPSCell: the execution condition that needs to be fulfilled for the associated PSCell in order to trigger the execution of a conditional reconfiguration for CHO with candidate SCG(s). TheMeasIdsrefer to themeasConfigassociated with the MCG. When configuring 2 triggering events (MeasIds) for a candidate cell, network ensures that both refer to the samemeasObject. The network only indicatesMeasId(s) associated withcondEventA4;

[0133] -condExecutionCondSCG: contains execution condition that needs to be fulfilled in order to trigger the execution of a conditional reconfiguration for SN initiated inter-SN CPC, SN initiated inter-SN subsequent CPAC, or SN initiated intra-SN subsequent CPAC with MN involvement. TheMeasIds refer to themeasConfigassociated with the SCG. When configuring 2 triggering events (MeasIds) for a candidate cell, network ensures that both refer to the samemeasObject. For eachcondReconfigId, the network always configures eithercondExecutionCondorcondExecutionCondSCG(not both). The network only indicatesMeasId(s) associated withcondEventA3orcondEventA5;

[0134] -condRRCReconfig: theRRCReconfigurationmessage to be applied when the condition(s) are fulfilled. TheRRCReconfigurationmessage contained incondRRCReconfigcannot contain the fieldconditionalReconfigurationor the fielddaps-Config;

[0135] -securityCellSetId: this field is used to determine whether the UE should perform security update when conditional reconfiguration containingsubsequentCondReconfigis executed. If the fieldservingSecurityCellSetIdis configured inconditionalReconfiguration, this field is configured for all the candidate configurations for subsequent CPAC;

[0136] -subsequentCondReconfig: contains the execution conditions that need to be fulfilled in order to trigger the execution of a subsequent CPAC. If the field is configured, the configuration of candidate PSCells for subsequent CPAC is supported. The subsequent execution condition is used for conditional reconfiguration evaluation for other candidate cells when theRRCReconfigurationmessage contained incondRRCReconfighas been applied;

[0137] -subsequentCondExecutionCond: the execution condition that needs to be fulfilled in order to trigger the subsequent execution of a conditional reconfiguration for SN initiated intra-SN subsequent CPAC without MN involvement. When configuring 2 triggering events (MeasIds) for a candidate cell, the network ensures that both refer to the samemeasObject. The network only indicatesMeasId(s) associated withcondEventA3orcondEventA5; and

[0138] -subsequentCondExecutionCondSCG: contains execution condition that needs to be fulfilled in order to trigger the subsequent execution of a conditional reconfiguration for SN initiated inter-SN subsequent CPAC, SN initiated intra-SN subsequent CPAC with MN involvement, or MN initiated subsequent CPAC. TheMeasIds refer to themeasConfigassociated with the SCG. When configuring 2 triggering events (MeasIds) for a candidate cell, network ensures that both refer to the samemeasObject. The network only indicatesMeasId(s) associated withcondEventA3orcondEventA5.

[0139] In step S803, the UE may start evaluating the one or more execution conditions for the candidate cells.

[0140] In step S805, if the target cell satisfies the corresponding execution condition(s), the UE may execute the conditional mobility towards the target cell and / or apply the RRC reconfiguration for the target cell including a configuration of the target cell. When / upon executing the conditional mobility and / or applying the RRC reconfiguration (e.g.,RRCReconfigurationincludingReconfigurationWithSync) for the target cell, the UE may start a timer (e.g., T304 timer). The timer value of the T304 timer (i.e., T304 timer value) for the target cell may be included in theReconfigurationWithSyncinRRCReconfigurationfor the target cell.

[0141] While the timer is running, the UE may perform DL synchronization and / or UL synchronization (e.g., random access) towards the target cell. The UE may skip the random access towards the target cell if timing advance (TA) information for the target cell is available.

[0142] In step S807, the UE, serving BS and / or BS related to the target cell may perform actions related to conditional mobility completion. For example, upon successful completion of the random access on the corresponding target cell, the UE may stop the timer (e.g., T304 timer).

[0143] Hereinafter, detailed procedure of the conditional reconfiguration / mobility is described.

[0144] The network configures the UE with one or more candidate target SpCells in the conditional reconfiguration. The UE evaluates the condition of each configured candidate target SpCell. The UE applies the conditional reconfiguration associated with one of the target SpCells which fulfils associated execution condition.

[0145] The network can also configure the UE with one or more candidate target PCells associated with one or more candidate target PSCells. The UE evaluates the conditions for the candidate target PCells and the associated candidate target PSCells in parallel and applies a target configuration that include PCell and PSCell for which the associated execution conditions are fulfilled. If there are multiple candidate PSCells associated with one candidate target PCell, the network provides multiple conditional configurations for the same candidate target PCell, i.e., each configuration contains one MCG configuration (for the same candidate target PCell) and one SCG configuration (for one of the multiple associated candidate PSCells). For this case, the network may also provide a complementary CHO only configuration, i.e., there is execution condition only for candidate PCell.

[0146] The network provides the configuration parameters for the target SpCell(s) in thecondRRCReconfig.

[0147] In NR-DC, the UE may receive two independentconditionalReconfiguration:

[0148] - aconditionalReconfigurationassociated with MCG, that is included in theRRCReconfigurationmessage received via SRB1; and

[0149] - aconditionalReconfiguration, associated with SCG, that is included in theRRCReconfigurationmessage received via SRB3, or, alternatively, included within aRRCReconfigurationmessage embedded in aRRCReconfigurationmessage received via SRB1.

[0150] In this case:

[0151] - the UE maintains two independentVarConditionalReconfig, one associated with eachconditionalReconfiguration;

[0152] - the UE independently performs all the conditional reconfiguration procedures for eachconditionalReconfigurationand the associatedVarConditionalReconfig, unless explicitly stated otherwise;

[0153] - the UE performs the measurement procedures for theVarConditionalReconfigassociated with the same cell group like themeasConfig.

[0154] In EN-DC, theVarConditionalReconfigis associated with the SCG.

[0155] In NE-DC and when no SCG is configured, theVarConditionalReconfigis associated with the MCG.

[0156] The UE performs the following actions based on a receivedConditionalReconfigurationIE:

[0157] 1> if theConditionalReconfigurationcontains thecondReconfigToRemoveList:

[0158] 2> perform conditional reconfiguration removal procedure;

[0159] 1> if theConditionalReconfigurationcontains thecondReconfigToAddModList:

[0160] 2> perform conditional reconfiguration addition / modification;

[0161] 1> if theConditionalReconfigurationcontains thescpac-ReferenceConfiguration:

[0162] 2> perform subsequent CPAC reference configuration addition / removal;

[0163] 1> if theConditionalReconfigurationcontains thesk-CounterConfiguration:

[0164] 2> performsk-CounterListaddition / modification / removal;

[0165] 1> if theConditionalReconfigurationcontains theservingSecurityCellSetId:

[0166] 2> if the currentVarServingSecurityCellSetIDincludesservingSecurityCellSetId:

[0167] 3> replace theservingSecurityCellSetIdvalue withinVarServingSecurityCellSetIDwith the receivedservingSecurityCellSetID;

[0168] 2> else:

[0169] 3> store the receivedservingSecurityCellSetIdwithinVarServingSecurityCellSetID.

[0170] I. Conditional reconfiguration removal

[0171] The UE shall:

[0172] 1> for eachcondReconfigIdvalue included in thecondReconfigToRemoveListthat is part of the current UE conditional reconfiguration inVarConditionalReconfig:

[0173] 2> remove the entry with the matchingcondReconfigIdfrom theVarConditionalReconfig;

[0174] The UE does not consider the message as erroneous if thecondReconfigToRemoveListincludes any condReconfigIdvalue that is not part of the current UE configuration.

[0175] II. Conditional reconfiguration addition / modification

[0176] For eachcondReconfigIdreceived in thecondReconfigToAddModListIE the UE shall:

[0177] 1> if an entry with the matchingcondReconfigIdexists in thecondReconfigToAddModListwithin theVarConditionalReconfig:

[0178] 2> if the entry incondReconfigToAddModListincludes ancondExecutionCond,condExecutionCondSCG, orcondExecutionCondPSCell;

[0179] 3> replacecondExecutionCond,condExecutionCondSCG, orcondExecutionCondPSCellwithin theVarConditionalReconfigwith the value received for thiscondReconfigId;

[0180] 2> if the entry incondReconfigToAddModListincludessubsequentCondReconfigcontainingcondExecutionCondToAddModList:

[0181] 3> for eachcondReconfigIdreceived incondExecutionCondToAddModList:

[0182] 4> if an entry with the matchingcondReconfigIdexists in thecondExecutionCondToAddModListwithinVarConditionalReconfig;

[0183] 5> replace the entry incondExecutionCondToAddModListwithinVarConditionalReconfigwith the value received for thiscondReconfigId;

[0184] 4> else:

[0185] 5> add a new entry incondExecutionCondToAddModListwithinVarConditionalReconfigwith the value received for thiscondReconfigId;

[0186] 2> if the entry incondReconfigToAddModListincludessubsequentCondReconfigcontainingcondExecutionCondToReleaseList:

[0187] 3> for eachcondReconfigIdreceived incondExecutionCondToReleaseListthat is part of current storedcondExecutionCondToAddModListwithinVarConditionalReconfig:

[0188] 4> remove the entry incondExecutionCondToAddModListwithinVarConditionalReconfigwith the value received for thiscondReconfigId;

[0189] The UE does not consider the message as erroneous if thecondExecutionCondToReleaseListincludes anycondReconfigIdvalue that is not part of the current UE configuration.

[0190] 2> if the entry incondReconfigToAddModListincludes asecurityCellSetId;

[0191] 3> replacesecurityCellSetIdwithin theVarConditionalReconfigwith the value received for thiscondReconfigId;

[0192] The UE should release the entry withinVarServingSecurityCellSetIDin case all the subsequent CPAC configurations are released.

[0193] 2> if the entry incondReconfigToAddModListincludes acondRRCReconfig;

[0194] 3> replacecondRRCReconfigwithin theVarConditionalReconfigwith the value received for thiscondReconfigId;

[0195] 1> else:

[0196] 2> add a new entry for thiscondReconfigIdwithin theVarConditionalReconfig;

[0197] 1> perform conditional reconfiguration evaluation.

[0198] III. Conditional reconfiguration evaluation

[0199] The UE shall:

[0200] 1> for eachcondReconfigIdwithin theVarConditionalReconfig:

[0201] 2> if theRRCReconfigurationwithincondRRCReconfigincludes themasterCellGroupincluding thereconfigurationWithSync:

[0202] 3> if the associatedcondExecutionCondPSCellis configured:

[0203] 4> consider the cell which has a physical cell identity matching the value indicated in theServingCellConfigCommonincluded in thereconfigurationWithSyncwithin themasterCellGroupin the receivedcondRRCReconfigto be applicable cell; and

[0204] 4> consider the cell which has a physical cell identity matching the value indicated in theServingCellConfigCommonincluded in thereconfigurationWithSyncwithin thesecondaryCellGroupwithin thenr-SCGwithin the receivedcondRRCReconfigto be applicable cell;

[0205] 3> else:

[0206] 4> consider the cell which has a physical cell identity matching the value indicated in theServingCellConfigCommonincluded in thereconfigurationWithSyncwithin themasterCellGroupin the receivedcondRRCReconfigto be applicable cell;

[0207] 2> else if theRRCReconfigurationwithincondRRCReconfigincludes thesecondaryCellGroupincluding thereconfigurationWithSync:

[0208] 3> if the cell which has a physical cell identity matching the value indicated in theServingCellConfigCommonincluded in thereconfigurationWithSyncwithin thesecondaryCellGroupwithin the receivedcondRRCReconfigis not the PSCell:

[0209] 4> ifsubsequentCondReconfigis not included for thecondReconfigId; or

[0210] 4> ifsubsequentCondReconfigis not included for the PSCell; or

[0211] 4> ifsubsequentCondReconfigis included for thecondReconfigIdand there is asubsequentCondReconfigfor the PSCell with a matchingcondReconfigIdvalue incondExecutionCondToAddModList:

[0212] 5> consider the cell to be applicable cell;

[0213] 2> ifcondExecutionCondSCGis configured:

[0214] 3> in the remainder of the procedure, consider eachmeasIdindicated in thecondExecutionCondSCGas ameasIdin theVarMeasConfigassociated with the SCGmeasConfig;

[0215] 2> if thecondExecutionCondPSCellis configured:

[0216] 3> in the remainder of the procedure, consider eachmeasIdindicated in thecondExecutionCondPSCellas ameasIdin theVarMeasConfigassociated with the MCGmeasConfig;

[0217] 2> ifcondExecutionCondis configured:

[0218] 3> if it is configured via SRB3 or configured withinnr-SCGor withinnr-SecondaryCellGroupConfigvia SRB1:

[0219] 4> in the remainder of the procedure, consider eachmeasIdindicated in thecondExecutionCondas ameasIdin theVarMeasConfigassociated with the SCGmeasConfig;

[0220] 3> else:

[0221] 4> in the remainder of the procedure, consider eachmeasIdindicated in thecondExecutionCondas ameasIdin theVarMeasConfigassociated with the MCGmeasConfig;

[0222] 2> for eachmeasIdincluded in themeasIdListwithinVarMeasConfigindicated in thecondExecutionCond, condExecutionCondSCG,orcondExecutionCondPSCellof thecondReconfigId:

[0223] 3> ifcondExecutionCond,condExecutionCondSCG, andsubsequentCondReconfigare included for thecondReconfigId:

[0224] 4> ignore themeasId(s)in thecondExecutionCondof thecondReconfigId;

[0225] 3> if thecondTriggerConfigis not configured withnesEvent:

[0226] 4> if thecondEventIdis associated withcondEventT1, and if the entry condition applicable for this event associated with thecondReconfigId, i.e. the event corresponding with thecondEventId(s)of the correspondingcondTriggerConfigwithinVarConditionalReconfig, is fulfilled for the applicable cell; or

[0227] 4> if thecondEventIdis associated withcondEventD1orcondEventD2, and if the entry conditions applicable for this event associated with thecondReconfigId, i.e. the event corresponding with thecondEventId(s)of the correspondingcondTriggerConfigwithinVarConditionalReconfig, is fulfilled for the applicable cell during the correspondingtimeToTriggerdefined for this event within theVarConditionalReconfig; or

[0228] 4> if thecondEventIdis associated withcondEventA3,condEventA4orcondEventA5, and if the entry condition(s) applicable for this event associated with thecondReconfigId, i.e. the event corresponding with thecondEventId(s)of the correspondingcondTriggerConfigwithinVarConditionalReconfig, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the correspondingtimeToTriggerdefined for this event within theVarConditionalReconfig:

[0229] 5> consider the event associated to thatmeasIdto be fulfilled;

[0230] 4> if themeasIdfor this event associated with thecondReconfigIdhas been modified; or

[0231] 4> if thecondEventIdis associated withcondEventT1, and if the leaving condition applicable for this event associated with thecondReconfigId, i.e. the event corresponding with thecondEventId(s)of the correspondingcondTriggerConfigwithinVarConditionalReconfig, is fulfilled for the applicable cell; or

[0232] 4>if thecondEventIdis associated withcondEventD1orcondEventD2, and if the leaving condition(s) applicable for this event associated with thecondReconfigId, i.e. the event corresponding with thecondEventId(s)of the correspondingcondTriggerConfigwithinVarConditionalReconfig, is fulfilled for the applicable cell during the correspondingtimeToTriggerdefined for this event within theVarConditionalReconfig; or

[0233] 4> if thecondEventIdis associated withcondEventA3,condEventA4orcondEventA5, and if the leaving condition(s) applicable for this event associated with thecondReconfigId, i.e. the event corresponding with thecondEventId(s)of the correspondingcondTriggerConfigwithinVarConditionalReconfig, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the correspondingtimeToTriggerdefined for this event within theVarConditionalReconfig:

[0234] 5> consider the event associated to thatmeasIdto be not fulfilled;

[0235] 3> else:

[0236] 4> if NES mode indication is received from lower layers, indicating that the NES-specific CHO execution condition of the PCell is enabled; and

[0237] 4> if the entry condition(s) applicable for this event associated with thecondReconfigId, i.e. the event corresponding with thecondEventId(s)of the correspondingcondTriggerConfigwithinVarConditionalReconfig, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the correspondingtimeToTriggerdefined for this event within theVarConditionalReconfig:

[0238] 5> consider the event associated to thatmeasIdto be fulfilled;

[0239] 4> if themeasIdfor this event associated with thecondReconfigIdhas been modified; or

[0240] 4> if NES mode indication is received from lower layers, indicating that the NES-specific CHO execution condition of the PCell is disabled; or

[0241] 4> if the leaving condition(s) applicable for this event associated with thecondReconfigId, i.e. the event corresponding with thecondEventId(s)of the correspondingcondTriggerConfigwithinVarConditionalReconfig, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the correspondingtimeToTriggerdefined for this event within theVarConditionalReconfig:

[0242] 5> consider the event associated to thatmeasIdto be not fulfilled;

[0243] 2> ifcondExecutionCondPSCellis not configured:

[0244] 3> if event(s) associated to allmeasId(s) withincondTriggerConfigfor the applicable cell are fulfilled:

[0245] 4> consider the applicable cell, associated to thatcondReconfigId, as a triggered cell;

[0246] 4> initiate the conditional reconfiguration execution;

[0247] 2> else:

[0248] 3> if event(s) associated to allmeasId(s), as indicated in thecondExecutionCondandcondExecutionCondPSCell,withincondTriggerConfigfor a target candidate cell within the storedcondRRCReconfigare fulfilled:

[0249] 4> consider the target candidate PCell within the storedcondRRCReconfig, associated to thatcondReconfigId, as a triggered PCell;

[0250] 4> consider the target candidate PSCell within the storedcondRRCReconfig, associated to thatcondReconfigId, as a triggered PSCell;

[0251] 4> initiate the conditional reconfiguration execution;

[0252] 2> if one of the events associated to themeasIds withincondTriggerConfigfor the applicable cell within the storedcondRRCReconfigis not configured withnesEvent, and the other event associated to themeasIds withincondTriggerConfigfor the applicable cell within the storedcondRRCReconfigis configured withnesEvent, and at least one of them is fulfilled:

[0253] 3> consider the applicable cell within the storedcondRRCReconfig, associated to thatcondReconfigId, as a triggered cell;

[0254] 3> initiate the conditional reconfiguration execution.

[0255] Up to 2MeasIdcan be configured for eachcondReconfigId, ifcondExecutionCondPSCellis not configured.The conditional reconfiguration event of the 2MeasIdmay have the same or different event conditions, triggering quantity, time to trigger, and triggering threshold.

[0256] For CHO with candidate SCG(s), up to 2MeasIdcan be configured forcondExecutionCondandup to 2MeasIdcan be configured forcondExecutionCondPSCellfor eachcondReconfigId.

[0257] IV. Conditional reconfiguration execution

[0258] The UE shall:

[0259] 1> if more than one pair of triggered PCell and associated triggered PSCell exist:

[0260] 2> select one of the triggered PCell(s) and the associated triggered PSCell(s) as the selected cells for conditional reconfiguration execution;

[0261] 1> else if only one pair of triggered PCell and associated triggered PSCell exists:

[0262] 2> consider the triggered PCell and the associated triggered PSCell as the selected cells for conditional reconfiguration execution;

[0263] 1> else if more than one triggered cell exists:

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

[0265] 1> else:

[0266] 2> consider the triggered cell as the selected cell for conditional reconfiguration execution;

[0267] 1> for the selected cell(s) of conditional reconfiguration execution:

[0268] 2> if thesubsequentCondReconfigis included in the entry inVarConditionalReconfigcontaining theRRCReconfigurationmessage for the selected cell:

[0269] 3> perform the subsequent CPAC execution;

[0270] 2> else:

[0271] 3> apply the storedcondRRCReconfigof the selected cell and perform the actions upon receiving / applying theRRCReconfigurationmessage in thecondRRCReconfig(i.e., perform a mobility to the corresponding SpCell / target cell based on theRRCReconfigurationmessage in thecondRRCReconfig).

[0272] If multiple NR cells are triggered in conditional reconfiguration execution, it is up to UE implementation which one to select, e.g. the UE considers beams and beam quality to select one of the triggered cells for execution.

[0273] V. Subsequent CPAC reference configuration addition / removal

[0274] The UE shall:

[0275] 1> if thescpac-ReferenceConfigurationis set tosetup:

[0276] 2> ifscpac-ReferenceConfigurationexists within theVarConditionalReconfig:

[0277] 3> replace thescpac-ReferenceConfigurationwithin theVarConditionalReconfig;

[0278] 2> else:

[0279] 3> store thescpac-ReferenceConfigurationwithin theVarConditionalReconfig;

[0280] 1> else (ifscpac-ReferenceConfigurationis set torelease):

[0281] 2> remove thescpac-ReferenceConfigurationwithin theVarConditionalReconfig;

[0282] VI.sk-Counterconfiguration addition / modification / removal

[0283] The UE shall:

[0284] 1> for eachsecurityCellSetIdreceived in thesk-CounterConfigToAddModListIE:

[0285] 2> if an entry with the matchingsecurityCellSetIdexists in thesk-CounterConfigToAddModListwithin theVarConditionalReconfig:

[0286] 3> replace thesk-CounterListwithin theVarConditionalReconfigwith thesk-CounterListaccording to the receivedsecurityCellSetId;

[0287] 2> else:

[0288] 3> add a new entry for thissecurityCellSetIdwithin theVarConditionalReconfig;

[0289] 1> for eachsecurityCellSetIdvalue included in thesk-CounterConfigToRemoveListthat is part of the currentsk-CounterConfigToAddModListinVarConditionalReconfig:

[0290] 2> remove the entry with the matchingsecurityCellSetIdfrom thesk-CounterConfigToAddModList;

[0291] VII. Subsequent CPAC execution

[0292] Upon the conditional reconfiguration execution for subsequent CPAC, the UE shall:

[0293] 1> if the selected subsequent CPAC candidate configuration is stored in MCGVarConditionalReconfig:

[0294] 2> for each SRB / DRB in current UE configuration:

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

[0296] - release all fields related to the SRB / DRB configuration except forsrb-Identity,drb-Identity, andsecurityConfig;

[0297] 2> release / clear all current dedicated radio configuration except for the following:

[0298] - the MCG C-RNTI;

[0299] - the AS security configurations associated with the master key and the secondary key;

[0300] - thelogicalChannelIdentityandlogicalChannelIdentityExtof RLC bearers configured in RLC-BearerConfig and the associated RLC entities, their state variables, buffers, and timers;

[0301] - the bh-LogicalChannelIdentityof BH RLC channels configured inBH-RLC-ChannelConfigand the associated RLC entities, their state variables, buffers, and timers;

[0302] - the UE variablesVarConditionalReconfigandVarServingSecurityCellSetID;

[0303] - the logged measurement configuration.

[0304] 2> release / clear all current common radio configuration, except for theServingCellConfigCommonof the PCell;

[0305] 2> apply the default MAC Cell Group configuration for MCG MAC and SCG MAC;

[0306] 2> use the default values for timers T310, T311 and constants N310, N311, where T310, N310, and N311 are for both MCG and SCG, and T311 is only for the MCG;

[0307] 2> apply the default L1 parameter values as specified in corresponding physical layer specifications for the MCG and SCG;

[0308] 1> else:

[0309] 2> for each SRB / DRB in current UE configuration:

[0310] - keep the associated PDCP and SDAP entities, their state variables, buffers and timers;

[0311] - release all fields related to the SRB / DRB configuration except forsrb-Identity,drb-Identity, andsecurityConfig;

[0312] 2> release / clear all current dedicated radio configuration associated with the SCG except for the following:

[0313] - the AS security configurations associated with the secondary key;

[0314] - the UE variablesVarConditionalReconfig.

[0315] 2> release / clear all current common radio configuration associated with the SCG;

[0316] 2> apply the default MAC Cell Group configuration for the SCG MAC;

[0317] 2> use the default values for timer T310 and constants N310 and N311 for the SCG;

[0318] 2> apply the default L1 parameter values as specified in corresponding physical layer specifications for the SCG;

[0319] 1> if thesecurityCellSetIdis included in the entry inVarConditionalReconfigcontaining theRRCReconfigurationmessage:

[0320] 2> ifservingSecurityCellSetIdis not included withinVarServingSecurityCellSetID; or

[0321] 2> if the value of thesecurityCellSetIdis not equal to the value ofservingSecurityCellSetIdwithinVarServingSecurityCellSetID:

[0322] 3> consider the firstsk-Countervalue in thesk-CounterListassociated with thesecurityCellSetIdwithin theVarConditionalReconfigas the selectedsk-Countervalue, and perform security key update procedure;

[0323] 3> remove the selectedsk-Countervalue from thesk-CounterListassociated with thesecurityCellSetIdwithin theVarConditionalReconfig;

[0324] 3> if the currentVarServingSecurityCellSetIDincludesservingSecurityCellSetId:

[0325] 4> replace the value ofservingSecurityCellSetIdwithinVarServingSecurityCellSetIDwith the value ofsecurityCellSetIdassociated with the selected cell;

[0326] 3> else:

[0327] 4> store theservingSecurityCellSetIdwithinVarServingSecurityCellSetIDwith the value ofsecurityCellSetIdassociated with the selected cell;

[0328] 1> if the selected subsequent CPAC candidate configuration is stored in the SCGVarConditionalReconfig:

[0329] 2> for eachdrb-Identityvalue included in eachRadioBearerConfigin the selected subsequent CPAC candidate configuration that is part of the current UE configuration, the UE shall perform the following actions after the end of this procedure:

[0330] 3> if the bearer is an AM DRB:

[0331] 4> trigger the PDCP entity of the bearer to perform PDCP data recovery;

[0332] 3> re-establish the corresponding RLC entity;

[0333] 1> else:

[0334] 2> for eachdrb-Identityvalue included in eachRadioBearerConfigin the selected subsequent CPAC candidate configuration that is part of the current UE configuration, the UE shall perform the following actions after the end of this procedure:

[0335] 3> if thekeyToUsein theRadioBearerConfigis different from thekeyToUsein the current UE configuration; or

[0336] 3> if the bearer is associated with the secondary key (S-KgNB) as indicated bykeyToUsein the current UE configuration and a newsk-Countervalue has been selected due to the conditional reconfiguration execution for subsequent CPAC:

[0337] 4> if the PDCP entity of this DRB is not configured withcipheringDisabled:

[0338] 5> configure the PDCP entity with the ciphering algorithm and KUPenc key associated with the master key (KgNB) or the secondary key (S-KgNB), as indicated inkeyToUse, i.e., the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE;

[0339] 4> if the PDCP entity of this DRB is configured withintegrityProtection:

[0340] 5> configure the PDCP entity with the integrity protection algorithms according tosecurityConfigand apply the KUPint key associated with the master key (KgNB) or the secondary key (S-KgNB) as indicated inkeyToUse;

[0341] 4> ifdrb-ContinueROHCis included inpdcp-Config:

[0342] 5> indicate to lower layer thatdrb-ContinueROHCis configured;

[0343] 4> ifdrb-ContinueEHC-DLis included inpdcp-Config:

[0344] 5> indicate to lower layer thatdrb-ContinueEHC-DLis configured;

[0345] 4> ifdrb-ContinueEHC-ULis included inpdcp-Config:

[0346] 5> indicate to lower layer thatdrb-ContinueEHC-ULis configured;

[0347] 4> ifdrb-ContinueUDCis included inpdcp-Config:

[0348] 5> indicate to lower layer thatdrb-ContinueUDCis configured;

[0349] 4> re-establish the corresponding RLC entity;

[0350] 4> trigger the PDCP entity of the bearer to perform PDCP re-establishment;

[0351] 3> else:

[0352] 4> if there is an associated SCG RLC bearer in the selected subsequent CPAC candidate configuration that is part of the current UE configuration:

[0353] 5> re-establish the SCG RLC entity;

[0354] 4> if the RLC entity of the associated RLC bearer(s) is re-established; or

[0355] 4> if an associated RLC bearer is released in the selected subsequent CPAC candidate configuration:

[0356] 5> if the bearer is an AM DRB:

[0357] 6> trigger the PDCP entity of the bearer to perform PDCP data recovery;

[0358] 2> for eachsrb-Identityincluded inRadioBearerConfigthat is part of the current UE configuration and if the radio bearer is SRB3 or SRB5, the UE shall perform the following actions after the end of this procedure:

[0359] 3> if a newsk-Countervalue has been selected due to the conditional reconfiguration execution for subsequent CPAC:

[0360] 4> configure the PDCP entity to apply the integrity protection algorithm and KRRCint key associated with the secondary key (S-KgNB) as indicated inkeyToUse, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

[0361] 4> configure the PDCP entity to apply the ciphering algorithm and KRRCenc key associated with the secondary key (S-KgNB) as indicated inkeyToUse, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

[0362] 4> trigger the PDCP entity of SRB to perform PDCP re-establishment;

[0363] 3> else:

[0364] 4> trigger the PDCP entity of SRB to perform SDU discard;

[0365] 3> re-establish the corresponding RLC entity;

[0366] 1> ifscpac-ConfigCompleteis not included within theVarConditionalReconfigfor the selected cell:

[0367] 2> if the subsequent CPAC candidate cell configuration is stored in MCGVarConditionalReconfig:

[0368] 3> considerscpac-ReferenceConfigurationin MCGVarConditionalReconfigto be the current UE configuration;

[0369] 2> else:

[0370] 3> considerscpac-ReferenceConfigurationin SCGVarConditionalReconfigto be the current SCG configuration;

[0371] When the UE considers the reference configuration to be the current UE configuration, the UE should store fields and configurations that are part of the reference configuration but should not execute any actions or procedures triggered by the reception of anRRCReconfigurationmessage.

[0372] 1> apply the storedcondRRCReconfigof the selected cell(s) and perform the actions upon receiving / applying theRRCReconfigurationmessage in thecondRRCReconfig(i.e., perform a mobility to the corresponding SpCell / target cell based on theRRCReconfigurationmessage in thecondRRCReconfig);

[0373] 1> release the radio bearer(s) and the associated logical channel(s) that are part of the current UE configuration but not part of the subsequent CPAC candidate configuration for the selected cell, or the subsequent CPAC reference configuration (in case the subsequent CPAC candidate configuration does not includescpac-ConfigComplete).

[0374] Whenscpac-ConfigCompleteis not included for the selected cell, before a subsequent CPAC execution, a UE implementation may generate and store an RRC reconfiguration message by applying the received subsequent CPAC candidate configuration on top of the subsequent CPAC reference configuration, and the stored RRC reconfiguration message is applied for subsequent CPAC execution. The UE needs to ensure that the RRC reconfiguration applied at the time of subsequent CPAC execution is in accordance with the latest receivedscpac-ReferenceConfigurationandcondRRCReconfigfor the subsequent CPAC configuration.

[0375] Further, there may be another type of mobility called L1 / L2-triggered mobility (LTM)(or, cell switch). LTM is a procedure in which a gNB receives L1 or L3 measurement report(s) from a UE, and on their basis the gNB may change UE serving cell by a cell switch command signalled via a MAC CE. The cell switch command indicates an LTM candidate configuration that the gNB previously prepared and provided to the UE through RRC signalling. Then the UE switches to the target configuration according to the cell switch command. The LTM procedure can be used to reduce the mobility latency.

[0376] When configured by the network, it is possible to activate TCI states of one or multiple cells that are different from the current serving cell. For instance, the TCI states of the LTM candidate cells can be activated in advance before any of those cells become the serving cell. This allows the UE to be DL synchronized with those cells, thereby facilitating a faster cell switch to one of those cells when cell switch is triggered. All the activated TCI states except those received in the cell switch command are deactivated upon LTM cell switch execution.

[0377] When configured by the network, it is possible to initiate UL TA acquisition (called early TA) procedure of one or multiple cells that are different from the current serving cells. If the cell has the same NTA as the current serving cells or NTA=0, early TA acquisition procedure is not required. The network may request the UE to perform early TA acquisition of a candidate cell before a cell switch. The early TA acquisition procedure is triggered by PDCCH order or realized through UE-based TA measurement as configured by RRC. In the former case, the gNB / gNB-DU to which the candidate cell belongs calculates the TA value and sends it to the gNB / gNB-DU to which the serving cell belongs via gNB-CU. The serving cell sends the TA value in the LTM cell switch command MAC CE when triggering LTM cell switch. In the latter case, the UE performs TA measurement for the candidate cells after being configured by RRC but the exact time the UE performs TA measurement is up to UE implementation. The UE applies the TA value measured by itself and performs RACH-less LTM upon receiving the cell switch command, if it does not include any valid TA value. The network may also send a TA value in the LTM cell switch command MAC CE without early TA acquisition.

[0378] When two TAG IDs are configured for an LTM candidate cell, the gNB-DU to which the LTM candidate cell belongs assigns the same TAG ID pointer value for each TRP to be used by the UEs.

[0379] Depending on the availability of a valid TA value, the UE performs either a RACH-less LTM or RACH-based LTM cell switch. If the valid TA value is provided in the cell switch command, the UE applies the TA value as instructed by the network. In the case where UE-based TA measurement is configured, but no valid TA value is provided in the cell switch command, the UE applies the valid TA value by itself if available. The UE performs RACH-less LTM cell switch upon receiving the cell switch command whenever a valid TA value is available. If no valid TA value is available, the UE performs RACH-based LTM cell switch.

[0380] Regardless of whether the UE is configured for UE-based TA measurement for a certain candidate cell, it will still follow the PDCCH order, which includes performing a random access procedure towards one or more candidate cells.

[0381] This also applies to the candidate cells for which the UE is capable of deriving TA values by itself. Additionally, regardless of whether the UE has already performed a random access procedure towards the candidate cells, it will still follow the UE-based measurement configuration if configured by the network.

[0382] For RACH-less LTM, the UE accesses the target cell using either a configured grant or a dynamic grant. The configured grant is provided in the LTM candidate configuration, and the UE selects the configured grant occasion associated with the beam indicated in the cell switch command. Upon initiation of LTM cell switch to the target cell, the UE starts to monitor PDCCH on the target cell for dynamic scheduling. Before RACH-less LTM procedure completion, the UE shall not trigger random access procedure if it does not have a valid PUCCH resource for triggered SRs.

[0383] The following principles apply to LTM:

[0384] - Security keys are maintained upon an LTM cell switch;

[0385] - Subsequent LTM is supported.

[0386] LTM supports both intra-gNB-DU and inter-gNB-DU mobility within the same gNB-CU. LTM supports both intra-frequency and inter-frequency mobility, including mobility to inter-frequency cell that is not a current serving cell.

[0387] LTM is supported only for licensed spectrum. The following scenarios are supported:

[0388] - PCell change in non-CA scenario and non-DC scenario;

[0389] - PCell and SCell(s) change in CA scenario;

[0390] - Dual connectivity scenario: including PCell and MCG SCell(s) change and intra-SN PSCell and SCG SCell(s) change without MN involvement. LTM for simultaneous PCell and PSCell change is not supported.

[0391] While the UE has stored LTM candidate configurations the UE can also execute any L3 handover except for DAPS handover. In the RRC message which the UE applies for any L3 handover (except DAPS), LTM candidate configurations can be added / modified / released by the target cell.

[0392] Cell switch command is conveyed in a MAC CE, which contains the necessary information to perform the LTM cell switch.

[0393] The overall procedure for LTM is shown in FIG. 9 below. Subsequent LTM is done by repeating the early synchronization, LTM cell switch execution, and LTM cell switch completion steps without the need to release, reconfigure or add other LTM candidate configurations after each LTM cell switch completion.

[0394] FIG. 9 shows an example of a signalling procedure for LTM according to an embodiment of the present disclosure.

[0395] Referring to FIG. 9, in step S901, the UE may send aMeasurementReportmessage to the gNB. The gNB decides to configure LTM and initiates LTM preparation.

[0396] In step S903, the gNB may transmit anRRCReconfigurationmessage to the UE including the LTM candidate cell configurations of one or multiple candidate cells. TheRRCReconfigurationmessage comprise an LTM configuration / cell switch configuration (e.g.,LTM-Config) comprising a list of LTM candidate configurations (e.g.,ltm-CandidateToAddModList). That is, the network configures the UE with one or more LTM candidate configurations within theLTM-ConfigIE.

[0397] The IEs in the LTM configuration / cell switch configuration (e.g.,LTM-Config) are shown in table 7:

[0398] LTM-Config-r18 ::= SEQUENCE {ltm-ReferenceConfiguration-r18 SetupRelease {ReferenceConfiguration-r18} OPTIONAL, -- Need Mltm-CandidateToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofLTM-Configs-r18)) OF LTM-CandidateId-r18 OPTIONAL, -- Need Nltm-CandidateToAddModList-r18 SEQUENCE (SIZE (1..maxNrofLTM-Configs-r18)) OF LTM-Candidate-r18 OPTIONAL, -- Need Nltm-ServingCellNoResetID-r18 INTEGER (1..maxNrofLTM-Configs-plus1-r18) OPTIONAL, -- Need Nltm-CSI-ResourceConfigToAddModList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-ResourceConfigurations-r18)) OF LTM-CSI-ResourceConfig-r18OPTIONAL, -- Need Nltm-CSI-ResourceConfigToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-ResourceConfigurations-r18)) OF LTM-CSI-ResourceConfigId-r18OPTIONAL, -- Need NattemptLTM-Switch-r18 ENUMERATED {true} OPTIONAL, -- Cond LTM-MCGltm-ServingCellUE-MeasuredTA-ID-r18 INTEGER (1..maxNrofLTM-Configs-plus1-r18) OPTIONAL, -- Need N...}

[0399] In table 7:-ltm-ReferenceConfiguration: LTM reference configuration used to provide a configuration that is common, within the same cell group, to all configured non-complete LTM candidate configurations;

[0400] -ltm-CandidateToAddModList: a list of LTM candidate configurations (e.g.,LTM-Candidate(s)) related to candidate SpCells to be added or modified for LTM;

[0401] -ltm-CandidateToReleaseList: a list of LTM candidate configuration IDs (e.g.,LTM-CandidateId(s)) related to candidate SpCells to be removed;

[0402] -ltm-ServingCellNoResetID: serving cell ID based on which the UE determines whether a L2 reset is needed or not upon an LTM cell switch procedure; and

[0403] -ltm-ServingCellUE-MeasuredTA-ID: serving cell ID based on which the UE determines whether UE-based TA measurements are needed or not.

[0404] The LTM candidate configuration / candidate configuration / candidate cell configuration (e.g.,LTE-Candidate) may be related to a candidate (target) cell. The IEs in the LTM candidate configuration / candidate configuration / candidate cell configuration (e.g.,LTE-Candidate) are shown in table 8:

[0405] LTM-Candidate-r18 ::= SEQUENCE {ltm-CandidateId-r18 LTM-CandidateId-r18,ltm-CandidatePCI-r18 PhysCellId OPTIONAL, -- Need Mltm-SSB-Config-r18 LTM-SSB-Config-r18 OPTIONAL, -- Need Mltm-CandidateConfig-r18 OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, -- Need Mltm-ConfigComplete-r18 ENUMERATED {true} OPTIONAL, -- Need Rltm-EarlyUL-SyncConfig-r18 OCTET STRING (CONTAINING EarlyUL-SyncConfig-r18) OPTIONAL, -- Need Rltm-EarlyUL-SyncConfigSUL-r18 OCTET STRING (CONTAINING EarlyUL-SyncConfig-r18) OPTIONAL, -- Need Rltm-TCI-Info-r18 LTM-TCI-Info-r18 OPTIONAL, -- Need Mltm-NoResetID-r18 INTEGER (1..maxNrofLTM-Configs-plus1-r18) OPTIONAL, -- Need Mltm-UE-MeasuredTA-ID-r18 INTEGER (1..maxNrofLTM-Configs-plus1-r18) OPTIONAL, -- Need M...}LTM-SSB-Config-r18 ::= SEQUENCE {ssb-Frequency-r18 ARFCN-ValueNR,subcarrierSpacing-r18 SubcarrierSpacing,ssb-Periodicity-r18 ENUMERATED {ms5, ms10, ms20, ms40, ms80, ms160, spare2, spare1} OPTIONAL, ssb-PositionsInBurst-r18 CHOICE {shortBitmap BIT STRING (SIZE (4)),mediumBitmap BIT STRING (SIZE (8)),longBitmap BIT STRING (SIZE (64))} OPTIONAL, -- Need Rss-PBCH-BlockPower-r18 INTEGER (-60..50) OPTIONAL, -- Need R...-- Need S}

[0406] In table 8:-ltm-CandidateId: an ID used to identify an LTM candidate configuration;

[0407] -ltm-CandidateConfig: a configuration of the related candidate cell for LTM, comprisingRRCReconfigurationmessage to be applied when LTM / cell switch is executed;

[0408] -ltm-ConfigComplete: if included in theLTM-Candidate, the UE may consider that the relatedltm-CandidateConfigis a complete configuration of the related candidate cell for LTM;

[0409] -ltm-NoResetID: if this field is equal toltm-ServingCellNoResetID, UE may determine that L2 reset is needed upon an LTM cell switch procedure; or

[0410] -ltm-UE-MeasuredTA-ID: if this field is equal toltm-ServingCellNoResetID, UE may determine that the UE-based TA measurements are needed.

[0411] In NR-DC, the UE may receive two independentltm-Config:

[0412] - anltm-Configassociated with the MCG that is included within anRRCReconfigurationmessage received via SRB1; and

[0413] - anltm-Configassociated with the SCG that is included within anRRCReconfigurationmessage either received via SRB3, or, alternatively, embedded in anRRCReconfigurationmessage received via SRB1.

[0414] In case the UE receives two independentltm-Config:

[0415] - the UE maintains two independentltm-Config;

[0416] - the UE maintains two independentVarLTM-ServingCellNoResetID, one associated with eachltm-Config;

[0417] - the UE maintains two independentVarLTM-ServingCellUE-MeasuredTA-ID, one associated with eachltm-Config;

[0418] - the UE independently performs all the LTM configuration and / or execution procedures for eachltm-Configand the associatedVarLTM-ServingCellNoResetIDandVarLTM-ServingCellUE-MeasuredTA-IDunless explicitly stated otherwise.

[0419] The UE shall perform the following actions based on the receivedLTM-ConfigIE:

[0420] 1> if the receivedLTM-Configincludesltm-ServingCellNoResetID:

[0421] 2> if the currentVarLTM-ServingCellNoResetIDincludes anltm-ServingCellNoResetID:

[0422] 3> replace theltm-ServingCellNoResetIDvalue withinVarLTM-ServingCellNoResetIDwith the receivedltm-ServingCellNoResetID;

[0423] 2> else:

[0424] 3> store the receivedltm-ServingCellNoResetIDinVarLTM-ServingCellNoResetID;

[0425] 1> if the receivedLTM-Configincludesltm-ServingCellUE-MeasuredTA-ID:

[0426] 2> if the currentVarLTM-ServingCellUE-MeasuredTA-IDincludes anltm-ServingCellUE-MeasuredTA-ID:

[0427] 3> replace theltm-ServingCellUE-MeasuredTA-IDvalue withinVarLTM-ServingCellUE-MeasuredTA-IDwith the receivedltm-ServingCellUE-MeasuredTA-ID;

[0428] 2> else:

[0429] 3> store the receivedltm-ServingCellUE-MeasuredTA-IDinVarLTM-ServingCellUE-MeasuredTA-ID;

[0430] 1> if the receivedLTM-Configincludes theltm-CandidateToReleaseList:

[0431] 2> perform the LTM candidate configuration release;

[0432] 1> if the receivedLTM-Configincludes theltm-CandidateToAddModList:

[0433] 2> perform the LTM candidate configuration addition or modification;

[0434] 1> reconfigure the UE according to all other fields of the receivedLTM-ConfigIE.

[0435] To perform the LTM candidate configuration release, The UE shall:

[0436] 1> for eachltm-CandidateIdvalue included in theltm-CandidateToReleaseListthat is part of the current UE configuration:

[0437] 2> remove the correspondingLTM-Candidate.

[0438] To perform the LTM candidate configuration addition or modification, the UE shall:

[0439] 1> for eachltm-CandidateIdvalueincluded in theltm-CandidateToAddModList:

[0440] 2> if the current UE configuration contains anLTM-Candidatewith theltm-CandidateIdvalue:

[0441] 3> reconfigure the correspondingLTM-Candidatein accordance with the receivedLTM-Candidate;

[0442] 2> else:

[0443] 3> add the receivedLTM-Candidate;

[0444] 2> if theLTM-Candidatewith the receivedltm-CandidateIdvalue includesltm-UE-MeasuredTA-ID:

[0445] 3> if the value ofltm-UE-MeasuredTA-IDis equal to the value ofltm-ServingCellUE-MeasuredTA-IDwithinVarLTM-ServingCellUE-MeasuredTA-ID:

[0446] 4> inform lower layers that the UE is configured with UE-based TA measurements for thisLTM-Candidate;

[0447] 3> else:

[0448] 4> inform lower layers that the UE is not configured with UE-based TA measurements for thisLTM-Candidate;

[0449] 2> else:

[0450] 3> inform lower layers that the UE is not configured with UE-based TA measurements for thisLTM-Candidate.

[0451] In step S905, the UE may store the LTM configuration / cell switch configuration comprising the list of LTM candidate configurations, and transmit anRRCReconfigurationCompletemessage to the gNB.

[0452] In step S907, the UE may perform DL / UL synchronization with the LTM candidate cell(s) before receiving the cell switch command.

[0453] In some implementations, the UE may perform DL synchronization with the LTM candidate cell(s) before receiving the cell switch command. The UE may activate and deactivate TCI states of LTM candidate cell(s), as triggered by the gNB.

[0454] In some implementations, the UE may perform UL synchronization with LTM candidate cell(s) before receiving the cell switch command, by using UE-based timing advance (TA) measurement, if configured, and / or by transmitting a preamble towards the candidate cell, as triggered by the gNB. When UE-based TA measurement is configured, UE acquires the TA value(s) of the candidate cell(s) by measurement. UE performs early TA acquisition with the candidate cell(s) as requested by the network before receiving the cell switch command. This is done via CFRA triggered by a PDCCH order from the source cell, following which the UE sends preamble towards the indicated candidate cell. In order to minimize the data interruption of the source cell due to CFRA towards the candidate cell(s), the UE does not receive random access response from the network for the purpose of TA value acquisition and the TA value of the candidate cell is indicated in the cell switch command. The UE does not maintain the TA timer for the candidate cell and relies on network implementation to guarantee the TA validity.

[0455] In step S909, the UE may perform L1 measurements on the configured LTM candidate cell(s) and transmit L1 measurement reports to the gNB. L1 measurement should be performed as long as RRC reconfiguration (step S903) is applicable. The UE can also perform L3 measurement reporting to the gNB, including beam level measurement results on cell(s) which are configured as LTM candidate cell(s) according to the received network configuration.

[0456] In step S911, the gNB may decide to execute cell switch to a target cell and transmit an LTM cell switch command MAC CE triggering cell switch by including a target configuration ID which indicates the index of the candidate configuration of the target cell (e.g.,ltm-CandidateId), a beam indicated with a TCI state or beams indicated with DL and UL TCI states, and a timing advance command for the target cell, if available. The UE switches to the target cell and applies the candidate configuration (e.g.,ltm-CandidateConfig) indicated by the target configuration ID.

[0457] Upon the indication by lower layers that an LTM cell switch procedure is triggered (e.g., upon receiving the LTM cell switch command MAC CE), or upon performing LTM cell switch following cell selection performed while timer T311 was running, the UE shall:

[0458] 1> if the LTM cell switch is triggered on the MCG:

[0459] 2> release / clear all current dedicated and common radio configurations which have neither been received via SRB1 withinmrdc-SecondaryCellGroup, nor via SRB3 except for the following:

[0460] - the radio bearer configuration (configured viaRadioBearerConfig)

[0461] - thelogicalChannelIdentityandlogicalChannelIdentityExtof RLC bearers configured inRLC-BearerConfigand the associated RLC entities, their state variables, buffers, and timers, except for triggering the associated RLC entities to reset the variable RETX_COUNT its initial value;

[0462] - thebh-LogicalChannelIdentityof BH RLC channels configured inBH-RLC-ChannelConfigand the associated RLC entities, their state variables, buffers, and timers, except for triggering the associated RLC entities to reset the variable RETX_COUNT its initial value;

[0463] - the UE variablesVarLTM-ServingCellNoResetIDandVarLTM-ServingCellUE-MeasuredTA-ID;

[0464] - theltm-Config;

[0465] - the MCG C-RNTI;

[0466] - the AS security configurations associated with the master key;

[0467] - the logged measurement configuration;

[0468] 1> else, if the LTM cell switch is triggered on the SCG:

[0469] 2> release / clear all current dedicated and common radio configurations which have been received either via SRB1 withinmrdc-SecondaryCellGroup, or via SRB3 except for the following:

[0470] - the radio bearer configuration (configured viaRadioBearerConfigIE)

[0471] - thelogicalChannelIdentityandlogicalChannelIdentityExtof RLC bearers configured inRLC-BearerConfigand the associated RLC entities, their state variables, buffers, and timers, except for triggering the associated RLC entities to reset the variable RETX_COUNT its initial value;

[0472] - thebh-LogicalChannelIdentityof BH RLC channels configured inBH-RLC-ChannelConfigand the associated RLC entities, their state variables, buffers, and timers, except for triggering the associated RLC entities to reset the variable RETX_COUNT its initial value;

[0473] - the UE variablesVarLTM-ServingCellNoResetIDandVarLTM-ServingCellUE-MeasuredTA-ID;

[0474] - theltm-Config;

[0475] - the AS security configurations associated with the secondary key;

[0476] 1> for each SRB / DRB in the current UE configuration:

[0477] 2> if the LTM cell switch is triggered on the MCG and the SRB / DRB using the master key; or

[0478] 2> if the LTM cell switch is triggered on the SCG and the SRB / DRB using the secondary key:

[0479] 3> keep the associated PDCP and SDAP entities, their state variables, buffers and timers;

[0480] 3> release all fields related to the SRB / DRB configuration except forsrb-Identityanddrb-Identity;

[0481] For all radio bearers and RLC bearers included in the LTM candidate configuration to be applied at an LTM cell switch execution (i.e., as derived from the LTM reference configuration and the LTM candidate configuration), even if those radio bearers and RLC bearers were configured before the LTM cell switch execution, the network includes fields as specified for the initial setup of radio bearers and RLC bearers and sets the values previously stored by the UE for the fields that cannot be modified according to presence conditions or field descriptions.

[0482] 1> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in SIB1;

[0483] 1> use the default values for timers T310, T311 and constants N310, N311 associated with the cell group for which the LTM cell switch procedure is triggered, where T310, N310, and N311 are for both MCG and SCG, and T311 is only for the MCG;

[0484] 1> apply the default MAC Cell Group configuration for the cell group for which the LTM cell switch procedure is triggered;

[0485] 1> for eachsrb-Identityin the current UE configuration:

[0486] 2> apply the default SRB configuration for the corresponding SRB;

[0487] 1> if theLTM-CandidateIE inltm-Configindicated by lower layers or for the selected cell does not contain the fieldltm-NoResetIDand if the UE does not have any value stored ofltm-ServingCellNoResetIDwithinVarLTM-ServingCellNoResetID; or

[0488] 1> if the value of fieldltm-NoResetIDcontained within theLTM-CandidateIE inltm-Configindicated by lower layers or for the selected cell is not equal to the value ofltm-ServingCellNoResetIDwithinVarLTM-ServingCellNoResetID:

[0489] 2> for eachlogicalChannelIdentityandlogicalChannelIdentityExtthat is part of the current UE configuration for the cell group for which the LTM cell switch procedure is triggered:

[0490] 3> ifservedRadioBeareris set todrb-Identity:

[0491] 4> after the end of this procedure, re-establish the corresponding RLC entity, after applying the LTM configuration inltm-CandidateConfigwithin theLTM-CandidateIE inltm-Config;

[0492] 2> for eachbh-LogicalChannelIdentitythat is part of the current UE configuration for the cell group for which the LTM cell switch procedure is triggered:

[0493] 3> after the end of this procedure, re-establish the corresponding RLC entity, after applying the LTM configuration inltm-CandidateConfigwithin the LTM-Candidate IE inltm-Config;

[0494] 2> for eachdrb-Identityvalue that is part of the current UE configuration:

[0495] 3> if this DRB is an AM DRB:

[0496] 4> after the end of this procedure, trigger the PDCP entity of this DRB to perform data recovery, after applying the LTM configuration inltm-CandidateConfigwithinLTM-CandidateIE inltm-Config;

[0497] 2> if the value of fieldltm-NoResetIDcontained within theLTM-CandidateIE inltm-Configindicated by lower layers or for the selected cell is not equal to the value ofltm-ServingCellNoResetIDwithinVarLTM-ServingCellNoResetID:

[0498] 3> replace the value ofltm-ServingCellNoResetIDinVarLTM-ServingCellNoResetIDwith the value ofltm-NoResetIDin theLTM-Candidateinltm-Configindicated by lower layers or for the selected cell;

[0499] 1> if theLTM-CandidateIE inltm-Configindicated by lower layers or for the selected cell contains the fieldltm-UE-MeasuredTA-ID:

[0500] 2> if the value ofltm-UE-MeasuredTA-IDis not equal to the value ofltm-ServingCellUE-MeasuredTA-IDwithinVarLTM-ServingCellUE-MeasuredTA-ID:

[0501] 3> replace the value ofltm-ServingCellUE-MeasuredTA-IDinVarLTM-ServingCellUE-MeasuredTA-IDwith the value received withinltm-UE-MeasuredTA-ID;

[0502] 3> for eachLTM-CandidateIE inltm-Config:

[0503] 4> if the value ofltm-UE-MeasuredTA-IDwithinLTM-CandidateIE is equal to the value ofltm-ServingCellUE-MeasuredTA-IDwithinVarLTM-ServingCellUE-MeasuredTA-ID:

[0504] 5> inform lower layers that the UE is configured with UE-based TA measurements for theLTM-Candidate;

[0505] 4> else:

[0506] 5> inform lower layers that the UE is not configured with UE-based TA measurements for theLTM-Candidate;

[0507] The UE is not expected to perform UE-based TA measurements for an SpCell.

[0508] 1> ifltm-ConfigCompleteis not included within theLTM-CandidateIE inltm-Configindicated by lower layers or for the selected cell:

[0509] 2> considerltm-ReferenceConfigurationinltm-Config, associated with the cell group for which the LTM cell switch procedure is triggered, to be the current UE configuration for the fields and configurations to be released by the actions above in this procedure;

[0510] 2> ifmeasConfigis included withinltm-ReferenceConfigurationinltm-Config;

[0511] 3> perform the measurement configuration procedure by considering themeasConfigwithinltm-ReferenceConfigurationinltm-Configas the receivedmeasConfig:

[0512] When the UE considers the reference configuration to be the current UE configuration, the UE should store fields and configurations that are part of the reference configuration but should not execute any actions or procedures triggered by the reception of anRRCReconfigurationmessage, unless specified otherwise in this clause.

[0513] 1> if the LTM cell switch is triggered by an indication from lower layers:

[0514] 2> apply theRRCReconfigurationmessage inltm-CandidateConfigwithinLTM-CandidateIE inltm-Configidentified by the LTM candidate configuration identity received from lower layers;

[0515] 1> else (LTM cell switch triggered upon cell selection performed while timer T311 was running):

[0516] 2> apply theRRCReconfigurationmessage inltm-CandidateConfigwithinLTM-CandidateIE inltm-Configrelated to the LTM candidate configuration identity for the selected cell;

[0517] 1> release the radio bearer(s) and the logical channel(s) that were part of the UE configuration before of this LTM cell switch procedure but not part of the LTM candidate configuration either indicated by lower layers or for the selected cell, or the LTM reference configuration (in case the LTM candidate configuration does not includeltm-ConfigComplete).

[0518] Whenltm-ConfigCompleteis not included for an LTM candidate configuration, before an LTM cell switch is triggered a UE implementation may generate and store anRRCReconfigurationmessage by applying the received LTM candidate configuration on top of the LTM reference configuration, and the storedRRCReconfigurationmessage is applied when the LTM cell switch is triggered. It is up to the UE to ensure that the RRC reconfiguration applied at the time of LTM cell switch is in accordance with the latest LTM reference configuration and LTM candidate configuration.

[0519] In step S913, the UE may perform the random access procedure towards the target cell, if UE does not have valid TA of the target cell. If UE has valid TA of the target cell, the UE may skip the random access procedure towards the target cell (i.e., RACH-less LTM).

[0520] When performing the random access procedure / RACH procedure: i) the UE may perform a contention-free random access (CFRA) if CFRA resources / dedicated RACH configuration is available to the UE; and ii) the UE may perform a contention-based random access (CBRA) if CFRA resources / dedicated RACH configuration is not available to the UE.

[0521] For the CBRA, the UE may transmit a random access preamble in uplink, to a RAN node. The UE may transmit a message 1 (MSG1) comprising the random access preamble to the RAN node. The random access preamble may be associated with a random access - radio resource temporary identifier (RA-RNTI). The random access preamble may be selected based on the selected RACH resources, and transmitted through a time / frequency resources identified by the selected RACH resources.

[0522] For the CFRA, the UE may transmit a dedicated random access preamble in uplink, to a RAN node. The UE may transmit an MSG1 comprising the dedicated random access preamble to the RAN node. The dedicated random access preamble may be associated with a RA-RNTI. The dedicated random access preamble may be selected based on the CFRA resources / dedicated RACH configuration, and transmitted through a time / frequency resources identified by the CFRA resources / dedicated RACH configuration.

[0523] In step S915, the UE may complete the LTM cell switch procedure by sendingRRCReconfigurationCompletemessage to target cell. If the UE has performed a RA procedure in step S913, the UE considers that LTM cell switch execution is successfully completed when the random access procedure is successfully completed. For RACH-less LTM, the UE considers that LTM cell switch execution is successfully completed when the UE determines that the network has successfully received its first UL data.

[0524] To complete the LTM cell switch procedure, the UE shall:

[0525] 1> if theRRCReconfigurationmessage including theLTM-Candidate IErelated to the LTM candidate configuration identity as received by lower layers was received via SRB1 within thenr-SCGwithinmrdc-SecondaryCellGroup(UE in NR-DC):

[0526] 2> submit theRRCReconfigurationCompletemessage via the NR MCG embedded in NR RRC messageULInformationTransferMRDC;

[0527] 1> else ifRRCReconfigurationmessage including theLTM-Candidate IErelated to the LTM candidate configuration identity as received by lower layers was received via SRB3 (UE in NR-DC):

[0528] 2> submit theRRCReconfigurationCompletemessage via SRB3 to lower layers for transmission using the new configuration;

[0529] 1> else (RRCReconfigurationwas received via SRB1):

[0530] 2> submit theRRCReconfigurationCompletemessage to lower layers for transmission via SRB1 using the new configuration.

[0531] The steps S907 to S915 can be performed multiple times for subsequent LTM cell switch executions using the LTM candidate configuration(s) provided in step S903.

[0532] The procedure over the air interface described in FIG. 9 is applicable to both intra-gNB-DU LTM and inter-gNB-DU LTM.

[0533] Meanwhile, in case of conditional mobility such as CHO, CPA, or CPC, UE can perform mobility based on a pre-configuration when at least one L3 execution condition is satisfied. Additionally, for LTM, the UE can perform mobility based on another pre-configuration when at least one L1 execution condition is satisfied.

[0534] Currently, in 5G NR mobility, the conditional mobility and the LTM cell switching require different pre-configurations even though both mobility have the same candidate cell. This means that in the mobility procedure, the network must redundantly provide the UE with pre-configurations containing the same information when the same candidate cell information should be provided.

[0535] In addition, since the UE performs mobility based on any execution condition that is satisfied first among the L3 execution condition and the L1 execution condition, the UE or the network cannot prioritize an execution condition between the L3 execution condition and the L1 execution condition. For example, after providing the pre-configuration to the UE, if the network wants more reliable mobility to a specific candidate cell due to unstable L1 measurement results, the network must remove the candidate cell and / or the related L1 execution condition from the pre-configuration to ensure that mobility is based solely on the L3 execution condition. Conversely, after providing the pre-configuration to the UE, if the network decides to support latency-less mobility to a specific candidate cell without considering the L3 measurement results, the network must remove the candidate cell configuration and / or the related L3 execution condition from pre-configuration to ensure that mobility is based solely on the L1 execution condition.

[0536] In other words, depending on the situation, if the network needs to optimally adjust the execution conditions for the UE to perform mobility to the candidate cell, the network should perform inefficient signalling to re-configure the pre-configuration, including the mobility command for the candidate cell, to the UE.

[0537] Accordingly, the present disclosure provides various embodiments related to mobility based on multiple execution conditions.

[0538] FIG. 10 shows an example of a method performed by a UE for mobility based on multiple execution conditions according to an embodiment of the present disclosure.

[0539] Referring to FIG. 10, in step S1001, the UE may receive a conditional mobility configuration for a candidate cell comprising multiple execution conditions for the candidate cell, and a cell configuration for the candidate cell.

[0540] In step S1003, the UE may receive valid condition information for a validity of the multiple execution conditions.

[0541] In step S1005, the UE may determine one or more valid execution conditions for the candidate cell among the multiple execution conditions, based on the valid condition information.

[0542] In step S1007, the UE may evaluate the one or more valid execution conditions without evaluating one or more invalid execution conditions for the candidate cell other than the one or more valid execution conditions among the multiple execution conditions.

[0543] In step S1009, the UE may apply the cell configuration for the candidate cell based on the one or more valid execution conditions being fulfilled.

[0544] According to various embodiments, the valid condition information may be included in the conditional mobility configuration.

[0545] According to various embodiments, the valid condition information may be received separately from the conditional mobility configuration.

[0546] According to various embodiments, the UE may skip performing measurement related to the one or more invalid execution conditions.

[0547] According to various embodiments, the multiple execution conditions may comprise: one or more first execution conditions evaluated based on a raw measurement result for the candidate cell; and one or more second execution conditions evaluated based on a filtered measurement result for the candidate cell. The filtered measurement result is obtained based on applying a filtering to the raw measurement result.

[0548] According to various embodiments, the raw measurement result may comprise at least one of reference signal received power (RSRP), reference signal received quality (RSRQ), received signal strength indicator (RSSI), or signal to interference plus noise ratio (SINR).

[0549] According to various embodiments, the filtered measurement result may be obtained based on an equation Fn= (1-k)*Fn-1+ k*Mn, where: Fndenotes the filtered measurement result; k denotes a filter coefficient; Fn-1denotes a previous filtered measurement result; and Mndenotes the raw measurement result.

[0550] According to various embodiments, the one or more first execution conditions may comprise at least one of: a condition that the raw measurement result for the candidate cell is greater than that for a serving cell by at least an offset; a condition that the raw measurement result for the candidate cell is greater than a threshold; or a condition that the raw measurement result for the candidate cell is greater than a first threshold and a raw measurement result for the serving cell is less than a second threshold. The one or more second execution conditions may comprise at least one of: a condition that the filtered measurement result for the candidate cell is greater than that for the serving cell by at least an offset; a condition that the filtered measurement result for the candidate cell is greater than a threshold; or a condition that the filtered measurement result for the candidate cell is greater than a third threshold and a filtered measurement result for the serving cell is less than a fourth threshold.

[0551] According to various embodiments, the raw measurement result may comprise a layer 1 (L1) measurement result. The filtered measurement result may comprise a layer 3 (L3) measurement result. The filtering may comprise L3 filtering.

[0552] According to various embodiments, the valid condition information may indicate the one or more first execution conditions as the one or more valid execution conditions or indicates the one or more second execution conditions as the one or more valid execution conditions.

[0553] According to various embodiments, one or more execution conditions not indicated by the valid condition information as the one or more valid execution conditions may be considered as the one or more invalid execution conditions.

[0554] According to various embodiments, the UE may receive second valid condition information for updating a validity of the multiple execution conditions. The UE may update the one or more valid execution conditions for the candidate cell among the multiple execution conditions, based on the second valid condition information. The UE may evaluate the one or more updated valid execution conditions without evaluating one or more invalid execution conditions for the candidate cell other than the one or more updated valid execution conditions among the multiple execution conditions.

[0555] According to various embodiments, the second valid condition information may be received via at least one of a radio resource control (RRC) signalling, a media access control (MAC) control element (CE) signalling, or downlink control information (DCI).

[0556] FIG. 11 shows an example of a signal flow between UE and network node for mobility based on multiple execution conditions according to an embodiment of the present disclosure.

[0557] Referring to FIG. 11, in step S1101, the network node may transmit, to the UE, a conditional mobility configuration for a candidate cell comprising multiple execution conditions for the candidate cell, and a cell configuration for the candidate cell.

[0558] In step S1103, the network node may transmit, to the UE, valid condition information for a validity of the multiple execution conditions.

[0559] In step S1105, the UE may determine one or more valid execution conditions for the candidate cell among the multiple execution conditions, based on the valid condition information.

[0560] In step S1107, the UE may evaluate the one or more valid execution conditions without evaluating one or more invalid execution conditions for the candidate cell other than the one or more valid execution conditions among the multiple execution conditions.

[0561] In step S1109, the UE may apply the cell configuration for the candidate cell based on the one or more valid execution conditions being fulfilled.

[0562] Hereinafter, detailed descriptions of mobility based on multiple execution conditions will be provided.

[0563] According to implementations of the present disclosure, the UE may determine which execution condition to consider for each candidate cell based on the pre-configuration that includes the L1 execution condition and the L3 execution condition per candidate cell for performing mobility, provided by the network. To determine which execution condition to consider for each candidate cell, the UE may check if there are one or more indicators (e.g., valid condition information) for candidate cells from the network. If there is at least one indicator received for a candidate cell and the indicator indicates the L1 execution condition, the UE may consider the L1 execution condition as an applicable condition to evaluate but the UE considers the L3 execution condition as a not applicable condition to evaluate. Conversely, if there is at least one indicator received for the candidate cell and the indicator indicates the L3 execution condition, the UE may consider the L3 execution condition as an applicable condition to evaluate but the UE considers the L1 execution condition as a not applicable condition to evaluate.

[0564] For the pre-configuration, the UE may receive the below information before initiating the mobility:

[0565] - Candidate cell configuration (e.g.,RRCReconfigurationfor the corresponding candidate cell): cell configuration is dedicated to the corresponding candidate cell when performing the mobility;

[0566] - Reference configuration (e.g.,ReferenceConfiguration): if provided, cell configuration is used commonly for candidate cells when performing mobility. However, the network may indicate additional information (e.g.,scpac-ConfigComplete,ltm-ConfigComplete) that some candidate cell configurations don't need to apply the reference configuration (i.e., mobility for some candidate cell configurations requires only applying the candidate cell configuration without the reference configuration);

[0567] - Security key lists (e.g.,sk-CounterConfiguration): one or more lists for each node (or, for each cell group) are used for security updates when performing mobility (e.g., conditional mobility / cell switching). Each list may consist of one or more security keys for a node / cell group. For example, each security key may comprise at least one of a gNB key or an input parameter for security key derivation such as next chaining count (NCC) value and / orsk-counter(e.g., SCG counter) value. For discriminating the security key lists, each security key list may contain a group identity (e.g.,securityCellSetId);

[0568] - Current group identity for the source cell: to discriminate whether upcoming mobility (e.g., conditional mobility / cell switching) is for inter-node mobility or not. The UE may update this current group identity after each mobility (e.g., conditional mobility / cell switching) is successfully completed;

[0569] - L1 execution condition(s): the L1 execution condition(s) may be used to make a decision to initiate the mobility to the suitable candidate based on layer 1 (L1) measurement results. Each L1 execution condition may correspond to one of the candidate cells and if the L1 execution condition is met, the UE may consider the corresponding candidate cell as suitable to initiate mobility. Each L1 execution condition may be such as A3 / A4 / A5-like conditions based on L1 measurement results;

[0570] - L3 execution condition(s): the L3 Execution condition(s) may be used to make a decision to initiate mobility to the suitable candidate based on layer 3 (L3) measurement results. Each L3 execution condition may correspond to one of the candidate cells and if the L3 execution condition is met, the UE may consider the corresponding candidate cell as suitable to initiate mobility. Each L3 execution condition may be such as A3 / A4 / A5 conditions based on L3 measurement results;

[0571] - Indicator(s) (e.g., valid condition information): The indicator(s) may indicate which execution condition is applicable for the mobility between the L1 execution condition and the L3 execution condition per candidate cell. Each indicator may be configured per candidate cell. If the indicator is configured for a candidate cell, for the mobility towards the candidate cell, the execution condition should be evaluated based on this indicator. Otherwise, if the indicator is not configured for a candidate cell, for the mobility towards the candidate cell, all execution conditions received for the candidate cell should be evaluated. In some implementations, each indicator may also indicate that both execution conditions should be considered for a candidate cell. Then, the execution condition should be evaluated based on this indicator for the mobility towards the candidate cell, and the UE can initiate the mobility for the candidate cell if both execution conditions are met. The network may configure this indicator for the same type of execution conditions if one or more L3 execution conditions or one or more L1 execution conditions are provided. If the indicator is configured for the same type of execution conditions of a candidate cell, the indicated execution condition(s) should be considered as applicable among the same type of execution conditions.

[0572] For considering the execution conditions of each candidate cell based on the indicator, if the indicator indicates that one of the execution conditions is not applicable, the UE may regard the indicated execution condition as an invalid condition to initiate the mobility, and the UE may exclude the indicated execution condition for evaluation (e.g., the UE ignores and / or removes the indicated execution condition for the mobility). Otherwise, if the indicator indicates that another one of execution conditions is applicable, the UE may regard the indicated execution condition as valid condition to initiate the mobility, and the UE may include the indicated execution condition for evaluation (e.g., the UE uses the indicated execution condition for the mobility).

[0573] For the indicator, the network may update the indicator after providing the indicator with initial information (e.g., initial value). If the network decides to change the applicable execution condition, the network may update the indicator at any time via at least one of RRC dedicated signalling (e.g., RRC reconfiguration), layer 1 signalling (e.g., DCI), or layer 2 signalling (e.g., MAC CE). Upon reception of the update of the indicator, the UE may check again which execution condition should be newly considered to be applicable to evaluate.

[0574] When performing mobility, the UE may decide whether to perform RACH-less mobility based on DL / UL early synchronization results for a target cell. For the DL early synchronization, the UE may early activate a TCI state (or, beam) of the target cell via L1 / L2 signalling e.g., MAC CE before performing the mobility. For the UL early synchronization, the UE may perform a random access procedure towards the target cell before performing the mobility. Alternatively / additionally, for the UL early synchronization, the UE may perform TA measurement for the target cells after being configured by RRC. If the network configures the indicator indicating that the applicable execution condition is the L3 execution condition, the UE may not perform the DL / UL early synchronization for the candidate cell. That is, the UE may only perform the DL / UL early synchronization for candidate cells which are evaluated based on the L1 execution conditions. Then, the UE may also ignore the DL / UL early synchronization results for a target cell even though the UE has acquired the DL / UL early synchronization results if the indicator is updated from the L1 execution condition to the L3 execution condition. Alternatively / additionally, the UE may perform the DL / UL early synchronization of candidate cells regardless of the applicable execution conditions.

[0575] FIG. 12 shows an example of a signal flow for combined L1 and L3 mobility according to an embodiment of the present disclosure.

[0576] Referring to FIG. 12, in step S1201, the UE may receive a subsequent mobility configuration (e.g.,ConditionalReconfigurationcomprisingCondReconfigToAddModeList, where at least oneCondReconfigToAddModecomprisessubsequentCondReconfig) from the cell 0. The cell 0 may configure 3 cell configurations (e.g.,condRRCReconfigcontainingRRCReconfiguration) of candidate cells (i.e. cell 1, cell 2, and cell 3) for the subsequent mobility. In the subsequent mobility configuration, multiple execution conditions for each candidate cell and cell configurations for candidate cells (i.e. cell 1, cell 2, and cell 3) may be included. In addition, in the subsequent mobility configuration, multiple indicators (e.g., valid condition information) for candidate cells may be included. For multiple execution conditions, there may be L1 execution condition(s) and L3 execution condition(s) per candidate cell. For multiple indicators, each indicator may be configured for each candidate cell to indicate which execution condition should be considered for now between the L1 execution condition(s) and the L3 execution condition(s). For example, the indicators may be configured such as: cell 1 - L1 execution condition, cell 2 - L1 execution condition, cell 3 - L3 execution condition.

[0577] In step S1203, the UE may check whether the indicators are configured for candidate cells and the UE may determine which execution conditions should be used for evaluation. Based on the indicators, the UE may evaluate the L1 execution condition for the cell 1, the L1 execution condition for the cell 2, and the L3 execution condition for the cell 3. The UE may ignore the L3 execution condition for the cell 1, the L3 execution condition for the cell 2, and the L1 execution condition for the cell 3 and doesn't evaluate these ignored execution conditions for candidate cells. For candidate cells which are evaluated based on the L1 execution conditions, the UE may perform the DL / UL early synchronization for the RACH-less mobility.

[0578] In step S1205, the UE may receive an RRC reconfiguration message from the network. In the RRC reconfiguration message, the indicators may be updated. Upon reception of the RRC reconfiguration message, the indicators may be configured such as: cell 1 - L1 execution condition, cell 2 - L3 execution condition, cell 3 - L3 execution condition.

[0579] In step S1207, the UE may check again whether the indicators are configured for candidate cells and the UE may determine which execution conditions should be used for evaluation. Based on the indicators, the UE may evaluate the L1 execution condition for the cell 1, the L3 execution condition for the cell 2, and the L3 execution condition for the cell 3. The UE may ignore the L3 execution condition for the cell 1, the L1 execution condition for the cell 2, and the L1 execution condition for the cell 3 and doesn't evaluate these ignored execution conditions for candidate cells. For candidate cells which are evaluated based on the L1 execution conditions, the UE may perform the DL / UL early synchronization for the RACH-less mobility.

[0580] In step S1209, the UE may receive MAC CE information from the network. In the MAC CE information, the indicators may be updated. Upon reception of the MAC CE information, the indicators may be configured as: cell 1 - L1 execution condition, cell 2 - L1 execution condition, cell 3 - L1 execution condition.

[0581] In step S1211, the UE may check again whether the indicators are configured for candidate cells and the UE may determine which execution conditions should be used for evaluation. Based on the indicators, the UE may evaluate the L1 execution condition for the cell 1, the L1 execution condition for the cell 2, and the L1 execution condition for the cell 3. The UE may ignore the L3 execution condition for the cell 1, the L3 execution condition for the cell 2, and the L3 execution condition for the cell 3 and doesn't evaluate these ignored execution conditions for candidate cells. For candidate cells which are evaluated based on the L1 execution conditions, the UE may perform the DL / UL early synchronization for the RACH-less mobility.

[0582] In step S1213, the UE may receive DCI from the network. In the DCI, the indicators may be updated. Upon reception of the DCI, the Indicators may be configured as: cell 1 - L3 execution condition, cell 2 - L1 execution condition, cell 3 - L1 execution condition.

[0583] In step S1215, the UE may check again whether the indicators may be configured for candidate cells and the UE may determine which execution conditions should be used for evaluation. Based on the indicators, the UE may evaluate the L3 execution condition for the cell 1, the L1 execution condition for the cell 2, and the L1 execution condition for the cell 3. The UE may ignore the L1 execution condition for the cell 1, the L3 execution condition for the cell 2, and the L3 execution condition for the cell 3 and doesn't evaluate these ignored execution conditions for candidate cells. For candidate cells which are evaluated based on the L1 execution conditions, the UE may perform the DL / UL early synchronization for the RACH-less mobility.

[0584] In step S1217, the UE may initiate the subsequent mobility from the cell 0 to the cell 2 when the L1 execution condition of the cell 2 is met. After the UE check that the DL / UL early synchronization is available, the UE may perform RACH-less mobility towards the cell 2. The UE may complete the subsequent mobility successfully, and send mobility complete message (e.g. RRC reconfiguration complete).

[0585] According to various embodiments, the UE may receive conditional mobility configuration including one or more candidate cell configurations and corresponding execution condition information for each candidate cell from the network. The execution condition information may contain L1 event conditions and L3 event conditions for each candidate cell. The execution condition information may comprise an indication indicating which event condition is currently valid between the L1 event conditions and L3 event conditions for each candidate cell. The UE may evaluate all the valid conditions for each candidate cell after checking validity based on the indication from the execution condition information. The UE may ignore an invalid condition between the L1 event conditions and L3 event conditions per candidate cell and doesn’t evaluate the related candidate cell based on the invalid condition. The UE may initiate the conditional mobility for one of the candidate cells when the valid condition for the candidate cell is met.

[0586] Furthermore, the method in perspective of the communication device / UE described in the present disclosure (e.g., in FIG. 10) may be performed by the first wireless device 100 shown in FIG. 2 and / or the UE 100 shown in FIG. 3.

[0587] More specifically, the communication device / UE comprises at least one transceiver, at least processor, and at least one computer memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, perform operations.

[0588] The operations comprise: receiving a conditional mobility configuration for a candidate cell comprising multiple execution conditions for the candidate cell, and a cell configuration for the candidate cell; receiving valid condition information for a validity of the multiple execution conditions; determining one or more valid execution conditions for the candidate cell among the multiple execution conditions, based on the valid condition information; evaluating the one or more valid execution conditions without evaluating one or more invalid execution conditions for the candidate cell other than the one or more valid execution conditions among the multiple execution conditions; and applying the cell configuration for the candidate cell based on the one or more valid execution conditions being fulfilled.

[0589] Furthermore, the method in perspective of the communication device / UE described in the present disclosure (e.g., in FIG. 10) may be performed by a software code 105 stored in the memory 104 included in the first wireless device 100 shown in FIG. 2.

[0590] More specifically, at least one computer readable medium (CRM) stores instructions that, based on being executed by at least one processor, perform operations comprising: receiving a conditional mobility configuration for a candidate cell comprising multiple execution conditions for the candidate cell, and a cell configuration for the candidate cell; receiving valid condition information for a validity of the multiple execution conditions; determining one or more valid execution conditions for the candidate cell among the multiple execution conditions, based on the valid condition information; evaluating the one or more valid execution conditions without evaluating one or more invalid execution conditions for the candidate cell other than the one or more valid execution conditions among the multiple execution conditions; and applying the cell configuration for the candidate cell based on the one or more valid execution conditions being fulfilled.

[0591] Furthermore, the method in perspective of the communication device / UE described in the present disclosure (e.g., in FIG. 10) may be performed by control of the processor 102 included in the first wireless device 100 shown in FIG. 2 and / or by control of the processor 102 included in the UE 100 shown in FIG. 3.

[0592] More specifically, an apparatus configured to / adapted to operate in a wireless communication system (e.g., communication device / UE) comprises at least processor, and at least one computer memory operably connectable to the at least one processor. The at least one processor is configured to / adapted to perform operations comprising: receiving a conditional mobility configuration for a candidate cell comprising multiple execution conditions for the candidate cell, and a cell configuration for the candidate cell; receiving valid condition information for a validity of the multiple execution conditions; determining one or more valid execution conditions for the candidate cell among the multiple execution conditions, based on the valid condition information; evaluating the one or more valid execution conditions without evaluating one or more invalid execution conditions for the candidate cell other than the one or more valid execution conditions among the multiple execution conditions; and applying the cell configuration for the candidate cell based on the one or more valid execution conditions being fulfilled.

[0593] Furthermore, the method in perspective of a network node described in the present disclosure (e.g., in FIG. 11) may be performed by the second wireless device 200 shown in FIG. 2. The network node may be related to a serving cell.

[0594] More specifically, the network node comprises at least one transceiver, at least processor, and at least one computer memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, perform operations.

[0595] The operations comprise: transmitting, to a user equipment (UE), a conditional mobility configuration for a candidate cell comprising multiple execution conditions for the candidate cell, and a cell configuration for the candidate cell; and transmitting, to the UE, valid condition information for a validity of the multiple execution conditions, wherein the UE is configured to perform operations comprising: determining one or more valid execution conditions for the candidate cell among the multiple execution conditions, based on the valid condition information; evaluating the one or more valid execution conditions without evaluating one or more invalid execution conditions for the candidate cell other than the one or more valid execution conditions among the multiple execution conditions; and applying the cell configuration for the candidate cell based on the one or more valid execution conditions being fulfilled.

[0596] The present disclosure may have various advantageous effects.

[0597] For example, the network can provide a single pre-configuration including the L1 execution condition and the L3 execution condition and also indicate which execution condition should be applicable to initiate mobility. Therefore, the UE doesn't need to receive duplicated pre-configuration for the same candidate cell for the L3 execution based conditional mobility and the L1 execution condition based LTM cell switching. Also, the UE doesn't need to receive frequent pre-configuration updates from the network due to execution condition changes for the same candidate cell.

[0598] Advantageous effects which can be obtained through specific embodiments of the present disclosure are not limited to the advantageous effects listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art can understand and / or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that may be understood or derived from the technical features of the present disclosure.

[0599] Claims in the present disclosure can be combined in a various way. For instance, technical features in method claims of the present disclosure can be combined to be implemented or performed in an apparatus, and technical features in apparatus claims can be combined to be implemented or performed in a method. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in an apparatus. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in a method. Other implementations are within the scope of the following claims.

Claims

A method comprising:receiving a conditional mobility configuration for a candidate cell comprising multiple execution conditions for the candidate cell, and a cell configuration for the candidate cell;receiving valid condition information for a validity of the multiple execution conditions;determining one or more valid execution conditions for the candidate cell among the multiple execution conditions, based on the valid condition information;evaluating the one or more valid execution conditions without evaluating one or more invalid execution conditions for the candidate cell other than the one or more valid execution conditions among the multiple execution conditions; andapplying the cell configuration for the candidate cell based on the one or more valid execution conditions being fulfilled.The method of claim 1, wherein the valid condition information is included in the conditional mobility configuration.The method of claim 1, wherein the valid condition information is received separately from the conditional mobility configuration.The method of claim 1, further comprising skipping performing measurement related to the one or more invalid execution conditions.The method of claim 1, wherein the multiple execution conditions comprise:one or more first execution conditions evaluated based on a raw measurement result for the candidate cell; andone or more second execution conditions evaluated based on a filtered measurement result for the candidate cell,wherein the filtered measurement result is obtained based on applying a filtering to the raw measurement result.The method of claim 5, wherein the raw measurement result comprises at least one of reference signal received power (RSRP), reference signal received quality (RSRQ), received signal strength indicator (RSSI), or signal to interference plus noise ratio (SINR).The method of claim 5, wherein the filtered measurement result is obtained based on an equation Fn= (1-k)*Fn-1+ k*Mn, where:Fndenotes the filtered measurement result;k denotes a filter coefficient;Fn-1denotes a previous filtered measurement result; andMndenotes the raw measurement result.The method of claim 5, wherein the one or more first execution conditions comprise at least one of:a condition that the raw measurement result for the candidate cell is greater than that for a serving cell by at least an offset;a condition that the raw measurement result for the candidate cell is greater than a threshold; ora condition that the raw measurement result for the candidate cell is greater than a first threshold and a raw measurement result for the serving cell is less than a second threshold; andwherein the one or more second execution conditions comprise at least one of:a condition that the filtered measurement result for the candidate cell is greater than that for the serving cell by at least an offset;a condition that the filtered measurement result for the candidate cell is greater than a threshold; ora condition that the filtered measurement result for the candidate cell is greater than a third threshold and a filtered measurement result for the serving cell is less than a fourth threshold.The method of claim 5, wherein the raw measurement result comprises a layer 1 (L1) measurement result,wherein the filtered measurement result comprises a layer 3 (L3) measurement result, andwherein the filtering comprises L3 filtering.The method of claim 5, wherein the valid condition information indicates the one or more first execution conditions as the one or more valid execution conditions or indicates the one or more second execution conditions as the one or more valid execution conditions, andwherein one or more execution conditions not indicated by the valid condition information as the one or more valid execution conditions are considered as the one or more invalid execution conditions.The method of claim 1, further comprising:receiving second valid condition information for updating a validity of the multiple execution conditions;updating the one or more valid execution conditions for the candidate cell among the multiple execution conditions, based on the second valid condition information; andevaluating the one or more updated valid execution conditions without evaluating one or more invalid execution conditions for the candidate cell other than the one or more updated valid execution conditions among the multiple execution conditions.The method of claim 11, wherein the second valid condition information is received via at least one of a radio resource control (RRC) signalling, a media access control (MAC) control element (CE) signalling, or downlink control information (DCI).The method of claims 1, wherein the method is performed by a user equipment (UE) in communication with at least one of a mobile device, a network, or autonomous vehicles.A user equipment (UE) comprising:at least one transceiver;at least one processor; andat least one memory operatively coupled to the at least one processor and storing instructions that, based on being executed by the at least one processor, perform operations comprising:receiving a conditional mobility configuration for a candidate cell comprising multiple execution conditions for the candidate cell, and a cell configuration for the candidate cell;receiving valid condition information for a validity of the multiple execution conditions;determining one or more valid execution conditions for the candidate cell among the multiple execution conditions, based on the valid condition information;evaluating the one or more valid execution conditions without evaluating one or more invalid execution conditions for the candidate cell other than the one or more valid execution conditions among the multiple execution conditions; andapplying the cell configuration for the candidate cell based on the one or more valid execution conditions being fulfilled.An apparatus comprising:at least processor; andat least one memory operatively coupled to the at least one processor and storing instructions that, based on being executed by the at least one processor, perform operations comprising:receiving a conditional mobility configuration for a candidate cell comprising multiple execution conditions for the candidate cell, and a cell configuration for the candidate cell;receiving valid condition information for a validity of the multiple execution conditions;determining one or more valid execution conditions for the candidate cell among the multiple execution conditions, based on the valid condition information;evaluating the one or more valid execution conditions without evaluating one or more invalid execution conditions for the candidate cell other than the one or more valid execution conditions among the multiple execution conditions; andapplying the cell configuration for the candidate cell based on the one or more valid execution conditions being fulfilled.A non-transitory computer readable medium (CRM) having stored thereon a program code implementing instructions that, based on being executed by at least one processor, perform operations comprising:receiving a conditional mobility configuration for a candidate cell comprising multiple execution conditions for the candidate cell, and a cell configuration for the candidate cell;receiving valid condition information for a validity of the multiple execution conditions;determining one or more valid execution conditions for the candidate cell among the multiple execution conditions, based on the valid condition information;evaluating the one or more valid execution conditions without evaluating one or more invalid execution conditions for the candidate cell other than the one or more valid execution conditions among the multiple execution conditions; andapplying the cell configuration for the candidate cell based on the one or more valid execution conditions being fulfilled.A method comprising:transmitting, to a user equipment (UE), a conditional mobility configuration for a candidate cell comprising multiple execution conditions for the candidate cell, and a cell configuration for the candidate cell; andtransmitting, to the UE, valid condition information for a validity of the multiple execution conditions,wherein the UE is configured to perform operations comprising:determining one or more valid execution conditions for the candidate cell among the multiple execution conditions, based on the valid condition information;evaluating the one or more valid execution conditions without evaluating one or more invalid execution conditions for the candidate cell other than the one or more valid execution conditions among the multiple execution conditions; andapplying the cell configuration for the candidate cell based on the one or more valid execution conditions being fulfilled.A network node comprising:at least one transceiver;at least one processor; andat least one memory operatively coupled to the at least one processor and storing instructions that, based on being executed by the at least one processor, perform operations comprising:transmitting, to a user equipment (UE), a conditional mobility configuration for a candidate cell comprising multiple execution conditions for the candidate cell, and a cell configuration for the candidate cell; andtransmitting, to the UE, valid condition information for a validity of the multiple execution conditions,wherein the UE is configured to perform operations comprising:determining one or more valid execution conditions for the candidate cell among the multiple execution conditions, based on the valid condition information;evaluating the one or more valid execution conditions without evaluating one or more invalid execution conditions for the candidate cell other than the one or more valid execution conditions among the multiple execution conditions; andapplying the cell configuration for the candidate cell based on the one or more valid execution conditions being fulfilled.

Images