Method for uplink transmission and reception and apparatus therefor

Abstract

A method according to an embodiment of the present specification comprises the steps of: receiving a cell group configuration; receiving configuration information related to a first serving cell among the serving cells; and transmitting an uplink signal related to the first serving cell based on the unified TCI state related to a second serving cell among the serving cells. The cell group configuration includes a list of simultaneously updated serving cells applying a unified TCI state. The uplink timing associated with the uplink signal is determined based on the TAG associated with the unified TCI state. The TAG is associated with a first TAG ID or a second TAG ID of a first serving cell applying a unified TCI state.

Description

Technical Field

[0001] This disclosure relates to methods and apparatus for uplink transmission and reception in wireless communication systems. Background Technology

[0002] Mobile communication systems have evolved to the point where they can provide voice services while maintaining user activity. These systems are expanding their services from voice-only to data. The current surge in data traffic is exhausting resources, and user demand for higher data rates necessitates more advanced mobile communication systems.

[0003] Next-generation mobile communication systems need to meet requirements such as handling explosive growth in data traffic, significantly increasing transmission rates for individual users, working with a large number of connected devices, and supporting very low end-to-end latency and high energy efficiency. To this end, various research efforts are underway targeting a range of technologies, including dual connectivity, massive MIMO, in-band full-duplex, non-orthogonal multiple access (NOMA), ultra-wideband support, and device networking.

[0004] In existing LTE and NR standards, in the uplink timing advance configuration / indication, a single timing advance (TA) value is supported for the timing advance group (TAG) to which a specific cell or cell group belongs.

[0005] In environments where there is a significant distance difference between the UE and different Transmit and Receive Points (TRPs), multi-DCI-based multi-TRP (M-DCI-based M-TRP) operation can be performed. In this case, within the CC / BWP, differences in propagation delay, slot boundary differences, and inter-UE panel delay may occur between the target TRPs for uplink transmission. In particular, this phenomenon may occur more extensively in non-ideal backhaul operations where coordination is not performed between TRPs.

[0006] As mentioned above, to compensate for timing differences or delays between TRPs, uplink timing needs to be determined differently for each TRP. For this purpose, it has been agreed to connect / map TAGs to the TCI state of a unified TCI (e.g., joint TCI state, individual TCI state (DL TCI state or UL TCI state)). To support TRP-specific TAs (i.e., to support two TAs for two TRPs), two TAGs can be configured within a serving cell.

[0007] The CC list (Serving Cell List) can be configured to update the TCI state of CCs (Serving Cells) simultaneously. In this example, the TCI state (TCI state pool) can be configured only for the reference CC in the CC list. For CCs in the CC list other than the reference CC (e.g., non-reference CCs), transmit / receive operations related to the CC (non-reference CC) can be performed based on the TCI state defined / configured for the reference CC. Summary of the Invention

[0008] Technical issues

[0009] According to the current standard, it is not assumed that CCs within a CC list belong to the same TAG. Therefore, any CC in the CC list (e.g., a non-reference CC) and another CC (e.g., a reference CC) may belong to different TAG-ids. Since the information for the TAG-id associated with each TCI state (joint TCI state and / or UL TCI state) is configured via RRC signaling, the following issues may occur.

[0010] The TCI state configured for the reference CC (within the TCI state pool) is used for non-reference CCs. Due to the association between TAG-id and TCI state, a TAG-id associated with / related to the reference CC can be used for uplink transmissions performed in a non-reference CC. In other words, a TAG-id different from the TAG-id configured for a non-reference CC can be used for uplink transmissions associated with a non-reference CC. In this case, uplink timing may not be suitable for the non-reference CC.

[0011] The purpose of this disclosure is to provide a method for solving the above-mentioned problems.

[0012] The technical objectives to be achieved by this disclosure are not limited to those described above by way of example only, and other technical objectives not mentioned can be clearly understood by those skilled in the art from the following description.

[0013] Technical solution

[0014] A method performed by a user equipment (UE) according to an embodiment of the present disclosure includes the following steps: receiving cell group configuration, receiving configuration information related to a first serving cell in the serving cells, and sending an uplink signal related to the first serving cell based on a unified TCI state related to a second serving cell in the serving cells.

[0015] Cell group configuration includes a list of serving cells updated simultaneously with the application of the Uniform Transport Configuration Indicator (TCI) status. The first timing advance group (TAG) ID and the second TAG ID are configured based on the configuration information.

[0016] The uplink timing associated with the uplink signal is determined based on the TAG associated with the unified TCI state.

[0017] The TAG is associated with the first TAG ID or the second TAG ID of the first serving cell in the application unified TCI status.

[0018] The serving cell can correspond to a component carrier (CC).

[0019] The second serving cell can be based on the reference CC in the CC corresponding to the serving cell.

[0020] The first serving cell can be based on a first CC that is different from the reference CC in the CC corresponding to the serving cell.

[0021] The bandwidth portion (BWP) of the first CC may not contain a unified TCI state configuration.

[0022] The unified TCI status can be correlated with the reference BWP of the reference CC.

[0023] The unified TCI status can include TAG ID information. Based on the TAG ID information being set to a first value, the TAG can be a first TAG indicated by a first TAG ID of the first serving cell. Based on the TAG ID information being set to a second value, the TAG can be a second TAG indicated by a second TAG ID of the first serving cell.

[0024] The first TAG may be the same as or different from the TAG indicated by the first TAG ID configured for the second serving cell.

[0025] The second TAG may be the same as or different from the TAG indicated by the second TAG ID configured for the second serving cell.

[0026] A unified TCI state can be a combined TCI state or a separate TCI state.

[0027] The method may further include the following step: receiving a Media Access Control-Control Element (MAC CE). The MAC CE may be associated with the activation and / or deactivation of the Uniform TCI state. Since the serving cell indicated by the MAC CE is part of the serving cell, the MAC CE can be applied to the serving cell.

[0028] The unified TCI state can be the unified TCI state indicated by downlink control information (DCI) in the unified TCI state activated based on MAC CE.

[0029] A user equipment (UE) according to another embodiment of the present disclosure includes: one or more transceivers; one or more processors; and one or more memories connected to one or more processors and configured to store instructions.

[0030] The instructions are based on all the steps of configuring one or more processors to perform any of the methods in the method, which are executed by one or more processors.

[0031] An apparatus according to another embodiment of the present disclosure includes: one or more memories; and one or more processors operatively connected to the one or more memories. The one or more memories are configured to store instructions based on instructions executed by the one or more processors, and the instructions are configured to allow the one or more processors to perform all steps of any of the methods described.

[0032] One or more non-transitory computer-readable media according to another embodiment of this disclosure store instructions. These instructions, executable by one or more processors, are configured to allow one or more processors to perform all steps of any of the methods described.

[0033] A method performed by a base station according to another embodiment of the present disclosure includes the following steps: sending cell group configuration, sending configuration information related to a first serving cell in the serving cells, and receiving uplink signals related to the first serving cell based on a unified TCI state related to a second serving cell in the serving cells.

[0034] Cell group configuration includes a list of serving cells updated simultaneously with the application of the Uniform Transport Configuration Indicator (TCI) status. The first timing advance group (TAG) ID and the second TAG ID are configured based on the configuration information.

[0035] The uplink timing associated with the uplink signal is determined based on the TAG associated with the unified TCI state.

[0036] The TAG is associated with the first TAG ID or the second TAG ID of the first serving cell in the application unified TCI status.

[0037] A base station according to another embodiment of the present disclosure includes: one or more transceivers; one or more processors; and one or more memories connected to one or more processors and storing instructions.

[0038] The instructions are based on all steps of configuring one or more processors to perform the method, which are executed by one or more processors.

[0039] Beneficial effects

[0040] According to embodiments of this disclosure, uplink signals associated with a first serving cell (e.g., a non-reference CC) are transmitted based on a TCI state associated with a second serving cell (e.g., a reference CC). Uplink timing associated with the uplink signals is determined based on a TAG-ID associated with a TAG configured for the first serving cell applying the TCI state.

[0041] Therefore, even if the serving cells in the list used to update the TCI status at the same time belong to different TAGs (e.g., even if different TAG IDs are configured for the reference CC and non-reference CC), the ambiguity for the TAG to be used to perform uplink transmissions related to a specific serving cell (non-reference CC) can be resolved.

[0042] Furthermore, in uplink transmissions associated with the first serving cell (non-reference CC) that utilize the TCI state associated with the second serving cell (reference CC), degradation of uplink timing accuracy (i.e., when using the TAG associated with the second serving cell) can be prevented.

[0043] It also prevents uplink retransmissions caused by inaccurate uplink timing. In other words, unnecessary signaling overhead can be prevented during uplink transmission and reception, which are performed based on the TCI state updated simultaneously by the application.

[0044] The effects that can be achieved using this disclosure are not limited to those described above by way of example only. Other effects and advantages of this disclosure will become clearer to those skilled in the art from the following description. Attached Figure Description

[0045] Figure 1 An example of a MAC RAR according to an embodiment of the present disclosure is shown.

[0046] Figure 2 An example of a timing advance command MAC CE according to an embodiment of the present disclosure is illustrated.

[0047] Figure 3 An example is provided of a TCI state activation / deactivation MAC CE that can be implemented using embodiments of this disclosure.

[0048] Figure 4 This is a flowchart illustrating a method performed by a user equipment according to an embodiment of the present disclosure.

[0049] Figure 5 This is a flowchart illustrating a method performed by a base station according to another embodiment of the present disclosure.

[0050] Figure 6The configurations of the first and second devices according to embodiments of the present disclosure are illustrated. Detailed Implementation

[0051] Preferred embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. The following detailed description, taken in conjunction with the drawings, is intended to describe embodiments of the present disclosure, but does not represent the only embodiments of the present disclosure. The detailed description below includes specific details to convey a thorough understanding of the present disclosure. However, those skilled in the art will readily understand that embodiments of the present disclosure can be practiced even without these details.

[0052] In some cases, to avoid conceptual ambiguity, known structures or devices may be omitted or shown in block diagrams, while the focus is placed on the core features of each structure and device.

[0053] In the following text, downlink (DL) refers to communication from a base station to a terminal, and uplink (UL) refers to communication from a terminal to a base station. In the downlink, the sender can be part of the base station, and the receiver can be part of the terminal. In the uplink, the sender can be part of the terminal, and the receiver can be part of the base station. A base station can be referred to as a first communication device, and a terminal can be referred to as a second communication device. The term base station (BS) can be replaced by terms including fixed station, Node B, evolved Node B (eNB), next-generation Node B (gNB), base transceiver system (BTS), access point (AP), network (5G network), AI system, roadside unit (RSU), vehicle, robot, unmanned aerial vehicle (UAV), augmented reality (AR) device, virtual reality (VR) device, etc. Furthermore, the terminal can be fixed or mobile, and can be replaced by terms including user equipment (UE), mobile station (MS), user terminal (UT), mobile subscriber station (MSS), subscriber station (SS), advanced mobile station (AMS), wireless terminal (WT), machine-type communication (MTC) device, machine-to-machine (M2M) device and device-to-device (D2D) device, vehicle, robot, AI module, unmanned aerial vehicle (UAV), augmented reality (AR) device, virtual reality (VR) device, etc.

[0054] Multiple Transmit / Receive Point (M-TRP) related operations

[0055] M-TRP transmission schemes, in which M TRPs send data to a single User Equipment (UE), can be divided into two main types: eMBB M-TRP transmission, which is used to increase the transmission rate, and URLLC M-TRP transmission, which is used to increase the reception success rate and reduce latency.

[0056] UL MTRP-URLLC means that multiple TRPs use different layer / time / frequency resources to receive the same data / UCI from a UE. For example, TRP 1 receives the same data / UCI from the UE in resource 1, TRP 2 receives the same data / UCI from the UE in resource 2, and then shares the received data / UCI through the backhaul link connected between the TRPs. A UE configured with the UL MTRP-URLLC transmission scheme transmits the same data / DCI using different layer / time / frequency resources. In this case, the BS indicates to the UE which transmit beam and which transmit power (i.e., the UL TCI state) to use in the layer / time / frequency resources for transmitting the same data / DCI. For example, when transmitting the same data / UCI in resource 1 and resource 2, the UL TCI state used in resource 1 and the UL TCI state used in resource 2 are indicated. UL MTRP URLLC can be applied to PUSCH / PUCCH.

[0057] MTRP transmission based on SDCI or MDCI

[0058] From the perspective of downlink control information (DCI) transmission, M-TRP (multi-TRP) transmission schemes can be divided into i) M-TRP transmission schemes based on multiple DCI (M-DCI), where each TRP transmits a different DCI and ii) M-TRP transmission schemes based on a single DCI (S-DCI), where one TRP transmits a DCI.

[0059] R16 NR MTRP transmission

[0060] The R16 NR standard supports both S-DCI-based MTRP PDSCH transmission schemes and M-DCI-based MTRP PDSCH transmission schemes.

[0061] MTRP PDSCH based on R16 M-DCI

[0062] MTRP PDSCH transmission based on M-DCI is a method where each TRP schedules and transmits PDSCHs via DCI. That is, TRP 1 transmits PDSCH 1 via DCI 1, and TRP 2 transmits PDSCH 2 via DCI 2. When PDSCH 1 and PDSCH 2 overlap in the same frequency time resource, both PDSCHs are received for the same RE, thereby improving resource efficiency and increasing transmission capacity. To this end, the R16 standard introduces CORESET pools, which are groups of multiple CORESETs. TRP 1 transmits PDCCHs through CORESETs belonging to CORESET pool 0, and PDSCHs scheduled by the corresponding PDCCHs are also transmitted by TRP 1. TRP 2 transmits PDCCHs through CORESETs belonging to CORESET pool 1, and PDSCHs scheduled by the corresponding PDCCHs are also transmitted by TRP 2. For PUSCHs, a specific TRP can schedule the transmission of PUSCHs to the UE through CORESETs belonging to each CORESET pool. For PUCCH, TRP 1 schedules some PUCCH resources to receive UCI, and TRP 2 schedules the remaining PUCCH resources to receive UCI. For PUSCH or PUCCH, the channels scheduled / used by each TRP are TDM-based and do not overlap. Therefore, no increase in transmission capacity can be expected, but the UE can independently send PUSCH / PUCCH to each of TRP 1 and TRP 2.

[0063] Furthermore, the UE can identify PUSCH (or PUCCH) received by DCI and received through different CORESETs (or CORESETs belonging to different CORESET groups) as PUSCH (or PUCCH) sent to different TRPs, or identify PUSCH (or PUCCH) of different TRPs. The scheme for UL transmissions (e.g., PUSCH / PUCCH) sent to different TRPs can also be applied to UL transmissions (e.g., PUSCH / PUCCH) sent to different panels belonging to the same TRP.

[0064] The CORESET group ID (or COERSET pool index with the same meaning) described / mentioned in this disclosure may refer to index / identification information (e.g., ID) used to distinguish CORESETs for each TRP / panel. Furthermore, a CORESET group may be a group / union of CORESETs categorized by index / identification information (e.g., ID) / CORESET group ID, etc., used to distinguish CORESETs for each TRP / panel. For example, a CORESET group ID may be specific index information defined in the CORESET configuration. For example, a CORESET group may be configured / indicated / defined by an index defined in the CORESET configuration for each CORESET. And / or, a CORESET group ID may refer to index / identification information / indicators, etc., used to distinguish / identify CORESETs configured / associated with each TRP / panel, and the CORESET group ID described / mentioned in this disclosure may be replaced and expressed by specific indexes / specific identification information / specific indicators, etc., used to distinguish / identify CORESETs configured / associated with each TRP / panel. The CORESET group ID, i.e., the specific index / identification information / specific indicator used to distinguish / identify the CORESET configured / associated with each TRP / panel, can be configured / indicated through higher-layer signaling (e.g., RRC signaling) / L2 signaling (e.g., MAC-CE) / L1 signaling (e.g., DCI). For example, PDCCH detection for each TRP / panel can be configured / indicated to be performed on a per-CORESET group basis, and / or uplink control information (e.g., CSI, HARQ-A / N, SR) and / or uplink physical channel resources (e.g., PUCCH / PRACH / SRS resources) can be configured / indicated to be managed / controlled individually for each TRP / panel on a per-CORESET group basis, and / or HARQ A / N (processing / retransmission) of PDSCH / PUSCH scheduled for each TRP / panel can be managed on a per-CORESET group basis.

[0065] For example, the high-layer parameter ControlResourceSet IE (Information Element) is used to configure the time / frequency control resource set (CORESET). For example, the control resource set (CORESET) may be related to the detection and reception of downlink control information. The ControlResourceSet IE may include the CORESET-related ID (e.g., controlResourceSetID) / the index of the CORESET pool for the CORESET (e.g., CORESETPoolIndex) / the time-frequency resource configuration of the CORESET / the TCI information related to the CORESET, etc. For example, the index of the CORESET pool (e.g., CORESETPoolIndex) may be set to 0 or 1. In the specification, the CORESET group may correspond to the CORESET pool, and the CORESET group ID may correspond to the CORESET pool index (e.g., CORESETPoolIndex). The ControlResourceSet (i.e., CORESET) may be configured by high-layer signaling (e.g., RRC).

[0066] <Meaning of TCI state / beam indication>

[0067] In addition, in the method proposed by the present disclosure below, the meaning of using ( / mapping) a specific TCI state (or TCI) when receiving data / DCI / UCI for a certain frequency / time / space resource is as follows.

[0068] For DL, using ( / mapping) a specific TCI state (or TCI) when receiving data / DCI / UCI for a certain frequency / time / space resource may mean using the QCL type and QCL RS indicated by the DL TCI state in that frequency / time / space resource to estimate the channel from the DMRS, and receiving / demodulating the data / DCI using the estimated channel.

[0069] For UL, using ( / mapping) a specific TCI state (or TCI) when receiving data / DCI / UCI for a certain frequency / time / space resource may mean transmitting / modulating the DMRS and data / UCI by using the transmission beam and / or transmission power indicated by the UL TCI state.

[0070] The UL TCI state may include the transmission beam or transmission power information of the UE, and the spatial relationship information may be configured to the UE by other parameters (rather than the TCI state). The UL TCI state may mean the spatial relationship information of the SRS resource, which may be directly indicated by the UL grant DCI, or may be indicated by the SRI field of the UL grant DCI.

[0071] Alternatively, the UL TCI state may mean the OL transmission power control parameters (j: index for the open-loop parameters Po and α (up to 32 parameter value sets per cell), q_d: index for the DL RS resources for PL measurement (up to 4 measurements per cell), and l: closed-loop power control process index (up to 2 processes per cell)), which are connected to the value indicated by the SRI field of the UL grant DCI. Alternatively, in R17 NR, the DL grant DCI may be used to indicate the UL TCI.

[0072] <Extended description related to TRP classification>

[0073] For ease of description, this disclosure is applied to the proposed scheme by assuming cooperative transmission / reception between 2 TRPs, but it can be widely applied to a multi-TRP environment with 3 or more TRPs, and can also be widely applied to a multi-panel environment. Different TRPs can be perceived by the UE as different TCI states (associated with different CORESET pool indices).

[0074] For example, the UE receiving data / DCI using the first TCI state associated with the first CORESET pool index means that the data / DCI is received from TRP1. For example, the UE sending data / DCI using the first TCI state associated with the first CORESET pool index means that the data / DCI is sent to TRP1.

[0075] For example, the UE receiving data / DCI using the second TCI state associated with the second CORESET pool index means that the data / DCI is received from TRP2. For example, the UE sending data / DCI using the second TCI state associated with the second CORESET pool index means that the data / DCI is sent to TRP1.

[0076] Timing Advance (TA) related procedures

[0077] The uplink frame number i for transmissions from a user equipment (UE) should start before the start of the corresponding downlink frame at that UE. Start.

[0078] The uplink timing (e.g., uplink frame) related to can be defined as follows. (For example, uplink frame).

[0079] Uplink timing

[0080] The uplink frame number for transmissions from the UE i should start before the start of the corresponding downlink frame at that UE. Start.

[0081] - and As given in Clause 4.2 of [5, TS 38.213], except for msgA transmissions on PUSCH, whereby the following shall be used .

[0082] - As given by Clause 4.2 of [5, TS 38.213]. It is obtained based on the high-level parameters TACommon, TACommonDrift, and TACommonDrift (if configured); otherwise, ; - As given by Clause 4.2 of [5, TS 38.213]. It is calculated by the UE based on higher-level parameters related to the UE's location and the serving satellite ephemeris (if configured); otherwise, .

[0083] Based on and To calculate / determine. and It can be configured / applied as follows.

[0084] 1) Configured via Random Access Response (RAR) and 2) Configured via Pre-Time Command (MAC-CE); 1) Configure specific values ​​for the serving cell and 2) Apply predefined values ​​based on duplex mode / FR appropriately to the serving cell.

[0085] The above configuration / application is described in detail below. and The method.

[0086]

[0087] Case 1) Method of configuring specific values ​​based on serving cell

[0088] For example, the UE can receive information from the base station including details about... Configuration information (e.g., ServingCellConfigCommon information). This configuration information can be received based on RRC signaling. Table 1 below shows the configuration information.

[0089] [Table 1]

[0090] Case 2) Appropriately applying predefined values ​​based on duplex mode / FR to the serving cell

[0091] For example, the UE can use predefined duplex modes (TDD / FDD) / FR. The values ​​are appropriately applied to the serving cell. Table 2 below shows... The value of .

[0092] [Table 2]

[0093] Scenario 1) Configuring via Random Access Response (RAR)

[0094] For example, in a random access procedure (e.g., a 2-step RACH procedure or a 4-step RACH procedure), the UE can receive a RAR from the base station. N can be determined / configured based on the RAR. TA Specifically, a RAR can include a timing advance command. This timing advance command indicates an index value (e.g., index value TA) associated with the timing adjustment. The timing can be determined based on this index value. RAR can be based on MAC RAR. This will be referenced below. Figure 1 Describe it.

[0095] Figure 1 An example of a MAC RAR according to an embodiment of the present disclosure is shown.

[0096] Reference Figure 1 A MAC RAR can include reserved bits R, timing advance commands, UL authorization, and temporary C-RNTI. The MAC payload of a MAC RAR is described in detail below.

[0097] 6.2.3 MAC payload for random access response

[0098] MAC RAR has the following features: Figure 6 It has a fixed size as shown in .2.3-1 and consists of the following fields.

[0099] - R: Reserved bit, set to 0; - TI: If two TAGs are configured for the serving cell performing a random access procedure, this field indicates one of the two TAGs for which the application timing advance command is applied. Setting this field to 0 indicates the first TAG ID, and setting it to 1 indicates the second TAG ID. If no two TAGs are configured for the serving cell performing a random access procedure, an R bit is present instead. - Timing Advance Command: The Timing Advance Command field in TS 38.213[6] indicates the index value TA of the timing adjustment that must be applied to control the MAC entity. The Timing Advance Command field is 12 bits in size; - UL Authorization: The uplink authorization field in TS 38.213[6] indicates the resources to be used on the uplink. The UL authorization field is 27 bits in size; - Temporary C-RNTI: The Temporary C-RNTI field indicates a temporary identifier used by the MAC entity during random access. The Temporary C-RNTI field is 16 bits in size.

[0100] MAC RAR is octet aligned.

[0101] The following describes transmission timing adjustment based on the timing advance command.

[0102] 4.2 Transmission Timing Adjustment

[0103] The timing advance offset of the serving cell can be provided to the UE via the n-TimingAdvanceOffset of the serving cell. If, for the serving cell, the UE is provided with two coresetPoolIndex values ​​of 0 and 1 for the first and second CORESETs, or is not provided with a coresetPoolIndex value for the first CORESET but is provided with a coresetPoolIndex value of 1 for the second CORESET, then the UE can be provided with the first coresetPoolIndex value via n-TimingAdvanceOffset and n-TimingAdvanceOffset2. value and second Values ​​are used for transmissions having TCI states associated with the first CORESET and the second CORESET, respectively. This is in addition to the first transmission utilizing a spatial domain filter corresponding to the TCI state associated with the serving cell's physCellId. In addition to the value, the UE can also be provided with a second transmission method that utilizes a spatial domain filter corresponding to a TCI state associated with a physCellId different from that of the serving cell. Value. First value and second The values ​​correspond to the first and second tags [11, TS 38.321], which have an association with the first and second joint TCI states provided by dl-OrJointTCI-StateList or the first and second UL TCI states provided by ul-TCI-StateList, as indicated by tag-Id-ptr. If no n-TimingAdvanceOffset of the serving cell is provided to the UE, the UE determines the default value of the timing advance offset of the serving cell. As described in [10, TS38.133].

[0104] If the UE is configured with two UL carriers for the serving cell, the same timing advance offset value will be used. Applied to two carriers associated with the same tag for transmission on the serving cell. The UE does not expect the two... The value is applied to transmission on the SUL carrier.

[0105] Upon receiving a timing advance command for the TAG, the UE will base its actions on the value... (The UE expects this value to be the same for all serving cells in this TAG) and adjusts the uplink timing of PUSCH / SRS / PUCCH transmissions for all serving cells in this TAG based on the received timing advance command (where the uplink timing of PUSCH / SRS / PUCCH transmissions is the same for all serving cells in this TAG).

[0106] For a frequency band with synchronous continuous EN-DC in a frequency band combination having an inapplicable maximum transmission timing difference requirement (as described in Note 1 of Table 7.5.3-1 of [10, TS 38.133]), if the UE indicates ul-TimingAlignmentEUTRA-NR as "Required" and the UE determines that the uplink transmission timing based on timing adjustments for TAGs from MCGs and TAGs from SCGs are different, the UE adjusts the transmission timing of PUSCH / SRS / PUCCH transmissions on all serving cell portions of the frequency band with synchronous continuous EN-DC based on the timing adjustment indication for TAGs from serving cells in the MCGs of that frequency band. The UE does not expect to transmit PUSCH / SRS / PUCCH in one CG when PUSCH / SRS / PUCCH overlaps in time with (even partially overlaps) a random access preamble transmitted in another CG.

[0107] against The SCS, for a TAG, indicates a change in the timing advance command relative to the current uplink timing for the TAG. Multiples of. The start timing of the random access preamble is described in [4, TS 38.211].

[0108] In the case of random access response, or in the absolute timing advance command MAC CE, or in the timing advance command in the cell handover command [11, TS 38.321] For TAG passing = 0, 1, 2, ..., 3846 to indicate Values, where for SCS are The time alignment of the tag is . Defined in [4, TS 38.211], and related to the SCS transmitted from the UE for the first time on the uplink after receiving a random access response or absolute timing advance command MAC CE or cell handover command.

[0109] In other cases, the timing advance command for TAG [11, TS 38.321] Indicates by index value =0, 1, 2,..., 63 will be the current value Adjusted to new value Among them, targeting SCS, .

[0110] If a UE has multiple active UL BWPs in the same TAG (as described in Clause 12), including UL BWPs in two UL carriers of the serving cell, the timing advance command value is associated with the largest SCS among the multiple active UL BWPs. For UL BWPs with lower SCS, the applicable... The value can be rounded to maintain consistency with the timing advance granularity of the UL BWP with a lower SCS, while meeting the timing advance accuracy requirements in [10, TS 38.133].

[0111] Adjust by increment or decrement The values ​​indicate the amount by which the uplink transmission timing for the TAG will be advanced or delayed.

[0112] For timing advance commands received on uplink time slot n, and for PUSCHs scheduled by RAR UL authorization or fallbackRAR UL authorization as described in Clauses 8.2A or 8.3, or for transmissions other than PUCCHs responding to successRAR with HARQ-ACK information as described in Clause 8.2A, the corresponding adjustment of uplink transmission timing from the uplink time slot n is as follows: The application begins here, where , This corresponds to the PDSCH processing time for UE processing capability 1 when additional PDSCH DM-RS is configured. The duration of each symbol (in milliseconds). This corresponds to the PUSCH preparation time for UE processing capability 1. Duration of each symbol (in milliseconds) [6, TS 38.214], It is the maximum timing advance value (in milliseconds) that the 12-bit TA command field can provide. It is the number of time slots in each subframe. It is the duration of a 1-millisecond subframe, and ,in Provided by cellSpecificKoffset, and Provided by the Differential Koffset MAC CE command [11, TS 38.321]; otherwise, if not provided separately, then or . and It is determined by the minimum SCS among all configurations of UL BWP for all uplink carriers in the TAG and all configurations of DL BWP for the corresponding downlink carriers. UE assumption [6, TS 38.214]. Time slot n and It is determined by the minimum SCS among all configured UL BWPs for all uplink carriers in the TAG. It is determined by the minimum SCS among all configured UL BWPs for all uplink carriers in the TAG and all configured initial UL BWPs provided by the initialUplinkBWP. Uplink slot n It is the last uplink time slot that overlaps with the PDSCH reception time slot, assuming Among them, PDSCH provides timing advance commands and Defined in [4, TS 38.211].

[0113] If the UE changes the active UL BWP between the time the timing advance command is received and the time of the corresponding adjustment for uplink transmission timing by the application, the UE determines the timing advance command value based on the SCS of the new active UL BWP. If the UE changes the active UL BWP after the application adjusts the uplink transmission timing, the UE will use the same absolute timing advance command value before and after the change of the active UL BWP.

[0114] If the received downlink timing changes and is not compensated or is only partially compensated by uplink timing adjustment without a timing advance command (as described in [10, TS 38.133]), then the UE will change accordingly. If the UE operates on an active UL BWP in the serving cell using two tags, the UE expects the difference between the first downlink timing associated with the first tag and the second downlink timing associated with the second tag to be no greater than the CP length for that active UL BWP, unless the UE indicates larger-thanCP-capability. If the UE indicates XYZ_capability, is provided with SRS-autonomousTAupdate [10, TS 38.133], and sends SRS in the RRC_INACTIVE state based on the configuration of SRS-PosResourceSet in SRS-PosRRC-InactiveConfig-ValidityArea, the UE can update autonomously during cell reselection. Otherwise, if the UE is not provided with SRS-autonomousTAupdate, the UE remains in the last serving cell prior to the release of the dedicated RRC connection. [11, TS38.321].

[0115] For operations using a single TAG on the serving cell, if two adjacent time slots overlap due to a TA command, the duration of the later time slot is shortened relative to the duration of the earlier time slot. During the actual transmission time window used for PUSCH or PUCCH transmission, the UE does not change... [6, TS 38.214]. If the UE is not provided with enableSTx2PofMDCI and operates using two TAGs on the serving cell, the UE does not expect transmission overlap associated with different TAGs unless the UE indicates XYZ; if the UE indicates XYZ, the UE shortens the duration of the subsequent transmission using the first TAG to avoid overlap with the preceding transmission using the second TAG.

[0116] Scenario 2) Configuring via Pre-Time Command (MAC-CE)

[0117] For example, MAC-CE can be used to determine / configure Specifically, it can be determined based on the timed advance command MAC CE. The MAC CE can include timed advance commands. This is because the determination is based on the timed advance commands. This is the same as described in Case 1, so repeated descriptions are omitted. See below for details. Figure 2 This describes the scheduled advance command MAC CE.

[0118] Figure 2 An example of a timing advance command MAC CE according to an embodiment of the present disclosure is illustrated.

[0119] Reference Figure 2 The timing advance command MAC CE can include a TAG ID and a timing advance command. The payload of the timing advance command MAC CE is described in detail below.

[0120] 6.1.3.4 Pre-timed command MAC CE

[0121] The MAC CE (Pre-Timed Command) is identified by a MAC sub-header with LCID, as specified in Table 6.2.1-1.

[0122] It has a fixed size and consists of a single octet, defined as follows ( Figure 6 .1.3.4-1): - TAG Identifier (TAG ID): This field indicates the TAG identifier of the addressed TAG. TAGs containing SpCells have TAG identifier 0. This field is 2 bits long; - Timing Advance Command: This field indicates the index value TA (0, 1, 2...63) of the timing adjustment amount that must be applied to control the MAC entity (as specified in TS 38.213 [6]). The field is 6 bits long.

[0123] 6.1.3.4a Absolute timing advance command MAC CE

[0124] The absolute timing advance command (MAC CE) is identified by a MAC subheader with eLCID, as specified in Table 6.2.1-1b.

[0125] It has a fixed size and consists of two octets, defined as follows ( Figure 6 .1.3.4a-1): - Timing Advance Command: This field indicates the index value TA used to control the amount of time adjustment that the MAC entity must apply in TS 38.213 [6]. This field is 12 bits in size; - TI: If two tags are configured for SpCell, this field indicates the tag on which the timing advance command is applied. Setting this field to 0 indicates the first tag ID, and setting it to 1 indicates the second tag ID. If no two tags are configured for SpCell, the R bit is used instead. - R: Reserved bit, set to 0.

[0126] TAG (Timed Advance Group)

[0127] A timing advance group (TAG) refers to a group of serving cells that use the same timing advance value. Table 3 below shows the definition of a TAG and the configuration information associated with it.

[0128] [Table 3]

[0129] process

[0130] The following describes in detail the operations for uplink time alignment.

[0131] 5.2 Uplink Time Alignment Maintenance

[0132] RRC configuration uses the following parameters to maintain UL time alignment: - timeAlignmentTimer (by TAG), which controls the MAC entity to determine the serving cell belonging to the associated TAG as the uplink time alignment time length. - inactivePosSRS-TimeAlignmentTimer, whose controlling MAC entity considers the positioning SRS transmission in clause 5.26 as the uplink time-aligned time length; - cg-SDT-TimeAlignmentTimer, whose controlling MAC entity considers the uplink transmission used for CG-SDT to be the uplink time-aligned time length.

[0133] MAC entities should: 1> When a timing advance command MAC CE is received, and if the NTA has been maintained using the indicated TAG (as defined in TS 38.211 [8]): 2> Apply the timed advance command to the indicated TAG; 2> If there is an ongoing location SRS transmission in RRC_INACTIVE, as described in Clause 5.26: 3> Start or restart the inactivePosSRS-TimeAlignmentTimer associated with the indicated TAG.

[0134] 2> If the triggered CG-SDT procedure (as described in Clause 5.27) is in progress: 3> Start or restart the cg-SDT-TimeAlignmentTimer associated with the indicated TAG.

[0135] 2> Otherwise: 3> Start or restart the timeAlignmentTimer associated with the indicated TAG.

[0136] 1> When a timing advance command is received in the random access response message for a serving cell belonging to a TAG or in the MSGB for a SpCell: 2> If the MAC entity does not select a random access preamble from the contention-based random access preamble: 3> Apply the timing advance command for this TAG; 3> Start or restart the timeAlignmentTimer associated with this TAG.

[0137] 2> Otherwise, if the timeAlignmentTimer associated with this TAG is not running: 3> Apply the timing advance command for this TAG; 3> Start the timeAlignmentTimer associated with this TAG; 3> When competition resolution is deemed unsuccessful, as described in Clause 5.1.5; or 3> When contention resolution is considered successful for an SI request, as described in Clause 5.1.5, after sending HARQ feedback (including the UE contention resolution identifier MAC CE) for the MAC PDU: 4> Stop the timeAlignmentTimer associated with this TAG.

[0138] 3> When a competition resolution is deemed unsuccessful, as described in Clause 5.1.5: 4> If the triggered CG-SDT procedure (as described in Clause 5.27) is in progress: 5> Set the NTA value to the value before the timing advance command received by the application, as in TS 38.211 [8].

[0139] 3> When the CG-SDT process is in progress, contention resolution is considered successful for the random access procedure: 4> Stop the timeAlignmentTimer associated with this tag; 4> Start or restart the cg-SDT-TimeAlignmentTimer associated with this TAG.

[0140] 3> When contention resolution is considered successful for the random access procedure while an SRS transmission in RRC_INACTIVE is in progress: 4> Start or restart the inactivePosSRS-TimeAlignmentTimer associated with this TAG.

[0141] 2> Otherwise: 3> Ignore received advance timing commands.

[0142] 1> When an absolute timing advance command is received in response to an MSGA transmission including C-RNTI MAC CE (as specified in Clause 5.1.4a): 2> Apply timing advance commands for PTAG; 2> If there is an ongoing location SRS transmission in RRC_INACTIVE (as described in Clause 5.26): 3> Start or restart the inactivePosSRS-TimeAlignmentTimer associated with the indicated TAG.

[0143] 2> If the CG-SDT process is in progress: 3> Start or restart the cg-SDT-TimeAlignmentTimer associated with PTAG.

[0144] 2> Otherwise: 3> Start or restart the timeAlignmentTimer associated with PTAG.

[0145] 1> When an instruction to stop the inactivePosSRS-TimeAlignmentTimer is received from the upper layer: 2> Stop inactivePosSRS-TimeAlignmentTimer.

[0146] 1> When an instruction to start the inactivePosSRS-TimeAlignmentTimer is received from the upper layer: 2> Start or restart inactivePosSRS-TimeAlignmentTimer.

[0147] 1> When the instruction to start cg-SDT-TimeAlignmentTimer has been received from the upper layer: 2> Start cg-SDT-TimeAlignmentTimer.

[0148] 1> When an instruction to stop cg-SDT-TimeAlignmentTimer has been received from the upper layer: 2> It is assumed that cg-SDT-TimeAlignmentTimer has expired.

[0149] 1> When an instruction to start the TimeAlignmentTimer associated with the PTAG has been received from the upper layer: 2> Start the TimeAlignmentTimer associated with PTAG.

[0150] 1> When the timeAlignmentTimer expires: 2> If timeAlignmentTimer is associated with PTAG: 3> Refresh all HARQ buffers for all serving cells; 3> Notify RRC to release PUCCH for all serving cells (if configured); 3> Notify RRC to release SRS for all serving cells (if configured); 3> Clear any configured downlink assignments and configured uplink authorizations; 3> Remove any PUSCH resources used for semi-persistent CSI reporting; 3> Treat all running timeAlignmentTimers as expired; 3> Maintain the NTA for all TAGs (defined in TS 38.211 [8]).

[0151] 2> Otherwise, if the timeAlignmentTimer is associated with a STAG, then for all serving cells belonging to that TAG: 3> Flush all HARQ buffers; 3> Notify RRC to release PUCCH (if configured); 3> Notify RRC to release SRS (if configured); 3> Clear any configured downlink assignments and configured uplink authorizations; 3> Remove any PUSCH resources used for semi-persistent CSI reporting; 3> Maintain the NTA of this TAG (defined in TS 38.211 [8]).

[0152] 1> When the inactivePosSRS-TimeAlignmentTimer expires: 2> Notify RRC to release the positioning SRS used for RRC_INACTIVE configuration.

[0153] 1> When cg-SDT-TimeAlignmentTimer expires: 2> Clear any configured uplink authorizations; 2> If, after the initial transmission of the CCCH message for the CG-SDT, a PDCCH addressing the C-RNTI to the MAC entity has not yet been received: 3> Treat the ongoing CG-SDT process as terminated; 3> Indicate the expiration of cg-SDT-TimeAlignmentTimer to the upper layer.

[0154] 2> Flush all HARQ buffers; 2> Maintain the NTA of this TAG (defined in TS 38.211 [8]).

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

[0156] When the timeAlignmentTimer associated with the TAG to which the serving cell belongs is not running, the CG-SDT process is not in progress, or the SRS transmission of RRC_INACTIVE in Clause 5.26 is not in progress, the MAC entity shall not perform any uplink transmissions on the serving cell other than random access preamble and MSGA transmissions.

[0157] Furthermore, when the timeAlignmentTimer associated with PTAG is not running, the CG-SDT process is not in progress, and the SRS transmission of RRC_INACTIVE in Clause 5.26 is not in progress, the MAC entity shall not perform any uplink transmissions on any serving cell other than random access preamble and MSGA transmissions on SpCell.

[0158] When the cg-SDT-TimeAlignmentTimer is not running during an ongoing CG-SDT procedure triggered as in Clause 5.27, the MAC entity shall not perform any uplink transmissions other than random access preamble and MSGA transmissions. When the inactivePosSRS-TimeAlignmentTimer is not running during an SRS transmission procedure in RRC_INACTIVE as described in Clause 5.26, the MAC entity shall not perform any uplink transmissions other than random access preamble and MSGA transmissions.

[0159] The foregoing content can be used in combination with the methods proposed in this disclosure, which are described below, or can be supplemented to clarify the technical features of the methods proposed in this disclosure. The methods described below are distinguished only for ease of explanation, and it is self-evident that some components of any one method can be replaced by some components of another method, or can be combined with each other.

[0160] According to 3GPP standards up to NR Rel-17, timing advance (TA) settings for UE uplink transmissions by the base station can be executed via higher-layer signaling to compensate for propagation delays between the base station and the UE. Furthermore, TAs for specific cell groups can be set / managed individually through the concept / definition of timing advance groups (TAGs).

[0161] To date, there is no method to support multiple TA values ​​within a specific cell. However, considering the large distance difference between different target TRPs and the UE during M-TRPUL transmission, enhancements will be implemented to enable the setting / indication of multiple (two) TA values ​​within a specific CC / BWP.

[0162] In this context, it is necessary to discuss how the base station configures / indicates multiple TA values ​​to the UE and / or how to implement the connection relationship between multiple TA values ​​and the UE's UL channel / RS. As described in the Rel-18 MIMO WID target (RP-213598) in Table 4 below, consider the configuration of TA values ​​for M-TRP operations based on multiple DCI (M-DCI).

[0163] [Table 4]

[0164] Here, TA (TA value) can be based on Figure 2 The description and the content described in the above-mentioned timing advance (TA) related process.

[0165] In the RAN1 and RAN2 standards prior to Rel-18, base stations were accessed via what was called N. TA and N TA,offset The UETA value is managed using the value of N. The base station can set N as follows: TA The base station can be configured via RAR MAC CE. TA Or ii) Set N via the timed advance command MAC CE (TA MAC CE) TA Furthermore, base stations can utilize the concept of advance timing groups (TAGs) to configure up to four TAGs per UE for a specific cell or cell combination, and can execute N for each TAG. TA Value updates / management.

[0166] As described in WID, the scenario supporting two TA values ​​is based on M-DCI-based M-TRP operations. In M-DCI-based M-TRP operations, each TRP can be classified based on the CORESET pool index associated with the CORESET present in the BWP. Based on the CORESET pool index, each TRP can be classified as i) a TRP performing DL transmission (i.e., PDCCH, PDSCH) or / and ii) a target TRP for UL transmission. For example, CORESET 0 and 1 set to CORESET pool index 0 can correspond to TRP1, while CORESET 2 and 3 set to CORESET pool index 1 can correspond to TRP2.

[0167] In Rel-18 MIMO, an agreement was reached regarding the two TAs, as shown in Table 5 below.

[0168] [Table 5]

[0169] As described above, it was discussed that two TAGs can be configured to manage two TA values ​​in a serving cell, and it was also agreed that the reference timing applied to the TA values ​​managed in each TAG will support two DL reference timings in a serving cell.

[0170] Additionally, the CFRA mechanism for PDCCH ordering is agreed upon for both TA acquisitions. Uplink resources and the connection relationship between the two TAs regarding which uplink transmission the two acquired TAs (TAGs) should be used for are discussed. As a result, it is agreed that the TAG ID will be associated with the UL and / or joint TCI status (via RRC signaling) for association between the two TAGs configured within the serving cell and the UL channel / RS, as in the protocol. In this case, if there is a misalignment between the cell group constituting the TAGs used for two TA operations in a particular CC / BWP and the CC list used for simultaneous multi-CC TCI activation / update, ambiguity may occur in UE operation when simultaneous TCI activation / update is performed in multiple CCs, because the TAG ID updated via TCI activation / update differs from the TAG ID configured for the corresponding CC. For example, suppose CC#1 and CC#2 are configured for TAG ID#1, CC#1 and CC#2 are configured for TAG ID#2, CC#3 and CC#4 are configured for TAG ID#3, and CC#3 and CC#4 are configured for TAG ID#4. In this case, if four CCs from CC#1 to CC#4 are configured in the list of CCs used for simultaneous multi-CC TCI activation / update (especially if the reference CC is CC#1), then TCI activation / update is performed by the TCI state configured in CC#1 (associated with TAG ID#1 or TAG ID#2), but this results in a conflict because CC#3 and CC#4 are associated with TAG ID#3 and TAG ID#4.

[0171] To address these issues, this disclosure proposes a TAG CC grouping method and a method for the base station to configure / manage a list of CCs for the UE that are simultaneously activated / updated by multiple CC TCIs when a specific CC / BWP of the UE supports multiple TAs.

[0172] In this disclosure, depending on the context, " / " can be interpreted as "and", "or", or "and / or".

[0173] Before describing the present invention, the CC grouping method for TAG configuration in existing standards and the simultaneous multi-CC TCI activation / update method in the Rel-17 unified TCI framework are described below.

[0174] Table 6 below shows the CC packetization method used for TAG configuration. For each TAG ID, the base station via... ServingCellConfig Configure the TAG ID of the corresponding cell for the UE.

[0175] [Table 6]

[0176] The following describes in detail the method for simultaneous multi-CC TCI activation / update in the Rel-17 Unified TCI framework.

[0177] In the Rel-17 Unified TCI, the following TCI management operations have been standardized. A beam indication can be performed via the DL licensed / unlicensed DCI for a specific CC / BWP. Specifically, for a beam indication for a pre-configured DL / UL channel / RS, one of up to eight active TCI states can be indicated based on the TCI state field of the DCI.

[0178] In addition, simultaneous multi-CC TCI update operations have also been standardized. The simultaneous multi-CC TCI update operation is as follows: The indicated TCI (i.e., TCI status) applies not only to a specific CC, but also to all CCs included in the CC list configured via RRC signaling.

[0179] For the above-mentioned simultaneous multi-CC TCI update operation, the TCI state can be configured using the following two methods.

[0180] Method i: It can be assumed that a TCI state is configured for each CC in the CC list.

[0181] Method ii: It can be assumed that TCI states (TCI state pools) are configured only for specific CCs / BWPs in the CC list (e.g., reference BWPs of reference CCs).

[0182] In method i, simultaneous multi-CC TCI update operations can be performed as follows.

[0183] The base station sends a TCI state activation / deactivation MAC CE to the UE. Based on the TCI state activation / deactivation MAC CE, the same TCI state ID (up to 8 TCI state IDs) is activated to the code point of the TCI state field in all CCs in the CC list based on the DCI. When the UE receives a DCI that updates the indicated TCI in a specific CC in the CC list, the UE can update the DL and / or UL beams to the indicated TCI (TCI state ID) for all CCs in the CC list.

[0184] In method ii, simultaneous multi-CC TCI update operations can be performed as follows.

[0185] The base station performs TCI state activation for all CCs in the CC list. Specifically, up to 8 (or 16) TCI states are activated in the TCI state ID based on the reference CC (reference BWP). When the UE receives a DCI that updates the indicated TCI in a specific CC in the CC list, the UE can update the DL and / or UL beams to the indicated TCI (TCI state ID) for all CCs in the CC list.

[0186] The following reference Figure 3 The above MAC CE is described in detail.

[0187] Figure 3 An example of TCI status activation / deactivation of MAC CE that can be implemented using embodiments of this disclosure is illustrated. Each field in MAC CE is described in detail below.

[0188] 6.1.3.47 Unified TCI Status Activation / Deactivation MAC CE

[0189] The unified TCI status activation / deactivation MAC CE is identified by a MAC subheader with an eLCID as specified in Table 6.2.1-1b. It has a variable size consisting of the following fields: - Serving Cell ID: This field indicates the identity of the serving cell to which the MAC CE is applied. The field is 5 bits long. If the indicated serving cell is configured as part of the simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3 or simultaneousU-TCI-UpdateList4 specified in TS 38.331[5], then the MAC CE is applied to all serving cells in the simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3 or simultaneousU-TCI-UpdateList4 respectively; - DL BWP ID: This field indicates the DL BWP of the code point for the DCI bandwidth portion indicator field as specified in TS 38.212[9] for which the MAC CE application is applied. The BWP ID field is 2 bits long; - UL BWP ID: This field indicates the UL BWP of the code point for the DCI bandwidth portion indicator field as specified in TS 38.212[9] for which the MAC CE application is performed. If the value of the unifiedTCI-StateType in the serving cell indicated by the serving cell ID is unified, this field is treated as a reserved bit. The BWP ID field is 2 bits long; - P i This field indicates whether each TCI code point has multiple TCI states or a single TCI state. If P i If the field is set to 1, it indicates that the i-th TCI code point includes both DL TCI and UL TCI states. If P i When a field is set to 0, it indicates that the i-th TCI code point includes only DL / joint TCI states or UL TCI states. The code point mapped to a TCI state is determined by its sequential position in all TCI state ID fields; - D / U: This field indicates whether the TCI status ID in the same octet is used for the joint / downlink or uplink TCI status. If this field is set to 1, the TCI status ID in the same octet is used for the joint / downlink. If this field is set to 0, the TCI status ID in the same octet is used for the uplink. - TCI State ID: This field indicates the TCI state identified by TCI-StateId as specified in TS 38.331[5]. If D / U is set to 1, the 7-bit TCI state ID specified in TS 38.331[5], i.e., TCI-StateId, is used. If D / U is set to 0, the most significant bit of the TCI state ID is treated as a reserved bit, and the remaining 6 bits indicate TCI-UL-State-Id as specified in TS 38.331[5]. The maximum number of active TCI states is 16; - R: Reserved bit, set to 0.

[0190] Table 7 below illustrates the method for indicating the TCI status in the Rel-17 Unified TCI.

[0191] [Table 7]

[0192] Question 1

[0193] Simultaneously, the method ii for multi-CC TCI update operations may have the following problems.

[0194] When a TAG-id (via RRC signaling) is configured in the joint TCI state and / or ULTCI state for two TA operations of the UE, the non-reference CC and reference CC in the CC list used for simultaneous TCI updates can belong to different TAGs. Since the TCI state configured for the reference CC (within the TCI state pool) is utilized in the non-reference CC, the TAG-id associated with / related to the reference CC can also be used as the TAG-id. In this case, ambiguity may occur in UE operations because the TAG-id configured for the non-reference CC and the TAG-id configured for the reference CC are different.

[0195] For example, suppose TAG-id#1 and TAG-id#2 are configured for CC#1 (which is the reference CC), and TAG-id#3 and TAG-id#4 are configured for CC#2 (which is the non-reference CC). Additionally, suppose CC#1 and CC#2 are configured in the CC list for simultaneous multi-CC TCI update operations. TCI activation / update is performed based on the TCI state configured for CC#1 (related to TAG-id#1 and / or TAG-id#2). Uplink transmissions based on CC#2 are performed based on the TCI state (related to TAG-id#1 and / or TAG-id#2), while CC#2 is related to TAG-id#3 and TAG-id#4, creating a contradiction.

[0196] Suggestion 1

[0197] To address issue 1, the UE can expect the cell group configuration used for TAG configuration (for two TA operations) to include a list of CCs for simultaneous multi-CC TCI updates.

[0198] For example, a UE can expect that the CCs in the cell group used for TAG configuration (for dual TA operation) and the CCs in the CC list used for simultaneous multiple CCTCI updates are the same.

[0199] For example, a UE can expect that the combination of CCs in the CC list configured for the UE is part of the combination of CCs within the cell group used for TAG configuration.

[0200] For example, a UE may not expect the combination of TAG-IDs configured for non-reference CCs and reference CCs in the CC list used for simultaneous multi-CC TCI updates to be different. This configuration can be implemented by the base station.

[0201] According to Proposal 1, the configuration of the cell group used for TAG configuration is dependent on the configuration of the CC list used for simultaneous multi-CC TCI updates. Specifically, the non-reference CCs in the CC list for simultaneous multi-CC TCI updates unconditionally configured to the UE belong to the same TAG as the reference CC. Therefore, the following effect can be achieved: There is no ambiguity when the non-reference CC uses a TAG-ID related to the TCI state of the reference CC.

[0202] For example, this implementation can be applied only to method ii, which involves simultaneous multi-CC TCI update operations. For example, this implementation can be applied to both method i and method ii.

[0203] Suggestion 2

[0204] The following describes in detail the method for resolving ambiguity, where the TAG-ID configured in the UE-specific serving cell and the TAG-ID configured in the TCI state used for uplink transmission are different.

[0205] Proposal 2-1

[0206] If we assume that method i is used for simultaneous multi-CC TCI update operations, the following implementation can be considered.

[0207] In existing UE operation, when performing simultaneous multi-CC TCI updates, the TCI state ID configured in the TCI state pool for each CC / BWP is utilized. Therefore, the UE can perform uplink transmissions by utilizing the TAG-id configured in the combined TCI state and / or UL TCI state (via RRC signaling) of each CC / BWP.

[0208] For example, suppose the TAG-id is configured as follows.

[0209] TAG-id#1: CC#1, CC#2

[0210] TAG-id#2: CC#1, CC#2

[0211] TAG-id#3: CC#3, CC#4

[0212] TAG-id#4: CC#3, CC#4

[0213] Four CCs, including CC#1 through CC#4, can be configured in the CC list for simultaneous multi-CC TCI updates. (Since the TCI state configured for each CC / BWP is used for the operation in each CC / BWP,) there is no ambiguity even if TCI updates are performed simultaneously for all CCs in the CC list. Specifically, in CC#1 and CC#2, uplink transmissions are performed using the TCI states associated with / related to TAG-id#1 and / or TAG-id#2. In CC#3 and CC#4, uplink transmissions are performed using the TCI states associated with / related to TAG-id#3 and / or TAG-id#4.

[0214] Suggestion 2-2

[0215] If we assume that method ii is used for simultaneous multi-CC TCI update operations, the following implementation can be considered.

[0216] If the TAG-id configured in the reference CC and the non-reference CC differs from that in Problem 1 above, a problem arises where the TAG-id configured in the non-reference CC differs from the TAG-id (associated with TCI state) to be used for uplink transmission in the non-reference CC. To resolve this problem, the UE can operate based on either method 1) or method b).

[0217] Method a) (even if the TAG-ids configured in the reference CC and the non-reference CC are different), the UE performs uplink transmission by utilizing the TAG-id configured in the non-reference CC / associated with the TCI state of the reference CC. In other words, the TAG-id configured in the non-reference CC can be ignored, or the TAG-id configured in the non-reference CC can be overridden by the TAG-id configured in the reference CC.

[0218] Method b) The UE can operate by ignoring or overriding the TAG-id configured in the TCI state of the reference CC for uplink transmission in a non-reference CC. For example, depending on whether the TAG-id configured in the indicated TCI updated by the DCI is the first TAG in the reference CC (e.g., tag-Id in the RRC configuration, TAG-id with the lowest ID, etc.) or the second TAG (e.g., tag-Id2 in the RRC configuration, TAG-id with the highest ID, etc.), the UE can perform uplink transmission by utilizing the first TAG and / or the second TAG configured in the non-reference CC. In other words, based on the TAG-id configured in the TCI state of the reference CC being a first value (e.g., a value n0 indicating the first TAG), the UE can perform uplink transmission by utilizing the first TAG configured in the non-reference CC (indicated by the first TAG ID). Based on the fact that the TAG-id configured in the TCI state of the reference CC is the second value (e.g., indicating the value n1 of the second TAG), the UE can perform uplink transmissions by utilizing the second TAG configured in the non-reference CC (indicated by the second TAG ID).

[0219] For example, suppose the TAG-id is configured as follows.

[0220] TAG-id#1: CC#1 (refer to CC), CC#2

[0221] TAG-id#2: CC#1 (refer to CC), CC#2

[0222] TAG-id#3: CC#3, CC#4

[0223] TAG-id#4: CC#3, CC#4

[0224] Suppose that the CC list for simultaneous multi-CC TCI updates is configured with four CCs, CC#1 through CC#4, and the reference CC is CC#1. When a TCI update is performed simultaneously for all CCs in the CC list, the TCI state configured and indicated in CC#1 is used for uplink transmissions in all CCs (CC#1 through CC#4) in the CC list.

[0225] For CC#1 and CC#2, the aforementioned ambiguity does not occur because uplink transmission is performed based on the TCI state associated with (CC#1) TAG-id#1 and / or TAG-id#2.

[0226] In CC#3 and CC#4, the TCI state of CC#1 is used for uplink transmission in method b) of proposal 2-2. In this example, uplink transmission is performed based on TAG-id#3 and / or TAG-id#4 (not TAG-id#1 and / or TAG-id#2 configured in CC#1). For example, if the information associated with the TAG ID configured in the TCI state of CC#1 is a first value (e.g., representing the value of TAG-id#1), uplink transmission can be performed based on the first TAG indicated by the first TAG ID (TAG-id#3) configured in CC#3 / CC#4. For example, if the information associated with the TAG ID configured in the TCI state of CC#1 is a second value (e.g., representing the value of TAG-id#2), uplink transmission can be performed based on the second TAG indicated by the second ID (TAG-id#4) configured in CC#3 / CC#4. Therefore, the aforementioned ambiguity does not occur.

[0227] The implementation method can be based on a combination of specific implementation methods.

[0228] Examples of UE (base station) operation based on at least one of the above embodiments (e.g., at least one of Proposal 1 and Proposal 2) are as follows.

[0229] 1) The UE (base station) receives (transmits) configurations related to two TAGs (two TAs) within a specific serving cell.

[0230] This configuration can include the relationship between TAG IDs and UL resources.

[0231] This configuration may include the configuration of cell groups associated with the two TAGs and the CC list configuration associated with simultaneous multi-CC TCI activation / update based on Proposal 1 and Proposal 2.

[0232] Before / after configuration, two TA fetches (CFRA sorted using PDCCH) can be performed for each TAG.

[0233] 2) The UE (base station) receives (sends) messages that schedule uplink transmissions related to the two TAGs.

[0234] This message can be based on an RRC message, MAC CE, or DCI.

[0235] 3) The UE (base station) sends (receives) uplink signals based on this message.

[0236] Uplink signal transmission can be performed based on Proposal 1 and Proposal 2.

[0237] The UE / base station operations are merely examples, and each operation (or step) is not necessarily necessary. The TCI update operations related to the two TA operations of the UE according to the above implementation method may be omitted or added, depending on the UE / base station implementation method.

[0238] From an implementation perspective, the operation of the UE / base station according to the above embodiments (e.g., operation based on at least one of Proposal 1 and Proposal 2) can be described below. Figure 6 Devices (e.g., Figure 6 Processors 110 and 210 are used to process it.

[0239] Furthermore, the operation of the UE / base station according to the above embodiments (e.g., based on the operation of at least one of Proposal 1 and Proposal 2) can be used to run at least one processor (e.g., Figure 6 The commands / programs (e.g., instructions, executable code) of the processors 110 and 210 are stored in memory (e.g., Figure 6 In the memory (140 and 240).

[0240] Below, refer to Figure 4 and Figure 5 The above implementation methods are described in detail from the perspective of UE / base station operation. The methods described below are distinguished only for ease of explanation. Therefore, it is obvious that a portion of the configuration of any method can replace a portion of the configuration of another method or be combined with a portion of the configuration of another method.

[0241] Figure 4 This is a flowchart illustrating a method performed by a user equipment according to an embodiment of the present disclosure.

[0242] Reference Figure 4 The method performed by a user equipment according to an embodiment of the present disclosure includes: step S410 of receiving cell group configuration; step S420 of receiving configuration information related to a first serving cell; and step S430 of sending an uplink signal related to the first serving cell.

[0243] In step S410, the UE receives the cell group configuration from the base station. The cell group configuration includes a list of serving cells updated simultaneously with the application of the Uniform Transport Configuration Indicator (TCI) status.

[0244] For example, cell group configuration can be based on high-rise parameters. CellGroupConfigFor example, a list can refer to a list of CCs used to simultaneously update the unified TCI state. Specifically, the list can be based on the higher-level parameters simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, or simultaneousU-TCI-UpdateList4.

[0245] In step S420, the UE receives configuration information related to the first serving cell in the serving cells from the base station. Based on the configuration information, it configures the first timing advance group (TAG) ID and the second TAG ID.

[0246] For example, configuration information can be based on high-level parameters. ServingCellConfig (See Table 6). The first TAG ID can be tag-id, and the second TAG ID can be tag2-id.

[0247] In step S430, the UE sends an uplink signal related to the first serving cell to the base station based on the unified TCI state associated with the second serving cell in the serving cell.

[0248] For example, uplink signals can be signals scheduled / triggered based on downlink control information (DCI). For example, uplink signals can be the Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Sound Reference Signal (SRS), or Physical Random Access Channel (PRACH).

[0249] For example, a unified TCI state can be: i) a first TCI state associated with a first control resource set (CORESET) (e.g., a first joint TCI state or a first UL TCI state), or ii) a second TCI state associated with a second CORESET (e.g., a second joint TCI state or a second UL TCI state). The first CORESET can be based on a first CORESET pool index. The second CORESET can be based on a second CORESET pool index.

[0250] For example, spatial domain filters can be determined based on the unified TCI state. Specifically, uplink signals can be transmitted based on spatial domain filters associated with the unified TCI state.

[0251] According to the implementation, uplink timing associated with the uplink signal can be determined based on a TAG associated with the unified TCI state. The TAG can be associated with a first TAG ID or a second TAG ID of the first serving cell applying the unified TCI state. This implementation can be based on method b) of proposal 2-2.

[0252] A serving cell can correspond to a component carrier (CC). In other words, a list of CCs can be used to interpret / replace a list of serving cells.

[0253] The second serving cell can be based on a reference CC in the CC of the corresponding serving cell. For example, the second serving cell can be a serving cell configured / defined with a unified TCI state configuration (e.g., dl-OrJointTCI-StateToAddModList or ul-TCI-ToAddModList) within a serving cell configured with a unifiedTCI-StateType (e.g., federated or individual).

[0254] The first serving cell can be based on a first CC that is different from the reference CC in the CC of the corresponding serving cell. For example, the first serving cell can be a serving cell configured with higher-level parameters (e.g., UnifiedTCI-StateRef) that represent a second serving cell among serving cells configured with unifiedTCI-StateType (e.g., federated or individual). UnifiedTCI-StateRef represents a serving cell (e.g., the second serving cell / reference CC) configured / defined with unified TCI state configuration (e.g., dl-OrJointTCI-StateToAddModList or ul-TCI-ToAddModList) and bandwidth portion (BWP) (e.g., the BWP / reference BWP of the second serving cell).

[0255] In the bandwidth portion (BWP) of the first CC, a unified TCI state configuration may not exist. In this case, a unified TCI state can be configured / defined for the reference CC. Specifically, the unified TCI state can be associated with the reference bandwidth portion (BWP) of the reference CC.

[0256] According to the implementation, the unified TCI state may include TAG ID information (e.g., tag-id-ptr). Based on the TAG ID information being set to a first value (e.g., n0), the TAG may be a first TAG indicated by a first TAG ID of the first serving cell. Based on the TAG ID information being set to a second value (e.g., n1), the TAG may be a second TAG indicated by a second TAG ID of the first serving cell.

[0257] For example, the first TAG may be the same as or different from the TAG indicated by the first TAG ID configured for the second serving cell. The second TAG may be the same as or different from the TAG indicated by the second TAG ID configured for the second serving cell. This is described in detail below.

[0258] For example, the two tags configured for the second serving cell could be i) TAG#1 and ii) TAG#2, and the two tags configured for the first serving cell could be i) TAG#3 and ii) TAG#4. In this case, the tags (TAG#1 and TAG#2) indicated by the first and second TAG IDs of the second serving cell can be different from the tags (TAG#3 and TAG#4) indicated by the first and second TAG IDs of the first serving cell. That is, the two tags configured for each of the first and second serving cells as described above can be different from each other.

[0259] For example, the two tags configured for the second serving cell can be i) TAG#1 and ii) TAG#2, and the two tags configured for the first serving cell can be i) TAG#1 and ii) TAG#4. In this case, the TAG (TAG#1) indicated by the first TAG ID of the second serving cell is the same as the TAG (TAG#1) indicated by the first TAG ID of the first serving cell. The TAG (TAG#2) indicated by the second TAG ID of the second serving cell is different from the TAG (TAG#4) indicated by the second TAG ID of the first serving cell. That is, as described above, the first TAG in the two tags configured for each of the first and second serving cells can be the same, and the second TAG can be different.

[0260] For example, the two tags configured for the second serving cell could be i) TAG#2 and ii) TAG#3, and the two tags configured for the first serving cell could be i) TAG#1 and ii) TAG#3. In this case, the tag (TAG#2) indicated by the first TAG ID of the second serving cell is different from the tag (TAG#1) indicated by the first TAG ID of the first serving cell. The tag (TAG#3) indicated by the second TAG ID of the second serving cell is the same as the tag (TAG#3) indicated by the second TAG ID of the first serving cell. That is, as described above, the first tag in the two tags configured for each of the first and second serving cells can be different, and the second tag can be the same.

[0261] According to the implementation, the unified TCI state can be a combined TCI state or a separate TCI state. For example, the parameter `unifiedTCI-StateType` can be set to combined. The unified TCI state can be a combined TCI state for UL and DL operations. For example, the parameter `unifiedTCI-StateType` can be set to separate. The unified TCI state can be a UL TCI state for UL operations.

[0262] The method may also include receiving a MAC CE. Specifically, the UE receives a Medium Access Control-Control Element (MAC CE) from the base station. The MAC CE may be related to the activation and / or deactivation of the Unified TCI state. That is, the MAC CE may be based on... Figure 3 The MAC CE. Since the serving cell indicated by the MAC CE is part of the serving cell, the MAC CE can be applied to the serving cell.

[0263] The unified TCI state can be the unified TCI state indicated by downlink control information (DCI) in the unified TCI state activated based on MAC CE.

[0264] The operation based on the above steps S410 to S430 and the MAC CE receiving step can be performed by... Figure 6 The device implementation. For example, UE 200 may control one or more transceivers 230 and / or one or more memories 240 to perform operations based on steps S410 to S430 and the MAC CE receiving step.

[0265] The above implementation method will now be described in detail from the perspective of base station operation.

[0266] The steps S510 to S530 and the MAC CE sending steps described below correspond to the reference. Figure 4 Steps S410 to S430 and the MAC CE receiving steps are described. Redundant descriptions have been omitted to account for the above correspondence. That is, the detailed description of the base station operation described below can be replaced with the corresponding base station operation... Figure 4 Description / implementation method.

[0267] For example, Figure 4 The description / implementation of steps S410 to S430 can also be applied to the base station operation of steps S510 to S530 described below.

[0268] For example, the description / implementation of the MAC CE receiving step can also be applied to the base station operation of the MAC CE transmitting step described below.

[0269] Figure 5This is a flowchart illustrating a method performed by a base station according to another embodiment of the present disclosure.

[0270] Reference Figure 5 According to another embodiment of the present disclosure, the method performed by the base station includes: step S510 of sending cell group configuration, step S520 of sending configuration information related to the first serving cell, and step S530 of receiving uplink signals related to the first serving cell.

[0271] In step S510, the base station sends cell group configuration to the UE. The cell group configuration includes a list of serving cells updated simultaneously with the application of the Uniform Transport Configuration Indicator (TCI) state.

[0272] In step S520, the base station sends configuration information related to the first serving cell in the serving cells to the UE. Based on the configuration information, a first timing advance group (TAG) ID and a second TAG ID are configured.

[0273] In step S530, the base station receives uplink signals related to the first serving cell from the UE based on the unified TCI state related to the second serving cell in the serving cell.

[0274] According to the implementation method, uplink timing associated with uplink signals can be determined based on a TAG associated with the unified TCI state. The TAG can be associated with a first TAG ID or a second TAG ID of the first serving cell applying the unified TCI state.

[0275] The method may also include sending a MAC CE. Specifically, the base station sends a Media Access Control-Control Element (MAC CE) to the UE.

[0276] The operation based on the above steps S510 to S530 and the MAC CE sending step can be performed by... Figure 6 The device is implemented in this way. For example, base station 100 may control one or more transceivers 130 and / or one or more memories 140 to perform operations based on steps S510 to S530 and MAC CE transmission steps.

[0277] The following reference Figure 6 Describes the apparatus to which embodiments of this disclosure are applicable (apparatus for implementing the methods / operations according to embodiments of this disclosure).

[0278] Figure 6 The configurations of the first and second devices according to embodiments of the present disclosure are illustrated.

[0279] The first device 100 may include a processor 110, an antenna unit 120, a transceiver 130, and a memory 140.

[0280] Processor 110 can perform baseband-related signal processing and includes a higher-layer processing unit 111 and a physical layer processing unit 115. Higher-layer processing unit 111 can handle operations at the MAC layer, RRC layer, or higher layers. Physical layer processing unit 115 can handle PHY layer operations. For example, if the first device 100 is a base station (BS) device in BS-UE communication, physical layer processing unit 115 can perform uplink receive signal processing, downlink transmit signal processing, etc. For example, if the first device 100 is a first UE device in UE-to-UE communication, physical layer processing unit 115 can perform downlink receive signal processing, uplink transmit signal processing, sidelink transmit signal processing, etc. In addition to performing baseband-related signal processing, processor 110 can also control the overall operation of the first device 100.

[0281] Antenna unit 120 may include one or more physical antennas, and if antenna unit 120 includes multiple antennas, MIMO transmission / reception is supported. Transceiver 130 may include a radio frequency (RF) transmitter and an RF receiver. Memory 140 may store information processed by processor 110, as well as software, operating system, and applications related to the operation of first device 100. Memory 140 may also include components such as buffers.

[0282] In the embodiments described in this disclosure, the processor 110 of the first device 100 may be configured to implement the operation of the BS in BS-UE communication (or the operation of the first UE device in UE-UE communication).

[0283] The second device 200 may include a processor 210, an antenna unit 220, a transceiver 230, and a memory 240.

[0284] Processor 210 can perform baseband-related signal processing and includes a higher-layer processing unit 211 and a physical layer processing unit 215. Higher-layer processing unit 211 can handle operations at the MAC layer, RRC layer, or higher layers. Physical layer processing unit 215 can handle PHY layer operations. For example, if the second device 200 is a UE device in BS-UE communication, physical layer processing unit 215 can perform downlink receive signal processing, uplink transmit signal processing, etc. For example, if the second device 200 is a second UE device in inter-UE communication, physical layer processing unit 215 can perform downlink receive signal processing, uplink transmit signal processing, sidelink receive signal processing, etc. In addition to performing baseband-related signal processing, processor 210 can also control the overall operation of the second device 200.

[0285] Antenna unit 220 may include one or more physical antennas, and if antenna unit 220 includes multiple antennas, MIMO transmission / reception is supported. Transceiver 230 may include an RF transmitter and an RF receiver. Memory 240 may store information processed by processor 210, as well as software, operating system, and applications related to the operation of second device 200. Memory 240 may also include components such as buffers.

[0286] In the embodiments described in this disclosure, the processor 210 of the second device 200 may be configured to implement the operation of the UE in BS-UE communication (or the operation of the second UE device in inter-UE communication).

[0287] The descriptions of the BS and UE (or the first UE device and the second UE device in inter-UE communication) in the examples of this disclosure are equivalent to those for the operation of the first device 100 and the second device 200, and redundant descriptions are omitted.

[0288] In addition to LTE, NR, and 6G, the wireless communication technologies implemented in apparatus 100 and apparatus 200 according to this disclosure may also include narrowband Internet of Things (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of low-power wide-area network (LPWAN) technology and may be implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2. NB-IoT technology is not limited to the names mentioned above.

[0289] Additionally or alternatively, the wireless communication technology implemented in apparatus 100 and apparatus 200 according to this disclosure may be based on LTE-M technology to perform communication. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names, such as enhanced machine-type communication (eMTC). For example, LTE-M technology may be implemented using at least one of various standards, such as 1) LTE Cat0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE machine-type communication, and / or 7) LTE M. LTE-M technology is not limited to the names mentioned above.

[0290] Additionally or alternatively, considering low-power communication, the wireless communication technologies implemented in apparatus 100 and apparatus 200 according to this disclosure may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN), and are not limited to the aforementioned names. For example, ZigBee technology can be based on various standards such as IEEE 802.15.4 to create personal area networks (PANs) associated with small / low-power digital communication, and may be referred to by various names.

Claims

1. A method performed by a user equipment (UE), the method comprising the following steps: Receive cell group configuration, wherein the cell group configuration includes a list of serving cells that are updated simultaneously with the application of the Uniform Transport Configuration Indicator (TCI) status; Receive configuration information related to a first serving cell in the serving cells, wherein a first timing advance group TAG ID and a second TAG ID are configured based on the configuration information; and Based on the unified TCI state associated with the second serving cell in the serving cells, an uplink signal associated with the first serving cell is transmitted. The uplink timing associated with the uplink signal is determined based on a TAG associated with the unified TCI state. The TAG is associated with the first TAG ID or the second TAG ID of the first serving cell that applies the unified TCI state.

2. The method according to claim 1, wherein, The serving cell corresponds to the component carrier CC.

3. The method according to claim 1, wherein, The second serving cell is based on a reference CC in the CC corresponding to the serving cell.

4. The method according to claim 1, wherein, The first serving cell is based on a first CC that is different from the reference CC in the CC corresponding to the serving cell.

5. The method according to claim 4, wherein, The bandwidth portion of the first CC, BWP, does not have a unified TCI state configuration.

6. The method according to claim 5, wherein, The unified TCI state is related to the reference BWP of the reference CC.

7. The method according to claim 1, wherein, The unified TCI status includes TAG ID information. Wherein, the TAG ID information is set to a first value, and the TAG is the first TAG indicated by the first TAG ID of the first serving cell, and Wherein, the TAG ID information is set to a second value, and the TAG is a second TAG indicated by the second TAG ID of the first serving cell.

8. The method according to claim 7, wherein, The first TAG may be the same as or different from the TAG indicated by the first TAG ID configured for the second serving cell.

9. The method according to claim 7, wherein, The second TAG may be the same as or different from the TAG indicated by the second TAG ID configured for the second serving cell.

10. The method according to claim 1, wherein, The unified TCI state can be either a combined TCI state or a single TCI state.

11. The method according to claim 1, further comprising the following step: Receive Media Access Control - Control Element MAC CE Wherein, the MAC CE is related to the activation and / or deactivation of the unified TCI state, and Wherein, the MAC CE is applied to the serving cell based on the serving cell indicated by the MAC CE, since the serving cell is part of the serving cell.

12. The method according to claim 11, wherein, The unified TCI state is the unified TCI state indicated by the downlink control information (DCI) within the unified TCI state activated by the MAC CE.

13. A user equipment (UE), the UE comprising: One or more transceivers; One or more processors; as well as One or more memories, said one or more memories being connected to said one or more processors and storing instructions. The instructions are based on the one or more processors being executed to configure the one or more processors to perform all the steps of the method according to any one of claims 1 to 12.

14. An apparatus comprising: One or more memory units; as well as One or more processors, said one or more processors being operatively connected to said one or more memories, The one or more memory storage instructions are based on the one or more processors executing to configure the one or more processors to perform all the steps of the method according to any one of claims 1 to 12.

15. One or more non-transitory computer-readable media, said one or more non-transitory computer-readable media storing instructions, in, The instructions, which can be executed by one or more processors, configure one or more processors to perform all the steps of the method according to any one of claims 1 to 12.

16. A method performed by a base station, the method comprising the following steps: Send cell group configuration, wherein the cell group configuration includes a list of serving cells that are updated simultaneously with the application of the Uniform Transport Configuration Indicator (TCI) status; Send configuration information related to the first serving cell in the serving cells, wherein a first timing advance group TAG ID and a second TAG ID are configured based on the configuration information; and Based on the unified TCI state associated with the second serving cell in the serving cells, the uplink signal associated with the first serving cell is received. The uplink timing associated with the uplink signal is determined based on a TAG associated with the unified TCI state. The TAG is associated with the first TAG ID or the second TAG ID of the first serving cell that applies the unified TCI state.

17. A base station, the base station comprising: One or more transceivers; One or more processors; as well as One or more memories, connected to the one or more processors and storing instructions. The instructions are based on the one or more processors executing to configure the base station to perform all the steps of the method according to claim 16.

Images