Method and apparatus for uplink time alignment in a wireless communication system

Abstract

A method and apparatus for uplink time alignment in a wireless communication system are disclosed. In an example from the perspective of a user equipment, the user equipment receives first signaling indicating a configuration of a first cell, where the first cell is associated with a first occasion advance group. The user equipment receives second signaling indicating an addition of the first cell as a first serving cell. In response to the second signaling, the user equipment (i) adds the first cell as the first serving cell, and (ii) determines whether to initiate a random access procedure based on the second signaling and / or based on whether the first cell is associated with a first valid timing advance value.

Description

Technical Field

[0001] This disclosure generally relates to wireless communication networks, and more particularly to a method and apparatus for uplink time alignment in a wireless communication system. Background Technology

[0002] With the rapid growth in demand for transmitting large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks that communicate using Internet Protocol (IP) data packets. This IP data packet communication can provide users of mobile communication devices with IP-bearing voice, multimedia, multicast, and video-on-demand communication services.

[0003] An exemplary network architecture is the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). E-UTRAN systems can provide high data throughput to enable the aforementioned IP-based voice and multimedia services. Currently, the 3GPP standards organization is discussing next-generation (e.g., 5G) radio technologies. Therefore, changes to the current core of the 3GPP standards are currently being submitted and considered to facilitate their evolution and completion. Summary of the Invention

[0004] According to this disclosure, one or more apparatuses and / or methods are provided. In an example from the perspective of user equipment (UE), the UE receives a first signaling indicating the configuration of a first cell, wherein the first cell is associated with a first timing advance group (TAG). The UE receives a second signaling indicating that the first cell be added as a first serving cell. In response to the second signaling, the UE (i) adds the first cell as the first serving cell, and (ii) determines whether to initiate a random access procedure based on the second signaling and / or based on whether the first cell is associated with a first effective timing advance value. Attached Figure Description

[0005] Figure 1 A diagram illustrating a wireless communication system according to an exemplary embodiment is shown;

[0006] Figure 2 This is a block diagram of a transmitter system (also referred to as an access network) and a receiver system (also referred to as a user equipment or UE) according to an exemplary embodiment;

[0007] Figure 3 This is a functional block diagram of a communication system according to an exemplary embodiment;

[0008] Figure 4 This is based on an exemplary embodiment. Figure 3 Functional block diagram of the program code;

[0009] Figure 5 This is a diagram illustrating an exemplary scenario related to uplink-downlink timing relationships according to an exemplary embodiment;

[0010] Figure 6 This is a diagram illustrating an exemplary scenario associated with a UE, a first cell, and a second cell, according to an exemplary embodiment.

[0011] Figure 7 This is a diagram illustrating an exemplary scenario associated with a UE and a network, based on an exemplary embodiment.

[0012] Figure 8 This is a diagram illustrating an exemplary scenario associated with a UE and a network, based on an exemplary embodiment.

[0013] Figure 9 This is a diagram illustrating an exemplary scenario associated with a UE and a network, based on an exemplary embodiment.

[0014] Figure 10 This is a diagram illustrating an exemplary scenario associated with a UE and a network, based on an exemplary embodiment.

[0015] Figure 11 This is a diagram illustrating an exemplary scenario associated with a UE and a network, based on an exemplary embodiment.

[0016] Figure 12 This is a diagram illustrating an exemplary scenario associated with a UE and a network, based on an exemplary embodiment.

[0017] Figure 13 This is a diagram illustrating an exemplary scenario associated with a UE and a network, based on an exemplary embodiment.

[0018] Figure 14 This is a diagram illustrating an exemplary scenario associated with a UE and a network, based on an exemplary embodiment.

[0019] Figure 15 This is a diagram illustrating an exemplary scenario associated with a UE and a network, based on an exemplary embodiment.

[0020] Figure 16 This is a diagram illustrating an exemplary scenario associated with a UE and a network, based on an exemplary embodiment.

[0021] Figure 17 This is a diagram illustrating an exemplary scenario associated with a UE and a network, based on an exemplary embodiment.

[0022] Figure 18 This is a flowchart according to an exemplary embodiment;

[0023] Figure 19 This is a flowchart according to an exemplary embodiment;

[0024] Figure 20 This is a flowchart according to an exemplary embodiment;

[0025] Figure 21 This is a flowchart according to an exemplary embodiment;

[0026] Figure 22 This is a flowchart based on an exemplary embodiment. Detailed Implementation

[0027] The exemplary wireless communication systems and apparatus described below employ wireless communication systems that support broadcast services. Wireless communication systems are widely deployed to provide various types of communication, such as voice, data, etc. These systems may be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) radio access, 3GPP Long Term Evolution Advanced (LTE-A or LTE-Advanced), 3GPP2 Ultra Mobile Broadband (UMB), WiMax, 3GPP New Radio (NR) radio access for 5G, or some other modulation techniques.

[0028] In particular, the exemplary wireless communication system apparatus described below may be designed to support one or more standards, such as those provided by the association known herein as the "3rd Generation Partnership Project" (3GPP), including: RP-212710NR further mobility enhancements; 3GPP specification 38.331 v16.6.0; 3GPP specification 38.321 v16.6.0; and 3GPP specification 38.211 v16.7.0. The standards and documents listed above are hereby expressly incorporated by reference in their entirety.

[0029] Figure 1A multiple access wireless communication system according to one or more embodiments of the present disclosure is presented. Access network 100 (AN) includes multiple antenna groups, one antenna group including 104 and 106, another antenna group including 108 and 110, and a further antenna group including 112 and 114. Figure 1 In this diagram, only two antennas are shown in each antenna group; however, each antenna group can utilize more or fewer antennas. Access terminal 116 (AT) communicates with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 via forward link 120 and receive information from access terminal 116 via reverse link 118. AT 122 communicates with antennas 106 and 108, where antennas 106 and 108 transmit information to AT 122 via forward link 126 and receive information from AT 122 via reverse link 124. In a frequency-division duplex (FDD) system, communication links 118, 120, 124, and 126 can use different frequencies for communication. For example, forward link 120 can use a frequency different from that used by reverse link 118.

[0030] Each group of antennas and / or the area in which they are designed to communicate is often referred to as a sector of the access network. In an embodiment, each antenna group may be designed to communicate with an access terminal in a sector of the area covered by the access network 100.

[0031] In communications via forward links 120 and 126, the transmit antennas of access network 100 can utilize beamforming to improve the signal-to-noise ratio of the forward links for different access terminals 116 and 122. Furthermore, compared to an access network transmitting to its access terminals via a single antenna, an access network using beamforming to transmit to access terminals randomly distributed throughout its coverage area typically causes less interference to access terminals in neighboring cells.

[0032] An access network (AN) can be a fixed station or base station used for communication with terminals, and may also be referred to as an access point, Node B, base station, enhanced base station, eNodeB (eNB), next-generation NodeB (gNB), or other terms. An access terminal (AT) may also be referred to as user equipment (UE), wireless communication device, terminal, access terminal, or other terms.

[0033] Figure 2An embodiment of a multiple-input multiple-output (MIMO) system 200 is presented, comprising a transmitter system 210 (also referred to as an access network) and a receiver system 250 (also referred to as an access terminal (AT) or user equipment (UE)). At the transmitter system 210, service data from multiple data streams can be provided from a data source 212 to a transmit (TX) data processor 214.

[0034] In one embodiment, each data stream is transmitted via a corresponding transmit antenna. The TX data processor 214 formats, decodes, and interleaves the service data of the data streams based on a specific decoding scheme selected for each data stream to provide decoded data.

[0035] Orthogonal frequency-division multiplexing (OFDM) technology can be used to multiplex the decoded data and pilot data of each data stream. The pilot data can typically be a known data pattern processed in a known manner and can be used at the receiver system to estimate the channel response. The multiplexed pilot and decoded data of the data stream can then be modulated (i.e., symbol mapped) based on a specific modulation scheme selected for each data stream (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-ary phase shift keying (M-PSK), or M-ary quadrature amplitude modulation (M-QAM) to provide modulated symbols. Instructions executed by processor 230 can determine the data rate, decoding, and / or modulation for each data stream.

[0036] The modulation symbols of the data stream are then provided to a TX MIMO processor 220, which can further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then provides NT modulation symbol streams to NT transmitters (TMTRs) 222a to 222t. In some embodiments, the TX MIMO processor 220 may apply beamforming weights to the symbols of the data stream and the antennas from which the symbols are transmitted.

[0037] Each transmitter 222 receives and processes a corresponding symbol stream to provide one or more analog signals, and further modulates (e.g., amplifies, filters, and / or up-converts) the analog signals to provide modulated signals suitable for transmission via a MIMO channel. Then, NT modulated signals from transmitters 222a to 222t can be transmitted from NT antennas 224a to 224t respectively.

[0038] At receiver system 250, the transmitted modulated signal is received by NR antennas 252a to 252r, and the signal received from each antenna 252 can be provided to the corresponding receiver (RCVR) 254a to 254r. Each receiver 254 can regulate (e.g., filter, amplify, and down-convert) the corresponding received signal, digitize the regulated signal to provide a sample, and / or further process the sample to provide a corresponding "received" symbol stream.

[0039] Next, the RX data processor 260 receives and / or processes the NR received symbol streams from NR receivers 254 based on specific receiver processing techniques to provide NT "detected" symbol streams. The RX data processor 260 can then demodulate, deinterleave, and / or decode each detected symbol stream to recover the service data used for the data stream. The processing performed by the RX processor 260 can complement the processing performed by the TX MIMO processor 220 and TX data processor 214 at the transmitter system 210.

[0040] Processor 270 can periodically determine which pre-decoding matrix to use (discussed below). Processor 270 formulates a reverse link message including a matrix index portion and a rank portion.

[0041] The reverse link message may include various types of information about the communication link and / or the received data stream. The reverse link message may then be processed by the TX data processor 238 (which also receives service data from multiple data streams from the data source 236), modulated by the modulator 280, regulated by the transmitters 254a to 254r, and / or transmitted back to the transmitter system 210.

[0042] At transmitter system 210, the modulated signal from receiver system 250 is received by antenna 224, conditioned by receiver 222, demodulated by demodulator 240, and processed by RX data processor 242 to extract the reverse link message transmitted by receiver system 250. Next, processor 230 can determine which pre-decoding matrix to use to determine beamforming weights, and then process the extracted message.

[0043] Figure 3An alternative simplified functional block diagram of a communication device according to one embodiment of the disclosed subject matter is presented. Figure 3 As shown, the communication device 300 in the wireless communication system can be used to achieve... Figure 1 UE (or AT) 116 and 122 or Figure 1 The communication device 300 includes a base station (or AN) 100, and the wireless communication system can be an LTE system or an NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 via the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive signals input by a user via the input device 302 (e.g., a keyboard or keypad) and can output images and sounds via the output device 304 (e.g., a display or speaker). The transceiver 314 is used to receive and transmit wireless signals, transmit received signals to the control circuit 306, and wirelessly output signals generated by the control circuit 306. Alternatively, the communication device 300 in a wireless communication system can also be used. Figure 1 AN 100 in the middle.

[0044] Figure 4 This is an embodiment based on the disclosed subject matter. Figure 3 The diagram shows a simplified block diagram of program code 312. In this embodiment, program code 312 includes an application layer 400, a layer 3 portion 402, and a layer 2 portion 404, and is coupled to a layer 1 portion 406. Layer 3 portion 402 can perform radio resource control. Layer 2 portion 404 can perform link control. Layer 1 portion 406 can perform and / or implement physical connections.

[0045] The new Work Item Description (WID) regarding further mobility enhancements for NR provided in RP-212710 discusses one or more objectives for enhancing NR mobility. One or more sections of RP-212710 are quoted below:

[0046] 3 Adjustments

[0047] When a UE moves from the coverage area of ​​one cell to another, a serving cell change needs to be performed at some point. Currently, serving cell changes are triggered by L3 measurements and reconfigured via synchronized RRC signaling for changes to PCell and PSCell, and, where applicable, for SCell release. In all cases, L2 (and L1) are completely reset, and this involves more latency, more overhead, and more downtime compared to beam-switching mobility. The goal of L1 / L2 mobility enhancement is to enable serving cell changes via L1 / L2 signaling with such low latency, low overhead, and low downtime.

[0048] 4 objectives

[0049] 4.1 Core Components: WI's Objectives

[0050] The detailed objectives of this work item are:

[0051] 1. Specify the mechanisms and procedures for reducing mobility latency based on L1 / L2 inter-cell mobility:

[0052] Configure and maintain multiple candidate cells to allow for rapid application of candidate cell configurations [RAN2, RAN3].

[0053] o A dynamic handover mechanism [RAN2, RAN1] based on L1 / L2 signaling for potential applicable scenarios between candidate serving cells (including SpCell and SCell).

[0054] ○L1 enhancements include inter-cell beam management, L1 measurement and reporting, beam indication, and are used to handle asynchronous scenarios in TA management [RAN1, RAN2].

[0055] ○ Support CU-DU interface signaling for L1 / L2 mobility (if required) [RAN3]

[0056] Note 1: FR2-specific enhancements are not excluded (if they exist).

[0057] Note 2: Programs based on L1 / L2 inter-cell mobility can be applied to the following scenarios:

[0058] ■ Independent, CA, and NR-DC scenarios with serving cell changes within a CG

[0059] ■ Situation within CU and between DUs within CU (applicable to independent and CA)

[0060] ■ Same frequency and different frequency

[0061] = Both FR1 and FR2

[0062] Reconfiguration with synchronization (e.g., handover) and SCell additions is described in 3GPP specification 38.331v16.6.0, one or more of which are cited below:

[0063] 3.1 Definition

[0064] Primary cell: An MCG cell that operates on the primary frequency, in which the UE executes the initial connection establishment procedure or initiates a connection re-establishment procedure.

[0065] Primary SCG cell: For dual connectivity operations, the UE uses the SCG cell for random access when performing a reconfiguration with a synchronization procedure.

[0066] Sub-cell: For UEs configured to use CA, a cell that provides additional radio resources on top of a special cell.

[0067] Subcell group: For UEs configured to use dual connectivity, this includes a subset of serving cells with PSCell and zero or more subcells.

[0068] Serving Cell: For a UE in RRC_CONNECTED state and not configured to use CA / DC, there exists only one serving cell, which includes the primary cell. For a UE in RRC_CONNECTED state and configured to use CA / DC, the term 'serving cell' is used to refer to the set of cells that includes the primary cell and all secondary cells.

[0069] Special Cell: For dual connectivity operations, the term special cell refers to the PCell of the MCG or the PSCell of the SCG. In other cases, the term special cell refers to the PCell.

[0070] 5.3.5.5 Cell Group Configuration

[0071] 5.3.5.5.1 Overview

[0072] The network configures the UE using a Master Cell Group (MCG) and zero or one Secondary Cell Group (SCG). In (NG)EN-DC, the MCG is configured as specified in TS 36.331

[10] , and for NE-DC, the SCG is configured as specified in TS 36.331

[10] . The network provides the configuration parameters for the cell groups in the CellGroupConfig IE.

[0073] Based on the received CellGroupConfig IE, the UE performs the following actions:

[0074] 1> If CellGroupConfig contains spCellConfig with reconfigurationWithSync:

[0075] 2> Perform a synchronized reconfiguration according to 5.3.5.5.2;

[0076] 2> Restore all suspended radio bearers except for the SRB of the source cell group, and restore SCG transmission of all radio bearers, restore the BH RLC channel, and restore SCG transmission of the BH RLC channel for IAB-MT (if suspended).

[0077] 1> If CellGroupConfig contains rlc-BearerToReleaseList:

[0078] 2> Perform RLC bearer release as specified in 5.3.5.5.3;

[0079] 1> If CellGroupConfig contains rlc-BearerToAddModList:

[0080] 2> Perform RLC bearer addition / modification as specified in 5.3.5.5.4;

[0081] 1> If CellGroupConfig contains mac-CellGroupConfig:

[0082] 2> Configure the MAC entity for this cell group as specified in 5.3.5.5.5;

[0083] 1> If CellGroupConfig contains sCellToReleaseList:

[0084] 2> Perform SCell release as specified in 5.3.5.5.8;

[0085] 1> If CellGroupConfig contains spCellConfig:

[0086] 2> Configure SpCell as specified in 5.3.5.5.7;

[0087] 1> If CellGroupConfig contains sCellToAddModList:

[0088] 2> Perform SCell addition / modification as specified in 5.3.5.5.9;

[0089] 1> If CellGroupConfig contains bh-RLC-ChannelToReleaseList:

[0090] 2> Perform BH RLC channel release as specified in 5.3.5.5.10;

[0091] 1> If CellGroupConfig contains bh-RLC-ChannelToAddModList:

[0092] 2> Perform BH RLC channel addition / modification as specified in 5.3.5.5.11;

[0093] 5.3.5.5.2 Features synchronized reconfiguration

[0094] The UE will perform the following actions to perform a synchronous reconfiguration.

[0095] 1> If AS security is not activated, then the action is performed as specified in 5.3.11 after going to RRC_IDLE, with the release reason being "other", and the program ends after the release reason;

[0096] 1> If DAPS bearer is not configured:

[0097] 2> Stop the timer T310 for the corresponding SpCell (if it is running);

[0098] 1> If this procedure is executed against MCG:

[0099] 2> If timer T316 is running;

[0100] 3> Stop timer T316;

[0101] 3> Clear the information contained in the VarRLF-Report (if it exists);

[0102] 2> Resume MCG transfer (if paused).

[0103] 1> Stop the timer T312 for the corresponding SpCell (if it is running);

[0104] 1> Start the timer T304 for the corresponding SpCell, where the timer value is set to t304, as included in reconfigurationWithSync;

[0105] 1> If frequencyInfoDL is included:

[0106] 2> Treat the target SpCell as an SpCell on the SSB frequency indicated by frequencyInfoDL, which has a physical cell identity indicated by physCellId;

[0107] 1> Otherwise:

[0108] 2> Treat the target SpCell as the SpCell on the SSB frequency of the source SpCell, which has a physical cell identity indicated by physCellId;

[0109] 1> Begin DL synchronization with the target SpCell;

[0110] 1> Apply the specified BCCH configuration defined in 9.1.1.1 to the target SpCell;

[0111] 1> Obtain the MIB of the target SpCell, which is scheduled as specified in TS 38.213

[13] ;

[0112] Note 1: The UE should perform a synchronized reconfiguration as soon as possible after receiving an RRC message that triggers a synchronized reconfiguration, which may be before confirming successful reception (HARQ and ARQ) of this message.

[0113] Note 2: If the UE already has the required timing information, or if the timing information is not needed for random access, then the UE can omit reading the MIB.

[0114] Note 2a: UEs with DAPS bearers do not listen to system information updates in the source PCell.

[0115] 1> If any DAPS bearers are configured:

[0116] 2> Create a MAC entity for the target cell group with the same configuration as the MAC entity for the source cell group;

[0117] 2> For each DAPS bearer:

[0118] 3> Establish an RLC entity or an entity for the target cell group, which has the same configuration as the entity for the source cell group;

[0119] 3> Establish a logical channel for the target cell group, which has the same configuration as the channel for the source cell group;

[0120] Note 2b: For understanding, if DAPS bearer is configured, the UE needs to check whether the field daps-Config exists in the RadioBearerConfig IE received in radioBearerConfig or radioBearerConfig2.

[0121] 2> For each SRB:

[0122] 3> Establish an RLC entity for the target cell group, which has the same configuration as the entity for the source cell group;

[0123] 3> Establish a logical channel for the target cell group, which has the same configuration as the channel for the source cell group;

[0124] 2> Suspend SRBs used for source cell groups;

[0125] Note 3: Invalid

[0126] 2> Apply the value of the newUE-identity as the C-RNTI in the target cell group;

[0127] 2> Configure the lower layer of the target SpCell according to the received spCellConfigCommon configuration;

[0128] 2> If the received reconfigurationWithSync contains any additional fields not previously covered, then configure the lower layer for the target SpCell based on those additional fields.

[0129] 1> Otherwise:

[0130] 2> Reset the MAC entity of this cell group;

[0131] 2> Treat SCells of this cell group (if configured) that are not included in the SCellToAddModList in the RRCReconfiguration message as being in a deactivated state;

[0132] 2> Apply the value of the newUE-identity as the C-RNTI for this cell group;

[0133] 2> Configure the lower layer according to the received spCellConfigCommon;

[0134] 2> If the received reconfigurationWithSync contains any additional fields not previously covered, then configure the lower layer based on those additional fields.

[0135] 5.3.5.5.8 SCell Release

[0136] UE should:

[0137] 1> If the release is triggered by the receive of sCellToReleaseList:

[0138] 2> For each sCellIndex value contained in sCellToReleaseList:

[0139] 3> If the current UE configuration contains an SCell with the value sCellIndex:

[0140] 4> Release SCell.

[0141] 5.3.5.5.9 SCell Additions / Modifications

[0142] UE should:

[0143] 1> For each sCellIndex value contained in sCellToAddModList that is not part of the current UE configuration (SCell addition):

[0144] 2> Based on sCellConfigCommon and sCellConfigDedicated, add an SCell corresponding to sCellIndex;

[0145] 2> If it contains sCellState:

[0146] 3> Configure the lower layer to assume that the SCell is active;

[0147] 2> Otherwise:

[0148] 3> Configure the lower layer to assume that the SCell is in a deactivated state;

[0149] 2> For each measId in the measIdList contained in VarMeasConfig:

[0150] 3> If SCell is not applicable to associated measurements; and

[0151] 3> If the relevant SCell is contained in cellsTriggeredList defined within VarMeasReportList for this measId:

[0152] 4> Remove the relevant SCell from the cellsTriggeredList defined within VarMeasReportList for this measId;

[0153] 1> For each sCellIndex value contained in sCellToAddModList and which is part of the current UE configuration (SCell modification):

[0154] 2> Modify the SCell configuration according to sCellConfigDedicated;

[0155] 2> If sCellToAddModList is received in an RRCReconfiguration message containing reconfigurationWithSync, or in an RRCReconfiguration message containing reconfigurationWithSync embedded in an RRCReconfiguration message, an E-UTRA RRCConnectionReconfiguration message, or an E-UTRA RRCConnectionResume message:

[0156] 3> If it contains sCellState:

[0157] 4> Configure the lower layer to assume that the SCell is active;

[0158] 3> Otherwise:

[0159] 4> Configure the lower layer to assume that SCell is in a deactivated state.

[0160] Cell group configuration, serving cell configuration, and / or advance timing group (TAG) configuration are described in 3GPP specification 38.331v16.6.0, one or more of which are cited below:

[0161] CellGroupConfig

[0162] The CellGroupConfig IE is used to configure a master cell group (MCG) or a secondary cell group (SCG). A cell group consists of a MAC entity, a set of logical channels with associated RLC entities, a master cell (SpCell), and one or more secondary cells (SCells).

[0163] CellGroupConfig information element

[0164] --Configuration of a cell group:

[0165]

[0166]

[0167] --SpCell's cell-specific MAC and PHY parameters:

[0168]

[0169]

[0170]

[0171]

[0172]

[0173]

[0174]

[0175]

[0176] MAC-CellGroupConfigIE is used to configure the MAC parameters of a cell group, including DRX.

[0177] MAC-CellGroupConfig information element

[0178]

[0179] }

[0180] DataInactivityTimer::=ENUMERATED{s1,s2,s3,s5,s7,s10,s15,s20,s40,s50,s60,s80,s100,s120,s150,s180}

[0181]

[0182] -CellGroupId

[0183] The IE CellGroupId is used to identify cell groups. A value of 0 identifies the primary cell group. Other values ​​identify secondary cell groups. In this version of the specification, only values ​​0 and 1 are supported.

[0184] CellGroupId information element

[0185] CellGroupId::=INTEGER(0..maxSecondaryCellGroups)

[0186] -CellIdentity

[0187] IE CellIdentity is used to explicitly identify cells within a PLMN / SNPN.

[0188] CellIdentity information element

[0189] CellIdentity::=BIT STRING(SIZE(36))

[0190] -ServCellIndex

[0191] The IE ServCellIndex relates to a short identity used to uniquely identify the serving cell (i.e., PCell, PSCell, or SCell) across cell groups. A value of 0 applies to PCells, while a previously assigned SCellIndex applies to SCells.

[0192] ServCellIndex information element

[0193] ServCellIndex::=INTEGER(0..maxNrofServingCells-1)

[0194] -ServingCellConfig

[0195] The IE ServingCellConfig is used to configure (add or modify) the UE and the serving cell, which can be an SpCell or SCell of an MCG or SCG. The parameters in this document are primarily UE-specific, but some are also cell-specific (e.g., in the bandwidth section of a separate configuration). Only SCells are used to release and add reconfiguration between SCells supporting PUCCH and those without PUCCH.

[0196] ServingCellConfig information element

[0197]

[0198]

[0199]

[0200]

[0201] TAG-Config is used to configure parameters for time alignment groups.

[0202] TAG-Config information element

[0203]

[0204]

[0205]

[0206] Random access procedures, timing advance, and / or timing alignment are described in 3GPP specification 38.321v16.6.0, one or more of which are cited below:

[0207] Timing Advance Group: A group of serving cells configured via RRC for cells with a configured UL, using the same timing reference cell and the same timing advance value. The timing advance group of a SpCell containing a MAC entity is called the Primary Timing Advance Group (PTAG), while the term Secondary Timing Advance Group (STAG) refers to other TAGs.

[0208] 5.1 Random Access Procedure

[0209] 5.1.1 Random Access Program Initialization

[0210] According to TS 38.300[2], the random access procedure described in this clause is initiated by a PDCCH command, the MAC entity itself, or an RRC of an event. In a MAC entity, there is only one in-progress random access procedure at any given time. The random access procedure on the SCell will be initiated solely by a PDCCH command where ra-PreambleIndex is different from 0b000000.

[0211] Note 1: If a new random access procedure is triggered while another random access procedure is already in progress in the MAC entity, then it will depend on the UE implementation scheme whether to continue the ongoing procedure or start a new procedure (e.g., for an SI request).

[0212] Note 2: If there is an ongoing random access procedure triggered by a PDCCH command when the UE receives another PDCCH command indicating the same random access preamble, PRACH mask index and uplink carrier, then the random access procedure is considered to be the same as the ongoing random access procedure and is not re-initialized.

[0213] When initiating a random access procedure for the serving cell, the MAC entity will:

[0214] 1> Clear the Msg3 buffer;

[0215] 1> Clear the MSGA buffer;

[0216] 1> Set PREAMBLE_TRANSMISSION_COUNTER to 1;

[0217] 1> Set PREAMBLE_POWER_RAMPING_COUNTER to 1;

[0218] 1> Set PREAMBLE_BACKOFF to 0ms;

[0219] 1> Set POWER_OFFSET_2STEP_RA to 0dB;

[0220] 1> If the carrier used for the random access procedure is transmitted explicitly:

[0221] 2> Select the transmitted carrier for performing the random access procedure;

[0222] 2> Set PCMAX to the PCMAX,f,c of the transmitted carrier.

[0223] 1> Otherwise, if the carrier used for the random access procedure is not explicitly transmitted; and

[0224] 1> If the serving cell used for the random access procedure is configured with a supplemental uplink as specified in TS 38.331[5]; and

[0225] 1> If the downlink path loss reference RSRP is less than rsrp-ThresholdSSB-SUL:

[0226] 2> Select the SUL carrier to perform the random access procedure;

[0227] 2> Set PCMAX to PCMAX,f,c with SUL carrier.

[0228] 1> Otherwise:

[0229] 2> Select an NUL carrier to perform random access procedures;

[0230] 2> Set PCMAX to PCMAX,f,c of NUL carrier.

[0231] 1> Perform the BWP operation as specified in Clause 5.15;

[0232] 1> If the random access procedure is initiated by a PDCCH command, and if the ra-PreambleIndex explicitly provided by the PDCCH is not 0b000000; or

[0233] 1> If a random access procedure is initiated for an SI request (as specified in TS 38.331[5]) and the random access resource for the SI request has been explicitly provided by the RRC; or

[0234] 1> If a random access procedure is initiated for SpCell beam fault recovery (as specified in Clause 5.17) and if the RRC has explicitly provided contention-free random access resources for a 4-step RA type beam fault recovery request for the BWP selected for the random access procedure; or

[0235] 1> If a random access procedure is initiated for a synchronous reconfiguration, and if a contention-free random access resource for a 4-step RA type has been explicitly provided in rach-ConfigDedicated for the BWP selected for the random access procedure:

[0236] 2> Set RA_TYPE to 4-stepRA.

[0237] 1> Otherwise, if the BWP selected for the random access procedure is configured to use 2-step and 4-step RA type random access resources and the downlink path loss reference RSRP is higher than msgA-RSRP-Threshold; or

[0238] 1> If the BWP selected for the random access procedure is only configured with 2-step RA type random access resources (i.e., 4-step RACH RA type resources are not configured); or

[0239] 1> If a random access procedure is initiated for a synchronous reconfiguration, and if a contention-free random access resource for a 2-step RA type has been explicitly provided in rach-ConfigDedicated for the BWP selected for the random access procedure:

[0240] 2> Set RA_TYPE to 2-stepRA.

[0241] 1> Otherwise:

[0242] 2> Set RA_TYPE to 4-stepRA.

[0243] 1> Perform initialization of variables specific to the random access type specified in Clause 5.1.1a;

[0244] 1> If RA_TYPE is set to 2-stepRA:

[0245] 2> Perform a random access resource selection procedure for the 2-step RA type (see Clause 5.1.2a).

[0246] 1> Otherwise:

[0247] 2> Perform the random access resource selection procedure (see Clause 5.1.2).

[0248] 5.1.2 Random Access Resource Selection

[0249] If the selected RA_TYPE is set to 4-step RA, then the MAC entity should:

[0250] 1> If a random access procedure is initiated for SpCell beam fault recovery (as specified in Clause 5.17); and

[0251] 1> If beamFailureRecoveryTimer (in Clause 5.17) is running or not configured; and

[0252] 1> If the contention-free random access resources for a beam fault recovery request associated with either the SSB or CSI-RS have been explicitly provided by the RRC; and

[0253] 1> If at least one of the SSBs in candidateBeamRSList with an SS-RSRP higher than rsrp-ThresholdSSB or a CSI-RS in candidateBeamRSList with a CSI-RSRP higher than rsrp-ThresholdCSI-RS is available:

[0254] 2> Select an SSB in the candidateBeamRSList that has an SS-RSRP higher than rsrp-ThresholdSSB or an SSB in the candidateBeamRSList that has a CSI-RSRP higher than rsrp-ThresholdCSI-RS.

[0255] 2> If CSI-RS is selected, and there is no ra-PreambleIndex associated with the selected CSI-RS:

[0256] 3> Set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the SSB in candidateBeamRSList, which is co-located with the selected CSI-RS quasi-as specified in TS 38.214[7].

[0257] 2> Otherwise:

[0258] 3> Set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the SSB or CSI-RS selected from a set of random access preambles used for beam fault recovery requests.

[0259] 1> Otherwise, if ra-PreambleIndex has been explicitly provided by PDCCH; and

[0260] 1> If ra-PreambleIndex is not 0b000000:

[0261] 2> Set PREAMBLE_INDEX to the transmitted ra-PreambleIndex;

[0262] 2> Select the SSB transmitted by PDCCH.

[0263] 1> Otherwise, if the contention-free random access resource associated with the SSB has been explicitly provided in rach-ConfigDedicated, and at least one of the associated SSBs with an SS-RSRP higher than rsrp-ThresholdSSB is available:

[0264] 2> Select the SSB with an SS-RSRP higher than that of the associated SSB;

[0265] 2> Set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected SSB.

[0266] 1> Otherwise, if the contention-free random access resource associated with the CSI-RS has been explicitly provided in rach-ConfigDedicated, and at least one CSI-RS with a CSI-RSRP higher than rsrp-ThresholdCSI-RS among the associated CSI-RSs is available:

[0267] 2> Select the CSI-RS with a higher CSI-RSRP than rsrp-ThresholdCSI-RS among the associated CSI-RS;

[0268] 2> Set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected CSI-RS.

[0269] 1> Otherwise, if a random access procedure is initiated for the SI request (as specified in TS 38.331[5]); and

[0270] 1> If the random access resources requested for the SI have been explicitly provided by RRC:

[0271] 2> If at least one of the SSBs with an SS-RSRP higher than rsrp-ThresholdSSB is available:

[0272] 3> Select an SSB with an SS-RSRP higher than rsrp-ThresholdSSB.

[0273] 2> Otherwise:

[0274] 3> Select any SSB.

[0275] 2> Select the random access preamble corresponding to the selected SSB from the random access preamble determined according to the ra-PreambleStartIndex specified in TS 38.331[5];

[0276] 2> Set PREAMBLE_INDEX to the selected random access preamble.

[0277] 1> Otherwise (i.e., for contention-based random access preamble selection):

[0278] 2> If at least one of the SSBs with an SS-RSRP higher than rsrp-ThresholdSSB is available:

[0279] 3> Select an SSB with an SS-RSRP higher than rsrp-ThresholdSSB.

[0280] 2> Otherwise:

[0281] 3> Select any SSB.

[0282] 2> If RA_TYPE is switched from 2-stepRA to 4-stepRA:

[0283] 3> If a random access preamble group was selected during the current random access procedure:

[0284] 4> Select the same random access preamble group as the one selected for the 2-step RA type.

[0285] 3> Otherwise:

[0286] 4> If random access preamble group B is configured; and

[0287] 4> If the transport block size of the MSGA payload configured in rach-ConfigDedicated corresponds to the transport block size of the MSGA payload associated with random access preamble group B:

[0288] 5> Select random access preamble group B.

[0289] 4> Otherwise:

[0290] 5> Select random access preamble group A.

[0291] 2> Otherwise, if the Msg3 buffer is empty:

[0292] 3> If random access preamble group B is configured:

[0293] 4> If the potential Msg3 size (e.g., the UL data that can be transmitted plus the MAC sub-header and, if necessary, the MAC CE) is greater than ra-Msg3SizeGroupA and the path loss is less than (the serving cell performing the random access procedure) PCMAX-preambleReceivedTargetPower-msg3-DeltaPreamble-messagePowerOffsetGroupB; or

[0294] 4> If a random access procedure is initiated for the CCCH logical channel and the CCCH SDU size plus the MAC sub-header is greater than ra-Msg3SizeGroupA:

[0295] 5> Select random access preamble group B.

[0296] 4> Otherwise:

[0297] 5> Select random access preamble group A.

[0298] 3> Otherwise:

[0299] 4> Select random access preamble group A.

[0300] 2> Otherwise (i.e., Msg3 is retransmitted):

[0301] 3> Select the same random access preamble group as the random access preamble transmission attempt used for the first transmission corresponding to Msg3.

[0302] 2> Random access preambles are randomly selected from those associated with the selected SSB and the selected random access preamble group with equal probability;

[0303] 2> Set PREAMBLE_INDEX to the selected random access preamble.

[0304] 1> If a random access procedure is initiated for an SI request (as specified in TS 38.331[5]); and

[0305] 1> If ra-AssociationPeriodIndex and si-RequestPeriod are configured:

[0306] 2> The next available PRACH opportunity is determined from the PRACH opportunity corresponding to the selected SSB within the association period given by the ra-AssociationPeriodIndex in the si-RequestPeriod permitted by the restrictions given by ra-ssb-OccasionMaskIndex (if configured) (the MAC entity will randomly select a PRACH opportunity with equal probability from consecutive PRACH opportunities according to Clause 8.1 of TS 38.213[6] corresponding to the selected SSB).

[0307] 1> Otherwise, if SSB is selected as above:

[0308] 2> The next available PRACH timing is determined based on the PRACH timing corresponding to the selected SSB as permitted by the limits given by ra-ssb-OccasionMaskIndex (if configured) or indicated by PDCCH (the MAC entity will randomly select the PRACH timing with equal probability from the consecutive PRACH timings corresponding to the selected SSB in accordance with Clause 8.1 of TS 38.213[6]; the MAC entity may take into account the possibility of measurement gaps when determining the next available PRACH timing corresponding to the selected SSB).

[0309] 1> Otherwise, if CSI-RS is selected above:

[0310] 2> If no contention-free random access resource is associated with the selected CSI-RS:

[0311] 3> The next available PRACH timing is determined based on the PRACH timing of the candidateBeamRSList corresponding to the selected CSI-RS quasi-co-located candidateBeamRSList as specified in TS 38.214[7], as permitted by the restrictions given by ra-ssb-OccasionMaskIndex (if configured). (The MAC entity will randomly select a PRACH timing with equal probability from the consecutive PRACH timings corresponding to the selected CSI-RS quasi-co-located SSB in accordance with Clause 8.1 of TS 38.213[6]; the MAC entity may take into account the possibility of measurement gaps when determining the next available PRACH timing corresponding to the selected CSI-RS quasi-co-located SSB).

[0312] 2> Otherwise:

[0313] 3> Determine the next available PRACH timing based on the PRACH timing corresponding to the selected CSI-RS in the ra-OccasionList (the MAC entity will randomly select the PRACH timing from the PRACH timings corresponding to the selected CSI-RS that occur simultaneously but on different subcarriers with equal probability; the MAC entity may consider the possibility of measurement gaps when determining the next available PRACH timing corresponding to the selected CSI-RS).

[0314] 1> Execute the random access preamble transmission procedure (see Clause 5.1.3).

[0315] Note 1: When the UE determines whether there is an SSB with SS-RSRP higher than rsrp-ThresholdSSB or a CSI-RS with CSI-RSRP higher than rsrp-ThresholdCSI-RS, the UE uses the latest unfiltered L1-RSRP measurement.

[0316] Note 2: Invalid.

[0317] 5.1.3 Random Access Preamble Transmission

[0318] For each random access preamble, the MAC entity will:

[0319] 1> If PREAMBLE_TRANSMISSION_COUNTER is greater than one; and

[0320] 1> If a notification to pause the power ramp counter has not yet been received from the lower layer; and

[0321] 1> If no LBT fault indication is received from the lower layer for the last random access preamble transmission; and

[0322] 1> If the selected SSB or CSI-RS was not changed from the last random access preamble transmission:

[0323] 2> Increase PREAMBLE_POWER_RAMPING_COUNTER by 1.

[0324] 1> Select the value of DELTA_PREAMBLE according to clause 7.3;

[0325] 1>Set PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower+DELTA_PREAMBLE+(PREAMBLE_POWER_RAMPING_COUNTER-1)×PREAMBLE_POWER_RAMPING_STEP+POWER_OFFSET_2STEP_RA;

[0326] 1> Except for the contention-free random access preamble used for beam fault recovery requests, calculate the RA-RNTI associated with the PRACH timing in which the random access preamble is transmitted.

[0327] 1> Instruct the physical layer to use the selected PRACH timing, the corresponding RA-RNTI (if available), PREAMBLE_INDEX, and PREAMBLE_RECEIVED_TARGET_POWER to transmit the random access preamble.

[0328] 5.1.4 Random Access Response Reception

[0329] Once the random access preamble is transmitted, the MAC entity will: regardless of whether a measurement gap is possible.

[0330] 1> If the contention-free random access preamble used for beam fault recovery requests is transmitted by the MAC entity:

[0331] 2> Starting from the end of the random access preamble transmission, as specified in TS 38.213[6], the ra-ResponseWindow configured in BeamFailureRecoveryConfig begins at the first PDCCH timing;

[0332] 2> When ra-ResponseWindow is running, listen for PDCCH transmissions on the search space indicated by the recoverySearchSpaceId of the SpCell identified by C-RNTI.

[0333] 1> Otherwise:

[0334] 2> Starting from the end of the random access preamble transmission, as specified in TS 38.213[6], the ra-ResponseWindow configured in RACH-ConfigCommon will begin at the first PDCCH timing;

[0335] 2> When ra-ResponseWindow is running, listen for the PDCCH of the SpCell that receives a random access response identified by RA-RNTI.

[0336] 1> If the lower layer on the serving cell from which the preamble is transmitted receives a notification that a PDCCH transmission has been received in the search space indicated by recoverySearchSpaceId; and

[0337] 1> If the PDCCH transmission is addressed to C-RNTI; and

[0338] 1> If the contention-free random access preamble used for beam fault recovery requests is transmitted by the MAC entity:

[0339] 2> The random access procedure is considered to have been successfully completed.

[0340] 1> Otherwise, if a valid downlink allocation (as specified in TS 38.213[6]) has been received on the PDCCH for RA-RNTI, and the received TB has been successfully decoded:

[0341] 2> If the random access response contains a MAC sub-PDU with a backoff indicator:

[0342] 3> Use Table 7.2-1 to set PREAMBLE_BACKOFF to the value of the BI field of the MAC sub-PDU by multiplying it by SCALING_FACTOR_BI.

[0343] 2> Otherwise:

[0344] 3> Set PREAMBLE_BACKOFF to 0ms.

[0345] 2> If the random access response contains a MAC sub-PDU with a random access preamble identifier corresponding to the transmitted PREAMBLE_INDEX (see Clause 5.1.3):

[0346] 3> This random access response is considered to have been successfully received.

[0347] 2> If the random access response is considered to have been successfully received:

[0348] 3> If the random access response contains a MAC sub-PDU with only RAPID:

[0349] 4> This random access procedure is considered to have completed successfully;

[0350] 4> Indicate to the upper layer that an acknowledgment has been received regarding the SI request.

[0351] 3> Otherwise:

[0352] 4> Apply the following actions to the serving cell that transmits the random access preamble:

[0353] 5. Process received timing advance commands (see Clause 5.2);

[0354] 5> Indicate the preambleReceivedTargetPower and the power slack variable applied to the latest random access preamble transmission to the lower layer (i.e., (PREAMBLE_POWER_RAMPING_COUNTER-1)×PREAMBLE_POWER_RAMPING_STEP);

[0355] 5> If a random access procedure for SCell is performed on an uplink carrier that is not configured with pusch-Config:

[0356] 6> Ignore the received UL approval.

[0357] 5> Otherwise:

[0358] 6> Process the received UL grant value and indicate the value to the lower layer.

[0359] 4> If the MAC entity does not select a random access preamble from the contention-based random access preamble:

[0360] 5> The random access procedure is considered to have been successfully completed.

[0361] 4> Otherwise:

[0362] 5> Set TEMPORARY_C-RNTI to the value received in the random access response;

[0363] 5> If this is the first successfully received random access response within this random access procedure:

[0364] 6> If no transmission is made for the CCCH logical channel:

[0365] 7> The multiplexing and aggregation entity indication includes C-RNTI MAC CE in subsequent uplink transmissions.

[0366] 6> If a random access procedure is initiated for SpCell beam fault recovery and the configuration value of spCell-BFR-CBRA is true:

[0367] 7> Indicate to the multiplexing and aggregation entity that a BFR MAC CE or a truncated BFR MAC CE is included in subsequent uplink transmissions.

[0368] 6> Obtain the MAC PDU to transfer from the multiplexed and aggregated entity and store it in the Msg3 buffer.

[0369] 5.1.5 Dispute Resolution

[0370] Once Msg3 is transmitted, the MAC entity will:

[0371] 1> For each HARQ retransmission in the first symbol after Msg3 transmission ends, start ra-ContentionResolutionTimer and restart ra-ContentionResolutionTimer;

[0372] 1> Regardless of whether a measurement gap is possible, listen to the PDCCH while the ra-ContentionResolutionTimer is running;

[0373] 1> If a notification of receiving a PDCCH transmission from SpCell is received from the lower layer:

[0374] 2> If C-RNTI MAC CE is included in Msg3:

[0375] 3> If a random access procedure is initiated for SpCell beam fault recovery (as specified in Clause 5.17) and the PDCCH transmission is addressed to C-RNTI; or

[0376] 3> If a random access procedure is initiated via a PDCCH command and the PDCCH transmission is addressed to C-RNTI; or

[0377] 3> If a random access procedure is initiated by the MAC sublayer itself or by the RRC sublayer and the PDCCH transmission addresses to the C-RNTI and contains UL permission for the new transmission:

[0378] 4> Consider this dispute resolved successfully;

[0379] 4>Stop ra-ContentionResolutionTimer;

[0380] 4> Discard TEMPORARY_C-RNTI;

[0381] 4> This random access procedure is considered to have been successfully completed.

[0382] 2> Otherwise, if the CCCH SDU is contained in Msg3 and the PDCCH transport is addressed to its TEMPORARY_C-RNTI:

[0383] 3> If the MAC PDU is successfully decoded:

[0384] 4>Stop ra-ContentionResolutionTimer;

[0385] 4> If the MAC PDU contains the UE contention resolution identity MAC CE; and

[0386] 4> If the UE contention in the MAC CE resolves the identity matching of the CCCH SDU transmitted in Msg3:

[0387] 5> It is considered that this contention has been successfully resolved and the disassembly and multiplexing of the MAC PDU has ended;

[0388] 5> If this random access procedure is initiated in response to an SI request:

[0389] 6> Indicate to the upper layer that an acknowledgment has been received regarding the SI request.

[0390] 5> Otherwise:

[0391] 6> Set C-RNTI to the value of TEMPORARY_C-RNTI;

[0392] 5> Discard TEMPORARY_C-RNTI;

[0393] 5> This random access procedure is considered to have been successfully completed.

[0394] 4> Otherwise:

[0395] 5> Discard TEMPORARY_C-RNTI;

[0396] 5> The contention is considered unsuccessful and the successfully decoded MAC PDU is discarded.

[0397] …

[0398] 5.1.6 Complete the random access procedure

[0399] After the random access procedure is completed, the MAC entity will:

[0400] 1> Discard any contention-free random access resources explicitly transmitted for 2-step RA type and 4-step RA type, except for 4-step RA type contention-free random access resources (if present) for beam failure recovery requests.

[0401] 1> Clear the HARQ buffers used for transmitting MAC PDUs in the Msg3 and MSGA buffers.

[0402] Upon successful completion of the random access procedure initiated in response to the DAPS handover, the target MAC entity will:

[0403] 1> Indicate to the upper layer that the random access procedure has been successfully completed.

[0404] 5.2 Uplink Time Alignment Maintenance

[0405] The RRC configuration uses the following parameters to maintain UL time alignment:

[0406] -timeAlignmentTimer(per TAG) controls how long the MAC entity considers a serving cell belonging to the associated TAG to need uplink time alignment.

[0407] MAC entities will:

[0408] 1> When the timing advance command MAC CE is received, and if the NTA has been maintained with the indicated TAG (as defined in TS 38.211[8]):

[0409] 2> Advance command for the indicated TAG application timing;

[0410] 2> Start or restart the timeAlignmentTimer associated with the indicated TAG.

[0411] 1> When a timing advance command is received in the random access response message for the serving cell belonging to the TAG or in the MSGB for SpCell:

[0412] 2> If the MAC entity does not select a random access preamble from the contention-based random access preamble:

[0413] 3> Advance command for the timing of this TAG application;

[0414] 3> Start or restart the timeAlignmentTimer associated with this TAG.

[0415] 2> Otherwise, if the timeAlignmentTimer associated with this TAG is not running:

[0416] 3> Advance command for the timing of this TAG application;

[0417] 3> Start the timeAlignmentTimer associated with this TAG;

[0418] 3> When dispute resolution is deemed unsuccessful as described in Clause 5.1.5; or

[0419] 3> When, after transmitting the HARQ feedback for the MAC PDU containing the UE contention resolution identity MAC CE, the contention resolution is considered successful for the SI request as described in Clause 5.1.5:

[0420] 4> Stop the timeAlignmentTimer associated with this TAG.

[0421] 2> Otherwise:

[0422] 3> Ignore the received timing command.

[0423] 1> When an absolute timing advance command is received in response to an MSGA transmission containing C-RNTI MAC CE as specified in Clause 5.1.4a:

[0424] 2> Advance commands for PTAG application timing;

[0425] 2> Start or restart the timeAlignmentTimer associated with PTAG.

[0426] 1> When the timeAlignmentTimer expires:

[0427] 2> If timeAlignmentTimer is associated with PTAG:

[0428] 3. Clear all HARQ buffers for all serving cells;

[0429] 3> Notify RRC to release PUCCHs used for all serving cells (if configured);

[0430] 3> Notify RRC to release SRS for all serving cells (if configured);

[0431] 3> Clear any configured downlink allocations and configured uplink permissions;

[0432] 3> Remove any PUSCH resources used for semi-static CSI reporting;

[0433] 3> It is assumed that all running timeAlignmentTimers have expired;

[0434] 3> Maintain the NTA for all TAGs (defined in TS 38.211[8]).

[0435] 2> Otherwise, if timeAlignmentTimer is associated with STAG, then all serving cells belong to this TAG:

[0436] 3> Clear all HARQ buffers;

[0437] 3> Notify RRC to release PUCCH (if configured);

[0438] 3> Notify RRC to release SRS (if configured);

[0439] 3> Clear any configured downlink allocations and configured uplink permissions;

[0440] 3> Remove any PUSCH resources used for semi-static CSI reporting;

[0441] 3> Maintain the NTA of this TAG (as defined in TS 38.211[8]).

[0442] When a MAC entity stops uplink transmission of an SCell due to the maximum uplink transmission timing difference between MAC entity TAGs or the fact that the maximum uplink transmission timing difference between any MAC entity TAGs of the UE has been exceeded, the MAC entity considers the timeAlignmentTimer associated with the SCell to have expired.

[0443] When the timeAlignmentTimer associated with the TAG to which the serving cell belongs is not running, the MAC entity will not perform any uplink transmissions on the serving cell, except for the random access preamble and MSGA transmissions. Furthermore, when the timeAlignmentTimer associated with the PTAG is not running, the MAC entity will not perform any uplink transmissions on any serving cell, except for the random access preamble and MSGA transmissions on the SpCell.

[0444] 5.9 SCell Activation / Deactivation

[0445] If a MAC entity is configured with one or more SCells, then network activation and deactivation are configured for each SCell. After a SCell is configured, it is deactivated unless the sCellState parameter is set to activate for that SCell by the upper layer.

[0446] Activate and deactivate the configured SCell using the following operations:

[0447] - Receive the SCell activation / deactivation MAC CE as described in Clause 6.1.3.10;

[0448] - Configure an sCellDeactivationTimer for each configured SCell (except for SCells configured with PUCCH (if they exist)): Deactivate the associated SCell when the timer expires;

[0449] - Each configured SCell configures sCellState: If configured, the associated SCell is activated after the SCell is configured.

[0450] The MAC entity will target each configured SCell:

[0451] 1> If the SCell is configured with sCellState set to be activated immediately after the SCell is configured, or if a SCell activation / deactivation MAC CE is received to activate the SCell:

[0452] 2> If you want to revoke the activation of the SCell before receiving this SCell activation / revocation MAC CE; or

[0453] 2> If the SCell is configured to use sCellState, which is set to be activated after the SCell is configured:

[0454] 3> If firstActiveDownlinkBWP-Id is not set to a dormant BWP:

[0455] 4> Activate the SCell according to the timing restrictions for MAC CE activation in TS 38.213[6] and the timing restrictions for direct SCell activation in TS 38.133

[11] ; that is, apply normal SCell operation, including:

[0456] 5> SRS transmission on SCell;

[0457] 5> CSI report for SCell;

[0458] 5> PDCCH monitoring on SCell;

[0459] 5> SCell PDCCH monitoring;

[0460] 5> PUCCH transmission on SCell (if configured).

[0461] 3> Otherwise (i.e., firstActiveDownlinkBWP-Id is set to the dormant BWP):

[0462] 4> Stop the bwp-InactivityTimer for this serving cell (if it is running).

[0463] 3> Activate the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id respectively.

[0464] 2> Start or restart the sCellDeactivationTimer associated with the SCell according to the timing restrictions for MAC CE activation in TS 38.213[6] and the timing restrictions for direct SCell activation in TS 38.133

[11] ;

[0465] 2> If the active DL BWP is not a dormant BWP:

[0466] 3> Re-initialize any suspended configured uplink permissions of configured permission type 1 associated with this SCell according to the stored configuration (if it exists), and begin in the symbol of the rule in accordance with clause 5.8.2;

[0467] 3> PHR is triggered according to clause 5.4.6.

[0468] 1> Otherwise, if a SCell activation / deactivation MAC CE is received to revoke the activation of the SCell; or

[0469] 1> If the sCellDeactivationTimer associated with activating the SCell expires:

[0470] 2> Revoke the activation of the SCell according to the timing defined in TS 38.213[6];

[0471] 2> Stop the sCellDeactivationTimer associated with SCell;

[0472] 2> Stop the bwp-InactivityTimer associated with SCell;

[0473] 2> Revoke the activation of any BWP activity associated with SCell;

[0474] 2> Clear any configured downlink assignments and any configured uplink permission type 2 associated with SCell respectively;

[0475] 2> Clear any PUSCH resources used for semi-static CSI reports associated with SCell;

[0476] 2> Suspend any configured uplink permission type 1 associated with SCell;

[0477] 2> Clear all HARQ buffers associated with SCell;

[0478] 2> If it exists, cancel the triggered consistent LBT fault of SCell.

[0479] 1> If the PDCCH on the activated SCell indicates uplink grant or downlink allocation; or

[0480] 1> If the PDCCH indication on the serving cell of the activated SCell is used for uplink granting or downlink allocation of the activated SCell; or

[0481] 1> If the MAC PDU is transmitted in the configured uplink permission and no LBT fault indication is received from the lower layer; or

[0482] 1> If the MAC PDU is received in a configured downlink allocation:

[0483] 2> Restart the sCellDeactivationTimer associated with SCell.

[0484] 1> If SCell is deactivated:

[0485] 2> Do not transmit SRS on SCell;

[0486] 2> CSI is not reported for SCell;

[0487] 2> No transmission on UL-SCH on SCell;

[0488] 2> No transmission on the RACH on the SCell;

[0489] 2> Do not listen to PDCCH on SCell;

[0490] 2> Do not monitor PDCCH for SCell;

[0491] 2> Do not transmit PUCCH on SCell.

[0492] In TS 38.133

[11] , the HARQ feedback of a MAC PDU containing SCell activation / deactivation activation of a MAC CE will not be affected by PCell, PSCell, and PUCCH SCell interruptions caused by SCell activation / deactivation.

[0493] When SCell is reactivated, the random access procedure in progress on SCell (if it exists) is aborted.

[0494] The timing of this discussion in 3GPP specification 38.211v16.7.0 is earlier than expected. It's worth noting that section 4.3.1 of 3GPP specification 38.211v16.7.0 is titled "Uplink-Downlink Timing Relationship". Figure 4 .3.1-1 is reproduced in this article as Figure 5 One or more parts of 3GPP specification 38.211v16.7.0 are quoted below:

[0495] 3.2 Symbols

[0496] The timing between NTA downlink and uplink is advanced; see Clause 4.3.1

[0497] NTA,offset is used to calculate the fixed offset for timing advancement; see Clause 4.3.1

[0498] 4.3 Frame Structure

[0499] 4.3.1 Frames and Subframes

[0500] Downlink, uplink, and sidelink transmissions are organized into a T f =(Δf max N f / 100)·T c = A frame with a duration of 10ms, each frame consisting of T sf =(Δf max N f / 1000)·T c It consists of ten subframes with a duration of 1 ms. The number of consecutive OFDM symbols in each subframe is... Each frame is divided into two equal half-frames consisting of five subframes, each having half-frame 0 composed of subframes 0-4 and half-frame 1 composed of subframes 5-9.

[0501] On a carrier, there is one set of frames in the uplink and one set of frames in the downlink.

[0502] The number of uplink frames i to be transmitted from the UE will start T before the corresponding downlink frame begins at the UE. TA =(N TA +N TA,offset )T c , where N TA,offset As given in [5, TS 38.213], except for the transmission of msgA on the PUSCH where NTA = 0.

[0503] Figure 4 3.1-1: Uplink-Downlink Timing Relationship.

[0504] 4.3.2 Time Slot

[0505] For the subcarrier spacing configuration μ, the time slots are numbered in ascending order within the subframe. And within the frame, they are numbered in ascending order. Existing in time slots 1 consecutive OFDM symbol, of which Depends on the cyclic prefix given in Tables 4.3.2-1 and 4.3.2-2. Time slots in subframes. The beginning is temporally related to the OFDM symbol in the same subframe. The beginning is aligned.

[0506] OFDM symbols in time slots within downlink or uplink frames can be classified as 'downlink', 'flexible', or 'uplink'. The transmission of time slot formats is described in Clause 11.1 of [5, TS 38.213].

[0507] In the time slots of a downlink frame, the UE will assume that downlink transmissions occur only in the 'downlink' or 'flexible' symbols.

[0508] In the time slots of the uplink frame, the UE will only transmit in the 'uplink' or 'flexible' symbols.

[0509] In NR, a UE can perform a handover procedure to switch from one cell to another. The UE performs the handover procedure in response to Radio Resource Control (RRC) signaling transmitted by the network. The RRC signaling includes cell information of the target cell. The network determines to initiate the handover procedure based on the UE's measurement report. Changing the primary cell (PCell) and / or PSCell via synchronous reconfiguration (e.g., involving Layer 3 (L3) RRC messages) can involve higher latency and / or more overhead compared to Layer 1 (L1) / Layer 2 (L2) signaling (e.g., beam switching mobility). Alternatively and / or additionally, frequent secondary cell group (SCG) changes will occur during operation in Frequency Range 2 (FR2), which can also lead to high latency in UE-NW communication when using L3 handover. In this disclosure, the term "PSCell" may refer to the primary SCG cell and / or primary and secondary cells. Therefore, in the WID for further mobility enhancement of the NR provided in RP-212710, the objective of the work item may be to specify a mechanism and / or procedure for dynamic handover in the serving cell, which includes one or more special cells (SpCells) and / or one or more subcells (SCells) based on L1 / L2 signaling. In this disclosure, the term "L1 / L2" may refer to L1 and / or L2.

[0510] Figure 6This describes scenario 600, which relates to a UE, a first cell "Cell 0", and a second cell "Cell 1". The UE may receive first information 610 (e.g., a step 1 RRC message) from Cell 0, including Cell 1 configuration. The UE may establish an RRC connection with Cell 0. Cell 1 configuration may include the serving cell configuration of Cell 1. Cell 1 may be a neighboring cell, SCell, or PCell of the UE. The UE may transmit an L1 / L3 measurement report 616 to Cell 0 (e.g., the L1 / L3 measurement report 616 may include measurements associated with Cell 1). Cell 0 may transmit second information 622 (e.g., a step 3 Downlink Control Information (DCI) or Medium Access Control (MAC) Control Element (CE)) to the UE for initiating a mobility procedure associated with Cell 1. In response to receiving the second information 622, the UE may initiate and / or execute a mobility procedure 626 associated with Cell 1. Corresponding to various settings of information (e.g., first information 610 and / or second information 622) and / or procedures (e.g., procedures), the UE may perform one or more procedures on cell 1 (e.g., SCell addition and / or SCell release; PCell handover, etc.). The UE may regard cell 1 as a PCell or SCell (in, for example, a Master Cell Group (MCG) or SCG) in response to completing a mobility procedure (and / or in response to receiving the second information). For communications via cell (e.g., cell 1), the UE may need to obtain and / or maintain Timing Advance (TA) (and / or time alignment) associated with cell 1. Depending on some system and / or procedure, the UE obtains TA information (e.g., timing advance command) of SCells in the timing advance group (TAG) in the random access response during a network-initiated random access procedure (e.g., a random access procedure may be initiated via a PDCCH command). In some instances, in L1 / L2 mobility procedures associated with adding and / or changing SCells, a random access procedure may not be present and / or a timing advance command provided in the random access response may not be present. This disclosure discusses methods and procedures for achieving maintenance time alignment in L1 / L2 mobility for SCell and / or SCG handover.

[0511] The concept of this disclosure is that a UE can receive first information including one or more configurations of one or more cells. The UE can receive second information indicating to the UE an index / identity associated with at least one of the one or more cells. In this disclosure, the term "index / identity" may correspond to an index and / or an identity (id). The second information may not include (e.g., may not indicate) one or more configurations of the one or more cells. The second information may instruct the UE (e.g., instruct the UE) to initiate a mobility procedure (e.g., the second information may include signaling for initiating a mobility procedure and / or may include information about the mobility procedure, such as information necessary to perform the mobility procedure). The UE may initiate a mobility procedure in response to receiving the second information. The UE may not initiate a mobility procedure in response to receiving the first information. Alternatively and / or additionally, the UE may consider a first cell (e.g., at least one cell) of the one or more cells as its serving cell in response to completing a mobility procedure initiated in response to receiving the second information. The UE may not consider the first cell of the one or more cells as its serving cell in response to receiving the first information (and / or before performing and / or completing a mobility procedure initiated in response to receiving the second information).

[0512] The first and second information can be transmitted in different signaling messages. In this disclosure, the term "signaling" may correspond to at least one of a signal, a set of signals, a transmission, a message, etc.

[0513] The first and second information may be transmitted at different times. In this disclosure, the term "time" may correspond to at least one of time, time period, time unit, time slot, symbol, etc.

[0514] One or more configurations may contain serving cell configurations.

[0515] Example 1

[0516] In Example 1, the first information may indicate timing advance information associated with the SCell (e.g., the first information may indicate timing advance information per TAG, per cell, etc.).

[0517] In some instances, the first information indicates the timing lead time for a set of cells (e.g., per TAG). For example, the first information may indicate an existing TAG (and / or a TAG ID associated with an existing TAG) associated with the set of cells. For example, the first information indicates the timing lead time for a set of cells (e.g., per TAG) by indicating an existing TAG (and / or by indicating a TAG ID associated with an existing TAG).

[0518] The first information (received by the UE) may indicate one or more first sets of cells (e.g., CellGroupConfig). In this disclosure, the term "cell set" may correspond to a set of cells and / or CGs, wherein the set of cells and / or CGs may include one or more cells and / or one or more CGs. Each of the one or more first sets may include one or more cells and / or one or more CGs. Each of the one or more first sets may include SpCells associated with the UE (e.g., PCells and / or PSCells) (e.g., SpCells may be in a primary cell group (MCG) associated with the UE or in an SCG associated with the UE). Each of the one or more first sets may include one or more SCells associated with the UE (e.g., one or more SCells may be in an MCG or in an SCG). The first information may indicate a cell configuration associated with each of the cells (e.g., ServingCellConfig) (e.g., for each cell in the one or more first sets, the first information may indicate the cell configuration associated with the cell). Each of the one or more first sets may include one or more neighboring cells associated with the UE. Each of the one or more first sets may include one or more non-serving cells of the UE (e.g., one or more non-serving cells may correspond to one or more cells associated with one or more Physical Cell Identifiers (PCIs) that are different from one or more serving cells). Each of the one or more first sets may be a candidate cell group or candidate cell set for the UE to perform mobility procedures and / or L1 / L2 mobility. Alternatively and / or additionally, the first information may indicate the configuration of each of the one or more first sets of cells (e.g., CellGroupConfig).

[0519] Each of one or more first sets may be associated with a TAG (e.g., a current and / or existing TAG) (e.g., may include and / or indicate the TAG). For example, each of one or more first sets may be associated with a TAG id (e.g., TAG-Id). A TAG id may be associated with a Primary Timing Advance Group (pTAG) of an MCG (e.g., a UE), a Secondary Timing Advance Group (sTAG) of an MCG (e.g., a UE), a pTAG of an SCG, or an sTAG of an SCG. A TAG id may be associated with an effective timing advance value (e.g., NTA) that is associated with a pTAG or sTAG (e.g., an existing pTAG or an existing sTAG).

[0520] In response to (i) initiating or completing a mobility procedure associated with a first cell set (e.g., a first set of one or more cells) in a first set of cells to be added / activated and / or (ii) receiving a second message (and / or when said operation occurs), the UE may apply, configure, and / or set a TAG id (e.g., tag-Id) for the first cell set based on an indication of the TAG id (e.g., in the first message). In this disclosure, the term "add / activate" may refer to adding and / or activating. In some instances, if the first cell set is associated with a TAG id that is the same as a current and / or existing TAG (e.g., a TAG that the UE has configured and / or activated before and / or after receiving the second message) (e.g., configured and / or indicated to be associated with said TAG id) (and / or when the first cell set is associated with said TAG id), then the UE may, in response to receiving the second message (and / or after receiving the second message), not perform a random access procedure (e.g., to obtain a timing advance value for the first cell set). In response to (i) initiating or completing a mobility procedure and / or (ii) receiving second information (and / or when said operation occurs), the UE may apply a timing advance value (e.g., NTA) associated with the current and / or existing TAGs (which, for example, have the same TAG id) to the first cell set (e.g., the UE may apply the timing advance value after adding / activating the first cell set and / or when adding / activating the first cell set). The UE may initiate (and / or restart) the timeAlignmentTimer associated with the current and / or existing TAGs in response to applying the timing advance value.

[0521] Example 2

[0522] In Example 2, the UE may release one or more current and / or existing TAG cells that are not in the first cell set.

[0523] In some instances, in response to (i) initiating or completing a mobility procedure associated with adding / activating a first set of cells (one or more in a first set) associated with a TAG id (e.g., indicated in the first information) and / or (ii) receiving a second information (and / or when said operation), the UE may release / remove / revoke activation of one or more cells (e.g., SCells) that are (i) not indicated in the first set of cells (and / or not indicated in the first or second information) and (ii) associated with the same TAG id (e.g., indicated by the first information as the same TAG id associated with the first set of cells). In this disclosure, the term “release / remove / revoke activation” may refer to the release, removal, and / or revocation of activation (e.g., the release, removal, and / or revocation of activated cells). Alternatively and / or additionally, in response to (i) initiating or completing a mobility procedure associated with adding / activating a first set of cells associated with a TAG id (e.g., indicated in the first information) and / or (ii) receiving a second information (and / or when said operation), the UE may release / remove / revoke activation of cells (e.g., SCells) in the first set of cells that are not indicated (and / or not indicated in the first information).

[0524] Example 3

[0525] In Embodiment 3, the first information may indicate the timing lead time for the cell set (e.g., per TAG). For example, the first information may indicate a new TAG (and / or a TAG id associated with the new TAG) associated with the cell set.

[0526] In some instances, a cell set may be associated with a first TAG ID that is different from the current and / or existing TAG IDs of one or more cell groups of the UE (e.g., when the cell set does not share the same timing advance value with any of the one or more existing cell groups). First information and / or second information may indicate the first TAG ID. The first TAG ID can be used to indicate that one or more cells associated with the first TAG ID share the same timing advance value. Different sets within one or more first sets (e.g., one or more first sets of cells indicated by the first information) may share and / or be associated with the same TAG ID. Alternatively and / or additionally, different sets within one or more first sets may be associated with different TAG IDs.

[0527] In response to (i) initiating or completing a mobility procedure associated with one or more cells in a second cell set from a first set of cells being added / activated and / or (ii) receiving second information (and / or when said operation occurs), the UE may apply, configure, and / or set a TAG ID (e.g., tag-Id) for the second cell set based on a first TAG ID (e.g., as indicated in the first information). For example, the applied, configured, and / or set TAG ID for the second cell set may be the same as the first TAG ID. Alternatively, the UE may apply, configure, and / or set a second cell set having a TAG associated with a TAG ID different from the first TAG ID indicated in the first information. In some instances, the UE may apply, configure, and / or set cells in the same set having the same TAG. If the second cell set is associated with one, some, or all of one or more TAG IDs that are different from the current and / or existing TAGs (e.g., TAGs that the UE uses and / or configures before and / or after receiving the second information) (e.g., TAGs that are configured and / or indicated to be associated with said TAG ID) (and / or when the second cell set is associated with said TAG ID), then the UE may perform a random access procedure (e.g., to obtain an advance value for the timing of the second cell set) in response to receiving the second information (and / or after receiving the second information).

[0528] Example 4

[0529] In Example 4, one or more current and / or existing cells associated with a TAG may be replaced with one or more cells associated with a new TAG.

[0530] In some instances, the UE may replace one or more current and / or existing cells associated with the first TAG id with one or more new cells associated with the second TAG id indicated in the first and / or second information. The UE may replace one or more current and / or existing cells with one or more new cells in response to (i) receiving the second information and / or (ii) initiating or completing a mobility procedure (and / or when said operation). The second information may instruct the UE (e.g., instruct the UE) to add / activate one or more new cells. The one or more new cells may be associated with the same TAG (e.g., the same TAG indicated by the first and / or second information). The one or more new cells may be associated with a TAG of the same type as the TAG of one or more current and / or existing cells (e.g., a pTAG or sTAG of an MCG or SCG). The type of TAG may be indicated by the first and / or second information. In response to adding / activating one or more new cells, the UE may allocate and / or apply one or more new cells with the first TAG id (as a new TAG id for the serving cell). The UE may apply a timing advance value associated with one or more current and / or existing cells to one or more new cells. Alternatively or additionally, the UE may apply a different timing advance value (different from the timing advance value of one or more current and / or existing cells) to one or more new cells. The UE may determine whether to apply the timing advance value associated with one or more current and / or existing cells to one or more new cells based on whether current and / or existing cells in the activation TAG are released / removed / deactivated (e.g., based on whether all current and / or existing cells in the activation TAG are released / removed / deactivated). The UE may determine whether to apply the timing advance value associated with one or more current and / or existing cells to one or more new cells based on the indication in the second information. If at least one of the one or more current and / or existing cells is not released / removed / deactivated (and / or when at least one of the one or more current and / or existing cells is not released / removed / deactivated), then the UE may apply the timing advance value associated with one or more current and / or existing cells to one or more new cells. If one or more current and / or existing cells (e.g., all or all current and / or existing cells) are released / removed / deactivated (and / or when said one or more current and / or existing cells are released / removed / deactivated), then the UE may not apply the timing advance value associated with one or more current and / or existing cells to one or more new cells. One or more current and / or existing cells in the activation TAG (e.g., all current and / or existing cells in the TAG) may be released / removed / deactivated in response to second information.If the timing advance value associated with one or more current and / or existing cells is not applied to one or more new cells (and / or when the timing advance value associated with one or more current and / or existing cells is not applied to one or more new cells), then the UE may stop the timeAlignmentTimer associated with the TAG. If the timing advance value associated with one or more current and / or existing cells is not applied to one or more new cells (and / or when the timing advance value associated with one or more current and / or existing cells is not applied to one or more new cells), then the UE may initiate a random access procedure (for a cell in one or more new cells, such as a single cell).

[0531] Example 5

[0532] In Embodiment 5, it may be determined whether to initiate a random access procedure (e.g., a Random Access Channel (RACH) procedure) based on whether there is a cell that does not belong to the current and / or existing TAG (e.g., it may implicitly indicate whether to perform a random access procedure).

[0533] In some instances, the UE may determine whether to initiate (and / execute) a random access procedure (e.g., execute a random access procedure to obtain a timing advance value for the cell set) based on whether the set of cells (which are added / activated in the mobility procedure) is associated with one or more current and / or existing TAGs in the MCG or SCG (e.g., whether the cell set belongs to one or more current and / or existing TAGs in the MCG or SCG) during and / or after the mobility procedure for adding / activating the cell set. If the first cell is not associated with a current and / or existing TAG (e.g., the first cell does not belong to a current and / or existing TAG) (and / or when the first cell is not associated with a current and / or existing TAG), then the UE may initiate a random access procedure for the first cell in the cell set (e.g., if the first cell is not associated with any current and / or existing TAG, then the UE may initiate a random access procedure for the first cell). In some instances, if the second cell is associated with a current and / or existing TAG (e.g., the second cell belongs to a current and / or existing TAG) (and / or when the second cell is associated with a current and / or existing TAG), then the UE may not initiate a random access procedure for the second cell in the cell set (e.g., if the second cell is associated with any current and / or existing TAG, then the UE may not initiate a random access procedure for the second cell). Alternatively and / or additionally, the UE may determine whether to initiate (and / perform) a random access procedure during and / or after the mobility procedure of adding / activating the cell set based on whether the set of cells (which are added / activated in the mobility procedure) is associated with a valid timing advance value (e.g., whether the cell set belongs to a valid timing advance value). If the first cell is not associated with a valid timing advance value (e.g., the first cell does not belong to a valid timing advance value) (and / or when the first cell is not associated with a valid timing advance value), then the UE may initiate a random access procedure for the first cell in the cell set (e.g., if the first cell is not associated with any valid timing advance value, then the UE may initiate a random access procedure for the first cell). In some instances, if the second cell is associated with a valid timing advance value (e.g., the second cell belongs to a valid timing advance value) (and / or when the second cell is associated with a valid timing advance value), then the UE may not initiate a random access procedure for the second cell in the cell set (e.g., if the second cell is associated with any valid timing advance value, then the UE may not initiate a random access procedure for the second cell).

[0534] Example 6

[0535] In Embodiment 6, it may be explicitly indicated whether a random access procedure (e.g., RACH procedure) is initiated.

[0536] In some instances, the UE may be instructed by the network (e.g., indicated via the first and / or second information) whether to initiate a random access procedure (e.g., a random access procedure to obtain a timing advance value) for the cell in response to (i) receiving the second information and / or (ii) initiating or completing a mobility procedure associated with adding a cell (e.g., a mobility procedure executed in response to the second information). For example, for each set of one or more first sets of cells (e.g., one or more first sets of cells indicated by the first information), in response to (i) receiving the second information and / or a mobility procedure (e.g., a mobility procedure executed in response to the second information), there may be an indication (e.g., at least one of a flag, parameter value, timing advance information, etc.) of whether to initiate a random access procedure for the cell when adding / activating a cell in the set, wherein the indication may be included in the first and / or second information. In one instance, the first and / or second information may include an instruction to initiate a random access procedure for cells in one or more of the first sets (e.g., at least one of a flag, parameter value, timing advance information, etc.), wherein based on the instruction, the UE may initiate a random access procedure for the cell in response to (i) receiving the second information and / or (ii) initiating or completing a mobility procedure (e.g., adding / activating a mobility procedure for the cell in response to the second information). Alternatively and / or additionally, the first and / or second information may include an instruction not to initiate a random access procedure for cells in one or more of the first sets (e.g., at least one of a flag, parameter value, timing advance information, etc.), wherein based on the instruction, the UE may not initiate a random access procedure for the cell in response to (i) receiving the second information and / or (ii) initiating or completing a mobility procedure (e.g., adding / activating a mobility procedure for the cell in response to the second information).

[0537] In some instances, one or more first sets may include (i) a set of cells indicated as (and / or configured as) not having random access procedure requirements (e.g., the first and / or second information may indicate that a random access procedure is not required for the first set of cells); and (ii) a set of cells indicated as (and / or configured as) being associated with random access procedure requirements (e.g., the first and / or second information may indicate that a random access procedure is required for the second set of cells). In response to receiving the second information, the UE initiates a mobility procedure and / or adds / activates one or more cells (e.g., the one or more cells may be added / activated during a mobility procedure). In some instances, if the second information indicates adding / activating one or more cells in the first set of cells (and does not indicate adding / activating one or more cells in the second set of cells) (and / or when this is the case), then the UE, in response to (i) the second information and / or (ii) initiating or completing a mobility procedure, does not initiate a random access procedure (e.g., the UE does not initiate a random access procedure for the one or more cells based on the fact that the one or more cells are not associated with random access procedure requirements). In some instances, if the second information indicates the addition / activation of one or more cells in a second cell set (and, for example, does not indicate the addition / activation of one or more cells in a first cell set) (and / or when said), then the UE initiates a random access procedure in response to (i) the second information and / or (ii) the initiation or completion of a mobility procedure (for example, the one or more cells in the second cell set) (e.g., the UE initiates a random access procedure for the one or more cells based on the association of the one or more cells with a random access procedure requirement).

[0538] Alternatively and / or additionally, the UE may possess (e.g., be configured with) one or more random access resources / configurations (e.g., one or more RACH resources / configurations) associated with one or more sets of one or more first sets of cells (e.g., the UE may possess one or more random access resources / configurations via first information). The UE may determine whether to initiate a random access procedure for one or more cells in one or more sets of cells based on whether the UE possesses (e.g., is configured with) one or more random access resources / configurations for the set including one or more cells (e.g., whether to initiate a random access procedure in response to (i) receiving second information and / or (ii) initiating or completing a mobility procedure for the one or more cells). In some instances, if the UE possesses (e.g., is configured with) one or more random access resources / configurations for the set (and / or when said), then the UE may initiate a random access procedure for the one or more cells in the set (e.g., the UE may initiate a random access procedure in response to (i) receiving second information and / or (ii) initiating or completing, for example, a mobility procedure for the one or more cells). In some instances, if the UE does not possess (e.g., is configured with) one or more random access resources / configurations for the set (and / or in such cases), then the UE may not initiate a random access procedure for the one or more cells in the set (e.g., the UE may not initiate a random access procedure in response to (i) receiving the second information and / or (ii) initiating or completing, for example, adding / activating the one or more cells). If one or more random access resources / configurations are provided / configured for the set (and / or when one or more random access resources / configurations are provided / configured for the set), then the first information may not provide timing advance information for the set. In this disclosure, the term "resources / configurations" may refer to resources and / or configurations.

[0539] Example 7

[0540] In Embodiment 7, a timing lead time (e.g., new NTA) for the cell set (e.g., per TAG) can be indicated. For example, the timing lead time can be indicated by first information.

[0541] In some instances, one or more sets of one or more first sets of a cell may be associated with timing advance information (e.g., included in the first information). For example, timing advance information may be provided (e.g., indicated in the first information) for said one or more sets. Timing advance information may include a timing advance amount (e.g., NTA) between the uplink (UL) and downlink (DL). Timing advance information may include a timeAlignmentTimer. Timing advance information may include a TAG id. Timing advance information may include one or more parameters in the TAG-config. Each set (of one or more sets) may be associated with a timing advance amount between the uplink and downlink. For example, each set of one or more sets may be associated with an NTA (e.g., each set of one or more sets may be associated with a different NTA). Alternatively and / or additionally, for each set of one or more sets, timing advance information may include a timing advance amount (e.g., NTA) between the uplink and downlink. For each set of one or more first sets of a cell, the UE may maintain (e.g., store and / or update) the timing advance information (e.g., NTA). In response to (i) the second information and / or (ii) the initiation or completion of a mobility procedure for adding / activating cells in one or more of the first sets of cells, the UE may apply timing advance information (e.g., NTA) associated with the first set to the cells (e.g., the timing advance information may be maintained by the UE for the first set).

[0542] In some instances, if a set (in one or more first sets) is associated with timing advance information (e.g., timing advance information maintained and / or indicated and / or included in the first information) (and / or when said), then the UE may not initiate a random access procedure for the cell when adding / activating a cell in the set. Alternatively and / or additionally, if a second set (in one or more first sets) is not associated with timing advance information (e.g., timing advance information is not maintained and / or indicated for the second set and / or the first information does not include timing advance information for the second set) (and / or when said), then the UE may initiate a random access procedure for the second cell when adding / activating a second cell (e.g., a PCell of a candidate set of cells) in the second set of one or more first sets. In some instances, the first information may not indicate timing advance information for the sets in one or more first sets (and / or may not indicate timing advance information for at least a portion of the sets). In some instances, the UE may be unsure (and / or may be certain not to) initiate a random access procedure for a SCell in one or more sets of first sets.

[0543] Figure 7This describes scenario 700, which relates to the UE and the network "NW". The UE can communicate with the NW via serving cells including cell 1, cell 2, and cell 3, where each serving cell is one of three TAGs (e.g., three original TAGs) associated with TAG id 1, TAG id 2, and TAG id 3, respectively (e.g., cell 1 is associated with TAG id 1, cell 2 with TAG id 2, and cell 3 with TAG id 3). The TAG with TAG id 1 is associated with a timing advance value NTA,1. The TAG with TAG id 2 is associated with a timing advance value NTA,2. The TAG with TAG id 3 is associated with a timing advance value NTA,3. The NW transmits first information 704 to the UE (e.g., via an RRC message). The first information 704 indicates (i) cell group A (e.g., candidate cell group) including cell 4 and cell 5; and (ii) cell group B (e.g., candidate cell group) including cell 6. Cell 4 is configured with TAG id 1 (e.g., the ServingCellConfig of cell 4 indicates that cell 4 belongs to TAG id 1). Cell 5 is configured with TAG id 2 (e.g., the ServingCellConfig of cell 5 indicates that cell 5 belongs to TAG id 2). Cell 6 is configured with TAG id 1 (e.g., the ServingCellConfig of cell 6 indicates that cell 6 belongs to TAG id 1). The NW transmits second information 710 to the UE for adding and / or activating cell group A (e.g., the NW may transmit second information 710 to initiate a mobility procedure to switch the UE's serving cell to cell group A). ​​Second information 710 indicates TAG id 2 and TAG id 3 (e.g., for cells 4 and 5 and / or for cell group A). ​​In response to receiving second information 710, the UE adds cell 4 in the TAG with TAG id 1 (e.g., as indicated in first information 704) and adds cell 5 in the TAG with TAG id 2. In response to the second information 710 (and / or in response to the addition of cells 4 and 5), the UE applies timing advance values ​​associated with TAG id 2 (e.g., the original TAG id 2) and TAG id 3 to cells 4 and 5, respectively. For example, the UE may (i) apply timing advance value NTA,2 to cell 4 (e.g., based on the second information 710 indicating TAG id 2 and / or TAG id 2 associated with timing advance value NTA,2) and / or (ii) apply timing advance value NTA,3 to cell 5 (e.g., based on the second information 710 indicating TAG id 3 and / or TAG id 3 associated with timing advance value NTA,3).

[0544] Figure 8This describes scenario 800, which is associated with the UE and NW. In scenario 800, upon receiving the first information 704 (displayed in...), Figure 7 Neutralization / or about Figure 7 After the described steps, the UE may receive a second message 810 indicating timing advance values ​​NTA,4 and NTA,5 (for cell 4 and cell 5 and / or for cell group A). ​​In response to receiving the second message 810, the UE adds cell 4 in a TAG with TAG id 1 (e.g., as indicated in the first message 704) and adds cell 5 in a TAG with TAG id 2. In response to the second message 810 (and / or in response to adding cell 4 and cell 5), the UE applies the timing advance values ​​indicated in the second message to cell 4 (e.g., applying timing advance value NTA,4 to cell 4) and cell 5 (e.g., applying timing advance value NTA,5 to cell 5), respectively.

[0545] Figure 9 This describes scenario 900, which is associated with the UE and NW. In scenario 900, upon receiving the first information 704 (displayed in...), Figure 7 Neutralization / or about Figure 7 Following the description, the UE may receive second information 910. Second information 910 (and / or first information 704) does not indicate timing advance information associated with cells in cell group A (e.g., cells 4 and 5). First information 704 or second information 910 may (e.g., via SpCellConfig) indicate cell 4 as the PCell of cell group A. In response to second information 910, the UE adds / activates cells 4 and 5 in cell group A. In response to second information 910 (and / or in response to adding cells 4 and 5), the UE determines to initiate a random access procedure 914 for cell 4 (e.g., the UE may initiate a random access procedure 914 for cell 4 based on cell 4 being the PCell of cell group A and / or based on cell 4 not being associated with a valid timing advance value). Alternatively and / or additionally, the UE may initiate a random access procedure for cell 5 (e.g., the UE may initiate a random access procedure for cell 5 based on cell 5 not being associated with a valid timing advance value). Alternatively, the UE may be uncertain (and / or uncertain not) about initiating a random access procedure for cell 5 (e.g., based on cell 5 being a SCell). The NW may instruct the UE (e.g., instruct the UE) to initiate a random access procedure for cell 5 (e.g., the NW may instruct the UE to initiate a random access procedure via a PDCCH command).

[0546] Each of one or more first sets may be associated with an index / identity (e.g., may be assigned an index / identity). The index / identity may be provided in the first information (e.g., an indication).

[0547] The second information (received by the UE) may indicate an index / identity associated with a first set of one or more first sets. The UE may add and / or activate one or more cells, including one, some, and / or all of the cells associated with the first set (e.g., indicated in the first set), in response to a mobility procedure corresponding to the second information (e.g., in response to initiating or completing a mobility procedure) and / or in response to receiving the second information. The UE may treat the one or more cells associated with the first set (e.g., indicated in the first set) as one or more serving cells in response to a mobility procedure (e.g., in response to initiating or completing a mobility procedure) and / or in response to receiving the second information. The second information may indicate whether the first set is for an MCG or an SCG. The first set may correspond to a set of one or more cells and / or a set of one or more CGs.

[0548] Example 8

[0549] In Example 8, TAG information and / or NTA information may be indicated in the first information (e.g., per cell).

[0550] In some instances, the first information may indicate one or more first cells. Each of the one or more first cells may be a serving cell, a neighboring cell, a non-serving cell, an ACell (e.g., a secondary and / or additional cell), and / or a PCI-associated cell different from the UE's serving cell. Each of the one or more first cells may be associated with a TAG (e.g., configured with a TAG). For example, the one or more first cells may be associated with different and / or individual TAGs (e.g., configured with different and / or individual TAGs). In one instance, each of the one or more first cells may be associated with a TAG id (e.g., configured with a TAG id), wherein the TAG id may be associated with the TAG id of a current and / or existing pTAG or sTAG of the MCG or SCG.

[0551] For example, the first information may include a first cell configuration of the first cell (e.g., one or more parameters in ServingCellConfig). The first cell configuration may indicate (e.g., may include) a first TAGid associated with the first cell. The first information may include a second cell configuration of the second cell. The second cell configuration may indicate (e.g., may include) a second TAGid associated with the second cell. In response to (i) receiving the second information and / or (ii) initiating or completing a mobility procedure to add / activate the first and second cells, the UE may (A) apply timing advance information (e.g., a first NTA) of the first TAG to the first cell, wherein the first TAG is associated with a first TAGid; and (B) apply timing advance information (e.g., a second NTA) of the second TAG to the second cell, wherein the second TAG is associated with a second TAGid. The UE may consider the first cell as a cell in the first TAG when adding / activating the first cell as a serving cell (e.g., the UE may assign the first cell to the first TAG). The UE may consider the second cell as a cell in the second TAG when adding / activating the second cell as a serving cell (e.g., the UE may assign the second cell to the second TAG).

[0552] Alternatively and / or additionally, the UE may determine whether to initiate a random access procedure (e.g., obtain the timing advance of the cell) for the cell based on the validity of the timing advance information (e.g., NTA) of the TAG when adding / activating the cell associated with the TAG. The timing advance information may be valid when the time alignment timer (e.g., timeAlignmentTimer) of the TAG is running. The UE may determine whether to initiate a random access procedure (e.g., obtain the TA of the cell) for the cell based on the validity of the time alignment timer (e.g., timeAlignmentTimer) associated with the TAG when adding the cell (and / or thereafter). If the time alignment timer associated with the TAG is not running (and / or when the time alignment timer associated with the TAG is not running), then the UE may initiate a random access procedure for the cell when adding the cell (and / or thereafter). When the time alignment timer is not running and / or the NTA is invalid, the UE may not apply the NTA of the TAG to the cell.

[0553] Alternatively and / or additionally, the first information may indicate timing advance information for each of one or more first cells. Timing advance information may include the timing advance amount between the uplink and downlink (e.g., a timing advance value, such as NTA). Timing advance information may include a timeAlignmentTimer. Timing advance information may include a TAG id. Timing advance information may include one or more parameters in the TAG-config. The first information may indicate a first NTA for the first cell. In response to (i) receiving second information and / or (ii) initiating or completing a mobility procedure to add / activate the first cell, the UE may apply a first NTA to the first cell. The first information may indicate a second NTA for the second cell. In response to (i) receiving second information and / or (ii) initiating or completing a mobility procedure to add / activate the second cell, the UE may apply a second NTA to the second cell.

[0554] Example 9

[0555] In Example 9, it may be indicated whether to initiate a random access procedure (e.g., RACH procedure) for the cell.

[0556] In some instances, the first information may not indicate (and / or may not configure) timing advance information for one or more cells (and / or subsets of cells) in the first cells. The second information may not indicate timing advance information for one or more cells (and / or subsets of cells) in the first cells. Alternatively and / or additionally, the first information may (i) indicate the TAG for one or more cells (and / or subsets of cells) and (ii) not indicate timing advance information (e.g., NTA) for the cells (and / or subsets of cells). The UE may determine whether to initiate a random access procedure for the first cell (e.g., perform a random access procedure to obtain a timing advance value and / or in response to (i) receiving the second information and / or (ii) initiating or completing a mobility procedure to add / activate the first cell) based on whether the first cell has a valid timing advance value (NTA) and / or a TAG (e.g., having a valid NTA) (e.g., in the first information). A valid timing advance value may be indicated and / or configured via the first information and / or the second information. If the timeAlignmentTimer of the TAG associated with the timing advance value is running (and / or when the timeAlignmentTimer of the TAG associated with the timing advance value is running), then the timing advance value is valid. If the timeAlignmentTimer of the TAG associated with the timing advance value is not running (and / or when the timeAlignmentTimer of the TAG associated with the timing advance value is not running), then the timing advance value is invalid. If the NTA is invalid (and / or when the NTA is invalid), then the UE may not apply the NTA when adding a cell in the TAG. If the NTA is not applied (e.g., the NTA of the TAG), then the UE may stop the time alignment timer of the TAG. Alternatively and / or additionally, if the UE initiates (and / or indicates and / or indicates initiation) a random access procedure for the cell associated with the TAG, then the UE may stop the time alignment timer of the TAG, wherein the UE adds / activates the cell in response to (i) the second information and / or (ii) initiating or completing a mobility procedure to add / activate the cell.

[0557] Alternatively and / or additionally, the first information may indicate the random access resources / configuration of one or more cells in the first cells. If the random access resources / configuration is provided / configured for the cell (and / or when the random access resources / configuration is provided / configured for the cell), then the first information may not provide timing advance information for the cell. The UE may determine whether to initiate a random access procedure for the second cell (e.g., perform a random access procedure to obtain a timing advance value and / or in response to (i) receiving the second information and / or (ii) initiating or completing a mobility procedure to add / activate the second cell) based on whether the second cell is configured with random access resources / configuration. For example, if the first information indicates the random access resources / configuration of the second cell (and, for example, does not indicate the timing advance information of the second cell) (and / or when said in this case), then the UE may initiate a random access procedure for the second cell. Alternatively and / or additionally, if the first information does not indicate the random access resources / configuration of the second cell (and, for example, indicates the timing advance information of the second cell) (and / or when said in this case), then the UE may not initiate a random access procedure for the second cell.

[0558] Example 10

[0559] In Embodiment 10, the second information may indicate one or more second cells, which may be a subset of one or more first cells indicated in the first information.

[0560] In some instances, the second information may indicate one or more second cells. The second information may indicate timing advance information (e.g., NTA) and / or TAG (e.g., via TAG id) associated with one or more second cells. The first information may not indicate timing advance information associated with one or more first cells (and / or may not indicate TAG associated with one or more second cells). Alternatively and / or additionally, the first information may not indicate timing advance information and / or TAG associated with one or more first sets of cells. One or more second cells may be a subset of the one or more first cells indicated in the first information. The UE may add / activate one or more second cells in response to (i) the second information and / or (ii) initiating or completing a mobility procedure. The UE may initiate a mobility procedure to add / activate one or more second cells in response to receiving the second information. The UE may treat one or more second cells as one or more serving cells in response to (i) receiving the second information and / or (ii) initiating or completing a mobility procedure. Timing advance information may include a timing advance amount between the uplink and downlink (e.g., a timing advance value, such as NTA). Timing advance information may include a timeAlignmentTimer. Timing advance information may include a TAG ID. Timing advance information may include one or more parameters in the TAG-config. Alternatively and / or additionally, the second information may indicate the type of one or more second cells (e.g., pTAG or sTAG for MCG / SCG). The UE may apply timing advance information associated with the cell (e.g., indicated in the second information) in response to (i) the second information and / or (ii) initiating or completing a mobility procedure to add / activate the cell. The cell may be associated with a TAG (e.g., the TAG indicated by the second information). Timing advance information may be associated with a TAG (e.g., the TAG indicated by the second information and / or the first information). The UE may determine whether to apply timing advance information (e.g., NTA) to the cell based on whether the timing advance information is valid. If the timing advance information is invalid, then the UE may not apply the timing advance information (e.g., the timing advance information is invalid when the time alignment timer of the TAG associated with the timing advance information is not running and / or expired). Alternatively and / or additionally, if the time alignment timer of the TAG associated with the timing advance information is not running, the UE may initiate a random access procedure for the cell. Alternatively and / or additionally, when the time alignment timer of the TAG is not running, the UE may apply the NTA of the TAG to the cell.

[0561] Alternatively and / or additionally, the second information may indicate a TAG (e.g., a single TAG) (and / or the second information may indicate one or more cells associated with the TAG). The second information may not indicate (and / or may not be allowed and / or configured to indicate) more than one TAG. Alternatively and / or additionally, the second information may not indicate (and / or may not be allowed and / or configured to indicate) cells associated with multiple (different) TAGs. Therefore, one or more second cells (indicated by the second information) may be associated with the same TAG. In some instances, the second information may indicate a TAG id (e.g., a single TAG id). In response to (i) receiving the second information and / or (ii) initiating or completing a mobility procedure, the UE may add / activate one or more cells associated with the TAG id (e.g., indicating / configuring one or more first cells and / or one or more second cells in the first and / or second information). Alternatively and / or additionally, the second information may indicate the type of TAG. In response to (i) receiving the second information and / or (ii) initiating or completing a mobility procedure, the UE may add / activate one or more cells associated with the TAG of the aforementioned type (e.g., indicating / configuring one or more first cells and / or one or more second cells in the first and / or second information). In response to (i) receiving the second information and / or (ii) initiating or completing a mobility procedure, the UE may release / remove / revoke activation of one or more current and / or existing cells that are (A) associated with the TAG of the aforementioned type and (B) not indicated in the second information.

[0562] For example, the first information may indicate a first cell associated with the pTAG of the MCG. The second information may instruct the UE (e.g., instruct the UE) to add / activate the cell associated with the pTAG of the MCG indicated in the first information (e.g., add / activate the cell as a SCell). In some instances, in response to receiving the second information, the UE adds / activates the first cell and applies the Timing Advance Value (NTA) associated with the pTAG of the UE's MCG to the first cell.

[0563] Alternatively and / or additionally, the first information may indicate a TAG (e.g., via TAG id) associated with one or more first cells (and / or one or more first sets of cells), and the second information may indicate timing advance information associated with one or more second cells.

[0564] Alternatively and / or additionally, the second information may indicate multiple TAGs. The UE may add / activate one or more cells indicated in the first and / or second information in response to (i) receiving the second information and / or (ii) initiating or completing a mobility procedure, wherein said one or more cells may be associated with one of multiple TAGs (e.g., one of multiple TAGs is configured). For example, the UE may receive the second information indicating a first TAG and a second TAG.

[0565] Example 11

[0566] In Example 11, activation of one or more cells that are not indicated in the second information and / or (ii) are not associated with a TAG (e.g., the original TAG) can be released / removed / revoked.

[0567] In some instances, in response to (i) initiating or completing a mobility procedure associated with adding / activating one or more cells associated with a TAG (e.g., the TAG indicated in the second information) and / or (ii) receiving the second information (and / or when said operation occurs), the UE may release / remove / deactivate one or more third cells (e.g., SCells) that are (A) not associated with one or more cells with the TAG and / or (B) not indicated in the second information. Alternatively and / or additionally, the UE may release / remove / deactivate one or more fourth cells that are (i) activated before initiating the mobility procedure and / or before receiving the second information and / or (ii) not indicated in the second information.

[0568] Example 12

[0569] In Example 12, if the non-serving cell is a non-serving multi-transmission and Reception Point (mTRP) ACell, then the TA of the serving cell can be applied to the non-serving cell (e.g., implicitly implied).

[0570] In some instances, the UE may apply the timing advance value of the serving cell to the non-serving cell in response to (i) second information and / or (ii) initiating or completing a mobility procedure to add / activate a non-serving cell (e.g., adding / activating the non-serving cell as a serving cell or as an ACell for inter-cell mTRP operations). The non-serving cell may be a secondary cell or ACell associated with the serving cell. The non-serving cell may be associated with a PCI different from that of any serving cell other than the UE. The UE may perform inter-cell mTRP operations on both the non-serving cell and the serving cell.

[0571] Alternatively and / or additionally, the UE may initiate a random access procedure to a non-serving cell in response to (i) the second information and / or (ii) the initiation or completion of a mobility procedure for adding / activating a non-serving cell for performing inter-cell mTRP operations with the serving cell (e.g., a random access procedure may be initiated to obtain the TA of the non-serving cell).

[0572] Figure 10 This describes scenario 1000, which relates to a UE and a network "NW". The UE may be configured to have and / or activate cell 1 (e.g., SCell) and cell 2 (e.g., SCell). In some instances, the UE communicates with the NW via cell 1 and cell 2. Cell 1 is associated with a TAG having TAG id 1. Cell 2 is associated with a TAG having TAG id 2. The NW transmits first information 1004, indicating cell 3 with TAG id 1 (e.g., first information 1004 may indicate that cell 3 is associated with TAG id 1), cell 4 with TAG id 2 (e.g., first information 1004 may indicate that cell 4 is associated with TAG id 2), and cell 5 with TAG id 2 (e.g., first information 1004 may indicate that cell 5 is associated with TAG id 2). In some instances, the UE responds to receiving first information 1004 without adding / activating the cells indicated in first information 1004. The NW transmits second information 1010 indicating the addition / activation of cells 3 and 4. In response to the second information 1010, the UE adds / activates cells 3 and 4 (e.g., as SCells). Cell 3 and / or cell 4 (e.g., as SCells) can be added in response to receiving the second information 1010. The UE can apply one or more TAG IDs indicated in the first information and set cell 3 in the TAG associated with TAG ID 1 and configure cell 4 in the TAG associated with TAG ID 2. For example, the UE can add cell 3 in the TAG associated with TAG ID 1 based on the first information 1004 indicating that cell 3 is associated with TAG ID 1. The UE can add cell 4 in the TAG associated with TAG ID 2 based on the first information 1004 indicating that cell 4 is associated with TAG ID 2. The UE may (i) apply the timing advance value (e.g., NTA) associated with TAG id 1 to cell 3 and (ii) apply the timing advance value (e.g., NTA) associated with TAG id 2 to cell 4.

[0573] exist Figure 10 In scenario 1000 shown, the UE may not release / remove / revoke the activation of cell 1 and cell 2 in response to receiving the second information 1010. In some instances, the UE may release / remove / revoke the activation of cell 1 and cell 2 in response to receiving the second information 1010. Figure 11This describes a scenario 1100 where the UE responds to receiving the second information 1010 to release / remove / revoke the activation of cell 1 and cell 2. After receiving the second information 1010, the UE may configure (and / or maintain) cell 3 in a TAG with TAG id 1 and cell 4 in a TAG with TAG id 2.

[0574] Figure 12 This describes scenario 1200 associated with a UE and a network "NW". The UE may be configured to have and / or activate cells 1 and 2. In some instances, the UE communicates with the NW via cells 1 and 2. The UE may be configured with a first TAG with TAG id 1 and a first timing advance value NTA,1. The UE may be configured with a second TAG with TAG id 2 and a second timing advance value NTA,2. Cell 1 is associated with the first TAG and / or the first timing advance value NTA,1. Cell 2 is associated with the second TAG and / or the second timing advance value NTA,2. The NW transmits first information 1204 indicating cell 3 with timing advance value NTA,3 (e.g., the first information 1204 may indicate that cell 3 is associated with timing advance value NTA,3) and cell 4 with timing advance value NTA,4 (e.g., the first information 1204 may indicate that cell 4 is associated with timing advance value NTA,4). The NW transmits a second message 1210, which instructs the UE (e.g., instructs the UE) to add / activate cell 3. In some instances, in response to the second message 1210, the UE can configure and / or add / activate cell 3 by applying its timing advance value NTA,3 provided in the first message 1204. In one instance, in response to the second message 1210, the UE can (i) add and / or activate cell 3 and / or (ii) apply the timing advance value NTA,3 to cell 3. Figure 12 In scenario 1200, the timing advance value NTA,3 and the timing advance value NTA,1 associated with TAG id 1 can be the same value (e.g., they can be equal). The UE can add cell 3 in the first TAG with TAG id 1 (e.g., based on NTA,3 being equal to NTA,1 associated with TAG id 1).

[0575] Figure 13 This describes scenario 1300 associated with the UE and NW. In scenario 1300, upon receiving the first information 1204 (displayed in...), Figure 12 Neutralization / or about Figure 12Following the description, the UE may receive second information 1310. Second information 1310 may instruct the UE (e.g., instruct the UE) to add / activate cell 4. Cell 4 may be indicated (e.g., in first information 1204) as associated with a timing advance value NTA,4, which may be different from the timing advance amounts of TAG id 1 and TAG id 2 (e.g., NTA,1 and NTA,2). The UE may allocate and / or configure cell 4 to a TAG with a TAG id different from TAG id 1 and TAG id 2 (e.g., TAG id 3 in scenario 1300). Alternatively and / or additionally, first information 1204 or second information 1310 may indicate the TAG id of cell 4, wherein the UE may allocate and / or configure cell 4 to a TAG with a TAG id indicated by first information 1204 or second information 1310 (e.g., TAG id 3).

[0576] Figure 14 This describes scenario 1400, which is associated with the UE and NW. In scenario 1400, upon receiving the first information 1204 (displayed in...), Figure 12 Neutralization / or about Figure 12 Following the description, the UE may receive second information 1410. Second information 1410 may instruct the UE (e.g., instruct the UE) to replace one or more cells associated with TAG id 1 with the added / activated cell – cell 4. This covers embodiments where the first information 1204 instructs the replacement of the one or more cells associated with TAG id 1 with cell 4. In response to second information 1410, the UE may add cell 4 and assign / configure TAG id 1 for cell 4 (e.g., cell 4 may be added to a first TAG with TAG id 1). The UE may, in response to second information 1410, release / remove / revoke activation of cell 1 (and / or one or more other cells in the original TAG associated with TAG id 1).

[0577] Figure 15This describes scenario 1500, which relates to the UE and the network "NW". The UE may be configured to have and / or activate cells 1 and 2. In some instances, the UE communicates with the NW via cells 1 and 2. The UE may be configured with a first TAG with TAG id 1 and a first timing advance value NTA,1. The UE may be configured with a second TAG with TAG id 2 and a second timing advance value NTA,2. Cell 1 is associated with the first TAG and / or the first timing advance value NTA,1. Cell 2 is associated with the second TAG and / or the second timing advance value NTA,2. The NW transmits first information 1504 indicating the configuration of cell 5 (e.g., cell configuration). In some instances, the first information 1504 does not indicate the NTA of cell 5 and / or does not indicate the TAG id of cell 5. The NW may transmit second information 1510 indicating the addition / activation of cell 5. The second information 1510 may provide the timing advance value (e.g., NTA,5) of cell 5. In response to the second information 1510, the UE configures / adds cell 5 (e.g., as a SCell) and assigns cell 5 in a TAG with TAG id 3 (e.g., the UE may add cell 5 in a TAG with TAG id 3). Alternatively and / or additionally, the second information 1510 may indicate (e.g., include) the TAG id associated with cell 5 (e.g., TAG id 3) (e.g., the NW may provide an indication of the TAG id 3 of cell 5).

[0578] In some instances, NTA,5 may have the same value as NTA,1 (e.g., associated with cell 1 and / or TAG id 1). Figure 16 This describes scenario 1600, where NTA,5 and NTA,1 have the same value. In scenario 1600, the UE may (i) add / activate cell 5 in the first TAG with TAG id 1 (e.g., based on NTA,5 and NTA,1 having the same value and / or based on NTA,1 being associated with TAG id 1) and / or (ii) apply NTA,5 as the timing advance value for cell 5.

[0579] Figure 17This describes scenario 1700, which relates to the UE and the network "NW". The UE may be configured to have and / or activate cells 1 and 2. In some instances, the UE communicates with the NW via cells 1 and 2. The UE may be configured with a first TAG with TAG id 1 and a first timing advance value NTA,1. The UE may be configured with a second TAG with TAG id 2 and a second timing advance value NTA,2. Cell 1 is associated with the first TAG and / or the first timing advance value NTA,1. Cell 2 is associated with the second TAG and / or the second timing advance value NTA,2. The NW transmits first information 1704 instructing cell 6 (e.g., the first information 1704 instructs cell 6 on its cell configuration, such as one or more parameters in the serving cell configuration). In some instances, the first information 1704 does not provide timing advance information for cell 6. The NW transmits second information 1710 instructing the UE (e.g., instructing the UE) to add / activate cell 6. In some instances, the second information 1710 does not provide timing advance information for cell 6. In response to the second information 1710, the UE may initiate a random access procedure 1712 for cell 6 (e.g., to obtain a TA associated with cell 6). Random access resources and / or configurations associated with the random access procedure for cell 6 may be provided in the first information 1704 and / or the second information 1710. Alternatively and / or additionally, if the TAG (e.g., indicated in the first information 1704 and / or the second information 1710) does not have a valid NTA (and / or if so) and / or if the TAG's time alignment timer (e.g., timeAlignmentTimer) is not running (and / or if so), then the UE may initiate a random access procedure 1712 for cell 6.

[0580] In some instances, the embodiments disclosed herein, such as those described with respect to each of Embodiments 1 to 12, may be implemented independently and / or individually. Alternatively and / or additionally, the embodiments described herein, such as combinations of one, some, and / or all of the embodiments described with respect to Embodiments 1 to 12, may be implemented. Alternatively and / or additionally, the embodiments described herein, such as combinations of one, some, and / or all of the embodiments described with respect to Embodiments 1 to 12, may be implemented in parallel and / or simultaneously.

[0581] The various techniques, embodiments, methods, and / or alternatives disclosed herein can be performed independently and / or separately. Alternatively and / or additionally, the various techniques, embodiments, methods, and / or alternatives disclosed herein can be combined and / or implemented using a single system. Alternatively and / or additionally, the various techniques, embodiments, methods, and / or alternatives disclosed herein can be implemented in parallel and / or simultaneously.

[0582] With respect to one or more embodiments herein, such as one or more technologies, apparatuses, concepts, methods, instance scenarios and / or alternatives described above, the mobility procedure may be used to add, release and / or switch one or more SCells of the UE. In some instances, the mobility procedure may not add, release or switch the PCell and / or PSCell of the UE.

[0583] Alternatively and / or additionally, a mobility procedure may include the UE triggering and / or generating a message, and / or transmitting the message to a target cell (e.g., PCell, PSCell, neighboring cell, or SCell). The mobility procedure may include the UE initiating a random access procedure (e.g., a contention-free random access procedure) to the target cell. A random access procedure may be initiated in response to a message becoming available for transmission. The message may indicate the completion of the mobility procedure. The mobility procedure may be used to hand over the UE's PCell (or PSCell) to the target cell. The UE may consider the mobility procedure complete in response to the completion of the random access procedure. The UE may consider the mobility procedure complete in response to receiving a positive acknowledgment associated with the message (from, for example, the target cell). The message may be a mobility completion message. In some instances, a mobility completion message may not include an RRC message. A mobility completion message may include a MACCE. Mobility completion messages may be transmitted via the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH).

[0584] In some instances, a mobility procedure (e.g., an L1 / L2 mobility procedure) may include the serving cell providing first information (e.g., the first information discussed in one, some, and / or all of Embodiments 1 to 12) to the UE, wherein the first information provides (e.g., an indication) a configuration (e.g., cell configuration) associated with the target cell. The configuration may include cell addition information and / or beaming information associated with the target cell. The first information may be signaling dedicated to the UE. The source cell may provide second information (e.g., the second information discussed in one, some, and / or all of Embodiments 1 to 12) to the UE, indicating the initiation of a mobility procedure to the target cell. The mobility procedure may include a random access procedure, one or more PUSCH transmissions, and / or beam / TCI state activation. In some instances, the second information does not include RRC signaling and / or RRC messages. The second information may be an L1 (e.g., downlink control information) or L2 (e.g., MAC CE) message. The first and second information may be transmitted in different signaling and / or at different times. In some instances, the UE may not initiate a mobility procedure to the target cell in response to a first message (e.g., in response to receiving the first message). The UE may transmit a mobility completion message indicating the completion of the mobility procedure to the target cell. Alternatively and / or additionally, the target cell may transmit an acknowledgment indicating the completion of the mobility procedure to the UE. The UE may consider the mobility procedure complete in response to the acknowledgment from the target cell. Alternatively and / or additionally, the UE may consider the mobility procedure complete in response to the transmission of the mobility completion message. Alternatively and / or additionally, the UE may consider the mobility procedure complete in response to the completion of a random access procedure (e.g., a random access procedure associated with the mobility procedure, such as a random access procedure executed as part of the mobility procedure).

[0585] Mobility procedures may include cross-regional handover procedures and / or a portion of a synchronized reconfiguration procedure.

[0586] The completion of mobility procedures may correspond to the completion of random access procedures associated with the mobility procedures. Alternatively and / or additionally, the completion of mobility procedures may correspond to the transmission of a mobility completion message (to, for example, the target cell). Alternatively and / or additionally, the completion of mobility procedures may correspond to the receipt of an acknowledgment of a mobility completion message (from, for example, the target cell).

[0587] In some instances, the mobility procedure does not involve synchronous reconfiguration (e.g., not a Layer 3 cross-regional handover).

[0588] In one or more embodiments described herein, the first information may be an RRC message (e.g., an RRCReconfiguration message).

[0589] The first information may include the UL and / or DL ​​resource configuration associated with the target cell (and / or one or more cells added as an SCell when initiating or completing a mobility procedure).

[0590] The first information may include the target cell and the ServingCellConfigCommon of one or more cells. The one or more cells may be candidate serving cells for the UE's MCG or SCG.

[0591] Regarding one or more embodiments herein, the second information is not an RRC message (e.g., the second information is not RRC signaling). The second information may include Physical Downlink Control Channel (PDCCH) signaling (e.g., DCI) and / or MAC CE. The second information may instruct the UE (e.g., instruct the UE) to initiate a mobility procedure to add / activate the one or more cells (and / or a subset of the one or more cells). Alternatively and / or additionally, the second information may instruct the UE (e.g., instruct the UE) to add / activate the one or more cells (and / or a subset of the one or more cells) (e.g., the second information may instruct the UE to add / activate the one or more cells and / or a subset of the one or more cells as SCells and / or as PCells). The second information may instruct the addition, handover, and / or release (via, for example, a mobility procedure) of one or more cells (e.g., via an index indicated in the first information and / or via an SCell index). In response to the addition / activation of the one or more cells (and / or a subset of the one or more cells) (e.g., in response to the completion of the addition / activation of the one or more cells and / or a subset), the UE may regard the one or more cells (and / or a subset of the one or more cells) as the serving cell.

[0592] The second information may include sCellToAddModList and / or sCellToReleaseList (e.g., in cell information). The second information may indicate (e.g., may include) one or more cell lists indicating cells (e.g., SCells) to be added / modified / released when a mobility procedure is initiated or completed.

[0593] The second piece of information may not be (and / or may not include) SCell activation / deactivation MAC CE.

[0594] Regarding one or more embodiments herein, the L1 / L2 handover procedure may be a mobility procedure. Regarding one or more embodiments herein, the L1 / L2 handover (HO) may not be a reconfiguration procedure with synchronization. The mobility procedure may be an inter-cell mobility procedure centered on L1 / L2.

[0595] With respect to one or more embodiments herein, mobility procedures may include the UE transmitting UL data and / or control information to a target cell. UL data may include information associated with the UE (e.g., Cell Radio Network Temporary Identifier (C-RNTI) MAC CE). UL data may be transmitted via PUSCH. UL control information may be transmitted via PUCCH.

[0596] Regarding one or more embodiments herein, the one or more cells may not include a PCell or a target cell. Second information may indicate to the UE both the target cell and the other one or more cells (via, for example, cell information), wherein the UE initiates a mobility procedure and, in response to the completion (or initiation) of the mobility procedure, considers the target cell as the PCell.

[0597] Regarding one or more embodiments herein, in order to add a cell (e.g., a candidate serving cell) associated with an identity (e.g., SCellIndex), the UE adds the cell as an SCell and applies the cell's configuration (e.g., cell configuration). The cell configuration may be indicated in the first information (e.g., via one or more parameters in sCellConfigCommon and sCellConfigDedicated).

[0598] In one or more embodiments described herein, the index / identity (e.g., provided in the first information) may not be ServCellIndex. In some instances, the index / identity may not be sCellIndex.

[0599] With respect to one or more embodiments herein, cell information (e.g., in second information) may indicate one or more cells that will be added (in the MCG and / or SCG) in response to receiving the second information.

[0600] Regarding one or more embodiments herein, the current and / or existing TAG may be a TAG associated with the UE before receiving the first information and / or the second information (e.g., configured with a TAG id). Alternatively and / or additionally, the current and / or existing TAG may be a TAG associated with the UE after receiving the first information and / or the second information and / or after completing the mobility procedure (e.g., configured with a TAG id).

[0601] Regarding one or more embodiments herein, the current and / or existing TAG ID may be the TAG ID of the TAG associated with the UE before receiving the first and / or second information. Alternatively and / or additionally, the current and / or existing TAG ID may be the TAG ID of the TAG associated with the UE after receiving the first and / or second information and / or after completing the mobility procedure.

[0602] Regarding one or more embodiments herein, the TAG of a cell in the one or more cells may be indicated in the first information and / or the second information. Timing advance information of a cell in the one or more cells may be indicated in the first information and / or the second information.

[0603] Regarding one or more embodiments herein, the current and / or existing cell may be a cell configured, activated, and / or added before receiving the second information and / or before initiating a mobility procedure (e.g., by the UE). The current and / or existing cell may be an SCell (or PCell). The current and / or existing cell may be indicated in the first and / or second information. If the cell is indicated in the second information (and / or when the cell is indicated in the second information), then the UE may not release / remove / revoke the activation of the current and / or existing cell (in response to receiving the second information and / or in response to initiating or completing a mobility procedure).

[0604] Regarding one or more embodiments herein, in order to add / activate a cell associated with a TAG, the UE may configure the cell and / or apply a cell with a TAG ID associated with the TAG. The UE may regard the cell as a serving cell associated with the TAG (e.g., an activated serving cell, SCell, and / or PCell).

[0605] In one or more embodiments described herein, a TAG may not include PCell or PSCell. In some instances, a TAG may not be associated with a TAG id equal to 0.

[0606] With respect to one or more embodiments herein, the application of NTA to and / or to a cell by the UE may mean that when the UE performs a UL transmission on the cell, the UL transmission uses NTA (e.g., except for using an offset NTA, offset) as a timing advance between the downlink and the uplink (e.g., the timing advance may be determined based on NTA and NTA, offset, for example, where the timing advance is equal to the sum of NTA and NTA, offset).

[0607] Alternatively and / or additionally, the UE applying an NTA to and / or to the cell may mean that the UE starts an uplink frame for transmission by an offset derived from the value of the NTA before starting the corresponding downlink frame.

[0608] Regarding one or more embodiments herein, the NTA of one or more cells may be indicated and / or configured (by, for example, first information and / or second information) as a value (e.g., a fixed value), such as a value of 0 or a non-zero value (e.g., the NTA may be indicated and / or configured as a value equal to 0 or a non-zero value, such as a fixed value). Alternatively and / or additionally, the NTA may be indicated and / or configured via an index (e.g., ServCellindex or SCellindex) of the cell (e.g., a different cell different from the one or more cells). For example, the UE may be configured with an NTA via an index. In instances where the cell is a different cell different from the one or more cells, the NTA of the one or more cells has the same value as the NTA of the different cells.

[0609] In some embodiments, in this disclosure, one, some, and / or all instances of the term "identity" may be replaced by the terms "ID" and / or "id," and / or may be used interchangeably with the aforementioned terms.

[0610] In some embodiments, in this disclosure, one, some, and / or all instances of the term "TAG id" may be replaced by the terms "TAG ID," "TAG-Id," and / or "TAG identity," and / or may be used interchangeably with the aforementioned terms.

[0611] In some embodiments, in this disclosure, one, some, and / or all instances of the terms “timing advance” and / or “TA” may be replaced with (and / or supplemented with) the term “time alignment”.

[0612] In some embodiments, in this disclosure, one, some, and / or all instances of the terms “timing advance group” and / or “TAG” may be replaced with (and / or supplemented with) the term “time alignment group”.

[0613] One, some, and / or all of the foregoing examples, concepts, techniques, and / or embodiments can be formed and / or combined to form new embodiments.

[0614] Figure 18This is a flowchart 1800 from the perspective of a UE according to an exemplary embodiment. In step 1805, the UE receives a first signaling indicating the cell configuration of a first cell (e.g., one or more parameters in ServingCellconfig and / or sCellConfigCommon and / or sCellConfigDedicated). The first signaling indicates a first TAG id associated with the first cell. In step 1810, the UE receives a second signaling indicating the addition of the first cell as an SCell, wherein the second signaling includes PDCCH signaling and / or MAC CE (e.g., the second signaling may be PDCCH signaling or MAC CE). For example, the second signaling may instruct the UE to add the first cell as an SCell. In step 1815, the UE (i) adds the first cell as an SCell and (ii) applies a timing advance value associated with the first TAG id to the first cell. For example, the UE may apply the timing advance value associated with the first TAG id to the first cell based on the first signaling indicating the first TAG id associated with the first cell (e.g., based on the first signaling indicating the first TAG id associated with the first cell).

[0615] Return to reference Figure 3 and Figure 4 In one exemplary embodiment of the UE, the apparatus 300 includes program code 312 stored in memory 310. CPU 308 is executable program code 312 to enable the UE to (i) receive first signaling indicating a cell configuration of a first cell, wherein the first signaling indicates a first TAG id associated with the first cell; (ii) receive second signaling indicating adding the first cell as an SCell, wherein the second signaling includes PDCCH signaling and / or MAC CE; and (iii) add the first cell as an SCell and (B) apply a timing advance value associated with the first TAG id to the first cell. Furthermore, CPU 308 can execute program code 312 to perform one, some, and / or all of the above actions and steps and / or other actions and steps described herein.

[0616] Figure 19This is a flowchart 1900 from the perspective of the UE according to an exemplary embodiment. In step 1905, the UE receives a first signaling indicating the cell configuration of the first cell (e.g., one or more parameters in ServingCellconfig and / or sCellConfigCommon and / or sCellConfigDedicated). In step 1910, the UE receives a second signaling indicating the addition of the first cell as an SCell, wherein the second signaling includes PDCCH signaling and / or MAC CE (e.g., the second signaling may be PDCCH signaling or MAC CE), and wherein the second signaling indicates a first TAG id associated with the first cell. For example, the second signaling may instruct the UE to add the first cell as an SCell. In step 1915, the UE (i) adds the first cell as an SCell and (ii) applies a timing advance value associated with the first TAG id to the first cell. For example, the UE may apply a timing advance value associated with the first TAG id to the first cell based on the second signaling indication of the first TAG id associated with the first cell (e.g., based on the second signaling indication of the first TAG id associated with the first cell).

[0617] Return to reference Figure 3 and Figure 4 In one exemplary embodiment of the UE, the apparatus 300 includes program code 312 stored in memory 310. CPU 308 can execute program code 312 to enable the UE to (i) receive first signaling indicating a cell configuration of a first cell; (ii) receive second signaling indicating adding the first cell as an SCell, wherein the second signaling includes PDCCH signaling and / or MAC CE, and wherein the second signaling indicates a first TAG id associated with the first cell; and (iii) add the first cell as an SCell and (B) apply a timing advance value associated with the first TAG id to the first cell. Furthermore, CPU 308 can execute program code 312 to perform one, some, and / or all of the above actions and steps and / or other actions and steps described herein.

[0618] about Figure 18 and Figure 19 In one embodiment, the UE releases / removes / deactivates a second cell associated with a first TAG id in response to receiving a second signaling, wherein the second signaling does not indicate the second cell. For example, the UE may release / remove / deactivate a second cell based on the second signaling not indicating the second cell.

[0619] In one embodiment, adding a first cell as an SCell may include (i) adding the first cell to the UE's set of SCells (e.g., the set of currently used and / or active SCells); (ii) activating the first cell; and / or (iii) treating the first cell as an SCell. The UE may use the first cell (e.g., as an SCell) after adding it as an SCell.

[0620] In one embodiment, the UE adds a first cell as a SCell and / or applies a timing advance value to the first cell in response to a second signaling.

[0621] Figure 20 This is a flowchart 2000 from the perspective of a UE according to an exemplary embodiment. In step 2005, the UE receives a first signaling indicating the cell configuration of a first cell (e.g., one or more parameters in ServingCellconfig and / or sCellConfigCommon and / or sCellConfigDedicated). The first signaling indicates a timing advance value associated with the first cell. In step 2010, the UE receives a second signaling indicating the addition of the first cell as an SCell, wherein the second signaling includes PDCCH signaling and / or MAC CE (e.g., the second signaling may be PDCCH signaling or MAC CE). For example, the second signaling may instruct the UE to add the first cell as an SCell. In step 2015, the UE (i) adds the first cell as an SCell and (ii) applies the timing advance value to the first cell. For example, the UE may apply the timing advance value to the first cell based on the timing advance value associated with the first cell indicated by the first signaling (e.g., based on the first signaling indicating the timing advance value associated with the first cell).

[0622] Return to reference Figure 3 and Figure 4 In one exemplary embodiment of the UE, the apparatus 300 includes program code 312 stored in memory 310. CPU 308 is executable program code 312 to enable the UE to (i) receive first signaling indicating a cell configuration of a first cell, wherein the first signaling indicates a timing advance value associated with the first cell; (ii) receive second signaling indicating adding the first cell as an SCell, wherein the second signaling includes PDCCH signaling and / or MAC CE; and (iii) add the first cell as an SCell and (B) apply the timing advance value to the first cell. Furthermore, CPU 308 can execute program code 312 to perform one, some, and / or all of the above actions and steps and / or other actions and steps described herein.

[0623] Figure 21This is a flowchart 2100 from the perspective of the UE according to an exemplary embodiment. In step 2105, the UE receives a first signaling indicating the cell configuration of a first cell (e.g., one or more parameters in ServingCellconfig and / or sCellConfigCommon and / or sCellConfigDedicated). In step 2110, the UE receives a second signaling indicating the addition of the first cell as an SCell, wherein the second signaling includes PDCCH signaling and / or MAC CE (e.g., the second signaling may be PDCCH signaling or MAC CE), and wherein the second signaling indicates a timing advance value associated with the first cell. For example, the second signaling may instruct the UE to add the first cell as an SCell. In step 2115, the UE (i) adds the first cell as an SCell and (ii) applies the timing advance value to the first cell. For example, the UE may apply the timing advance value to the first cell based on the timing advance value associated with the first cell indicated by the second signaling (e.g., based on the second signaling indicating the timing advance value associated with the first cell).

[0624] Return to reference Figure 3 and Figure 4 In one exemplary embodiment of the UE, the apparatus 300 includes program code 312 stored in memory 310. CPU 308 can execute program code 312 to enable the UE to (i) receive first signaling indicating a cell configuration of a first cell; (ii) receive second signaling indicating the addition of the first cell as an SCell, wherein the second signaling includes PDCCH signaling and / or MAC CE, and wherein the second signaling indicates a timing advance value associated with the first cell; and (iii) add the first cell as an SCell and (B) apply the timing advance value to the first cell. Furthermore, CPU 308 can execute program code 312 to perform one, some, and / or all of the above actions and steps and / or other actions and steps described herein.

[0625] about Figure 20 and Figure 21 In one embodiment, the first signaling indicates the TAG id associated with the first cell.

[0626] In one embodiment, the second signaling indicates the TAG id associated with the first cell.

[0627] In one embodiment, the UE adds a first cell to a TAG associated with a TAG id (indicated by a first signaling and / or a second signaling).

[0628] In one embodiment, the UE releases / removes / deactivates a second cell in a TAG associated with a TAG id, where the second cell is not indicated in the second signaling. For example, the UE may release / remove / deactivate a second cell based on the second signaling not indicating a second cell (e.g., in response to receiving the second signaling).

[0629] In one embodiment, adding a first cell as an SCell may include (i) adding the first cell to the UE's set of SCells (e.g., the set of currently used and / or active SCells); (ii) activating the first cell; and / or (iii) treating the first cell as an SCell. The UE may use the first cell (e.g., as an SCell) after adding it as an SCell.

[0630] In one embodiment, the UE adds a first cell as a SCell and / or applies a timing advance value to the first cell in response to a second signaling.

[0631] about Figures 18 to 21 In one embodiment, the first signaling includes an RRC message.

[0632] In one embodiment, before the UE receives the second signaling, the first cell is (e.g., the UE's) non-serving cell and / or the UE's neighboring cell.

[0633] In one embodiment, the UE adds the first cell as an SCell by performing an SCell add operation.

[0634] In one embodiment, the UE adds a first cell as an SCell by applying the cell configuration of the first cell indicated in the first signaling.

[0635] In one embodiment, the second signaling indicates the index / identity associated with the first cell.

[0636] In one embodiment, the second signaling instructs the third cell, wherein the UE switches its SpCell to the third cell in response to the second signaling.

[0637] Figure 22This is a flowchart 2200 from the perspective of the UE according to an exemplary embodiment. In step 2205, the UE receives a first signaling indicating the configuration of a first cell, wherein the first cell is associated with a first TAG. The configuration may correspond to the cell configuration of the first cell (e.g., one or more parameters in ServingCellconfig and / or sCellConfigCommon and / or sCellConfigDedicated). In step 2210, the UE receives a second signaling indicating that the first cell be added as a first serving cell. For example, the second signaling may instruct the UE to add the first cell as a first serving cell. Alternatively and / or additionally, the second signaling may be used to add the first cell as a first serving cell. In step 2215, in response to the second signaling, the UE (i) adds the first cell as the first serving cell, and (ii) determines, based on the second signaling, whether to initiate a random access procedure and / or whether the first cell is associated with a first effective timing advance value.

[0638] In one embodiment, the second signaling includes PDCCH signaling and / or MAC CE. In some instances, the second signaling can be either PDCCH signaling or MAC CE.

[0639] In one embodiment, a first effective timing advance value may be determined to be valid based on the determination that a time alignment timer (e.g., timeAlignmentTimer) associated with the first effective timing advance value is running. The time alignment timer may correspond to a time alignment timer for a TAG (e.g., a first TAG) associated with the first effective timing advance value. In some instances, a timing advance value may be determined to be invalid based on the determination that a time alignment timer (e.g., timeAlignmentTimer) associated with the timing advance value is not running.

[0640] In one embodiment, the UE determines whether a first cell is associated with a first valid timing advance value by: (i) determining a first timing advance value associated with the first cell based on first signaling and / or second signaling (e.g., the first signaling and / or second signaling may indicate the first timing advance value and / or a TAG associated with the first timing advance value, such as a first TAG); and / or (ii) determining whether the first timing advance value is valid based on whether a time alignment timer (e.g., timeAlignmentTimer) associated with the first timing advance value is running. The first timing advance value may be determined to be valid based on determining that the time alignment timer is running (and therefore, the UE may determine that the first cell is associated with, for example, the first valid timing advance value). The first timing advance value may be determined to be invalid based on determining that the time alignment timer is not running (and therefore, the UE may determine that the first cell is not associated with, for example, the first valid timing advance value).

[0641] In one embodiment, the first signaling and / or the second signaling indicate a first effective timing advance value and / or a TAG (e.g., the first TAG) associated with the first effective timing advance value.

[0642] In one embodiment, a first signaling and / or a second signaling is configured (and / or allowed) to indicate a first effective timing advance value and / or a TAG (e.g., a first TAG) associated with the first effective timing advance value.

[0643] In one embodiment, an entity (e.g., a network) that configures (and / or allows) the transmission of first signaling and / or second signaling includes an indication of a first effective timing advance value and / or a TAG (e.g., a first TAG) associated with the first effective timing advance value in the first signaling and / or second signaling.

[0644] In one embodiment, the UE responds to a second signaling message by applying a first effective timing advance value associated with the first cell.

[0645] In one embodiment, the UE applies a first effective timing advance value associated with the first cell after adding the first cell as the first serving cell.

[0646] In one embodiment, the UE initiates a random access procedure based on determining that no valid timing advance value is associated with the first cell (and / or determining that the first cell is not associated with the first valid timing advance value). For example, determining that no valid timing advance value is associated with the first cell may be based on determining that the timing advance value associated with the first cell is invalid (e.g., the time alignment timer associated with the timing advance value is not running).

[0647] In one embodiment, if no valid timing advance value is associated with the first cell (and / or the first cell is not associated with the first valid timing advance value) (and / or when no valid timing advance value is associated with the first cell (and / or the first cell is not associated with the first valid timing advance value)), the UE initiates a random access procedure.

[0648] In one embodiment, the UE does not initiate a random access procedure based on the fulfillment of one or more conditions (e.g., based on determining that one or more conditions are met). For example, the UE does not initiate a random access procedure if one or more conditions are met (and / or when one or more conditions are met). One or more conditions include a condition that the first cell is associated with a first effective timing advance value. The UE may determine that the first cell is associated with the first effective timing advance value by: (i) determining a first timing advance value associated with the first cell (e.g., a first effective timing advance value) (e.g., the first timing advance value may be determined based on a first signaling and / or a second signaling); and / or (ii) determining that the first timing advance value is valid based on determining that the time alignment timer associated with the first timing advance value is running (and therefore, determining that the first cell is associated with, for example, the first effective timing advance value).

[0649] In one embodiment, the second signaling includes an indication (e.g., a command) of whether to initiate a random access procedure. For example, if the indication in the second signaling indicates to initiate a random access procedure (e.g., if the indication indicates the UE to initiate a random access procedure), then the UE may initiate a random access procedure based on the indication. Alternatively and / or additionally, if the indication in the second signaling indicates not to initiate a random access procedure (e.g., if the indication indicates the UE not to initiate a random access procedure), then the UE does not initiate a random access procedure based on the indication.

[0650] In one embodiment, adding a first cell as a first serving cell includes applying the configuration of the first cell.

[0651] In one embodiment, the first signaling indicates a second configuration for the second cell, wherein the second cell is associated with a second TAG. The second configuration may correspond to the cell configuration of the second cell (e.g., one or more parameters in ServingCellconfig and / or sCellConfigCommon and / or sCellConfigDedicated).

[0652] In one embodiment, the second signaling instructs the UE to add a second cell as a second serving cell. For example, the second signaling may instruct the UE to add a second cell as a second serving cell. Alternatively and / or additionally, the second signaling may be used to add a second cell as a second serving cell (e.g., in addition to adding a first cell as a first serving cell). The UE adds the second cell as a second serving cell in response to the second signaling.

[0653] In one embodiment, the determination of whether to initiate a random access procedure (in response to a second signaling) is based on whether the second cell is associated with a second effective timing advance value.

[0654] In one embodiment, the UE determines whether a second cell is associated with a second valid timing advance value by: (i) determining a second timing advance value associated with the second cell based on a first signaling and / or a second signaling (e.g., the first and / or second signaling may indicate a second timing advance value and / or a TAG associated with the second timing advance value, such as a second TAG); and / or (ii) determining whether the second timing advance value is valid based on whether a time alignment timer (e.g., timeAlignmentTimer) associated with the second timing advance value is running. The second timing advance value may be valid based on determining that the time alignment timer is running (and therefore, the UE may determine that the second cell is associated with, for example, a second valid timing advance value). The second timing advance value may be invalid based on determining that the time alignment timer is not running (and therefore, the UE may determine that the second cell is not associated with, for example, a second valid timing advance value).

[0655] In one embodiment, the UE initiates a random access procedure based on determining (i) that a first cell is associated with a first valid timing advance value (which can be determined by determining a first timing advance value associated with the first cell and / or determining that the first timing advance value is valid) and (ii) that no valid timing advance value is associated with a second cell (which can be determined by determining a second timing advance value associated with the second cell and / or determining that the second timing advance value is invalid).

[0656] In one embodiment, the first signaling and / or the second signaling indicate a second effective timing advance value associated with the second cell and / or a TAG associated with the second effective timing advance value.

[0657] In one embodiment, a first signaling and / or a second signaling is configured (and / or allowed) to indicate a second effective timing advance value and / or a TAG associated with the second effective timing advance value.

[0658] In one embodiment, an entity (e.g., a network) that configures (and / or allows) the transmission of first signaling and / or second signaling includes an indication of a second effective timing advance value and / or a TAG associated with the second effective timing advance value in the first signaling and / or second signaling.

[0659] In one embodiment, the first signaling and / or the second signaling indicates (i) a first effective timing advance value and a second effective timing advance value and / or (ii) a TAG associated with the first effective timing advance value and a TAG associated with the second effective timing advance value.

[0660] In one embodiment, a first signaling and / or a second signaling instruction is configured (and / or enabled) to indicate (i) a first effective timing advance value and a second effective timing advance value and / or (ii) a TAG associated with the first effective timing advance value and a TAG associated with the second effective timing advance value.

[0661] In one embodiment, the entity (e.g., a network) that configures (and / or allows) the transmission of the first signaling and / or the second signaling includes in the first signaling and / or the second signaling (i) a first effective timing advance value and a second effective timing advance value and / or (ii) an indication of a TAG associated with the first effective timing advance value and a TAG associated with the second effective timing advance value.

[0662] In one embodiment, adding a first cell as a first serving cell may include (i) adding the first cell to the set of serving cells of the UE (e.g., the set of currently used and / or active serving cells); (ii) activating the first cell; and / or (iii) treating the first cell as the first serving cell. The UE may use the first cell (e.g., as the first serving cell) after adding it as the first serving cell.

[0663] In one embodiment, adding a second cell as a second serving cell may include (i) adding the second cell to the UE's set of serving cells (e.g., the set of currently used and / or active serving cells); (ii) activating the second cell; and / or (iii) treating the second cell as a second serving cell. The UE may use the second cell (e.g., as a second serving cell) after adding it as a second serving cell.

[0664] Return to reference Figure 3 and Figure 4 In one exemplary embodiment of the UE, apparatus 300 includes program code 312 stored in memory 310. CPU 308 is executable program code 312 to enable the UE to (i) receive first signaling indicating the configuration of a first cell, wherein the first cell is associated with a first TAG; (ii) receive second signaling indicating the addition of the first cell as a first serving cell (e.g., PDCCH signaling and / or MAC CE); and (iii) in response to the second signaling, (A) add the first cell as the first serving cell, and determine, based on the second signaling, whether to initiate a random access procedure and / or whether the first cell is associated with a first effective timing advance value. Furthermore, CPU 308 may execute program code 312 to perform one, some, and / or all of the above actions and steps and / or other actions and steps described herein.

[0665] A communication device (e.g., UE, base station, network node, etc.) may be provided, wherein the communication device may include a control circuit, a processor mounted in the control circuit, and / or a memory mounted in the control circuit and coupled to the processor. The processor may be configured to execute program code stored in the memory to perform... Figures 18 to 22 The methods and steps described herein. Furthermore, the processor can execute program code to perform one, some, and / or all of the above actions and steps and / or other actions and steps described herein.

[0666] Computer-readable media may be provided. The computer-readable media may be non-transitory computer-readable media. The computer-readable media may include flash memory devices, hard disks, disks (e.g., magnetic disks and / or optical disks, such as at least one of digital versatile discs (DVDs), compact discs (CDs), etc.), and / or memory semiconductors, such as at least one of static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), etc. The computer-readable media may include processor-executable instructions that, when executed, cause execution to... Figures 18 to 22 One, some, and / or all of the steps of the method described herein and / or one, some, and / or all of the above actions and steps and / or other actions and steps described herein.

[0667] It is understood that applying one or more of the techniques presented herein may produce one or more benefits, including but not limited to improving the efficiency of communication between devices (e.g., UE and / or network nodes). This efficiency improvement may result in the UE being able to handle cell (e.g., SCell) timing alignment during mobility changes (e.g., L1 / L2 mobility enhancement SCell / SCG changes), thereby enabling the UE to change cells (e.g., from using one or more first cells to using one or more second cells) and / or add and / or activate cells.

[0668] Various aspects of this disclosure have been described above. It should be understood that the teachings herein can be implemented in a wide variety of forms, and any particular structure, function, or both disclosed herein are merely representative. Based on the teachings herein, those skilled in the art will understand that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in different ways. For example, any number of aspects set forth herein can be used to implement an apparatus or practice. Furthermore, this apparatus or practice can be implemented or practiced by using other structures, functions, or structures and functions other than or different from one or more aspects set forth herein. As examples of some of the foregoing concepts, in some aspects, a parallel channel can be established based on the pulse repetition frequency. In some aspects, a parallel channel can be established based on the pulse position or offset. In some aspects, a parallel channel can be established based on a time-hopping sequence. In some aspects, a parallel channel can be established based on the pulse repetition frequency, the pulse position or offset, and the time-hopping sequence.

[0669] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0670] Those skilled in the art will further appreciate that the various illustrative logic blocks, modules, processors, components, circuits, and algorithmic steps described in conjunction with the aspects disclosed herein can be implemented as electronic hardware (e.g., a digital implementation designed using source decoding or some other technique, an analog implementation, or a combination of both), incorporating various forms of program or design code with instructions (which, for convenience, may be referred to herein as "software" or "software module"), or a combination of both. To clearly illustrate the interchangeability of hardware and software, the various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as a departure from the scope of this disclosure.

[0671] Furthermore, the various illustrative logic blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within or executed by an integrated circuit (“IC”), access terminal, or access point. An IC may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute code or instructions residing within the IC, outside the IC, or both. A general-purpose processor may be a microprocessor; however, alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0672] It should be understood that any particular order or hierarchy of steps in any disclosed process is an instance of the exemplary method. Based on design preferences, it should be understood that a particular order or hierarchy of steps in the process may be rearranged while remaining within the scope of this disclosure. The appended method claims give the elements of each step in an exemplary order, but this does not imply limitation to the given particular order or hierarchy.

[0673] The steps of the methods or algorithms described in conjunction with the aspects disclosed herein can be implemented directly in hardware, with software modules executed by a processor, or a combination of both. Software modules (e.g., containing executable instructions and associated data) and other data can reside in data memory, such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of computer-readable storage media known in the art. Example storage media can be coupled to a machine such as a computer / processor (for convenience, this machine may be referred to herein as a "processor"), such that the processor can read information (e.g., code) from the storage media and write information to the storage media. Example storage media can be integrated with a processor. The processor and storage media can reside in an ASIC. The ASIC can reside in a user equipment. Alternatively, the processor and storage media can reside in a user equipment as discrete components. Alternatively and / or additionally, in some aspects, any suitable computer program product may include computer-readable media comprising code associated with one or more aspects of this disclosure. In some respects, computer program products may include packaging materials.

[0674] Although the disclosed subject matter has been described in conjunction with various aspects, it should be understood that the disclosed subject matter is subject to further modifications. This application is intended to cover any changes, uses, or adaptations of the disclosed subject matter that generally follow the principles of the disclosed subject matter and include deviations from the scope of practice known and customary in the art to which this disclosure pertains.

Claims

1. A method for a user equipment, characterized in that, The method includes: Receive first signaling indicating the configuration of a first cell, wherein the first cell is associated with a first timing advance group; Receiving a second signaling instruction to switch the user equipment's special cell to the first cell and an advance indication of timing information, the second signaling including a media access control element; and In response to the second signaling, the user equipment is switched from the special cell to the first cell, and at least based on whether the timing advance information is valid, a random access procedure is initiated on the first cell.

2. The method according to claim 1, characterized in that: At least one indication of the first signaling or the second signaling: Timing advance groups associated with the aforementioned timing advance information.

3. The method according to claim 1, characterized in that, The method includes: If the timing advance information is valid, the timing advance information associated with the first cell is applied in response to the second signaling.

4. The method according to claim 1, characterized in that, The method includes: After adding the first cell as the first serving cell, the timing advance information associated with the first cell is applied.

5. The method according to claim 1, characterized in that, The method includes: The random access procedure is initiated at least based on the determination that the timing advance information associated with the first cell is invalid.

6. The method according to claim 1, characterized in that, The method includes: The random access procedure will not be initiated if one or more conditions are met, wherein the timing advance information associated with the first cell is valid.

7. The method according to claim 1, characterized in that: The timing advance information indicates whether to initiate the random access procedure.

8. The method according to claim 1, characterized in that: Switching the user equipment to the special cell of the first cell includes applying the configuration of the first cell.

9. The method according to claim 1, characterized in that: The first signaling indicates a second configuration of the second cell, wherein the second cell is associated with a second timing advance group.

10. The method according to claim 9, characterized in that: The second signaling instruction indicates that the second cell be added as the second serving cell; and The method includes adding the second cell as the second serving cell in response to the second signaling.

11. The method according to claim 9, characterized in that: In response to the second signaling, a determination is made as to whether to initiate a random access procedure on the second cell based on whether the second cell is associated with a second effective timing advance value.

12. The method according to claim 11, characterized in that, The method includes: The random access procedure is initiated on the second cell based on the following determinations: The timing advance information associated with the first cell is valid; and There is no effective lead time value associated with the second cell.

13. The method according to claim 9, characterized in that: The second signaling indicates at least one of the following: The second effective timing advance value associated with the second cell; or Timing advance group associated with the second effective timing advance value.

14. The method according to claim 9, characterized in that: At least one of the first signaling or the second signaling indicates at least one of the following: The timing advance information and the second effective timing advance value associated with the second cell; or Timing advance groups associated with the timing advance information and timing advance groups associated with the second effective timing advance value.

15. A user equipment, characterized in that, The user equipment includes: Control circuit; The processor, which is installed in the control circuit; and A memory, mounted in the control circuitry and operatively coupled to the processor, wherein the processor is configured to execute program code stored in the memory to perform operations, the operations including: Receive first signaling indicating the configuration of a first cell, wherein the first cell is associated with a first timing advance group; Receiving a second signaling instruction to switch the user equipment's special cell to the first cell and an advance indication of timing information, the second signaling including a media access control element; and In response to the second signaling, the user equipment is switched from the special cell to the first cell, and at least based on whether the timing advance information is valid, a random access procedure is initiated on the first cell.

16. The user equipment according to claim 15, characterized in that: At least one indication of the first signaling or the second signaling: Timing advance groups associated with the aforementioned timing advance information.

17. The user equipment according to claim 15, characterized in that, The operation includes: The random access procedure is initiated at least based on the determination that the timing advance information associated with the first cell is invalid.

18. The user equipment according to claim 15, characterized in that, The operation includes: The random access procedure will not be initiated if one or more conditions are met, wherein the timing advance information associated with the first cell is valid.

19. The user equipment according to claim 15, characterized in that: The timing advance information indicates whether to initiate the random access procedure.

Images