Cell group configuration handling for mobility in wireless communications

Abstract

The invention relates to cell group configuration handling for mobility in wireless communications. According to an embodiment of the present disclosure, a method performed by a communication device adapted to operate in a wireless communication system comprises: receiving a first configuration for a first mobility and a second configuration for a second mobility, the second configuration comprises i) a cell group configuration for the first cell, and ii) a cell group configuration for the second cell; performing a first mobility based on applying the first configuration; detecting an event for a second mobility to the first cell; determining whether the node of the first cell for the second mobility is different from the node of the current serving cell after performing the first mobility, based on the information received from the network; and performing a second mobility to the second cell based on the cell group configuration for the second cell based on the node of the first cell being different from the node of the current serving cell.

Description

Technical Field

[0001] This disclosure relates to cell group configuration processing for mobility in wireless communications. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a technology for enabling high-speed packet communication. Many proposals have been put forward for LTE objectives, including those aimed at reducing costs for users and providers, improving quality of service, and expanding and improving coverage and system capacity. 3GPP LTE requires, as a high level of compliance, reduced cost per bit, increased service availability, flexible use of frequency bands, a simple architecture, open interfaces, and appropriate terminal power consumption.

[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 the new RATs that meet both urgent market demands and longer-term requirements outlined by the ITU Radiocommunication Sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process. Furthermore, even in the more distant future, NR should be able to utilize any spectrum band available for wireless communication, at least up to 100 GHz.

[0004] NR is a single technology framework designed to address all use cases, requirements, and deployment scenarios, including enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). NR will be inherently forward compatible.

[0005] In wireless communication, a communication device can receive multiple configurations for various types of mobility. The device can retain these configurations after implementing another type of mobility. However, some configurations may become inapplicable after a certain type of mobility has been implemented. For example, some cell group configurations may become unsuitable. Summary of the Invention

[0006] Solution to the problem

[0007] This disclosure provides a method and apparatus for cell group configuration processing for mobility in a wireless communication system.

[0008] According to embodiments of this disclosure, a method performed by a communication device adapted to operate in a wireless communication system includes: receiving a first configuration for first mobility and a second configuration for second mobility, wherein the second configuration includes i) a cell group configuration for a first cell and ii) a cell group configuration for a second cell; performing the first mobility based on the first configuration; detecting an event of second mobility to the second cell; determining, based on information received from a network, whether a node of the first cell performing the second mobility after performing the first mobility is different from a node of the current serving cell; and performing the second mobility to the second cell based on the cell group configuration for the second cell, since the node of the first cell is different from the node of the current serving cell.

[0009] According to embodiments of this disclosure, a method performed by a network node configured to operate in a wireless communication system includes: sending a first configuration for first mobility and a second configuration for second mobility to a communication device, wherein the second configuration includes i) a cell group configuration for a first cell and ii) a cell group configuration for a second cell; and receiving from the communication device a notification that the cell group configuration for the first cell is inapplicable, wherein the communication device is configured to perform operations including: performing first mobility based on the application of the first configuration; detecting an event for second mobility to the first cell; determining, based on information received from the network, whether the node of the first cell performing second mobility after performing first mobility is different from the node of the current serving cell; and performing second mobility to the second cell based on the cell group configuration for the second cell, since the node of the first cell is different from the node of the current serving cell.

[0010] According to embodiments of this disclosure, an apparatus for implementing the above method is described.

[0011] This disclosure can have various beneficial effects.

[0012] For example, the UE can determine whether the SCG configuration is applicable, and if the SCG configuration in LTM is not applicable to previous mobility based on subsequent CPCs, it can decide to stop operating the SCG. The UE can avoid connection failures on the SCG, which can reduce data throughput.

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

[0014] Figure 1 An example of a communication system applying embodiments of the present disclosure is shown.

[0015] Figure 2 Examples of wireless devices applying embodiments of the present disclosure are shown.

[0016] Figure 3 An example of a UE applying an embodiment of this disclosure is shown.

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

[0018] Figure 6 The image illustrates a frame structure in a 3GPP-based wireless communication system applying embodiments of the present disclosure.

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

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

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

[0022] Figure 10 An example of a process for conditional SN change according to an embodiment of the present disclosure is shown.

[0023] Figure 11 An example of a signaling procedure for LTM according to an embodiment of this disclosure is shown.

[0024] Figure 12 An example of a DC scenario according to an embodiment of this disclosure is shown.

[0025] Figure 13 An example of an invalid cell handover configuration according to an embodiment of this disclosure is shown.

[0026] Figure 14 An example of a situation where LTM execution fails according to an embodiment of this disclosure is shown.

[0027] Figure 15 An example of a method for cell group configuration processing for mobility, performed by a communication device according to an embodiment of the present disclosure, is shown.

[0028] Figure 16 An example of a cell group configuration process for mobility is shown according to an embodiment of the present disclosure.

[0029] Figure 17 An example of a method for checking inapplicable cell group configurations according to embodiments of the present disclosure is shown.

[0030] Figure 18 Examples of methods for utilizing partial cell group configurations according to embodiments of the present disclosure are shown. Detailed Implementation

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

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

[0033] For any terms and techniques not specifically described in this invention, please refer to wireless communication standard documents published prior to this disclosure.

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

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

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

[0037] Additionally, in this 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." Furthermore, "at least one of A, B, or C" or "at least one of A, B, and / or C" may mean "at least one of A, B, and C."

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

[0039] The technical features described individually in one of the accompanying drawings of this disclosure can be implemented individually or simultaneously.

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

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

[0042] Figure 1An example of a communication system applying embodiments of the present disclosure is shown.

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

[0044] The three main demand categories for 5G include (1) Enhanced Mobile Broadband (eMBB), (2) Massive Machine Type Communications (mMTC), and (3) Ultra Reliable Low Latency Communications (URLLC).

[0045] refer to Figure 1 The communication system 1 includes wireless devices 100a to 100f, a base station (BS) 200, and a network 300. Although Figure 1 The 5G network is illustrated as an example of the network of communication system 1, but the embodiments of this disclosure are not limited to 5G systems and can be applied to future communication systems beyond 5G systems.

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

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

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

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

[0050] Wireless communication / connections 150a, 150b, and 150c can be established between wireless devices 100a to 100f and / or between wireless devices 100a to 100f and BS 200 and / or between BS 200. In this document, wireless communication / connections can be established via various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication (or device-to-device (D2D) communication) 150b, 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 can mutually send / receive radio signals via wireless communication / connections 150a, 150b, and 150c. For example, wireless communication / connections 150a, 150b, and 150c can send / receive signals via various physical channels. Therefore, at least a portion of various configuration information configuration processes, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping) and resource allocation processes for transmitting / receiving radio signals can be performed based on various proposals of this disclosure.

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

[0052] NR bands can be defined as two types of frequency ranges: frequency range 1 (FR1) and frequency range 2 (FR2). The numerical values ​​of the frequency ranges can be varied. For example, the two types (FR1 and FR2) of frequency ranges can be shown in Table 1 below. For clarity, in the frequency ranges used in NR systems, FR1 may refer to "below 6 GHz," and FR2 may refer to "above 6 GHz," and can also 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 frequency range of an NR system can be varied. For example, FR1 can include a frequency band from 410MHz to 7125MHz, as shown in Table 2 below. That is, FR1 can include a frequency band of 6GHz (or 5850, 5900, 5925MHz, etc.) or more. For example, the 6GHz (or 5850, 5900, 5925MHz, etc.) or more frequency bands included in FR1 can also include license-free bands. License-free bands can be used for various purposes, such as for vehicle communications (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 technologies implemented in the wireless devices of this disclosure may include narrowband Internet of Things (NB-IoT) technologies for low-power communication, as well as LTE, NR, and 6G. For example, NB-IoT technology may be an example of low-power wide-area network (LPWAN) technology, implemented in specifications such as LTE Cat NB1 and / or LTE Cat NB2, and may not be limited to the names mentioned above. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices of this disclosure may communicate based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and is referred to by 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 names mentioned above. Additionally and / or alternatively, the radio communication technology implemented in the wireless devices of this disclosure may include at least one of ZigBee, Bluetooth, and / or LPWAN, which takes into account low-power communication, and may not be limited to the names mentioned above. For example, ZigBee technology may be based on various specifications such as IEEE 802.15.4 to generate personal area networks (PANs) associated with small / low-power digital communication, and may be referred to by various names.

[0059] exist Figure 2 In this context, the first wireless device 100 and / or the second wireless device 200 can be implemented in various forms depending on the use case / service. For example, {the first wireless device 100 and the second wireless device 200} can correspond to... Figure 1At least one of {wireless devices 100a to 100f and BS 200}, {wireless devices 100a to 100f and wireless devices 100a to 100f} and / or {BS 200 and BS 200}. The first wireless device 100 and / or the second wireless device 200 may be configured from various elements, devices / components and / or modules.

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

[0061] The processing chip 101 may include at least one processor, such as processor 102, and at least one memory, such as memory 104. Alternatively and alternatively, memory 104 may be located outside the processing chip 101.

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

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

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

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

[0066] The processing chip 201 may include at least one processor, such as processor 202; and at least one memory, such as memory 204. Alternatively and alternatively, memory 204 may be located outside the processing chip 201.

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

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

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

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

[0071] 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 through hardware, firmware, software, or a combination thereof. As an example, one or more processors 102 and 202 may include 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). For example, one or more processors 102 and 202 may be configured as a collection of communication control processors, application processors (APs), electronic control units (ECUs), central processing units (CPUs), graphics processing units (GPUs), and memory control processors.

[0072] 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, code, instructions, and / or commands. One or more memories 104 and 204 may be configured with random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EPROM), flash memory, volatile memory, non-volatile memory, hard disk, registers, digital memory, computer-readable storage media, and / or combinations thereof. One or more memories 104 and 204 may be located internally and / or externally to one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 via various technologies such as wired or wireless connections.

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

[0074] 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 operation flowcharts disclosed herein via one or more antennas 108 and 208. In this disclosure, one or more antennas 108 and 208 may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

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

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

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

[0078] In this disclosure, BS is also referred to as node B (NB), e-node B (eNB), or gNB.

[0079] Figure 3 An example of a UE applying an embodiment of this disclosure is shown.

[0080] refer to Figure 3 UE 100 can correspond to Figure 2 The first wireless device 100.

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

[0082] Processor 102 may be adapted to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. Processor 102 may be adapted to control one or more other components of UE 100 to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. A layer of the radio interface protocol may be implemented in processor 102. Processor 102 may include an ASIC, other chipsets, logic circuits, and / or data processing devices. Processor 102 may be an application processor. Processor 102 may include at least one of a DSP, CPU, GPU, and modem (modulator and demodulator). Examples of processor 102 can be found in Qualcomm... ® SNAPDRAGON manufactured TM Series processors, by Samsung® EXYNOS manufactured TM Series processors, manufactured by Apple ® A series of processors manufactured by MediaTek ® HELIO manufactured TM Series processors, manufactured by Intel ® Manufactured ATOM TM It can be found in the series of processors or the corresponding next-generation processors.

[0083] Memory 104 is operatively coupled to processor 102 and stores various information for operating processor 102. Memory 104 may include ROM, RAM, flash memory, memory cards, storage media, and / or other storage devices. When embodiments are implemented in software, the techniques described herein can be implemented using modules (e.g., processes, functions, etc.) that perform the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed herein. Modules can be stored in memory 104 and executed by processor 102. Memory 104 can be implemented within or outside processor 102, in which case these modules can be communicatively coupled to processor 102 via various means as known in the art.

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

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

[0086] Display 143 outputs the results processed by processor 102. Keypad 144 receives inputs to be used by processor 102. Keypad 144 can be displayed on display 143.

[0087] The SIM 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 devices such as mobile phones and computers. It can also store contact information on many SIM cards.

[0088] Speaker 146 outputs sound-related results processed by processor 102. Microphone 147 receives sound-related input to be used by processor 102.

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

[0090] In particular, Figure 4 The diagram illustrates an example of the user plane protocol stack for the radio interface between the UE and the BS. Figure 5 This diagram illustrates an example of the control plane protocol stack for the radio interface between the UE and the BS. The control plane refers to the path through which control messages used to manage calls between the UE and the network are delivered. The user plane refers to the path through which data generated in the application layer (such as voice data or Internet packet data) is delivered. Reference Figure 4 The user plane protocol stack can be divided into Layer 1 (i.e., the PHY layer) and Layer 2. (See reference...) Figure 5 The control plane protocol stack can be divided into Layer 1 (i.e., the PHY layer), Layer 2, Layer 3 (e.g., the RRC layer), and the Non-Access Layer (NAS). Layers 1, 2, and 3 are referred to as the Access Layer (AS).

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

[0092] In the 3GPP NR system, the main services and functions of the MAC sublayer include: mapping between logical channels and transport channels; multiplexing MAC SDUs belonging to one or different logical channels on the transport channel to / from the transport block (TB) delivered to the physical layer; scheduling information reporting; error correction via Hybrid Automatic Repeat Request (HARQ) (one HARQ entity per cell in the case of carrier aggregation (CA)); prioritizing among UEs through dynamic scheduling; prioritizing among logical channels of a UE through logical channel prioritization; and padding. A single MAC entity can support multiple parameter sets, transmission timings, and units. The mapping constraints in logical channel prioritization control the parameters, units, and transmission timings that can be used by the logical channel.

[0093] MAC provides different types of data transmission services. To accommodate these different data transmission services, multiple types of logical channels are defined, each supporting the transmission of a specific type of information. Each logical channel type is defined by the type of information being transmitted. Logical channels are classified into two groups: control channels and traffic channels. Control channels are used only for transmitting control plane information, and traffic channels are used only for transmitting user plane information. The Broadcast Control Channel (BCCH) is a downlink logical channel used for broadcasting system control information; the Paging Control Channel (PCCH) is a downlink logical channel for transmitting paging information, system information change notifications, and indications of ongoing Public Warning Service (PWS) broadcasts; the Common Control Channel (CCCH) is a logical channel used to send control information between the UE and the network, and is used by UEs that do not have an RRC connection to 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 a single UE for transmitting user information. DTCHs can exist in both the uplink and downlink. In the downlink, the following connections exist between the logical channels and the transport channels: BCCH can be mapped to the broadcast channel (BCH); BCCH can be mapped to the downlink shared channel (DL-SCH); PCCH can be mapped to the paging channel (PCH); CCCH can be mapped to DL-SCH; DCCH can be mapped to DL-SCH; and DTCH can be mapped to DL-SCH. In the uplink, the following connections exist between the logical channels and the 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.

[0094] The RLC sublayer supports three transmission modes: Transparent Mode (TM), Non-Acknowledgment Mode (UM), and Acknowledgment Mode (AM). RLC configuration is per logical channel and does not depend on the parameter set and / or transmission duration. In 3GPP NR systems, the main services and functions of the RLC sublayer depend on the transmission mode and include: transmission of upper-layer PDUs; sequence numbering independent of the sequence number in PDCP (UM and AM); error correction via ARQ (AM only); RLC SDU segmentation (AM and UM) and re-segmentation (AM only); SDU (AM and UM) reassembly; duplicate detection (AM only); RLC SDU dropping (AM and UM); RLC reconstruction; and protocol error detection (AM only).

[0095] 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); user data transmission; reordering and deduplication detection; in-order delivery; PDCP PDU routing (in the case of separate bearers); PDCP SDU retransmission; encryption, decryption, and integrity protection; PDCP SDU discarding; PDCP reconstruction and data recovery for RLC AM; PDCP status reporting for RLC AM; PDCP PDU duplication and duplicate discarding indication to lower layers. The main services and functions of the PDCP sublayer for the control plane include: sequence numbering; encryption, decryption, and integrity protection; control plane data transmission; reordering and deduplication detection; in-order delivery; PDCP PDU duplication and duplicate discarding indication to lower layers.

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

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

[0098] Figure 6 The image illustrates a frame structure in a 3GPP-based wireless communication system applying embodiments of the present disclosure.

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

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

[0101] Table 3 is based on subcarrier spacing βf = 2 u *15 kHz shows N per time slot used for normal CP. slot symb The number of OFDM symbols, N per frame frame,u slot The number of time slots and N per subframe subframe,u slot The number of time slots.

[0102] [Table 3]

[0103] 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

[0104] Table 4 is based on subcarrier spacing βf=2 u *15kHz shows N per time slot used for extending CP. slot symb The number of OFDM symbols, N per frame frame,u slot The number of time slots and N per subframesubframe,u slot The number of time slots.

[0105] [Table 4]

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

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

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

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

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

[0111] Figure 7 An example of a data flow in a 3GPP NR system applying embodiments of the present disclosure is shown.

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

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

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

[0115] refer to Figure 8 The diagram illustrates MN 811, SN 821, and UE 830 communicating with both MN 811 and SN 821. Figure 8 As illustrated, DC refers to a scheme in which the UE (e.g., UE 830) utilizes radio resources provided by at least two RAN nodes, including an MN (e.g., MN 811) and one or more SNs (e.g., SN 821). In other words, DC refers to a scheme in which the UE is connected to and communicates with both the MN and one or more SNs. Since the MN and SN may be located at different sites, the backhaul between the MN and SN may be constructed as a non-ideal backhaul (e.g., significant delays between nodes).

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

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

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

[0119] A Network Node (MN) can be associated with a Primary Cell Group (MCG). An MCG can refer to a group of serving cells associated with an MN, and may include the Primary Cell (PCell) and optionally one or more Secondary Cells (SCells). User plane data and / or control plane data can be transmitted from the core network to the MN via MCG bearers. An MCG bearer refers to a bearer whose radio protocol resides within the MN to utilize MN resources. Figure 8 As shown, the radio protocols carried by the MCG may include PDCP, RLC, MAC and / or PHY.

[0120] A Service Provider (SN) can be associated with a Secondary Cell Group (SCG). An SCG can refer to a group of serving cells associated with the SN, and may include a Primary Secondary Cell (PSCell) and optionally one or more SCells. User plane data can be transported from the core network to the SN via SCG bearers. An SCG bearer refers to a bearer whose radio protocol resides within the SN to utilize SN resources. Figure 8 As shown, the radio protocols carried by SCG may include PDCP, RLC, MAC, and PHY.

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

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

[0123] According to various embodiments, the MN of the UE can be changed. This can be referred to as a switch or MN switch.

[0124] According to various embodiments, the SN can newly begin providing radio resources to the UE, establishing a connection with the UE, and / or communicating with the UE (i.e., a new SN for the UE can be added). This can be referred to as SN addition.

[0125] According to various embodiments, the SN of the UE can be changed while maintaining the MN of the UE. This can be referred to as SN change.

[0126] According to various embodiments, the DC may include E-UTRAN NR-DC (EN-DC) and / or Multiple Radio Access Technology (RAT)-DC (MR-DC). EN-DC refers to a DC scenario where the UE utilizes radio resources provided by E-UTRAN nodes and NR RAN nodes. MR-DC refers to a DC scenario where the UE utilizes radio resources provided by RAN nodes with different RATs.

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

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

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

[0130] Network-controlled mobility (or legacy mobility) involves the network determining a target cell for mobility and configuring mobility for the UE within that target cell. The network may send an RRCReconfiguration message to the UE, which includes the configuration for the target cell. Upon receiving the cell configuration for the target cell, the UE may execute mobility to the target cell and / or apply the configuration for the target cell.

[0131] UE-based mobility (or conditional mobility) involves the network configuring multiple candidate cells for the UE, and the UE determining mobility to a target cell among these candidate cells that meets mobility execution conditions. Conditional mobility can include at least one of conditional PCell change / conditional handover (CHO) or conditional PSCell mobility. Conditional PSCell mobility can include conditional PSCell add / change (CPAC), which includes conditional PSCell add (CPA) and / or conditional PSCell change (CPC). The network can send an RRCReconfiguration message to the UE, including a ConditionalReconfiguration Information Element (IE), which includes a list of conditional reconfigurations for the multiple candidate cells. Conditional reconfigurations for candidate cells can include a conditional reconfiguration identifier, mobility execution conditions for the candidate cells, and configurations for the candidate cells. The UE can evaluate the mobility execution conditions for the multiple candidate cells, and when the mobility execution conditions for a candidate cell are met, the UE can treat that candidate cell as the target cell and execute mobility to the target cell and / or apply the configurations for the target cell.

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

[0133] In this disclosure, the term “switch (HO)” may mean a change in PCell, or it may be a broader concept that includes not only changes in PCell but also changes / additions to PSCell.

[0134] In this disclosure, the terms “switching” and “mobility” can be used interchangeably.

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

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

[0137] exist Figure 9 middle:

[0138] - The service BS may be related to PCell, which may be the source PCell used for CHO;

[0139] - The service BS may be an MN associated with a SN in the DC, where the SN may be associated with a source PSCell used for the CPC; and

[0140] - The target cell could be a target PCell for CHO or a target PSCell for CPA / CPC.

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

[0142] In step S903, the UE may begin evaluating one or more execution conditions for the candidate cell.

[0143] In step S905, if the target cell meets the corresponding execution conditions, the UE can perform conditional mobility toward the target cell and / or apply RRC reconfiguration for the target cell, including cell configuration for the target cell. When performing conditional mobility and / or applying RRC reconfiguration for the target cell, the UE can start a timer (e.g., timer T304). While the timer is running, the UE can perform DL synchronization and / or UL synchronization toward the target cell (e.g., random access). If timing advance (TA) information for the target cell is available, the UE can skip random access toward the target cell.

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

[0145] Figure 10Examples of conditional SN change processes (i.e., conditional SN change processes / CPC processes) according to embodiments of this disclosure are shown. Figure 10 In this process, the MN initiates a conditional SN change procedure to configure and execute the CPC. Furthermore, Figure 10 The conditional SN change process can also be applied to the CPC process.

[0146] refer to Figure 10 In step S1001, the MN initiates a conditional SN change by requesting the candidate SN to allocate resources for the UE through the SN addition process, indicating that the request is for CPAC. The MN also provides the candidate SN with candidate cells recommended by the MN based on the latest measurement results for selecting and configuring SCG cells, and provides an upper limit on the number of PSCells that can be prepared by the candidate SN.

[0147] In step S1003, within the list of cells indicated as shown in the measurement results indicated by the MN, the candidate SN determines the list of PSCells to be prepared (considering the maximum number indicated by the MN), and for each prepared PSCell, the candidate SN determines other SCG SCells and provides the new corresponding SCG radio resource configuration to the MN in an NR RRCReconfiguration** message included in the SN Addition Request Acknowledge message with the prepared PSCell ID. If data forwarding is required, the candidate SN provides the MN with a data forwarding address. The candidate SN includes an indication of full or incremental RRC configuration. The candidate SN can accept or reject each of the candidate cells listed in the measurement results indicated by the MN; that is, it cannot configure any alternative candidates.

[0148] The MN can trigger an SN modification process initiated by the MN (to the source SN) to retrieve the current SCG configuration and allow the provision of relevant information for data forwarding prior to step S1001.

[0149] In step S1005, the MN sends an RRCReconfiguration message to the UE that includes the CPC configuration, i.e., an RRCReconfiguration* message and a list of associated execution conditions, wherein each RRCReconfiguration* message contains the SCG configuration and possible MCG configuration from the RRCReconfiguration** message received from the candidate SN in step S1003. Furthermore, the RRCReconfiguration message can also include updated MCG configurations, for example, to configure the required conditional measurements.

[0150] In step S1007, the UE applies the RRCReconfiguration message received in step S1005, stores the CPC configuration, and replies to the MN using the RRCReconfigurationComplete message. If the UE cannot follow (a portion of) the configuration included in the RRCReconfiguration message, it performs a reconfiguration failure procedure.

[0151] Upon receiving the MN RRCReconfigurationComplete message from the UE, the MN notifies the source SN via the Xn-U address indication procedure that the CPC has been configured. If applicable, the source SN initiates early data forwarding along with the early state transition procedure. PDCP SDU forwarding can occur during early data forwarding.

[0152] A separate Xn-U address indication procedure can be invoked to provide different forwarding addresses for the candidate target SNs being prepared. In this case, the implementations of the MN and the source SN need to ensure that EARLY STATUS TRANSFER messages (if any) from the source SN are forwarded to the correct target address. If the prepared conditional SNs no longer undergo data forwarding due to modifications or cancellation of the change procedure, the Xn-U address indication procedure can be further invoked to instruct the source SN to stop early data forwarding initiated for bearers terminated by some SNs.

[0153] In step S1009, the UE begins evaluating the execution conditions. If the execution conditions for a candidate PSCell are met, the UE performs a CPC towards the selected candidate PSCell and / or applies an RRCReconfiguration* message corresponding to the selected candidate PSCell. When the RRCReconfiguration* message is applied, the UE starts a timer (e.g., a T304 timer) and / or sends an MN RRCReconfigurationComplete* message, including an NR RRCReconfigurationComplete** message for the selected candidate PSCell, and information enabling the MN to identify the selected candidate PSCell's SN.

[0154] In step S1011, MN triggers an SN release procedure initiated by MN to notify the source SN to stop providing user data to the UE, and if applicable, triggers an Xn-U address indication procedure to notify the source SN of the SN address of the candidate PSCell selected to begin late data forwarding.

[0155] In step S1013, if the RRC connection reconfiguration process is successful, the MN notifies the SN of the selected candidate PSCell via an SN Reconfiguration Complete message including the SNRRCReconfigurationComplete** message. The MN sends an SN Release Request message to cancel the CPC in other candidate SNs (if configured). The other candidate SNs acknowledge the release request.

[0156] In step S1015, the UE synchronizes to the PSCell indicated in the RRCReconfiguration* message applied in step S1009. For example, while a timer (e.g., timer T304) is running, the UE performs DL synchronization and / or UL synchronization (e.g., random access) toward the PSCell. When random access toward the PSCell is successful, the UE stops the timer and completes the conditional SN procedure / CPC procedure.

[0157] In the following text, L1 / L2 triggered mobility (LTM) is described. In this disclosure, the terms "LTM" and "cell handover" are used interchangeably.

[0158] LTM is the process by which the gNB receives L1 measurement reports from the UE and, based on these reports, changes the UE's serving cell via MAC CE. The gNB prepares one or more candidate cells and provides their configurations to the UE via RRC messages. The gNB then triggers LTM cell handover by selecting one of the candidate configurations as the target configuration for LTM. The network can only add, modify, and release candidate cell configurations via RRC signaling.

[0159] LTM candidate cells can be configured via the RRCReconfiguration message for candidate target cells and / or the CellGroupConfig IE for each candidate target cell.

[0160] The following principles can be applied to LTM:

[0161] Candidate cell configurations can be provided as incremental configurations on top of reference configurations. Reference configurations are managed separately, and the UE stores the reference configuration as a separate configuration.

[0162] - In the absence of a reset, and with the objective of avoiding additional delays in data loss and data recovery, continue the user plane as much as possible (e.g., within the Distributed Unit DU).

[0163] - No security updates were made in LTM.

[0164] - Subsequent LTMs between candidates (i.e., after an LTM is triggered, the UE does not release other candidate cell configurations) can be performed without RRC reconfiguration.

[0165] LTM supports both intra-gNB-DU and inter-gNB-DU mobility within and between gNB-CUs. LTM also supports inter-frequency mobility, including mobility to cells on frequencies other than the current serving cell. It can support the following scenarios:

[0166] - PCell changes in non-CA scenarios;

[0167] - In the CA scenario, PCell changes without any changes to SCell;

[0168] - PCell changes with SCell changes in CA scenarios include the following cases:

[0169] a) The target PCell / target SCell is not the current serving cell (CA-CA scenario with PCell change).

[0170] b) The target PCell is the current SCell

[0171] c) The target SCell is the current PCell.

[0172] - Dual-connection scenarios, at least for PSCell changes without MN involvement, i.e., within SN.

[0173] It also supports inter-cell beam management, but this is not considered a prerequisite for using LTM.

[0174] Designs based on L1 / L2 mobility within and between DUs should share a reasonable number of commonalities.

[0175] In some implementations, validity / compliance checks of candidate cell configurations are performed upon receiving the candidate cell configuration.

[0176] Cell handover triggering information is transmitted in the MAC CE, which includes at least a candidate configuration index. Cell-specific configurations, radio bearer configurations, and measurement configurations can be part of the LTM candidate cell configuration.

[0177] In some implementations, the MAC CE can indicate the TCI state (or other beam information) to be activated for the target cell.

[0178] In some implementations, SCell activation / deactivation can be performed simultaneously with the MAC CE that triggers LTM (within the SCell associated with the candidate configuration).

[0179] The UE can perform either contention-based random access (CBRA) or contention-free random access (CFRA) during cell handover. If the UE does not need to acquire the timing advance (TA) of the target cell during cell handover, it can also skip the random access procedure. The RACH resources used for CFRA are provided in the RRC configuration.

[0180] In some implementations, CFRA resources can be provided via MAC CE.

[0181] The overall process for LTM is as follows: Figure 11 As shown. If no other candidate cells are released after each LTM completion, subsequent LTMs are completed by repeating the early synchronization, LTM execution, and LTM completion steps.

[0182] Figure 11 An example of a signaling procedure for LTM according to an embodiment of this disclosure is shown.

[0183] refer to Figure 11 In step S1101, the UE can send a MeasurementReport message to the gNB.

[0184] In step S1103, gNB can decide to use LTM and initiate LTM candidate preparation.

[0185] In step S1105, the gNB may send an RRCReconfiguration message to the UE, which includes the configuration of one or more LTM candidate target cells.

[0186] In step S1107, the UE can store the configuration of the LTM candidate target cell and send an RRCReconfigurationComplete message to the gNB.

[0187] In some implementations, the UE may optionally perform early synchronization (or DL / UL synchronization management) with the candidate cell. In this case, the UE may perform DL synchronization and / or UL synchronization (e.g., TA acquisition) with the candidate target cell before receiving the LTM cell handover command.

[0188] For example, DL synchronization of candidate cells can be performed at least based on SSB support before a cell handover command.

[0189] For example, TA acquisition of candidate cells can be supported at least based on RACH of PDCCH commands before LTM cell handover commands, where PDCCH commands are triggered only by the source cell.

[0190] The UE may perform early synchronization before, after, or during step S1109.

[0191] In step S1109, the UE can perform L1 measurements on the configured LTM candidate target cells and send a lower-layer measurement report to the gNB. The lower-layer measurement report can be carried on L1 or MAC.

[0192] In step S1111, the gNB can decide to perform an LTM cell handover to the target cell.

[0193] In step S1113, the gNB can send a cell handover command MAC CE that triggers LTM cell handover by including the candidate configuration index of the target cell. The UE can then switch to the configuration of the LTM candidate target cell.

[0194] In step S1115, the UE can detach from the source cell and apply the target cell configuration. If the TA is unavailable, the UE can perform a random access procedure (or RACH procedure) toward the target cell.

[0195] In step S1117, the UE can indicate the successful completion of the LTM cell handover toward the target cell.

[0196] In some implementations, uplink signals or messages after the UE has switched to the target cell can be used to indicate the successful completion of LTM cell handover.

[0197] exist Figure 11 In this context, when the RACH skip condition is met, the RACH process can be skipped (i.e., the UE can perform RACH-free mobility to the target cell). The RACH skip condition can include one or more of the following conditions:

[0198] - The target cell's TA information can be used for the UE and / or the target cell's TA is valid;

[0199] - The beam indication of the target cell can be used by the UE and / or when no beam fault is detected on the target cell; or

[0200] - An uplink (UL) license, used to send an uplink signal indicating the successful completion of an LTM cell handover, may be available to the UE.

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

[0202] For CBRA, the UE can send a random access preamble to the RAN node in the uplink. The UE can send Message 1 (MSG1) including the random access preamble to the RAN node. The random access preamble can be associated with a Random Access-Radio Resource Temporary Identifier (RA-RNTI). The random access preamble can be selected based on the selected RACH resource and transmitted through the time-frequency resource identified by the selected RACH resource.

[0203] For CFRA, the UE can send a dedicated random access preamble to the RAN node in the uplink. The UE can send MSG1, which includes the dedicated random access preamble, to the RAN node. The dedicated random access preamble can be associated with RA-RNTI. The dedicated random access preamble can be selected based on the CFRA resource / dedicated RACH configuration and transmitted via time-frequency resources identified by the CFRA resource / dedicated RACH configuration.

[0204] In this disclosure, subsequent mobility (e.g., subsequent CHO / CPC / CPA / LTM) is described. Subsequent mobility can refer to mobility performed after a previous mobility without reconfiguration and / or reinitialization from the network. For example, when mobility is performed based on receiving multiple mobility configurations including a configuration for mobility, subsequent mobility can be performed based on a configuration among the multiple mobility configurations already received, without reconfiguration and / or reinitialization from the network (or, without receiving a new configuration).

[0205] Meanwhile, NR Dual Connectivity (NR-DC) is a generalization of NR Intra-NR Dual Connectivity (DC), in which a UE with multiple Rx / Tx capabilities can be configured to utilize resources provided by two different nodes via a non-ideal backhaul connection, both of which provide NR access. One node can act as the primary node (MN), and the other node can act as the secondary node (SN). The MN and SN can be connected via a network interface, and at least the MN is connected to the core network.

[0206] To ensure robust SN mobility, a conditional PSCell change (CPC) is introduced. For CPC, the network can provide the UE with a CPC configuration for candidate serving cells in advance (i.e., a pre-configuration of candidate cells for CPC). This CPC configuration includes a list of RRCReconfiguration messages for candidate cells, the associated execution conditions, and / or the required conditional measurements. The UE can then begin evaluating the execution conditions. If the execution conditions for a candidate PSCell are met, the UE can perform CPC execution (i.e., apply the RRCReconfiguration message corresponding to the candidate PSCell that meets the execution conditions, and / or send an RRCReconfigurationComplete message to the network). The UE can then synchronize to the PSCell indicated in the RRCReconfiguration message.

[0207] To reduce latency, overhead, and downtime, L1 / L2 triggered mobility (LTM) is introduced. For LTM, the network can provide the UE with the configuration of candidate serving cells in advance (i.e., pre-configuration of candidate cells for LTM). The UE can then perform L1 measurements on the candidate cells and report the L1 measurement results to the network. The network can determine whether the UE should perform LTM on the candidate cells based on the L1 measurement reports. The network can send an LTM cell handover command to the UE via L1 / L2 signaling to trigger the UE to perform LTM towards the candidate cells. Upon receiving the LTM cell handover command, the UE can initiate a cell handover procedure (i.e., LTM execution on the candidate cells).

[0208] CPC supports intra-CU / inter-CU mobility scenarios (i.e., intra-SN / inter-SN CPC). On the other hand, LTM only supports intra-CU mobility scenarios. This means that for NR-DC, LTM can only be used for intra-MN PCell changes and / or intra-SN PSCell changes.

[0209] Figure 12 An example of a DC scenario according to an embodiment of this disclosure is shown.

[0210] refer to Figure 12 :

[0211] – Serving the UE using DC (e.g., NR-DC), where cell #1 is PCell and cell #3 is PSCell;

[0212] - Cell #1 and Cell #2 are configured as candidate cells for LTM cell handover in PCell;

[0213] Cells #3 and #4 are configured as candidate cells for LTM cell handover in PSCell; and

[0214] Cell #5 and Cell #6 are configured as candidate cells for inter-SN CPC.

[0215] exist Figure 12 In this scenario, it is assumed that the UE is simultaneously configured with inter-SN CPC and intra-SN LTM. In this case, for example, at least one of the following two situations may occur:

[0216] Scenario 1) During the execution of CPC between SNs, an RRC (connectivity) reconstruction process may be initiated due to an invalid RRC configuration (e.g., an invalid cell handover configuration).

[0217] Scenario 2) If an LTM cell handover command indicating a change in PSCell (i.e., intra-SN mobility) is received during inter-SN CPC execution, LTM execution may fail.

[0218] In respectively Figure 13 and Figure 14 The details of Situation 1 and Situation 2 are described in detail.

[0219] Figure 13 An example of an invalid cell handover configuration according to an embodiment of this disclosure is shown.

[0220] refer to Figure 13 During the execution of CPC between SNs, an RRC (connectivity) reconstruction process can be initiated due to an invalid RRC configuration (e.g., an invalid cell handover configuration).

[0221] In step S1301, the following can be established: Figure 12 The DCs of MN and SN#1 are shown. Cell #1 of MN can be the currently serving PCell, and cell #3 of SN#1 can be the currently serving PSCell.

[0222] In step S1303, MN and SN#1 can prepare for LTM candidate cells #3 and #4.

[0223] In step S1305, MN may send an RRCReconfiguration message, which includes cell handover configurations for LTM candidate cells #1, #2, #3 and #4.

[0224] In step S1307, MN and SN#2 can prepare CPC candidate cells #3 and #4.

[0225] In step S1309, MN may send an RRCReconfiguration message, which includes CPC configurations for CPC candidate cells #5 and #6.

[0226] In step S1311, the UE can evaluate the execution conditions for CPC candidate cells and determine that the execution conditions for cell #5 are met.

[0227] In step S1313, if the execution conditions for cell #5 are met, the UE can execute CPC toward cell #5 (i.e., inter-SN CPC) and / or apply CPC configuration for cell #5. While executing CPC toward cell #5 and / or applying CPC configuration for cell #5, the UE can start a timer (i.e., timer T304) and / or send an RRCReconfigurationComplete message to the MN. While timer T304 is running, the UE can execute random access toward cell #5.

[0228] In step S1315, the UE may detect that the cell handover configuration for candidate cells #3 and #4 has become invalid. If inter-SN CPC is performed, the configuration for LTM cell handover to PSCells of cells #3 and #4 (i.e., the cell handover configuration for candidate cells #3 and #4) may become invalid because after CPC is performed, LTM cell handover to PSCells of cells #3 and #4 becomes inter-SN (i.e., inter-CU) mobility, which is not a scenario supported by LTM.

[0229] In step S1317, the UE can initiate an RRC connection reconstruction process when an invalid RRC configuration (i.e., an invalid cell handover configuration) is detected. However, the invalid RRC configuration for LTM caused by inter-SN CPC may lead to an RRC connection reconstruction process, which can cause interruption and delay.

[0230] Figure 14 An example of a situation where LTM execution fails according to an embodiment of this disclosure is shown.

[0231] refer to Figure 14 During the CPC execution between SNs, if an LTM cell handover command indicating a change in PSCell (i.e., intra-SN mobility) is received, the LTM execution may fail.

[0232] In step S1401, the following can be established: Figure 12 The DCs of MN and SN#1 are shown. Cell #1 of MN can be the currently serving PCell, and cell #3 of SN#1 can be the currently serving PSCell.

[0233] In step S1403, MN and SN#1 can prepare for LTM candidate cells #3 and #4.

[0234] In step S1405, MN may send an RRCReconfiguration message that includes cell handover configurations for LTM candidate cells #1, #2, #3 and #4.

[0235] In step S1407, MN and SN#2 can prepare CPC candidate cells #3 and #4.

[0236] In step S1409, MN may send an RRCReconfiguration message containing CPC configurations for CPC candidate cells #5 and #6.

[0237] In step S1411, the UE can evaluate the execution conditions for CPC candidate cells and determine whether the execution conditions for cell #5 are met.

[0238] In step S1413, if the execution conditions for cell #5 are met, the UE can execute CPC toward cell #5 (i.e., inter-SN CPC) and / or apply CPC configuration for cell #5. When executing CPC toward cell #5 and / or applying CPC configuration for cell #5, the UE can start a timer (i.e., timer T304) and / or send an RRCReconfigurationComplete message to the MN. While timer T304 is running, the UE can execute random access toward cell #5.

[0239] While the UE is sending an RRCReconfigurationComplete message for CPC to cell #5 (i.e., the UE has sent the RRCReconfigurationComplete message, but the network has not yet received the RRCReconfigurationComplete message) and / or while a timer (e.g., T304 timer) is running, the network may send an LTM cell handover command to the PSCell of cell #4 sent by the UE.

[0240] In step S1415, the UE may fail to perform LTM execution. Because the UE applies the RRC configuration corresponding to cell #5 (i.e., the CPC configuration for cell #5), the target cell for the LTM cell handover command (i.e., cell #4) may be an invalid target cell, as cell #5 is inter-SN and / or inter-CU. Ultimately, the UE may fail the LTM cell handover to cell #4 and thus initiate an RRC (connectivity) reconstruction or failure recovery procedure, which can cause interruptions and latency.

[0241] Therefore, this disclosure provides various embodiments / implementations for cell group configuration processing for mobility.

[0242] Figure 15 An example of a method for cell group configuration processing for mobility, performed by a communication device according to an embodiment of the present disclosure, is shown.

[0243] refer to Figure 15 In step S1501, the communication device may receive a first configuration for first mobility and a second configuration for second mobility. The second configuration may include i) a cell group configuration for the first cell and ii) a cell group configuration for the second cell.

[0244] In step S1503, the communication device may perform first mobility based on the first configuration applied.

[0245] In step S1505, the communication device can detect events related to the second mobility to the first cell.

[0246] In step S1507, the communication device may determine, based on information received from the network, whether the node of the first cell used for the second mobility after performing the first mobility is different from the node of the current serving cell.

[0247] In step S1509, since the nodes of the first cell are different from the nodes of the current serving cell, the communication device can perform second mobility to the second cell based on the cell group configuration for the second cell.

[0248] According to various embodiments, this information may include information for distinguishing nodes.

[0249] According to various embodiments, the information used to distinguish nodes may include at least one of the node identifier of a first cell or the node identifier of a third cell that becomes the current serving cell after the first mobility is performed. The node identifier of the first cell may be included in the cell group configuration for the first cell. The node identifier of the third cell may be included in the cell group configuration for the third cell in the first configuration.

[0250] According to various embodiments, the first configuration may be associated with a cell group type, and the cell group configuration for the first cell may also be associated with a cell group type. The cell group type may include at least one of a primary cell group (MCG) or a secondary cell group (SCG).

[0251] According to various embodiments, a first configuration can be applied to the SCG. The cell group configuration for the first cell may include the SCG configuration for the primary and secondary cells (PSCell).

[0252] According to various embodiments, the cell group configuration for the second cell may include the MCG configuration for the primary cell (PCell).

[0253] According to various embodiments, based on the fact that the nodes of the first cell are different from the nodes of the currently serving cell, the communication device can determine that the cell group configuration used for the first cell is not suitable for the second mobility. Because the cell group configuration used for the first cell is not suitable, the communication device does not consider a configuration failure to be detected.

[0254] According to various embodiments, during the second mobility to the second cell, the cell group configuration for the first cell can be deactivated, suspended, or released.

[0255] According to various embodiments, the communication device can send information to the network for disabling, suspending, or releasing cell group configurations for a first cell.

[0256] According to various embodiments, the first mobility may include conditional primary / secondary cell (PSCell) change (CPC), and the second mobility may include cell handover.

[0257] According to various embodiments, cell handover can be applied to intra-node mobility but not to inter-node mobility.

[0258] According to various embodiments, the communication device can execute a CPC based on the satisfaction of corresponding CPC execution conditions. The communication device can receive a cell handover command for a first cell from the network to detect events related to second mobility to the first cell.

[0259] According to various embodiments, a communication device can receive at least one first configuration including a first cell group and a second cell group for network-triggered mobility, and at least one second configuration including a second cell group for UE autonomous mobility. The communication device can perform mobility based on the second configuration. Upon receiving a mobility command for the first configuration, the communication device can apply the first cell group configuration of the first configuration. The communication device can apply the second cell group configuration based on a check whether the first configuration is applicable to mobility based on the second configuration. The first configuration may be related to LTM. The second configuration may be related to conditional mobility. A check can be performed to determine whether the second cell group configuration is not applied when performing mobility based on the first configuration. The check can be based on an indication included in the first or second configuration.

[0260] Figure 16 An example of a cell group configuration process for mobility is shown according to an embodiment of the present disclosure.

[0261] refer to Figure 16 In step S1601, the network node may send a first configuration for first mobility and a second configuration for second mobility to the communication device. The second configuration may include i) a cell group configuration for the first cell and ii) a cell group configuration for the second cell.

[0262] In step S1603, the communication device may perform first mobility based on the application of the first configuration.

[0263] In step S1605, the communication device can detect events related to the second mobility to the first cell.

[0264] In step S1607, the communication device may determine, based on information received from the network, whether the node of the first cell used for the second mobility after the first mobility is performed is different from the node of the current serving cell.

[0265] In step S1609, since the nodes of the first cell are different from the nodes of the current serving cell, the communication device can perform second mobility to the second cell based on the cell group configuration for the second cell.

[0266] In step S1611, the network node can receive a notification from the communication device that the cell group configuration for the first cell is not applicable.

[0267] The following describes a detailed implementation of cell group configuration processing for mobility.

[0268] According to embodiments of this disclosure, when performing mobility based on a cell handover command for LTM or a conditional reconfiguration for CHO / CPA / CPC, the UE can determine whether a cell group configuration for mobility is applicable. If an inapplicable cell group configuration for mobility exists, the UE can perform the mobility procedure without applying the inapplicable cell group configuration, so that the UE does not declare configuration failure or mobility failure.

[0269] To check for inappropriate cell group configurations, the UE can perform the following steps: Figure 17 The following detailed steps are illustrated in the diagram.

[0270] Figure 17 An example of a method for checking inapplicable cell group configurations according to embodiments of the present disclosure is shown.

[0271] refer to Figure 17In step S1701, the UE may receive information to check the applicability of one or more cell group configurations in the (pre)configuration of LTM and / or one or more cell group configurations in the (pre)configuration of CHO / CPA / CPC. This information may indicate whether the relevant cell group configuration in the (pre)configuration is for mobility belonging to cell groups of different nodes (e.g., inter-Center Cell (CU) mobility, such as inter-MN or inter-SN mobility), or for mobility belonging to cell groups of the same node (e.g., intra-CU mobility, such as intra-MN or intra-SN mobility). In other words, this information may indicate a mobility type that includes at least one of inter-node mobility or intra-node mobility.

[0272] For example, the network may include / transmit a single type of mobility for this information. For instance, if information indicating mobility belonging to cell groups of different nodes (i.e., inter-node mobility) is included / transmitted, other information indicating mobility belonging to cell groups of the same node (i.e., intra-node mobility) may not be included, and vice versa. The UE can then assume that cell group configurations without this information are considered another type of mobility.

[0273] For example, to obtain this information, the network can include node identifiers in each cell group configuration to check whether each mobility is initiated within the same node or different nodes. The UE can compare the node identifiers between the source cell and the target cell when performing mobility.

[0274] In the (pre)configuration (i.e., the (pre)configuration of LTM and / or the (pre)configuration of CHO / CPA / CPC), there may be one or more candidate cells and corresponding mobility commands including one or more cell group configurations (e.g., MCG and / or SCG configurations).

[0275] In step S1703, the UE can check the applicability of all cell group configurations in the mobility command (or mobility configuration) used for mobility based on information from when / when mobility is initiated. When the cell group configuration of mobility includes information indicating that the mobility is for a change of cell group belonging to the same node (e.g., intra-central cell (CU) mobility, such as intra-MN mobility or intra-SN mobility), or when the information indicates a node identifier of a node different from the node of the serving cell to which the UE currently belongs, the UE can determine that the cell group configuration in the mobility command used for LTM or the mobility command used for CHO / CPA / CPC is not applicable to the next mobility.

[0276] When checking whether nodes are the same or different, UEs with multiple connections can consider the cell group configuration associated with the corresponding connection. That is, the UE can check the cell group configuration associated with the SCG when performing an SCG change, or the UE can check the cell group configuration associated with the MCG when performing an MCG change.

[0277] In step S1705, after checking the applicability of the mobility command, in order to apply the applicable cell group information / configuration based on the check, the UE can apply the applicable cell group configuration and disable / suspend / release inapplicable cell group configurations. For example, after the UE identifies which cell group configuration (e.g., MCG or SCG) is considered inapplicable in the RRC reconfiguration to be used for mobility, if at least one cell group configuration is applicable to that mobility, the UE can perform mobility based on applying the applicable partial cell group configuration. If at least one applicable cell group configuration exists, the UE may not declare mobility failure or configuration failure.

[0278] For inapplicable cell group configurations, the UE can perform the following operations:

[0279] - Cell Group Deactivation: Regardless of the status indication from the network, the UE can apply the cell group configuration but deactivate the cell group. When a cell group is deactivated, the UE can: i) stop PDCCH monitoring on the SpCell configured by the cell group; ii) stop PDSCH transmission on the SpCell configured by the cell group; iii) stop PUCCH transmission on the SpCell configured by the cell group; iv) stop PUSCH transmission on the SpCell configured by the cell group; v) stop CSI-RS reporting on the SpCell configured by the cell group; vi) if configured, perform Radio Resource Management (RRM) related to the SpCell configured by the cell group; and / or vii) if configured, perform Radio Link Monitoring (RLM) and / or Beam Failure Detection (BFD) related to the SpCell configured by the cell group.

[0280] - Cell Group Suspension: The UE can apply cell group configuration but suspend any transmissions on the cell group, regardless of the status indication from the network. When a cell group is suspended, the UE can suspend CG transmissions associated with the cell group for all Signaling Radio Bearers (SRBs) / Data Radio Bearers (DRBs).

[0281] - Cell group release: The UE does not apply the cell group configuration (i.e., cell group configuration), or it releases the cell group configuration automatically as soon as it is applied.

[0282] Figure 18 Examples of methods for utilizing partial cell group configurations according to embodiments of the present disclosure are shown.

[0283] refer to Figure 18 In step S1801, the UE can establish connections with the MN and SN. The UE can apply the DC configuration from the network and can have connections to the MN and SN.

[0284] In step S1803, the UE can receive (pre)configuration for LTM and (pre)configuration for subsequent CPC from the network. Each (pre)configuration may include a list of candidate cells for performing the corresponding mobility, and may also include RRC reconfiguration, which includes a cell group configuration for each candidate cell. Furthermore, the subsequent CPC (pre)configuration may (further) include multiple execution conditions corresponding to the candidate cell list. For example, the network may include information (e.g., mobility type) in the cell group configuration indicating whether the relevant mobility is a cell change with different nodes (i.e., between nodes) or not a cell change with different nodes (i.e., within nodes). As another example, the network may include information indicating the node identifier in the cell group configuration to the UE.

[0285] In step S1805, the UE can evaluate the execution conditions for subsequent CPC and perform L1 measurement (i.e., measurement without L3 filtering) according to the pre-configuration for LTM.

[0286] In step S1807, the UE can determine to perform subsequent CPC on candidate cell A that meets the corresponding execution conditions (e.g., the execution conditions for candidate cell A).

[0287] In step S1809, the UE can check whether the subsequent CPC of candidate cell A is for mobility changes of cells with different nodes (i.e., between nodes such as inter-SN CPC) based on the information in the cell group configuration in the RRC reconfiguration of (candidate cell A) for subsequent CPC.

[0288] In step S1811, the UE may apply the configuration for candidate cell A and / or the relevant cell group configuration for subsequent CPCs. The UE may perform synchronization with candidate cell A and may perform a random access procedure during the execution of subsequent CPCs.

[0289] In step S1813, after the subsequent CPC is successfully completed, the UE can receive an LTM command via L1 / L2 signaling to perform a handover from the network to candidate cell B, where the mobility commands / configurations for candidate cell B include MCG and SCG configurations. The network can send a separate LTM command for each of the MCG and SCG configurations. If the network sends a separate LTM command for each of the MCG and SCG configurations, candidate cell B can be a PSCell for the SCG configuration, and candidate cell C associated with the (pre)configuration can be used for the MCG configuration.

[0290] In step S1815, the UE can check whether the LTM of candidate cell B is for mobility (i.e., inter-SN mobility) for SCG cell changes with different nodes, based on the information in the cell group configuration in the RRC reconfiguration for LTM.

[0291] In step S1817, the UE can confirm whether the LTM to candidate cell B is mobility (i.e., inter-SN mobility) related to a cell change with an SCG configuration having different nodes, based on information in the cell group configuration in the RRC reconfiguration for LTM. If the network provides node identifiers for inspection, the UE can compare the node identifiers between candidate cell B and the current serving cell (i.e., the source PSCell cell). If the node identifiers between candidate cell B and the current serving cell are different from each other, the UE can consider that the relevant cell group configuration (i.e., SCG configuration) for LTM is not applicable.

[0292] In step S1819, the UE may apply only the MCG configuration used for LTM cell handover. The UE may release the SCG configuration without applying it for LTM cell handover. The UE may indicate the release of the SCG configuration to the network when sending signaling for LTM cell handover completion.

[0293] Furthermore, in this disclosure (e.g., in Figure 15 The method described in the text (from the UE's perspective) can be derived from... Figure 2 The first wireless device 100 and / or shown Figure 3 The UE 100 shown is executed.

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

[0295] The operation includes: receiving a first configuration for first mobility and a second configuration for second mobility, wherein the second configuration includes i) a cell group configuration for a first cell and ii) a cell group configuration for a second cell; performing first mobility based on the application of the first configuration; detecting an event for second mobility to the first cell; determining, based on information received from the network, whether the node of the first cell used for second mobility after performing first mobility is different from the node of the current serving cell; and performing second mobility to the second cell based on the cell group configuration for the second cell, since the node of the first cell is different from the node of the current serving cell.

[0296] Furthermore, in this disclosure (e.g., in Figure 15 The method described in the text (from the UE's perspective) can be stored in... Figure 2 The software code 105 in the memory 104 included in the first wireless device 100 shown is executed.

[0297] More specifically, at least one computer-readable medium (CRM) stores instructions that perform operations based on execution by at least one processor, the operations including: receiving a first configuration for first mobility and a second configuration for second mobility, wherein the second configuration includes i) a cell group configuration for a first cell and ii) a cell group configuration for a second cell; performing the first mobility based on applying the first configuration; detecting an event for the second mobility to the first cell; determining, based on information received from the network, whether the node of the first cell for the second mobility is different from the node of the current serving cell after performing the first mobility; and performing the second mobility to the second cell based on the cell group configuration for the second cell, since the node of the first cell is different from the node of the current serving cell.

[0298] Furthermore, in this disclosure (e.g., in Figure 15 The method described in the text, from the UE's perspective, can be used... Figure 2 The processor 102 included in the first wireless device 100 shown controls and / or transmits data through the processor 102. Figure 3 The processor 102 included in the UE 100 shown is used to perform the operation.

[0299] More specifically, an apparatus (e.g., a wireless device / UE) configured / adapted to operate in a wireless communication system includes at least one processor and at least one computer memory operatively connected to the at least one processor. The at least one processor is configured / adapted to perform operations including: receiving a first configuration for first mobility and a second configuration for second mobility, wherein the second configuration includes i) a cell group configuration for a first cell and ii) a cell group configuration for a second cell; performing the first mobility based on the applied first configuration; detecting an event related to the second mobility to the first cell; determining, based on information received from a network, whether the node of the first cell used for the second mobility is different from the node of the current serving cell after performing the first mobility; and performing the second mobility to the second cell based on the cell group configuration for the second cell, since the node of the first cell is different from the node of the current serving cell.

[0300] Furthermore, in this disclosure (for example, Figure 16 The method described in the text (from the perspective of network nodes) can be derived from... Figure 2 The second wireless device 200 shown in the diagram performs this function. This network node can be associated with a serving cell.

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

[0302] The operation includes: sending a first configuration for first mobility and a second configuration for second mobility to a communication device, wherein the second configuration includes i) a cell group configuration for a first cell and ii) a cell group configuration for a second cell; and receiving from the communication device a notification that the cell group configuration for the first cell is not applicable, wherein the communication device is configured to perform an operation including: performing first mobility based on applying the first configuration; detecting an event for second mobility to the first cell; determining, based on information received from the network, whether the node of the first cell for second mobility is different from the node of the current serving cell after performing first mobility; and performing second mobility to the second cell based on the cell group configuration for the second cell, since the node of the first cell is different from the node of the current serving cell.

[0303] This disclosure can have a variety of beneficial effects.

[0304] For example, the UE can determine whether the SCG configuration is applicable, and if the SCG configuration in LTM is not applicable to previous mobility based on subsequent CPCs, it can decide to stop operating the SCG. The UE can avoid connection failures on the SCG, which can reduce data throughput.

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

[0306] The claims in this specification can be combined in various ways. For example, the technical features in the method claims can be combined to implement or perform in an apparatus, and the technical features in the apparatus claims can be combined to implement or perform in a method. Furthermore, the technical features in the method claims and apparatus claims can be combined to implement or perform in a method. Other embodiments are within the scope of the appended claims.

Claims

1. A method performed by a communication device adapted to operate in a wireless communication system, the method comprising: Receive a first configuration for first mobility and a second configuration for second mobility, wherein the second configuration includes i) a cell group configuration for a first cell and ii) a cell group configuration for a second cell; The first mobility is performed based on the first configuration applied; Detect events related to the second mobility in the first cell; Based on information received from the network, determine whether the node of the first cell used for the second mobility after performing the first mobility is different from the node of the current serving cell; and The second mobility to the second cell is performed based on the cell group configuration for the second cell, since the node of the first cell is different from the node of the current serving cell.

2. The method according to claim 1, wherein, The information includes information used to distinguish nodes.

3. The method according to claim 2, wherein, The information used to distinguish nodes includes at least one of the node identifier of the first cell or the node identifier of the third cell that serves as the current serving cell after the first mobility is performed. Wherein, the node identifier of the first cell is included in the cell group configuration used for the first cell, and The node identifier of the third cell is included in the cell group configuration for the third cell in the first configuration.

4. The method according to claim 1, wherein, The first configuration is related to the cell group type. Wherein, the cell group configuration used for the first cell is related to the cell group type, and The cell group type includes at least one of primary cell group (MCG) or secondary cell group (SCG).

5. The method according to claim 4, wherein, Change the application of the first configuration to SCG, and The cell group configuration for the first cell includes the SCG configuration for the primary and secondary cells (PSCell).

6. The method according to claim 5, wherein, The cell group configuration for the second cell includes the MCG configuration for the primary cell (PCell).

7. The method of claim 1, further comprising: Based on the fact that the node of the first cell is different from the node of the current serving cell, it is determined that the cell group configuration used for the first cell is not applicable to the second mobility; Where the cell group configuration used for the first cell is not applicable, the communication device does not consider to detect a configuration failure.

8. The method according to claim 1, wherein, During the second mobility to the second cell, the cell group configuration used for the first cell is deactivated, suspended, or released.

9. The method of claim 8, further comprising: Send information to the network regarding the deactivation, suspension, or release of the cell group configuration for the first cell.

10. The method according to claim 1, wherein, The first mobility includes conditional primary / secondary cell (PSCell) change (CPC), and the second mobility includes cell handover.

11. The method according to claim 10, wherein, The cell handover applies to intra-node mobility but not to inter-node mobility.

12. The method according to claim 10, wherein, The execution of the first mobility includes executing the CPC based on the satisfaction of the corresponding CPC execution conditions, and The event of detecting the second mobility to the first cell includes receiving a cell handover command for the first cell from the network.

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

14. A user equipment (UE) configured to operate in a wireless communication system, the UE comprising: At least one transceiver; At least one processor; as well as At least one memory, operatively coupled to the at least one processor and storing instructions that perform operations based on execution by the at least one processor, the operations including: Receive a first configuration for first mobility and a second configuration for second mobility, wherein the second configuration includes i) a cell group configuration for a first cell and ii) a cell group configuration for a second cell; The first mobility is performed based on the first configuration applied; Detect events related to the second mobility in the first cell; Based on information received from the network, determine whether the node of the first cell used for the second mobility is different from the node of the currently serving cell after the first mobility is performed; and The second mobility to the second cell is performed based on the cell group configuration for the second cell, since the node of the first cell is different from the node of the current serving cell.

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

16. A network node configured to operate in a wireless communication system, the network node comprising: At least one transceiver; At least one processor; as well as At least one memory, operatively coupled to the at least one processor and storing instructions that perform operations based on execution by the at least one processor, the operations including: A first configuration for first mobility and a second configuration for second mobility are transmitted to the communication device, wherein the second configuration includes i) a cell group configuration for a first cell and ii) a cell group configuration for a second cell; and Receive a notification from the communication device that the cell group configuration for the first cell is not applicable. The communication device is configured to perform operations, the operations including: The first mobility is performed based on the first configuration applied; Detect events related to the second mobility in the first cell; Based on information received from the network, determine whether the node of the first cell used for the second mobility is different from the node of the currently serving cell after the first mobility is performed; and The second mobility to the second cell is performed based on the cell group configuration for the second cell, since the node of the first cell is different from the node of the current serving cell.

17. A method performed by a network node configured to operate in a wireless communication system, the method comprising: A first configuration for first mobility and a second configuration for second mobility are transmitted to the communication device, wherein the second configuration includes i) a cell group configuration for a first cell and ii) a cell group configuration for a second cell; and Receive a notification from the communication device that the cell group configuration for the first cell is not applicable. The communication device is configured to perform operations, the operations including: The first mobility is performed based on the first configuration applied; Detect events related to the second mobility in the first cell; Based on information received from the network, determine whether the node of the first cell used for the second mobility is different from the node of the currently serving cell after the first mobility is performed; and The second mobility to the second cell is performed based on the cell group configuration for the second cell, since the node of the first cell is different from the node of the current serving cell.

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

19. An apparatus adapted to operate in a wireless communication system, the apparatus comprising: At least one processor; as well as At least one memory, operatively coupled to the at least one processor and storing instructions that perform operations based on execution by the at least one processor, the operations including: Receive a first configuration for first mobility and a second configuration for second mobility, wherein the second configuration includes i) a cell group configuration for a first cell and ii) a cell group configuration for a second cell; The first mobility is performed based on the first configuration applied; Detect events related to the second mobility in the first cell; Based on information received from the network, determine whether the node of the first cell used for the second mobility is different from the node of the currently serving cell after the first mobility is performed; and The second mobility to the second cell is performed based on the cell group configuration for the second cell, since the node of the first cell is different from the node of the current serving cell.

20. A non-transitory computer-readable medium (CRM) having program code containing implementation instructions stored thereon, the instructions performing operations based on execution by at least one processor, the operations including: Receive a first configuration for first mobility and a second configuration for second mobility, wherein the second configuration includes i) a cell group configuration for a first cell and ii) a cell group configuration for a second cell; The first mobility is performed based on the first configuration applied; Detect events related to the second mobility in the first cell; Based on information received from the network, determine whether the node of the first cell used for the second mobility is different from the node of the currently serving cell after the first mobility is performed; and The second mobility to the second cell is performed based on the cell group configuration for the second cell, since the node of the first cell is different from the node of the current serving cell.

Images