ID-based cell configuration for subsequent mobility

Abstract

Methods and apparatus are provided for identifier (ID)-based cell configuration for subsequent mobility. The wireless device receives a first reconfiguration from a network. The first reconfiguration includes i) a plurality of reference cell configurations, and ii) an identifier (ID) associated with each of the plurality of reference cell configurations. The wireless device receives a second reconfiguration from the network. The second reconfiguration includes at least one mobility command related to mobility for each target cell. Each of the at least one mobility command includes a single cell configuration for each target cell. Each of the at least one mobility command is linked to one of the IDs associated with each of the plurality of reference cell configurations. The wireless device applies a single cell configuration for the target cell to a corresponding one of the at least one reference configuration to which the ID is linked.

Description

Technical Field

[0001] The present disclosure relates to identifier (ID) based cell configuration for subsequent mobility. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a technology for implementing high-speed packet communications. Many solutions have been proposed for the LTE goal, including those aimed at reducing user and provider costs, improving service quality, and expanding and improving coverage and system capacity. 3GPP LTE requires reduced cost per bit, increased service availability, flexible use of frequency bands, simple structure, open interfaces, and appropriate power consumption of terminals as higher-level requirements.

[0003] The International Telecommunication Union (ITU) and 3GPP have begun work to develop requirements and specifications for New Radio (NR) systems. 3GPP must identify and develop the technical components needed to successfully standardize a new RAT that meets both urgent market needs in a timely manner and longer-term requirements set forth by the ITU Radiocommunication Sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process. In addition, even in the more distant future, NR should be able to use any spectrum band available for wireless communications up to at least 100 GHz.

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

[0005] In Rel-17 Conditional Secondary Cell (PSCell) Change (CPC) / Conditional PSCell Addition (CPA), a CPC / CPA configured user equipment (UE) must release the CPC / CPA configuration upon completion of random access towards the target PSCell. Therefore, the UE has no opportunity to perform subsequent CPC / CPA without previous CPC / CPA reconfiguration and reinitialization from the network. This will increase latency for cell changes and increase signaling overhead, especially in the case of frequent secondary cell group (SCG) changes when operating in frequency range-2 (FR2).

[0006] In Rel-18, 3GPP aims to support optimized mobility procedures for UEs without receiving additional reconfiguration and performing reinitialization using a given conditional mobility command. This means that the UE can maintain a given conditional mobility command regardless of the change of the serving cell and use the conditional mobility command whenever the condition is met. That is, multiple subsequent mobilities can be allowed based on a given conditional mobility command. Summary of the invention

[0007] Technical Solution

[0008] The present disclosure will provide methods and apparatus for providing and / or applying identifier (ID) based cell configuration for subsequent mobility.

[0009] In one aspect, a method performed by a wireless device adapted to operate in a wireless communication system is provided. The method includes the following steps: receiving a first reconfiguration from a network. The first reconfiguration includes i) multiple reference cell configurations, and ii) an identifier (ID) associated with each of the multiple reference cell configurations. The method also includes the following steps: receiving a second reconfiguration from the network. The second reconfiguration includes at least one mobility command associated with mobility for each target cell. Each of the at least one mobility command includes a single cell configuration for each target cell. Each of the at least one mobility command is linked to one of the IDs associated with each of the multiple reference cell configurations. The method also includes the following steps: applying the single cell configuration for the target cell to the corresponding reference configuration to which the ID is linked in the at least one reference configuration.

[0010] In another aspect, a device for implementing the above method is provided.

[0011] Beneficial Effects

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

[0013] For example, the network may prevent signaling overhead in subsequent mobility scenarios by providing mobility commands to the UE based on linking to pre-configured IDs for candidate cells.

[0014] For example, since there is no need to further configure the reference cell to update the old reference cell configuration whenever mobility is performed, that is, since the reference cell can be configured by an ID, signaling overhead can be reduced.

[0015] For example, since the reference cell can be managed based on the ID even if the source cell continuously changes, configuration mismatch can be avoided when the UE applies incremental configuration in subsequent mobility scenarios.

[0016] The beneficial effects that can be obtained by the specific embodiments of the present disclosure are not limited to the beneficial effects listed above. For example, there are various technical effects that a person of ordinary skill in the relevant field can understand and / or derive from the present disclosure. Therefore, the specific effects of the present disclosure are not limited to those effects explicitly described herein, but can include various effects that can be understood or derived from the technical features of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 An example of a communication system to which an implementation of the present disclosure is applied is shown.

[0018] Figure 2 An example of a wireless device to which an implementation of the present disclosure is applied is shown.

[0019] Figure 3 An example of a UE to which an implementation of the present disclosure is applied is shown.

[0020] Figure 4 and Figure 5 An example of a protocol stack in a 3GPP-based wireless communication system to which an implementation of the present disclosure is applied is shown.

[0021] Figure 6 The frame structure in a 3GPP-based wireless communication system to which the implementation of the present disclosure is applied is shown.

[0022] Figure 7 An example of data flow in a 3GPP NR system to which an implementation of the present disclosure is applied is shown.

[0023] Figure 8 An example of a method performed by a wireless device to which an implementation of the present disclosure is applied is shown.

[0024] Fig. 9 An example of a method executed by a base station to which an implementation of the present disclosure is applied is shown.

[0025] Fig.10 An example of preconfiguration to which Example 1 of the present disclosure is applied is shown.

[0026] Fig.11 An example of conditional reconfiguration to which Example 1 of the present disclosure is applied is shown.

[0027] Fig.12 An example of preconfiguration to which Example 2 of the present disclosure is applied is shown.

[0028] Fig.13 An example of conditional reconfiguration to which Example 2 of the present disclosure is applied is shown.

[0029] Fig.14 An example of preconfiguration to which Example 3 of the present disclosure is applied is shown.

[0030] Fig.15 An example of conditional reconfiguration to which Example 3 of the present disclosure is applied is shown. DETAILED DESCRIPTION

[0031] The following techniques, devices and systems can be applied to various wireless multiple access systems. Examples of these multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multi-carrier frequency division multiple access (MC-FDMA) systems. CDMA can be implemented by radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented by radio technologies such as Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data Rate for GSM Evolution (EDGE). OFDMA can be implemented by radio technologies 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 part of 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 adopts OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). The evolutions of 3GPP LTE include LTE Advanced (LTE-A), LTE-A Pro and / or 5G New Radio (NR).

[0032] For ease of description, the embodiments of the present disclosure are mainly described with respect 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 a 3GPP-based wireless communication system are applicable to other mobile communication systems.

[0033] For terms and techniques not specifically described in the terms and techniques adopted in the present disclosure, reference may be made to wireless communication standard documents issued prior to the present disclosure.

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

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

[0036] 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 being the same as "at least one of A and B".

[0037] 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".

[0038] In addition, the brackets 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, in the present disclosure, "control information" is not limited to "PDCCH", and "PDDCH" may be proposed as an example of "control information". In addition, even when it is shown as "control information (ie, PDCCH)", "PDCCH" may be proposed as an example of "control information".

[0039] The technical features described separately in one figure in the present disclosure can be implemented separately or simultaneously.

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

[0041] Hereinafter, the present disclosure will be described in more detail with reference to the accompanying drawings. Unless otherwise specified, 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.

[0042] Figure 1 An example of a communication system to which an embodiment of the present disclosure is applied is shown.

[0043] exist Figure 1 The 5G usage scenarios shown in the present disclosure are only exemplary, and the technical features of the present disclosure may be applied to Figure 1 Other 5G usage scenarios shown in .

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

[0045] Reference Figure 1 , the communication system 1 includes wireless devices 100a to 100f, a base station (BS) 200, and a network 300. Figure 1 A 5G network is illustrated as an example of a network of the communication system 1 , but embodiments of the present disclosure are not limited to the 5G system and may be applied to future communication systems other than the 5G system.

[0046] BS 200 and network 300 may be implemented as wireless devices, and a specific wireless device may operate as a BS / network node relative to other wireless devices.

[0047] The wireless devices 100a to 100f represent devices that perform communication using a radio access technology (RAT) (e.g., 5G NR or LTE) and may be referred to as communication / wireless / 5G devices. The wireless devices 100a to 100f may include, but are not limited to, a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a home appliance 100e, an Internet of Things (IoT) device 100f, and an artificial intelligence (AI) device / server 400. For example, a vehicle may include a vehicle with a wireless communication function, an autonomous vehicle, and a vehicle capable of performing communication between vehicles. A vehicle 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) installed in a vehicle, a television, a smart phone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, and the like. Handheld devices may include smart phones, smart tablets, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., notebooks). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0048] In the present disclosure, the wireless devices 100a to 100f may be referred to as user equipment (UE). For example, the UE may include a cellular phone, a smart phone, a laptop computer, a digital broadcast terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a plate-shaped personal computer (PC), a tablet PC, an ultrabook, a vehicle, a vehicle with an autonomous driving function, a connected car, a 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 / environmental device, a device related to 5G services, or a device related to the field of the fourth industrial revolution.

[0049] The wireless devices 100a to 100f may be connected to the network 300 via the BS 200. 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 super 5G network. Although the wireless devices 100a to 100f may communicate with each other via the BS 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., sidelink communication) with each other without passing through the BS 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). An IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0050] Wireless communication / connection 150a, 150b, and 150c may be established between wireless devices 100a to 100f and / or between wireless devices 100a to 100f and BS 200 and / or between BS 200. In this document, wireless communication / connection 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. Wireless devices 100a to 100f and BS 200 / wireless devices 100a to 100f may send / receive radio signals to each other through wireless communication / connection 150a, 150b, and 150c. For example, wireless communication / connection 150a, 150b, and 150c may send / receive signals through various physical channels. To this end, various configuration information configuration processes for sending / receiving radio signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and at least a portion of the resource allocation process may be performed based on various proposals of the present disclosure.

[0051] NR supports multiple parameter sets (and / or multiple subcarrier spacing (SCS)) to support various 5G services. For example, if the SCS is 15kHz, wide areas can be supported in traditional cellular bands, and if the SCS is 30kHz / 60kHz, dense cities, lower latency, and wider carrier bandwidths can be supported. If the SCS is 60kHz or higher, bandwidths greater than 24.25GHz can be supported to overcome phase noise.

[0052] The NR frequency band may be defined as two types of frequency ranges, namely, frequency range 1 (FR1) and frequency range 2 (FR2). The numerical values ​​of the frequency ranges may be changed. For example, the two types of frequency ranges (FR1 and FR2) may be as shown in Table 1 below. For ease of explanation, in the frequency range used in the NR system, FR1 may mean "a range below 6 GHz", FR2 may mean "a range above 6 GHz", and may be referred to as millimeter wave (mmW).

[0053] [Table 1]

[0054] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 450MHz–6000MHz 15, 30, 60kHz FR2 24250MHz–52600MHz 60, 120, 240kHz

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

[0056] [Table 2]

[0057] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 410MHz–7125MHz 15, 30, 60kHz FR2 24250MHz–52600MHz 60, 120, 240kHz

[0058] Here, the radio communication technology implemented in the wireless device 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 a low-power wide area network (LPWAN) technology, which may be implemented in specifications such as LTE Cat NB1 and / or LTE Cat NB2, and may not be limited to the names mentioned above. Additionally and / or alternatively, the radio communication technology implemented in the wireless device in the present disclosure may be based on LTE-M technology for communication. For example, LTE-M technology may be an example of LPWAN technology and is referred to as various names such as enhanced MTC (eMTC). For example, LTE-M technology may be implemented in at least one of various specifications such as 1) LTE CaT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE machine type communication and / or 7) LTE M, and may not be limited to the above names. Additionally and / or alternatively, the radio communication technology implemented in the wireless device in the present disclosure may include at least one of ZigBee, Bluetooth, and / or LPWAN considering low-power communication, and may not be limited to the names mentioned above. For example, ZigBee technology may generate a personal area network (PAN) associated with small / low-power digital communication based on various specifications such as IEEE 802.15.4, and may be referred to as various names.

[0059] Figure 2 An example of a wireless device to which an embodiment of the present disclosure is applied is shown.

[0060] exist Figure 2 In the embodiment, the first wireless device 100 and / or the second wireless device 200 may be implemented in various forms according to the usage / service. For example, {the first wireless device 100 and the second wireless device 200} may correspond to Figure 1At least one of {wireless devices 100a to 100f and BS200}, {wireless devices 100a to 100f and wireless devices 100a to 100f} and / or {BS200 and BS200}. The first wireless device 100 and / or the second wireless device 200 may be configured by various elements, devices / components and / or modules.

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

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

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

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

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

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

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

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

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

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

[0071] In the following, the hardware elements of the wireless devices 100 and 200 will be described in more detail. One or more protocol layers may be implemented by, but not limited to, one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as physical (PHY), layer, medium access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, radio resource control (RRC) layer, and service data adaptation protocol (SDAP) layer). One or more processors 102 and 202 may generate one or more protocol data units (PDUs), one or more service data units (SDUs), messages, control information, data, or information according to the descriptions, functions, processes, suggestions, methods, and / or operation flow charts disclosed in the present disclosure. The one or more processors 102 and 202 may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the description, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in the present disclosure and provide the generated signal to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive a signal (e.g., a baseband signal) from the one or more transceivers 106 and 206 and obtain the PDU, SDU, message, control information, data, or information according to the description, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in the present disclosure.

[0072] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in one or more processors 102 and 202. For example, one or more processors 102 and 202 may be configured by a collection of a communication control processor, an application processor (AP), an electronic control unit (ECU), a central processing unit (CPU), a graphics processing unit (GPU), and a memory control processor. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, codes, instructions, and / or commands.

[0073] 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 and non-volatile memory, hard disk drive, register, cache memory, computer-readable storage medium and / or a combination thereof. The one or more memories 104 and 204 may be located inside and / or outside 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 connections.

[0074] One or more transceivers 106 and 206 may send user data, control information, and / or radio signals / channels mentioned in the description, function, process, suggestion, method, and / or operation flow chart disclosed in the present disclosure to one or more other devices. One or more transceivers 106 and 206 may receive user data, control information, and / or radio signals / channels mentioned in the description, function, process, suggestion, method, and / or operation flow chart disclosed in the present disclosure from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and send and receive radio signals. For example, one or more processors 102 and 202 may perform control so that one or more transceivers 106 and 206 may send user data, control information, or radio signals to one or more other devices. One or more processors 102 and 202 may perform control so that one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices.

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

[0076] The one or more transceivers 106 and 206 may convert received user data, control information, radio signals / channels, etc. from RF band signals to baseband signals so as to process the 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 baseband signals to 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 may up-convert OFDM baseband signals to OFDM signals through 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 an OFDM signal at a carrier frequency and down-convert the OFDM signal to an OFDM baseband signal through their (analog) oscillators and / or filters under the control of the one or more processors 102 and 202 .

[0077] Although in Figure 2 140, but the wireless devices 100 and 200 may further include additional components. The additional components 140 may be configured differently depending on the type 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., an audio I / O port, a video I / O port), a drive 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 wired or wireless connections.

[0078] In an embodiment of the present disclosure, a UE may operate as a transmitting device in UL and as a receiving device in DL. In an embodiment of the present disclosure, a BS may operate as a receiving device in UL and as a transmitting device in DL. In the following, for the convenience of description, it is mainly assumed that the first wireless device 100 is a UE and the second wireless device 200 is a BS. For example, a processor 102 connected to, installed on, or started in the first wireless device 100 may be suitable for executing a UE behavior according to an embodiment of the present disclosure or controlling a transceiver 106 to execute a UE behavior according to an embodiment of the present disclosure. A processor 202 connected to, installed on, or started in the second wireless device 200 may be suitable for executing a BS behavior according to an embodiment of the present disclosure or controlling a transceiver 206 to execute a BS behavior according to an embodiment of the present disclosure.

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

[0080] Figure 3 An example of a UE to which an embodiment of the present disclosure is applied is shown.

[0081] refer to Figure 3 , UE 100 may correspond to Figure 2 A first wireless device 100 is provided.

[0082] 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 identity module (SIM) card 145 , a speaker 146 , and a microphone 147 .

[0083] The processor 102 may be configured to implement the descriptions, functions, processes, suggestions, methods and / or operational flow charts disclosed in the present disclosure. The processor 102 may be configured to control one or more other components of the UE 100 to implement the descriptions, functions, processes, suggestions, methods and / or operational flow charts disclosed in the present disclosure. The layers of the radio interface protocol may be implemented in the processor 102. The processor 102 may include an ASIC, other chipsets, logic circuits and / or data processing devices. The processor 102 may be an application processor. The processor 102 may include at least one of a DSP, a CPU, a GPU, a modem (modulator and demodulator). Examples of the processor 102 may be found at MANUFACTURED BY SNAPDRAGON TM Series processors, Manufactured by EXYNOS TM Series processors, A series processors manufactured by Made by HELIO TM Series processors, ATOM manufactured TM series processors or corresponding next-generation processors.

[0084] The memory 104 is operably coupled to 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 devices. When the embodiment is implemented in software, the technology described herein can be implemented with modules (e.g., processes, functions, etc.) that execute the descriptions, functions, processes, suggestions, methods and / or operational flow charts 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 outside the processor 102, in which case the memory 104 can be communicatively coupled to the processor 102 via various means known in the art.

[0085] The transceiver 106 is operably coupled to the processor 102 and transmits and / or receives radio signals. The transceiver 106 includes a transmitter and a receiver. The transceiver 106 may include a baseband circuit for processing radio frequency signals. The transceiver 106 controls one or more antennas 108 to transmit and / or receive radio signals.

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

[0087] The display 143 outputs the result processed by the processor 102. The keyboard 144 receives input to be used by the processor 102. The keyboard 144 may be shown on the display 143.

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

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

[0090] Figure 4 and Figure 5 An example of a protocol stack in a 3GPP-based wireless communication system to which an implementation of the present disclosure is applied is shown.

[0091] Specifically, Figure 4An example of a radio interface user plane protocol stack between a UE and a BS is illustrated, and Figure 5 An example of a radio interface control plane protocol stack between a UE and a BS is illustrated. The control plane refers to a path through which control messages for managing calls made between a UE and a network are transmitted. The user plane refers to a path through which data generated in an application layer (e.g., voice data or Internet packet data) is transmitted. Figure 4 , the user plane protocol stack can be divided into layer 1 (ie, PHY layer) and layer 2. Figure 5 , the control plane protocol stack can be divided into layer 1 (ie, PHY layer), layer 2, layer 3 (eg, RRC layer), and non-access stratum (NAS) layer. Layer 1, layer 2, and layer 3 are called access stratum (AS).

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

[0093] In the 3GPP NR system, the main services and functions of the MAC sublayer include: mapping between logical channels and transport channels; multiplexing / demultiplexing MAC SDUs belonging to one or different logical channels to / from transport blocks (TBs) on transport channels for delivery to / from the physical layer; scheduling information reporting; error correction through hybrid automatic repeat request (HARQ) (one HARQ entity per cell in the case of carrier aggregation (CA); priority handling between UEs through dynamic scheduling; priority handling between logical channels of one UE through logical channel prioritization; padding. A single MAC entity can support multiple parameter sets, transmission timings, and cells. The mapping restrictions in the logical channel prioritization control which parameter set(s), cell, and transmission timing can be used by the logical channel.

[0094] MAC provides different kinds of data transmission services. In order to accommodate different kinds of data transmission services, multiple types of logical channels are defined, that is, each logical channel supports the transmission of a specific type of information. Each logical channel type is defined by what type of information is transmitted. Logical channels are divided into two groups: control channels and traffic channels. Control channels are used only for the transmission of control plane information, and traffic channels are used only for the transmission of user plane information. The broadcast control channel (BCCH) is a downlink logical channel for broadcasting system control information, the paging control channel (PCCH) is a downlink logical channel for transmitting paging information, system information change notifications, and indications of ongoing public warning services (PWS) broadcasts, the common control channel (CCCH) is a logical channel used to send control information between the UE and the network and is used by UEs that do not have an RRC connection with the network, and the dedicated control channel (DCCH) is a point-to-point bidirectional logical channel used by UEs with an RRC connection to send dedicated control information between the UE and the network. The dedicated traffic channel (DTCH) is a point-to-point logical channel dedicated to one UE for transmitting user information. DTCH can exist in both the uplink and downlink. In the downlink, there are the following connections between logical channels and transport channels: BCCH can be mapped to the broadcast channel (BCH); BCCH can be mapped to the downlink shared channel (DL-SCH); PCCH can be mapped to the paging channel (PCH); CCCH can be mapped to DL-SCH; DCCH can be mapped to DL-SCH; and DTCH can be mapped to DL-SCH. In the uplink, there are the following connections between logical channels and transport channels: CCCH can be mapped to the uplink shared channel (UL-SCH); DCCH can be mapped to UL-SCH; and DTCH can be mapped to UL-SCH.

[0095] The RLC sublayer supports three transmission modes: transparent mode (TM), unacknowledged mode (UM) and acknowledged mode (AM). The RLC configuration is per logical channel without dependency on parameter sets and / or transmission duration. In 3GPP NR systems, the main services and functions of the RLC sublayer depend on the transmission mode and include: delivery of upper layer PDUs; sequence numbering independent of sequence numbering 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 SDUs (AM and UM); duplicate detection (AM only); RLC SDU discard (AM and UM); RLC re-establishment; protocol error detection (AM).

[0096] In the 3GPP NR system, the main services and functions of the PDCP sublayer for the user plane include: sequence numbering; header compression and decompression using robust header compression (RoHC); transmission of user data; reordering and duplicate detection; in-sequence delivery; PDCP PDU routing (in the case of split bearers); retransmission of PDCP SDU; ciphering, deciphering and integrity protection; PDCP SDU discard; PDCP re-establishment and data recovery for RLC AM; PDCP status reporting for RLC AM; PDCP PDU duplication 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; transmission of control plane data; reordering and duplicate detection; in-sequence delivery; PDCP PDU duplication and duplicate discard indication to lower layers.

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

[0098] 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 the 5G core network (5GC) or the next generation radio access network (NG-RAN); establishment, maintenance and release of the RRC connection between the UE and the NG-RAN; security functions including key management; establishment, configuration, maintenance and release of signaling 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 reporting; detection and recovery of radio link failures; NAS message transmission from UE to NAS / from NAS to UE.

[0099] Figure 6 The frame structure in a 3GPP-based wireless communication system to which the implementation of the present disclosure is applied is shown.

[0100] Figure 6The frame structure shown in is merely exemplary, and the number of subframes, the number of time slots, and / or the number of symbols in a frame may vary. In a 3GPP-based wireless communication system, OFDM parameter sets (e.g., SCS, transmission time interval (TTI) duration) may be configured differently between multiple cells aggregated for one UE. For example, if the UE is configured with different SCSs for cells aggregated for the cell, the (absolute time) duration of time resources (e.g., subframes, time slots, or TTIs) including the same number of symbols may be different among the aggregated cells. In this article, the symbol may include an OFDM symbol (or a cyclic prefix (CP)-OFDM symbol), an SC-FDMA symbol (or a discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbol).

[0101] Reference Figure 6 , downlink and uplink transmissions are organized into frames. Each frame has T f = 10ms duration. Each frame is divided into two half-frames, where each half-frame has a duration of 5ms. Each half-frame includes 5 sub-frames, where the duration of each sub-frame is T sf is 1ms. Each subframe is divided into slots, and the number of slots in a subframe depends on the subcarrier spacing. Each slot includes 14 or 12 OFDM symbols based on the CP. In a normal CP, each slot includes 14 OFDM symbols, and in an extended CP, each slot includes 12 OFDM symbols. The parameter set is based on an exponentially scalable subcarrier spacing Δf=2 u *15kHz.

[0102] Table 3 shows the subcarrier spacing Δf=2 u *N is the number of OFDM symbols per time slot of 15kHz slot symb , the number of time slots per frame N frame,u slot , and the number of time slots N per subframe for normal CP subframe,u slot .

[0103] [Table 3]

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

[0105] Table 4 shows the subcarrier spacing Δf=2 u *N is the number of OFDM symbols per time slot of 15kHz slot symb , the number of time slots per frame N frame,u slot and the number of slots N per subframe for the extended CPsubframe,u slot .

[0106] [Table 4]

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

[0108] A slot includes a plurality of symbols (e.g., 14 or 12 symbols) in the time domain. For each parameter set (e.g., subcarrier spacing) and carrier, a common resource block (CRB) N indicated by higher layer signaling (e.g., RRC signaling) is allocated. start,u grid To begin, we define N size,u grid，x *N RB sc subcarriers and N subfrane，u symb OFDM symbol resource grid, where N size,u grid，x is the number of resource blocks (RBs) in the resource grid, and the subscript x is DL for the downlink and UL for the uplink. N RB sc is the number of subcarriers per RB. In 3GPP-based wireless communication systems, N RB sc Typically 12. For a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL), there is one resource grid. The carrier bandwidth N for subcarrier spacing configuration u size,u grid Given by high-level parameters (e.g., RRC parameters). Each element in the resource grid for antenna port p and subcarrier spacing configuration u is called a resource element (RE), and one complex symbol can be mapped to each RE. Each RE in the resource grid is uniquely identified by an index k in the frequency domain and an index 1 representing the symbol position relative to a reference point in the time domain.

[0109] In 3GPP-based wireless communication systems, an RB is defined by 12 consecutive subcarriers in the frequency domain. In 3GPP NR systems, RBs are classified into CRBs and physical resource blocks (PRBs). CRBs are numbered upwards from 0 in the frequency domain for subcarrier spacing configuration u. The center of subcarrier 0 of CRB 0 for subcarrier spacing configuration u coincides with "point A" used as a common reference point for the resource block grid. In 3GPP NR systems, PRBs are defined within bandwidth parts (BWPs) and are numbered from 0 to N. size BWP，i -1 numbering, where i is the number of the bandwidth part. Physical resource block n in bandwidth part i PRB With common resource block n CRB The relationship between them is as follows:PRB =n CRB +N size BWP,i , where N size BWP，i It is a common resource block where the bandwidth part starts relative to CRB 0. A BWP includes multiple consecutive RBs. A carrier can include up to N (e.g., 5) BWPs. A UE can be configured with one or more BWPs on a given component carrier. Only one BWP can be activated at a time among the BWPs configured for a UE. The active BWP defines the operating bandwidth of the UE within the operating bandwidth of the cell.

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

[0111] In CA, two or more CCs are aggregated. The UE can receive or transmit on one or more CCs simultaneously according to its capabilities. CA is supported for both continuous CCs and non-contiguous CCs. When CA is configured, the UE has only one RRC connection with the network. When the RRC connection is established / reestablished / switched, one serving cell provides NAS mobility information, and when the RRC connection is reestablished / switched, one serving cell provides security input. This cell is called the primary cell (PCell). PCell is a cell operating on the primary frequency, where the UE performs an initial connection establishment process or initiates a connection reestablishment process. Depending on the UE capabilities, the secondary cell (SCell) can be configured to form a set of serving cells together with the PCell. SCell is a cell that provides additional radio resources on top of a special cell (PCell). Therefore, the set of configured serving cells for the UE always consists of one PCell and one or more SCells. For dual connection (DC) operation, the term "PCell" refers to the PCell of the primary cell group (MCG) or the primary SCell (PSCell) of the secondary cell group (SCG). SpCell supports physical uplink control channel (PUCCH) transmission and contention-based random access, and is always activated. MCG is a set of serving cells associated with the master node, which includes SpCell (PCell) and optionally one or more SCells. For UEs configured with DC, SCG is a subset of serving cells associated with the secondary node, which includes PSCell and zero or more SCells. For UEs in RRC_CONNECTED that are not configured with CA / DC, there is only one serving cell consisting of PCell. For UEs in RRC_CONNECTED that are configured with CA / DC, the term "serving cell" is used to refer to the set of cells consisting of SpCell and all SCells. In DC, two MAC entities are configured in the UE: one for MCG and one for SCG.

[0112] Figure 7 An example of data flow in a 3GPP NR system to which an implementation of the present disclosure is applied is shown.

[0113] Reference Figure 7 , "RB" means radio bearer, and "H" means header. Radio bearers are classified into two groups: DRB for user plane data and SRB for control plane data. MAC PDU is transmitted / received to / from an external device through the PHY layer using radio resources. MAC PDU arrives at the PHY layer in the form of a transport block.

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

[0115] Network-controlled mobility is applied to UEs in RRC_CONNECTED and is classified into two types of mobility: cell-level mobility and beam-level mobility. Beam-level mobility includes intra-cell beam-level mobility and inter-cell beam-level mobility.

[0116] Cell-level mobility requires triggering explicit RRC signaling, i.e., handover. For inter-gNB handover, the signaling process includes at least the following operations.

[0117] 1. The source gNB initiates handover and sends a HANDOVER REQUEST message via the Xn interface.

[0118] 2. The target gNB performs admission control and provides the new RRC configuration as part of the HANDOVER REQUESTACKNOWLEDGE message.

[0119] 3. The source gNB provides the RRC configuration to the UE by forwarding the RRCReconfiguration message received in the HANDOVER REQUEST ACKNOWLEDGE message. The RRCReconfiguration message includes at least the cell identity (ID) and all information required to access the target cell so that the UE can access the target cell without reading system information. For some cases, the information required for contention-based and contention-free random access may be included in the RRCReconfiguration message. The access information to the target cell may include beam-specific information (if any).

[0120] 4. The UE moves the RRC connection to the target gNB and replies with the RRCReconfigurationComplete message.

[0121] In case of dual active protocol stack (DAPS) handover, the UE continues DL user data reception from the source gNB until the source cell is released and continues UL user data transmission to the source gNB until successful random access to the target gNB.

[0122] Only the source PCell and the target PCell are used during DAPS handover. CA, DC, Supplementary UL (SUL), Multiple Transmit / Receive Points (TRP), Ethernet Header Compression (EHC), Conditional Handover (CHO), User Data Convergence (UDC), NR Secondary Link Configuration and V2X Secondary Link Configuration are released by the source gNB before the handover command is sent to the UE and are not configured by the target gNB until the DAPS handover is completed (i.e., at the earliest in the same message that releases the source PCell).

[0123] The handover mechanism triggered by RRC requires the UE to at least reset the MAC entity and re-establish the RLC (except for DAPS handover), where upon receiving the handover command, the UE:

[0124] -Create a MAC entity for the target;

[0125] - Establishing the associated DTCH logical channel and RLC entity for the target for each DRB configured with DAPS;

[0126] - For each DRB configured with DAPS, reconfigure PDCP entities with separate security and ROHC functions for the source and target, and associate them with the RLC entities configured by the source and target, respectively;

[0127] - Keep the rest of the source configuration until the source is released.

[0128] Supports RRC managed handover with and without PDCP entity re-establishment. For DRBs using RLC AM mode, PDCP can be re-established with a security key change or initiate a data recovery procedure without a key change. For DRBs using RLC UM mode, PDCP can be re-established with a security key change or remain intact without a key change. For SRBs, PDCP can remain intact, discard its stored PDCP PDUs / SDUs without a key change, or be re-established with a security key change.

[0129] When the target gNB uses the same DRB configuration as the source gNB, data forwarding, in-order delivery, and duplication avoidance during handover can be guaranteed.

[0130] Timer-based handover failure procedures are supported in NR. The RRC connection re-establishment procedure is used to recover from handover failures (except for specific CHO or DAPS handover scenarios):

[0131] -When a DAPS handover fails, the UE falls back to the source cell configuration, resumes the connection with the source cell, and if the source link has not been released, reports the DAPS handover failure via the source without triggering RRC connection re-establishment.

[0132] -When the initial CHO execution attempt fails or HO fails, the UE performs cell selection, and if the selected cell is a CHO candidate, and if the network configures the UE to attempt CHO after handover / CHO failure, the UE attempts CHO execution once, otherwise performs re-establishment.

[0133] Beam level mobility does not require triggering explicit RRC signaling. Beam level mobility can be intra-cell or inter-cell, the latter being referred to as inter-cell beam management (ICBM). For ICBM, the UE can receive or send UE-specific channels / signals via a TRP associated with a physical cell ID (PCI) that is different from the serving cell's PCI, while non-UE-specific channels / signals can only be received via a TRP associated with the serving cell's PCI. The gNB provides the UE with a measurement configuration via RRC signaling, which contains synchronization signal block (SSB) / channel state information (CSI) resources and resource sets, trigger states for triggering channel and interference measurements and reports, and configuration of the report. In the case of ICBM, the measurement configuration includes SSB resources associated with a PCI that is different from the serving cell's PCI. Beam level mobility is then handled at the lower layers with the help of physical layer and MAC layer control signaling, and does not require RRC to know which beam is being used at a given point in time.

[0134] The SSB-based beam-level mobility is based on the SSB associated with the initial DL BWP and can only be configured for the initial DL BWP and the DL BWP containing the SSB associated with the initial DL BWP. For other DL BWPs, beam-level mobility can only be performed based on CSI-RS.

[0135] CHO is defined as a handover performed by the UE when one or more handover execution conditions are met. The UE starts evaluating the execution conditions when receiving the CHO configuration and stops evaluating the execution conditions once the handover is performed.

[0136] The following principles apply to CHO:

[0137] -CHO configuration contains the configuration of the CHO candidate cell generated by the candidate gNB and the execution conditions generated by the source gNB.

[0138] - The execution condition can consist of one or two trigger conditions (CHO events A3 / A5). Only a single reference signal (RS) type is supported, and up to two different trigger quantities (e.g., reference signal received power (RSRP) and reference signal received quality (RSRQ), RSRP and signal-to-noise-interference ratio (SINR), etc.) can be configured simultaneously to evaluate the CHO execution condition of a single candidate cell.

[0139] - Before any CHO execution conditions are met, upon receiving a HO command (without CHO configuration), the UE performs the HO procedure independently of any previously received CHO configuration.

[0140] - While performing CHO, ie from the time the UE starts synchronizing with the target cell, the UE does not monitor the source cell.

[0141] The UE variable VarConditionalReconfig includes the accumulated configuration of CPC configuration and / or CHO, including pointers to CHO and / or CPC execution conditions (associated measId) and the stored target candidate SpCellRRCReconfiguration.

[0142] Table 5 shows an example of VarConditionalReconfig.

[0143] [Table 5]

[0144]

[0145] The UE operation with respect to conditional reconfiguration (e.g., CHO, CPA, CPC) and VarConditionalReconfig may be as follows.

[0146] For example, in order for the UE to receive RRCReconfiguration, the UE may perform the following actions upon receiving RRCReconfiguration or upon performing conditional reconfiguration (e.g., CHO, CPA, CPC):

[0147] 1> If RRCReconfiguration is applied due to conditional reconfiguration execution when cell selection is performed while timer T311 is running:

[0148] 2> Remove all entries in VarConditionalReconfig, if any;

[0149] 1> If reconfigurationWithSync is included in the spCellConfig of the MCG or SCG, and when the MAC of the NR cell group successfully completes the random access procedure triggered above:

[0150] 2> If reconfigurationWithSync is included in the spCellConfig of MCG; or

[0151] 2> If reconfigurationWithSync is included in the spCellConfig of the SCG and the CPC is configured:

[0152] 3> Remove all entries in VarConditionalReconfig, if any;

[0153] For example, for SCG release, the UE may:

[0154] 1> As a result of SCG release triggered by E-UTRA (i.e., (NG)EN-DC case) or NR (i.e., NR-DC case):

[0155] 2> Reset SCG MAC, if configured;

[0156] 2> For each RLC bearer that is part of the SCG configuration:

[0157] 3>Execute the RLC bearer release process;

[0158] 2> For each backhaul (BH) RLC channel that is part of the SCG configuration:

[0159] 3>Execute BH RLC channel release process;

[0160] 2> Release SCG configuration;

[0161] 2> If CPC is configured,

[0162] 3> Remove all entries in VarConditionalReconfig, if any;

[0163] For example, for conditional reconfiguration, the network configures one or more candidate target SpCells to the UE in the conditional reconfiguration. The UE evaluates the conditions of each configured candidate target SpCell. The UE applies the conditional reconfiguration associated with one of the target SpCells that meets the associated execution condition. The network provides configuration parameters for the target SpCell in the ConditionalReconfiguration IE.

[0164] The UE may perform the following actions based on the received ConditionalReconfiguration IE:

[0165] 1> If ConditionalReconfiguration contains condReconfigToRemoveList:

[0166] 2>Execute the conditional reconfiguration removal process;

[0167] 1> If ConditionalReconfiguration contains condReconfigToAddModList:

[0168] 2>Perform conditional reconfiguration additions / modifications;

[0169] For conditional reconfiguration removal, the UE may:

[0170] 1> For each condReconfigId value included in condReconfigToRemoveList as part of the current UE conditional reconfiguration in VarConditionalReconfig:

[0171] 2> Remove the entry with matching condReconfigId from VarConditionalReconfig;

[0172] For conditional reconfiguration addition / modification, for each condReconfigId received in the condReconfigToAddModList IE, the UE may:

[0173] 1> If an entry with a matching condReconfigId exists in condReconfigToAddModList within VarConditionalReconfig:

[0174] 2>If the entries in condReconfigToAddModList include condExecutionCond;

[0175] 3>Replace condExecutionCond in VarConditionalReconfig with the value received for that condReconfigId;

[0176] 2> If the entries in condReconfigToAddModList include condRRCReconfig;

[0177] 3>Replace condRRCReconfig in VarConditionalReconfig with the value received for this condReconfigId;

[0178] 1> Otherwise:

[0179] 2> Add a new entry in VarConditionalReconfig for the condReconfigId;

[0180] 1>Perform conditional reconfiguration evaluation;

[0181] For conditional reconfiguration evaluation, the UE may:

[0182] 1>For each condReconfigId in VarConditionalReconfig:

[0183] 2> Treat the cell with a physical cell identity matching the value indicated in ServingCellConfigCommon included in reconfigurationWithSync in the received condRRCReconfig as an applicable cell;

[0184] 2> For each measId included in the measIdList within the VarMeasConfig indicated in the condExecutionCond associated with the condReconfigId:

[0185] 3> If the entry conditions applicable to the event associated with condReconfigId (i.e., the event corresponding to the condEventId of the corresponding condTriggerConfig in VarConditionalReconfig) are met for all measurements after layer 3 filtering made during the corresponding timeToTrigger defined in VarConditionalReconfig for the event for the applicable cell:

[0186] 4> It is considered that the event associated with the measId will be satisfied;

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

[0188] 3> If the leaving condition applicable to the event associated with condReconfigId (i.e., the event corresponding to the condEventId of the corresponding condTriggerConfig in VarConditionalReconfig) is met for the applicable cell for all measurements after layer 3 filtering made during the corresponding timeToTrigger defined in VarConditionalReconfig for the event:

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

[0190] 2> If the events associated with all measIds in the condTriggerConfig for the target candidate cell in the stored condRRCReconfig are met:

[0191] 3> The target candidate cell in the stored condRRCReconfig associated with the condReconfigId is regarded as the triggering cell;

[0192] 3>Initiate conditional reconfiguration execution;

[0193] Up to 2 measIds can be configured for each condReconfigId. The conditional reconfiguration events of 2measIds can have the same or different event conditions, trigger quantities, trigger times, and trigger thresholds.

[0194] For conditional reconfiguration execution, the UE may:

[0195] 1> If there is more than one triggering cell:

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

[0197] 1> For the selected cell executed for conditional reconfiguration:

[0198] 2> Apply the stored condRRCReconfig of the selected cell and perform the action;

[0199] For example, the actions after cell selection when T311 is running may be as follows.

[0200] After selecting a suitable NR cell, the UE can:

[0201] 1> Ensure that the basic system information is valid and up-to-date;

[0202] 1> Stop timer T311;

[0203] 1> If T390 is running:

[0204] 2> Stop timer T390 for all access categories;

[0205] 1> If cell selection is triggered by reconfiguration or mobility caused by detection of radio link failure to MCG or synchronization failure with MCG, and

[0206] 1> If attemptCondReconfig is configured; and

[0207] 1> If the selected cell is one of the candidate cells, reconfigurationWithSync is included in the masterCellGroup in VarConditionalReconfig for that candidate cell:

[0208] 2> Apply the stored condRRCReconfig associated with the selected cell and perform actions related to UE receiving RRCReconfiguration;

[0209] 1> Otherwise:

[0210] 2> If the UE is configured with conditionalReconfiguration:

[0211] 3>Reset MAC;

[0212] 3>Release spCellConfig, if configured;

[0213] 3> Release MCG SCell, if configured;

[0214] 3> Release delayBudgetReportingConfig, if configured, and stop timer T342, if running;

[0215] 3> Release overheatingAssistanceConfig, if configured, and stop timer T345, if running;

[0216] 3> If MR-DC is configured:

[0217] 4>Execute MR-DC release;

[0218] 3> Release idc-AssistanceConfig, if configured;

[0219] 3>Release btNameList, if configured;

[0220] 3>Release wlanNameList, if configured;

[0221] 3>Release sensorNameList, if configured;

[0222] 3> Release the drx-PreferenceConfig for MCG, if configured, and stop the timer T346a associated with MCG, if running;

[0223] 3> Release the maxBW-PreferenceConfig for MCG, if configured, and stop the timer T346b associated with MCG, if running;

[0224] 3> Release the maxCC-PreferenceConfig for MCG, if configured, and stop the timer T346c associated with MCG, if running;

[0225] 3> Release the maxMIMO-LayerPreferenceConfig for MCG, if configured, and stop the timer T346d associated with MCG, if running;

[0226] 3> Release the minSchedulingOffsetPreferenceConfig for MCG, if configured, and stop the timer T346e associated with MCG, if running;

[0227] 3> Release releasePreferenceConfig, if configured, and stop timer T346f, if running;

[0228] 3> Release onDemandSIB-Request, if configured, and stop timer T350, if running;

[0229] 3>Release referenceTimePreferenceReporting, if configured;

[0230] 3> Release sl-AssistanceConfigNR, if configured;

[0231] 3>Release obtainCommonLocation, if configured;

[0232] 3>Suspend all RBs except SRB0;

[0233] 2> Remove all entries in VarConditionalReconfig, if any;

[0234] For example, the actions after entering RRC_IDLE may be as follows.

[0235] The UE can:

[0236] 1>Reset MAC;

[0237] 1> If the variable pendingRNA-Update is set to true, set it to false;

[0238] 1> If entering RRC_IDLE is triggered by receiving a RRCRelease message including waitTime:

[0239] 2> If T302 is running:

[0240] 3> Stop timer T302;

[0241] 2>Start timer T302, and its value is set to waitTime;

[0242] 2> Notify the upper layer that access barring applies to all access categories except categories "0" and "2".

[0243] 1> Otherwise:

[0244] 2> If T302 is running:

[0245] 3> Stop timer T302;

[0246] 1> If T390 is running:

[0247] 2> Stop timer T390 for all access categories;

[0248] 1> If the UE leaves RRC_INACTIVE:

[0249] 2> If entering RRC_IDLE is not triggered by receiving the RRCRelease message:

[0250] 3> If stored, discard the cell reselection priority information provided by cellReselectionPriorities;

[0251] 3> Stop timer T320, if it is running;

[0252] 1> Stop all running timers except T302, T320, T325, T330, T331 and T400;

[0253] 1> discard UE inactive AS context, if configured;

[0254] 1> Release suspendConfig, if configured;

[0255] 1>Remove all entries in VarConditionalReconfig, if any;

[0256] In summary, i) if RRCReconfiguration is applied due to conditional reconfiguration after cell selection performed while timer T311 is running (i.e., conditional reconfiguration upon RRC connection reestablishment after radio link failure (RLF)), ii) if reconfigurationWithSync is included in the spCellConfig of the MCG or SCG, and when the MAC of the NR cell group successfully completes the above-mentioned triggered random access procedure (i.e., successful mobility), iii) at the time of SCG release, iv) at the time of cell selection performed while timer T311 is running (i.e., RRC connection reestablishment after RLF), or when entering RRC_IDLE, all entries within VarConditionalReconfig can be removed.

[0257] Typically, all conditional reconfigurations (eg, VarConditionalReconfig) for a given UE may be removed (eg, not maintained) when any conditional mobility is completed.

[0258] The introduction of subsequent mobility in Rel-18 has been discussed. In subsequent mobility, the UE can maintain a given conditional mobility command regardless of the change of the serving cell, and use the conditional mobility command whenever a condition is met. Therefore, without receiving additional reconfiguration and performing reinitialization using the given conditional mobility command, the UE can perform one or more subsequent mobilities based on the given conditional mobility command.

[0259] As described above, whenever mobility is performed, information for subsequent mobility (e.g., conditional mobility commands and / or UE variables VarConditionalReconfig) may be maintained. The list of candidate cell configurations maintained may be different for each target cell. In addition, from the perspective of the UE, there is a high probability that many candidate cell configurations for each target cell that need to be maintained for subsequent mobility are actually duplicates. In other words, candidate cell configurations with the same physical cell identifier may be included in multiple mobility commands, and therefore, candidate cell configurations for each target cell that need to be maintained for subsequent mobility may overlap.

[0260] In practice, candidate cell configurations with the same physical identifier may have similar cell configurations, but may have different roles depending on whether the candidate cell will be an SpCell or an SCell in multiple mobility commands. Therefore, the UE may have a large number of candidate cell configurations for each mobility command for performing subsequent mobility, and since the UE may have a large number of repeated cell configurations, information redundancy may increase from the UE's perspective.

[0261] In addition, information for subsequent conditional mobility based on full configuration may result in significant signaling overhead. Therefore, incremental configuration may be supported as a cell configuration for subsequent conditional mobility. That is, the cell configuration may be incremental information to be applied to the serving cell configuration when providing the cell configuration to the UE, with the serving cell being the reference cell.

[0262] The biggest problem with incremental configuration for subsequent conditional mobility is the reference cell. The reference cell configuration may be a source PSCell configuration, and this may result in a configuration mismatch between the network and the UE. This is because the source PSCell may be changed while performing subsequent conditional mobility, but the mobility commands for subsequent conditional mobility may not be updated for the changed source PSCell. That is, unless the network updates the reference cell and notifies the UE each time mobility is performed, the UE may use the old reference cell configuration to apply the target cell configuration when performing subsequent mobility. For this reason, without the new principle of reference cell selection, incremental configuration may result in mobility failure or connection failure.

[0263] In addition, in the process of updating the reference cell configuration, information for many repeated candidate cells needs to be updated separately, and this may also cause signaling overhead.

[0264] According to an implementation of the present disclosure, the UE may receive from the network at least one cell configuration list having an identifier (ID) as a pre-configuration for subsequent mobility. The UE may receive from the network a mobility command including a set of multiple IDs. The mobility command may also include at least one indication to indicate which cell configuration should be applied to the SpCell (i.e., PCell or PSCell).

[0265] According to an implementation of the present disclosure, upon receiving a mobility command, the UE may check from the perspective of UE capabilities whether each cell configuration in the preconfiguration linked to a set of multiple IDs in the mobility command is fully applicable. It may be assumed that a complete configuration is generated based on a set of multiple IDs. If all cell configurations are applicable, the UE may generate a complete configuration for each cell and / or for each cell group. In order to generate a complete configuration, if the cell configuration is linked to an ID, the UE may use the cell configuration in the preconfiguration.

[0266] According to an implementation of the present disclosure, among given IDs, if a specific ID is specifically indicated for SpCell, the cell configuration in the preconfiguration linked to the specific ID can be used for SpCell configuration independently of the current PSCell configuration (if any) for incremental configuration. After generating the full configuration, the UE can apply the full configuration and perform mobility from the current SpCell to the cell according to the preconfiguration indicated by the network as the new SpCell in the mobility command.

[0267] According to the implementation of the present disclosure, for pre-configuration, the network may provide the UE with a public configuration that can be used when performing mobility. The public configuration may include a cell configuration list and / or a cell group configuration list. An ID may be assigned per cell configuration and / or per cell group configuration. Each ID may be assigned by a unique value.

[0268] According to the implementation of the present disclosure, for the case of cell configuration, a cell configuration list to be used for SpCell and a cell configuration list to be used for SCell can be provided separately. In the cell configuration list for SpCell, a cell configuration list to be used for PCell and a cell configuration list to be used for PSCell can also be provided separately. Alternatively, the network can provide a single cell configuration list that can be used for SpCell or SCell in any case. The network can assign multiple IDs per cell configuration. If the network provides a cell configuration list to be used for SpCell and a cell configuration list to be used for SCell, the network can assign multiple IDs per list. That is, the ID can be repeated with the IDs of other lists.

[0269] According to the implementation of the present disclosure, a cell group configuration list may be provided for the case of cell group configuration. In each cell group configuration, at least one cell configuration for SpCell and one or more cell configurations for SCell may be included. The network may assign multiple IDs per cell group configuration. That is, each cell configuration in the cell group configuration may not have an ID.

[0270] According to an implementation of the present disclosure, in order to provide an ID for a mobility command, the network may construct a message using only preconfigured IDs. The network may configure a mobility command by including only one ID for each cell and / or each cell group, and may also configure candidate cells and / or candidate cell groups to perform conditional mobility using preconfigured multiple IDs.

[0271] According to the implementation of the present disclosure, if the network has configured the cell configuration list as pre-configuration, the pre-configured multiple IDs can be used to configure the cells to be applied to the cell group. When the cell ID is used to configure the cell group, the network can provide an additional indication to identify which cell should be the SpCell of the cell group, or the network can provide information notifying which ID (the corresponding cell configuration is linked to the ID) should be used for the SpCell of the cell group.

[0272] According to an implementation of the present disclosure, when configuring a cell group configuration in a mobility command, the network may specify a reference cell instead of a source cell separately to the UE. In order to notify the UE of the reference cell specified for incremental configuration, the network may additionally indicate to the UE to apply a cell configuration linked to a specific ID. The reference cell information is sufficient as an indication for SpCell only when the full configuration has provided a preconfigured cell configuration. That is, if only an indication for SpCell is provided, the UE may apply the cell configuration for SpCell as the reference cell when performing incremental configuration. Otherwise, even if a unique indication for the reference cell is provided, the UE may apply the cell configuration for the reference cell as for SpCell.

[0273] According to an implementation of the present disclosure, when constructing a mobility command, if the network decides that it is not sufficient to provide an ID, the network may include additional information as an incremental configuration based on an ID set. For example, if a new radio bearer configuration and / or a new measurement configuration not included in the pre-configuration is required, the network may add additional information to the ID for the cell group, i.e., ID+additional information.

[0274] The following figures are created to explain the specific embodiments of the present disclosure. The names of specific devices or the names of specific signals / messages / fields shown in the figures are provided by way of example, so the technical features of the present disclosure are not limited to the specific names used in the following figures.

[0275] Figure 8 An example of a method performed by a wireless device to which an implementation of the present disclosure is applied is shown.

[0276] At step S800, the method comprises receiving a first reconfiguration from a network. The first reconfiguration comprises i) a plurality of reference cell configurations, and ii) an ID associated with each of the plurality of reference cell configurations.

[0277] At step S810, the method includes receiving a second reconfiguration from the network. The second reconfiguration includes at least one mobility command associated with mobility for each target cell. Each of the at least one mobility command includes a single cell configuration for each target cell. Each of the at least one mobility command is linked to one of the IDs associated with each of the plurality of reference cell configurations.

[0278] At step S820 , the method includes applying the single cell configuration for the target cell to a corresponding reference configuration to which the ID is linked in the at least one reference configuration.

[0279] At step S830 , the method includes performing mobility to a target cell.

[0280] In some implementations, the second configuration may include information notifying which cell configuration among multiple reference cell configurations is applied to the SpCell. The information may correspond to a specific ID among the IDs. In this case, the step of applying the single cell configuration may include: applying the single cell configuration for the SpCell to the corresponding reference configuration to which the specific ID is linked. That is, when a specific ID among the IDs is indicated as an ID related to the SpCell, the single cell configuration linked to the specific ID may be applied to the corresponding reference configuration with the specific ID.

[0281] In some implementations, the method may further include checking whether each of the plurality of reference configurations in the first reconfiguration is applicable.

[0282] In some implementations, applying the single cell configuration may include generating a full configuration based on the corresponding reference configuration and the single cell configuration.

[0283] In some implementations, the plurality of reference cell configurations may include a cell configuration list for SpCell and a cell configuration list for SCell. The cell configuration list for SpCell may include a cell configuration list for PCell and a cell configuration list for PSCell.

[0284] In some implementations, each of the plurality of reference cell configurations may be included in each of the plurality of cell group configurations. Each of the plurality of cell group configurations includes at least one cell configuration for SpCell and one or more cell configurations for SCell.

[0285] In some implementations, each of the at least one mobility command may also be linked to additional information not included in the first reconfiguration. The additional information may include a radio bearer configuration and / or a measurement configuration.

[0286] In some implementations, the wireless device communicates with at least one of a mobile device other than the wireless device, a network, and / or an autonomous vehicle.

[0287] In addition, the above Figure 8 The method described in the angle of the wireless device can be obtained by Figure 2 The first wireless device 100 and / or Figure 3 The UE 100 shown is used for execution.

[0288] The wireless device includes at least one transceiver, at least one processor, and at least one memory, the at least one memory being operatively connected to the at least one processor and storing instructions, the instructions being executed based on execution by the at least one processor Figure 8 The method described in .

[0289] More specifically, the wireless device receives a first reconfiguration from a network. The first reconfiguration includes i) a plurality of reference cell configurations, and ii) an ID associated with each of the plurality of reference cell configurations.

[0290] The wireless device receives a second reconfiguration from the network. The second reconfiguration includes at least one mobility command associated with mobility for each target cell. Each of the at least one mobility command includes a single cell configuration for each target cell. Each of the at least one mobility command is linked to one of the IDs associated with each of the plurality of reference cell configurations.

[0291] The wireless device applies the single cell configuration for the target cell to a corresponding reference configuration to which the ID is linked in the at least one reference configuration.

[0292] The wireless device performs mobility to a target cell.

[0293] In some implementations, the second configuration may include information notifying which cell configuration among multiple reference cell configurations is applied to the SpCell. The information may correspond to a specific ID among the IDs. In this case, the step of applying the single cell configuration may include: applying the single cell configuration for the SpCell to the corresponding reference configuration to which the specific ID is linked. That is, when a specific ID among the IDs is indicated as an ID related to the SpCell, the single cell configuration linked to the specific ID may be applied to the corresponding reference configuration with the specific ID.

[0294] In some implementations, the wireless device may also check whether each of the plurality of reference configurations in the first reconfiguration is fully applicable.

[0295] In some implementations, applying the single cell configuration may include generating a full configuration based on the corresponding reference configuration and the single cell configuration.

[0296] In some implementations, the plurality of reference cell configurations may include a cell configuration list for SpCell and a cell configuration list for SCell. The cell configuration list for SpCell may include a cell configuration list for PCell and a cell configuration list for PSCell.

[0297] In some implementations, each of the plurality of reference cell configurations may be included in each of the plurality of cell group configurations. Each of the plurality of cell group configurations includes at least one cell configuration for SpCell and one or more cell configurations for SCell.

[0298] In some implementations, each of the at least one mobility command may also be linked to additional information not included in the first reconfiguration. The additional information may include a radio bearer configuration and / or a measurement configuration.

[0299] In addition, the above Figure 8 The method described in the wireless device angle can be included in Figure 2 The processor 102 in the first wireless device 100 shown controls and / or performs the Figure 3 The processor 102 in the UE 100 shown controls the execution.

[0300] A processing device adapted to control a wireless device includes at least one processor and at least one memory operatively connected to the at least one processor. The at least one processor is adapted to execute Figure 8 The method described in .

[0301] In addition, the above Figure 8 The method of describing the angle of the wireless device may be stored in a Figure 2 The first wireless device 100 is shown to be executed by software code 105 in the memory 104.

[0302] The technical features of the present disclosure may be implemented directly in hardware, in software executed by a processor, or in a combination of the two. For example, a method performed by a wireless device in wireless communication may be implemented in hardware, software, firmware, or any combination thereof. For example, the software may reside in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, removable disk, CD-ROM, or any other storage medium.

[0303] Some examples of storage media can be connected to a processor so that the processor can read information from the storage medium. In an alternative, the storage medium can be integrated into the processor. The processor and the storage medium can reside in an ASIC. For another example, the processor and the storage medium can reside as discrete components.

[0304] The computer-readable medium may include a tangible and non-transitory computer-readable storage medium.

[0305] For example, non-transitory computer-readable media may include RAM (e.g., synchronous DRAM (SDRAM)), ROM, non-volatile RAM (NVRAM), EEPROM, flash memory, magnetic or optical data storage media, or any other media that can be used to store instructions or data structures. Non-transitory computer-readable media may also include combinations of the above items.

[0306] Additionally, the methods described herein may be implemented at least in part by a computer-readable communication medium that carries or communicates code in the form of instructions or data structures and can be accessed, read, and / or executed by a computer.

[0307] According to some implementations of the present disclosure, a non-transitory computer readable medium (CRM) stores instructions that are executed by at least one processor. Figure 8 The method described in .

[0308] Fig. 9 An example of a method executed by a base station to which an implementation of the present disclosure is applied is shown.

[0309] At step S900, the method includes sending a first reconfiguration to a wireless device. The first reconfiguration includes i) a plurality of reference cell configurations, and ii) an ID associated with each of the plurality of reference cell configurations.

[0310] At step S910, the method includes sending a second reconfiguration to the wireless device. The second reconfiguration includes at least one mobility command associated with mobility for each target cell. Each of the at least one mobility command includes a single cell configuration for each target cell. Each of the at least one mobility command is linked to one of the IDs associated with each of the plurality of reference cell configurations.

[0311] In step S920, the single cell configuration for the target cell is applied to the corresponding reference configuration to which the ID is linked in the at least one reference configuration, and mobility to the target cell is performed.

[0312] In addition, the above Fig. 9 The method described in the figure can be performed by Figure 2The second wireless device 200 is shown to perform.

[0313] The base station includes at least one transceiver, at least one processor and at least one memory, the at least one memory being operatively connected to the at least one processor and storing instructions, the instructions being executed based on execution by the at least one processor Fig. 9 The method described in .

[0314] More specifically, the base station sends a first reconfiguration to the wireless device. The first reconfiguration includes i) a plurality of reference cell configurations, and ii) an ID associated with each of the plurality of reference cell configurations.

[0315] The base station sends a second reconfiguration to the wireless device. The second reconfiguration includes at least one mobility command associated with mobility for each target cell. Each of the at least one mobility command includes a single cell configuration for each target cell. Each of the at least one mobility command is linked to one of the IDs associated with each of the plurality of reference cell configurations.

[0316] The single cell configuration for the target cell is applied to the corresponding reference configuration to which the ID is linked in the at least one reference configuration, and mobility to the target cell is performed.

[0317] In the following, various examples of UE operation according to the implementation of the present disclosure are described. The various examples described below can be applied to the above Figure 8 and / or Fig. 9 The method of applying the implementation of the present disclosure described in .

[0318] 1. Example 1: Common Cell Configuration for Conditional PSCell Addition and / or Change (CPAC) 1

[0319] Step 1: Receive provisioning for CPAC

[0320] The UE receives a first RRC signaling including a cell configuration list for CPA and / or CPC. The cell configuration list may generally be used for pre-configuration for the UE. In the pre-configuration, each cell configuration may be assigned an ID as a unique value. Each cell configuration may be a complete configuration for one of the serving cells. Upon receiving the pre-configuration, the UE stores the pre-configuration in a UE variable (e.g., VarConditionalReconfig).

[0321] Fig.10 An example of preconfiguration to which Example 1 of the present disclosure is applied is shown.

[0322] exist Fig.10In the pre-configuration, the pre-configuration includes a public cell configuration list for CPAC. The public cell configuration list includes cell configuration #1, cell configuration #2, ..., cell configuration #16.

[0323] Step 2: Receive conditional reconfiguration for PSCell change

[0324] The UE receives a second RRC signaling including conditional reconfiguration for CPC. The conditional reconfiguration may include one or more mobility commands for a candidate cell (e.g., RRC reconfiguration for CPC) and one or more mobility execution conditions corresponding to each of the one or more mobility commands (e.g., measID for CPC). In addition, one or more mobility commands and one or more mobility execution conditions may be linked by CPC ID. For each of the one or more mobility commands, for the target cell group configuration, multiple IDs configured for the cell may be included. Among the multiple IDs configured for the cell, a specific ID may be indicated by the network for PSCell configuration. Upon receiving the conditional reconfiguration for CPC, the UE begins to evaluate one or more execution conditions to execute CPC.

[0325] Fig.11 An example of conditional reconfiguration to which Example 1 of the present disclosure is applied is shown.

[0326] Reference Fig.11 , each mobility command and each mobility execution condition are linked by a CPC ID. For example, RRC reconfiguration #1 (i.e., mobility command #1) and Meas ID #1 (i.e., execution condition #1) are linked by CPC ID #1. RRC reconfiguration #2 (i.e., mobility command #2) and Meas ID #2 (i.e., execution condition #2) are linked by CPC ID #2. RRC reconfiguration #3 (i.e., mobility command #3) and Meas ID #3 (i.e., execution condition #3) are linked by CPC ID #3. RRC reconfiguration #4 (i.e., mobility command #4) and Meas ID #4 (i.e., execution condition #4) are linked by CPC ID #4.

[0327] In addition, RRC reconfiguration #1 includes PSCell configuration #1, SCell configuration #2, SCell configuration #3, and SCell configuration #4. RRC reconfiguration #2 includes PSCell configuration #2, SCell configuration #1, SCell configuration #3, and SCell configuration #4. RRC reconfiguration #3 includes PSCell configuration #3, SCell configuration #1, SCell configuration #4, and SCell configuration #5. RRC reconfiguration #4 includes PSCell configuration #4, SCell configuration #1, SCell configuration #3, and SCell configuration #6.

[0328] Step 3: First conditional PSCell change

[0329] If at least one mobility execution condition is met, the UE initiates a mobility procedure for CPC. The UE then generates the RRC reconfiguration to be applied based on the CPC ID linked to the execution condition from ID-based configuration to full configuration. For the generation of RRC reconfiguration, the UE can use the cell configuration list in the preconfiguration stored in the UE variable. When applying RRC reconfiguration, if the network indicates one of the IDs of the cell configuration for the PSCell, the UE can apply the preconfigured ID-related cell configuration to the PSCell configuration. Otherwise, if the network does not indicate the remaining IDs in the RRC reconfiguration, the UE can apply the preconfigured ID-related cell configuration to the SCell configuration.

[0330] For example, based on Fig.11 In the example of, if the execution condition related to Meas ID#2 is met, the UE may generate an RRC reconfiguration based on CPC ID#2 linked to Meas ID#2 by applying RRC reconfiguration#2.

[0331] If the UE cannot apply any cell configuration associated with the ID for RRC reconfiguration, the UE may declare a configuration failure and may initiate sending SCG failure information to the network.

[0332] After CPC contention, the UE may consider the rest of the list for CPCs to be allowed to perform optimization / subsequent mobility for the next CPC. The UE may maintain conditional reconfiguration and preconfiguration for CPCs and may keep evaluating execution conditions to perform CPC.

[0333] Step 4: Second conditional PSCell change

[0334] After the first conditional PSCell change, if another mobility execution condition is met, the UE may initiate a mobility process for the CPC. The UE may then generate the RRC reconfiguration to be applied based on the CPC ID linked to the execution condition from ID-based configuration to full configuration. For the generation of the RRC reconfiguration, the UE may use a list of cell configurations in the preconfiguration stored in the UE variables. The UE may not use the current PSCell (i.e., the source PSCell) as a reference cell, and the UE may use the cell configurations in the preconfiguration because each preconfigured cell configuration is a full configuration. When applying the RRC reconfiguration, if the network indicates one of the IDs of the cell configuration for the PSCell, the UE may apply the preconfigured ID-related cell configuration to the PSCell configuration. Otherwise, if the network does not indicate the remaining IDs in the RRC reconfiguration, the UE may apply the preconfigured ID-related cell configuration to the SCell configuration.

[0335] If the UE cannot apply any cell configuration associated with the ID for RRC reconfiguration, the UE may declare a configuration failure and may initiate sending SCG failure information to the network.

[0336] After CPC contention, the UE may consider the rest of the list for CPCs to be allowed to perform optimization / subsequent mobility for the next CPC. The UE may maintain pre-configuration and conditional reconfiguration for CPCs and may keep evaluating execution conditions to perform CPC.

[0337] 2. Example 2: Public cell configuration for CPAC 2

[0338] Step 1: Receive provisioning for CPAC

[0339] The UE receives a first RRC signaling including a cell configuration list for CPA and / or CPC. The cell configuration list can generally be used for pre-configuration for the UE. In the pre-configuration, each cell configuration can be assigned an ID as a unique value. Each cell configuration can be a complete configuration for one of the serving cells. There can be at least two lists per cell group (e.g., one list for PSCell configuration and another list for SCell configuration). Upon receiving the pre-configuration, the UE stores the pre-configuration in a UE variable (e.g., VarConditionalReconfig).

[0340] Fig.12 An example of preconfiguration to which Example 2 of the present disclosure is applied is shown.

[0341] exist Fig.12In the pre-configuration, the public cell configuration list includes a first cell configuration list for PSCell and a second cell configuration list for SCell. The first cell configuration list for PSCell includes PSCell configuration #1, PSCell configuration #2, ..., PSCell configuration #8. The second cell configuration list for SCell includes SCell configuration #1, SCell configuration #2, ..., SCell configuration #8. The public cell configuration list may correspond to the cell configuration list for the cell group, and there may be another cell configuration list for another cell group.

[0342] Step 2: Receive conditional reconfiguration for PSCell change

[0343] The UE receives a second RRC signaling including conditional reconfiguration for CPC. The conditional reconfiguration may include one or more mobility commands for a candidate cell (e.g., RRC reconfiguration for CPC) and one or more mobility execution conditions corresponding to each of the one or more mobility commands (e.g., measID for CPC). In addition, one or more mobility commands and one or more mobility execution conditions may be linked by CPC ID. For each of the one or more mobility commands, for the target cell group configuration, multiple IDs for cell configuration may be included. For each of the one or more mobility commands, the network may include at least one ID from the PSCell configuration list in the preconfiguration, and may include one or more IDs from the SCell configuration list in the preconfiguration. The UE may distinguish each identifier for the PSCell configuration or the SCell configuration based on a predefined manner between the UE and the network. Upon receiving the conditional reconfiguration for CPC, the UE begins to evaluate one or more execution conditions to execute CPC.

[0344] Fig.13 An example of conditional reconfiguration to which Example 2 of the present disclosure is applied is shown.

[0345] Reference Fig.13, each mobility command and each mobility execution condition are linked by a CPC ID. For example, RRC reconfiguration #1 (i.e., mobility command #1) and Meas ID #1 (i.e., execution condition #1) are linked by CPC ID #1. RRC reconfiguration #2 (i.e., mobility command #2) and Meas ID #2 (i.e., execution condition #2) are linked by CPC ID #2. RRC reconfiguration #3 (i.e., mobility command #3) and Meas ID #3 (i.e., execution condition #3) are linked by CPC ID #3. RRC reconfiguration #4 (i.e., mobility command #4) and Meas ID #4 (i.e., execution condition #4) are linked by CPC ID #4.

[0346] In addition, RRC reconfiguration #1 includes PSCell configuration #1, SCell configuration #1, SCell configuration #2, and SCell configuration #3. RRC reconfiguration #2 includes PSCell configuration #2, SCell configuration #1, SCell configuration #3, and SCell configuration #4. RRC reconfiguration #3 includes PSCell configuration #3, SCell configuration #1, SCell configuration #3, and SCell configuration #5. RRC reconfiguration #4 includes PSCell configuration #4, SCell configuration #1, SCell configuration #3, and SCell configuration #6.

[0347] Step 3: First conditional PSCell change

[0348] If at least one mobility execution condition is met, the UE initiates a mobility procedure for CPC. The UE then generates the RRC reconfiguration to be applied based on the CPC ID linked to the execution condition from ID-based configuration to full configuration. For the generation of RRC reconfiguration, the UE may use the PSCell configuration list and SCell configuration list in the preconfiguration stored in the UE variables. The UE may not use the current PSCell (i.e., the source PSCell) as a reference cell for incremental configuration, and the UE may use the cell configuration in the preconfiguration because each preconfigured cell configuration is a full configuration. When applying RRC reconfiguration, if the ID is in the preconfigured PSCell configuration list, the UE may apply the preconfigured ID-related cell configuration to the PSCell configuration. Otherwise, if the ID is in the preconfigured SCell configuration list, the UE may apply the preconfigured ID-related cell configuration to the SCell configuration.

[0349] For example, based on Fig.13For example, if the execution condition related to Meas ID#3 is met, the UE may generate an RRC reconfiguration based on CPC ID#3 linked to Meas ID#3 by applying RRC reconfiguration#3.

[0350] If the UE cannot apply any cell configuration associated with the ID for RRC reconfiguration, the UE may declare a configuration failure and may initiate sending SCG failure information to the network.

[0351] After CPC contention, the UE may consider the rest of the list for CPCs to be allowed to perform optimization / subsequent mobility for the next CPC. The UE may maintain conditional reconfiguration and preconfiguration for CPCs and may keep evaluating execution conditions to perform CPC.

[0352] Step 4: Second conditional PSCell change

[0353] After the first conditional PSCell change, if another mobility execution condition is met, the UE may initiate a mobility process for CPC. The UE may then generate the RRC reconfiguration to be applied based on the CPC ID linked to the execution condition from ID-based configuration to full configuration. For the generation of RRC reconfiguration, the UE may use the PSCell configuration list and SCell configuration list in the preconfiguration stored in the UE variables. The UE may not use the current PSCell (i.e., the source PSCell) as a reference cell for incremental configuration, and the UE may use the cell configuration in the preconfiguration because each preconfigured cell configuration is a full configuration. When applying RRC reconfiguration, if the ID is in the preconfigured PSCell configuration list, the UE may apply the preconfigured ID-related cell configuration to the PSCell configuration. Otherwise, if the ID is in the preconfigured SCell configuration list, the UE may apply the preconfigured ID-related cell configuration to the SCell configuration.

[0354] If the UE cannot apply any cell configuration associated with the ID for RRC reconfiguration, the UE may declare a configuration failure and may initiate sending SCG failure information to the network.

[0355] After CPC contention, the UE may consider the rest of the list for CPCs to be allowed to perform optimization / subsequent mobility for the next CPC. The UE may maintain conditional reconfiguration and preconfiguration for CPCs and may keep evaluating execution conditions to perform CPC.

[0356] 3. Example 3: Public cell group configuration for CPAC

[0357] Step 1: Receive provisioning for CPAC

[0358] The UE receives a first RRC signaling including a list of cell group configurations for CPA and / or CPC. The cell group configuration list can generally be used for pre-configuration for the UE. In the pre-configuration, an ID as a unique value can be assigned to each cell group configuration. Each cell group configuration can be a set of complete configurations of the serving cell. In each cell group configuration, there may be at least one cell configuration for the PSCell and one or more cell configurations for the SCell. That is, a set of complete configurations may include at least one PSCell configuration and one or more SCell configurations. Upon receiving the pre-configuration, the UE stores the pre-configuration in a UE variable (e.g., VarConditionalReconfig).

[0359] Fig.14 An example of preconfiguration to which Example 3 of the present disclosure is applied is shown.

[0360] exist Fig.14 In the pre-configuration, the common cell configuration list for CPAC is included. The common cell configuration list includes four cell group configurations (i.e., cell group configuration #1 to cell group configuration #4). Each of cell group configuration #1 to cell group configuration #4 includes one SpCell (e.g., PSCell) configuration and three other cell configurations that can be used for SCell.

[0361] Step 2: Receive conditional reconfiguration for PSCell change

[0362] The UE receives a second RRC signaling including a conditional reconfiguration for CPC. The conditional reconfiguration may include one or more mobility commands for a candidate cell (e.g., RRC reconfiguration for CPC) and one or more mobility execution conditions corresponding to each of the one or more mobility commands (e.g., measID for CPC). In addition, the one or more mobility commands and the one or more mobility execution conditions may be linked by a CPC ID. For each of the one or more mobility commands, for a target cell group configuration, at least one ID configured for a cell group may be included. Upon receiving the conditional reconfiguration for CPC, the UE begins evaluating one or more execution conditions to execute CPC.

[0363] Fig.15 An example of conditional reconfiguration to which Example 3 of the present disclosure is applied is shown.

[0364] Reference Fig.15, each mobility command and each mobility execution condition are linked by a CPC ID. For example, RRC reconfiguration #1 (i.e., mobility command #1) and Meas ID #1 (i.e., execution condition #1) are linked by CPC ID #1. RRC reconfiguration #2 (i.e., mobility command #2) and Meas ID #2 (i.e., execution condition #2) are linked by CPC ID #2. RRC reconfiguration #3 (i.e., mobility command #3) and Meas ID #3 (i.e., execution condition #3) are linked by CPC ID #3. RRC reconfiguration #4 (i.e., mobility command #4) and Meas ID #4 (i.e., execution condition #4) are linked by CPC ID #4.

[0365] Step 3: First conditional PSCell change

[0366] If at least one mobility execution condition is met, the UE initiates a mobility procedure for CPC. The UE then generates the RRC reconfiguration to be applied based on the CPC ID linked to the execution condition from ID-based configuration to full configuration. For the generation of RRC reconfiguration, the UE may use the cell group configuration in the preconfiguration stored in the UE variable. The UE may not use the current PSCell (i.e., the source PSCell) as a reference cell for incremental configuration, and the UE may use the cell group configuration in the preconfiguration because each cell group configuration of the preconfiguration is a set of full configurations. When applying RRC reconfiguration, the UE may apply to SCell configuration and PSCell configuration based on a list linked to an ID.

[0367] For example, based on Fig.15 For example, if the execution condition related to Meas ID#1 is met, the UE may generate an RRC reconfiguration based on CPC ID#1 linked to Meas ID#1 by applying RRC reconfiguration#1.

[0368] If the UE cannot apply any cell configuration associated with the ID for RRC reconfiguration, the UE may declare a configuration failure and may initiate sending SCG failure information to the network.

[0369] After CPC contention, the UE may consider the rest of the list for CPCs to be allowed to perform optimization / subsequent mobility for the next CPC. The UE may maintain conditional reconfiguration and preconfiguration for CPCs and may keep evaluating execution conditions to perform CPC.

[0370] Step 4: Second conditional PSCell change

[0371] After the first conditional PSCell change, if another mobility execution condition is met, the UE may initiate a mobility procedure for CPC. The UE may then generate the RRC reconfiguration to be applied based on the CPC ID linked to the execution condition from ID-based configuration to full configuration. For the generation of RRC reconfiguration, the UE may use the cell group configuration in the preconfiguration stored in the UE variables. The UE may not use the current PSCell (i.e., the source PSCell) as a reference cell for incremental configuration, and the UE may use the cell group configuration in the preconfiguration because each cell group configuration of the preconfiguration is a set of full configurations. When applying RRC reconfiguration, the UE may apply to the SCell configuration and PSCell configuration based on a list linked to an ID.

[0372] If the UE cannot apply any cell configuration associated with the ID for RRC reconfiguration, the UE may declare a configuration failure and may initiate sending SCG failure information to the network.

[0373] After CPC contention, the UE may consider the rest of the list for CPCs to be allowed to perform optimization / subsequent mobility for the next CPC. The UE may maintain conditional reconfiguration and preconfiguration for CPCs and may keep evaluating execution conditions to perform CPC.

[0374] The present disclosure may have various beneficial effects.

[0375] For example, the network may prevent signaling overhead in subsequent mobility scenarios by providing mobility commands to the UE based on linking to pre-configured IDs for candidate cells.

[0376] For example, since there is no need to further configure a reference cell to update an old reference cell configuration whenever mobility is performed, that is, since the reference cell can be configured by an ID, signaling overhead can be reduced.

[0377] For example, since the reference cell can be managed based on the ID even if the source cell continuously changes, configuration mismatch can be avoided when the UE applies incremental configuration in subsequent mobility scenarios.

[0378] The beneficial effects obtained by the specific examples of this specification are not limited to the effects listed above. For example, there may be a variety of technical effects that a person of ordinary skill in the art can understand or derive from this specification. Therefore, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of the present disclosure.

[0379] The claims in this disclosure can be combined in various ways. For example, the technical features in the method claims of this disclosure can be combined to be implemented or performed in a device, and the technical features in the device claims can be combined to be implemented or performed in a method. In addition, the technical features in the method claims and the device claims can be combined to be implemented or performed in a device. In addition, the technical features in the method claims and the device claims can be combined to be implemented or performed in a method. Other implementations are within the scope of the appended claims.

Claims

1. A method performed by a wireless device adapted to operate in a wireless communication system, the method comprising the steps of: receiving a first reconfiguration from the network, The first reconfiguration includes i) a plurality of reference cell configurations, and ii) an identifier ID associated with each of the plurality of reference cell configurations; receiving a second reconfiguration from the network, wherein the second reconfiguration includes at least one mobility command related to mobility for each target cell, wherein each of the at least one mobility command comprises a single cell configuration for each target cell, and wherein each of the at least one mobility command is linked to one of the IDs associated with each of the plurality of reference cell configurations; applying the single cell configuration for the target cell to a corresponding reference configuration to which the ID is linked in at least one reference configuration; and Mobility is performed to the target cell.

2. The method according to claim 1, wherein: The second configuration includes information notifying which cell configuration among the plurality of reference cell configurations is applied to the special cell SpCell.

3. The method according to claim 2, wherein: The information corresponds to a specific ID among the IDs.

4. The method according to claim 3, wherein: The step of applying the single cell configuration includes applying the single cell configuration for the SpCell to the corresponding reference configuration to which the specific ID is linked.

5. The method according to claim 1 or 4, wherein: The method further comprises the step of checking whether each of the plurality of reference configurations in the first reconfiguration is fully applicable.

6. The method according to any one of claims 1 to 5, wherein: The step of applying the single cell configuration comprises generating a full configuration based on the corresponding reference configuration and the single cell configuration.

7. The method according to any one of claims 1 to 6, wherein: The multiple reference cell configurations include a cell configuration list for SpCell and a cell configuration list for secondary cell SCell.

8. The method according to claim 7, wherein: The cell configuration list for the SpCell includes a cell configuration list for a primary cell PCell and a cell configuration list for a primary SCell PSCell.

9. The method according to any one of claims 1 to 8, wherein: Each of the plurality of reference cell configurations is included in each of the plurality of cell group configurations.

10. The method according to claim 9, wherein: Each of the plurality of cell group configurations includes at least one cell configuration for a SpCell and one or more cell configurations for a SCell.

11. The method according to any one of claims 1 to 10, wherein: Each of the at least one mobility command is also linked to additional information not included in the first reconfiguration.

12. The method according to claim 11, wherein: The additional information includes radio bearer configuration and / or measurement configuration.

13. The method according to any one of claims 1 to 12, wherein: The wireless device communicates with at least one of a mobile device other than the wireless device, a network, and / or an autonomous vehicle.

14. A wireless device adapted to operate in a wireless communication system, the wireless device comprising: at least one transceiver; at least one processor; as well as At least one memory, the at least one memory being operatively connectable to the at least one processor and storing instructions, the instructions performing the method according to any one of claims 1 to 13 upon being executed by the at least one processor.

15. A processing device adapted to control a wireless device in a wireless communication system, the processing device comprising: at least one processor; as well as at least one memory operatively connectable to the at least one processor, Wherein, the at least one processor is adapted to perform the method according to any one of claims 1 to 13.

16. A non-transitory computer readable medium (CRM) storing instructions, the instructions being for executing, upon being executed by at least one processor, the method according to any one of claims 1 to 13.

17. A method performed by a base station adapted to operate in a wireless communication system, the method comprising the steps of: sending a first reconfiguration to the wireless device, The first reconfiguration includes i) a plurality of reference cell configurations, and ii) an identifier ID associated with each of the plurality of reference cell configurations; and sending a second reconfiguration to the wireless device, wherein the second reconfiguration includes at least one mobility command related to mobility for each target cell, wherein each of the at least one mobility command comprises a single cell configuration for each target cell, wherein each of the at least one mobility command is linked to one of the IDs associated with each of the plurality of reference cell configurations, wherein the single cell configuration for the target cell is applied to a corresponding reference configuration to which the ID is linked in the at least one reference configuration, and Therein, mobility to the target cell is performed.

18. A base station serving a second serving cell adapted to operate in a wireless communication system, the base station comprising: at least one transceiver; at least one processor; as well as At least one memory operatively connectable to the at least one processor and storing instructions for executing the method according to claim 17 upon being executed by the at least one processor.

Images