Method for uplink transmission and reception in wireless communication system and apparatus therefor

By receiving and configuring multiple CORESET-related information in a wireless communication system, and sequentially initiated a random access process, the problem of high complexity of TRP-specific TA acquisition is solved, the TA acquisition efficiency and uplink timing accuracy are improved, and the UL scheduling reliability.

CN119054359APending Publication Date: 2024-11-29LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380035591.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-26
Filing Date
2023-04-25
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

In wireless communication systems, the complexity of obtaining TRP specific TA (timed advance value) between the terminal and the base station is high, resulting in low acquisition efficiency, especially when there are differences in propagation delays and time slot boundary differences between TRPs. It is difficult to obtain TRP 1 TA accurately.

Method used

By receiving configuration information related to multiple control resource sets (CORESET), receiving downlink control information (DCI) from the base station, sending a random access preamble to the base station, and receiving a random access response (RAR) from the base station, based on configuration The information configuration is based on the CORESET of the first and second control resource sets, and a random access process is initiated using the PDCCH sequence to obtain the TRP specific TA.

Benefits of technology

Reduces the implementation complexity of terminal and base stations, improves the acquisition efficiency and uplink timing accuracy of TRP-specific TAs, enhances the reliability of TRP-specific UL scheduling and transmission based on M-DCI, and avoids errors caused by TA acquisition errors. .

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119054359A_ABST
    Figure CN119054359A_ABST
Patent Text Reader

Abstract

According to an embodiment disclosed herein, a method performed by a terminal in a wireless communication system comprises the steps of: receiving configuration information related to a plurality of control resource sets (CORESETs) from a base station; receiving downlink control information (DCI) from the base station; sending a random access preamble to the base station; and receiving a random access response (RAR) from the base station. The random access preamble is transmitted based on an SSB index, and the SSB index is related to the first CORESET pool index or the second CORESET pool index.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a method for transmitting and receiving an uplink in a wireless communication system and an apparatus thereof. Background Art

[0002] A mobile communication system has been developed to provide voice services while ensuring user activities. Mobile communication systems have expanded their services from voice to data. The current rapid growth of data services is consuming resources, and users' demand for higher data rate services has led to a demand for more advanced mobile communication systems.

[0003] The requirements for the next generation of mobile communication systems must be able to meet the processing of explosive data services, the sharp increase in the transmission rate per user, the significant increase in the number of connected devices, and the support of very low end-to-end latency and high energy efficiency. To this end, a variety of technologies have been studied, such as dual connectivity, massive multiple-input multiple-output (MIMO), in-band full-duplex, non-orthogonal multiple access (NOMA), ultra-wideband support, and device networking.

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

[0005] In an environment where there is a large difference in distance between the UE and different TRPs, multi-DCI-based multiple transmission and reception point (M-DCI-based M-TRP) operation can be performed. In this case, propagation delay differences, slot boundary differences, and inter-UE panel delay differences may occur between target TRPs for uplink transmission within a CC / BWP. In particular, this phenomenon may occur to a greater extent in non-ideal backhaul operations where no coordination is performed between TRPs.

[0006] As described above, in order to compensate for the timing differences or delays that occur between TRPs, it is necessary to determine the uplink timing differently for each TRP. To this end, an operation of connecting TAGs / TCI states corresponding to unified TCIs (e.g., joint TCI states, separate TCI states (DL TCI states or UL TCI states)) has been agreed upon. Summary of the invention

[0007]

Technical issues

[0008] In order to perform M-TRP-based communication using the above-mentioned TRP-specific TA (e.g., two TAs correspond to two TRPs), the corresponding TA must first be acquired through signaling between the terminal and the base station. On the other hand, if a new configuration / operation is defined / specified / added to obtain the TRP-specific TA, it is inefficient in terms of terminal / base station implementation complexity.

[0009] The present disclosure proposes a method for obtaining a TRP-specific TA by considering the terminal / base station implementation complexity.

[0010] In the existing TA-related operation, when the time alignment timer expires, the terminal selects a random SSB (SSB index) and sends a random access preamble based on the SSB index. Such operation may be inefficient in acquiring / managing a TRP-specific TA.

[0011] For example, it may be assumed that the time alignment timer of the TA (e.g., the first TA) associated with TRP 1 (e.g., the first CORESET pool index) has expired. Since the terminal randomly selects one of a plurality of SSB indexes, an SSB index associated with TRP 2 (or a DL transmit beam of TRP 2) may be selected. In this case, it may be difficult to obtain the TA of TRP 1, or an inaccurate TA may be obtained.

[0012] In addition, the present disclosure proposes a method for managing a TRP-specific TA.

[0013] The technical objectives of the present disclosure are not limited to the above-mentioned technical objectives, and a person of ordinary skill in the art will clearly understand other technical objectives not mentioned above from the following description.

[0014]

Technical solution

[0015] According to an embodiment of the present disclosure, a method performed by a user equipment (UE) in a wireless communication system includes: receiving configuration information related to a plurality of control resource sets (CORESETs) from a base station, receiving downlink control information (DCI) from the base station, sending a random access preamble to the base station, and receiving a random access response (RAR) from the base station.

[0016] A CORESET based on a first control resource set (CORESET) pool index and a second control resource set (CORESET) pool index is configured based on the configuration information.

[0017] The DCI includes information related to the Physical Downlink Control Channel (PDCCH) sequence. The random access procedure is initiated by the PDCCH sequence.

[0018] Information related to the PDCCH order includes a synchronization signal / physical broadcast channel block index (SSB index).

[0019] The random access preamble is sent based on the SSB index. The random access response (RAR) includes the timing advance command.

[0020] The SSB index is associated with the first CORESET pool index or the second CORESET pool index.

[0021] The method may also include receiving a synchronization signal / physical broadcast channel block (SS / PBCH block, SSB) from a base station based on a plurality of SSB indexes.

[0022] The plurality of SSB indexes may include: i) a first SSB index associated with a first CORESET pool index and ii) a second SSB index associated with a second CORESET pool index.

[0023] The SSB index may be i) one of the first SSB indices or ii) one of the second SSB indices.

[0024] The RAR may be received based on monitoring PDCCH candidates in a search space set (SS set).

[0025] The SS set can be based on a common search space set (CSS set) or a UE-specific search space set (USS set).

[0026] The SSB set may be associated with one or more CORESETs based on the first CORESET pool index or the second CORESET pool index.

[0027] The timing advance command may indicate an index related to the timing adjustment, and may indicate N for calculating the timing advance (TA) based on the index related to the timing adjustment. TA .

[0028] The TA may be associated with a first timing advance group (TAG) or a second timing advance group (TAG). The first TAG may be associated with a first CORESET pool index, and the second TAG may be associated with a second CORESET pool index.

[0029] The time alignment timer associated with the TA may be a first time alignment timer associated with the first TAG or a second time alignment timer associated with the second TAG.

[0030] Based on the first time alignment timer and / or the second time alignment timer being associated with a primary timing advance group (PTAG), and the first time alignment timer and the second time alignment timer expiring: the configuration of the uplink transmission may be released.

[0031] Based on the expiration of the time alignment timer associated with the TA, the random access preamble can be sent based on the SSB index associated with the expired time alignment timer, and the SSB index associated with the expired time alignment timer can be associated with the first CORESET pool index or the second CORESET pool index.

[0032] The SSB index may be based on one or more SSB indexes. Based on one or more SSB indexes including: i) a first SSB index associated with a first CORESET pool index and ii) a second SSB index associated with a second CORESET pool index: a first random access preamble may be sent based on the first SSB index, and a second random access preamble may be sent based on the second SSB index.

[0033] According to another embodiment of the present disclosure, a user equipment (UE) operating in a wireless communication system includes: one or more transceivers, one or more processors, and one or more memories operably connected to the one or more processors. The one or more memories are configured to store instructions that allow the one or more processors to perform operations based on execution by the one or more processors.

[0034] The operations include receiving configuration information related to a plurality of control resource sets (CORESETs) from a base station, receiving downlink control information (DCI) from the base station, sending a random access preamble to the base station, and receiving a random access response (RAR) from the base station.

[0035] A CORESET based on a first control resource set (CORESET) pool index and a second control resource set (CORESET) pool index is configured based on the configuration information.

[0036] The DCI includes information related to the Physical Downlink Control Channel (PDCCH) sequence. The random access procedure is initiated by the PDCCH sequence.

[0037] Information related to the PDCCH order includes a synchronization signal / physical broadcast channel block index (SSB index).

[0038] The random access preamble is sent based on the SSB index. The random access response (RAR) includes a timing advance command.

[0039] The SSB index is associated with the first CORESET pool index or the second CORESET pool index.

[0040] A device according to another embodiment of the present disclosure includes: one or more memories and one or more processors operably connected to the one or more memories.

[0041] The one or more memories include instructions that, upon execution by the one or more processors, configure the one or more processors to perform operations.

[0042] The operations include receiving configuration information related to a plurality of control resource sets (CORESETs) from a base station, receiving downlink control information (DCI) from the base station, sending a random access preamble to the base station, and receiving a random access response (RAR) from the base station.

[0043] A CORESET based on a first control resource set (CORESET) pool index and a second control resource set (CORESET) pool index is configured based on the configuration information.

[0044] The DCI includes information related to the Physical Downlink Control Channel (PDCCH) sequence. The random access procedure is initiated by the PDCCH sequence.

[0045] Information related to the PDCCH order includes a synchronization signal / physical broadcast channel block index (SSB index).

[0046] The random access preamble is sent based on the SSB index. The random access response (RAR) includes a timing advance command.

[0047] The SSB index is associated with the first CORESET pool index or the second CORESET pool index.

[0048] One or more non-transitory computer-readable media according to another embodiment of the present disclosure store one or more instructions.

[0049] The one or more instructions executable by the one or more processors are configured to enable the one or more processors to perform operations.

[0050] The operation includes: receiving configuration information related to a plurality of control resource sets (CORESETs) from a base station; receiving downlink control information (DCI) from the base station; sending a random access preamble to the base station; and receiving a random access response (RAR) from the base station.

[0051] A CORESET based on a first control resource set (CORESET) pool index and a second control resource set (CORESET) pool index is configured based on the configuration information.

[0052] The DCI includes information related to the Physical Downlink Control Channel (PDCCH) sequence. The random access procedure is initiated by the PDCCH sequence.

[0053] Information related to the PDCCH order includes a synchronization signal / physical broadcast channel block index (SSB index).

[0054] The random access preamble is sent based on the SSB index. The random access response (RAR) includes the timing advance command.

[0055] The SSB index is associated with the first CORESET pool index or the second CORESET pool index.

[0056] According to another embodiment of the present invention, a method performed by a base station in a wireless communication system includes: sending configuration information related to multiple control resource sets (CORESETs) to a user equipment (UE), sending downlink control information (DCI) to the UE, receiving a random access preamble from the UE, and sending a random access response (RAR) to the UE.

[0057] A CORESET based on a first control resource set (CORESET) pool index and a second control resource set (CORESET) pool index is configured based on the configuration information.

[0058] The DCI includes information related to the Physical Downlink Control Channel (PDCCH) sequence, and the random access procedure is initiated by the PDCCH sequence.

[0059] Information related to the PDCCH order includes a synchronization signal / physical broadcast channel block index (SSB index).

[0060] A random access preamble is received based on the SSB index. A random access response (RAR) includes a timing advance command.

[0061] The SSB index is associated with the first CORESET pool index or the second CORESET pool index.

[0062] According to another embodiment of the present disclosure, a base station operating in a wireless communication system includes: one or more transceivers, one or more processors, and one or more memories operably connected to the one or more processors. The one or more memories are configured to store instructions that allow the one or more processors to perform operations based on execution by the one or more processors.

[0063] The operation includes sending configuration information related to a plurality of control resource sets (CORESETs) to a user equipment (UE), sending downlink control information (DCI) to the UE, receiving a random access preamble from the UE, and sending a random access response (RAR) to the UE.

[0064] A CORESET based on a first control resource set (CORESET) pool index and a second control resource set (CORESET) pool index is configured based on the configuration information.

[0065] The DCI includes information related to the Physical Downlink Control Channel (PDCCH) sequence, and the random access procedure is initiated by the PDCCH sequence.

[0066] Information related to the PDCCH order includes a synchronization signal / physical broadcast channel block index (SSB index).

[0067] A random access preamble is received based on the SSB index. A random access response (RAR) includes a timing advance command.

[0068] The SSB index is associated with the first CORESET pool index or the second CORESET pool index.

[0069]

Beneficial Effects

[0070] According to an embodiment of the present disclosure, a random access preamble is transmitted based on an SSB index indicated by a DCI related to a PDCCH sequence. The SSB index is related to a TRP (ie, a CORESET pool index). Therefore, the following effects can be derived.

[0071] 1) The TRP-specific TA can be obtained through the existing RACH process initiated by the PDCCH sequence. Therefore, compared with configuring / defining new parameters or separate signaling to obtain the TRP-specific TA, the complexity of the terminal / base station implementation can be reduced.

[0072] 2) Before performing any uplink channel / signal transmission, except for PRACH transmission (i.e., random access preamble transmission), the TRP-specific TA can be acquired and used for UL transmission. For example, Msg3 (PUSCH) transmission based on the random access procedure initiated by PDCCH sequence can be performed based on the TRP-specific TA indicated via RAR.

[0073] 3) Ability to improve the reliability of M-DCI based TRP-specific UL scheduling / UL transmission by utilizing the acquired TRP-specific TA (improving the uplink timing accuracy of each TRP).

[0074] According to an embodiment of the present disclosure, when a time alignment timer associated with a TA expires, a random access preamble is sent based on an SSB index associated with the expired time alignment timer. The SSB index is associated with a first CORESET pool index or a second CORESET pool index.

[0075] Therefore, the process performed after the time alignment timer of the TRP-specific TA expires can be performed more efficiently in terms of acquisition / management of the TRP-specific TA. That is, after the time alignment timer of a TRP-specific TA (e.g., TA1 of TRP1) expires, it is possible to prevent an erroneous TA from being acquired due to an SSB index selected by the terminal (e.g., an SSB index associated with TRP2).

[0076] Effects that can be obtained from the present disclosure are not limited to the above-mentioned effects, and other technical effects that are not mentioned can be clearly understood by those skilled in the art to which the present disclosure belongs from the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0077] Figure 1 A MAC RAR according to an embodiment of the present disclosure is illustrated.

[0078] Figure 2 A timing advance command MAC CE according to an embodiment of the present disclosure is illustrated.

[0079] Figure 3 is a flowchart illustrating a method performed by a UE in a wireless communication system according to an embodiment of the present disclosure.

[0080] Figure 4 is a flowchart illustrating a method performed by a base station in a wireless communication system according to another embodiment of the present disclosure.

[0081] Figure 5 The configurations of the first device and the second device according to the embodiment of the present disclosure are illustrated. DETAILED DESCRIPTION

[0082] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Figure 1 The detailed description disclosed above is intended to describe exemplary embodiments of the present disclosure, rather than to describe the only embodiment for performing the present disclosure. The following detailed description includes details to provide a complete understanding of the present disclosure. However, those skilled in the art will appreciate that the present disclosure may be performed without the details.

[0083] In some cases, in order to prevent the concepts of the present disclosure from being unclear, known structures or devices may be omitted, or may be shown in the form of a block diagram focusing on the core functions of each structure and device.

[0084] In the following, 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 transmitter may be part of a base station, and the receiver may be part of a terminal. In the uplink, the transmitter may be part of a terminal, and the receiver may be part of a base station. The base station may be expressed as a first communication device, and the terminal may be expressed as a second communication device. The following terms may be used instead of a base station (BS), including: fixed station, Node B (Node B), evolved Node B (eNB), next generation Node B (gNB), base transceiver system (BTS), access point (AP), network (5G network), AI system, road side unit (RSU), vehicle, robot, unmanned aerial vehicle (UAV), AR (augmented reality) device, VR (virtual reality) device, and the like. In addition, the terminal may be fixed or mobile and may be replaced by the following 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), AR (augmented reality) device, VR (virtual reality) device, etc.

[0085] Multiple transmit / receive point (M-TRP) related operations

[0086] The M-TRP transmission scheme in which M TRPs transmit data to one user equipment (UE) can be divided into two main types, eMBB M-TRP transmission, which is a scheme for increasing the transmission rate, and URLLC M-TRP transmission, which is a scheme for increasing the reception success rate and reducing the delay.

[0087] MTRP URLLC

[0088] Hereinafter, in the method proposed in the present disclosure, DL MTRP-URLLC means that multiple TRPs send the same data / DCI using different layer / time / frequency resources. For example, TRP 1 sends the same data / DCI in resource 1, and TRP 2 sends the same data / DCI in resource 2. A UE configured with a DL MTRP-URLLC transmission scheme receives the same data / DCI using different layer / time / frequency resources. In this case, the base station indicates which QCL RS / type (i.e., DL TCI state) the UE should use in the layer / time / frequency resource for receiving the same data / DCI. For example, when the same data / DCI is received from resource 1 and resource 2, the DL TCI state used in resource 1 and the DL TCI state used in resource 2 are indicated to the UE. Since the UE receives the same data / DCI via resource 1 and resource 2, high reliability can be achieved. DLMTRP-URLLC can be applied to PDSCH / PDCCH.

[0089] In contrast, UL MTRP-URLLC means that multiple TRPs receive the same data / UCI from one UE using different layer / time / frequency resources. For example, TRP 1 receives the same data / UCI from the UE in resource 1, and TRP 2 receives the same data / UCI from the UE in resource 2. Then, TRP 1 and TRP 2 share the received data / UCI through the connection backhaul link between the TRPs. A UE configured with the UL MTRP-URLLC transmission scheme sends the same data / UCI using different layer / time / frequency resources. In this case, the base station indicates which Tx beam and which Tx power (ie, UL TCI state) the UE should use in the layer / time / frequency resource for sending the same data / UCI. For example, when the same data / UCI is sent in resource 1 and resource 2, the UE is indicated the UL TCI state used in resource 1 and the UL TCI state used in resource 2. UL MTRP-URLLC can be applied to PUSCH / PUCCH.

[0090] MTRP transmission based on SDCI or MDCI

[0091] In addition, from the perspective of downlink control information (DCI) transmission, the M-TRP (multi-TRP) transmission scheme can be divided into: i) an M-TRP transmission scheme based on multiple DCI (M-DCI), in which each TRP transmits different DCI, and ii) an M-TRP transmission scheme based on single DCI (S-DCI), in which one TRP transmits DCI. For example, in S-DCI, since all scheduling information of data transmitted by M TRPs should be transmitted via one DCI, S-DCI can be used in an ideal backhaul (BH) environment, in which dynamic collaboration can be performed between two TRPs.

[0092] R16 NR MTRP sent

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

[0094] R16 MTRP PDSCH based on M-DCI

[0095] M-DCI-based MTRP PDSCH transmission is a way that each TRP schedules and transmits PDSCH via DCI. That is, TRP1 transmits PDSCH 1 via DCI 1, and TRP 2 transmits PDSCH 2 via DCI 2. When PDSCH 1 and PDSCH 2 overlap on the same frequency-time resource, the two PDSCHs are received by the same RE, thereby improving resource efficiency and increasing transmission capacity. To this end, the R16 standard has introduced a CORESET pool, which is a group of multiple CORESETs, and TRP 1 transmits PDCCH through a CORESET belonging to CORESET pool 0, and the PDSCH scheduled by the corresponding PDCCH is also transmitted by TRP 1. TRP 2 transmits PDCCH through a CORESET belonging to CORESET pool 1, and the PDSCH scheduled by the corresponding PDCCH is also transmitted by TRP 2. For PUSCH, a specific TRP can schedule the transmission of PUSCH to the UE through a CORESET belonging to each CORESET pool. For PUCCH, TRP 1 schedules part of the 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 TDMed with each other and do not overlap. Therefore, an increase in transmission capacity cannot be expected, but the UE is able to independently transmit PUSCH / PUCCH to each of TRP 1 and TRP 2.

[0096] In addition, the UE may identify the PUSCH (or PUCCH) scheduled by the DCI received via different CORESETs (or CORESETs belonging to different CORESET groups) as the PUSCH (or PUCCH) sent to different TRPs, or identify the PUSCH (or PUCCH) of different TRPs. The scheme of 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.

[0097] The CORESET group ID (or the COERSET pool index having the same meaning) described / mentioned in the present disclosure may represent the index / identification information (e.g., ID) and the like for distinguishing the CORESET of each TRP / panel. In addition, the CORESET group may be a group / union of CORESETs for distinguishing the CORESET of each TRP / panel classified by the index / identification information (e.g., ID) / CORESET group ID and the like. For example, the CORESET group ID may be specific index information defined in the CORESET configuration. For example, the CORESET group may be configured / indicated / defined by the index defined for each CORESET in the CORESET configuration. And / or, the CORESET group ID may represent the index / identification information / indicator and the like for distinguishing / identifying the configured CORESET associated with each TRP / panel, and the CORESET group ID described / mentioned in the present disclosure may be replaced and expressed with the specific index / specific identification information / specific indicator and the like for distinguishing / identifying the configured CORESET associated with each TRP / panel. The CORESET group ID, i.e., a specific index / specific identification information / specific indicator for distinguishing / identifying a configured / related CORESET to each TRP / panel, may be configured / indicated via higher layer signaling (e.g., RRC signaling) / L2 signaling (e.g., MAC-CE) / L1 signaling (e.g., DCI), etc. For example, it may be configured / indicated that PDCCH detection for each TRP / panel is performed in units of the corresponding CORESET group, and / or it may be configured / indicated that uplink control information (e.g., CSI, HARQ-A / N, SR) and / or uplink physical channel resources (e.g., PUCCH / PRACH / SRS resources) are managed / controlled separately for each TRP / panel in units of the corresponding CORESET group, and / or the HARQ A / N (processing / retransmission) of PDSCH / PUSCH, etc. scheduled for each TRP / panel may be managed in units of the corresponding CORESET group.

[0098] For example, a higher layer parameter ControlResourceSet IE (information element) is used to configure a time / frequency control resource set (CORESET). For example, a control resource set (CORESET) may be associated with the 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 of a CORESET (e.g., CORESETPoolIndex) / a time / frequency resource configuration of a CORESET / TCI information associated with a CORESET, etc. For example, an index of a CORESET pool (e.g., CORESETPoolIndex) may be set to 0 or 1. In the 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). The ControlResourceSet (i.e., CORESET) may be configured via higher layer signaling (e.g., RRC).

[0099] R17 NR MTRP sent

[0100] In the R17 NR standard, MTRP PDCCH retransmission, MTRP PDCCH / PDSCH SFN transmission, S-DCI-based MTRP PUSCH retransmission, and MTRP PUCCH retransmission based on a single PUCCH resource are supported. In all these transmission schemes, the same content (i.e., DCI or UL TB or UCI) is retransmitted as URLLC target enhancement to improve reliability. In MTRP PDCCH retransmission, they are TDM or FDM and retransmitted, in MTRP PDCCH / PDSCH SFN retransmission, they are retransmitted at the same time / same frequency / same layer, in S-DCI-based MTRP PUSCH retransmission, they are TDM, and in MTRP PUCCH retransmission based on a single PUCCH resource, they are TDM and retransmitted.

[0101] R17 MTRP SFN PDCCH

[0102] As a special case of MTRP PDCCH retransmission, multiple TRPs can retransmit the same DCI through the same time / frequency / DMRS port, which can be called SFN PDCCH retransmission. However, for SFN PDCCH retransmission, the base station configures multiple TCI states to one CORESET instead of configuring multiple CORESETs with different TCI states. When the UE receives a PDCCH candidate through an SS set connected to one CORESET, the UE performs channel estimation of the PDCCH DMRS using all multiple TCI states and attempts to decode.

[0103] R17 MTRP SFN PDSCH

[0104] When performing MTRP PDCCH retransmission, the two TRPs retransmit the corresponding channel to different resources. However, in special cases, when the resources used by the two TRPs are the same, that is, when the same channel is retransmitted through the same frequency, time and layer (=DMRS port), the reliability of the corresponding channel can be improved. In this case, since the resources are not distinguished and are combined and received in the air, the retransmitted same channel is identified as one channel from the perspective of the receiving end. In the R17 NR standard, two DL TCI states configured for PDSCH DMRS reception can be sent for PDSCH SFN.

[0105] R17 MTRP PUCCH retransmission based on single PUCCH resource

[0106] In the R17 NR standard, the base station activates / configures two spatial relationship information (activates / configures two power control (PC) parameter sets in FR1) to the UE in a single PUCCH resource for MTRP PUCCH transmission based on a single PUCCH resource, and when transmitting UL UCI through the corresponding PUCCH resource, the UE uses each spatial relationship information to indicate the spatial relationship information toward each of TRP 1 and TRP 2. For example, the Tx beam / PC parameters toward TRP 1 are indicated to the UE by the value indicated in the first spatial relationship information, and the UE uses the information to perform PUCCH transmission in the TO corresponding to TRP 1. In the same way, the Tx beam / PC parameters toward TRP 2 are indicated to the UE by the value indicated in the second spatial relationship information, and the UE uses the information to perform PUCCH transmission in the TO corresponding to TRP 2.

[0107] In the Rel 17 standardization meeting, the configuration scheme was enhanced for MTRP PUCCH retransmission, so that two spatial relationship information can be configured in the PUCCH resources. That is, if PC parameters such as PLRS, Alpha, P0, closed-loop index, etc. are set for each spatial relationship information, the spatial relationship RS can be configured. Therefore, it is possible to configure the PC information and spatial relationship RS information corresponding to the two TRPs through two spatial relationship information, and the UE uses the first spatial relationship information to send PUCCH in TO 1, and uses the second spatial relationship information to send the same UCI (ie, CSI, ACKNAK, SR) PUCCH in TO 2. Hereinafter, the PUCCH resources configured with two spatial relationship information are referred to as MTRP PUCCH resources, and the PUCCH resources configured with one spatial relationship information are referred to as STRP PUCCH resources.

[0108] Meaning of TCI status / beam indication

[0109] In the following method proposed in the present disclosure, using ( / mapping) a specific TCI state (or TCI) when receiving data / DCI / UCI of a frequency / time / space resource may mean, for DL, estimating a channel from DMRS and receiving / demodulating data / DCI on the estimated channel using the QCL type and QCL RS indicated by the corresponding DL TCI state in the frequency / time / space resource. For UL, this may mean using the Tx beam and / or Tx power indicated by the corresponding UL TCI state in the frequency / time / space resource to transmit / demodulate DMRS and data / UCI.

[0110] The UL TCI state contains the Tx beam or Tx power information of the UE and can be configured to the UE by another parameter (such as spatial relationship information) instead of the TCI state. The UL TCI state can be directly indicated to the UL grant DCI, or can represent the spatial relationship information of the SRS resource indicated by the SRI field of the UL grant DCI. Alternatively, the UL TCI state can represent the OL Tx power control parameters connected to the value indicated by the SRI field of the UL grant DCI (j: index of open-loop parameters Po and alpha (up to 32 parameter value sets per cell), q_d: index of DL RS resources used for PL measurement (up to 4 measurements per cell), l: closed-loop power control process index (up to 2 processes per cell)). Alternatively, in R17 NR, the UL TCI state can use DL grant DCI to indicate the UL TCI.

[0111] For ease of explanation, the present disclosure has applied the proposed method assuming collaborative transmission / reception between two TRPs, but it can be extended and applied to 3 or more multi-TRP environments, and can be extended and applied to multi-panel environments. Different TRPs will be recognized by the UE as different TCI states, and the UE receiving / sending data / DCI / UCI using TCI state 1 means that the UE receives / sends data / DCI / UCI from / to TRP 1.

[0112] In the present disclosure, when multiple channels are TDMed, the transmission timing (TO) means that each channel is transmitted at different times; when multiple channels are FDMed, each channel is transmitted on different frequencies / RBs; and when multiple channels are SDMed, each channel is transmitted on different layers / beams / DMRS ports. Each TO is mapped to a TCI state. When the same channel is retransmitted, the complete DCI / data / UCI is sent to one TO, and the receiving end receives multiple TOs to improve the reception success rate.

[0113] Timing Advance (TA) Related Processes

[0114] The uplink frame number i from the user equipment (UE) shall start before the start of the corresponding downlink frame at the UE .

[0115] and The relevant uplink timing (eg, uplink frame) may be based on Table 1 below.

[0116]

Table 1

[0117]

[0118] In Table 1, Can be based on N TA and N TA,offset Calculate / determine. TA and N TA,offset Can be configured / applied as follows.

[0119] N TA : 1) via Random Access Response (RAR), and 2) via Timing Advance Command (MAC-CE)

[0120] N TA,offset : 1) configure a specific value for each serving cell and 2) apply the predefined value appropriately to the serving cell based on duplex mode / FR

[0121] The following describes the above configuration / application in detail TA,offset and N TA method.

[0122] NTA,offset

[0123] Case 1) Each serving cell is configured with a specific value

[0124] For example, the UE may receive information including information about N TA,offset The configuration information may be received based on RRC signaling, and the following Table 2 shows the configuration information.

[0125]

Table 2

[0126]

[0127] Case 2) Method of appropriately applying predefined values ​​based on duplex mode / FR to serving cell

[0128] For example, the UE can set N based on the duplex mode (TDD / FDD) / FR. TA,offset The predefined value of N is appropriately applied to the serving cell. TA,offset The value of .

[0129]

Table 3

[0130]

[0131] N TA

[0132] Case 1) Method configured via Random Access Response (RAR)

[0133] For example, in a random access procedure (e.g., a 2-step RACH procedure or a 4-step RACH procedure), the UE may receive a RAR from the base station. The NTA may be determined / configured based on the RAR. Specifically, the RAR may include a timing advance command. The timing advance command indicates an index value (e.g., index value TA) related to the timing adjustment. The NTA may be determined based on the index value (see Table 4 below). The RAR may be based on the MAC RAR. Figure 1 Describe this.

[0134] Figure 1 A MAC RAR according to an embodiment of the present disclosure is illustrated.

[0135] refer to Figure 1 , MAC RAR may include a reserved bit (R), a timing advance command, a UL grant, and a temporary C-RNTI. The following Table 4 shows the MAC payload of MAC RAR.

[0136]

Table 4

[0137]

[0138] Table 5 below shows the transmission timing adjustment based on the timing advance command.

[0139]

Table 5

[0140]

[0141] Case 2) Configuration via Timing Advance Command (MAC-CE)

[0142] For example, NTA may be determined / configured based on MAC-CE. Specifically, NTA may be determined based on a timing advance command MAC CE. The timing advance command MAC CE may include a timing advance command. Since determining NTA based on the timing advance command is the same as described in Case 1, repeated description is omitted (see Table 4). Figure 2 Describe the Timing Advance Command MAC CE.

[0143] Figure 2 A timing advance command MAC CE according to an embodiment of the present disclosure is illustrated.

[0144] refer to Figure 2 , the timing advance command MAC CE may include a TAG ID and a timing advance command. Table 6 below shows the payload of the timing advance command MAC CE.

[0145]

Table 6

[0146]

[0147] Timing Advance Group (TAG)

[0148] A timing advance group (TAG) refers to a group of serving cells using the same timing advance value. Table 7 below shows the definition of a TAG and configuration information related to the TAG.

[0149]

Table 7

[0150]

[0151]

[0152]

[0153] process

[0154] Uplink time alignment can be performed based on Table 8.

[0155]

Table 8

[0156]

[0157]

[0158]

[0159] The above contents (multiple TRPs and timing advance, etc.) 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 features of the methods proposed in this specification. The methods described below are classified only for the convenience of explanation, and some components of one method can be replaced with some components of another method, or can be applied in combination with each other.

[0160] Hereinafter, i) a method in which a base station configures / indicates multi-TA for a specific CC / BWP in uplink transmission of a terminal, and ii) a method in which a terminal requests / acquires multi-TA will be described, and subsequent terminal operations will be proposed.

[0161] According to the 3GPP standard up to NR Rel-17, the timing advance (TA) configuration of the UE uplink transmission of the base station can be performed via higher layer signaling to compensate for the propagation delay between the base station and the UE. In addition, the TA of a specific cell can be separately configured / managed through the concept / definition of a timing advance group (TAG).

[0162] So far, there is no method to support multiple TA values ​​within a specific cell. However, considering the scenario where the distances of different target TRPs to the UE vary greatly when M-TRP UL is transmitted, enhancements will be performed to be able to set / indicate multiple (two) TA values ​​in a specific CC / BWP.

[0163] In this case, it is necessary to discuss how the base station configures / indicates multiple TA values ​​to the UE or / and how to perform the connection relationship between multiple TA values ​​and UE UL channels / RS. As described in Rel-18 MIMO WID Target (RP-213598) in Table 9 below, the configuration of TA values ​​for M-TRP operation based on multi-DCI (M-DCI) is considered.

[0164]

Table 9

[0165]

[0166] Here, TA (TA value) can be based on Figure 2 and the contents described in the above timing advance (TA) related process.

[0167] In the RAN1 and RAN2 standards before Rel-18, the base station is based on N TA and N TA,offset The base station can set N based on i) RAR MAC CE or ii) TA command MAC CE.TA . In addition, the base station can configure up to four TAGs for the UE for a specific cell or cell combination using the concept of a timing advance group (TAG). The base station can perform update / management on the NTA value for each TAG. In other words, the NTA value related to the uplink timing of the UE can be determined / set based on the RAR MAC CE / TA command MAC CE for each TAG.

[0168] In Rel-18 MIMO, to support different TA values ​​for UEs based on target TRP, i) the base station can set N in a specific CC / BWP. TA (or / and N TA,offset ) two TRP specific values, or ii) the base station can configure separate parameters (such as N TA,TRP1 and / or N TA,TRP2 ), so that in addition to N TA or / and N TA,offset In addition to the TRP value, a TRP-specific TA offset value is also configured / allocated. In method ii), when calculating the existing TA value of the UE, the TA offset may need to be additionally subtracted / added due to separate parameters. Hereinafter, the two TA values ​​managed by methods i) or / and ii) may be represented as TA1 (or the first TA) and TA2 (or the second TA). In this case, the two TA values ​​may correspond to two TAGs. For example, TA1 corresponding to TRP1 may be associated with TAG 1, and TA2 corresponding to TRP2 may be associated with TAG 2.

[0169] As described in the WID, the scenario that supports two TA values ​​is M-DCI-based M-TRP operation. In M-DCI-based M-TRP operation, 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 that performs 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 TRP 1, and CORESET 2 and 3 set to CORESET pool index 1 can correspond to TRP 2.

[0170] In the unified TCI framework introduced in Rel-17 MIMO, a base station may dynamically indicate a specific reference RS to be used as a common beam for a DL / UL reception (Rx) / transmission (Tx) beam of a UE using a DL / UL joint TCI state and / or a DL / UL separate TCI state.

[0171] The DL / UL joint TCI state may be based on the joint TCI state configured for UL and DL operations. When the unifiedTCI-StateType of the serving cell is set to "joint", the joint TCI state may be configured based on the dl-OrJointTCI-StateList.

[0172] DL / UL separate TCI state can be based on DL TCI state and / or UL TCI state. When unifiedTCI-StateType of the serving cell is set to "separate", DL TCI state can be configured based on dl-OrJointTCI-StateList and UL TCI state can be configured based on ul-TCI-ToAddModList.

[0173] The TCI state (e.g., joint / DL TCI state) may be indicated / configured based on the dl-OrJoint-TCIStateList in the PDSCH-config. The dl-OrJoint-TCIStateList may i) provide a list of up to 128 TCI states (explicitlist→dl-OrJointTCI-StateToAddModList) or ii) indicate the serving cell and (DL / UL) BWP where the TCI state list (dl-OrJointTCI-StateToAddModList) is defined (unifiedTCI-StateRef→ServingCellAndBWP-Id). The TCI state (e.g., joint / DL TCI state) may provide a reference RS for quasi-co-location of DM-RS for PDSCH, DM-RS for PDCCH, and CSI-RS. The TCI state (e.g., joint TCI state) may provide a reference RS for determining uplink (UL) Tx spatial filters for PUSCH based on dynamic grant, PUSCH based on configured grant, and PUCCH resources and SRS.

[0174] The UL TCI state can be indicated / configured via ul-TCI-StateList in BWPUplinkDedicated. ul-TCI-StateList can i) provide a list of up to 64 UL TCI states (explicitlist→ul-TCI-ToAddModList), or ii) indicate the serving cell and UL BWP, where the UL TCI state applicable to the UL BWP is defined (unifiedTCI-StateRef→ServingCellAndBWP-Id).

[0175] The Rx / Tx beam of the DL / UL channel / RS that is not a common beam target may be configured as follows: The TCI state of the unified TCI framework may be configured for each channel / RS based on RRC and MAC CE signaling.

[0176] Until Rel-17, standardization was performed only when M / N, which is the number of DL / UL common beams to be supported in the unified TCI framework (the number of DL / UL TCI states), was M / N = 1. In other words, the unified TCI framework does not support M-TRP. Specifically, in a serving cell where two CORESET pool indexes are set (the value of coresetPoolIndex is more than one), unifiedTCI-StateType is not set.

[0177] Here, M / N represents the number of DL common beams (M) and / or the number of UL common beams (N). For example, M / N = 1 may mean that the number of DL common beams (DL TCI state) and / or the number of UL common beams (UL TCI state) is 1. For example, M / N = 1 may mean that the number of DL and UL common beams (joint TCI state) is 1.

[0178] If M / N > 1 is supported in Rel-18, two or more TCI states can have a connection relationship with the source / target TRP.

[0179] Specifically, in the M-TRP operation based on M-DCI, two or more TCI states corresponding to M / N > 1 may have a connection relationship with the CORESET pool index. As described above, the two TA values ​​of multiple TRPs may be configured / indicated in the same manner as the existing standard through higher layer signaling (eg, MAC CE).

[0180] In the case of a UE (UE after Rel-17) supporting unified TCI applied to FR 2, multiple TA values ​​may be connected / corresponded to two or more TCI states corresponding to M / N>1. For example, when M / N=2 or / and N=2, the first configured / indicated (first / lowest) TCI state may correspond to TA1 (e.g., TAG 1 or TA1 of TAG 1), and the second configured / indicated (second / second lowest) TCI state may correspond to TA2 (e.g., TAG 2 or TA2 of TAG 2).

[0181] Specifically, a specific payload may be included / added / defined in the MAC CE to configure / allocate / activate a TA value corresponding to each of two or more TCI states of M / N> 1. For example, a payload for allocating a target TCI state (group) for each TA value (e.g., TA1 and TA2) may be present in a MAC CE message for configuring two TA values.

[0182] The protocol for multiple TA values ​​is shown in Table 10 below.

[0183]

Table 10

[0184]

[0185]

[0186]

[0187] The operations / methods / terms according to the embodiments of the present disclosure described below may be based on Table 10. For example, the operations / methods / terms according to the embodiments of the present disclosure described below may be interpreted / changed / applied based on Table 10.

[0188] For example, multiple TA values ​​may mean multiple timing advance groups (TAGs) or multiple TAG IDs. One TA value may mean one TAG (TAG ID).

[0189] For example, multiple TA values ​​can represent TA values ​​corresponding to multiple TAGs (multiple TAG IDs). One TA value can represent the TA value of one TAG (TAG ID) (in Table 1).

[0190] In a TCI state configuration (TCI state pool) of a unified TCI, two TRP-specific TA values ​​(e.g., two TAGs or TAs corresponding to two TAGs) may be connected / correspond to a specific TCI state (group). When two TA values ​​are connected / correspond to two TCI states with M / N>1, the UE may perform UL transmission using the TRP-specific TA value connected to each TCI state in UL transmission using each TCI state. For example, the timing of UL transmission based on a first TCI state may be determined based on a TA associated with the first TCI state (e.g., a first TAG or a first TA of a first TAG), and the timing of UL transmission based on a second TCI state may be determined based on a TA associated with the second TCI state (e.g., a second TAG or a second TA of a second TAG).

[0191] However, even if unified TCI is supported by the UE, the reference RS of UL spatialRelationInfo or / and UL TCI cannot be applied to FR 1 (frequency range 1). For example, the UE capability of spatialRelationInfo of the UE may be defined as shown in Table 11 below.

[0192]

Table 11

[0193]

[0194] Referring to Table 11, FR1 does not support the spatial relationship of PUCCH and SRS (eg, UE operation in FR1).

[0195] Therefore, for FR1, when the base station configures / indicates two TA values ​​using the unified TCI framework, there may be ambiguity in UE operation.

[0196] The present disclosure describes i) a method for a BS to send multi-TA configuration / indication of a specific CC / BWP for uplink of a UE (especially FR1) (as described above), and ii) a method for a UE to request / acquire multi-TA, and proposes subsequent UE operations.

[0197] In the present disclosure, “ / ” may be interpreted as “and”, “or” or “and / or” based on the context.

[0198] Proposal 1

[0199] The UE may receive a unified TCI configuration corresponding to M / N > 1 (in FR1 operation). For example, the UE may receive configuration information of two or more unified TCI states from a base station (BS). The two or more unified TCI states may include at least one of: i) two or more joint TCI states, ii) two or more DL TCI states, and / or iii) two or more UL TCI states.

[0200] When two CORESET pool indexes within a CC / BWP are configured by the base station for the UE to perform M-TRP operation based on M-DCI, UL-related TCI states (e.g., DL / UL joint TCI states and / or DL / UL separate TCI states) connected to / corresponding to each of the two CORESET pool indexes may be configured / indicated. For example, the UE may receive configuration information of a plurality of CORESETs from the base station. A CORESET based on two CORESET pool indexes may be configured based on the configuration information. The UE may receive information indicating two UL-related TCI states (e.g., two joint TCI states or two UL TCI states) connected to / corresponding to / associated with the two CORESET pool indexes from the base station. Information indicating two UL-related TCI states may be received based on at least one of a DCI, a MAC CE, or an RRC message.

[0201] The two TRP-specific TA values ​​may be connected / correspond to two UL-related TCI states. In addition, the power control parameter set configured to each of the two UL-related TCI states may be used as the power control parameter set for each target TRP in an M-TRP UL transmission (e.g., M-TRP PUSCH / PUCCH repetition) (for S-DCI-based M-TRP operation).

[0202] Specifically, since UL spatialRelationInfo (UL TCI) information is not applicable in FR1, the TCI status for configuring / indicating two TA / PC parameter sets may be configured / used as follows.

[0203] The reference RS corresponding to QCL Type-D or / and UL spatialRelationInfo (UL TCI) may not be configured to both TCI states. For example, in each TCI state, the reference signal field (in QCL-Info) may not exist. For example, the UE may not expect to configure the reference signal field (in QCL-Info) in each TCI state.

[0204] If the reference RS corresponding to QCL type-D or / and UL spatialRelationInfo (UL TCI) is configured as two TCI states, the UE can skip / ignore / override the reference RS and perform UL transmission only using TA / PC information corresponding to each target TRP (e.g., first / second TCI or CORESET pool index 0 / 1).

[0205] As described above, the UE may determine TA / PC information corresponding to each target TRP (e.g., each of the two target TRPs) based on two TCI states. The UE may perform UL transmission for each target TRP based on the TA information / PC information. The UL transmission timing (e.g., uplink frame) of each target TRP may be determined based on the TA information (e.g., TAG or TA value of the TAG). The UL transmission power of each target TRP may be determined based on the PC information (e.g., one or more PC parameters).

[0206] The TCI state can be configured / indicated via RRC, MAC CE or / and DCI in the same manner as the existing Rel-17 operation. If the TCI state is indicated via DCI, the base station may use i) DL ( / UL) grant DCI, or ii) DL ( / UL) grant DCI without data scheduling. The base station may dynamically indicate the TCI state of each target TRP through the TCI field of the DCI. For example, if TCI indication via DCI as described above is performed in a CORESET with a specific CORESET pool index, the UE may use the corresponding TCI to receive / send a DL / UL channel / RS connected / corresponding to the CORESET pool index.

[0207] In this case, according to the Rel-17 standard, in the TCI indication via the grant DCI without data scheduling, the UE can send an Ack ( / Nack) after receiving the DCI (via PUCCH and / or PUSCH) (e.g., using an ACK / NACK mechanism similar to the SPS PDSCH release with both type 1 and type 2 HARQ-ACK codebooks).

[0208] If the above operation is performed in FR1 (ie, via TCI indication of grant DCI without data scheduling), the UE may skip Ack ( / Nack) transmission. Skipping Ack ( / Nack) transmission considers the following technical issues.

[0209] In Rel-17, the base station checks whether the UE has received the TCI state including beam information (e.g., reference RS) well for the UE's reception / transmission indicated via DCI. Thereafter, the base station can use the Tx / Rx beam of the base station corresponding to the indicated TCI information in subsequent DL / UL transmission / reception. On the other hand, the TCI state indication that does not include the UE's Tx / Rx beam information allows the base station to configure / indicate two TAs (e.g., two TAGs or two TAs corresponding to two TAGs) and two PCs (e.g., two parameter sets). Whether the TA / PC indication is successfully sent can be determined by the UE's subsequent transmission. Specifically, after the base station receives the UE's subsequent UL transmission, it can be determined whether the TA / PC indication of the previous DCI has been successfully sent to the UE, and the UE has performed UL transmission based on the indication.

[0210] Accordingly, the UE may skip sending the Ack ( / Nack) for the TCI status indication in FR1 (the TCI status indication does not include the UE's Tx / Rx beam information).

[0211] In addition, since Rx / Tx beam indication is performed dynamically in the existing Rel-17 unified TCI framework, concepts such as beam application time (BAT) have been defined to determine at which time the UE should perform the change of the corresponding Rx / Tx beam starting from the time of DCI reception. For example, the beamAppTime parameter can be set based on PDSCH-config. The beamAppTime parameter indicates the first time slot to which the unified TCI indicated by DCI is applied. The beamAppTime parameter can indicate the number of symbols (Y) (e.g., n1, n2, n4, n7, n14, n28, n42, n56, n70, n84, n98, n112, n224, n336). The first time slot can be a time slot of at least Y symbols after the last acknowledgment (Ack) symbol of the joint or separate DL / UL beam indication.

[0212] As described above, when the unified TCI framework is used to configure / indicate TA / PC, BAT can be used as a setting value for the time when ULTA / PC should be applied. Alternatively / and, since the TCI state is independent of the beam application, the UE may not expect to configure BAT or may expect the BAT value to be set to 0. As a specific example, it can be assumed that the unified TCI state of FR1 is indicated by DCI (e.g., DL granted DCI, UL granted DCI, DCI without DL grant, or DCI without UL grant). Since the indicated unified TCI state is independent of the beam application, the transmission of HARQ-ACK information of the DCI can be skipped. Since the transmission of HARQ-ACK information is skipped, the time (e.g., symbol, time slot, subframe, or frame) at which the indicated unified TCI state is applied cannot be determined by the beamAppTime parameter. In this case, even if the beamAppTime parameter is configured, the UE may not use the beamAppTime parameter. In other words, the UE may ignore the beamAppTime parameter. For example, the time (e.g., symbol, time slot, subframe, or frame) at which the indicated unified TCI state is applied can be determined without applying the beamAppTime parameter. For example, the time of the unified TCI state indicated by the application can be determined regardless of the beamAppTime parameter.

[0213] Proposal 2

[0214] For two TRP-specific TA values ​​or / and two TRP-specific PC parameter sets, the base station can configure separate parameters. Specifically, (in FR1 operation) two TRP-specific TA values ​​or / and two TRP-specific PC parameter sets can be configured / connected / correspond to separately configured parameters.

[0215] The separate parameters may include TRP specific TA values. In this case, the parameters may be configured as i) or ii) below.

[0216] i) A single parameter including both the first TA value and the second TA value may be configured.

[0217] ii) Two parameters may be configured. The first parameter may include a first TA value, and the second parameter may include a second TA value.

[0218] The separate parameters may include a TRP specific PC parameter set. In this case, the parameters may be configured as per i) or ii) below.

[0219] i) A single parameter including a first PC parameter set and a second PC parameter set may be configured.

[0220] ii) Two parameters may be configured. The first parameter may include a first PC parameter set, and the second parameter may include a second PC parameter set.

[0221] In i), a specific CORESET pool index may be connected to / correspond to a specific TA value or / and a specific PC parameter set in a single parameter. For example, CORESET pool index 0 may be connected to a first TA value / first PC parameter set, and CORESET pool index 1 may be connected to a second TA value / second PC parameter set.

[0222] In ii), a specific CORESET pool index may be connected to / correspond to a specific parameter of the two parameters. For example, CORESET pool index 0 may be connected to the first parameter, and CORESET pool index 1 may be connected to the second parameter.

[0223] As described above, the first TA value / first PC parameter set and the second TA value / second PC parameter set may be configured as specific parameters and may be connected to a specific CORESET pool index. When transmitting UL associated with / corresponding to a specific CORESET pool index, the UE may perform UL transmission by utilizing a TRP-specific TA value or / and a TRP-specific PC parameter set connected to the corresponding CORESET pool index.

[0224] For more flexible configuration, the TRP-specific TA value or / and two TRP-specific PC parameter sets corresponding to the above two TA values ​​may be configured / connected / mapped / updated in each CORESET (group) configuration. Therefore, the UE is able to perform UL transmission by utilizing the TRP-specific TA value or / and TRP-specific PC parameter set configured for the corresponding CORESET when performing UL transmission related to a specific CORESET (group).

[0225] In the above embodiment, the expression “(a specific parameter and another parameter) may be connected / correspond” may mean that the specific parameter and another parameter can be associated via RRC / MAC CE / DCI signaling.

[0226] Unless the embodiments of Proposal 1 and Proposal 2 are mutually exclusive, the embodiments of Proposal 1 and the embodiments of Proposal 2 can be combined and applied to UE / BS operations. For example, the operation of configuring a unified TCI (Proposal 1) and the operation of configuring separate parameters (Proposal 2) cannot be combined, but other embodiments can be combined and applied. Specifically, the embodiments of Proposal 1 and the embodiments of Proposal 2 related to two TRP-specific TA values ​​(two TRP-specific PC parameter sets) can be combined and applied to UE / BS operations.

[0227] Multi-TA acquisition

[0228] In order to configure the above-mentioned multiple TA values, it is necessary to determine how the BS will request / acquire multiple TA values. Hereinafter, a method for BS / UE to acquire multiple TA values ​​and a terminal operation are proposed. Specifically, Proposal 3 below proposes a method for UE to perform two TA acquisition without RACH enhancement and a method for configuring TA in the BS, and Proposal 4 proposes a method for UE to perform two TA acquisition through RACH enhancement and a method for configuring TA in the BS.

[0229] Hereinafter, a first TA or a second TA connected / corresponding to a specific CORESET pool index may mean a first TA or / and a second TA connected / corresponding to a first TCI state or / and a second TCI state (for common beam operation in a unified TCI framework).

[0230] Hereinafter, the first TA and the second TA may mean the first / second TA value managed for configuring two TRP specific TA values ​​within a specific TAG (i.e., one TAG). Alternatively, the first TA and the second TA may mean the first TA value and the second TA value managed corresponding to different TAGs (first TAG and second TAG) for the same CC (set).

[0231] Proposal 3

[0232] Hereinafter, a method of performing two-TA acquisition and a method of configuring a TA in a BS without RACH boosting will be described.

[0233] Proposal 3-1

[0234] The UE may perform RACH transmission using a single (and / or primary / first) TA in a RACH transmission process including initial access (e.g., RACH in PDCCH order, RACH transmitted when a TA timer expires, etc.). The BS may measure the first / second TA by receiving a subsequent SRS of the UE. That is, a method of configuring / indicating an implicit / explicit connection / correspondence relationship between a specific SRS resource (set) and a specific CORESET pool index is proposed.

[0235] For the aperiodic SRS resource (set) corresponding to dynamic scheduling, the following operations may be performed: the UE may receive an SRS triggering DCI in a CORESET with a specific CORESET pool index. At this time, the aperiodic SRS resource (set) sent by the UE may be connected / corresponding to the specific CORESET pool index.

[0236] For the periodic / semi-persistent SRS resource(s) sent by the UE via RRC / MAC CE signaling, the following operations may be performed. The BS may (explicitly) configure / connect / correspond to the associated CORESET pool index for a specific SRS resource(s). In this way, the UE / BS may know which CORESET pool index a specific SRS resource(s) is connected / corresponds to.

[0237] Therefore, the BS / UE can understand that the specific P / SP / AP SRS resource (set) sent by the UE is associated / corresponds to a specific CORESET pool index. In other words, the BS can identify the CORESET pool index associated / corresponds to the specific P / SP / AP SRS resource (set) sent by the UE. The BS can measure the first TA or / and the second TA through the SRS sent by the UE.

[0238] According to an embodiment, the first ( / primary) TA may be acquired through an existing RACH procedure. The second TA may be acquired through an SRS associated with CORESET pool index 1 as described above.

[0239] Proposal 3-2

[0240] The BS may measure the first TA or / and the second TA connected / corresponding to a specific CORESET pool index through Proposal 3-1. The BS may configure / indicate a TRP specific TA value (ie, the first / second TA) by utilizing the enhanced RAR MAC CE format or / and the enhanced TA command MAC CE.

[0241] As an example, the BS may configure the target CORESET pool index in the enhanced MAC CE format. Thus, the TA value associated with / corresponding to the corresponding CORESET pool index may be configured / indicated. As a specific example, the enhanced MAC CE format may include a field indicating the target CORESET pool index.

[0242] As an example, the BS may configure the first / second TCI corresponding to M / N>1 as a target for TRP-specific common beam operation in the enhanced MAC CE format. In this way, the TA value associated / corresponding to the first / second TCI may be configured / indicated. As a specific example, the enhanced MAC CE format may include a field indicating a target TCI (e.g., a first TCI state or a second TCI state).

[0243] As an example, the BS may configure a specific joint and / or separate UL TCI state index as a target in the enhanced MAC CE format. In this way, the TA value to be applied to the corresponding TCI state may be configured / indicated. Specifically, the TA value in the MAC CE format for configuring / indicating the second TA value may be configured / specified / indicated to have a TA granularity or / and value range that is different from the first TA value in the same MAC CE format. This is because in M-TRP operation, the difference in UL TA values ​​for different TRPs may differ from the DL timing reference by the CP length or more. The granularity of the second TA value (when the same number of bits as the first TA value is used) can be represented by a step size that is slightly larger than the first TA value. The value range of the second TA value (when the same number of bits as the first TA value is used) can be represented by a value range that is slightly larger than the first TA value.

[0244] As described above, the BS may configure / indicate the first / second TA for a specific target CORESET pool index / target common TCI / target TCI state. In the transmission of the UL channel / RS (especially the SRS in Proposal 3-1) associated with the target CORESET pool index / target common TCI / target TCI state, the BS may perform uplink transmission by applying the configured / indicated first / second TA value.

[0245] The BS can perform update / activation of the TRP-specific TA value based on measuring the UE's TRP-specific SRS transmission based on Proposal 3-1 after configuring / indicating the TRP-specific TA through Proposal 3-2.

[0246] Proposal 4

[0247] Hereinafter, a method of performing two TA acquisition and a method of configuring a TA in a BS without RACH boosting will be described.

[0248] Proposal 4-1

[0249] A method may be considered to support TRP-specific RACH transmission for TRP-specific TA measurements.

[0250] The BS may perform grouping on the SSBs (SS / PBCH blocks) used by the UE for RACH transmission. The BS may associate / correspond a specific SSB group with a specific CORESET pool index. For example, SSBs corresponding to SSB indexes 0 to 31 may be connected to / correspond to CORESET pool index 0, and SSBs corresponding to SSB indexes 32 to 64 may be connected to / correspond to CORESET pool index 1. Here, the SSB index may be an SS / PBCH index of an SS / PBCH block.

[0251] Based on the grouping, the BS may configure / instruct to utilize a specific SSB index when configuring / instructing to send a RACH (of PDCCH order) to the UE. RACH may mean a random access preamble. For example, the BS may send a DCI (e.g., DCI format 1_0) containing information related to the PDCCH order to the UE. The random access procedure is initiated by the PDCCH order. The UE sends a random access preamble to the BS. Information related to the PDCCH order may include an SS / PBCH index. The SS / PBCH index may be connected to / associated with a specific CORESET pool index, and a random access preamble may be sent based on the SS / PBCH index.

[0252] By having the UE send a RACH corresponding to an SSB (based on a specific SSB index), the BS can measure a TRP specific TA associated / corresponding to each CORESET pool index by utilizing the RACH.

[0253] According to an embodiment, multiple RACH transmissions may be indicated / scheduled to the UE via a single PDCCH (e.g., a single DCI) so that when the BS indicates (PDCCH-sequential) RACH transmission, the UE may send a RACH associated with each CORESET pool index. As a specific example, a single DCI may include information related to the PDCCH sequence. At this time, the information related to the PDCCH sequence may include two SS / PBCH indexes. The UE may send two random access preambles to the BS based on the two SS / PBCH indexes. In this way, overhead / delay may be reduced through a single PDCCH transmission, and the UE may be instructed to send all RACHs sent to each TRP. The BS may perform TA measurements for each TRP at a time.

[0254] According to an embodiment, the connection / correspondence between a specific SSB group and a specific CORESET pool index can be configured / defined / specified by connecting / corresponding to a specific CORESET pool index and a PRACH preamble index / RACH timing / PRACH mask index. Specifically, a DCI related to a PDCCH order (e.g., DCI format 1_0) may include a random access preamble index, an SS / PBCH index, and a PRACH mask index. When the value of the random access preamble index is not zero, the PRACH mask index indicates a RACH timing associated with the SS / PBCH indicated by the SS / PBCH index. A specific CORESET pool index may be configured to be connected / corresponding to at least one of a PRACH preamble index, a PRACH mask index, or a RACH timing.

[0255] In addition, if a connection / correspondence relationship between a specific SSB group and a specific CORESET pool index is defined / configured, the following operations may be performed. The BS may schedule RACH transmission of the UE according to the PDCCH order through the CORESET with the specific CORSET pool index. At this time, the UE may perform RACH transmission corresponding to the SSB connected / corresponding to the specific CORESET pool index (or may force such RACH transmission) (even if there is no SSB index indication in the corresponding PDCCH). In other words, the UE may perform RACH transmission based on the CORESET pool index of the CORESET for which the DCI (related to the PDCCH order) is received.

[0256] The RACH transmission in the above proposal 4-1 cannot be used for RACH transmission at the time of initial access.

[0257] Even if the UE performs TRP-specific RACH transmission as described above, since the UE performs all operations based on a specific SSB in the RA process, the TA value is not changed during UL transmission in the RA process. That is, the UE performs UL transmission by utilizing the same TA value. The RA process may include a 4-step RACH process and / or a 2-step RACH process. For example, a 4-step RACH process (e.g., contention-based RACH) may include operations of sending message 1 (preamble), receiving message 2 (RAR), sending message 3 (PUSCH), and receiving message 4 (contention resolution). For example, a 2-step RACH procedure may include operations of sending Msg A (preamble and PUSCH) and receiving Msg B (RAR).

[0258] Proposal 4-2

[0259] Hereinafter, a method for managing a TRP-specific TA timer will be described.

[0260] According to the existing TA maintenance operation, when the timer corresponding to the primary timing advance group (PTAG) expires due to timeAlignmentTimer (per TAG), the UE can release UL transmission and send RACH. This embodiment proposes a method for managing timeAlignmentTimer corresponding to the TA timer as TRP-specific.

[0261] The UE may manage up to two TA timers corresponding to CORESET pool indexes 0 and 1 or / and the first and second TA values ​​within a single TAG. Here, the two corresponding timers may be timers configured for different TAGs for different TRPs.

[0262] According to the existing operation, when the TA timer expires, the UE sends a RACH corresponding to a random SSB (e.g., an SSB based on one of the SSB indexes). On the other hand, according to this embodiment, when the TA timer associated with / corresponding to a specific CORESET pool index or / and a specific first / second TA value expires, the UE may send a RACH based on the CORESET pool index associated with / corresponding to the expired TA timer. That is, a RACH corresponding to the SSB connected with / corresponding to the corresponding CORESET pool index may be sent.

[0263] By such operation, when the TA value corresponding to the TRP expires, the UE can send a RACH for a specific TRP. The BS can measure the TA value of the UE from the corresponding TRP and configure / indicate / update the TRP-specific TA value to the UE (as in Proposal 3-2).

[0264] In addition, it can be assumed that in the existing operation, when the timer corresponding to the PTAG expires, a UL out-of-sync (OOS) operation is performed, but in the case where two TRP-specific timers corresponding to the first and second TAs are managed respectively as in the above-mentioned Proposal 4-2, one timer expires and the other timer does not expire. In this case, the UE may not need to perform all predefined UL OOS operations (e.g., not perform an RRC release operation, etc.). If both timers expire, all predefined UL OOS operations may need to be performed.

[0265] Proposal 4-3

[0266] Hereinafter, a method for a BS to send a RAR corresponding to a TRP-specific RACH transmission will be described.

[0267] According to the above proposals 4-1 or / and 4-2, the specific RACH transmission of the UE corresponds to a specific SSB. According to the correspondence between the SSB index and the CORESET pool index, the specific RACH transmission and the specific CORESET pool index naturally have a corresponding relationship. A method is proposed in which the BS sends the RAR as TRP-specific for the TRP-specific RACH transmission of the UE.

[0268] The BS may receive a specific RACH corresponding to a specific CORESET pool index, and the BS may send a RAR of the corresponding RACH to the UE based on a portion of the CORESETs in the CORESET with the specific CORESET pool index. For example, the portion of the CORESET may be the CORESET with the lowest index in the CORESET configured with the corresponding CORESET pool index.

[0269] In the existing standard operation, the UE may receive the configuration of the type 1-PDCCH common search space (CSS) set for receiving the RAR from the BS. Specifically, the type 1-PDCCH CSS set may be configured based on the ra-searchspace of the PDCCH-ConfigCommon IE. For example, the RAR may be received based on the PDCCH candidates in the monitoring search space set (SS set).

[0270] Proposal 4-3 proposes a method that enables the UE to receive TRP-specific RARs through a separate UE-specific search space (USS) set in addition to the Type 1-PDCCH CSS set.

[0271] According to an embodiment, a method of connecting / configuring a CORESET to receive separate USS sets and TRP-specific RARs may be considered. Each USS set may be connected / corresponding to a CORESET with a different CORESET pool index.

[0272] According to an embodiment, the BS may transmit a RAR for a RACH for first / primary (and / or corresponding to CORESET pool index 0) TA value measurement through an existing type-1-PDCCH CSS set. According to an embodiment, the BS may transmit a RAR for a RACH for first / primary (and / or corresponding to CORESET pool index 1) TA value measurement through an existing type-1-PDCCH CSS set. When a USS set is used for TRP-specific RAR reception as described above, a separate RNTI for TRP-specific RAR reception may be configured in the UE.

[0273] According to an embodiment, the UE may receive a TRP-specific RAR based on the configuration of multiple CSS sets (eg, configuration of two CSS sets considering two TRPs). Each USS set may be connected / corresponding to a CORESET with a different CORESET pool index.

[0274] The MAC CE format sent via such a TRP-specific RAR may include all configurations / indications of multiple TA values ​​within a specific CC / BWP, as described in Proposal 3-2 above. Alternatively, the MAC CE format sent via a TRP-specific RAR may only include configurations / indications of TA values ​​associated / corresponding to the CORESET pool index through which the RAR is sent.

[0275] For the TA value associated / corresponding to a specific CORESET pool index indicated by the MAC CE format, the UE may specify / define the DL timing reference based on the reception of the RAR (UL grant DCI) sent in the CORESET with the corresponding CORESET pool index. The UE may apply the TA value indicated from the corresponding DL timing reference. In the case of M-TRP in a non-ideal backhaul scenario based on M-DCI (e.g., a scenario where there is no coordination between TRPs), the DL timing references between TRPs may be significantly different. In this case, the BS may indicate to the UE the appropriate TRP-specific TA value for each DL timing reference of each TRP through the above operations.

[0276] The embodiments of Proposal 3 and Proposal 4 may be combined with the embodiments of Proposal 1 and Proposal 2 and applied to BS / UE operation as long as these embodiments are not mutually exclusive. For example, performing two-TA acquisition operation without RACH enhancement (Proposal 3) and performing two-TA acquisition operation with RACH enhancement (Proposal 4) may not be combined, but other embodiments may be combined and applied. Specifically, the embodiment of Proposal 3 and the embodiment of Proposal 4 associated with two TRP-specific TA values ​​may be combined and applied to UE / BS operation.

[0277] The signaling process based on the above embodiment is described in detail below.

[0278] An example of UE (or BS) operation based on at least one of the above-described embodiments (eg, at least one of Proposal 1 and Proposal 2) is as follows.

[0279] 1) The UE receives (sends) unified TCI-related configuration information and / or TRP-specific TA / PC-related configuration information.

[0280] The configuration information may be based on the contents of proposals 1 to 4.

[0281] The UE transmits (receives) SRS or / and RACH based on Proposal 3 or Proposal 4 according to the BS configuration.

[0282] The BS may receive SRS or / and RACH and measure a TRP-specific TA, and then configure / indicate a TRP-specific TA value to the UE through (RAR or / and TA command) MAC CE based on Proposal 3 or Proposal 4.

[0283] 2) The UE receives (sends) a message scheduling a TRP-specific UL transmission.

[0284] The message may be based on at least one of the first PDCCH (first DCI) and / or the second PDCCH (first DCI).

[0285] The message may be related to a specific CORESET pool index or / and a specific CORESET (group).

[0286] 3) The UE sends (receives) UL channels / RS based on this message using TRP-specific TA / PC-related configuration information.

[0287] The UL channel / RS may be based on at least one of SRS, PUSCH, PUCCH, or a random access preamble, and the transmission of the UL channel / RS may be performed based on the contents of Proposals 1 to 4.

[0288] 4) The UE may manage the TRP-specific TA timer based on the content of Proposal 4.

[0289] The UE / BS operations are merely examples, and each operation (and step) is not necessarily essential. For example, operations related to uplink transmission using a TRP-specific TA / PC of a UE according to the above embodiment may be omitted or added based on the method implemented by the UE / BS.

[0290] From an implementation perspective, the operations of the UE / BS according to the above-described embodiments (e.g., operations related to uplink transmission using a TRP-specific TA / PC of the UE based on at least one of Proposals 1 to 4) can be performed by the following description. Figure 5 equipment (for example, Figure 5 The processors 110 and 210 are used for processing.

[0291] In addition, the operations of the UE / BS according to the above-described embodiments (e.g., operations related to uplink transmission using a TRP-specific TA / PC of the UE based on at least one of Proposals 1 to 4) can be stored in a memory (e.g., Figure 5 140 and 240) for running at least one processor (e.g., Figure 5 processors 110 and 210).

[0292] Below, reference Figure 3 and Figure 4 The above embodiments are described in detail from the perspective of UE / BS operation. The methods described below are distinguished only for the convenience of explanation. Therefore, it is obvious that part of the configuration of any method can be replaced or combined with part of the configuration of another method.

[0293] Figure 3 is a flowchart illustrating a method performed by a UE in a wireless communication system according to an embodiment of the present disclosure.

[0294] See also Figure 3According to an embodiment of the present disclosure, a method performed by a UE in a wireless communication system includes a configuration information receiving step (S310), a DCI receiving step (S320), a random access preamble sending step (S330), and a random access response receiving step (S340).

[0295] In S310 , the UE receives configuration information related to a plurality of control resource sets (CORESETs) from the BS.

[0296] Based on the configuration information, a CORESET based on a first CORESET pool index and a second CORESET pool index (eg, a first CORESET and a second CORESET) may be configured. In other words, based on the configuration information, a CORESET based on two different control resource set (CORESET) pool indexes may be configured.

[0297] In S320, the UE receives downlink control information (DCI) from the BS. The DCI may include information related to a physical downlink control channel (PDCCH) sequence.

[0298] For example, the DCI may be DCI format 1_0. The information (field) related to the PDCCH order may include at least one of i) a random access preamble index and ii) an SS / PBCH index. The SS / PBCH index field may indicate an SS / PBCH (or SSB index) used to determine a RACH timing for PRACH transmission (ie, random access preamble transmission).

[0299] According to an embodiment, the information related to the PDCCH sequence may include a synchronization signal / physical broadcast channel block index (SSB index). Here, the SSB index may be an SS / PBCH index of an SS / PBCH block. As an example, the information related to the PDCCH sequence may include one or more SSB indexes.

[0300] The random access procedure may be initiated by the PDCCH sequence. For example, the random access procedure may be initiated by the PDCCH sequence to establish a timing advance for the timing advance group. That is, the DCI related to the PDCCH sequence may be sent from the BS to the UE.

[0301] The type 1 random access procedure may include sending a random access preamble (Msg1) on a physical random access channel (PRACH), receiving a random access response (RAR) (Msg2), sending a PUSCH (Msg3) scheduled by a UL grant of the RAR, and sending a PDSCH (Msg4) for contention resolution. When the random access procedure is a contention-free random access (CFRA), the Msg3 transmission and Msg4 reception operations are omitted.

[0302] The type 2 random access procedure may include sending a random access preamble and PUSCH (MsgA) and receiving a RAR (MsgB).

[0303] In S330, the UE sends a random access preamble to the BS. The random access preamble may be based on Msg1 of a type 1 random access procedure or MsgA of a type 2 random access procedure.

[0304] According to an embodiment, the random access preamble may be transmitted based on the SSB index. This embodiment may be based on Proposal 4. The SSB index may mean the SSB index indicated by DCI (eg, DCI format 1_0) containing information related to the PDCCH order.

[0305] Specifically, the RACH opportunity for sending a random access preamble may be determined based on the SSB index. A RACH opportunity (or PRACH opportunity) may mean an area in the time-frequency domain for sending a random access preamble. SSBs and RACH opportunities (ROs) based on SSB indexes have a mapping relationship. As an example, the upper layer parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB may indicate i) the number of SSBs mapped to one RACH opportunity (RO) and ii) the preamble index mapped to one SSB.

[0306] The SSB index may be associated with the first CORESET pool index or the second CORESET pool index. The SSB index may be the first SSB index or the second SSB index.

[0307] According to an embodiment, a plurality of random access preambles associated with a plurality of TRPs (CORESET pool indices) may be transmitted based on a DCI associated with a PDCCH order.

[0308] As an example, the SSB index may be based on one or more SSB indexes. Based on one or more SSB indexes including i) a first SSB index associated with a first CORESET pool index and ii) a second SSB index associated with a second CORESET pool index, a first random access preamble may be sent based on the first SSB index, and a second random access preamble may be sent based on the second SSB index. Based on the sending of the first / second random access preamble, the UE may receive a first / second random access response from the BS.

[0309] In S340, the UE receives a random access response (RAR) from the BS. The random access response (RAR) may include a timing advance command. The RAR may be based on Msg1 of a type 1 random access procedure or MsgA of a type 2 random access procedure.

[0310] For example, the RAR may be received based on the PDCCH and the PDSCH. The UE detects the DCI (e.g., DCI format 1_0) sent via the PDCCH in a window configured for the random access procedure. The above window may be configured in time slots (e.g., one or more time slots) by the upper layer parameter ra-ResponseWindow. The UE receives a transport block corresponding to the PDSCH searched by the DCI in the window. The RAR may be based on the transport block. The above RAR may refer to Figure 1 MAC RAR.

[0311] The detection (reception) of DCI may be based on monitoring of PDCCH candidates. According to an embodiment, RAR may be received based on monitoring of PDCCH candidates in a search space set (SS set). This embodiment may be based on Proposal 4-3.

[0312] The SS set may be based on a common search space set (CSS set) or a UE-specific search space set (USS set). For example, the CSS set may be a type 1-PDCCH CSS set configured by the upper layer parameter ra-SearchSpace.

[0313] The SS set may be separately configured to receive a RAR corresponding to each TRP (i.e., each CORESET pool index). As an example, the SSB set may be associated with one or more CORESETs based on a first CORESET pool index or a second CORESET pool index. The SS set may be i) a USS set (or CSS set) associated with one or more first CORESETs having a first CORESET pool index, or ii) a USS set (or CSS set) associated with one or more second CORESETs having a second CORESET pool index.

[0314] The method may further include an SSB receiving step. Specifically, the UE receives a synchronization signal / physical broadcast channel block (SS / PBCH block, SSB) from the BS based on a plurality of SSB indexes. The SSB receiving step may be performed before S310 to S320.

[0315] Multiple SSB indexes may be classified into groups corresponding to multiple TRPs (multiple CORESET pool indexes). This embodiment may be based on Proposal 4-1.

[0316] The plurality of SSB indexes may include an SSB index (eg, a first SSB index) belonging to a first group associated with a first CORESET pool index and an SSB index (eg, a second SSB index) belonging to a second group associated with a second CORESET pool index.

[0317] According to an embodiment, the plurality of SSB indexes may include i) a first SSB index associated with a first CORESET pool index and ii) a second SSB index associated with a second CORESET pool index.

[0318] The SSB index may be i) one of the first SSB indices or ii) one of the second SSB indices. The SSB index may mean an SSB index indicated by a DCI (eg, DCI format 1_0) containing information related to a PDCCH order.

[0319] The grouping of multiple SSB indexes may be performed in ascending or descending order of the index value (ie, the value of the SSB index).

[0320] As an example, grouping may be performed in ascending order of the SSB index.Based on a plurality of SSB indexes including SSB index 0 to SSB index 63: a first SSB index may include SSB index 0 to SSB index 31, and a second SSB index may include SSB index 32 to SSB index 63.

[0321] As described above, when there are two CORESET pool indexes corresponding to the TRP, the first group may be SSB indexes 0 to 31 (or SSB indexes 32 to 63), and the second group may be SSB indexes 32 to 63 (or SSB indexes 0 to 31).

[0322] Grouping of multiple SSB indexes may be performed regardless of the order of index values ​​(ie, values ​​of the SSB indexes).

[0323] As an example, when there are two CORESET pool indexes corresponding to TRPs, the first group may include even SSB indexes (or SSB indexes 0, 2, 4 to 62), and the second group may include odd SSB indexes (or SSB indexes 1, 3, 5 to 63). Conversely, the first group may contain odd SSB indexes, and the second group may contain even SSB indexes.

[0324] According to an embodiment, the timing advance command indicates an index associated with the timing adjustment (see Figure 1 , Table 4 and Table 5). The index related to the timing adjustment may mean the index value T of Table 4 and Table 5. A . N is used to calculate the timing advance (TA) TA It may be indicated based on an index associated with the timing adjustment.

[0325] TA can refer to Table 1 . The TA may be a TRP-specific TA (e.g., a first TA or a second TA). Specifically, the TA may be associated with a first timing advance group (TAG) or a second timing advance group (TAG). The first TAG (or first TAG ID) may be associated with a first CORESET pool index, and the second TAG (or second TAG ID) may be associated with a second CORESET pool index.

[0326] According to an embodiment, the time alignment timer associated with the TA may be a first time alignment timer associated with the first TAG or a second time alignment timer associated with the second TAG. This embodiment may be based on Proposal 4-2.

[0327] When the time alignment timer is not running, the UE does not perform any uplink transmission except sending the random access preamble (Msg1 and MsgA).

[0328] The first TAG and / or the second TAG may be associated with a primary timing advance group (PTAG). As an example, the first TAG (or the second TAG) may be a PTAG, and the second TAG (or the first TAG) may be a secondary timing advance group (STAG). As an example, the first TAG may be a first PTAG, and the second TAG may be a second PTAG.

[0329] According to the existing mode, when the TA alignment timer corresponding to the PTAG expires, the UL out-of-sync (OOS) operation is performed. However, if at least one of the multiple TA alignment timers has not expired, the operation may not be necessary. Therefore, when all TA alignment timers corresponding to the multiple TRPs expire, the UL OOS operation can be performed in a limited manner.

[0330] As an example, based on the first time alignment timer and / or the second time alignment timer being associated with a primary timing advance group (PTAG), and the first time alignment timer and the second time alignment timer expiring: the configuration for uplink transmission can be released. Thereafter, a random access preamble (e.g., a first random access preamble and / or a second random access preamble) can be sent based on a first SSB index and / or a second SSB index associated with the first time alignment timer and / or the second time alignment timer.

[0331] The configuration of the uplink transmission may include at least one of configuration of a physical uplink control channel (PUCCH), configuration of a sounding reference signal (SRS), physical uplink shared channel (PUSCH) resources, and / or a configured uplink grant.

[0332] For example, based on the expiration of a time alignment timer (e.g., a first time alignment timer or a second time alignment timer) associated with the TA: the random access preamble may be sent based on an SSB index (e.g., a first SSB index or a second SSB index) associated with the expired time alignment timer (e.g., a first time alignment timer or a second time alignment timer). Specifically, the SSB index associated with the expired time alignment timer may be associated with the first CORESET pool index or the second CORESET pool index. At this time, the random access preamble may be sent based on a random access procedure initiated by the UE (e.g., a RACH procedure initiated by the UE) rather than a PDCCH order.

[0333] The above operations based on S310 to S340 and the SSB receiving step can be performed by Figure 5 For example, the UE 200 may control one or more transceivers 230 and / or one or more memories 240 to perform operations based on steps S310 to S340 and the SSB receiving step.

[0334] Hereinafter, the embodiments described below will be described in detail in terms of the operation of the BS.

[0335] S410 to S440 and the SSB transmission steps described below correspond to Figure 3 S310 to S340 and SSB receiving steps described in the above. By considering the corresponding relationship, redundant explanations are omitted. That is, the specific description of the BS operation described below can be used with the corresponding operation. Figure 3 As an example, Figure 3 The description / example of S310 to S340 of the present invention may be additionally applied to the BS operations of S410 to S440 described below. As an example, Figure 3 The description / example of the SSB receiving step corresponding to the SSB sending step described below can be additionally applied to the SSB sending step described below.

[0336] Figure 4 is a flowchart describing a method performed by a BS in a wireless communication system according to another embodiment of the present disclosure.

[0337] See also Figure 4 According to another embodiment of the present disclosure, a method performed by a BS in a wireless communication system includes a configuration information sending step (S410), a DCI sending step (S420), a random access preamble receiving step (S430) and a random access response sending step (S440).

[0338] In S410 , the BS sends configuration information related to a plurality of control resource sets (CORESETs) to the UE.

[0339] In S420 , the BS sends downlink control information (DCI) to the UE.

[0340] In S430 , the BS receives a random access preamble from the UE.

[0341] In S440 , the BS sends a random access response (RAR) to the UE.

[0342] The method may further include an SSB transmission step. Specifically, the BS transmits a synchronization signal / physical broadcast channel block (SS / PBCH block, SSB) to the UE based on a plurality of SSB indexes. The SSB transmission step may be performed before S410 to S420.

[0343] The operations based on the above S410 to S440 and the SSB sending step can be Figure 5 For example, the BS 100 may control one or more transceivers 130 and / or one or more memories 140 to perform operations based on steps S410 to S440 and the SSB transmission step.

[0344] Reference below Figure 5 A device to which an embodiment of the present disclosure is applicable (a device that implements a method / operation according to an embodiment of the present disclosure) is described.

[0345] Figure 5 The configurations of a first device and a second device according to an embodiment of the present disclosure are illustrated.

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

[0347] The processor 110 may perform baseband-related signal processing, and includes 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 a higher layer. The physical layer processing unit 115 may process operations of a PHY layer. For example, if the first device 100 is a base station (BS) device in base station-UE communication, the physical layer processing unit 115 may perform uplink received signal processing, downlink transmitted signal processing, etc. For example, if the first device 100 is a first UE device in inter-UE communication, the physical layer processing unit 115 may perform downlink received signal processing, uplink transmitted signal processing, side link transmitted 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.

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

[0349] The processor 110 of the first device 100 may be configured to implement operations of the BS in BS-UE communication (or operations of the first UE device in inter-UE communication) in the embodiments described in the present disclosure.

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

[0351] The processor 210 may perform baseband-related signal processing and 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 a higher layer. The physical layer processing unit 215 may process operations of a PHY layer. For example, if the second device 200 is a UE device in BS-UE communication, the physical layer processing unit 215 may perform downlink received signal processing, uplink transmitted signal processing, etc. For example, if the second device 200 is a second UE device in inter-UE communication, the physical layer processing unit 215 may perform downlink received signal processing, uplink transmitted signal processing, side link received 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.

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

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

[0354] The description of the BS and the UE in BS-UE communication (or the first UE device and the second UE device in inter-UE communication) in the examples of the present disclosure can be equally applied to the operations of the first device 100 and the second device 200, and redundant description is omitted.

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

[0356] Additionally or alternatively, the wireless communication technology implemented in the devices 100 and 200 according to the present disclosure may perform communication based on the LTE-M technology. For example, the LTE-M technology may be an example of an LPWAN technology and may be referred to as various names such as enhanced machine type communication (eMTC). For example, the LTE-M technology may be implemented in 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 names.

[0357] Additionally or alternatively, in consideration of low power, the wireless communication technology implemented in the devices 100 and 200 according to the present disclosure may include at least one of ZigBee, Bluetooth, and a low power wide area network (LPWAN), and is not limited to the above names. For example, ZigBee technology may generate a PAN (Personal Area Network) related to small / low power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.

Claims

1. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: receiving configuration information related to a plurality of control resource sets (CORESETs) from a base station, wherein a CORESET based on a first control resource set (CORESET) pool index and a second control resource set (CORESET) pool index is configured based on the configuration information; receiving downlink control information (DCI) from the base station, wherein the DCI includes information related to a physical downlink control channel (PDCCH) sequence, and a random access procedure is initiated by the PDCCH sequence; sending a random access preamble to the base station; and receiving a random access response (RAR) from the base station, The information related to the PDCCH sequence includes a synchronization signal / physical broadcast channel block index (SSB index), wherein the random access preamble is sent based on the SSB index, The random access response (RAR) includes a timing advance command, and The SSB index is related to the first CORESET pool index or the second CORESET pool index.

2. The method according to claim 1, further comprising: A synchronization signal / physical broadcast channel block (SS / PBCH block, SSB) is received from the base station based on a plurality of SSB indexes.

3. The method according to claim 2, wherein: The plurality of SSB indexes include i) a first SSB index associated with the first CORESET pool index and ii) a second SSB index associated with the second CORESET pool index.

4. The method according to claim 3, wherein: The SSB index is i) one of the first SSB indices or ii) one of the second SSB indices.

5. The method according to claim 1, wherein: The RAR is received based on monitoring PDCCH candidates in a search space set (SS set).

6. The method according to claim 5, wherein: The SS set is based on a common search space set (CSS set) or a UE-specific search space set (USS set).

7. The method according to claim 6, wherein: The SSB set is associated with one or more CORESETs based on the first CORESET pool index or the second CORESET pool index.

8. The method according to claim 1, wherein: The timing advance command indicates an index associated with the timing adjustment, and N used to calculate the timing advance (TA) TA Based on the index associated with the timing adjustment is indicated.

9. The method according to claim 8, wherein: The TA is associated with a first timing advance group (TAG) or a second timing advance group (TAG), Wherein, the first TAG is associated with the first CORESET pool index, and Among them, the second TAG is related to the second CORESET pool index.

10. The method according to claim 9, wherein: The time alignment timer associated with the TA is a first time alignment timer associated with the first TAG or a second time alignment timer associated with the second TAG.

11. The method according to claim 10, wherein: Based on the first time alignment timer and / or the second time alignment timer being associated with a primary timing advance group (PTAG), and the first time alignment timer and the second time alignment timer expiring: releasing the configuration for uplink transmission.

12. The method according to claim 10, wherein: Based on the expiration of the timing alignment timer associated with the TA: Sending a random access preamble based on an SSB index associated with an expired time alignment timer, The SSB index associated with the expired time alignment timer is associated with the first CORESET pool index or the second CORESET pool index.

13. The method according to claim 1, wherein: The SSB index is based on one or more SSB indexes, and Wherein, based on the one or more SSB indexes including i) a first SSB index associated with the first CORESET pool index and ii) a second SSB index associated with the second CORESET pool index: sending a first random access preamble based on the first SSB index, and A second random access preamble is sent based on the second SSB index.

14. A user equipment (UE) operating in a wireless communication system, comprising: one or more transceivers; one or more processors; as well as one or more memories operably connected to the one or more processors and storing instructions that configure the one or more processors to perform operations based on execution by the one or more processors, The operations include: receiving configuration information related to a plurality of control resource sets (CORESETs) from a base station, wherein a CORESET based on a first control resource set (CORESET) pool index and a second control resource set (CORESET) pool index is configured based on the configuration information, receiving downlink control information (DCI) from the base station, wherein the DCI includes information related to a physical downlink control channel (PDCCH) sequence, and a random access procedure is initiated by the PDCCH sequence, sending a random access preamble to the base station, and receiving a random access response (RAR) from the base station, The information related to the PDCCH sequence includes a synchronization signal / physical broadcast channel block index (SSB index), wherein the random access preamble is sent based on the SSB index, The random access response (RAR) includes a timing advance command, and The SSB index is related to the first CORESET pool index or the second CORESET pool index.

15. A device comprising: one or more memories and one or more processors functionally connected to the one or more memories, wherein the one or more memories include instructions for configuring the one or more processors to perform operations based on execution by the one or more processors, and The operations include: receiving configuration information related to a plurality of control resource sets (CORESETs) from a base station, wherein a CORESET based on a first control resource set (CORESET) pool index and a second control resource set (CORESET) pool index is configured based on the configuration information, receiving downlink control information (DCI) from the base station, wherein the DCI includes information related to a physical downlink control channel (PDCCH) sequence, and a random access procedure is initiated by the PDCCH sequence, sending a random access preamble to the base station, and receiving a random access response (RAR) from the base station, The information related to the PDCCH sequence includes a synchronization signal / physical broadcast channel block index (SSB index), wherein the random access preamble is sent based on the SSB index, The random access response (RAR) includes a timing advance command, and The SSB index is related to the first CORESET pool index or the second CORESET pool index.

16. One or more non-transitory computer-readable media storing one or more instructions, wherein: One or more instructions executable by one or more processors configure the one or more processors to perform operations, and The operations include: receiving configuration information related to a plurality of control resource sets (CORESETs) from a base station, wherein a CORESET based on a first control resource set (CORESET) pool index and a second control resource set (CORESET) pool index is configured based on the configuration information, receiving downlink control information (DCI) from the base station, wherein the DCI includes information related to a physical downlink control channel (PDCCH) sequence, and a random access procedure is initiated by the PDCCH sequence, sending a random access preamble to the base station, and receiving a random access response (RAR) from the base station, The information related to the PDCCH sequence includes a synchronization signal / physical broadcast channel block index (SSB index), wherein the random access preamble is sent based on the SSB index, The random access response (RAR) includes a timing advance command, and The SSB index is related to the first CORESET pool index or the second CORESET pool index.

17. A method performed by a base station in a wireless communication system, the method comprising: Sending configuration information related to a plurality of control resource sets (CORESETs) to a user equipment (UE), wherein a CORESET based on a first control resource set (CORESET) pool index and a second control resource set (CORESET) pool index is configured based on the configuration information; Sending downlink control information (DCI) to the UE, wherein the DCI includes information related to a physical downlink control channel (PDCCH) sequence, and a random access procedure is initiated by the PDCCH sequence; receiving a random access preamble from the UE; and sending a random access response (RAR) to the UE, The information related to the PDCCH sequence includes a synchronization signal / physical broadcast channel block index (SSB index), wherein the random access preamble is received based on the SSB index, The random access response (RAR) includes a timing advance command, and The SSB index is related to the first CORESET pool index or the second CORESET pool index.

18. A base station operating in a wireless communication system, comprising: one or more transceivers; one or more processors; as well as one or more memories operably connected to the one or more processors and storing instructions that configure the one or more processors to perform operations based on execution by the one or more processors, The operations include: Sending configuration information related to a plurality of control resource sets (CORESETs) to a user equipment (UE), wherein a CORESET based on a first control resource set (CORESET) pool index and a second control resource set (CORESET) pool index is configured based on the configuration information; Sending downlink control information (DCI) to the UE, wherein the DCI includes information related to a physical downlink control channel (PDCCH) sequence, and a random access procedure is initiated by the PDCCH sequence; receiving a random access preamble from the UE; and sending a random access response (RAR) to the UE, The information related to the PDCCH sequence includes a synchronization signal / physical broadcast channel block index (SSB index), wherein the random access preamble is received based on the SSB index, The random access response (RAR) includes a timing advance command, and The SSB index is related to the first CORESET pool index or the second CORESET pool index.