Medium access control (MAC) reset and / or radio link control (RLC) reset in layer 1 / layer 2 mobility

By introducing LTM cell group and reset group information in the RRC configuration, the mobility process of UE in the cellular network is optimized, the problem of signal quality deterioration and connection interruption in the UE during the movement process is solved, and more efficient signaling processing is achieved and network latency is reduced.

CN119096686APending Publication Date: 2024-12-06APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380013902.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-04-05
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

Prior Art In cellular network coverage, user equipment (UE) has difficulty efficiently switching cells during movement, resulting in signal quality deterioration and connection interruption, and the existing reset process is complex, affecting mobility delay and network delay.

Method used

By introducing LTM cell group and reset group information in the RRC configuration, the UE can determine whether to perform L2 reset based on the configuration information, optimize the mobility process within and between DUs, avoid unnecessary MAC and RLC resets, and improve signaling efficiency.

Benefits of technology

It improves the signal quality and connection stability of the UE during the movement process, reduces mobility delay and network delay, simplifies the cell handover process, and improves the reliability and efficiency of the cellular network.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096686A_ABST
    Figure CN119096686A_ABST
Patent Text Reader

Abstract

The invention relates to devices and components, including apparatuses, systems, and methods for L2 reset. For example, a UE may connect to a base station, DU, via a first cell, and may be configured with information about a second cell. The information may indicate whether an LTM association exists between the first cell and the second cell (e.g., whether the two cells are provided by the same base station DU). In accordance with a command to establish a connection with the second cell (e.g., a MAC CE handover command), the UE may determine whether an L2 reset is to be performed based on configuration information (e.g., when the two cells are provided by the same base station DU, the L2 reset may be abandoned; otherwise, the L2 reset may be performed).
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cellular communications may be defined in various standards to enable communication between user equipment (UE) and a cellular network. For example, the fifth generation mobile network (5G) is a wireless standard that aims to improve data transmission speed, reliability, availability, etc. Cellular coverage is a relevant feature of data transmission. Cellular coverage may also change over time and / or may depend on the mobility of the UE. The UE may be instructed to establish a connection with different cells of the cellular network to maintain cellular coverage. BRIEF DESCRIPTION OF THE DRAWINGS

[0002] Figure 1 An example of a network environment according to some embodiments is shown.

[0003] Figure 2 An example of network coverage based on different base stations and cells provided by such base stations is shown according to some embodiments.

[0004] Figure 3 An example of a process for establishing a connection with a cell according to some embodiments is shown.

[0005] Figure 4 Examples of radio resource control configuration information according to some embodiments are shown.

[0006] Figure 5 Examples of different types of information indicated in an RRC configuration according to some embodiments are shown.

[0007] Figure 6 Another example of different types of information indicated in an RRC configuration according to some embodiments is shown.

[0008] Figure 7 Another example of different types of information indicated in an RRC configuration according to some embodiments is shown.

[0009] Figure 8 Another example of different types of information indicated in an RRC configuration according to some embodiments is shown.

[0010] Fig. 9 Another example of different types of information indicated in an RRC configuration according to some embodiments is shown.

[0011] Fig.10 An example of timing advance reception according to some embodiments is shown.

[0012] Fig.11 An example of an operational flow / algorithm structure implemented by a UE to establish one or more connections with a network according to some embodiments is shown.

[0013] Fig.12An example of an operational flow / algorithm structure implemented by a network to establish one or more connections with a UE according to some embodiments is shown.

[0014] Fig.13 An example of a receiving component according to some embodiments is shown.

[0015] Fig.14 Examples of UEs according to some embodiments are shown.

[0016] Fig.15 An example of a base station according to some embodiments is shown. DETAILED DESCRIPTION

[0017] The following specific embodiments relate to the accompanying drawings. The same figure numbers may be used to identify the same or similar elements in different drawings. In the following description, for the purpose of illustration and not limitation, specific details, such as specific structures, architectures, interfaces, technologies, etc., are set forth to provide a thorough understanding of the various aspects of each embodiment. However, it will be apparent to those skilled in the art who benefit from the present disclosure that the various aspects of each embodiment can be practiced in other examples that deviate from these specific details. In some cases, the description of well-known equipment, circuits, and methods is omitted so that the description of the various embodiments will not be obscured by unnecessary details. For the purposes of this document, the phrase "A or B" refers to (A), (B), or (A and B).

[0018] Typically, when a user equipment (UE) is in network coverage of a network, the UE communicates with the network. Network coverage may be provided via a base station of the network. A base station may include a central unit (CU) and / or one or more distributed units (DUs). A CU may control the operation of a DU that may be partially controlled by the CU. In contrast, a DU may support one or more cells. Depending on network coverage conditions, an intra-DU mobility procedure or an inter-DU mobility procedure may be performed. Intra-DU mobility allows a UE to move from a cell provided by a DU to another cell provided by the same DU. An inter-DU mobility procedure allows a UE to move from a cell provided by a DU to a cell provided by another DU controlled by the same CU.

[0019] As used herein, a layer two (L2) reset refers to at least one of a medium access control (MAC) reset or a radio link control (RLC) reset. Depending on whether the UE's mobility procedure is for an intra-DU situation or an inter-DU situation, an L2 reset may be performed or abandoned. Generally speaking, an L2 reset is performed in an inter-DU situation. In contrast, an L2 reset is abandoned in an intra-DU situation.

[0020] The UE may be configured (e.g., via radio resource control (RRC) signaling) with information about candidate cells (which may be referred to herein as layer one (L1) / L2 triggered mobility (LTM) cells). The UE may also be configured with information about a grouping of such LTM cells. A group includes LTM cells having an LTM association, where the LTM association indicates that the cells are provided by the same DU.

[0021] The UE may have a first connection established with a first cell and may be instructed to establish a second connection with a second cell. For example, the first cell and the second cell are the source cell and the target cell in the handover command, respectively. Based on the group information, the UE may determine whether there is an LTM association between the two cells. If so, the L2 reset may be abandoned because these instructions correspond to the intra-DU mobility procedure. Otherwise, the L2 reset may be performed.

[0022] The following is a glossary of terms that may be used in this disclosure.

[0023] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or a memory (shared, dedicated, or group) configured to provide the described functions, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, a programmable system on chip (SoC)), a digital signal processor (DSP), etc. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functions. The term "circuit" may also refer to a combination of one or more hardware elements and a program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[0024] As used herein, the term "processor circuit" refers to, is part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuit" may refer to an application processor, a baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional processes).

[0025] As used herein, the term "interface circuit" refers to a circuit that enables, is a part of, or includes information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0026] As used herein, the term "user equipment" or "UE" refers to a device that has radio communication capabilities and can describe a remote user of network resources in a communication network. In addition, the term "user equipment" or "UE" may be considered synonymous and may be referred to as a client, device, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface. A UE may have the primary function of communicating with another UE or a network, and a UE may be integrated with other devices and / or systems (e.g., in a vehicle).

[0027] The term "base station" as used herein refers to a device with radio communication functionality, i.e., a device of a communication network (or more simply, a network), and can be configured as an access node in a communication network. Access of a UE to a communication network can be at least partially managed by a base station, whereby the UE connects to the base station to access the communication network. Depending on the radio access technology (RAT), a base station can be referred to as a gNodeB (gNB), an eNodeB (eNB), an access point, etc.

[0028] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to one another and configured to share computing resources or networked resources.

[0029] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a specific device, such as a computer device, a mechanical device, a memory space, a processor / CPU time, a processor / CPU usage, a processor and accelerator load, a hardware time or usage, a power supply, an input / output operation, a port or a network socket, a channel / link allocation, throughput, memory usage, storage, a network, a database and an application, a unit of work, etc. "Hardware resources" may refer to computing, storage or network resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage or network resources provided by a virtualized infrastructure to an application, a device, a system, etc. The term "network resources" or "communication resources" may refer to resources that a computer device / system can access via a communication network. The term "system resources" may refer to any kind of shared entity that provides a service, and may include computing resources or network resources. System resources may be considered as a set of coherent functions, network data objects or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.

[0030] As used herein, the term "channel" refers to any tangible or intangible transmission medium for transmitting data or data streams. The term "channel" may be synonymous or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" or any other similar term representing a path or medium through which data is transmitted. In addition, as used herein, the term "link" refers to a connection made between two devices for transmitting and receiving information.

[0031] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.

[0032] The term "connected" may mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0033] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure for providing wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, networking hardware, network equipment, network node, virtualized network function, etc.

[0034] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains the contents. An information element may include one or more additional information elements.

[0035] Figure 1 A network environment 100 according to some embodiments is shown. The network environment 100 may include a UE 104 and a network node 108. The network node 108 may be a base station that provides a wireless access cell; for example, a third generation partnership project (3GPP) new radio (NR) cell, through which the UE 104 can communicate with the network node 108. The base station may be a component of a terrestrial network. The UE 104 and the network node 108 may communicate via an interface compatible with 3GPP technical specifications, such as those defining the fifth generation (5G) NR system standard.

[0036] The network node 108 may transmit information (e.g., data and control signaling) in the downlink direction by mapping logical channels onto transport channels and then mapping the transport channels onto physical channels. Logical channels may transfer data between the RLC and MAC layers; transport channels may transfer data between the MAC and PHY layers; and physical channels may transfer information across the air interface. Physical channels may include a physical broadcast channel (PBCH); a physical downlink control channel (PDCCH); and a physical downlink shared channel (PDSCH).

[0037] The PBCH may be used to broadcast system information that the UE 104 may use to initially access a serving cell. The PBCH may be transmitted in a synchronization signal (SS) / PBCH block along with a physical synchronization signal (PSS) and a secondary synchronization signal (SSS). The SS / PBCH block (SSB) may be used by the UE 104 during a cell search procedure and for beam selection.

[0038] The PDSCH may be used to transfer end-user application data, Signaling Radio Bearer (SRB) messages, system information messages (in addition to, for example, the MIB), and paging messages.

[0039] The PDCCH may transmit downlink control information (DCI) which is used by a scheduler of the network node 108 to allocate both uplink and downlink resources. The DCI may also be used to provide uplink power control commands, configure the slot format, or indicate that preemption has occurred.

[0040] The network node 108 may also transmit various reference signals to the UE 104. The reference signals may include demodulation reference signals (DMRS) for the PBCH, PDCCH, and PDSCH. The UE 104 may compare the received version of the DMRS with the transmitted known DMRS sequence to estimate the impact of the propagation channel. The UE 104 may then apply the inverse channel of the propagation channel during the demodulation process of the corresponding physical channel transmission.

[0041] Reference signals may also include CSI-RS. CSI-RS may be a multi-purpose downlink transmission that may be used for CSI reporting, beam management, connected mode mobility, radio link failure detection, beam failure detection and recovery, and fine tuning of time and frequency synchronization.

[0042] Reference signals and information from physical channels can be mapped to resources of a resource grid. For a given antenna port, subcarrier spacing configuration, and transmission direction (e.g., downlink or uplink), there is one resource grid. The basic unit of the NR downlink resource grid can be a resource element, which can be defined by one subcarrier in the frequency domain and one orthogonal frequency division multiplexing (OFDM) symbol in the time domain. Twelve consecutive subcarriers in the frequency domain can constitute a physical resource block (PRB). A resource element group (REG) can include one PRB in the frequency domain and one OFDM symbol in the time domain, such as twelve resource elements. A control channel element (CCE) can represent a resource group used to transmit a PDCCH. One CCE can be mapped to multiple REGs; for example, six REGs.

[0043] Transmissions using different antenna ports may experience different radio channels. However, in some cases, different antenna ports may share common radio channel characteristics. For example, different antenna ports may have similar Doppler shift, Doppler spread, average delay, delay spread or spatial reception parameters (e.g., characteristics associated with the angle of arrival of the downlink received signal at the UE). Antenna ports that share one or more of these large-scale radio channel characteristics may be considered to be quasi-co-located (QCL) with each other. 3GPP has specified four types of QCL to indicate which specific channel characteristics are shared. In QCL Type A, antenna ports share Doppler shift, Doppler spread, average delay and delay spread. In QCL Type B, antenna ports share Doppler shift and Doppler spread. In QCL Type C, antenna ports share Doppler shift and average delay. In QCL Type D, antenna ports share spatial receiver parameters.

[0044] The network node 108 may provide transmission configuration indicator (TCI) status information to the UE 104 to indicate the QCL relationship between antenna ports used for reference signals (e.g., synchronization signals / PBCH or CSI-RS) and downlink data or control signaling (e.g., PDSCH or PDCCH). The network node 108 may use a combination of RRC signaling, MAC control element signaling, and DCI to inform the UE 104 of these QCL relationships.

[0045] The UE 104 may use physical uplink channels to transmit data and control information to the network node 108. Different types of physical uplink channels are possible, including a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH), wherein the PUCCH carries control information from the UE 104 to the network node 108, such as uplink control information (UCI), while the PUSCH carries data traffic (e.g., end-user application data) and may carry UCI.

[0046] In one example, communications with the network node 108 and / or base station may use channels in a frequency range 1 (FR1) band (between 40 megahertz (MHz) and 7,125 MHz) and / or a frequency range 2 (FR2) band (between 24,250 MHz and 52,600 MHz), although other frequency ranges are possible (e.g., frequency ranges with frequencies greater than 52,600 MHz). The FR1 band includes licensed bands and unlicensed bands. The NR unlicensed band (NR-U) includes spectrum shared with other types of radio access technologies (RATs) (e.g., LTE-LAA, WiFi, etc.). A listen-before-talk (LBT) process may be used to avoid or minimize conflicts between different RATs in NR-U, whereby a device applies a clear channel assessment (CCA) check before using a channel.

[0047] In one example, the network node 108 is a base station including a CU and / or one or more DUs. In this example, the network coverage provided to the UE 104 may change over time and / or depending on the location of the UE 104. Inter-DU mobility procedures or intra-DU mobility procedures may be performed to support the mobility of the UE 104 and provide appropriate network coverage.

[0048] Specifically, the DU may provide multiple cells (e.g., each cell may be provided via a transmission and reception point (TRP) connected to the DU). In the context of L1 / L2 mobility, such cells may be referred to as LTM cells. The UE 104 may be pre-camped in a serving cell. The base station may configure multiple candidate LTM cells to the UE 104. For example, the base station may configure the candidate LTM cells to the UE 104 using one or more RRC messages.

[0049] In some instances, there may be a connection problem between UE 104 and the serving cell, such as a radio link failure or signal quality degradation. In response to the connection problem, UE 104 may search for a neighboring cell to establish a connection with another cell from a candidate cell group. The candidate cells may include some or all of the cells in the candidate LTM cells. In some cases, the candidate LTM cells may have a higher priority than the candidate non-LTM cells. In the instance where UE 104 chooses to establish a connection with a candidate LTM cell, the process is different from the case where UE 104 chooses to establish a connection with a candidate cell that is not an LTM cell.

[0050] If UE 104 determines that the candidate LTM cell includes appropriate criteria, the base station's DU may transmit a Medium Access Control - Control Element (MAC CE) message to trigger LTM handover to UE 104. UE 104 may initiate an RRC message to establish a connection with the target LTM cell.

[0051] Examples of LTM cells and related configuration information are described in the following figures.

[0052] Figure 2 An example of network coverage based on different base stations and cells provided by such base stations according to some embodiments is shown. The network may include base stations and may communicate with UE 204 (which is an example of UE 204) via one or more of such base stations (each base station is an example of network node 108). The base station may include a CU and / or one or more DUs. In some embodiments, the base station may be a gNB, an eNB, etc. Figure 2 In the examples of FIG. 1 , each base station is shown as a gNB. In such examples, the CU of a base station may be referred to as a gNB-CU, and the DU of a base station may be referred to as a gNB-DU.

[0053] For illustrative purposes, Figure 2 A gNB-DU 210, a gNB-CU 220, a gNB-DU 230, and a g-NBCU 240 are shown. The gNB-DUs 210 and 230 are connected to the gNB-CU 220. Operations of the two gNB-DUs 210 and 230 may be controlled in part by the gNB-CU 220. The gNB-CU 220 may terminate an F1 interface connected to each of the first gNB-DU 210 and the second gNB-DU 230. Each of the first gNB-DU 210 and the second gNB-DU 230 may terminate an F1 interface connected to the gNB-CU 220.

[0054] The gNB-CU 220 may be a logical node for hosting at least one of the RRC, Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of a base station. The gNB-CU 240 may be a logical node for hosting at least one of the RRC, SDAP, and PDCP protocols of another base station.

[0055] Each of the first gNB-DU 210 and the second gNB-DU 230 may be a logical node hosting at least one of the RLC, MAC, and physical (PHY) layers of the base station. Each of the first gNB-DU 210 and the second gNB-DU 230 may provide or support one or more cells. One cell is supported by only one DU. For example, the first gNB-DU 210 may provide cells 212 (having a physical cell ID “0” shown as PCI0), 214 (having a physical cell ID “1” shown as PCI1), and 216 (having a physical cell ID “3” shown as PCI3). Each cell may be provided by a TRP connected to the gNB-CU 210. Similarly, the second gNB-DU 230 may provide cells 232 (having a physical cell ID “4” shown as PCI4), 234 (having a physical cell ID “5” shown as PCI5), and 236 (having a physical cell ID “6” shown as PCI6). Each cell may be provided by a TRP. As used herein, a cell may refer to components of a TRP and / or a base station, wherein these components enable communication with a UE.

[0056] The gNB-CU 240 may also provide or support one or more cells. For example, the gNB-CU 240 may provide cell 2242 (having a physical cell ID "7" shown as PCI7) and cell 244 (having a physical cell ID "8" shown as PCI8).

[0057] It should be understood that the number of UEs, CUs and / or DUs is for illustrative purposes only and does not imply any limitation to the present disclosure. A network may include any suitable number of UEs, CUs and DUs suitable for implementing the present disclosure.

[0058] Communications in the network may conform to any suitable standard, including but not limited to Global System for Mobile Communications (GSM), Long Term Evolution (LTE), LTE-Evolution, LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSMEDGE Radio Access Network (GERAN), Machine Type Communications (MTC), etc.

[0059] In addition, communication may be performed according to any generation of communication protocols currently known or to be developed in the future. Examples of communication protocols include, but are not limited to, first generation (1G) communication protocols, second generation (2G) communication protocols, 2.5G communication protocols, 2.75G communication protocols, third generation (3G) communication protocols, fourth generation (4G) communication protocols, 4.5G communication protocols, and fifth generation (5G) communication protocols.

[0060] The UE 204 may access one cell provided by the first gNB-DU 210. For example, the UE 204 may initially connect to the cell 216 provided by the first gNB-DU 210. Based on the measurement, the UE 204 may perform an intra-DU mobility procedure to move from the cell 216 to another cell provided by the first gNB-DU 210. For example, the UE 204 may perform an intra-DU mobility procedure to move from the cell 216 to one of the cells 212 or 214. Hereinafter, the intra-DU mobility is also referred to as intra-gNB-DU mobility.

[0061] Alternatively, based on the measurement, the UE 204 may perform an inter-DU mobility procedure to move from a cell provided by the first gNB-DU 210 to a cell provided by the second gNB-DU 220. For example, the UE 204 may perform an inter-DU mobility procedure to move from the cell 216 provided by the first gNB-DU 210 to one of the cells 232, 234, or 236 provided by the second gNB-DU 230. Hereinafter, inter-DU mobility is also referred to as inter-gNB-DU mobility.

[0062] In some embodiments, UE 204 may be in dual connectivity (DC) with gNB-CU 220 and 240. When gNB-CU 220 is configured as a secondary node (SN) and gNB-CU 240 is configured as a master node (MN) in a DC configuration, intra-DU mobility procedures and inter-DU mobility procedures may be allowed.

[0063] For illustrative purposes, assume that UE 204 is in connected mode with PCI3 (e.g., cell 216 is the current serving cell). The network should be able to configure L2 mobility with PCI0 and / or PCI1 as intra-DU mobility and / or configure L2 mobility with PCI4, PCI5, and / or PCI6 as inter-DU mobility. There are differences between intra-DU mobility and inter-DU mobility. For example, a MAC reset and / or RLC reset may be required for inter-DU mobility, but a MAC reset and / or RLC reset may be avoided in the intra-DU case. Specifically, consider the case where UE 204 has received multiple packets via the serving cell before switching and has indicated to the gNB-DU 210 (e.g., via a hybrid automatic repeat request (HARQ) process) the erroneous packets that need to be retransmitted. If the switch is to intra-cell (e.g., either PCI0 or PCI1), the gNB-DU 210 can retransmit the erroneous packets without requiring either a MAC reset or an RLC reset. If switching to an inter-cell (e.g., any one of PCI 4, PCI 5, or PCI 6), the gNB-DU 240 may receive relevant information from the gNB-DU 210 via the gNB-CU 220 so that the gNB-DU 240 may retransmit the erroneous packet to the UE 204. Nevertheless, in order to improve network latency, one or both of a MAC reset or an RLC reset may be performed by the UE 204. Specifically, the gNB-DU 240 does not need to receive HARQ related information from the gNB-DU 210 via the gNB-CU 220. In the case where both resets are performed, the UE 204 may discard received packets (including correctly detected packets) and may expect to receive all packets again from the gNB-DU 230 after the switch. A similar situation may exist when switching to a cell of the gNB-CU 240, whereby both a MAC reset and an RLC reset are performed here.

[0064] Figure 3An example of a process for establishing a connection with a cell according to some embodiments is shown. The process can be implemented by a UE 310 (an example of a UE 204) and a network 320 (such as the network described herein above) including base stations CU and DU. Generally speaking, the UE 310 receives configuration information for one or more candidate cell groups for intra-DU mobility and / or for one or more candidate cell groups for inter-DU mobility from the network 320 (e.g., its gNB-CU). The configuration information may be received via RRC signaling. Subsequently, the UE 310 may be instructed to establish one or more connections (e.g., via a MAC handover command). Here, based on the source cell and the target cell, the UE 310 may determine whether there is an LTM association between the two cells (as indicated in the configuration information), and if so, determine whether to perform or abandon an L2 reset, which is associated with establishing a connection to the target cell. Figure 3 The method is shown in the context of an RRC reconnection procedure.

[0065] In the exemplary illustration, the UE 310 receives an RRCReconfiguration message from the network 320 (or multiple messages of such messages from, for example, a gNB-CU). The received RRC reconfiguration information particularly indicates the configuration of candidate cells including LTM candidate cells. The configuration for the candidate LTM cells may be referred to herein as the LTM candidate cell configuration. In addition, the received RRC reconfiguration information indicates the configuration for the LTM cell group (e.g., each group represents a cell group with an LTM association, which LTM association may allow the UE to abandon performing at least one of a MAC reset or an RLC reset). The configuration for the LTM cell group may be referred to herein as the LTM group configuration. The LTM group configuration may be separate from the LTM cell configuration and may be indexed in the LTM cell configuration. The UE 310 may respond to the network 320 (e.g., responding to the gNB-CU) with an RRCReconfigurationComplete message (or multiple messages of such messages). Next, the UE 310 may receive a connection command (e.g., a MAC CE for handover for LTM handover) from the network 320 (e.g., from a gNB-CU or gNB-DU of a serving cell in which the UE 310 is camped). Based on the source cell and the target cell, the UE 310 may determine from the LTM cell configuration information and / or the LTM group configuration information whether there is an LTM association between the two cells and whether a MAC reset and / or an RLC reset will be performed. The UE 310 may then establish a connection with the TRP providing the target cell by performing a handover based on the determination. When the target cell has an LTM association with the source cell (e.g., belongs to a candidate cell group for intra-DU mobility), the UE 310 may perform a handover to the target cell by performing an intra-DU mobility procedure, and an L2 reset may be avoided. In contrast, when the target cell has no LTM association with the source cell (e.g., belongs to a candidate cell group for inter-DU mobility), the UE 310 may perform a handover to the target cell by performing an inter-DU mobility procedure that may include an L2 reset.

[0066] In this exemplary illustration, mobility delays can be reduced because the cell and group configuration is provided to the UE 310 prior to handover. In addition, mobility delays can be further reduced by forgoing the need to perform an L2 reset when appropriate (e.g., during intra-DU handover).

[0067] Therefore, according to Figure 3, UE 310 is preconfigured with multiple L2 reset groups (e.g., LTM cell groups). Under the LTM handover command (e.g., using a MAC CE from the network 320), if the target LTM cell (given in a MAC CE that may indicate the target cell) is part of the same group as the source LTM cell, then no L2 reset may be performed, or based on the configuration within the group, UE 310 may only perform the configured: MAC reset only or RLC reset only. Otherwise, the target LTM cell is not part of the same group as the source LTM cell. In this case, the UE performs an L2 reset (MAC reset and RLC reset).

[0068] Figure 4 An example of RRC configuration information according to some embodiments is shown. The RRC configuration information may be received from a base station CU and may in particular indicate an LTM cell configuration for a candidate LTM cell and separately indicate an LTM cell group configuration (e.g., by indicating that the cells belonging to the group are LTM cells, provided by the same base station DU).

[0069] exist Figure 4 In the exemplary illustration of , the RRC configuration information indicates an RRCReconfiguration 410 that may be received from a gNB-CU (e.g., gNB-CU 220) of a base station. The RRCReconfiguration 410 may include a primary cell group (MCG) configuration 412 and a secondary cell group (SCG) configuration 414. The RRCReconfiguration 410 also includes an LTM configuration 420.

[0070] LTM configuration 420 indicates the configuration of “k” candidate cells provided by the gNB-CU. Some of these candidate cells are provided by the same gNB-DU of the base station, while other candidate cells are provided by different gNB-DUs of the base station. These cells are candidate LTM cells. Return to reference Figure 2 , gNB-CU 220 is connected to gNB-DUs 210 and 230, which in turn provide PCI0, PCI1, PCI3, PCI4, PCI5, and PCI6. Therefore, "k" here is six (where PCI2 is not part of the provided cell). Therefore, LTM configuration 420 indicates six LTM cell configurations 422, each of which corresponds to PCI0 (e.g., candidate LTM cell 212), PCI1 (e.g., candidate LTM cell 214), PCI3 (e.g., candidate LTM cell 216), PCI4 (e.g., candidate LTM cell 232), PCI5 (e.g., candidate LTM cell 234), and PCI6 (e.g., candidate LTM cell 236).

[0071] In addition, the LTM configuration 420 indicates an L2 reset LTM group configuration 424. In the example, the L2 reset LTM group configuration 424 is indicated separately from the LTM cell configuration 422 (e.g., not a part of the LTM cell configuration 422). Generally speaking, the L2 reset LTM group configuration 424 includes information indicating whether two or more candidate LTM cells belong to the same cell group (e.g., are intra-DU cells provided by the same DU) or belong to different cell groups (e.g., are inter-DU cells provided by different DUs). Return to Reference Figure 2 , the L2 reset LTM group configuration 424 indicates that a first LTM association exists between PCI0 (e.g., candidate LTM cell 212), PCI1 (e.g., candidate LTM cell 214), and PCI3 (e.g., candidate LTM cell 216), so that any handover from a source cell belonging to the first group of candidate LTM cells to a target cell can follow an intra-DU handover procedure, which can skip a portion or all of the L2 reset. In addition, the L2 reset LTM group configuration 424 indicates that a second LTM association exists between PCI4 (e.g., candidate LTM cell 232), PCI5 (e.g., candidate LTM cell 234), and PCI6 (e.g., candidate LTM cell 236), so that any handover from a source cell belonging to the second group of candidate LTM cells to a target cell can follow an intra-DU handover procedure, which can skip a portion or all of the L2 reset. In contrast, the L2 reset LTM group configuration 424 indicates that there is no LTM association between any cell of the first group and any cell from the second group, so that any switch from a source cell of the first group (or the second group) to a target cell of the second group (or the first group) can follow the inter-DU switching process, which may not skip at least part or all of the L2 reset.

[0072] like Figure 4As further shown in FIG. 4 , at least a portion of the L2 reset LTM group configuration 424 may overflow into each candidate LTM cell configuration. Specifically, the first LTM cell configuration in the LTM cell configuration 422 corresponds to the first LTM cell (e.g., PCI0), the second LTM cell configuration in the LTM cell configuration 422 corresponds to the second LTM cell (e.g., PCI1), and so on, until the kth LTM cell configuration in the LTM cell configuration 422 corresponds to the kth LTM cell (e.g., PCI6). The first LTM cell (e.g., PCI0) may have a first RRC configuration 430 that includes a reference configuration 432 (e.g., a configuration specific to the candidate LTM cell) and a Delta configuration 434 (e.g., a configuration that indexes the LTM cell group to which the candidate LTM cell belongs and / or a specific portion of the L2 reset LTM group configuration 424 applicable to the candidate LTM cell). Similarly, the second LTM cell (e.g., PCI1) can have a second RRC configuration 440 that includes a reference configuration 442 (e.g., a configuration specific to the candidate LTM cell) and a Delta configuration 444 (e.g., a configuration that indexes the LTM cell group to which the candidate LTM cell belongs and / or a specific portion of the L2 reset LTM group configuration 424 applicable to the candidate LTM cell). Additionally or alternatively, the kth LTM cell (e.g., PCI6) can have a kth RRC configuration 450 that includes a reference configuration 452 (e.g., a configuration specific to the candidate LTM cell) and a Delta configuration 454 (e.g., a configuration that indexes the LTM cell group to which the candidate LTM cell belongs and / or a specific portion of the L2 reset LTM group configuration 424 applicable to the candidate LTM cell). These and other configuration variations are further illustrated in the following figures.

[0073] Figure 5 An example of different types of information indicated in an RRC configuration according to some embodiments is shown. Specifically, an RRC configuration (e.g., RRCReconfiguration 410) includes two types of information: LTM group information 510 (e.g., a configuration of a candidate LTM cell group, such as one or more of the L2 reset LTM group configuration 424) and candidate cell information 520 (e.g., information about candidate LTM cells belonging to the LTM cell group). LTM group information 510 may not be part of the configuration of a candidate LTM cell (e.g., may not be included in LTM cell configuration 422).

[0074] In one example, LTM group information 510 corresponds to an explicit group configuration indicated by explicit signaling of the group (e.g., via RRC). Each group is signaled a corresponding LTM association of an LTM cell. Different options may be used for LTM association. A first option includes using a candidate configuration identifier of a candidate LTM cell (e.g., an identifier that uniquely identifies a particular configuration from LTM cell configuration 424). A second option includes using a physical cell identifier (PCI) and an associated absolute radio frequency channel number (ARFCN) of a candidate LTM cell. In this example, for each group, LTM group information 510 includes an identifier of the group. For cells belonging to the group, candidate cell information 520 includes one or more candidate configuration identifiers, and / or PCI and ARFCN for such cells.

[0075] Return to reference Figure 2 And using the candidate configuration identifier, group information 510 may be set to: {group information ID: 1; candidate configuration ID: ID0, ID1, ID3}, which corresponds to the group formed by LTM cells 212, 214, and 216; {group information ID: 2; candidate configuration ID: ID4, ID5, ID6}, which corresponds to the group formed by LTM cells 222, 224, and 226; and {group information ID: 3; candidate configuration ID: ID7, ID8}, which corresponds to the group formed by LTM cells 242 and 244. In this example, “group information ID” may be listed in group information 510, and “candidate configuration ID” may be listed in candidate cell information 520.

[0076] In the context of a 5G NR system, the following information may be defined in the technical specification to obtain the above-mentioned method for explicit group configuration.

[0077]

[0078]

[0079] like Figure 5 As further shown, the LTM group information 510 may optionally include reset information 530. In the absence of reset information 530 explicitly included in the LTM group information 510, if the LTM group information 510 does not indicate that the target cell has an LTM association with the source cell (e.g., as part of the same group), the UE may determine that an L2 reset will be performed when establishing a connection with the target cell. Otherwise, an L2 reset may not be performed.

[0080] In contrast, when reset information 530 is included in LTM group information 510, reset information 530 may explicitly indicate whether an L2 reset is to be performed. Furthermore, the indication may be refined to the granularity of the possible L2 reset types (e.g., MAC reset, RLC reset, or any other type of L2 reset). Thus, information group 510 may include the details of the L2 reset.

[0081] Return to reference Figure 2 And using the candidate configuration identifier, the group information 510 can be set to: {Group information ID: 1; Candidate configuration ID: ID0, ID1, ID3; Intra-DU L2 reset: MAC=false, RLC=false}, which corresponds to the group formed by LTM cells 212, 214 and 216; {Group information ID: 2; Candidate configuration ID: ID4, ID5, ID6; Intra-DU L2 reset: MAC=false, RLC=false}, which corresponds to the group formed by LTM cells 222, 224 and 226; {Group information ID: 3; Candidate configuration ID: ID7, ID8; L2 reset: MAC=true, RLC=false} and {Inter-DU L2 reset=L2 reset: MAC=true, RLC=true}, which corresponds to the group formed by LTM cells 242 and 244. In this example, “Group Information ID” may be listed in the group information 510 , while “Candidate Configuration ID” may be listed in the candidate cell information 520 , and “Intra-DU / Inter-DU L2 Reset” may be listed in the reset information 530 .

[0082] In the context of a 5G NR system, the following information may be defined in the technical specification to obtain the above-mentioned method for explicit group configuration including explicit reset information.

[0083]

[0084]

[0085] Figure 6 Another example of different types of information indicated in an RRC configuration according to some embodiments is shown. Specifically, an RRC configuration (e.g., RRCReconfiguration 410) includes two types of information: candidate cell configuration information 610 (e.g., information about the configuration of each candidate LTM cell, such as LTM cell configuration 424) and LTM group reference information 620 (e.g., a reference to a candidate LTM cell group or a configuration for the group (such as one or more configurations in L2 reset LTM group configuration 424)). The LTM group configuration itself may not be part of the candidate cell configuration information 610 (e.g., may not be included in the LTM cell configuration 422).

[0086] In one example, each LTM candidate configuration is included in the candidate cell configuration information 610, which corresponds to the LTM cell and includes an index to the LTM cell group to which the LTM cell belongs. In this example, the UE determines the current group to which its serving cell belongs, the group to which the target cell belongs (which may be the same as the current group) based on the LTM group index information 620, and may look up the LTM group information 630 (which may correspond to the L2 reset LTM group configuration 424 and / or the LTM group information 510) to determine whether an L2 reset is required. Specifically, the LTM group information 630 may indicate whether an LTM association exists (e.g., in the case of determining the same group) or not (e.g., in the case of determining different groups), and / or may include an explicit indication of the type of L2 reset to be performed or avoided.

[0087] Return to reference Figure 2 And using the candidate configuration identifier, the candidate cell configuration information 610 can be set as: {LTM configuration; group information ID: 1, 2, 3; LTM candidate 0: LTM configuration as RRCReconfiguration, candidate group ID: 1; LTM candidate 3: LTM configuration as RRCReconfiguration, candidate group ID: 1; LTM candidate 4: LTM configuration as RRCReconfiguration, candidate group ID: 2}. "LTM configuration" and "group information ID" can be listed in the candidate cell configuration information 610, and "LTM candidates" can be listed in the LTM group indexing information 620. In this example, for LTM cell 212 (e.g., PCI0), the cell has an LTM configuration indicated by RRCconfiguraiton and belongs to the first group "1". The same is true for LTM cell 216 (e.g., PCI3). In contrast, LTM cell 232 (e.g., PCI4) has an LTM configuration indicated by RRCconfiguraiton and belongs to the first group "2". Therefore, the UE may determine that LTM cells 212 and 216 have LTM associations in the same first group, while LTM cell 232 has no LTM association with LTM cells 212 and 216 but may be associated with other LTM cells in the second group. LTM group information 630 may indicate L2 reset details for both groups.

[0088] In the context of a 5G NR system, the following information may be defined in the technical specification to obtain the above-mentioned method for explicit group configuration.

[0089]

[0090]

[0091] In the above examples, the grouping of LTM cells is based on linking. Specifically, each LTM cell has an LTM cell configuration that includes an index to the group to which the LTM cell belongs. In addition, in the above examples, the linking is explicit, where the index to the group is included in the LTM cell configuration as independent information (e.g., the LTM group indexing information 620 is included in the candidate cell configuration information 610 but is separate from the candidate cell configuration information). However, other examples are also possible, where the linking can be implicit. For example, the index to the group does not need to be separated from the LTM cell configuration, but can be embedded in the configuration.

[0092] Return to reference Figure 2 And using the candidate configuration identifier, an implicit link can be defined by setting the candidate cell configuration information 610 to: {LTM configuration; group information ID: 1, 2, 3; LTM candidate 0: LTM configuration as RRCReconfiguration; LTM candidate 3: LTM configuration as RRCReconfiguration; LTM candidate 4: LTM configuration as RRCReconfiguration}. "LTM configuration" and "group information ID" can be listed in the candidate cell configuration information 610. The RRCReconfiguration of each of these cells can embed the corresponding candidate group identifier (for example, "Candidate Group ID: 1" is included in the RRCReconfiguration of LTM cell 212 (e.g., PCI0) and LTM cell 216 (e.g., PCI3), and "Candidate Group ID: 2" is included in the RRCReconfiguration of LTM cell 232 (e.g., PCI4)).

[0093] In the context of a 5G NR system, the following information may be defined in the technical specification to obtain the above-mentioned method for implicit linking.

[0094]

[0095]

[0096]

[0097] Figure 7Another example of different types of information indicated in an RRC configuration according to some embodiments is shown. In this example, the RRC configuration indicates default LTM group information 710 and other LTM group information 720. The default LTM group information 710 corresponds to the configuration of the default LTM group. The other LTM group information 720 corresponds to one or more configurations of one or more other LTM groups. If an LTM cell is not explicitly indicated as belonging to any of the other LTM groups, the UE may assume that the LTM cell belongs to the default group. The explicit indication may follow Figure 5 method (e.g., an identifier of the LTM cell configuration and / or a PCI of the LTM cell is included in the configuration of the LTM group) or Figure 6 method (e.g., by using links in an LTM cell configuration). Figure 7 The former method is further described in Figure 8 The latter method is shown in .

[0098] In practice (and usually), the configuration is such that the current DU has many serving TRPs, while TRPs / cells near the current DU will be linked via CUs (e.g., corresponding inter-DU TRPs / cells). Therefore, multiple PCIs can be part of a serving DU, while the number of inter-DU PCIs is relatively small. Return to reference Figure 2 , this is illustrated by considering an example where the serving DU is gNB-DU 210. In this example, UE 204 is connected at PCI3 and is near a TRP with PCI0, PCI1, PCI3, and PCI4. Therefore, an intra-DU handover may have two cells corresponding to PCI0 and PCI1, while an inter-DU handover may have one cell corresponding to PCI4 (the other cells corresponding to PCI5 and PCI6 are not near the UE, so that they can be considered candidate cells). Therefore, the number of intra-DU cells is greater than the number of inter-DU cells.

[0099] Thus, all LTM candidate cells may be considered to belong to the same DU group (eg, the default LTM group) unless explicitly signaled otherwise (eg, the absence of group information will be interpreted as being part of the default / same group).

[0100] Return to reference Figure 2And using the candidate configuration identifier, the default grouping may be defined by setting the default LTM group information 710 to: {Group information ID: 1}. No LTM cell configuration identifier is explicitly signaled in the default LTM group information 710. In contrast, other LTM group information 7120 may be set to: {Group information ID: 2; Candidate configuration IDs: ID4, ID5, ID6}, which corresponds to the group formed by the LTM cells 222, 224, and 226; and {Group information ID: 3; Candidate configuration IDs: ID7, ID8}, which corresponds to the group formed by the LTM cells 242 and 244. In this example, because the identifiers of the LTM cell configurations of the cells 212 and 214 are not explicitly indicated in any of the groups, these cells 212 and 214 are assumed to belong to the default group (e.g., “Group information ID: 1”).

[0101] Figure 8 Another example of different types of information indicated in an RRC configuration according to some embodiments is shown. Here, the RRC configuration indicates a link between an LTM cell configuration and an LTM group. If the link is omitted from the LTM cell configuration, the corresponding cell is assumed to belong to a default group.

[0102] As shown, the RRC configuration indicates default LTM group information 810 and other LTM group information 820. The default LTM group information 810 then corresponds to the configuration of the default LTM group, while the other LTM group information 820 corresponds to one or more configurations of one or more other LTM groups. In addition, the RRC configuration indicates candidate cell configuration information 830. The candidate cell configuration information 830 then indicates the configuration of each candidate cell and may include a candidate group indication 840 (separately or embedded in the configuration). As shown in the dashed box, the candidate group indication 840 may or may not exist. If present, the candidate group indication 840 may be a reference to any of the other LTM groups (e.g., by being an identifier of the group or an identifier of the configuration of the group). The absence of the candidate group indication 840 may be an implicit link to the default LTM group.

[0103] Return to reference Figure 2And using the candidate configuration identifier, the candidate group indication 840 can be defined by: setting the candidate cell configuration information 830 to: {LTM configuration; group information ID: 1, 2, 3; LTM candidate 0: LTMconfig as RRCReconfiguration; LTM candidate 3: LTMconfig as RRCReconfiguration; LTM candidate 4: LTMconfig as RRCReconfiguration, candidate group ID: 2}. Here, the default LTM group has "Group Information ID: 1". The LTM cell configuration of cell 212 is defined in "LTM candidate 0", but does not include a reference to any LTM group. Therefore, the cell 212 is assumed to belong to the default group "Group Information ID: 1". Similarly, the LTM cell configuration of cell 216 is defined in "LTM candidate 3", but does not include a reference to any LTM group. Therefore, the cell 216 is assumed to belong to the default group "Group Information ID: 1".

[0104] Fig. 9 Another example of different types of information indicated in an RRC configuration according to some embodiments is shown. In this example, the RRC configuration indicates a bitmap 900, wherein each bit value in the bitmap 900 corresponds to a pair of source cells and target cells, and indicates whether the two cells have an LTM association. One or more bits can be used to set the bit value. If a single bit is used, the bit can be set to "1" to indicate an LTM association, whereby the UE can abandon performing an L2 reset (e.g., as part of a handover from a source cell to a target cell). Conversely, the bit can be set to "0" to indicate that an L2 reset is required (e.g., when the two cells are not associated with an LTM as part of the same DU). If multiple bits are used, a more fine-grained indication of the L2 reset type becomes possible. For example, the first bit can be set to indicate whether a MAC CE will be performed, and the second bit can be set to indicate whether an RLC CE will be performed. Alternatively, multiple bitmaps (each of which is similar to bitmap 900) can be used, wherein each bitmap corresponds to an L2 reset type (e.g., one bitmap corresponds to a MAC reset and another bitmap corresponds to an RLC reset).

[0105] exist Fig. 9 In the exemplary illustration of , the bitmap 900 can be considered as a two-dimensional bit string (eg, a table). The rows of the bitmap 900 correspond to the source cell identifiers 910, and the columns of the bitmap 900 correspond to the target cell identifiers 910. Return to Reference Figure 2, the first row may correspond to PCI0, while the third and fourth columns may correspond to PCI3 and PCI4, respectively. In this example, the bit value of the intersection between the first row and the third column may be set to indicate that PCI0 and PCI3 are part of the same LTM group and therefore an L2 reset may be foregone. In contrast, the bit value of the intersection between the first row and the fourth column may be set to indicate that PCI0 and PCI4 are part of different LTM groups and therefore an L2 reset should be performed.

[0106] The above bitmap 900 is an example of a two-dimensional bit string. Other forms of bit strings are also possible. For example, the network may only provide a bit string of length<maxLTMCandidates×maxLTMCandidates> The UE simply checks<srcConfigID×maxLTMCandidates+targetConfigID> The corresponding bit of the position in the bit string determines the L2 reset information. If the bit is "1", L2 reset is required. If the bit is "0", L2 reset is not required. In this way, the network can hide the group logic and intra-DU / inter-DU differences from the UE. Since there is no group level information, the data structure is also simpler. If the source and target LTM candidates are in the same LTM group, the value will be "0". For L2 reset granularity indicating the need for MAC reset and / or RLC reset respectively, two such bit strings can be used, one of which corresponds to MAC reset and the other corresponds to RLC reset.

[0107] In another example, the network configures a single "L2 reset distance" threshold for L2 reset. The threshold distance (which can be a positive integer) can be included in the RRC configuration. The UE can implement logic to determine whether an L2 reset is required based on the difference between the configuration identifier of the source cell and the configuration identifier of the target cell and how the difference compares to the threshold distance. If it is equal to or less than the threshold distance, then there will be no need to perform an L2 reset. If it is greater than the threshold distance, then an L2 reset should be performed. Thus, the UE's logic can be implemented as "if abs(SrcConfigID-TargetConfigID)≤L2ResetDistance, then there is no L2 reset; otherwise, there is an L2 reset." Knowing this threshold, the network can carefully assign "configuration IDs" to ensure that the candidate configuration IDs for PCIs under different DUs are sufficiently separated (e.g., greater than the threshold).

[0108] Fig.10An example of timing advance reception according to some embodiments is shown. As shown, the gNB-DU 1010 (or more generally, the base station DU) provides a source LTM cell 1012 (e.g., via a first TRP) and a target LTM cell 1014 (via a second TRP). The UE 1004 may connect to the gNB-DU 1010 via the source LTM cell 1012 (e.g., the source LTM cell 1012 is the current serving cell). The UE 1004 may then establish a second connection with the gNB-DU 1010 via the target LTM cell 1014 (e.g., in response to a MAC CE handover command).

[0109] As part of establishing the connection, the UE 1004 may send a random access channel (RACH) message 1020 via the target LTM cell 1014 for different purposes. For example, the RACH message may be used for timing advance (TA) acquisition. Because the target LTM cell 1014 and the source LTM cell 1012 have an LTM association by being provided by the same gNB-DU 1010, TA information (e.g., a TA value) may be sent by the gNB-DU in a random access response (RAR) 1030 via the source LTM cell 1012 instead of the target LTM cell 1014. Additionally or alternatively, the TA value may be sent by the gNB-DU via the source LTM using a message other than the RAR (e.g., another MACCE). This approach may improve communication efficiency. However, if there is no LTM association between the target cell and the source cell (such as when the two cells are not provided by the same base station DU), the RAR response is sent via the target cell.

[0110] According to an embodiment of the present disclosure, because a means is provided for UE 1004 to know whether the target LTM candidate cell is part of the same DU, it is possible to determine whether the candidate LTM cell for which UE 1004 has a RACH is part of the current serving DU. If the target LTM cell on which UE 1004 has a RACH for TA acquisition is part of the same DU as the source LTM cell, UE 1004 can assume that the RAR is provided on the source LTM cell itself. This assumption can be made without any configuration of the UE 1004 by the network (e.g., by being predefined in the technical specifications). Alternatively, the network can configure (e.g., via RRC signaling) UE 1004 to assume such an association, so that the RAR reception for TA acquisition at the UE is based on the group configuration for L2 reset.

[0111] Fig.11 An example of an operational flow / algorithm structure 1100 implemented by a UE to establish one or more connections with a network according to some embodiments is shown. The UE is an example of any of the UEs described in this disclosure.

[0112] The operation flow / algorithm structure 1100 may include: at 1102, receiving first configuration information and second configuration information, wherein the first configuration information indicates a configuration of each cell in a plurality of cells, and wherein the second configuration information is separate from the first configuration information and indicates a layer 1 / layer 2 triggered mobility (LTM) association between two or more cells in the plurality of cells. For example, the first configuration includes an LTM cell configuration for each cell in the plurality of cells, and the first configuration is received from a base station CU via RRC signaling. The second configuration includes an LTM group configuration for each LTM cell group provided by the same base station DU, and the second configuration is received from the base station CU via RRC signaling.

[0113] The operation flow / algorithm structure 1100 may include: at 1104, establishing a first connection with a first cell among the multiple cells, wherein the first connection is associated with medium access control (MAC) and radio link control (RLC) information. For example, the first cell is a serving cell, and the first connection is established according to an RRC connection procedure or an RRC reconnection procedure.

[0114] The operation flow / algorithm structure 1100 may include receiving a command to establish a second connection with a second cell in the plurality of cells at 1106. For example, the second cell is a target cell, and the command is a MAC CE handover command indicating the target cell.

[0115] The operation flow / algorithm structure 1100 may include: at 1108, determining whether at least one of a MAC reset or an RLC reset is to be performed based on the second configuration information. For example, the UE may determine whether the target cell and the serving cell belong to the same LTM group (e.g., provided by the same base station DU) by using at least the second configuration information. If so, the UE may determine that an L2 reset is not required. Otherwise, the UE may determine that an L2 reset is required and the type of the reset (e.g., only a MAC reset, only an RLC reset, or both a MAC reset and an RLC reset).

[0116] The operation flow / algorithm structure 1100 may include: at 1110, establishing the second connection based on the determination. For example, if L2 reset is not required, the UE establishes the second connection without removing the existing L2 information. Otherwise, if MAC reset and / or RLC reset, the UE may remove the relevant L2 information.

[0117] Fig.12 An example of an operational flow / algorithm structure 1200 implemented by a network to establish one or more connections with a UE according to some embodiments is shown. The network is an example of any of the networks described in this disclosure.

[0118] The operation flow / algorithm structure 1200 may include: at 1202, sending first configuration information and second configuration information to a user equipment (UE), wherein the first configuration information indicates a configuration of each cell in a plurality of cells, and wherein the second configuration information is separate from the first configuration information and indicates a layer 1 / layer 2 triggered mobility (LTM) association between two or more cells in the plurality of cells. For example, the first configuration includes an LTM cell configuration for each cell in the plurality of cells, and the first configuration is sent from a base station CU via RRC signaling. The second configuration includes an LTM group configuration for each LTM cell group provided by the same base station DU, and the second configuration is sent from the base station CU via RRC signaling.

[0119] The operation flow / algorithm structure 1200 may include: at 1204, establishing a first connection with the UE via a first cell among the multiple cells, wherein the first connection is associated with medium access control (MAC) and radio link control (RLC) information. For example, the first cell is a serving cell, and the first connection is established according to an RRC connection procedure or an RRC reconnection procedure.

[0120] The operation flow / algorithm structure 1200 may include: at 1206, sending a command to the UE to establish a second connection with a second cell among the multiple cells. For example, the second cell is a target cell, and the command is a MAC CE switching command indicating the target cell.

[0121] The operation flow / algorithm structure 1200 may include: at 1208, establishing the second connection based on the first configuration information and the second configuration information. For example, the UE may determine whether the target cell and the serving cell belong to the same LTM group (e.g., provided by the same base station DU) by using at least the second configuration information. If so, the UE may determine that an L2 reset is not required. Otherwise, the UE may determine that an L2 reset is required and the type of the reset (e.g., only a MAC reset, only an RLC reset, or both a MAC reset and an RLC reset). If an L2 reset is not required, the second connection does not remove the existing L2 information. Otherwise, if the MAC is reset and / or the RLC is reset, the relevant L2 information may remove the relevant L2 information, and the base station CU may resend such information to the UE via the target cell.

[0122] Fig.13 A receiving component 1300, such as a UE or a base station, is shown according to some embodiments. The receiving component 1300 may include an antenna panel 1304 including a plurality of antenna elements. The panel 1304 is shown with four antenna elements, but other embodiments may include other numbers of antenna elements.

[0123] The antenna panel 1304 may be coupled to an analog beam forming (BF) component including a plurality of phase shifters 1308(1)-1308(4). The phase shifters 1308(1)-1308(4) may be coupled to a radio frequency (RF) chain 1312. The RF chain 1312 may amplify the received analog RF signal, down-convert the RF signal to baseband, and convert the analog baseband signal to a digital baseband signal that may be provided to a baseband processor for further processing.

[0124] In various embodiments, control circuitry, which may reside in a baseband processor, may provide BF weights (e.g., W1-W4) to phase shifters 1308(1)-1308(4), which may represent phase shift values ​​to provide receive beams at antenna panel 1304. These BF weights may be determined based on channel-based beamforming.

[0125] Fig.14 A UE 1400 is shown according to some embodiments. The UE 1400 may be similar to, and substantially interchangeable with, any of the UEs described herein above.

[0126] Similar to what is described above with respect to UE 144, UE 1400 may be any mobile or non-mobile computing device, such as a mobile phone, computer, tablet, industrial wireless sensor (e.g., microphone, carbon dioxide sensor, pressure sensor, humidity sensor, thermometer, motion sensor, accelerometer, laser scanner, fluid level sensor, inventory sensor, voltage / current meter, actuator, etc.), video surveillance / monitoring equipment (e.g., camera, camcorder, etc.), wearable device, or loose IoT device. In some embodiments, the UE may be a reduced capacity UE or an NR-Light UE.

[0127] UE 1400 may include a processor 1404, an RF interface circuit 1408, a memory / storage device 1412, a user interface 1416, a sensor 1420, a driver circuit 1422, a power management integrated circuit (PMIC) 1424, and a battery 1428. The components of UE 1400 may be implemented as an integrated circuit (IC), a portion of an integrated circuit, a discrete electronic device, or other module, logic, hardware, software, firmware, or a combination thereof. Fig.14 The block diagram of UE 1400 is intended to show a high-level view of certain of the components of UE 1400. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0128] Components of UE 1400 may be coupled to various other components via one or more interconnects 1432, which may represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, optical connection, etc., which allows various circuit components (on a common or different chip or chipset) to interact with each other.

[0129] The processor 1404 may include processor circuits such as a baseband processor circuit (BB) 1404A, a central processor unit circuit (CPU) 1404B, and a graphics processor unit circuit (GPU) 1404C. The processor 1404 may include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions (such as program codes, software modules, or functional processes from the memory / storage device 1412) to cause the UE 1400 to perform operations as described herein.

[0130] In some embodiments, the baseband processor circuit 1404A can access the communication protocol stack 1436 in the memory / storage device 1412 to communicate through a 3GPP compatible network. Generally speaking, the baseband processor circuit 1404A can access the communication protocol stack to: perform user plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and perform control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access layer (NAS) layer. In some embodiments, the PHY layer operations can be additionally / alternatively performed by components of the RF interface circuit 1408.

[0131] The baseband processor circuit 1404A may generate or process baseband signals or waveforms that carry information in a 3GPP-compatible network. In some embodiments, the waveforms used for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

[0132] The baseband processor circuit 1404A may also access group information from the memory / storage 1412 to determine a search space group in which multiple repetitions of the PDCCH may be transmitted.

[0133] The memory / storage 1412 may include any type of volatile or non-volatile memory that may be distributed throughout the UE 1400. In some implementations, some of the memory / storage 1412 may be located on the processor 1404 itself (e.g., L1 cache and L2 cache), while other memory / storage 1412 is external to the processor 1404 but accessible via a memory interface. The memory / storage 1412 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0134] RF interface circuit 1408 may include transceiver circuits and radio frequency front end modules (RFEMs) that allow UE 1400 to communicate with other devices through a radio access network. RF interface circuit 1408 may include various components arranged in a transmission path or a reception path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, control circuits, etc.

[0135] In the receive path, the RFEM may receive the radiated signal from the air interface via antenna 1450 and proceed to filter and amplify the signal (using a low noise amplifier). The signal may be provided to a transceiver's receiver, which down-converts the RF signal to a baseband signal that is provided to a baseband processor of processor 1404.

[0136] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides an RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier before the signal is radiated across the air interface via the antenna 1450.

[0137] In various embodiments, the RF interface circuit 1408 may be configured to transmit / receive signals in a manner compatible with NR access technology.

[0138] Antenna 1450 may include multiple antenna elements, each of which converts electrical signals into radio waves to pass through the air and converts received radio waves into electrical signals. These antenna elements may be arranged into one or more antenna panels. Antenna 1450 may have an antenna panel that is omnidirectional, directional, or a combination thereof to achieve beamforming and multi-input, multi-output communication. Antenna 1450 may include a microstrip antenna, a printed antenna manufactured on the surface of one or more printed circuit boards, a patch antenna, a phased array antenna, etc. Antenna 1450 may have one or more panels that are designed for a specific frequency band included in a band in FR1 or FR2.

[0139] The user interface circuit 1416 includes various input / output (I / O) devices designed to enable a user to interact with the UE 1400. The user interface 1416 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual device for accepting input, including in particular one or more physical or virtual buttons (e.g., reset button), physical keyboard, keypad, mouse, touch pad, touch screen, microphone, scanner, headset, etc. The output device circuit includes any physical or virtual device for displaying information or otherwise conveying information (such as sensor readings, (multiple) actuator positions or other similar information). The output device circuit may include any number or combination of audio or visual displays, including in particular one or more simple visual outputs / indicators (e.g., binary state indicators, such as light emitting diodes (LEDs) and multi-character visual outputs), or more complex outputs, such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the UE 1400.

[0140] Sensor 1420 may include a device, module, or subsystem whose purpose is to detect events or changes in its environment and send information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit including an accelerometer; a gyroscope; or a magnetometer; a microelectromechanical system or nanoelectromechanical system including: a three-axis accelerometer; a three-axis gyroscope; or a magnetometer; a level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; a microphone or other similar audio capture device; and the like.

[0141] The driver circuit 1422 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 1400. The driver circuit 1422 may include various drivers to allow other components to interact with or control various input / output (I / O) devices that may be present in or connected to the UE 1400. For example, the driver circuit 1422 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface, a sensor driver for obtaining sensor readings of the sensor circuit 1420 and controlling and allowing access to the sensor circuit 1420, a driver for obtaining an actuator position of an electromechanical component or controlling and allowing access to an electromechanical component, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0142] The PMIC 1424 may manage the power provided to various components of the UE 1400. Specifically, with respect to the processor 1404, the PMIC 1424 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0143] In some embodiments, the PMIC 1424 may control or otherwise be part of various power saving mechanisms of the UE 1400. For example, if the platform UE is in the RRC_Connected state, in which the platform is still connected to the RAN node because it expects to receive traffic soon, then after a period of inactivity, the platform may enter a state known as discontinuous reception mode (DRX). During this state, the UE 1400 may be powered off for short intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the UE 1400 may transition to the RRC_Idle state, in which it is disconnected from the network and does not perform operations such as channel quality feedback, handovers, etc. The UE 1400 enters a very low power state and performs paging, in which it wakes up again periodically to listen to the network, and then powers off again. The UE 1400 may not receive data in this state; in order to receive data, the platform must transition back to the RRC_Connected state. Additional power saving modes may prevent the device from using the network for longer than the paging interval (which can range from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

[0144] The battery 1428 can power the UE 1400, but in some examples, the UE 1400 can be installed and deployed in a fixed location and can have a power source coupled to the power grid. The battery 1428 can be a lithium-ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, the battery 1428 can be a typical lead-acid car battery.

[0145] Fig.15 A gNB 1500 is shown according to some embodiments. The gNB 1500 may be similar to any of the base stations described herein above and may be substantially interchangeable therewith.

[0146] gNB 1500 may include a processor 1504, RAN interface circuitry 1508, core network (CN) interface circuitry 1512, and memory / storage device circuitry 1516.

[0147] Components of gNB 1500 may be coupled to various other components via one or more interconnects 1528.

[0148] The processor 1504, RAN interface circuit 1508, memory / storage circuit 1516 (including communication protocol stack 1510), antenna 1550 and interconnect 1528 may be similar to those of reference Fig.14 Like named elements are shown and described.

[0149] The CN interface circuitry 1512 may provide connectivity to a core network, e.g., a fifth generation core network (5GC) using a 5GC-compatible network interface protocol such as a Carrier Ethernet protocol or some other suitable protocol. Network connectivity may be provided to / from the gNB 1500 via optical fiber or wireless backhaul. The CN interface circuitry 1512 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 1512 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0150] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0151] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following examples. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the example section below.

[0152] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0153] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following examples. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the example section below.

[0154] Example

[0155] In the following sections, additional exemplary embodiments are provided.

[0156] Embodiment 1 includes a method implemented by a user equipment (UE), the method comprising: receiving first configuration information and second configuration information, wherein the first configuration information indicates a configuration of the cell for each cell in a plurality of cells, and wherein the second configuration information is separate from the first configuration information and indicates a layer 1 / layer 2 triggered mobility (LTM) association between two or more cells in the plurality of cells; establishing a first connection with a first cell in the plurality of cells, wherein the first connection is associated with medium access control (MAC) and radio link control (RLC) information; receiving a command to establish a second connection with a second cell in the plurality of cells; determining whether at least one of a MAC reset or an RLC reset will be performed based on the second configuration information; and establishing the second connection based on the determination.

[0157] Embodiment 2 includes a method according to embodiment 1, wherein the first configuration information and the second configuration information are received via radio resource control (RRC) signaling, wherein the first configuration information includes an LTM cell configuration for each of the multiple cells, wherein the second configuration information includes a reset group configuration indicating the LTM association, and wherein the LTM association indicates that the two or more cells are provided by the same base station distributed unit.

[0158] Embodiment 3 includes the method according to embodiment 2, wherein the LTM configuration corresponding to the second cell further indicates whether the LTM association between the second cell and the first cell is provided by the same base station distributed unit.

[0159] Embodiment 4 includes a method according to any one of embodiments 1 to 3, wherein the second configuration information indicates that the first cell and the second cell are part of the two or more cells having the LTM association, and wherein the determination indicates that the MAC reset and the RLC reset will be abandoned.

[0160] Embodiment 5 includes a method according to any one of Embodiments 1 to 4, wherein the second configuration information indicates that the first cell and the second cell are excluded from the two or more cells having the LTM association, and wherein the determination indicates that a MAC reset and an RLC reset are to be performed.

[0161] Embodiment 6 includes a method according to any one of Embodiments 1 to 5, wherein the second configuration information indicates that the first cell and the second cell are part of the two or more cells having the LTM association, and wherein the LTM association indicates that the MAC reset will be abandoned and the RLC reset will be performed.

[0162] Embodiment 7 includes a method according to any one of Embodiments 1 to 6, wherein the second configuration information indicates that the two or more cells form a cell group having the LTM association, and associates the first cell and the second cell with the group.

[0163] Embodiment 8 includes a method according to any one of embodiments 1 to 7, wherein the second configuration information includes group information for the group, and wherein the group information includes a first configuration identifier of the first cell and a second configuration identifier of the second cell.

[0164] Embodiment 9 includes a method according to any one of embodiments 1 to 8, wherein the second configuration information includes group information for the group, and wherein the group information includes a first cell identifier of the first cell, a second cell identifier of the second cell, and an absolute radio frequency channel number (ARFCN).

[0165] Embodiment 10 includes a method according to any one of Embodiments 1 to 9, wherein the second configuration information includes group information for the group, and wherein the group information includes an indication of whether at least one of the MAC reset or the RLC reset will be performed.

[0166] Embodiment 11 includes a method according to any one of Embodiments 1 to 10, wherein the second configuration information indicates that the two or more cells form a cell group having the LTM association and includes group information for the group, and wherein the first configuration information includes an LTM cell configuration indicating the group for the second cell.

[0167] Embodiment 12 includes a method according to embodiment 11, wherein determining whether to perform at least one of the MAC reset or the RLC reset includes: determining that the second cell belongs to the group based on the LTM cell configuration; determining that the first cell belongs to the group; and based on the group information, determining that the LTM association is applicable to the second cell based on the second cell and that the second cell belongs to the group.

[0168] Embodiment 13 includes the method according to embodiment 11, wherein the first configuration information includes a reference to the group for the second cell.

[0169] Embodiment 14 includes a method according to any one of Embodiments 1 to 13, wherein the second configuration information indicates that the two or more cells form a default LTM cell group having the LTM association, and wherein the method further includes: determining that the first cell and the second cell belong to the default LTM group based on the absence of an explicit indication that the first cell and the second cell belong to another LTM group.

[0170] Embodiment 15 includes a method according to any one of Embodiments 1 to 14, wherein the second configuration information indicates that the two or more cells form a default LTM cell group having the LTM association, wherein the first configuration information includes an LTM cell configuration for the second cell, and wherein the method further includes: determining that the second cell belongs to the default LTM group based on the absence of an explicit indication in the LTM cell configuration that the second cell belongs to another LTM group.

[0171] Embodiment 16 includes a method according to any one of Embodiments 1 to 15, wherein the second configuration information includes a bit string indicating an LTM association between the multiple cells, and wherein determining whether to perform at least one of the MAC reset or the RLC reset includes: determining bit values ​​corresponding to the first cell and the second cell based on the bit string; and determining at least one of the MAC reset or the RLC reset to be performed based on the bit value.

[0172] Embodiment 17 includes the method of embodiment 16, wherein the bit value corresponds to a single bit indicating that both the MAC reset and the RLC reset are to be performed.

[0173] Embodiment 18 includes the method of embodiment 16, wherein the bit value corresponds to a plurality of bits, wherein at least a first bit of the plurality of bits indicates that the MAC reset is to be performed, and wherein a second bit of the plurality of bits indicates that the RLC reset is to be performed.

[0174] Embodiment 19 includes a method according to any one of Embodiments 1 to 18, wherein the second configuration information includes a first bit string and a second bit string indicating the LTM association between the multiple cells, and wherein determining whether at least one of the MAC reset or the RLC reset will be performed includes: determining a first bit value based on the first bit string, the first bit value corresponding to the first cell and the second cell and indicating whether the MAC reset will be performed; and determining a second bit value based on the second bit string, the second bit value corresponding to the first cell and the second cell and indicating whether the RLC reset will be performed.

[0175] Embodiment 20 includes a method according to any one of Embodiments 1 to 19, wherein the second configuration information indicates a source configuration identifier and a threshold distance, and wherein determining whether to perform at least one of the MAC reset or the RLC reset includes: determining a difference between the second configuration identifier of the second cell and the source configuration identifier; and determining that the MAC reset and the RLC reset will be abandoned if the difference is less than or equal to the threshold distance, and determining that the MAC reset and the RLC reset will be performed if the difference is greater than the threshold distance.

[0176] Embodiment 21 includes a method according to any one of embodiments 1 to 20, wherein the second configuration information indicates that the two or more cells form a cell group having the LTM association, wherein the group corresponds to a base station distributed unit.

[0177] Embodiment 22 includes a method according to any one of Embodiments 1 to 21, wherein establishing the second connection includes sending a random access channel message on the second cell, and wherein the method further includes: receiving a random access response indicating timing advance information for the second cell from the first cell in response to the random access channel message, wherein the random access response is received from the first cell rather than the second cell based on the first cell and the second cell being part of the two or more cells having the LTM association.

[0178] Embodiment 23 includes a method according to any one of embodiments 1 to 22, wherein at least one of the first configuration information, the second configuration information, or the additional configuration information indicates that the random access response will be received on the first cell.

[0179] Embodiment 24 includes a method implemented by a network, the method comprising: sending first configuration information and second configuration information to a user equipment (UE), wherein the first configuration information indicates a configuration of the cell for each cell in a plurality of cells, and wherein the second configuration information is separate from the first configuration information and indicates a layer 1 / layer 2 triggered mobility (LTM) association between two or more cells in the plurality of cells; establishing a first connection with the UE via a first cell in the plurality of cells, wherein the first connection is associated with medium access control (MAC) and radio link control (RLC) information; sending a command to the UE to establish a second connection with a second cell in the plurality of cells; and establishing the second connection based on the first configuration information and the second configuration information.

[0180] Embodiment 25 includes a method according to embodiment 24, wherein the network includes a base station distributed unit, wherein the first cell is provided by a first transmission and reception point of the base station distributed unit, and wherein the second cell is provided by a second transmission and reception point of the base station distributed unit.

[0181] Embodiment 26 includes a method according to any one of embodiments 24 to 25, wherein the first configuration information includes an LTM cell configuration for each cell in the plurality of cells, and wherein the second configuration information includes a reset group configuration indicating the LTM association.

[0182] Embodiment 27 includes a method according to any one of embodiments 24 to 26, wherein the second configuration information indicates that the two or more cells form a default LTM cell group with the LTM association, and excludes explicit indication that the first cell and the second cell belong to another LTM group.

[0183] Embodiment 28 includes a method according to any one of Embodiments 24 to 27, wherein the second configuration information indicates that the two or more cells form a default LTM cell group having the LTM association, wherein the first configuration information includes an LTM cell configuration for the second cell, and wherein the LTM cell configuration excludes an explicit indication that the second cell belongs to another LTM group.

[0184] Embodiment 29 includes a method according to any one of embodiments 24 to 28, wherein the second configuration information includes a bit string indicating an LTM association between the multiple cells.

[0185] Embodiment 30 includes a method according to any one of Embodiments 24 to 29, wherein the second configuration information indicates a source configuration identifier and a threshold distance.

[0186] Embodiment 31 includes a method according to any one of embodiments 24 to 30, wherein at least one of first configuration information, second configuration information, or additional configuration information indicating at least one of a random access response or a timing advance value in response to a random access channel message sent on a target cell will be received on a source cell, wherein the target cell and the source cell are part of the two or more cells having the LTM association.

[0187] Embodiment 32 includes an apparatus comprising means for performing one or more elements of a method according to any one of or related to Embodiments 1 to 31.

[0188] Embodiment 33 includes one or more non-transitory computer-readable media, which include instructions that, when executed by one or more processors of a device, cause the device to perform one or more elements of a method described in or related to any one of Embodiments 1 to 31.

[0189] Embodiment 34 includes an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method according to any one of or related to Embodiments 1 to 31.

[0190] Embodiment 35 includes a device comprising one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of a method described in or related to any one of Embodiments 1 to 31.

[0191] Embodiment 36 includes a system comprising means for performing one or more elements of the method according to any one of or related to Embodiments 1-31.

[0192] Embodiment 37 includes a network comprising means for performing one or more elements of a method according to any one of or related to Embodiments 1 to 31.

[0193] Embodiment 38 comprises one or more non-transitory computer-readable media, which include instructions that, when executed by one or more processors of a network, cause the network to perform one or more elements of a method described in or related to any one of Embodiments 1 to 31.

[0194] Embodiment 39 includes a network comprising logic components, modules or circuits for executing one or more elements of the method according to any one of or related to embodiments 1 to 31.

[0195] Embodiment 40 includes a network comprising one or more processors and one or more computer-readable media, the one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of a method described in or related to any one of Embodiments 1 to 31.

[0196] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In view of the above teachings, modifications and variations are possible or can be obtained from the practice of various embodiments.

[0197] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in view of the above teachings or may be obtained from the practice of the various embodiments.

[0198] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to encompass all such variations and modifications.

Claims

1. A method implemented by a user equipment (UE), the method comprising: receiving first configuration information and second configuration information, wherein the first configuration information indicates, for each cell of a plurality of cells, a configuration of the cell, and wherein the second configuration information is separate from the first configuration information and indicates a layer 1 / layer 2 triggered mobility (LTM) association between two or more cells of the plurality of cells; establishing a first connection with a first cell of the plurality of cells, wherein the first connection is associated with medium access control (MAC) and radio link control (RLC) information; receiving a command to establish a second connection with a second cell among the plurality of cells; determining whether to perform at least one of a MAC reset or an RLC reset based on the second configuration information; as well as The second connection is established based on the determination.

2. The method of claim 1, wherein the first configuration information and the second configuration information are received via radio resource control (RRC) signaling, wherein the first configuration information includes an LTM cell configuration for each of the plurality of cells, wherein the second configuration information includes a reset group configuration indicating the LTM association, and wherein the LTM association indicates that the two or more cells are provided by the same base station distributed unit.

3. The method according to claim 2, wherein the LTM configuration corresponding to the second cell further indicates whether the LTM association of the second cell and the first cell is provided by the same base station distributed unit.

4. The method of claim 1, wherein the second configuration information indicates that the first cell and the second cell are part of the two or more cells having the LTM association, and wherein the determination indicates that the MAC reset and the RLC reset are to be abandoned.

5. The method of claim 1, wherein the second configuration information indicates that the first cell and the second cell are excluded from the two or more cells having the LTM association, and wherein the determination indicates that the MAC reset and the RLC reset are to be performed.

6. The method of claim 1, wherein the second configuration information indicates that the first cell and the second cell are part of the two or more cells having the LTM association, and wherein the LTM association indicates that the MAC reset is to be abandoned and the RLC reset is to be performed. 7 . The method according to claim 1 , wherein the second configuration information indicates that the two or more cells form a cell group with the LTM association, and associates the first cell and the second cell with the group. 8 . The method according to claim 7 , wherein the second configuration information comprises group information for the group, and wherein the group information comprises a first configuration identifier of the first cell and a second configuration identifier of the second cell.

9. The method according to claim 7, wherein the second configuration information includes group information for the group, and wherein the group information includes a first cell identifier of the first cell, a second cell identifier of the second cell, and an Absolute Radio Frequency Channel Number (ARFCN).

10. The method of claim 7, wherein the second configuration information comprises group information for the group, and wherein the group information comprises an indication of whether the at least one of the MAC reset or the RLC reset is to be performed.

11. The method according to claim 1, wherein the second configuration information indicates that the two or more cells form a cell group having the LTM association and includes group information for the group, wherein the first configuration information includes an LTM cell configuration indicating the group for the second cell.

12. The method of claim 11 , wherein determining whether the at least one of the MAC reset or the RLC reset is to be performed comprises: determining, based on the LTM cell configuration, that the second cell belongs to the group; determining that the first cell belongs to the group; as well as Based on the group information, it is determined that the LTM association is applicable to the second cell based on the second cell and the second cell belonging to the group. The method according to claim 11 , wherein the first configuration information comprises a reference to the group for the second cell.

14. The method according to claim 1, wherein the second configuration information indicates that the two or more cells form a default LTM cell group with the LTM association, and wherein the method further comprises: Determining that the first cell and the second cell belong to the default LTM group is based on the absence of an explicit indication that the first cell and the second cell belong to another LTM group.

15. The method of claim 1, wherein the second configuration information indicates that the two or more cells form a default LTM cell group with the LTM association, wherein the first configuration information includes an LTM cell configuration for the second cell, and wherein the method further comprises: Determining that the second cell belongs to the default LTM group is based on the absence of an explicit indication in the LTM cell configuration that the second cell belongs to another LTM group.

16. The method of claim 1 , wherein the second configuration information comprises a bit string indicating an LTM association between the plurality of cells, and wherein determining whether the at least one of the MAC reset or the RLC reset is to be performed comprises: determining bit values ​​corresponding to the first cell and the second cell based on the bit string; as well as At least one of the at least one of the MAC reset or the RLC reset is to be performed is determined based on the bit value.

17. The method of claim 16, wherein the bit value corresponds to a single bit indicating that both the MAC reset and the RLC reset are to be performed.

18. The method of claim 16, wherein the bit value corresponds to a plurality of bits, wherein at least a first bit of the plurality of bits indicates that the MAC reset is to be performed, and wherein a second bit of the plurality of bits indicates that the RLC reset is to be performed.

19. The method of claim 1, wherein the second configuration information comprises a first bit string and a second bit string indicating an LTM association between the plurality of cells, and wherein determining whether the at least one of the MAC reset or the RLC reset is to be performed comprises: determining a first bit value based on the first bit string, the first bit value corresponding to the first cell and the second cell and indicating whether the MAC reset is to be performed; as well as A second bit value is determined based on the second bit string, the second bit value corresponding to the first cell and the second cell and indicating whether the RLC reset is to be performed.

20. The method of claim 1, wherein the second configuration information indicates a source configuration identifier and a threshold distance, and wherein determining whether to perform the at least one of the MAC reset or the RLC reset comprises: determining a difference between a second configuration identifier of the second cell and the source configuration identifier; as well as If the difference is less than or equal to the threshold distance, it is determined that the MAC reset and the RLC reset will be abandoned, and if the difference is greater than the threshold distance, it is determined that the MAC reset and the RLC reset will be performed.

21. A user equipment (UE), comprising: one or more processors; and One or more memories storing instructions that, when executed by the UE, configure the UE to: receiving first configuration information and second configuration information, wherein the first configuration information indicates, for each cell of a plurality of cells, a configuration of the cell, and wherein the second configuration information is separate from the first configuration information and indicates a layer 1 / layer 2 triggered mobility (LTM) association between two or more cells of the plurality of cells; establishing a first connection with a first cell of the plurality of cells, wherein the first connection is associated with medium access control (MAC) and radio link control (RLC) information; receiving a command to establish a second connection with a second cell among the plurality of cells; determining whether to perform at least one of a MAC reset or an RLC reset based on the second configuration information; as well as The second connection is established based on the determination.

22. The UE of claim 21, wherein the second configuration information indicates that the two or more cells form a cell group having the LTM association, wherein the group corresponds to a base station distributed unit.

23. The UE of claim 21 , wherein establishing the second connection comprises sending a random access channel message on the second cell, and wherein execution of the instructions further configures the UE to: A random access response indicating timing advance information for the second cell is received from the first cell in response to the random access channel message, wherein the random access response is received from the first cell instead of the second cell based on the first cell and the second cell being part of the two or more cells having the LTM association.

24. The UE of claim 23, wherein at least one of the first configuration information, the second configuration information, or additional configuration information indicates that the random access response is to be received on the first cell.

25. A method implemented by a network, the method comprising: sending first configuration information and second configuration information to a user equipment (UE), wherein the first configuration information indicates, for each cell in a plurality of cells, a configuration of the cell, and wherein the second configuration information is separate from the first configuration information and indicates a layer 1 / layer 2 triggered mobility (LTM) association between two or more cells in the plurality of cells; establishing a first connection with the UE via a first cell of the plurality of cells, wherein the first connection is associated with medium access control (MAC) and radio link control (RLC) information; Sending a command to the UE to establish a second connection with a second cell among the multiple cells; as well as The second connection is established based on the first configuration information and the second configuration information.

26. The method of claim 25, wherein the network comprises a base station distributed unit, wherein the first cell is provided by a first transmission and reception point of the base station distributed unit, and wherein the second cell is provided by a second transmission and reception point of the base station distributed unit.

27. The method of claim 25, wherein the first configuration information comprises an LTM cell configuration for each of the plurality of cells, and wherein the second configuration information comprises a reset group configuration indicating the LTM association.

28. The method of claim 25, wherein the second configuration information indicates that the two or more cells form a default LTM cell group with the LTM association, and excludes an explicit indication that the first cell and the second cell belong to another LTM group.

29. The method of claim 25, wherein the second configuration information indicates that the two or more cells form a default LTM cell group having the LTM association, wherein the first configuration information includes an LTM cell configuration for the second cell, and wherein the LTM cell configuration excludes an explicit indication that the second cell belongs to another LTM group.

30. The method of claim 25, wherein the second configuration information comprises a bit string indicating an LTM association between the plurality of cells. The method of claim 25 , wherein the second configuration information indicates a source configuration identifier and a threshold distance.

32. The method of claim 25, wherein at least one of the first configuration information, the second configuration information, or the additional configuration information indicating at least one of a random access response or a timing advance value in response to a random access channel message sent on a target cell is to be received on a source cell, wherein the target cell and the source cell are part of the two or more cells having the LTM association.