METHOD AND APPARATUS FOR RANDOM ACCESS PROCEDURE IN A WIRELESS COMMUNICATION SYSTEM - Patent application

Abstract

A method according to an embodiment of the present disclosure includes receiving configuration information, transmitting a PRACH, and receiving the RAR based on a window associated with the RAR. The configuration information includes i) a first RACH configuration associated with a PCI of a serving cell and ii) a second RACH configuration associated with an additional PCI. The RAR is associated with one of two TAGs. The PCI is associated with the first TAG, and the additional PCI is associated with the second TAG. Based on which additional PCI the PRACH is associated with, the length of the window is determined based on a response window parameter associated with the second RACH configuration.

Description

[Technical Field]

[0001] The present specification relates to a method and apparatus for a random access procedure in a wireless communication system. [Background technology]

[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, the scope of mobile communication systems has expanded beyond voice to include data services, and currently, explosive traffic growth is causing resource shortages and users are demanding faster services, so more advanced mobile communication systems are required.

[0003] The requirements for next-generation mobile communication systems are significant: they must be able to accommodate explosive data traffic, dramatically increase the transmission rate per user, accommodate a significantly increased number of connected devices, achieve extremely low end-to-end latency, and be energy efficient. To achieve this, various technologies are being researched, including dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking.

[0004] In conventional LTE and NR standards, uplink timing advance configuration / indication supports a single TA value for a timing advance group (TAG) to which a specific cell or group of cells belongs.

[0005] Meanwhile, M-DCI-based M-TRP operation (Multiple-DCI based Multiple-Transmission and Reception point operation) can be performed in an environment where there is a large difference in distance between the UE and different TRPs. In this case, there may be differences in propagation delay, slot boundary, and inter-UE panel delay between target TRPs of uplink transmission within CC / BWP. In particular, this phenomenon may be more pronounced in non-IDEAL backhaul operation where coordination between TRPs is not performed.

[0006] To compensate for the timing difference or delay that occurs between TRPs, it is necessary to determine different uplink timing for each TRP. To this end, it has been agreed that TAGs are connected to / corresponding to the TCI states of the unified TCI (e.g., joint TCI states, separate TCI states (DL TCI states or UL TCI states)). To support TRP-specific TAs (i.e., to support two TAs for two TRPs), two TAGs can be configured within one serving cell.

[0007] In an M-DCI-based M-TRP environment, it has been agreed that cross-TRP RACH triggering, in which a specific TRP triggers RACH transmission to another TRP by a UE, is supported. In this case, in the case of a non-ideal backhaul situation between TRPs, a delay of the amount of backhaul delay may occur before a Random Access Response (RAR) related to a specific TRP (e.g., a non-serving cell or additional Physical Cell Identity (PCI)) is transmitted to another TRP (e.g., a serving cell).

[0008] As an example, in the case of an inter-cell M-DCI based TRP, a random access response (RAR) associated with TRP 2 (e.g., a non-serving cell or additional Physical Cell Identity (PCI)) may be received from TRP 1 (e.g., a serving cell (primary cell)).

[0009] More specifically, i) if the UE transmits a PRACH associated with TRP 1 (e.g., a serving cell), the UE receives an RAR from TRP 1 (e.g., a serving cell). ii) even if the UE transmits a PRACH associated with TRP 2 (e.g., a non-serving cell or an additional Physical Cell Identity (PCI)), the UE receives an RAR from TRP 1 (due to a non-ideal backhaul situation). In either case, the RAR (PDCCH / PDSCH) is received based on the Type 1-PDCCH CSS set configured for the serving cell (primary cell) (e.g., TRP 1).

[0010] The time it takes for the terminal to receive the RAR associated with TRP2 (case ii) may be delayed by a backhaul delay (e.g., the time it takes for the RAR to be transmitted from TRP2 to TRP1) compared to the time it takes for the terminal to receive the RAR associated with TRP1 (case i). Summary of the Invention [Problem to be solved by the invention]

[0011] As mentioned above, the delay that occurs in a non-ideal backhaul environment can cause the following problem: When two TAGs configured in a serving cell are managed, the time required to receive an RAR in a random access procedure initiated by a PDCCH order may vary for each TAG (and / or PCI). However, if the RAR is received based on one / the same RAResponse window (-response window) (configured in the serving cell), the RAR associated with a specific TAG (e.g., TRP, non-serving cell, or additional PCI) may not be received correctly.

[0012] The purpose of this document is to propose a method for solving the above problems.

[0013] The technical problems to be achieved in this specification are not limited to the technical problems described above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the art to which the present invention pertains from the following description. [Means for solving the problem]

[0014] A method performed by a terminal in a wireless communication system according to an embodiment of the present specification includes receiving configuration information, transmitting a Physical Random Access CHannel (PRACH), and receiving a Random Access Response (RAR) based on a window associated with the RAR.

[0015] The configuration information includes i) a first random access channel (RACH) configuration associated with the physical cell identity of the serving cell, and ii) a second random access channel (RACH) configuration associated with an additional PCI.

[0016] The PRACH is transmitted based on the initiation of a random access procedure.

[0017] The RAR is associated with one of two Timing Advance Groups (TAGs): the PCI of a serving cell is associated with the first of the two TAGs, and the additional PCI is associated with the second of the two TAGs.

[0018] Based on which the PRACH is associated with the PCI of the serving cell, the length of the window is determined based on a response window parameter associated with the first RACH configuration.

[0019] Based on which PRACH is associated with the additional PCI, the length of the window is determined based on a response window parameter associated with the second RACH configuration.

[0020] The RAR may be received based on a Physical Downlink Control Channel (PDCCH) and a Physical Downlink Shared Channel (PDSCH).

[0021] The serving cell may be a primary cell or a secondary cell. The PDCCH may be received based on a Type 1-PDCCH Common Search Space (CSS) set configured for the primary cell.

[0022] A transport block may be received on a physical downlink shared channel (PDSCH) scheduled based on DCI format 1_0 associated with the PDCCH. RAR may be based on a transport block.

[0023] The method may further include receiving a Physical Downlink Control Channel (PDCCH) order, which may initiate the random access procedure.

[0024] Based on the reception of the PDCCH order, a PRACH associated with the PCI or the additional PCI of the serving cell may be transmitted.

[0025] The PDCCH order may be based on Downlink Control Information (DCI).

[0026] The response window parameter may represent a number of slots.

[0027] The RAR may include a timing advance command applied to the first TAG or the second TAG.

[0028] Based on the setting information, a first NTA, offset and a second NTA, offset can be set. The first NTA, offset can be associated with the first TAG, and the second NTA, offset can be associated with the second TAG.

[0029] The method may further include receiving configuration information related to a control resource set (CORESETS). A CORESETPOOL INDEX may be associated with the second TAG.

[0030] According to yet another embodiment of the present disclosure, a terminal operating in a wireless communication system includes one or more transceivers, one or more processors, and one or more memories coupled to the one or more processors for storing instructions.

[0031] The instructions, when executed by the one or more processors, configure the one or more processors to perform all of the steps of any one of the methods.

[0032] According to still another embodiment of the present disclosure, an apparatus includes one or more memories and one or more processors operatively connected to the one or more memories.

[0033] The one or more memories are characterized by storing instructions that, when executed by the one or more processors, configure the one or more processors to perform all steps of any one of the methods.

[0034] One or more non-transitory computer-readable media according to other embodiments herein store instructions.

[0035] According to another embodiment of the present specification, a method performed by a base station in a wireless communication system includes the steps of transmitting configuration information, receiving a Physical Random Access CHannel (PRACH), and transmitting a Random Access Response (RAR) based on a window associated with the RAR.

[0036] The configuration information includes i) a first random access channel (RACH) configuration associated with a physical cell identity of the serving cell, and ii) a second random access channel (RACH) configuration associated with an additional PCI.

[0037] The PRACH is received based on the initiation of a random access procedure.

[0038] The RAR is associated with one of two Timing Advance Groups (TAGs): the serving cell's PCI is associated with the first of the two TAGs, and the additional PCI is associated with the second of the two TAGs.

[0039] Based on which the PRACH is associated with the PCI of the serving cell, the length of the window is determined based on a response window parameter associated with the first RACH configuration.

[0040] Based on which PRACH is associated with the additional PCI, the length of the window is determined based on a response window parameter associated with the second RACH configuration.

[0041] In accordance with yet another embodiment of the present specification, a base station operating in a wireless communication system includes one or more transceivers, one or more processors, and one or more memories coupled to the one or more processors and configured to store instructions.

[0042] The instructions, when executed by the one or more processors, configure the one or more processors to perform all of the steps of the method. [Effects of the Invention]

[0043] According to embodiments herein, the length of the window for RAR reception is determined based on a response window parameter associated with a first RACH configuration, based on which PCI the PRACH is associated with, and further based on which additional PCI the PRACH is associated with, based on a response window parameter associated with a second RACH configuration.

[0044] A window of a specific length is set for each TRP / TAG and RARs are received based on that, so the second TA associated with the additional PCI can be obtained more stably than when a window of the same length as the first TRP (serving cell) is used.

[0045] The effects obtained in this specification are not limited to those mentioned above, and other effects not mentioned will be clearly understood by those having ordinary skill in the art to which the present invention pertains from the following description. [Brief explanation of the drawings]

[0046] [Figure 1] 1 illustrates a MAC RAR according to an embodiment of the present specification. [Figure 2] 1 illustrates a Timing Advance Command MAC CE according to an embodiment of the present disclosure. [Figure 3] 1 is a flowchart illustrating a method performed by a terminal according to an embodiment of the present specification. [Figure 4] 10 is a flowchart illustrating a method performed by a base station according to another embodiment of the present disclosure. [Figure 5] FIG. 2 illustrates a configuration of a first device and a second device according to an embodiment of the present specification. DETAILED DESCRIPTION OF THE INVENTION

[0047] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. The detailed description disclosed below together with the accompanying drawings is intended to describe exemplary embodiments of the present invention and is not intended to show the only embodiments in which the present invention can be practiced. The following detailed description includes specific details to provide a thorough understanding of the present invention. However, those skilled in the art will recognize that the present invention can be practiced without such specific details.

[0048] In some cases, well-known structures and devices may be omitted or shown in block diagram form, focusing on the core functions of each structure and device, in order to avoid obscuring the concepts of the present invention.

[0049] Hereinafter, downlink (DL) refers to communication from a base station to a terminal, and uplink (UL) refers to communication from the terminal to the base station. In the downlink, the transmitter may be part of the base station, and the receiver may be part of the terminal. In the uplink, the transmitter may be part of the terminal, and the receiver may be part of the base station. The base station may also be expressed as a first communication device, and the terminal may also be expressed as a second communication device. The base station (BS) may also be replaced with terms such as fixed station, NodeB, evolved-NodeB (eNB), Next Generation NodeB (gNB), base transceiver system (BTS), access point (AP), network (5G network), AI system, road side unit (RSU), vehicle, robot, unmanned aerial vehicle (UAV), augmented reality (AR) device, and virtual reality (VR) device. Furthermore, a terminal may be fixed or mobile, and may be replaced with terms such as UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advance Mobile Station), WT (Wireless terminal), MTC (Machine-Type Communication) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, robot, AI module, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.

[0050] Multi-TRP (Transmission / Reception Point) related operations

[0051] The M-TRP transmission method, in which M TRPs transmit data to one terminal (User equipment, UE), can be broadly divided into two types: eMBB M-TRP transmission, which is a method for increasing the transmission rate, and ULLCM-TRP transmission, which is a method for increasing the reception success rate and reducing latency.

[0052] UL MTRP-URLLC means that multiple TRPs receive the same data / UCI from one UE using different layer / time / frequency resources. For example, TRP1 receives the same data / UCI from the UE using resource 1, and TRP2 receives the same data / UCI from the UE using resource 2. The received data / UCI is then shared via the connected backhaul link between the TRPs. A UE configured with the UL MTRP-URLLC transmission method transmits the same data / UCI using different layer / time / frequency resources. In this case, the UE receives instructions from the base station regarding which Tx beam and which Tx power (i.e., UL TCI state) to use on the layer / time / frequency resource for transmitting the same data / UCI. For example, if the same data / UCI is transmitted on resource 1 and resource 2, the UE is instructed on the UL TCI state to use on resource 1 and the UL TCI state to use on resource 2. Such UL MTRP URLLC can be applied to the PUSCH / PUCCH.

[0053] SDCI or MDCI based MTRP transmission

[0054] From the perspective of DCI (downlink control information) transmission, the M-TRP (multiple TRP) transmission method can be divided into i) M-DCI (multiple DCI) based M-TRP transmission, in which each TRP transmits different DCI, and ii) S-DCI (single DCI) based M-TRP method, in which one TRP transmits DCI.

[0055] R16 NR MTRP transmission

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

[0057] R16 M-DCI based MTRP PDSCH

[0058] M-DCI-based MTRP PDSCH transmission is a scheme in which each TRP schedules and transmits a PDSCH via DCI. That is, TRP1 transmits PDSCH1 via DCI1, and TRP2 transmits PDSCH2 via DCI2. When PDSCH1 and PDSCH2 overlap in the same frequency-time resource, two PDSCHs are received in the same RE, improving resource efficiency and increasing transmission capacity. To this end, the R16 standard introduces a CORESET pool, which is a group of multiple CORESETs. TRP1 transmits a PDCCH via a CORESET belonging to CORESET pool 0, and TRP1 also transmits the PDSCH scheduled by the PDCCH. TRP2 transmits a PDCCH via a CORESET belonging to CORESET pool 1, and TRP2 also transmits the PDSCH scheduled by the PDCCH. A specific TRP can also schedule PUSCH transmission to a UE via a CORESET belonging to each CORESET pool. For PUCCH, some PUCCH resources are scheduled by TRP1 to receive UCI, and the remaining PUCCH resources are scheduled by TRP2 to receive UCI. In the case of PUSCH and PUCCH, the channels scheduled / used by each TRP are TDM-multiplexed to prevent overlap, so an increase in transmission capacity cannot be expected, but the UE can transmit independent PUSCH / PUCCH to TRP1 and TRP2.

[0059] In addition, the UE can recognize a PUSCH (or PUCCH) scheduled by DCI received in a different CORESET (or a CORESET belonging to a different CORESET group) as a PUSCH (or PUCCH) transmitted via a different TRP, or as a PUSCH (or PUCCH) of a different TRP. In addition, the scheme for UL transmission (e.g., PUSCH / PUCCH) transmitted via a different TRP can be similarly applied to UL transmission (e.g., PUSCH / PUCCH) transmitted via a different panel belonging to the same TRP.

[0060] The CORESET group ID (or a CORESET pool index having the same meaning) described / mentioned in this specification may refer to an index / identification information (e.g., ID) for distinguishing a CORESET for each TRP / panel. A CORESET group is a group / union of CORESETs distinguished by an index / identification information (e.g., ID) for distinguishing a CORESET for each TRP / panel / the CORESET group ID. For example, the CORESET group ID may be specific index information defined in the CORESET configuration. For example, the CORESET group may be set / indicated / defined by an index defined in the CORESET configuration for each CORESET. And / or, the CORESET group ID may refer to an index / identification information / indicator for distinguishing / identifying CORESETs set in / associated with each TRP / panel, and the CORESET group ID described / mentioned in this specification may be expressed as a specific index / specific identification information or specific indicator for distinguishing / identifying CORESETs set in / associated with each TRP / panel. The CORESET group ID, i.e., a specific index / specific identification information / specific indicator for distinguishing / identifying between CORESETs set / associated with each TRP / panel, can be set / indicated via higher layer signaling (e.g., RRC signaling), L2 signaling (e.g., MAC-CE), L1 signaling (e.g., DCi), etc.As an example, it is set / instructed such that PDCCH detection for each TRP / panel is performed in units of the CORESET group, and / or it is set / instructed such that uplink control information (e.g., CSI, HARQ-A / N, SR) and / or uplink physical channel resources (e.g., PUCCH / PRACH / SRS resources) are separated and managed / controlled for each TRP / panel in units of the CORESET group, and / or HARQ A / N (process / resending) for PDSCH / PUSCH, etc., scheduled for each TRP / panel in the corresponding CORESET group unit can be managed.

[0061] For example, the ControlResourceSet IE (information element), which is a higher layer parameter, is used to set a time / frequency control resource set (control resource set, CORESET). As an example, the control resource set (CORESET) is related to the detection and reception of downlink control information. The ControlResourceSet IE may include a CORESET-related ID (e.g., controlResourceSetID) / an index of the CORESET pool for the CORESET (e.g., CORESETPoolIndex) / the time / frequency resource setting of the CORESET / TCI information related to the CORESET, etc. As an example, the index of the CORESET pool (e.g., CORESETPoolIndex) can be set to 0 or 1. In the above description, the CORESET group corresponds to the CORESET pool, and the CORESET group ID corresponds to the CORESET pool index (e.g., CORESETPoolIndex). The ControlResourceSet (e.g., CORESET) can be set via higher layer signaling (e.g., RRC).

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

[0063] In addition, in the method proposed in this specification, when receiving data / DCI / UCI for a certain frequency / time / space resource, a specific TCI situation (or TCI) means the following:

[0064] In the case of DL, this may mean estimating a channel from DMRS using the QCL type and QCL RS indicated by the corresponding DL TCI state in that frequency / time / space resource, and receiving / demodulating data / DCI on the estimated channel.

[0065] In the case of UL, this can mean transmitting / modulating DMRS and data / UCI using the Tx beam and / or Tx power indicated by the corresponding UL TCI state in the frequency / time / space resources.

[0066] The UL TCI state is the Tx bea m Alternatively, it may include Txpower information and may be configured in the UE via other parameters such as spatial relation info instead of TCI state. The UL TCI state may be directly indicated in the UL grant DCI or may refer to the spatial relation info of the SRS resource indicated through the SRI field of the UL grant DCI.

[0067] Or it can mean the OL Tx power control parameter (j: index for open loop parameters Po & alpha (maximum 32 parameter value sets per cell), q_d: index of DL RS resource for PL measurement (maximum 4 measurements per cell), l: closed loop power control process index (maximum 2 processes per cell) ) connected to the value indicated via the SRI field of the UL grant DCI. Alternatively, in R17 NR, the UL TCI can be indicated using the DL grant DCI.

[0068] <Explanation of TRP Category-related Extension>

[0069] In this specification, for the convenience of explanation, the proposed method is applied assuming cooperative transmission / reception between two TRPs, but it can also be extended and applied in a multi-TRP environment with three or more, and can also be extended and applied in a multi-panel environment. Different TRPs can be recognized by the UE as different TCI states (associated with different CORESET pool indices).

[0070] For example, the fact that the UE receives data / DCI using the first TCI state associated with the first CORESET pool index means that it receives data / DCI from TRP1. For example, the fact that the UE transmits data / UCI using the first TCI state associated with the first CORESET pool index means that it transmits data / UCI to TRP1.

[0071] For example, when the UE receives data / DCI using a second TCI state associated with a second CORESET pool index, it means that the UE has received the data / DCI from TRP2. For example, when the UE transmits data / UCI using a second TCI state associated with a second CORESET pool index, it means that the UE has transmitted the data / UCI to TRP2.

[0072] TA(Timing advance) related procedure

[0073] The transmission of uplink frame number i from a terminal (User Equipment, UE) is T from the start of the corresponding downlink frame at the terminal. TA It must start before.

[0074] T TA The uplink timing (eg, uplink frame) associated with the , ...

[0075] [Table 1]

[0076] T in Table 1 TA is N TA and N TA,offset It can be calculated / determined based on N TA and N TA,offset is set / applied as follows:

[0077] N TA : 1) Configured via RAR (Random access response), 2) Configured via Timing advance command (MAC-CE)

[0078] N TA,offset 1) Set a specific value for each serving cell, 2) Apply a predefined value to the serving cell according to Duplex mode / FR

[0079] In the following, the aforementioned N TA,offset and N TA This section explains in detail how to set up / apply the above.

[0080] N TA,offset

[0081] Case 1) How to set specific values ​​for each serving cell

[0082] For example, the terminal TA,offset The UE may receive configuration information (e.g., ServingCellConfigCommon Information) from the base station, which includes information about the UE's ServingCellConfigCommon information. The configuration information may be received based on RRC signaling. Table 2 below shows an example of the configuration information.

[0083] [Table 2]

[0084] Case 2) How to apply predefined values ​​to the serving cell according to Duplex mode / FR

[0085] For example, the terminal may use a predefined N TA,offset The value of N can be adapted to the serving cell. TA,offset The values ​​of are shown below.

[0086] [Table 3]

[0087] N TA

[0088] Case 1) Setting via RAR (Random Access Response)

[0089] For example, in a random access procedure (e.g., a 2-step RACH procedure or a 4-step RACH procedure), the terminal receives an RAR from the base station. TA can be determined / set. Specifically, the RAR may include a timing advance command. The timing advance command indicates an index value (e.g., index value TA) related to timing adjustment. N TA can be determined (see Table 5 below). The RAR may be based on the MAC RAR. Hereinafter, this will be described with reference to FIG.

[0090] FIG. 1 illustrates a MAC RAR according to an embodiment of the present disclosure.

[0091] As shown in Figure 1, the MAC RAR may include R (Reserved bit), Timing Advance Command, UL Grant, and Temporary C-RNTI. Table 4 below illustrates an example of the MAC payload of the MAC RAR.

[0092] [Table 4]

[0093] Table 5 below illustrates examples of transmission timing adjustments based on the Timing advance command.

[0094] [Table 5-1]

[0095] [Table 5-2]

[0096] [Table 5-3]

[0097] [Table 5-4]

[0098] Case 2) Setting via Timing advance command (MAC-CE)

[0099] For example, N TA can be set / determined based on MAC-CE. TA is determined based on a Timing Advance Command MAC CE. The Timing Advance Command MAC CE may include a timing advance command. N based on the timing advance command TA The determination of is the same as that in Case 1, so a duplicated explanation will be omitted (see Table 5). The Timing Advance Command MAC CE will be explained below with reference to FIG.

[0100] FIG. 2 illustrates a Timing Advance Command MAC CE according to an embodiment of the present disclosure.

[0101] As shown in Figure 2, the Timing Advance Command MAC CE may include a TAG ID and a Timing Advance Command. Table 6 below illustrates an example of the payload of the Timing Advance Command MAC CE.

[0102] [Table 6]

[0103] TAG (Timing advance group)

[0104] Timing Advance Group (TAG) refers to a group of serving cells that use the same Timing Advance value. Table 7 below illustrates the definition of TAG and configuration information related to TAG.

[0105] [Table 7-1]

[0106] [Table 7-2]

[0107] [Table 7-3]

[0108] Procedure

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

[0110] [Table 8-1]

[0111] [Table 8-2]

[0112] [Table 8-3]

[0113] The above-mentioned contents may be applied in combination with the methods proposed in this specification, which will be described later, or may be supplemented to clarify the technical features of the methods proposed in this specification. The methods described below are only divided for the convenience of explanation, and it goes without saying that some components of any one method may be substituted for some components of another method, or may be applied in combination with each other.

[0114] According to the 3GPP standard up to NR Rel-17, the timing advance (TA) setting for the UE uplink transmission from the BS to compensate for the propagation delay between the BS and the UE can be performed via higher layer signaling. Also, the TA for a specific group of cells can be separately configured / managed according to the concept / definition of a timing advance group (TAG).

[0115] Currently, there is no method to support multiple TA values ​​within a specific cell. However, considering scenarios where there is a large difference in distance between different target TRPs and the UE when transmitting M-TRP UL, an enhancement will be implemented to allow multiple (two) TA values ​​to be set / indicated in a specific CC / BWP.

[0116] In this case, it is necessary to discuss how the base station sets / instructs multiple TA values ​​to the terminal, and / or how the connection relationship between the multiple TA values ​​and the terminal UL channel / RS is performed. As described in the Rel-18 MIMO WID objective (RP-213598) in Table 9 below, the setting of TA values ​​for multi-DCI (M-DCI) based M-TRP operation is considered.

[0117] [Table 9]

[0118] Here, the TA (TA value) can be based on the description of FIG. 2 and the above-mentioned TA (Timing advance) related procedure.

[0119] In the RAN1 and RAN2 standards before Rel-18, the base station uses N TA and N TA,offset The base station manages the N TA can be set as follows: i) N via RAR MAC CE TA or ii) set N via TA command MAC CE (Timing Advance Command MAC CE) TA In addition, the base station uses the concept of TAG (Timing Advance Group) to set up to four TAGs per terminal for a specific cell or cell combination, and assigns N TA You can update / manage the values.

[0120] As described in the WID, a scenario that attempts to support 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(s) present in the BWP. Based on the CORESET pool index, each TRP is classified as i) a TRP performing DL transmission (e.g., PDCCH, PDSCH) or / and ii) a target TRP for UL transmission. For example, CORESETs 0 and 1 with CORESET pool index 0 may correspond to TRP 1, and CORESETs 2 and 3 with CORESET pool index 1 may correspond to TRP 2.

[0121] On the other hand, in Rel-18 MIMO, the agreement items shown in Table 10 below were derived for two TAs.

[0122] [Table 10]

[0123] As mentioned above, it was discussed that two TAGs can be configured to manage two TA values ​​in one serving cell, and it was also agreed that the reference timing to apply the TA values ​​managed by each TAG would also support two DL reference timings in one serving cell.

[0124] In this case, the UE can use RACH transmission to acquire multiple TA values. Depending on the results of standardization discussions, it was agreed to preferentially use RACH transmission based on contention-free random access (CFRA).

[0125] In an M-DCI based M-TRP environment, it has been agreed that cross-TRP RACH triggering, in which a specific TRP triggers RACH transmission to another TRP, is supported. In this case, in the case of a non-ideal backhaul situation between TRPs, a backhaul delay occurs until the information that a specific TRP has triggered RACH to the UE is transmitted to the other TRPs.

[0126] As an example, in the case of an inter-cell M-DCI based TRP, a Random Access Response (RAR) of TRP2 (e.g., a non-serving cell or additional Physical Cell Identity (PCI)) may be received from TRP1 (e.g., a serving cell (primary cell)).

[0127] More specifically, i) a terminal that transmitted a PRACH associated with TRP1 (e.g., a serving cell) receives an RAR from TRP1 (e.g., a serving cell). ii) a terminal that transmitted a PRACH associated with TRP2 (due to a non-ideal backhaul situation between TRPs) receives an RAR from TRP1.

[0128] The time required for the terminal to receive the RAR related to TRP2 (case ii) may be delayed by a backhaul delay (e.g., the time required for the RAR to be transmitted from TRP2 to TRP1, i.e., the forwarding delay) compared to the time required for the terminal to receive the RAR related to TRP1 (case i).

[0129] The existing terminal operations related to RAR reception are as follows.

[0130] After a PRACH transmission (associated with an additional PCI or a serving cell PCI), the terminal monitors PDCCH candidates in a Type 1-PDCCH CSS set configured for a serving cell (e.g., a primary cell). The terminal receives a PDCCH based on the monitoring. The terminal receives a PDSCH scheduled according to DC format 1_0 associated with the PDCCH. The terminal receives a transport block on the PDSCH. RAR is based on the transport block.

[0131] If a device uses the legacy RAR receiving window, there may be a problem where RAR cannot be received continuously due to the large backhaul delay.

[0132] Based on the above background, this specification describes a method for a base station to configure / indicate RACH transmission for a terminal, and proposes subsequent terminal operations. Specifically, this specification describes i) a method for configuring / indicating a TRP ( / CORESET pool index / TAG)-specific RAR window, and ii) a method for configuring / indicating a specific starting offset for an RAR window associated with a specific TRP ( / CORESET pool index / TAG)-specific RACH. Specifically, the RAR window-related operations may be performed based on Table 11 below.

[0133] [Table 11]

[0134] In the present invention, " / " can be interpreted as "and", "or", or "and / or" depending on the context.

[0135] Suggestion 1

[0136] If a terminal supports 2TA in a specific serving cell, a method for (separately) configuring / indicating a TRP ( / CORESET pool index / TAG)-specific RAR window may be considered.

[0137] When the UE transmits a RACH associated with / corresponding to a specific TRP ( / CORESET pool index / TAG), the RAR can be received based on the configured / indicated TRP ( / CORESET pool index / TAG)-specific RAR window.

[0138] (Considering the situation of a non-ideal backhaul in an M-DCI based M-TRP DL / UL scenario) The RAR window can be set / indicated / defined as follows:

[0139] As an example, the base station may set / indicate a different (longer) RAR window for PRACH transmissions associated / corresponding to a specific TRP / TAG / CORESETSpool index.

[0140] As an example, the RAR window for PRACH transmission associated with / corresponding to a particular TRP / TAG / CORESET pool index may be predefined (between the terminal / base station or at the time of terminal / base station implementation).

[0141] As a specific example, when a PRACH associated with a first TRP / first TAG / first CORESET pool index is transmitted, an RAR associated with the first TRP / first TAG / first CORESET pool index may be received based on a first RAR window. When a PRACH associated with a second TRP / second TAG / second CORESET pool index is transmitted, an RAR associated with the second TRP / second TAG / second CORESET pool index may be received based on a second RAR window. The first RAR window may be set separately from the second RAR window. The first RAR window may be set based on a first RACH configuration (e.g., a RACH configuration associated with TRP1 / serving cell / serving cell PCI). The second RAR window may be set based on a second RACH configuration (e.g., a RACH configuration associated with TRP2 / non-serving cell / additional PCI).

[0142] The length of the first RAR window (or the second RAR window) may be set to be greater than the length of the second RAR window (or the first RAR window).

[0143] In the existing method, only one RAR window is configured cell-specifically. Specifically, the RAR window in the existing method is configured based on one ra-ResponseWindow parameter (e.g., ServingCellConfigCommon → UplinkConfigCommon → BWP-UplinkCommon → rach-ConfigCommon → rach-ConfigGeneric → ra-ResponseWindow). The ra-ResponseWindow parameter indicates the window length (number of slots).

[0144] According to this embodiment, two or more RAR windows may be configured even in a specific serving cell. For example, two or more TRP ( / TAG / CORESETS pool index)-specific RAR windows (i.e., ra-ResponseWindow and / or msgB-ResponseWindow) may be configured. This embodiment may also be applied to an inter-cell M-DCI environment. For example, a terminal may receive a first RACH configuration associated with TRP1 (e.g., a serving cell or PCI) and a second RACH configuration associated with TRP2 (e.g., a non-serving cell or additional PCI) from a base station. Each of the first and second RACH configurations may include a response window parameter. The RAR window may be configured based on the response window parameter of each RACH configuration.

[0145] In an additional embodiment, a separate RAR window can be utilized only for RACH transmissions associated with a particular TAG / TRP / CORESETS pool index.

[0146] As an example, a separate RAR window may be configured / instructed for RACH transmissions associated with a second TAG / TRP / CORESETPOOL INDEX (ie, CORESETSpool index = 1) within a particular serving cell.

[0147] As an example, for RACH transmissions associated with the secondTAG / TRP / CORESETpool index (i.e., CORESETpoolindex = 1) within a particular serving cell, a RAR window based on a separately defined value (e.g., the number of slots determining the window length) may be used.

[0148] In this case, the RACH transmission related to the first TAG / TRP / CORESET pool index can be performed in the same manner as before. That is, after the RACH transmission related to the first TAG / TRP / CORESET pool index, the RAR can be received based on the RAR window set to cell-specific.

[0149] In one example, the term "secondTAG" used herein may refer to a second TAG among TAGs that share the same component carriers (CCs) and / or bands.

[0150] According to Proposal 1, the following problems can be solved.

[0151] In an M-DCI-based M-TRP DL / UL scenario, if TRPs are connected via a non-ideal backhaul, problems may occur in the UE's RAR reception. If each TRP triggers a (CFRA-based) RACH transmission to itself when it triggers a RACH transmission to the UE, it can use the legacy cell-specific RAR window as is. However, if each TRP triggers a RACH to another TRP to the UE, a delay occurs in transmitting information to the other TRP that the corresponding UE will transmit a RACH, which may cause problems in the UE's RAR reception.

[0152] It may be assumed that the TRP that received the RACH does not schedule the RAR, but the TRP that triggered the RACH (e.g., the TRP associated with the transmission of the PDCHORDER) schedules the RAR. For example, it may be assumed that the PRACH is associated with TRP 2 (additional PCI), but the RAR associated with the RACH is received from TRP 1 (serving cell). In this case, additional delay may occur because the TRP that received the RACH must convey information that the UE's RACH was successfully received to the TRP that triggered the RACH. In other words, the delay problem due to non-ideal backhaul may be further exacerbated.

[0153] In particular, in an intra-cell M-DCI environment and an inter-cell M-DCI environment, the same problem as described above exists according to existing methods.

[0154] Specifically, a PDCCH order for performing RACH triggering and an RAR scheduling PDCCH ( / RAR PDSCH) may be primarily associated with CORESET(s) having a first CORESET pool index. That is, a PDCCH associated with a PDCCH order and / or an RAR is transmitted / received in a CORESET having a first CORESET pool index. This means that i) a PDCCH order for RACH triggering for TA update associated with each TRP / TAG and ii) an RAR associated with each TRP / TAG are all received from one TRP (e.g., a serving cell (primary cell). While no delay occurs in the RACH procedure associated with the first CORESET pool index / first TA RACH G / serving cell, an additional delay may occur in the RACH procedure associated with the second CORESET pool index / second TAG / additional PCI.

[0155] The above problem can be solved by the operation of Proposal 1 as follows: According to Proposal 1, TRP / TAG / CORESETpool index-specific RAR windows can be set / indicated / defined. That is, each RAR window can be set / indicated / defined taking into account the delay involved in sharing information about RACH triggering between TRPs and / or information about RACH reception, thereby solving the problem of RARs not being correctly received due to the delay.

[0156] In other words, RARs can be received more stably than when RARs related to each TRP / TAG / CORESET pool index are received based on one RAR window specific to a cell. Therefore, TA acquisition / update Therefore, the reliability of the disclosed random access procedure can be improved.

[0157] Suggestion 2

[0158] If the UE supports 2TA in a specific serving cell, a method of setting / indicating a specific start offset for the RAR window associated with the corresponding TRP( / CORESET pool index / TAG-specific RACH) may be considered.

[0159] When the UE transmits a RACH associated with / corresponding to a specific TRP ( / CORESETpool index / TAG), the RAR window for receiving the RAR can start based on the configured / indicated starting offset.

[0160] Example 1: (Considering non-ideal backhaul situations in M-DCI-based M-TRP DL / UL scenarios) The base station can set / instruct an additional starting offset / back-off value of t msec and / or n slots for the RAR window start point associated with / corresponding to a specific TRP / TAG / CORESET pool index. In this case, the window is set to t msec and / or n slots from the already defined starting point. of The window can start after an additional t msec and / or n slots.

[0161] Example 2: In a UE associated with a non-terrestrial network (NTN) (considering a non-ideal backhaul situation in an M-DCI-based M-TRP DL / UL scenario), the base station can set / instruct an additional starting offset / back-off value of t msec and / or n slots for the RAR window starting point associated with the RACH associated with / corresponding to a specific TRP / TAG / CORESET pool index. In this case, windowcan start t msec and / or n slots later than the previously defined starting point. JPEG2026503545000020.jpg10121

[0162] As an example, k mac If UE-specific update / reset is possible (via RRC / MAC CE), the base station should set k with a value that includes the non-ideal backhaul delay. mac can be updated, i.e., k mac By updating the (TRP / TAG / CORESETpool index-specific) RAR window starting offset can be given. In this case, k mac Values ​​can be updated / set to TRP / TAG / CORESETpool index-specific.

[0163] Furthermore, in the M-TRP situation, when one TRP is a terrestrial network (TN) and the other TRP is a non-terrestrial network (NTN), the offset value (t / n) may be set differently. Specifically, the following i) and ii) may be set / indicated differently.

[0164] i) The t / n value of the RAR window starting point associated with the RACH associated with the TRP / TAG / CORESET pool index that is the TN

[0165] ii) t / n value related to the TRP / TAG / CORESET pool index, which is NTN

[0166] For example, i) and ii) may be set to different values. For example, i) and ii) may be set to values ​​based on different ranges.

[0167] Or / and k instead of utilizing t / n values macThe effect of the second embodiment can be obtained by increasing the value range of the second embodiment. The second embodiment can also be applied to the case where both TRPs are NTNs.

[0168] In a further embodiment, a separate RARwindow starting offset may be utilized only for RACH transmissions associated with a particular TAG / TRP / CORESETpool index.

[0169] As an example, a separate RAR window start offset may be configured / indicated for RACH transmissions associated with a secondTAG / TRP / CORESETpool index (ie, CORESETpool index=1) within a particular serving cell.

[0170] As an example, a separately defined value may be applied as the RAR window starting offset for RACH transmission associated with the second TAG / TRP / CORESET pool index (ie, CORESETpool index=1) within a specific serving cell.

[0171] In this case, the RACH transmission associated with the first TAG / TRP / CORESET pool index can be operated in the same manner as in the past, that is, the RAR associated with the RACH transmission associated with the first TAG / TRP / CORESET pool index can be received based on the RAR window starting point set to be cell-specific.

[0172] In an embodiment of Proposal 2, t msec and / or n slot may be set / indicated / defined as follows:

[0173] As an example, t msec and / or n slots (n slots) may be configured / instructed to the terminal based on higher layer signaling such as RRC and / or MAC CE signaling.

[0174] As an example, t msec and / or n slots may be predefined (between terminal / base station or at terminal / base station implementation) with specific values.

[0175] Proposal 2 leads to the following effects:

[0176] Similar to Proposal 1, Proposal 2 can solve the problem of RARs associated with specific TRP / TAG / CORESET pool indexes not being received correctly due to delay.

[0177] The differences between Proposal 1 and Proposal 2 are as follows: Proposal 2 solves the above problem by delaying the starting point of the window rather than increasing the window.

[0178] In the above embodiments, "configure" may refer to higher layer RRC / MAC signaling, and "indicate" may refer to dynamic indication via DCI.

[0179] The embodiments of proposal 1 / 2 and the additional embodiments can work in certain combinations.

[0180] The embodiments of Proposal 1 / 2 and the additional embodiments can be applied to solve the backhaul delay problem that occurs when cross-TRP (TRP-specific) RACH triggering is performed, as mentioned in the background. However, the scope of application of Proposal 1 / 2 is not limited to cases where backhaul delay occurs. That is, different delays in the RACH procedures related to each TRP / TAG / CORESET pool index can be solved. but It is obvious that the present invention can be extended to all cases that arise.

[0181] For example, if the above problem is not assumed, the RACH procedure can be performed according to the existing method. For example, it can be assumed that a specific TRP transmits a PDCCH order to the UE so that the RACH is transmitted to itself (CFRA-based RACH), and the corresponding TRP transmits an RAR after receiving the RACH. In such a case, the delay to If there are no related problems, the proposed embodiments 1 / 2 and additional embodiments may not be applied, i.e., the TRP-specific RAR window / TRP-specific RAR window starting offset may not be applied, or the UE may operate as previously defined (RAR reception based on a cell-specific RAR window).

[0182] For example, the embodiments of Proposal 1 / Proposal 2 may be applied even when the above-mentioned problem is not a prerequisite. That is, even if backhaul delay / forwarding delay does not occur, the above-mentioned embodiments of Proposal 1 / Proposal 2 may be applied in consideration of the fact that timing for each TRP can be different.

[0183] An example of a terminal (or base station) operation based on at least one of the above-described embodiments (for example, at least one of Proposal 1 to Proposal 2 and additional embodiments) is as follows.

[0184] 1) The terminal (base station) is responsible for the 2TAG in a specific serving cell. S (2TA S ) related settings.

[0185] The setting information can be based on the contents of Proposal 1 to Proposal 2 and additional embodiments.The setting information can include information based on at least one of Proposal 1, Proposal 2, and additional embodiments.

[0186] For example, the configuration information may include a RACH configuration associated with each TAG / TRP / serving cell (additional PCI). Based on each RACH configuration, an RAR window and / or an RAR window starting offset may be configured.

[0187] For example, based on the setting information, the RAR window and / or the RAR window starting offset associated with each TAG may be set.

[0188] 2) The terminal (base station) s Receive (send) messages that configure / instruct RACH transmissions related to the RACH (one of the RACHs).

[0189] The message is a CFRA-based RACH of It can be a PDCCH that triggers / orders.

[0190] 3) The terminal (base station) transmits (receives) the RACH based on the message.

[0191] The RACH transmission may be associated with a particular TAG / TRP / serving cell (or additional PCI).

[0192] 4) The terminal (base station) RAR The RAR is received (transmitted) based on a window (for example, a window set based on the response window parameter of the first RACH configuration or the second RACH configuration).

[0193] The above-described operations of the terminal / base station are merely examples, and each operation (or step) is not necessarily required. Depending on the implementation method of the terminal / base station, the 2TAG of the terminal according to the above-described embodiment may be s Operations related to RACH transmissions related to may be omitted or added.

[0194] In practical terms, the operation of the base station / terminal according to the above-mentioned embodiments (e.g., operation based on at least one of Proposal 1 to Proposal 2) can be processed by the device of Figure 5 (e.g., processors 110, 210 of Figure 5) described below.

[0195] In addition, the operation of the base station / terminal according to the above embodiments (e.g., operation based on at least one of Proposal 1 and Proposal 2) may be stored in a memory (e.g., 140, 240 in FIG. 5) in the form of instructions / programs (e.g., instructions, executable code) for driving at least one processor (e.g., 110, 210 in FIG. 5).

[0196] Hereinafter, the above-described embodiment will be described in detail from the viewpoint of the operation of a terminal and a base station with reference to Figures 3 and 4. The methods described below are only divided for the convenience of explanation, and it goes without saying that some components of any one method can be replaced with some components of another method or can be combined with each other and applied.

[0197] FIG. 3 is a flowchart illustrating a method performed by a terminal according to an embodiment of the present specification.

[0198] Referring to FIG. 3, the method performed by the terminal according to an embodiment of the present specification includes a step S310 of receiving configuration information, a step S320 of transmitting a PRACH, and a step S330 of receiving an RAR.

[0199] In S310, the terminal receives configuration information from the base station.

[0200] The configuration information may include information based on the above-mentioned Proposal 1 and / or Proposal 2. As an example, the configuration information may be based on ServingCellConfigCommon based on Table 2.

[0201] According to one embodiment, the configuration information may include i) a first Random Access Channel (RACH) configuration associated with a Physical Cell Identity (PCI) of a serving cell, and ii) a second Random Access Channel (RACH) configuration associated with an additional PCI.

[0202] According to an embodiment, the setting information may further include information related to an N-TimingAdvanceOffset (e.g., n-TimingAdvanceOffset, n-TimingAdvanceOffset2). TA、offset and 2N TA、offset can be set. TA、offset is associated with the first of two Timing Advance Groups (TAG), and the second TA、offset may be associated with the second TAG of the two TAGs.

[0203] The two TAGs may be set in the serving cell. TA、offset may be related to the Physical Cell Identity (PCI) of the serving cell. TA、offset can be associated with the additional PCI. Each PCI can be identified by a "PhysCellId".

[0204] That is, the PCI of the serving cell can be interpreted / substituted as a PhysCellId for the serving cell. Furthermore, the additional PCI can be interpreted / substituted as a PhysCellId different from the PhysCellId of the serving cell. TA、offset is associated with the PhysCellId for the serving cell. TA、offsetmay be associated with a PhysCellId that is different from the PhysCellId of the serving cell.

[0205] The uplink timing of each TAG is TA、offset (See Table 1.) Each uplink timing may be associated with an uplink frame.

[0206] The first N TA、offset may be applied to uplink transmission based on a first Transmission Configuration Indication (TCI) state. The first TCI state may be associated with a first CORESET based on a first CORESET pool index. In one example, the uplink transmission may be performed based on a spatial domain filter based on the first TCI state.

[0207] Said 2nd N TA、offset may be applied to uplink transmission based on a second TCI state. The second TCI state may be associated with a second CORESET based on a second CORESET pool index. As an example, the uplink transmission may be performed based on a spatial domain filter based on the second TCI state.

[0208] In S320, based on the initiation of the random access procedure, the terminal transmits a physical random access channel (PRACH) to the base station.

[0209] As an example, the PRACH may be associated with the PCI or the additional PCI of the serving cell.

[0210] At S330, the terminal receives a Random Access Response (RAR) from the base station based on a window associated with the RAR.

[0211] The RAR may be associated with one of two Timing Advance Groups (TAGs). Specifically, the RAR may include a Timing Advance Command applied to the first or second TAG.

[0212] The index value T indicated by the timing advance command A N related to the amount of time alignment for the first TAG or the second TAG based on TA Specifically, the index value T A By N TA As an example, the index value T A (e.g., 0, 1, 2, …, 3846) based on N TA can be indicated. TA is T A 16 64 / 2 μ (See Table 5)

[0213] The PCI of the serving cell may be associated with a first of two TAGs, and the additional PCI may be associated with a second of the two TAGs.

[0214] According to one embodiment, the window may be based on the RAR window of Proposal 1. Specifically, based on whether the PRACH is associated with the PCI of the serving cell, the length of the window may be determined based on a response window parameter associated with the first RACH configuration. Based on whether the PRACH is associated with the additional PCI, the length of the window may be determined based on a response window parameter associated with the second RACH configuration. The response window parameter (e.g., ra-Response window) may represent the number of slots.

[0215] As mentioned above, it may be assumed that a delay occurs in receiving the RAR associated with a specific TAG (e.g., the second TAG). This will be explained in detail below.

[0216] Specifically, the RAR may be received based on a Physical Downlink Control Channel (PDCCH) and a Physical Downlink Shared Channel (PDSCH). The serving cell may be a Primary Cell (PCell) or a Secondary Cell (SCell). The PDCCH may be received based on a Type1-PDCCH Common Search Space (CSS) set configured for the primary cell.

[0217] A transport block may be received on a Physical Downlink Shared Channel (PDSCH) scheduled based on DCI format 1_0 associated with the PDCCH, and the RAR may be based on the transport block.

[0218] As mentioned above, the RAR associated with the second TAG is also received from the primary cell, but there may be a delay in receiving the corresponding RAR, i.e., the time required for receiving the RAR associated with the second TAG may differ from the time required for receiving the RAR associated with the first TAG.

[0219] Depending on whether the PRACH is associated with the PCI of the serving cell or an additional PCI, the length of the window associated with the RAR is determined based on the response window parameter of the first RACH configuration or the second RACH configuration, so that the RAR associated with each TAG can be successfully received.

[0220] The method may further include receiving a PDCCH order. In the PDCCH order receiving step, the terminal receives a Physical Downlink Control Channel (PDCCH) order from a base station. The random access procedure may be initiated by the PDCCH order. In this case, the PDCCH order may trigger a RACH procedure related to the PCI or the additional PCI.

[0221] Based on the reception of the PDCCH order, the PRACH associated with the PCI or the additional PCI of the serving cell may be transmitted, i.e., a PRACH for the same or another PCI as the PCI associated with the reception of the PDCCH order may be triggered.

[0222] As an example, based on the reception of the PDCCH order associated with the PCI of the serving cell, the PRACH associated with the PCI of the serving cell or an additional PCI may be transmitted.

[0223] As an example, based on the reception of the PDCCH order associated with the additional PCI, the PRACH associated with the additional PCI or the PCI of the serving cell may be transmitted.

[0224] The PDCCH order may be based on Downlink Control Information (DCI). That is, DCI including information regarding the PDCCH order may be referred to as a PDCCH order. For example, the DCI may include information to trigger a PRACH related to the PCI or the additional PCI.

[0225] The method may further include receiving configuration information related to CORESETs. Specifically, the terminal may receive configuration information related to control resource sets (CORESETs) from the base station. Based on the configuration information related to the CORESETs, i) a first CORESET related to a first CORESET pool index and ii) a second CORESET related to a second CORESET pool index are configured. Different CORESET pool indexes may be associated with different physical cell IDs. A CORESET related to one CORESET pool index may be associated with the physical cell ID of a serving cell, and a CORESET related to another CORESET pool index may be associated with another physical cell ID.

[0226] As an example, the first CORESET pool index may be associated with the PCI of the serving cell. The second CORESET pool index may be associated with the additional PCI. Furthermore, as described above, the PCI of the serving cell is associated with the first TAG, and the additional PCI is associated with the second TAG. Thus, the first CORESET pool index may be associated with the first TAG. The second CORESET pool index may be associated with the second TAG.

[0227] The configuration information related to the CORESETs can be based on a PDCCH-config that includes a list of CORESETs (controlResourceSetToAddModList).

[0228] Each TAG has an association indicated by the tag-Id-ptrr. Specifically, a first TAG may have an association with a first TCI state associated with the first CORESET. The second TAG may have an association with a second TCI state associated with the second CORESET.

[0229] The method may further include receiving configuration information related to a TAG, in which the terminal receives the configuration information related to the TAG from a base station. The configuration information related to the TAG (e.g., TAG-Config in Table 7) may include information related to the first TAG and the second TAG.

[0230] The operations based on the above-described steps S310 to S330, the PDCCH order receiving step, the CORESETs related configuration information receiving step, and the TAG related configuration information receiving step may be realized by the device in Fig. 5. For example, terminal 200 may control one or more transceivers 230 and / or one or more memories 240 to perform operations based on steps S310 to S330, the PDCCH order receiving step, the CORESETs related configuration information receiving step, and the TAG related configuration information receiving step.

[0231] The above-described embodiment will now be described in detail from the perspective of the operation of the base station.

[0232] Regarding S410 to S430, which will be described later, a step of transmitting a PDCCH order, a step of transmitting configuration information related to CORESETs, and a step of transmitting configuration information related to TAGs, duplicated descriptions will be omitted in consideration of the correspondences with S310 to S330, a step of receiving a PDCCH order, a step of receiving configuration information related to CORESETs, and a step of receiving configuration information related to TAGs, described in Fig. 3. In other words, specific descriptions of base station operations, which will be described later, can be replaced with the descriptions / embodiments of Fig. 3 corresponding to the operations.

[0233] For example, the description / embodiment of S310 to S330 in FIG. 3 can be further applied to the base station operations of S410 to S430 described below.

[0234] As an example, the descriptions / embodiments of the PDCCH order receiving step, the CORESETs related configuration information receiving step, and the TAG related configuration information receiving step can be further applied to the base station operations of the PDCCH order transmitting step, the CORESETs related configuration information transmitting step, and the TAG related configuration information transmitting step described below.

[0235] FIG. 4 is a flowchart illustrating a method performed by a base station according to another embodiment of the present disclosure.

[0236] Referring to FIG. 4, a method performed by a base station in another embodiment herein includes a configuration information transmitting step S410, a PRACH receiving step S420, and an RAR transmitting step S430.

[0237] At S410, the base station transmits configuration information to the terminal.

[0238] In S420, the base station receives a physical random access channel (PRACH) from the terminal based on the start of the random access procedure.

[0239] At S430, the base station transmits a Random Access Response (RAR) to the terminal based on a window associated with the RAR.

[0240] The method may further include a PDCCH order transmission step, in which the base station transmits a Physical Downlink Control Channel (PDCCH) order to the terminal. The random access procedure may be initiated by the PDCCH order. In this case, the PDCCH order may trigger a RACH procedure related to the PCI or the additional PCI of the serving cell.

[0241] The method may further include transmitting configuration information related to CORESETs. Specifically, the base station may transmit configuration information related to control resource sets (CORESETs) to the terminal.

[0242] The method may further include a step of transmitting configuration information related to a TAG, in which the base station transmits the configuration information related to the TAG to the terminal.

[0243] The operations based on the above-described steps S410 to S430, the PDCCH order transmission step, the CORESETs-related configuration information transmission step, and the TAG-related configuration information transmission step, can be realized by the apparatus of Fig. 5. For example, the base station 100 can control one or more transceivers 130 and / or one or more memories 140 to perform the operations based on steps S410 to S430, the PDCCH order transmission step, the CORESETs-related configuration information transmission step, and the TAG-related configuration information transmission step.

[0244] An apparatus to which the embodiments of the present specification can be applied (an apparatus that implements the methods / operations according to the embodiments of the present specification) will be described below with reference to FIG.

[0245] FIG. 5 is a diagram illustrating the configuration of a first device and a second device according to an embodiment of the present specification.

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

[0247] The processor 110 performs baseband-related signal processing and may include an upper layer processing unit 111 and a physical layer processing unit 115. The upper layer processing unit 111 may process operations of the MAC layer, the RRC layer, or higher layers. The physical layer processing unit 115 may process operations of the PHY layer. For example, when the first device 100 is a base station device in base station-terminal communication, the physical layer processing unit 115 may perform uplink reception signal processing, downlink transmission signal processing, etc. For example, when the first device 100 is a first terminal device in terminal-terminal communication, the physical layer processing unit 115 may perform downlink reception signal processing, uplink transmission signal processing, sidelink transmission signal processing, etc. In addition to performing baseband-related signal processing, the processor 110 may also control the overall operation of the first device 100.

[0248] The antenna unit 120 may include one or more physical antennas, and when multiple antennas are included, it may support MIMO transmission and reception. The transceiver 130 may include an RF (Radio Frequency) transmitter and an RF receiver. The memory 140 may store information processed by the processor 110, as well as software, an operating system, applications, etc. related to the operation of the first device 100, and may also include components such as buffers.

[0249] The processor 110 of the first device 100 can be configured to implement the operation of a base station in base station-terminal communication (or the operation of a first terminal device in terminal-terminal communication) in the embodiments described in this disclosure.

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

[0251] The processor 210 performs baseband-related signal processing and may include an upper layer processing unit 211 and a physical layer processing unit 215. The upper layer processing unit 211 can process operations of the MAC layer, the RRC layer, or higher layers. The physical layer processing unit 215 can process operations of the PHY layer. For example, when the second device 200 is a terminal device in base station-terminal communication, the physical layer processing unit 215 can perform downlink reception signal processing, uplink transmission signal processing, etc. For example, when the second device 200 is a second terminal device in terminal-terminal communication, the physical layer processing unit 215 can perform downlink reception signal processing, uplink transmission signal processing, sidelink reception signal processing, etc. In addition to performing baseband-related signal processing, the processor 210 can also control the overall operation of the second device 200.

[0252] The antenna unit 220 may include one or more physical antennas, and when multiple antennas are included, it may support MIMO transmission and reception. The transceiver 230 may include an RF transmitter and an RF receiver. The memory 240 may store information processed by the processor 210, as well as software, an operating system, applications, etc. related to the operation of the second device 200, and may also include components such as buffers.

[0253] The processor 210 of the second device 200 may be configured to implement the operation of a terminal in base station-terminal communication (or the operation of a second terminal device in terminal-terminal communication) in the embodiments described in this disclosure.

[0254] In the operation of the first device 100 and the second device 200, the matters described in the examples of the present disclosure regarding the base station and terminal in base station-terminal communication (or the first terminal and second terminal in terminal-terminal communication) can be equally applied, and duplicate explanations will be omitted.

[0255] Here, the wireless communication technology implemented by the devices 100 and 200 of the present disclosure may include not only LTE, NR, and 6G, but also Narrowband Internet of Things (NB-IoT) for low-power communication. For example, the NB-IoT technology is an example of a Low Power Wide Area Network (LPWAN) technology, and can be implemented by standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the aforementioned names.

[0256] Additionally or alternatively, the wireless communication technology implemented in the devices 100 and 200 of the present disclosure may perform communication based on LTE-M technology. For example, LTE-M technology is an example of LPWAN technology and is referred to by various names such as enhanced machine type communication (eMTC). For example, LTE-M technology may be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above names.

[0257] Additionally or alternatively, the wireless communication technology implemented in the devices 100 and 200 of the present disclosure may include at least one of ZigBee (registered trademark), Bluetooth (registered trademark), and a Low Power Wide Area Network (LPWAN), which consider low-power communication, but is not limited to the aforementioned names. For example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be called by various names.

Claims

1. 1. A method performed by a terminal in a wireless communication system, comprising: receiving configuration information; The configuration information includes: i) a first random access channel (RACH) configuration associated with a physical cell identity (PCI) of a serving cell; and ii) a second random access channel (RACH) configuration associated with an additional PCI; transmitting a Physical Random Access Channel (PRACH) based on the initiation of a Random Access procedure; receiving a Random Access Response (RAR) based on a window associated with the RAR; The RAR is associated with one of two Timing Advance Groups (TAGs), the PCI of the serving cell is associated with a first TAG of the two TAGs, and an additional PCI is associated with a second TAG of the two TAGs; a length of the window is determined based on a response window parameter associated with the first RACH configuration based on which the PRACH is associated with the PCI of the serving cell; The method of claim 1, wherein the length of the window is determined based on a response window parameter associated with the second RACH configuration, based on which the PRACH is associated with the additional PCI.

2. The method according to claim 1, wherein the RAR is received based on a Physical Downlink Control Channel (PDCCH) and a Physical Downlink Shared Channel (PDSCH).

3. the serving cell is a primary cell or a secondary cell, The method of claim 2, wherein the PDCCH is received based on a Type 1-PDCCH Common Search Space (CSS) set configured for the primary cell.

4. A transport block is received on a Physical Downlink Shared Channel (PDSCH) scheduled based on a DCI format 1_0 (DCI format 1_0) associated with the PDCCH; The method of claim 3, wherein the RAR is based on a transport block.

5. receiving a Physical Downlink Control Channel (PDCCH) order; The method of claim 1, wherein the random access procedure is initiated by the PDCCH order.

6. The method of claim 5, wherein the PRACH associated with the PCI or the additional PCI of the serving cell is transmitted based on the reception of the PDCCH order.

7. The method of claim 5, wherein the PDCCH order is based on Downlink Control Information (DCI).

8. 2. The method of claim 1, wherein the response window parameter indicates a number of slots.

9. The method of claim 1 , wherein the RAR includes a Timing Advance Command applied to the first TAG or the second TAG.

10. The first Nth ＴＡ、ｏｆｆｓｅｔ and 2N ＴＡ、ｏｆｆｓｅｔ is set, The first N ＴＡ、ｏｆｆｓｅｔ is associated with the first TAG, and the second N ＴＡ、ｏｆｆｓｅｔ The method of claim 1 , wherein: is associated with the second TAG.

11. receiving configuration information related to control resource sets (COntrol REsource SETs, CORESETs); Based on the configuration information associated with the CORESETs, i) a first CORESET associated with a first CORESET pool index and ii) a second CORESET associated with a second CORESET pool index are configured; the first CORESET pool index is associated with a first TAG; The method of claim 1 , wherein the second CORESET pool index is associated with the second TAG.

12. In a terminal operating in a wireless communication system, One or more transceivers. one or more processors; coupled to the one or more processors; one or more memories for storing instructions, The instructions, when executed by the one or more processors, configure the one or more processors to perform all steps of the method according to any one of claims 1 to 11.

13. 1. An apparatus comprising one or more memories and one or more processors operatively connected to said one or more memories, The one or more memories store instructions that, when executed by the one or more processors, configure the one or more processors to perform all steps of the method according to any one of claims 1 to 11.

14. One or more non-transitory computer-readable media storing instructions, One or more non-transitory computer-readable media, characterized in that the instructions executable by one or more processors configure the one or more processors to perform all the steps of the method according to any one of claims 1 to 11.

15. 1. A method performed by a base station in a wireless communication system, comprising: transmitting the configuration information; The configuration information includes: i) a first Random Access Channel (RACH) configuration associated with a Physical Cell Identity (PCI) of a serving cell; and ii) a second Random Access Channel (RACH) configuration associated with an additional PCI; receiving a Physical Random Access CHannel (PRACH) based on the initiation of a Random Access procedure; transmitting a Random Access Response (RAR) based on a window associated with the RAR; The RAR is associated with one of two Timing Advance Groups (TAGs), the PCI of the serving cell is associated with a first TAG of the two TAGs, and an additional PCI is associated with a second TAG of the two TAGs; a length of the window is determined based on a response window parameter associated with the first RACH configuration based on which the PRACH is associated with the PCI of the serving cell; The method of claim 1, wherein the length of the window is determined based on a response window parameter associated with the second RACH configuration, based on which the PRACH is associated with the additional PCI.

16. 1. A base station operating in a wireless communication system, comprising: one or more transceivers; the one or more processors; one or more memories coupled to the one or more processors and configured to store instructions; 16. A base station, wherein the instructions, when executed by the one or more processors, configure the one or more processors to perform all steps of the method according to claim 15.

Images