Method for uplink transmission and reception, and device therefor
The method addresses ambiguity in uplink timing advance by using SRS and PUCCH resources to determine TRP-specific timing, improving communication reliability and compatibility in mobile communication systems.
Patent Information
- Application Number
- PCT/KR2024/006417
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-12
- Filing Date
- 2024-05-10
- Publication Date
- 2024-11-21
AI Technical Summary
In mobile communication systems, the ambiguity in uplink timing advance settings for multiple transmission and reception points (TRPs) leads to challenges in coordinating timing differences, especially in non-ideal backhaul operations without unified TCI framework support, affecting the reliability of M-TRP-based communication.
A method is proposed where the terminal determines uplink timing based on SRS resources, PUCCH resources, or TAG settings related to PUSCH, using configuration information and DCI, allowing for TRP-specific timing advance settings even without unified TCI, thereby resolving ambiguity and improving communication reliability.
This approach enhances the reliability of M-TRP-based communication by ensuring appropriate uplink timing for each TRP, minimizing implementation complexity, and maintaining backward compatibility with existing systems.
Smart Images

Figure KR2024006417_21112024_PF_FP_ABST
Abstract
Description
Method and device for uplink transmission and reception
[0001] This specification relates to a method and device for uplink transmission and reception.
[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, they have expanded beyond voice to include data services. Currently, explosive growth in traffic is leading to resource shortages and users are demanding faster services, necessitating a more advanced mobile communication system.
[0003] Next-generation mobile communication systems must support explosive data traffic growth, dramatically increasing data rates per user, a vastly increased number of connected devices, ultra-low end-to-end latency, and high energy efficiency. To achieve these goals, various technologies are being studied, including dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking.
[0004] In the existing LTE and NR standards, when setting / instructing uplink timing advance, a single TA value is supported for the Timing Advance Group (TAG) to which a specific cell or group of cells belongs.
[0005] Meanwhile, M-DCI-based Multiple-Transmission and Reception point (M-TRP) operations can be performed in environments where the distance between the UE and different TRPs is large. In such cases, propagation delay differences, slot boundary differences, and inter-UE panel delay differences may occur between target TRPs for uplink transmission within the CC / BWP. This phenomenon can be particularly significant in non-ideal backhaul operations where coordination between TRPs is not achieved.
[0006] To compensate for the timing differences or delays that occur between TRPs as described above, the uplink timing needs to be determined differently for each TRP. To this end, an operation has been agreed upon to associate / correspond TAGs with the TCI states of the unified TCI (e.g., joint TCI state, separate 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 single serving cell.
[0007] However, in environments where a unified TCI framework, such as Rel-15 / 16, is not utilized, it is unclear how TAGs should be linked / indicated for uplink transmission. For example, if two TAGs are managed in a specific CC / BWP based on Rel-15 / 16, it may be unclear how the TAG for uplink transmission should be determined.
[0008] As described above, when two TAGs are managed in a specific CC / BWP that does not utilize the unified TCI framework, the problem of TAG ambiguity for uplink transmission arises. The purpose of this specification is to propose a method to resolve the aforementioned problem.
[0009] The technical problems to be achieved in this specification are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present invention belongs from the description below.
[0010] A method performed by a terminal according to one embodiment of the present disclosure includes the steps of receiving configuration information related to a serving cell, receiving downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH), and transmitting the PUSCH based on uplink timing related to one of a first TAG and a second TAG. The configuration information includes an ID of the first TAG and an ID of the second TAG. The TAG related to the uplink timing is characterized in that it is determined based on a sounding reference signal (SRS) resource.
[0011] The TAG associated with the uplink timing may be determined based on i) the SRS resource, ii) a physical uplink control channel (PUCCH) resource, iii) an SRS resource indicator field of the DCI, or iv) a TAG setting associated with the PUSCH.
[0012] The TAG associated with the above uplink timing may be associated with spatial relation information for the SRS resource.
[0013] The above SRS resource may be i) an SRS resource based on the above SRS resource indicator field or ii) an SRS resource associated with a configured grant.
[0014] The TAG related to the above uplink timing can be determined based on the ID of the TAG mapped to the codepoint of the SRS resource indicator field.
[0015] The TAG associated with the uplink timing may be associated with spatial relation information for the PUCCH resource.
[0016] The above DCI may be based on DCI format 0_0. The above PUCCH resource may have the lowest ID within the active UL BandWidth Part (BWP).
[0017] The above DCI may be based on DCI format 0_0. Based on the TAG configuration, the ID of the TAG for the PUSCH scheduled based on the DCI format 0_0 may be indicated.
[0018] The above PUSCH can be transmitted based on spatial relationship information for the SRS resource or PUCCH resource.
[0019] The unified TCI state may not be set in the serving cell.
[0020] A terminal according to another embodiment of the present disclosure includes one or more transceivers, one or more processors, and one or more memories connected to the one or more processors and storing instructions.
[0021] The instructions are characterized in that, based on being executed by the one or more processors, the one or more processors are set to perform all steps of any one of the methods.
[0022] A device according to another embodiment of the present disclosure comprises one or more memories and one or more processors functionally connected to the one or more memories.
[0023] Said one or more memories are characterized in that they store instructions that cause said one or more processors to perform all steps of any one of said methods based on what is executed by said one or more processors.
[0024] In another embodiment of the present disclosure, one or more non-transitory computer-readable media store instructions, the instructions being executable by one or more processors, characterized in that they cause the one or more processors to perform all steps of any one of the methods.
[0025] A method performed by a base station includes the steps of transmitting configuration information related to a serving cell, transmitting downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH), and receiving the PUSCH based on uplink timing related to one of a first TAG and a second TAG. The configuration information includes an ID of the first TAG and an ID of the second TAG. The TAG related to the uplink timing is characterized in that it is determined based on a sounding reference signal (SRS) resource.
[0026] 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 coupled to the one or more processors and storing instructions.
[0027] The instructions are characterized in that they are executed by the one or more processors, and the one or more processors are set to perform all steps of the method.
[0028] According to an embodiment of the present specification, a TAG related to uplink timing is determined based on i) a Sounding Reference Signal (SRS) resource or a Physical Uplink Control Channel (PUCCH) resource, ii) an SRS resource indicator field of the DCI, or iii) a TAG setting related to scheduling of the PUSCH. Accordingly, ambiguity related to uplink timing determination can be resolved, and the reliability of M-TRP-based communication can be improved.
[0029] In addition, since the TAG is determined based on existing information utilized for uplink transmission, the terminal / base station implementation complexity required to support uplink transmission and reception based on two TAGs can be minimized.
[0030] Furthermore, even for CC / BWPs or terminals that do not support unified TCI state, uplink transmission can be performed based on a more appropriate timing for one of the multiple TRPs. Therefore, backward compatibility of uplink transmission and reception operations based on two TAGs can be improved.
[0031] The effects that can be obtained from this specification are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by those skilled in the art to which the present invention pertains from the description below.
[0032] Figure 1 illustrates a MAC RAR according to an embodiment of the present specification.
[0033] FIG. 2 illustrates a Timing Advance Command MAC CE according to an embodiment of the present specification.
[0034] FIG. 3 is a flowchart illustrating a method performed by a terminal according to one embodiment of the present specification.
[0035] FIG. 4 is a flowchart illustrating a method performed by a base station according to another embodiment of the present specification.
[0036] FIG. 5 is a drawing showing the configuration of a first device and a second device according to an embodiment of the present specification.
[0037] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to illustrate exemplary embodiments of the present invention and is not intended to represent the only embodiments in which the present invention may be practiced. The following detailed description includes specific details to provide a thorough understanding of the present invention. However, one of ordinary skill in the art will appreciate that the present invention may be practiced without these specific details.
[0038] In some cases, to avoid obscuring the concept of the present invention, well-known structures and devices may be omitted or illustrated in block diagram form focusing on the core functions of each structure and device.
[0039] Hereinafter, 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 downlink, a transmitter may be part of a base station, and a receiver may be part of a terminal. In uplink, a transmitter may be part of a terminal, and a receiver may be part of a base station. A base station may be expressed as a first communication device, and a terminal may be expressed as a second communication device. A base station (BS) may be replaced by terms such as a fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP: Access Point), network (5G network), AI system, RSU (road side unit), vehicle, robot, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, the terminal may be fixed or mobile, and may be replaced with terms such as UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), MTC (Machine-Type Communication) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, robot, AI module, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.
[0040] <Multi-TRP(Transmission / Reception Point) 관련 동작>
[0041] The M-TRP transmission method, in which M TRPs transmit data to one terminal (User equipment, UE), can be broadly divided into two types: eMBB M-TRP transmission, which is a method for increasing the transmission rate, and URLLC M-TRP transmission, which is a method for increasing the reception success rate and reducing latency.
[0042] UL MTRP-URLLC means that multiple TRPs receive the same data / UCI from a UE using different layer / time / frequency resources. For example, TRP 1 receives the same data / UCI from the UE on resource 1, and TRP 2 receives the same data / UCI from the UE on resource 2. Then, the received data / UCI is shared through the backhaul link connected between the TRPs. A UE configured with the UL MTRP-URLLC transmission method transmits the same data / UCI using different layer / time / frequency resources. At this time, the UE is instructed by the base station which Tx beam and which Tx power (i.e., UL TCI state) to use in the layer / time / frequency resource transmitting the same data / UCI. For example, if the same data / UCI is transmitted on resource 1 and resource 2, the UE is instructed on the UL TCI state used on resource 1 and the UL TCI state used on resource 2. This UL MTRP URLLC can be applied to PUSCH / PUCCH.
[0043] <SDCI or MDCI based MTRP 전송>
[0044] From the perspective of DCI (downlink control information) transmission, the M-TRP (multiple TRP) transmission method can be divided into i) M-DCI (multiple DCI) based M-TRP transmission in which each TRP transmits a different DCI, and ii) S-DCI (single DCI) based M-TRP transmission in which one TRP transmits DCI.
[0045] <R16 NR MTRP 전송>
[0046] The R16 NR standard supports S-DCI based MTRP PDSCH and M-DCI based MTRP PDSCH transmission methods.
[0047] <R16 M-DCI based MTRP PDSCH>
[0048] M-DCI based MTRP PDSCH transmission Each TRP schedules and transmits PDSCH through DCI. That is, TRP 1 transmits PDSCH 1 through DCI 1, and TRP 2 transmits PDSCH 2 through DCI 2. When PDSCH 1 and PDSCH 2 overlap in the same frequency time resource, two PDSCHs are received for the same RE, which increases resource efficiency and increases transmission capacity. To this end, the R16 standard introduces a CORESET pool, which is a group of multiple CORESETs. TRP 1 transmits a PDCCH through a CORESET belonging to CORESET pool 0, and the PDSCH scheduled by the PDCCH is also transmitted by TRP 1. TRP 2 transmits a PDCCH through a CORESET belonging to CORESET pool 1, and the PDSCH scheduled by the PDCCH is also transmitted by TRP 2. PUSCH can also schedule PUSCH transmission to a specific TRP for the UE through a CORESET belonging to each COERSET pool. For PUCCH, some PUCCH resources are scheduled by TRP 1 to receive UCI, and the remaining PUCCH resources are scheduled by TRP 2 to receive UCI. In the case of PUSCH or PUCCH, the channels scheduled / used by each TRP are TDMed with each other, so there is no overlap, and thus no increase in transmission capacity is expected. However, the UE can transmit independent PUSCH / PUCCH for each TRP 1 and 2.
[0049] Additionally, the UE may recognize the PUSCH (or PUCCH) scheduled by the DCI received in different CORESETs (or CORESETs belonging to different CORESET groups) as a PUSCH (or PUCCH) transmitted in different TRPs or as a PUSCH (or PUCCH) of different TRPs. Furthermore, the method for UL transmissions (e.g. PUSCH / PUCCH) transmitted in different TRPs can be equally applied to UL transmissions (e.g. PUSCH / PUCCH) transmitted in different panels belonging to the same TRP.
[0050] The CORESET group ID (or COERSET pool index having the same meaning) described / mentioned in this specification may mean an index / identification information (e.g. ID) for distinguishing a CORESET for each TRP / panel. And the CORESET group may be a group / union of CORESETs distinguished by an index / identification information (e.g. ID) for distinguishing a CORESET for each TRP / panel / the CORESET group ID, etc. For example, the CORESET group ID may be specific index information defined in the CORSET configuration. For example, the CORESET group may be set / indicated / defined by an index defined in the CORESET configuration for each CORESET. And / or CORESET group ID may mean an index / identification information / indicator for distinguishing / identifying between CORESETs set / associated in each TRP / panel, and the CORESET group ID described / mentioned in this specification may be expressed by being replaced with a specific index / specific identification information / specific indicator for distinguishing / identifying between CORESETs set / associated in each TRP / panel. The CORESET group ID, i.e., the specific index / specific identification information / specific indicator for distinguishing / identifying between CORESETs set / associated in each TRP / panel, may be set / indicated through higher layer signaling (e.g. RRC siganling) / L2 signaling (e.g. MAC-CE) / L1 signaling (e.g. DCI), etc. For example, PDCCH detection may be set / indicated to be performed for each TRP / panel in units of the corresponding CORESET group, 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 / instructed to be managed / controlled separately, and / or HARQ A / N (process / retransmission) for PDSCH / PUSCH, etc. scheduled for each TRP / panel by CORESET group unit can be managed.
[0051] For example, the upper layer parameter ControlResourceSet information element (IE) is used to configure a time / frequency control resource set (CORESET). For example, the control resource set (CORESET) may be related to detection and reception of downlink control information. The ControlResourceSet IE may include a CORESET-related ID (e.g., controlResourceSetID) / an index of a CORESET pool for the CORESET (e.g., CORESETPoolIndex) / time / frequency resource configuration of the CORESET / 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 above description, a CORESET group may correspond to a CORESET pool, and a CORESET group ID may correspond to a CORESET pool index (e.g., CORESETPoolIndex). ControlResourceSet (i.e. CORESET) can be set via higher layer signaling (e.g. RRC).
[0052] <TCI state / beam indication의 의미>
[0053] In addition, in the methods proposed in this specification 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.
[0054] For DL, this can mean estimating a channel from DMRS using the QCL type and QCL RS indicated by the DL TCI state in the frequency / time / spatial resources, and receiving / demodulating data / DCI through the estimated channel.
[0055] For UL, this may mean transmitting / modulating DMRS and data / UCI using the Tx beam and / or Tx power indicated by the corresponding UL TCI state in that frequency / time / space resource.
[0056] The above UL TCI state contains Tx beam or Tx power information of the UE, and can be set to the UE through other parameters such as spatial relation info instead of the TCI state. The UL TCI state can be directly indicated in the UL grant DCI, or it can mean spatial relation info of the SRS resource indicated through the SRI field of the UL grant DCI.
[0057] Or it can mean OL Tx power control parameter ( j: index for open loop parameters Po & alpha (maximum 32 parameter value sets per cell), q_d: index of DL RS resource for PL measurement (maximum 4 measurements per cell), l: closed loop power control process index (maximum 2 processes per cell) ) linked to the value indicated through SRI field of UL grant DCI. Or in R17 NR, UL TCI can be indicated using DL grant DCI.
[0058] <TRP 구분 관련 확장 설명>
[0059] For convenience of explanation, the proposed method assumes cooperative transmission / reception between two TRPs. However, it can be expanded to multiple TRP environments with three or more TRPs, as well as multi-panel environments. Different TRPs can be recognized by the UE as having different TCI states (associated with different CORESET pool indices).
[0060] For example, if the UE receives data / DCI using the first TCI state associated with the first CORESET pool index, it means that the data / DCI has been received from TRP1. For example, if the UE transmits data / UCI using the first TCI state associated with the first CORESET pool index, it means that the data / UCI has been transmitted to TRP 1.
[0061] For example, if the UE receives data / DCI using the second TCI state associated with the second CORESET pool index, it means that the data / DCI was received from TRP2. For example, if the UE transmits data / UCI using the second TCI state associated with the second CORESET pool index, it means that the data / UCI was transmitted to TRP 2.
[0062] <TA (Timing advance) related procedure >
[0063] Transmission of uplink frame number i from a terminal (User Equipment, UE) is earlier than the start of the corresponding downlink frame from that terminal. You have to start earlier.
[0064] The uplink timing (e.g., uplink frame) related to can be based on Table 1 below.
[0065]
[0066] Table 1 is N TA and N TA,offset can be calculated / determined based on N TA and N TA,offset can be set / applied as follows:
[0067] N TA : 1) Set via RAR (Random access response), 2) Set via Timing advance command (MAC-CE)
[0068] N TA,offset : 1) Set specific values for each serving cell, 2) Apply predefined values to each serving cell according to Duplex mode / FR
[0069] Below is the N described above TA,offset and N TAIt specifically explains how to set / apply.
[0070] N TA,offset
[0071] Case 1) How to set specific values for each serving cell
[0072] For example, the terminal is N TA,offset Configuration information (e.g., ServingCellConfigCommon Information) including information about can be received from the base station. The configuration information can be received based on RRC signaling. Table 2 below illustrates the configuration information.
[0073]
[0074] Case 2) How to apply predefined values to serving cells according to duplex mode / FR
[0075] For example, the terminal is predefined N according to Duplex mode (TDD / FDD) / FR. TA,offset The value of can be applied to the serving cell. Table 3 below shows N TA,offset exemplifies the value of .
[0076]
[0077] N TA
[0078] Case 1) How to set up using RAR (Random access response)
[0079] For example, in a random access procedure (e.g., a 2-step RACH procedure or a 4-step RACH procedure), the terminal may receive an RAR from the base station. Based on the RAR, N TAcan be determined / set. Specifically, the RAR may include a timing advance command. The timing advance command indicates an index value (e.g., index value TA) related to timing adjustment. Based on the index value, N TA can be determined (see Table 5 below). The RAR may be based on MAC RAR. This is described below with reference to FIG. 1.
[0080] Figure 1 illustrates a MAC RAR according to an embodiment of the present specification.
[0081] Referring to Figure 1, the MAC RAR may include an R (Reserved bit), a Timing Advance Command, a UL Grant, and a Temporary C-RNTI. Table 4 below illustrates the MAC payload of the MAC RAR.
[0082]
[0083] Table 5 below illustrates transmission timing adjustments based on the Timing advance command.
[0084]
[0085]
[0086]
[0087]
[0088] Case 2) How to set using Timing advance command (MAC-CE)
[0089] For example, N TA can be set / determined based on MAC-CE. Specifically, N TAcan be determined based on the Timing Advance Command MAC CE. The Timing Advance Command MAC CE may include a timing advance command. N based on the timing advance command TA Since the decision is the same as that described in Case 1, duplicate explanation is omitted (see Table 5). The Timing Advance Command MAC CE is described below with reference to FIG. 2.
[0090] FIG. 2 illustrates a Timing Advance Command MAC CE according to an embodiment of the present specification.
[0091] Referring to FIG. 2, the Timing Advance Command MAC CE may include a TAG ID and a Timing Advance Command. Table 6 below illustrates the payload of the Timing Advance Command MAC CE.
[0092]
[0093] <TAG (Timing advance group)>
[0094] A Timing Advance Group (TAG) is a group of serving cells that use the same Timing Advance value. Table 7 below illustrates the definition of a TAG and the associated configuration information.
[0095]
[0096]
[0097]
[0098] <procedure>
[0099] Uplink Time Alignment can be performed based on Table 8 below.
[0100]
[0101]
[0102]
[0103] The above-mentioned content can be applied in combination with the methods proposed in this specification, which will be described later, or can be supplemented to clarify the technical characteristics of the methods proposed in this specification. The methods described below are distinguished for convenience of explanation, and it is understood that certain components of one method may be substituted for or combined with other methods.
[0104] According to 3GPP standards up to NR Rel-17, the timing advance (TA) setting for uplink transmissions between base stations and terminals to compensate for propagation delay between the base station and terminals can be performed via higher-layer signaling. Furthermore, the concept / definition of a timing advance group (TAG) allows for separate TA settings and management for specific groups of cells.
[0105] Currently, configuring multiple TA values within a specific cell has not been supported. However, enhancements are planned to allow for the configuration / indication of multiple (two) TA values for a specific CC / BWP, considering scenarios where the distances between different target TRPs differ significantly during M-TRP UL transmission.
[0106] In this case, it is necessary to discuss how the base station will configure / instruct the terminal to configure / instruct multiple TA values, and / or how the connection between the multiple TA values and the terminal UL channel / RS will be performed. As described in Rel-18 MIMO WID objective (RP-213598) in Table 9 below, the configuration of TA values for multi-DCI (M-DCI) based M-TRP operation is being considered.
[0107]
[0108] Here, the above TA (TA value) may be based on the description of FIG. 2 and the contents described in the TA (Timing advance) related procedure described above.
[0109] In RAN1 and RAN2 standards prior to Rel-18, the base station must specify N for the terminal TA value. TA Wow N TA,offset It is managed through the value called . The base station is N TA can be set as follows: i) N via RAR MAC CE TA or ii) N through TA command MAC CE (Timing Advance Command MAC CE) TA In addition, the base station utilizes the concept of TAG (Timing Advance Group) to set up to 4 TAGs per terminal for a specific cell or cell combination, and N for each TAG. TA You can update / manage values.
[0110] A scenario that supports two TA values as described in WID is an M-DCI based M-TRP operation. In an M-DCI based M-TRP operation, each TRP can be distinguished based on a CORESET pool index associated with a CORESET(s) existing in a BWP. Based on the CORESET pool index, each TRP can be distinguished as i) a TRP performing DL transmission (i.e., PDCCH, PDSCH) or / and ii) a target TRP for UL transmission. For example, CORESETs 0 and 1 with CORESET pool index 0 can correspond to TRP 1, and CORESETs 2 and 3 with CORESET pool index 1 can correspond to TRP 2.
[0111] Meanwhile, in Rel-18 MIMO, an agreement was reached regarding two TAs, as shown in Table 10 below.
[0112]
[0113] As described above, it was discussed that two TAGs could be set up to manage two TA values in a single serving cell. Regarding the reference timings for applying the TA values managed in each TAG, it was agreed to support two DL reference timings in a single serving cell.
[0114] Additionally, it was agreed that the PDCCH ordered CFRA mechanism would be utilized for the two TA acquisitions. Discussions were held regarding uplink resources and the connectivity between the two TAs, which would determine which uplink transmissions the two acquired TAs (TAGs) should be utilized for. Consequently, it was agreed that the TAG ID would be associated with the UL and / or joint TCI state for the association of the two TAGs configured within the serving cell with the UL channel / RS, as shown in Table 10.
[0115] The remaining issues are as follows. For terminals utilizing the Rel-15 / 16 spatial relation framework, which does not support TCI state, the question is how to associate uplink resources with TAGs. Currently, the standardization meeting is primarily discussing associating TAG IDs with spatialRelationInfo, similar to associating TAGs with TCI states. However, even if TAG IDs are associated with spatialRelationInfo, the spatialRelation configuration / activation methods differ for each PUSCH / PUCCH / SRS, and when the UL default beam is utilized (e.g., when scheduled based on DCI format 0_0), ambiguity may exist regarding which TAG to utilize.
[0116] Based on this background, this specification proposes an uplink transmission method of a terminal when a base station supports multiple TAs in a specific CC / BWP(s) of the terminal.
[0117] In this specification, ' / ' can be interpreted as 'and', 'or', or 'and / or' depending on the context.
[0118] Issue 1: In the spatial relation framework of Rel-15 / 16, spatialRelationInfo is not directly configured / indicated for PUSCH. Specifically, the transmission beam of the SRS resource indicated by the SRI in the UL grant DCI is utilized for PUSCH transmission. In this case, ambiguity may exist regarding which of the multiple TAG IDs is utilized for the corresponding PUSCH transmission. Proposal 1 below specifically describes a solution to Issue 1.
[0119] <Proposal 1>
[0120] The TAG (TAG ID) associated with PUSCH can be determined based on at least one of the following ① to ③.
[0121] ① The TAG ID associated with PUSCH may be determined based on SRS resource(s). The SRS resource(s) may be SRS resource(s) indicated based on UL grant DCI. Specifically, the SRS resource(s) are indicated based on the SRI (SRS Resource Indicator) of the UL grant DCI. The UE may transmit the PUSCH based on the TAG ID associated with the spatialRelationInfo set / activated in the indicated SRS resource(s). For example, the UE may perform the corresponding PUSCH transmission by utilizing the TA value associated with the TAG ID utilized / applied when the indicated SRS resource(s) was previously transmitted.
[0122] ② The base station can indicate the TAG ID associated with the PUSCH to the terminal based on the codepoint of the SRI field in the UL grant DCI. Specifically, the TAG ID can be jointly encoded (along with the power control parameter set) for each codepoint in the SRI field.
[0123] According to the existing method, the following operations / configurations are applied for PUSCH scheduling based on UL grant DCI. A set of power control parameters (including closed / open-loop power control parameters) for PUSCH transmission is jointly encoded for each codepoint in the SRI field of the corresponding DCI. Similarly, a TAG ID to be utilized for PUSCH transmission can be jointly encoded for each codepoint in the SRI field of the UL grant DCI. If a specific codepoint is indicated based on the SRI field, the UE can perform PUSCH transmission by utilizing the TA value associated with the TAG ID jointly encoded in the corresponding codepoint.
[0124] ③ The TAG ID associated with PUSCH can be determined based on SRS resource(s). The SRS resource(s) may be SRS resource(s) configured based on ConfiguredGrantConfig. Specifically, SRS resource(s) are configured (for type 1 CG PUSCH) based on ConfiguredGrantConfig (in a semi-static manner). The UE can transmit PUSCH based on the TAG ID associated with the spatialRelationInfo configured / activated in the corresponding SRS resource(s). For example, the UE can perform the PUSCH transmission (e.g., type 1 configured grant PUSCH transmission) by utilizing the TA value associated with the TAG ID utilized when the SRS resource(s) configured in the corresponding ConfiguredGrantConfig was previously transmitted. The present embodiment can be utilized for type 1 configured grant PUSCH transmission, but is not limited thereto. That is, the present embodiment can also be applied to a PUSCH scheduled based on DCI.
[0125] Proposal 1 can be applied to i) dynamic grant PUSCH (DG PUSCH) and ii) CG PUSCH (e.g. Type 2 configured grant PUSCH scheduled / activated based on DCI).
[0126] Problem 2: It can be assumed that a PUSCH is scheduled based on DCI format 0_0 and a PUSCH is scheduled based on DCI format 0_1 / 0_2, and there is only one SRS resource in the SRS resource set. In this case, the usage set for the SRS resource set may be a codebook (CB) or a non-codebook (NCB). In this case, ambiguity may exist as to which of the multiple TAG IDs is utilized for the corresponding PUSCH. The following describes a case in which this problem occurs in more detail.
[0127] For example, in the case of a PUSCH scheduled based on DCI format 0_0, there is no SRI field in the DCI. The terminal determines the transmission beam (spatial domain transmission filter) of the PUSCH based on the PUCCH resource with the lowest ID. Specifically, the PUCCH resource may be the PUCCH resource with the lowest ID among the PUCCH resources to which PUCCH-spatialRelationInfo is connected. The spatial relation / spatial setting for PUSCH transmission may be based on a reference RS based on the spatialRelationInfo of the PUCCH resource. Similarly, a PUSCH may be scheduled based on DCI format 0_1 / 0_2. In this case, if there is only one SRS resource in the CB / NCB SRS resource set, the SRI field does not exist in the DCI.
[0128] Proposals 2-1 and 2-2 below specifically explain solutions to the above-mentioned problem 2.
[0129] <Proposal 2-1>
[0130] For a PUSCH scheduled based on DCI format 0_0, the TAG ID associated with the PUSCH may be determined based on at least one of the following embodiments.
[0131] ① The TAG ID associated with the PUSCH can be determined similarly to the transmission beam determination method of the PUSCH scheduled based on DCI format 0_0. Specifically, the UE can transmit the PUSCH based on the TAG ID associated with the (activated) spatialRelationInfo of the PUCCH that has the lowest ID among the PUCCH resources to which the PUCCH-spatialRelationInfo is connected / activated. The UE can perform the PUSCH transmission by utilizing the TA value based on the TAG ID associated with the spatialRelationInfo of the PUCCH.
[0132] ② The TAG ID associated with PUSCH can be semi-statically set / determined. Specifically, the base station can set / instruct the terminal via an RRC parameter the TAG ID to be applied when PUSCH transmission is scheduled based on DCI format 0_0. The RRC parameter can be a previously defined parameter or a newly defined parameter. The terminal can perform the corresponding PUSCH transmission by utilizing the TA value based on the TAG ID set based on the corresponding RRC parameter.
[0133] ③ The TAG ID can be determined based on embodiment ③ of proposal 1. That is, the terminal can transmit a PUSCH based on the TAG ID associated with the spatialRelationInfo set / activated in the SRS resource(s) set based on ConfiguredGrantConfig.
[0134] <Proposal 2-2>
[0135] When a PUSCH is scheduled based on DCI format 0_1 / 0_2 and there is only one SRS resource in a CB / NCB SRS resource set, a TAG ID associated with the PUSCH may be determined based on at least one of the following embodiments.
[0136] ① The TAG ID associated with PUSCH can be determined similarly to the PUSCH transmission beam determination method when there is only one SRS resource in the CB / NCB SRS resource set. Specifically, the UE can transmit the PUSCH based on the TAG ID associated with the spatialRelationInfo configured / activated in the SRS resource in the CB / NCB SRS resource set. The UE can perform the PUSCH transmission by utilizing the TA value associated with the TAG ID utilized when the configured SRS resource was previously transmitted.
[0137] Or / and, based on embodiment ② of proposal 2-1 or / and embodiment ③, the TAG ID associated with PUSCH can be determined.
[0138] As an additional embodiment of the above proposal 1 and proposal 2-1 / 2-2, the following operations / configurations may be considered for PUCCH and SRS.
[0139] In the case of PUCCH, the PUCCH transmission may be performed based on the TAG ID associated with the PUCCH-spatialRelationInfo configured / activated for each PUCCH resource. In this case, if different PUCCH resources exist within a specific PUCCH resource group, the UE may not expect that different PUCCH resources will be associated with different TAG IDs. Alternatively, when the base station configures different PUCCH resources within a PUCCH resource group, a restriction may be applied so that the PUCCH resources are associated with the same TAG ID (a restriction so that PUCCH resources are not associated with different TAG IDs). This embodiment takes into account the following technical matters.
[0140] Existing PUCCH resource groups are used as containers for simultaneously updating all PUCCH resources within the group with specific spatialRelationInfo. This may imply that the PUCCH resources within the PUCCH group are associated with a specific TRP / panel. Therefore, the additional embodiment described above is intended to prevent the mixing of different TRP-related TAG IDs within the PUCCH resource group.
[0141] In the case of SRS, the SRS transmission can be performed by utilizing the TAG ID associated with the spatialRelationInfo set / activated for each SRS resource. At this time, the terminal may not expect that different SRS resources within a specific SRS resource set are associated with different TAG IDs. Alternatively, the base station may apply a restriction to the SRS resources within the SRS resource set so that the SRS resources are associated with the same TAG ID (a restriction to prevent SRS resources from being associated with different TAG IDs). This embodiment takes into consideration the following technical matters.
[0142] Since SRS resources within a specific SRS resource set are associated with a single power control parameter set, this allows SRS resources within the SRS resource set to be associated with specific TRPs / panels. Therefore, the additional embodiment described above is intended to prevent SRS resources within the SRS resource set from being associated with different TRPs / TAGs.
[0143] In addition, when two SRS resource sets for CB / NCB use are set for M-TRP UL transmission, each SRS resource set can be associated / associated with a different TAG ID.
[0144] As an extension of Proposals 1 and 2, the following method can be considered. For M-TRP UL transmission, two SRI fields can be set / exist in the UL grant DCI (e.g., SRS resource indicator, second SRS resource indicator). In this case, when PUSCH transmissions related to different SRS resource sets are scheduled, the TAG ID associated with the spatialRelationInfo set / activated for the indicated SRS resource(s) based on each SRI field can be utilized when transmitting PUSCH related to each indicated SRS resource.
[0145] For the additional embodiments of the above proposals 1 and 2-1 / 2-2, it can also be applied to terminals supporting unified TCI standardized after Rel-17.
[0146] Issue 3: As the transmission beam update method evolves in the Rel-15 / 16 standards, spatialRelations can be updated based on RRC or MAC CEs for both PUCCH and SRS. The TAG ID associated with the spatialRelation can also be updated, but the timing of application of the updated TAG ID is unclear. This is explained in detail below.
[0147] For example, the spatialRelation for a specific UL resource can be updated from spatialRelation 1 to spatialRelation 2. If the update is an RRC based update, the spatialRelation is updated based on RRC reconfiguration. If the update is a MAC CE based update, the spatialRelation update is applied in slot n+3 when the (positive) A / N PUCCH transmission slot is n after receiving the MAC CE. As the spatialRelation is updated from spatialRelation 1 to spatialRelation 2, the associated TAG ID can be updated from TAG ID 1 to TAG ID 2. Unlike the updated spatialRelation, there is ambiguity as to when the TA value related to the updated TAG should be applied. A solution to problem 3 is specifically described in Proposal 3 below.
[0148] <Proposal 3>
[0149] ① The existing beam application timing can be extended and applied even when the TAG ID is updated. For example, spatialRelationInfo can be updated based on RRC signaling for a specific UL resource. In this case, the updated TAG ID can be applied to the RRC reconfiguration timing. For example, spatialRelationInfo can be updated based on MAC CE. The updated TAG ID can be applied at the time of MAC CE application (3 slots after the (positive) A / N PUCCH). If the terminal supports unified TCI, the beamAppTime (BAT) parameter related to the time slot for applying the indicated TCI after receiving the beam indication DCI can be utilized. Specifically, the updated TAG ID can be applied at the time slot after the Y symbol indicated by the beamAppTime (BAT) parameter from the last symbol of the acknowledgment for the beam indication DCI.
[0150] ② The behavior regarding when to apply the indicated TA value upon receiving a TA command (see Table 11 below) can also be extended and applied to TAG ID updates. Specifically, the updated TAG ID can be applied at the time (slot) when uplink timing adjustment based on the TA command is applied.
[0151]
[0152] Additionally, in the operation of ② above, the beam update application time for a specific UL resource can be redefined based on the TAG ID update application time. This allows the TAG ID update and beam update to be performed simultaneously. For example, if the beam update application time is earlier, the beam update time can be delayed temporally to match the TAG ID update time. This operation can be performed when the beam update application time is earlier temporally than the time required for the existing TAG ID update. This operation can solve the problem of misalignment between the transmission beam and TA values by updating the beam / TA simultaneously (as much as possible).
[0153] Proposal 3 above is applicable to terminals that support unified TCI standardized after Rel-17, even when the TCI state is associated with a TAG ID. That is, if the TCI state is updated by DCI / MAC CE / RRC and the TAG ID is also updated, the terminal can follow the operation of Proposal 3.
[0154] Issue 4: Current standardization discussions are underway to utilize RRC signaling to associate TAG IDs with UL or joint TCI states. In this case, up to eight TCI states are activated for the TCI state field of DL grant / non-grant DCI per CORESET pool based on MAC CE. This may lead to a mismatch in the rule (Table 10: 'One CORESET Pool Index corresponds to one TAG') that requires the same TAG ID to be associated with each CORESET pool (for the same TRP).
[0155] For example, it may be assumed that each TCI state is already associated with a TAG ID based on RRC signaling. In this case, when up to 8 TCI states are enabled in the TCI state field for a specific CORESET pool, a constraint may arise that only TCI states with the same TAG ID configured / associated can be utilized. Proposal 4 below specifically describes a solution to Problem 4.
[0156] <Proposal 4>
[0157] ① Restrictions may apply to base station operations. When activating up to 8 UL or joint TCI states in the TCI state field of DL grant / non-grant DCI for a specific CORESET pool within the CC / BWP, the base station may only utilize TCI states configured / connected with the same TAG ID.
[0158] ② When activating up to 8 UL or joint TCI states in the TCI state field of DL grant / non-grant DCI for a specific CORESET pool within CC / BWP, it may be acceptable for the TAG IDs configured / connected to the 8 TCI states to be different from each other. In this case, the 8 TCI states may be defined / regulated / agreed between the base station / terminal to be connected to a specific TAG ID among two different TAG IDs. For example, the specific TAG ID may be based on at least one of the following 1) to 5).
[0159] 1) TAG ID with the largest number of TAG IDs connected / configured to up to 8 TCI states
[0160] 2) TAG ID connected to the lowest TCI state among the TAG IDs connected / configured to the up to 8 TCI states
[0161] 3) TAG ID connected to the TCI state activated at the lowest codepoint among the TAG IDs connected / configured to up to 8 TCI states
[0162] 4) The lowest TAG ID among the TAG IDs connected / configured to the corresponding up to 8 TCI states.
[0163] 5) TAG ID associated with the CORESET pool index where the DCI was received
[0164] When activating up to 8 TCI states through the MAC CE through the above operation, the TAG ID associated / set with each TCI state can be updated by the corresponding MAC CE.
[0165] ③ When activating up to 8 UL or joint TCI states in the TCI state field of DL grant / non-grant DCI for a specific CORESET pool within CC / BWP, cases where the TAG IDs configured / connected to the 8 TCI states are different may be permitted. Since an explicit / implicit association relationship between a specific CORESET pool and a TAG ID may already exist, the associated / related TAG ID is connected / applied to the activated TCI states.
[0166] Additionally, in Rel-16 / 17 / 18 multi-beam enhancement, a simultaneous multi-CC TCI state update operation is defined to update (simultaneously / at once) specific TCI state ID(s) for (pre-configured) multiple CCs. Based on a target CC list pre-configured by the base station, the following operations i) and ii) can be performed.
[0167] i) By utilizing the TCI state pool set in the reference CC, simultaneous updates to the CC list can be performed with the TCI state(s) within the pool.
[0168] ii) Simultaneous updates can be performed for each CC (for TCI state(s) within the CC with the same TCI state ID(s)) by utilizing the TCI state pool set for each CC in the CC list.
[0169] When the above-described operation is performed together with an operation of linking the TCI state and TAG ID in two TAs, the following embodiment may be applied.
[0170] (In particular, in the above operation i) the terminal expects that all CCs in the CC list configured for simultaneous multi CC TCI state update are associated / associated with the same TAG ID(s). Or / and, the terminal does not expect that all CCs in the CC list configured for simultaneous multi CC TCI state update are associated / associated with different TAG ID(s). Or / and, the above-described setting can be enforced by the base station. The present embodiment takes into consideration the following technical matters.
[0171] Since the TAG ID related to the TCI state is updated together when the TCI state is updated, the above-described embodiment can be applied to prevent TAG IDs that are (previously) not related to the CC in each CC list from being indicated / updated by the TCI state update. That is, since a specific TAG is previously managed for a specific target group of CC(s), the above-described embodiment can be applied to maintain this connection.
[0172] The above-described embodiment is also applicable (for the target CC list) even when spatialRelationInfo is updated (simultaneously / at once) across multiple CCs.
[0173] Embodiments of proposals 1 / 2 / 3 / 4 and additional embodiments may operate in certain combinations.
[0174] An example of a terminal (or base station) operation based on at least one of the embodiments described above (e.g., at least one of Proposals 1 to 4) is as follows.
[0175] 1) The terminal (base station) receives (transmits) configurations related to two TAGs (two TAs) within a specific serving cell. These configurations may include the association between TAG IDs and UL resources. Before / after these configurations, two TA acquisitions (using PDCCH ordered CFRA) may be performed for each TAG.
[0176] 2) The terminal (base station) receives (transmits) a message scheduling uplink transmission related to the two TAGs. The message may be signaling via RRC / MAC / DCI. For example, the message may be DCI.
[0177] 3) The terminal (base station) transmits (receives) an uplink signal based on the above message.
[0178] The transmission and reception of the above uplink signal can be performed based on at least one of the above proposals 1 to 4.
[0179] The above terminal / base station operations are only an example, and each operation (or step) is not necessarily essential, and depending on the terminal / base station implementation method, operations related to uplink transmission related to different TAs of the terminal according to the above-described embodiments may be omitted or added.
[0180] In terms of implementation, the operations of the base station / terminal according to the embodiments described above (e.g., operations based on at least one of Proposals 1 to 4) can be processed by the device of FIG. 5 described below (e.g., processor (110, 210) of FIG. 5).
[0181] In addition, the operations of the base station / terminal according to the above-described embodiment (e.g., operations based on at least one of proposals 1 to 4) may be stored in a memory (e.g., 140, 240 of FIG. 5) in the form of commands / programs (e.g., instructions, executable codes) for driving at least one processor (e.g., 110, 210 of FIG. 5).
[0182] The embodiments described below are specifically described with reference to FIGS. 3 and 4 in terms of the operation of the terminal and base station. The methods described below are distinguished for convenience of explanation, and it is understood that some components of one method may be substituted for or combined with some components of another method.
[0183] FIG. 3 is a flowchart illustrating a method performed by a terminal according to one embodiment of the present specification.
[0184] Referring to FIG. 3, a method performed by a terminal according to one embodiment of the present specification includes a step of receiving configuration information related to a serving cell (S310), a step of receiving DCI (S320), and a step of transmitting PUSCH (S330).
[0185] In step S310, the terminal receives configuration information related to a serving cell from the base station. The configuration information includes the ID of the first Timing Advance Group (TAG) and the ID of the second TAG. For example, the configuration information may be based on the ServingCellConfig parameter.
[0186] In S320, the terminal receives downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) from the base station.
[0187] For example, the DCI may be based on DCI format 0_0, DCI format 0_1, or DCI format 0_2.
[0188] For example, the PUSCH may be a dynamic grant (DG) PUSCH. The PUSCH may be scheduled based on the DCI. For example, the PUSCH may be a configured grant (CG) PUSCH. PUSCH scheduling based on a configured grant (e.g., configured UL grant Type 2) may be activated based on the DCI.
[0189] In S330, the terminal transmits the PUSCH to the base station based on an uplink timing associated with one of the first TAG and the second TAG.
[0190] The TAG (i.e., the first TAG or the second TAG) associated with the above uplink timing may be determined based on at least one of the above-described proposals 1, 2-1, and / or 2-2. This will be described in detail below.
[0191] The TAG associated with the uplink timing may be determined based on i) a Sounding Reference Signal (SRS) resource, ii) a Physical Uplink Control Channel (PUCCH) resource, iii) an SRS resource indicator field of the DCI, or iv) a TAG setting associated with the PUSCH.
[0192] In one embodiment, the TAG associated with the uplink timing may be determined based on a Sounding Reference Signal (SRS) resource. This embodiment may be based on Embodiment ① of Proposal 1, Embodiment ③ of Proposal 1, and / or Embodiment ① of Proposal 2-2.
[0193] The TAG associated with the uplink timing may be associated with spatial relation information for the SRS resource. The spatial relation information for the SRS resource may refer to spatial relation information set / activated for the SRS resource.
[0194] The above SRS resource may be i) an SRS resource based on the above SRS resource indicator field or ii) an SRS resource associated with a configured grant.
[0195] In one embodiment, the TAG associated with the uplink timing may be determined based on the ID of the TAG mapped to the codepoint of the SRS resource indicator field. This embodiment may be based on embodiment ② of proposal 1.
[0196] According to one embodiment, the TAG associated with the uplink timing may be determined based on the PUCCH resource. Specifically, the TAG associated with the uplink timing may be associated with spatial relation information for the PUCCH resource. This embodiment may be based on embodiment ① of proposal 2-1. The DCI may be based on DCI format 0_0. The PUCCH resource may have a lowest ID within an active UL BandWidth Part (BWP). For example, the spatial relation information for the PUCCH resource may mean an activated spatial relation configuration for the PUCCH resource among spatial relation configurations (e.g., a List of spatial relation configurations) based on a PUCCH configuration (PUCCH-config).
[0197] In one embodiment, the TAG associated with the uplink timing may be determined based on a TAG configuration associated with the PUSCH. This embodiment may be based on embodiment ② of proposal 2-1. The DCI may be based on DCI format 0_0. Based on the TAG configuration, the ID of the TAG for the PUSCH scheduled based on the DCI format 0_0 may be indicated.
[0198] The above-described embodiments may be applied in cases where the unified Transmission Configuration Indication (TCI) state for PUSCH transmission cannot be utilized / used. Specifically, the above-described embodiments may be applied in cases where one of the TAGs for PUSCH transmission cannot be determined based on the unified TCI state.
[0199] For example, a unified TCI state may not be supported based on the capabilities of the terminal. For example, a unified TCI state may not be configured for an uplink bandwidth portion (UL BWP) or a component carrier (CC) (or serving cell). In such cases, the spatial relationship associated with the PUSCH (e.g., configuration of spatial relation, beam, spatial domain filter, or UL TX spatial filter) may be based on spatial relationship information for SRS resources or PUCCH resources.
[0200] Specifically, the PUSCH may be transmitted based on spatial relationship information for an SRS resource or a PUCCH resource. As described above, the spatial relationship information may refer to spatial relationship information (e.g., spatialRelationInfo parameter) set / activated in an SRS resource / PUCCH resource. If the unified TCI state is supported / set, the spatialRelationInfo parameter is not set. Conversely, if the unified TCI state is not supported / set, the spatialRelationInfo parameter is set. The following describes in detail the case where the unified TCI state is not set / supported in the serving cell.
[0201] The unified TCI state may not be set in the serving cell. Specifically, a parameter (e.g., the unifiedTCI-StateType parameter) indicating the type of unified TCI state (e.g., joint or separate) in the serving cell may not be set. The following describes in detail the operations / settings depending on whether the unifiedTCI-StateType parameter is set.
[0202] For example, if the unifiedTCI-StateType parameter is set to 'joint', a list of joint TCI states (e.g., dl-OrJointTCI-StateList) for UL and DL operations may be configured for the serving cell. For example, if the unifiedTCI-StateType parameter is set to 'separate', a list of UL TCI states for UL operation (e.g., ul-TCI-ToAddModList) and a list of DL TCI states for DL operation (e.g., dl-OrJointTCI-StateList) may be configured for the serving cell. For example, if the unifiedTCI-StateType parameter is not set, a list of unified TCI states may not be configured for the serving cell.
[0203] The limitations regarding cases where the unified TCI state described above is not configured / supported are not intended to limit the scope of the embodiments of this specification. Specifically, even when the unified TCI state is utilized / supported / configured, the TAG for PUSCH transmission can be determined based on the embodiments of this specification.
[0204] The operations based on S310 to S330 described above can be implemented by the device of FIG. 5. For example, the terminal (200) can control one or more transceivers (230) and / or one or more memories (240) to perform the operations based on S310 to S330.
[0205] The embodiments described below are specifically described in terms of base station operation.
[0206] S410 to S430 described below correspond to S310 to S330 described in FIG. 3. Considering the above correspondence, redundant descriptions are omitted. That is, the specific description of the base station operation described below may be replaced with the description / example of FIG. 3 corresponding to the corresponding operation.
[0207] FIG. 4 is a flowchart illustrating a method performed by a base station according to another embodiment of the present specification.
[0208] Referring to FIG. 4, a method performed by a base station in another embodiment of the present specification includes a step of transmitting configuration information related to a serving cell (S410), a step of transmitting DCI (S420), and a step of receiving PUSCH (S430).
[0209] In S410, the base station transmits configuration information related to the serving cell to the terminal.
[0210] In S420, the base station transmits downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) to the terminal.
[0211] In S430, the base station receives the PUSCH from the terminal based on an uplink timing associated with one of the first TAG and the second TAG.
[0212] The operations based on S410 to S430 described above can be implemented by the device of FIG. 5. For example, the base station (100) can control one or more transceivers (130) and / or one or more memories (140) to perform the operations based on S410 to S430.
[0213] The operations / terms based on the embodiments described above have been described assuming a 5G system. However, this is for convenience of explanation and is not intended to limit the scope of application of the technical problems and problem-solving means to be solved by this specification to a specific system. In other words, the technical problems / technical issues / problems mentioned in this specification may equally exist in other systems (e.g., 6G systems). It is self-evident that the embodiments of this specification can be expanded and applied to solve problems that equally exist in these other systems. Therefore, for the expanded application of the embodiments of this specification to other systems, the terms defined / described based on the 5G system can be replaced / changed with terms defined in the other systems (or generalized terms not specific to one system).
[0214] Hereinafter, a device to which an embodiment of the present specification can be applied (a device that implements a method / operation according to an embodiment of the present specification) is described with reference to FIG. 5.
[0215] FIG. 5 is a drawing showing the configuration of a first device and a second device according to an embodiment of the present specification.
[0216] The first device (100) may include a processor (110), an antenna unit (120), a transceiver (130), and a memory (140).
[0217] The processor (110) performs baseband-related signal processing and may include a higher layer processing unit (111) and a physical layer processing unit (115). The higher layer processing unit (111) may process operations of a MAC layer, an RRC layer, or higher layers. The physical layer processing unit (115) may process operations of a PHY layer. For example, when the first device (100) is a base station device in base station-terminal communication, the physical layer processing unit (115) may perform uplink reception signal processing, downlink transmission signal processing, etc. For example, when the first device (100) is a first terminal device in terminal-to-terminal communication, the physical layer processing unit (115) may perform downlink reception signal processing, uplink transmission signal processing, sidelink transmission signal processing, etc. In addition to performing baseband-related signal processing, the processor (110) may also control the overall operation of the first device (100).
[0218] The antenna unit (120) may include one or more physical antennas, and when it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (130) may include an RF (Radio Frequency) transmitter and an RF receiver. The memory (140) may store information processed by the processor (110), and software, an operating system, applications, etc. related to the operation of the first device (100), and may also include components such as a buffer.
[0219] The processor (110) of the first device (100) may be configured to implement the operation of the base station in the base station-to-terminal communication (or the operation of the first terminal device in the terminal-to-terminal communication) in the embodiments described in the present disclosure.
[0220] The second device (200) may include a processor (210), an antenna unit (220), a transceiver (230), and a memory (240).
[0221] The processor (210) performs baseband-related signal processing and may include a higher layer processing unit (211) and a physical layer processing unit (215). The higher layer processing unit (211) may process operations of a MAC layer, an RRC layer, or higher layers. The physical layer processing unit (215) may process operations of a PHY layer. For example, when the second device (200) is a terminal device in base station-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, etc. For example, when the second device (200) is a second terminal device in terminal-to-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, sidelink reception signal processing, etc. In addition to performing baseband-related signal processing, the processor (210) may also control the overall operation of the second device (210).
[0222] The antenna unit (220) may include one or more physical antennas, and when it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (230) may include an RF transmitter and an RF receiver. The memory (240) may store information processed by the processor (210), software, an operating system, applications, etc. related to the operation of the second device (200), and may also include components such as a buffer.
[0223] The processor (210) of the second device (200) may be configured to implement operations of the terminal in base station-to-terminal communication (or operations of the second terminal device in terminal-to-terminal communication) in the embodiments described in the present disclosure.
[0224] In the operation of the first device (100) and the second device (200), the same explanations given for the base station and the terminal (or the first terminal and the second terminal in the terminal-to-terminal communication) in the examples of the present disclosure may be applied, and redundant explanations are omitted.
[0225] Here, the wireless communication technology implemented in the device (100, 200) of the present disclosure may include not only LTE, NR, and 6G, but also Narrowband Internet of Things (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names.
[0226] Additionally or alternatively, the wireless communication technology implemented in the device (100, 200) of the present disclosure may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented by at least one of various standards such as 1) LTE CAT 0, 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, and is not limited to the above-described names.
[0227] Additionally or alternatively, the wireless communication technology implemented in the device (100, 200) of the present disclosure may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) that take low-power communication into account, and is not limited to the above-described names. For example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be called by various names.< / procedure>
Claims
1. In a method performed by a terminal, A step of receiving configuration information related to a serving cell, wherein the configuration information includes an ID of a first timing advance group (TAG) and an ID of a second TAG; A step of receiving downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH); and A step of transmitting the PUSCH based on an uplink timing associated with one of the first TAG and the second TAG; A method characterized in that the TAG related to the above uplink timing is determined based on a Sounding Reference Signal (SRS) resource.
2. In paragraph 1, A method characterized in that the TAG related to the uplink timing is determined based on i) the SRS resource, ii) a physical uplink control channel (PUCCH) resource, iii) an SRS resource indicator field of the DCI, or iv) a TAG setting related to the PUSCH.
3. In paragraph 2, A method characterized in that the TAG related to the uplink timing is associated with spatial relation information for the SRS resource.
4. In paragraph 3, A method characterized in that the above SRS resource is i) an SRS resource based on the SRS resource indicator field or ii) an SRS resource related to a configured grant.
5. In paragraph 2, A method characterized in that the TAG related to the uplink timing is determined based on the ID of the TAG mapped to the codepoint of the SRS resource indicator field.
6. In paragraph 2, A method characterized in that the TAG related to the uplink timing is associated with spatial relation information for the PUCCH resource.
7. In paragraph 6, A method characterized in that the above DCI is based on DCI format 0_0, and the PUCCH resource has the lowest ID within an active UL BandWidth Part (BWP).
8. In paragraph 2, The above DCI is based on DCI format 0_0, A method characterized in that the ID of the TAG for the PUSCH scheduled based on the DCI format 0_0 is indicated based on the TAG setting.
9. In paragraph 1, A method characterized in that the PUSCH is transmitted based on spatial relationship information for the SRS resource or PUCCH resource.
10. In paragraph 9, A method characterized in that a unified TCI state is not set in the serving cell.
11. In the terminal, One or more transmitters and receivers; one or more processors; and One or more memories connected to said one or more processors and storing instructions, A terminal characterized in that the instructions are set to cause the one or more processors to perform all steps of the method according to any one of claims 1 to 10, based on being executed by the one or more processors.
12. In a device comprising one or more memories and one or more processors functionally connected to the one or more memories, A device characterized in that said one or more memories store instructions that cause said one or more processors to perform all steps of a method according to any one of claims 1 to 10, based on execution by said one or more processors.
13. In one or more non-transitory computer-readable media storing instructions, One or more non-transitory computer-readable media characterized in that the instructions executable by one or more processors cause the one or more processors to perform all steps of the method according to any one of claims 1 to 10.
14. In a method performed by a base station, A step of transmitting configuration information related to a serving cell, wherein the configuration information includes an ID of a first timing advance group (TAG) and an ID of a second TAG; A step of transmitting downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH); and A step of receiving the PUSCH based on an uplink timing associated with one of the first TAG and the second TAG; A method characterized in that the TAG related to the above uplink timing is determined based on a Sounding Reference Signal (SRS) resource.
15. At the base station, One or more transmitters and receivers; one or more processors; and One or more memories connected to said one or more processors and storing instructions, A base station characterized in that the instructions are set to cause the one or more processors to perform all steps of the method according to claim 14, based on the instructions being executed by the one or more processors.
Citation Information
Patent Citations
Method and appratus for defalut beam behaviour of pusch for femimo
WO2022197065A1
Method and device for uplink transmission and reception in wireless communication system
WO2023080706A1
