Method and device for transmitting and receiving prach

Abstract

A method according to an embodiment of the present specification comprises the steps of: receiving DCI related to a PDCCH order; and transmitting a PRACH. Transmission power for the PRACH is determined on the basis of a pathloss (PL), and the PL is determined on the basis of an RS. The DCI comprises a pathloss offset indicator field related to a pathloss offset for the PRACH. The RS is determined on the basis of at least one of: i) the number of at least one indicated TCI state; ii) a value of the pathloss offset indicator field; and iii) whether the pathloss offset is configured in the at least one indicated TCI state.

Description

Method and device for transmitting and receiving PRACH

[0001] This specification relates to a method and apparatus for PRACH transmission and reception.

[0002] Mobile communication systems were developed to provide voice services while ensuring user mobility. However, mobile communication systems have expanded their scope to include data services as well as voice. Currently, due to the explosive increase in traffic leading to resource shortages and users demanding higher-speed services, more advanced mobile communication systems are required.

[0003] The requirements for next-generation mobile communication systems largely include the ability to accommodate explosive data traffic, a dramatic increase in transmission rates per user, a significantly increased number of connected devices, very low end-to-end latency, and high energy efficiency. To achieve this, various technologies are being researched, such as dual connectivity, massive multiple input multiple output (MMIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking.

[0004] Meanwhile, Multi-Transmission Reception Point (M-TRP) operation for uplink and / or downlink transmission and reception is defined. Regarding M-TRP operation, a scenario (DL / UL asymmetric scenario) is being discussed in which an uplink reception point (UL Rx point) supporting only uplink reception without a downlink transmission chain is additionally deployed in a macro cell to reduce base station installation costs.

[0005] When transmitting an uplink to a UL Rx point, a PL-RS mismatch may occur due to the absence of a DL RS. To resolve this issue, it was agreed to utilize a PL offset. Specifically, it was agreed to use the DL RS of the macro cell TRP as the PL-RS, and to perform uplink transmission by applying the PL offset value set in the UL-related TCI state to the PL compensation value.

[0006] Meanwhile, it was agreed to use the PL offset value for PRACH for TA acquisition (e.g., PRACH related to a random access procedure initiated by a PDCCH order). However, since it has not been specified which RS to use as PL-RS for the said PRACH, ambiguity may arise in base station / terminal operations and PL-RS discrepancies may occur.

[0007] The purpose of this specification is to propose a method for determining a PL-RS (e.g., RS related to the determination of pathloss) that is more suitable for the PRACH by considering whether to apply a PL offset.

[0008] The technical problems to be solved in this specification are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which this invention belongs from the description below.

[0009] A method according to one embodiment of the present specification for solving the aforementioned technical problem includes the steps of receiving Downlink Control Information (DCI) related to a Physical Downlink Control Channel (PDCCH) order and transmitting a Physical Random Access Channel (PRACH). The transmission power for the PRACH is determined based on a PathLoss (PL), and the PL is determined based on a Reference Signal (RS). The DCI includes a PathLoss offset indicator field related to a pathloss offset for the PRACH. The RS is characterized by being determined based on at least one of i) the number of at least one indicated Transmission Configuration Indicator (TCI, state), ii) the value of the PathLoss offset indicator field, and iii) whether the pathloss offset is set within the at least one indicated TCI state.

[0010] Accordingly, by considering at least one of the above i) to iii), an RS that is more suitable for PRACH transmission power can be utilized as an RS for determining path loss (PathLoss, PL).

[0011] According to an embodiment of the present specification, when a terminal is performing an asymmetric M-TRP operation in a specific CC / BWP, the TA value for the UL Rx point can be obtained / managed by utilizing a PDCCH ordered PRACH.

[0012] Under the conventional method, due to the aforementioned ambiguity in terminal operation / PL RS mismatch, transmission power may be used at a level lower or higher than the actual required power. In such cases, the error rate increases, leading to frequent retransmissions or a reduction in overall cell capacity due to interference. According to the embodiments of this specification, the transmission power of the PDCCH ordered PRACH can be determined based on a path loss that is more suitable for the UL Rx point. Therefore, by optimizing the transmission power of the PDCCH ordered PRACH, a combination of technical effects can be provided, such as improved signal quality, interference suppression, energy savings, increased system efficiency, and ensured equipment stability.

[0013] The effects obtainable in this specification are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art from the description below.

[0014] Figure 1 is a diagram illustrating an example of a conventional macro cell layout.

[0015] Figure 2 is a drawing illustrating an example of an uplink dense arrangement.

[0016] Figure 3 is a diagram illustrating an uplink resource allocation method.

[0017] Figure 4 is a diagram showing the average spectral efficiency (SE) performance gain of a UE dense deployment compared to a macro cell.

[0018] Figure 5 is a diagram showing the performance gain of cell edge spectral efficiency (SE) compared to macro cells in a UE dense deployment.

[0019] Figure 6 is a diagram showing the difference in path loss between the UE and the macro cell and between the UE and the UL RX point.

[0020] Figure 7 illustrates a MAC payload for a random access response.

[0021] FIG. 8 is a flowchart illustrating a method according to one embodiment of the present specification.

[0022] FIG. 9 is a flowchart illustrating a method according to another embodiment of the present specification.

[0023] FIG. 10 is a drawing showing the configuration of a first device and a second device according to an embodiment of the present specification.

[0024] Hereinafter, preferred embodiments according to the present specification 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 specification and is not intended to represent the only embodiment in which the invention according to the present specification can be practiced. The following detailed description includes specific details to provide a complete understanding of the present specification.

[0025] In some cases, to avoid obscuring the concept of the invention according to the embodiments of this specification, known structures and devices may be omitted or illustrated in the form of a block diagram focusing on the core functions of each structure and device.

[0026] In the following, the downlink (DL) refers to communication from a base station to a terminal, and the uplink (UL) refers to communication from a terminal to a 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 be referred to as the first communication device and the terminal as the second communication device. The base station (BS) may be replaced by terms such as fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), Access Point (AP), network (5G network), AI system, RSU (road side unit), vehicle, robot, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, the terminal may be fixed or mobile and may be replaced with terms such as UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), MTC (Machine-Type Communication) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, robot, AI module, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device.

[0027] Control information transmitted by a terminal to a base station via an uplink or received by a terminal from a base station includes downlink / uplink ACK / NACK signals, CQI (Channel Quality Indicator), PMI (Precoding Matrix Index), RI (Rank Indicator), etc. In the case of a 3GPP LTE system, the terminal may transmit the aforementioned control information, such as CQI / PMI / RI, via PUSCH and / or PUCCH.

[0028] Table 1 shows an example of the DCI format in an NR system.

[0029]

[0030] Referring to Table 1, DCI formats 0_0, 0_1, and 0_2 may include resource information related to PUSCH scheduling (e.g., UL / SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), transmission block (TB) related information (e.g., MCS, NDI, RV, etc.), HARQ related information (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), multi-antenna related information (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), and power control information (e.g., PUSCH power control, etc.), and the control information included in each DCI format may be predefined.

[0031] DCI format 0_0 is used for scheduling PUSCH in a single cell. The information contained in DCI format 0_0 is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0032] DCI format 0_1 ​​is used to instruct a terminal on the scheduling of one or more PUSCHs in a cell, or on configured grant (CG) downlink feedback information. The information contained in DCI format 0_1 ​​is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI.

[0033] DCI format 0_2 is used for scheduling PUSCH in a single cell. The information contained in DCI format 0_2 is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI.

[0034] Next, DCI formats 1_0, 1_1, and 1_2 may include resource information related to PDSCH scheduling (e.g., frequency resource allocation, time resource allocation, VRB-PRB mapping, etc.), transmission block (TB) related information (e.g., MCS, NDI, RV, etc.), HARQ related information (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), multi-antenna related information (e.g., antenna port, TCI, SRS request, etc.), and PUCCH related information (e.g., PUCCH power control, PUCCH resource indicator, etc.), and the control information included in each DCI format may be predefined.

[0035] DCI format 1_0 is used for scheduling PDSCH in a single DL cell. The information contained in DCI format 1_0 is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0036] DCI format 1_1 is used for scheduling PDSCH in a single cell. The information contained in DCI format 1_1 is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0037] DCI format 1_2 is used for PDSCH scheduling in a single cell. The information contained in DCI format 1_2 is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI.

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

[0039] The M-TRP transmission method, in which M TRPs transmit data to a single terminal (User equipment, UE), can be broadly classified into two types: i) eMBB M-TRP transmission, which is a method to increase the transmission rate, and ii) URLLC (Ultra Reliable and Low Latency Communication) M-TRP transmission, which is a method to increase the reception success rate and reduce latency.

[0040] MTRP URLLC

[0041] In the methods proposed herein, DL MTRP-URLLC refers to the transmission of the same data / DCI by multiple TRPs using different layer / time / frequency resources. For example, TRP 1 transmits the same data / DCI from resource 1, and TRP 2 transmits the same data / DCI from resource 2. A UE configured with the DL MTRP-URLLC transmission method receives the same data / DCI using different layer / time / frequency resources. At this time, the UE is instructed by the base station on which QCL RS / type (e.g., DL TCI state) to use at the layer / time / frequency resource receiving the same data / DCI. For example, if the same data / DCI is received from resource 1 and resource 2, the UE is instructed on the DL TCI state used by resource 1 and the DL TCI state used by resource 2. Since the UE receives the same data / DCI through resource 1 and resource 2, high reliability can be achieved. These DL MTRP URLLCs can be applied to PDSCH / PDCCH.

[0042] Conversely, UL MTRP-URLLC refers to a scenario where multiple TRPs receive the same data / UCI from a single UE using different layer / time / frequency resources. For example, TRP 1 receives the same data / UCI from the UE via Resource 1, and TRP 2 receives it via Resource 2; subsequently, the received data / UCI is shared through a 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 Tx power (e.g., UL TCI state) to use from the layer / time / frequency resource transmitting the same data / UCI. For instance, if the same data / UCI is transmitted from both Resource 1 and Resource 2, the UE is instructed on the UL TCI state to be used by Resource 1 and the UL TCI state to be used by Resource 2. These UL MTRP URLLCs can be applied to PUSCH / PUCCH.

[0043] S-DCI or M-DCI-based MTRP transmission

[0044] In addition, 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, where each TRP transmits different DCIs, and ii) S-DCI (single DCI) based M-TRP transmission, where a single TRP transmits a DCI. For example, in the case of S-DCI, since all scheduling information for the data transmitted by the M TRP must be conveyed through a single DCI, it can be used in an ideal BH (ideal BackHaul) environment where dynamic cooperation between two TRPs is possible.

[0045] Rel-16 NR MTRP transmission

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

[0047] - Rel-16 S-DCI-based MTRP PDSCH

[0048] S-DCI-based MTRP PDSCH transmission can be further refined to utilize one of the SDM, FDM, or TDM methods. In the case of SDM, a single TB is transmitted across multiple layers, but layers belonging to different DMRS and CDM groups are transmitted via different Tx beams (i.e., QCL RS or TCI states). This allows for an increase in the number of layers compared to the existing STRP transmission method, thereby improving transmission capacity. Additionally, when a single TB is transmitted across multiple layers, some layers are sent to TRP 1 and others to TRP 2, which can enhance channel reliability through diversity gain.

[0049] For FDM, two schemes, scheme 2a and scheme 2b, are supported. Scheme 2a is a method in which a single TB is transmitted via multi-RB, but RBs belonging to different RB groups are transmitted to different Tx beams (e.g., QCL RS or TCI state). Scheme 2b is a method in which the same TB is transmitted to different RB groups, but RBs belonging to different RB groups are transmitted to different Tx beams (e.g., QCL RS or TCI state).

[0050] In the case of TDM, two methods, scheme 3 and scheme 4, are supported. Scheme 4 (=interslot TDM) is a method in which the same TB is repeatedly transmitted across multiple slots, but slots belonging to different slot groups are transmitted to different Tx beams (e.g., QCL RS or TCI state). In contrast, Scheme 3 (=intraslot TDM) is a method in which the same TB is repeatedly transmitted across multiple OFDM symbol groups, but some OFDM symbol groups and the remaining OFDM symbol groups are transmitted to different Tx beams (e.g., QCL RS or TCI state).

[0051] - R16 M-DCI based MTRP PDSCH

[0052] M-DCI-based MTRP PDSCH transmission is a method in which each TRP schedules and transmits a PDSCH via DCI. In other words, TRP 1 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, two PDSCHs are received for the same RE, thereby increasing resource efficiency and transmission capacity. To achieve this, the Rel-16 standard introduced a CORESET pool, which is a group of multiple Control Resource Sets (CORESETs). TRP 1 transmits a PDCCH through a CORESET belonging to CORESET pool 0, and TRP 1 also transmits the PDSCH scheduled by that PDCCH. Similarly, TRP 2 transmits a PDCCH through a CORESET belonging to CORESET pool 1, and TRP 2 also transmits the PDSCH scheduled by that PDCCH. Similarly, for PUSCH, a specific TRP can schedule PUSCH transmissions to a UE through the CORESET belonging to each COERSET pool. For PUCCH, some PUCCH resources are scheduled by TRP 1 to receive UCIs, while the remaining PUCCH resources are scheduled by TRP 2 to receive UCIs. In the case of PUSCH or PUCCH, the channels scheduled / used by each TRP are TDMed together to prevent overlap, so an increase in transmission capacity cannot be expected; however, the UE can send independent PUSCH / PUCCH to TRP 1 and TRP 2, respectively.

[0053] Additionally, the UE may recognize a PUSCH (or PUCCH) scheduled by the DCI received from a different CORESET (or a CORESET belonging to a different CORESET group) as a PUSCH (or PUCCH) transmitted to a different TRP, or as a PUSCH (or PUCCH) of a different TRP. Furthermore, the method for UL transmission (e.g., PUSCH / PUCCH) transmitted to a different TRP can be applied in the same way to UL transmission (e.g., PUSCH / PUCCH) transmitted to a different panel belonging to the same TRP.

[0054] The CORESET group ID (or COERSET pool index having the same meaning) described or mentioned in this specification may refer to an index / identification information (e.g., ID) for distinguishing CORESETs for each TRP / panel. Furthermore, a CORESET group may be a group or union of CORESETs distinguished by the index / identification information (e.g., ID) for distinguishing CORESETs for each TRP / panel, or by the said CORESET group ID. For example, the CORESET group ID may be specific index information defined within the CORESET configuration. For example, the CORESET group may be set / indicated / defined by an index defined within the CORESET configuration for each CORESET. and / or the CORESET group ID may refer to an index, identification information, indicator, etc., for distinguishing / identifying CORESETs configured / associated with each TRP / panel, and the CORESET group ID described / mentioned in this specification may be replaced and expressed with a specific index, specific identification information, or specific indicator for distinguishing / identifying CORESETs configured / associated with each TRP / panel. The said CORESET group ID, i.e., the specific index, specific identification information, or specific indicator for distinguishing / identifying CORESETs configured / associated with each TRP / panel, may be configured / indicated through higher layer signaling (e.g., RRC signaling), L2 signaling (e.g., MAC-CE), L1 signaling (e.g., DCI), etc.For example, PDCCH detection for each TRP / panel may be configured / instructed to be performed at the level of the corresponding CORESET group, and / or uplink control information (e.g., CSI, HARQ-A / N, SR) and / or uplink physical channel resources (e.g., PUCCH / PRACH / SRS resources) may be configured / instructed to be managed / controlled separately at the level of the corresponding CORESET group for each TRP / panel, and / or HARQ A / N (process / retransmission) for PDSCH / PUSCH, etc. scheduled at the level of the corresponding CORESET group for each TRP / panel may be managed.

[0055] For example, the upper-level parameter ControlResourceSet IE (information element) is used to set a time / frequency control resource set (CORESET). For instance, the control resource set (CORESET) may be 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 settings of the CORESET, and TCI information related to the CORESET. For instance, the index of the CORESET pool (e.g., CORESETPoolIndex) may be set to 0 or 1. In the above description, the CORESET group may correspond to the CORESET pool, and the CORESET group ID may correspond to the CORESET pool index (e.g., CORESETPoolIndex). A ControlResourceSet (e.g., CORESET) can be configured via upper-level signaling (e.g., RRC).

[0056] Rel-17 NR MTRP

[0057] The Rel-17 NR standard supports MTRP PDCCH repeated transmission, MTRP PDCCH / PDSCH SFN (Single Frequency Network) transmission, S-DCI-based MTRP PUSCH repeated transmission, and single PUCCH resource-based MTRP PUCCH repeated transmission. All of these transmission techniques involve the repeated transmission of the same contents (e.g., DCI, UL TB, or UCI) through URLLC target enhancement to increase reliability. In the case of MTRP PDCCH repeated transmission, PDCCHs are transmitted repeatedly via TDM or FDM; MTRP PDCCH / PDSCH SFN is transmitted repeatedly over the same time, frequency, and layer; S-DCI-based MTRP PUSCH repeated transmission is transmitted via TDM; and single PUCCH resource-based MTRP PUCCH repeated transmission is transmitted via TDM.

[0058] - Rel-17 S-DCI based MTRP PDCCH recurrence

[0059] In the Rel-17 NR standard, for MTRP PDCCH recurring transmission, multiple CORESETs with different TCI states (e.g., different QCL RS) are configured for the UE, and multiple SS sets are configured, each connected to the respective CORESETs. The base station can instruct / configure the UE that the SS set connected to one CORESET and the SS set connected to another CORESET are linked for recurring transmission, and the UE can know that the PDCCH candidates of the corresponding SS set are being recurring.

[0060] For example, two CORESETs, CORESET 0 and 1, are configured for the UE, and CORESET 0 and 1 are connected to SS set 0 and 1, respectively, and SS set 0 and 1 may be linked. The UE can recognize that the PDCCH candidate of SS set 0 and the PDCCH candidate of SS set 1 have repeatedly transmitted the same DCI, and through a specific rule, it can recognize that a specific PDCCH candidate of SS set 0 and a specific PDCCH candidate of SS set 1 are a pair configured to repeatedly transmit the same DCI. These two PDCCH candidates are called linked PDCCH candidates, and the UE can successfully decode the corresponding DCI if it correctly receives either of the two PDCCH candidates. However, when receiving a PDCCH candidate of SS set 0, the QCL RS of the TCI state of COERSET 0 connected to SS set 0 (i.e., DL beam) is used, and when receiving a PDCCH candidate of SS set 1, the QCL RS of the TCI state of COERSET 1 connected to SS set 1 (e.g., DL beam) is used, thereby receiving the linked PDCCH candidate in a different beam.

[0061] - Rel-17 MTRP SFN PDCCH

[0062] As a special case of MTRP PDCCH repeated transmission, multiple TRPs can repeatedly transmit the same DCI through the same time / frequency / DMRS port, which can be called SFN PDCCH transmission. However, for SFN PDCCH transmission, the base station sets multiple TCI states in a single CORESET instead of setting multiple CORESETs with different TCI states. When the UE receives a PDCCH candidate through the SS set connected to that single CORESET, it attempts to estimate the channel of the PDCCH DMRS and decode it by utilizing all of the corresponding multiple TCI states.

[0063] - Rel-17 MTRP SFN PDSCH

[0064] In the above MTRP PDSCH repetitive transmission, the two TRPs repetitively transmit the corresponding channel to different resources. However, as a special case, if the resources used by the two TRPs are identical (e.g., when the same channel is repetitively transmitted through the same frequency, time, and layer (=DMRS port)), the reliability of the corresponding channel can be improved. In this case, since the resources for the repetitively transmitted same channel are not distinguished, they are combined and received in the air, so they are recognized as a single channel from the receiver's perspective. In the Rel-17 NR standard, two DL TCI states for PDSCH DMRS reception can be configured for PDSCH SFN transmission.

[0065] - Rel-17 S-DCI based MTRP PUSCH repetitive transmission

[0066] In the Rel-17 NR standard, the base station sets two SRS sets for the UE to perform S-DCI-based MTRP PUSCH transmission, and each set is used to indicate the UL Tx port and UL beam / QCL information for TRP 1 and TRP 2, respectively. Additionally, the base station indicates SRS resources per SRS set through two SRS resource indicator (SRI) fields per DCI, and can indicate up to two PC parameter sets. For example, the first SRI field can indicate the SRS resource and PC parameter set defined in set 0, and the second SRI field can indicate the SRS resource and PC parameter set defined in set 1. The UE receives the UL Tx port, PC parameter set, and UL beam / QCL information for TRP 1 through the first SRI field, and performs PUSCH transmission at the TO corresponding to set 0. Likewise, the UE is instructed by the UL Tx port, PC parameter set, and UL beam / QCL information toward TRP 2 through the second SRI field, and performs PUSCH transmission at the TO corresponding to set 1.

[0067] - Rel-17 single PUCCH resource based MTRP PUCCH repeated transmission

[0068] In the Rel-17 NR standard, for single PUCCH resource-based MTRP PUCCH transmission, the base station activates / configures two spatial relation infos for the UE in a single PUCCH resource (activates / configures two PC (power control) parameter sets in the case of FR1), and when a UL UCI is transmitted through the said PUCCH resource, each spatial relation info is used to indicate the spatial relation info toward TRP 1 and TRP 2, respectively. For example, through the value indicated in the first spatial relation info, the UE is instructed on the Tx beam / PC parameters toward TRP 1, and the UE uses this information to perform PUCCH transmission at the TO corresponding to TRP 1. Similarly, through the value indicated in the second spatial relation info, the UE is instructed on the Tx beam / PC parameters toward TRP 2, and the UE uses this information to perform PUCCH transmission at the TO corresponding to TRP 2.

[0069] At the Rel-17 standardization meeting, the configuration method was enhanced to allow two spatial relation infos to be configured in a PUCCH resource for MTRP PUCCH iterative transmission. In other words, if PC (power control) parameters such as PLRS, Alpha, P0, and Closed loop index are configured in each spatial relation info, a spatial relation RS can be configured. Consequently, PC information and spatial relation RS information corresponding to two TRPs can be configured through the two spatial relation infos, and the UE transmits to the PUCCH using the first spatial relation info in TO 1, and transmits to the PUCCH of the same UCI (e.g., CSI, ACKNAK, SR) using the second spatial relation info in TO 2. Hereinafter, a PUCCH resource configured with two spatial relation infos is named the MTRP PUCCH resource, and a PUCCH resource configured with one spatial relation info is named the STRP PUCCH resource.

[0070] TCI state / beam indication

[0071] In the methods proposed herein, the meaning of using (and / or mapping) a specific TCI state (or TCI) when receiving data / DCI / UCI for a certain frequency / time / space resource may mean, in the case of DL, that a channel is estimated from DMRS using the QCL type and QCL RS indicated by the corresponding DL TCI state in that frequency / time / space resource, and data / DCI is received / demodulated to the estimated channel. In the case of UL, it may mean that DMRS and data / UCI are transmitted / modulated using the Tx beam and / or Tx power indicated by the corresponding UL TCI state in that frequency / time / space resource.

[0072] The above UL TCI state contains information regarding the UE's Tx beam or Tx power, and instead of the TCI state, spatial relation info, etc., may be set for the UE through other parameters. The UL TCI state may be directly specified in the UL grant DCI, or it may refer to the spatial relation info of an SRS resource specified through the SRI field of the UL grant DCI. Alternatively, it may refer to an open-loop transmission power control (OL Tx power control) parameter connected to a value specified through the SRI field of the UL grant DCI. The above OL Tx power control parameter may include the following indices.

[0073] - Index j: An index to identify sets of Po and alpha values, which are Open Loop Parameters that can be set up to a maximum of 32 sets per cell.

[0074] - Index q_d: An index for identifying Downlink Reference Signal (DL RS) resources for Path Loss (PL) measurement, wherein up to 4 PL measurements are supported per cell.

[0075] - Index l: An index for identifying closed loop power control processes, wherein up to two processes are supported per cell.

[0076] Alternatively, in Rel-17 NR, UL TCI can be indicated via DL grant DCI.

[0077] For convenience of explanation, the proposed method is applied by assuming cooperative transmission / reception between 2 TRPs, but it can be extended to environments with 3 or more TRPs and also to multi-panel environments. Different TRPs may be recognized as different TCI states by the UE, and when the UE receives / transmits data / DCI / UCI using TCI state 1, it means that the UE has received / transmitted data / DCI / UCI from / to TRP 1.

[0078] In this specification, TO refers to i) each channel transmitted at different times when multiple channels are TDMed, ii) each channel transmitted to different frequencies / RBs when multiple channels are FDMed, and iii) each channel transmitted to different layer / beam / DMRS ports when multiple channels are SDMed. One TCI state is mapped to each TO. When the same channel is transmitted repeatedly, a complete DCI / data / UCI is transmitted in one TO, and the receiving end receives multiple TOs to increase the reception success rate.

[0079] Multiple uplink Rx points for UL dense deployment

[0080] Figure 1 is a diagram illustrating an example of a conventional macro cell layout.

[0081] Figure 2 is a drawing illustrating an example of an uplink dense arrangement.

[0082] Figure 3 is a diagram illustrating an uplink resource allocation method.

[0083] Figure 4 is a diagram showing the average spectral efficiency (SE) performance gain of a UE dense deployment compared to a macro cell.

[0084] Figure 5 is a diagram showing the performance gain of cell edge spectral efficiency (SE) compared to macro cells in a UE dense deployment.

[0085] Figure 6 is a diagram showing the difference in path loss between the UE and the macro cell and between the UE and the UL RX point.

[0086] Regarding the UL Rx point, the following discussion took place.

[0087] 3.1 Uplink Multiple Input Multiple Output (MIMO) Improvements

[0088] 3.1.1 Uplink Dense Deployment (UL dense deployment, UL receiving points)

[0089] In a traditional macro cell deployment, the UE communicates with the same cell for both downlink (DL) and uplink (UL) transmissions. As illustrated in FIG. 1, for a UE located at the cell edge, UL performance may be degraded due to large path loss and UE transmission power limitations. Small cell deployments can improve UL performance by reducing path loss, as well as DL performance; however, costs increase because more gNBs are required, and DL interference management becomes more severe. To simultaneously achieve cost / interference minimization and UL performance improvement, a dense UL deployment can be considered, as illustrated in FIG. 2. Since there are no DL transmission units (e.g., power amplifiers) at small UL receiving points (UL RX points), lower costs can be expected. Additionally, since there is no DL transmission from these UL receiving points, deployment management can be much easier. In this arrangement, the UE may receive DL transmissions from other cells (e.g., macro cells), and for the UL, a UL receiving point having smaller path loss and / or larger receive power from the UE may be selected to receive the UE's UL signal.

[0090] A system-level simulation was performed to evaluate the performance of uplink dense placement. Only uplink traffic is considered in the simulation. Within each macrocell, one to four small UL RX points are randomly placed. Detailed simulation assumptions are shown in Table A-1 of the Appendix. To utilize the performance of UL dense placement, UL multi-user scheduling is allowed, so that UL transmissions to different TRPs can be scheduled simultaneously as shown in FIG. 3. Additionally, interference from UEs within the same macrocell is also considered during the reception process of the simulation.

[0091] In uplink dense deployments, when a UL RX point is selected for UL reception for a specific UE, the Downlink Path Loss Reference Signal (PL-RS) is unavailable from that UL RX point; therefore, how the UE performs open-loop TPC must be considered. The most direct implementation method is to perform TPC for all UL reception points within the macrocell coverage using the PL-RS from the macrocell. However, considering that the path loss from the UE to the UL reception point is smaller than the path loss from the UE to the macrocell, the transmit power calculated at the UE may be higher than the value required at the UL reception point. In extreme cases, the receive power at the UL reception point may exceed the receiver's dynamic range. Therefore, more accurate power control (TPC) needs to be pursued. To investigate the necessity of such accurate TPC, an enhanced method using the actual path loss of each UL reception point was also evaluated. In summary, the following two cases were evaluated.

[0092] - Case 1 (baseline): The path loss of a macro cell is used for TPC for all UL receiving points within that macro cell coverage.

[0093] - Case 2 (Enhanced PL): When transmitting a UL to each UL receiving point, the path loss of that receiving point is used in the TPC.

[0094] The performance gains in average spectral efficiency (SE) and cell edge spectral efficiency (SE) provided by dense UL placement compared to macro cell placement are shown in Figures 4 and 5, respectively. By placing small UL receiving points, the average SE was improved by approximately 80% to 160%. When the number of small UL receiving points was 1 to 3, the performance gain in cell edge SE was also significant and appeared to be greater than 20%. However, when the number of small UL receiving points was 4, i.e., dense placement, the edge SE performance in Case 1 was worse than in the case with only macro cell placement due to high interference caused by inaccurate TPC. Furthermore, it is evident that in Case 1, performance did not improve as the number of TRPs increased. On the other hand, in Case 2 using the improved PL method, better UL SE performance could still be achieved near the cell edge, which led to an edge SE performance gain of 88% compared to macro cell placement.

[0095] Observation 1

[0096] With the placement of UL RX points, significant performance gains are observed in both average SE performance (up to +160%) and cell edge SE performance (up to +88%) compared to macro cell placement.

[0097] - As the density of UL RX points increases, the performance of the cell edge UE in Case 1 deteriorates, and when the number of UL RX points is 4, it becomes worse than the macro cell arrangement. However, in Case 2, where the improved PL method is applied, the performance gain of the cell edge UE is significantly improved, increasing up to 88%.

[0098] Simulation results show that the placement of UL RX points can improve the performance of both cell edge UEs and average UEs. Furthermore, accurate PL or TPC is important to guarantee the performance of cell edge UEs in UL dense placement. Although these results were evaluated in FR1, we believe that similar issues exist in FR2 as well. Therefore, we propose researching and standardizing methods to improve UL TPC for UL dense placement.

[0099] While some may think there could be other implementation methods to solve the TPC problem, no valid approach based on existing specifications is apparent at this stage. For example, the TPC equation includes a term determining the target power in RB units, which consists of the sum (p0 and / or alpha) of the cell-specific nominal target power and the UE-specific differential target power. Additionally, there is a closed-loop power control function that can dynamically direct power regulation via DCI. It could be argued that the problem can be solved by implementing p0 / alpha and / or closed-loop power control along with appropriate policies.

[0100] However, we believe that an approach based on these legacy features does not work well. First, we believe these parameters are already being utilized for other purposes. For example, a network can set a larger p0 value for UEs requiring higher communication priority. Therefore, if existing parameters are to be used for power tuning toward the UL RX point, the network must control those parameters based on entirely different policies simultaneously, which makes operations much more complex and, in some cases, may fail to achieve the goal of improving UL performance. Another issue is that when examining the power tuning range required between the macro cell and the UL RX point, the tuning range available in the existing method is insufficient. As illustrated in Figure 6, the difference in path loss between the “UE to macro cell” and the “UE to UL RX point” is significant, with the difference exceeding 15 dB for more than 50% of UEs. Given that the range of p0 is {-16..15}, proper tuning cannot be achieved by setting p0 alone. In addition, using only CL-PC is not appropriate, as more TPC instructions are required to adjust for large path loss differences, which ultimately leads to more frequent DCI instructions and large latency caused by CL-PC.

[0101] Observation 2

[0102] - When multiple UL RX points are placed within a single macro cell, the difference in path loss between different RX points may exceed 15 dB at 50% of the UE.

[0103] Neither p0 / alpha adjustment nor TPC instructions for CL-PC are suitable for adjusting this power difference.

[0104] In addition to improving UL TPC, UL Beam Management (BM) should also be studied. In FR2, beam correspondence is assumed in the UE, and the optimal UL beam can be derived from DL Beam Management (DL BM). However, in dense UL deployments, DL RS does not exist from the UL RX point; therefore, research is needed on how a UE with beam correspondence can acquire the optimal UL beam for a specific UL RX point.

[0105] Proposal 1

[0106] - Support UL dense deployment by researching improvements to UL TPC, UL BM, etc.

[0107] According to 3GPP standards up to NR Rel-18, multiple TRP (M-TRP) operations are defined for uplink / downlink transmission and reception of terminals. These M-TRP operation scenarios are classified into single-DCI (S-DCI) based M-TRP operations, where a specific TRP transmits the control signal, and multi-DCI (M-DCI) based M-TRP operations, where multiple TRPs transmit the control signal. In NR following Rel-18, discussions are underway regarding a scenario in which multiple UL Rx only TRPs (hereinafter “UL Rx points”) are additionally deployed in macro cells to compensate for terminal UL coverage. These UL Rx points can perform only UL reception without being equipped with a DL Tx chain to reduce base station installation costs. In this case, since the UL Rx point cannot transmit a DL reference signal (DL RS), the terminal cannot determine the DL slot boundary (or DL ​​reference point) for TA application to the UL Rx point. Additionally, because there is no SSB transmission, ambiguity arises in terminal operation regarding how to perform RACH transmission for TA acquisition. Furthermore, even if the terminal has beam correspondence capability, the problem arises that the base station cannot set the DL RS as the UL transmit beam reference RS because the UL Rx point lacks a DL RS, and must instead find the optimal UL transmit beam for the UL Rx point through the terminal's UL beam management operation.

[0108] In this specification, a method is proposed for a base station to schedule uplink transmission for a terminal when the terminal performs uplink transmission for a plurality of UL Rx points in a specific CC (Component Carrier) / BWP(s) of the terminal.

[0109] In this specification, ' / ' may be interpreted as 'and', 'or', or 'and / or' depending on the context.

[0110] Proposal 1

[0111] The UL Rx point between the base station and the terminal can be operated / managed as shown in Alt 1 to Alt 4 below.

[0112] Alt 1. Methods for allocating different frequency / time domain resources to macro cells and UL Rx points can be considered.

[0113] Alt 1-1. A base station can allocate the macro cell uplink and the UL Rx point uplink to different frequency resources.

[0114] For example, a base station may operate a macro cell uplink and a UL Rx point uplink within the same UL BWP, and may allocate independent (different) frequency resources within the BWP to the macro cell and the UL Rx point.

[0115] As another example, a base station may set the macro cell uplink and the UL Rx point uplink to different UL BWPs. In other words, power control-related parameters (and / or resources), timing advance (TA)-related parameters (and / or resources) and / or uplink beam-related parameters (and / or resources), etc., may be set independently (differently) between the different UL BWPs.

[0116] As another example, a base station can utilize a specific sub-uplink carrier (SUL carrier) for uplink transmission for a UL Rx point.

[0117] Through this operation, power control, timing advance, and / or uplink beam-related parameters (and / or resources) can be separately set / managed for uplink transmission to UL Rx points that are physically different from the macro cell.

[0118] Alt 1-2. The base station can allocate the macro cell uplink and the UL Rx point uplink to different time resources.

[0119] For example, in a pattern of downlink slot / uplink slot / flexible slot configuration set via upper layer signals TDD-UL-DL-ConfigCommon and / or TDD-UL-DL-ConfigDedicated, information such as i) specific slots among the uplink slots (and / or flexible slots) are utilized for macro cells, and ii) the remaining slots are utilized for UL Rx points, can be transmitted to a terminal via upper layer signals (e.g., RRC or MAC CE). The information can be transmitted via TDD-UL-DL-ConfigCommon and / or TDD-UL-DL-ConfigDedicated.

[0120] Through this operation, depending on which time resource the base station allocates as an uplink resource, the terminal can utilize different power control, timing advance, and / or uplink beam-related parameters for uplink transmission. In other words, depending on whether the base station allocates the time resource as an uplink resource of a macro cell or as an uplink resource of a UL Rx point, the terminal can utilize different power control, timing advance, and / or uplink beam-related parameters for uplink transmission.

[0121] Alt 2. In setting each UL channel / signal, the base station may separately set the UL channel / signal of the macro cell UL target and the UL channel / signal of the UL Rx point target, or independently set power control, timing advance and / or uplink beam related parameters for each UL channel / signal.

[0122] For example, a base station may utilize the same frequency / time domain resources for a macro cell and an UL Rx point. In this case, regarding the configuration of each UL channel / signal (e.g., PRACH / PUCCH / PUSCH / SRS), the base station may separately configure the UL channel / signal for the macro cell's UL and the UL channel / signal for the UL of the UL Rx point. Additionally, the base station may independently configure power control, timing advance, and / or uplink beam-related parameters for each UL channel / signal for the macro cell's UL and the UL channel / signal for the UL of the UL Rx point.

[0123] For example, the above UL channel / signal may include PUCCH, PUSCH, SRS, and / or PRACH.

[0124] As a specific example, the PUCCH resource of the macro cell UL target and the PUCCH resource of the UL Rx point target can be configured separately. Alternatively, the codebook (CB) based SRS resource set and / or non-codebook (NCB) based SRS resource set of the macro cell UL target and the UL Rx point target can be configured separately. In this way, the SRI field and / or the codepoint of the SRI field can be distinguished, and through this, the PUSCH transmission scheduling of the macro cell UL target and the UL Rx point target can be distinguished.

[0125] As a specific example, the SRS resource / resource set can be set and distinguished by target (by macro cell UL target and UL Rx point target).

[0126] As a specific example, the configured grant (CG) based PUSCH (CG PUSCH) can also be configured and distinguished by target.

[0127] As a specific example, regarding PRACH resources, the PRACH resources of the macro cell UL and the PRACH resources of the UL Rx point target can be configured independently.

[0128] For example, the same channel / signal may be set for the macro cell UL target and the UL Rx point target, but the power control / TA / beam parameters of the macro cell UL target and the power control, timing advance, and / or beam parameter values ​​of the UL Rx point target may be set differently.

[0129] As a specific example, multiple power control / timing advance / beam parameters for a macro cell UL target and multiple power control / timing advance / beam parameters for a UL Rx point target (e.g., two) can be set / instructed to the same PUCCH resource. In other words, the terminal can utilize a specific parameter among multiple uplink transmission parameters depending on whether the transmission target is a macro cell or a UL Rx point.

[0130] As a specific example, if a terminal is configured / instructed by a base station to simultaneously transmit a resource, for which the plurality of uplink transmission parameters are configured / instructed, to a macro cell and a UL Rx point, the terminal can simultaneously transmit the resource to the macro cell and the UL Rx point by utilizing specific parameters for each of the macro cell and the UL Rx point.

[0131] Alt 3. The base station can be configured to link macro cells and UL Rx points with different CORESET pool indices.

[0132] For example, a base station can operate a macro cell uplink and a UL Rx point uplink in the same UL BWP. In this case, the base station can configure the macro cell and the UL Rx point to be linked to different CORESET pool indices.

[0133] Through this operation, power control, timing advance, and / or uplink beam-related parameters / resources can be separately configured / managed (per CORESET pool index) for uplink transmission to UL Rx points that are physically different from the macro cell.

[0134] As an additional example, we specifically propose an operation in which a macro cell and a UL Rx point are configured to be linked to different CORESET pool indices, so that the terminal performs only uplink transmission for the CORESET pool index associated with the UL Rx point. In other words, in an M-DCI-based M-TRP environment, only uplink transmission can be configured / instructed for a specific CORESET pool index.

[0135] For example, similar to the configuration of two CB / NCB SRS resource sets in the existing Rel-18 M-TRP Simultaneous Transmission to Multiple Points (STxMP) PUSCH transmission method, a CB / NCB SRS resource set for a macro cell and a CB / NCB SRS resource set for a UL Rx point can be configured separately. In this case, a one-to-one connection may exist between the CB / NCB SRS resource set for the macro cell and a specific CORESET pool index, and a one-to-one connection may exist between the CB / NCB SRS resource set for the UL Rx point and another CORESET pool index.

[0136] As a specific example, when PUSCH scheduling, depending on which of the two SRS resource sets (CB / NCB SRS resource set for macro cell and CB / NCB SRS resource set for UL Rx point) the SRI associated with is indicated in the UL grant DCI, i) the target of uplink transmission (e.g., macro cell and / or UL Rx point) may differ, and ii) power control, timing advance, and / or uplink beam-related parameters for uplink transmission may be applied differently for each target.

[0137] As a specific example, if a terminal is configured / instructed by a base station to transmit a PUSCH simultaneously to a macro cell and a UL Rx point based on multiple SRI instructions, with all SRIs associated with the two SRS resource sets being indicated, the terminal can transmit the PUSCH simultaneously to the macro cell and the UL Rx point by utilizing each transmission parameter. Similarly, in the case of PUCCH / SRS, macro cell-specific power control / timing advance / uplink beam-related parameters or UL Rx point-specific power control / timing advance / uplink beam-related parameters may be applied during the terminal's uplink transmission, depending on which CORESET pool index (or which CB / NCB SRS resource set) the resource is associated with.

[0138] As another example, similar to the PUSCH repetition method in Rel-17 S-DCI based M-TRP, the base station may not have a CORESET pool index set, and may separately set a CB / NCB SRS resource set for macro cells and a CB / NCB SRS resource set for UL Rx points. As a specific example, the base station may operate the macro cell uplink and the UL Rx point uplink at the same UL BWP, but the CORESET pool index may not be set, and may separately set a CB / NCB SRS resource set for macro cells and a CB / NCB SRS resource set for UL Rx points.

[0139] In this case, since there is a one-to-one correspondence between the two SRS resource sets and a specific PUSCH TO group during repetition PUSCH transmission, the terminal can perform PUSCH repetition transmission for a macro cell and a UL Rx point as the base station schedules the repetition PUSCH transmission. For example, the terminal can perform S-TRP transmission (e.g., a receiving point of either a macro cell or a UL Rx point) according to the SRI indicator (or SRS resource set indicator field). For each TO group, the terminal can utilize specific parameters among the uplink transmission parameters (e.g., power control, timing advance, and / or uplink beam-related parameters) associated with the plurality of SRS resource sets depending on whether the transmission target is a macro cell or a UL Rx point. In other words, for each TO group, the terminal may utilize specific parameters among the uplink transmission parameters (e.g., power control, timing advance, and / or uplink beam related parameters) associated with the plurality of SRS resource sets, depending on which SRI and / or TPMI associated with which SRS resource set is indicated. Similarly, in the case of PUCCH / SRS, depending on which CB / NCB SRS resource set the resource is associated with, macro cell-specific power control / timing advance / uplink beam related parameters or UL Rx point-specific power control / timing advance / uplink beam related parameters may be applied during terminal uplink transmission.

[0140] Alt 4. The base station can be configured to link the macro cell and UL Rx point with different joint (UL) TCI states and / or separate (UL) TCI states in the unified TCI framework.

[0141] For example, since information related to power control, timing advance, and transmission beam is set in different joint and / or separate (UL) TCI states, depending on which joint and / or separate (UL) TCI state the base station utilizes for uplink transmission, it can be distinguished whether the target of the terminal uplink transmission is a macro cell or a UL Rx point.

[0142] In the extension of the unified TCI for Rel-18 M-TRP operation, the number of transmit / receive common beams was expanded to two (M / N=2) for TRP-specific common beam management. In this case, an operation in which two indicated TCIs (e.g., a joint TCI state and / or a separate UL TCI state) are utilized for macro cell and UL Rx point purposes can be considered.

[0143] In the operations of Proposal 1 above, a HARQ (Hybrid ARQ) process ID can be defined / configured for a macro cell and a UL Rx point, respectively. Additionally, an operation in which power control / timing advance / transmission beam-related parameters are determined during uplink transmission for each HARQ process ID distinguished by the macro cell target and the UL Rx point target can be considered. This operation is intended to distinguish transmission-related parameters by setting / defining a separate HARQ process for each macro cell and UL Rx point, as it is practically impossible in terms of complexity to soft combine the received signals from the macro cell and UL Rx point at the decoding stage even in a scenario connected by an ideal backhaul.

[0144] Problem 1. As described above, there is a problem in that DL RS transmission is impossible because the UL Rx point is equipped with a DL Tx chain to reduce base station installation costs and can only perform UL reception. Consequently, when a terminal transmits an uplink to a UL Rx point, it cannot measure the DL slot boundary (or DL ​​reference point) for TA application, and since the UL Rx point cannot transmit SSB, ambiguity arises in the terminal's operation regarding how the terminal's RACH transmission for TA acquisition should be performed.

[0145] To solve the above problem 1, the following proposal 2 may be considered.

[0146] Proposal 2

[0147] A method for a terminal to acquire timing advance information for a UL Rx point for uplink transmission to a UL Rx point.

[0148] Proposal 2-1. After the terminal acquires a timing advance (TA) for a UL Rx point, a method for defining / setting a reference point to apply the TA value (including N_TA and / or N_TA,offset) is considered.

[0149] In the following, the reference point may refer to the boundary of the downlink radio frame to which the TA value is applied.

[0150] Alt 1. The terminal can expect the reference point of the UL Rx point to be the same as the reference point of the macro cell.

[0151] For example, in base station deployment / implementation, there may be a constraint that the reference point of the UL Rx point is the same as the reference point of the macro cell. In this case, as shown in Table 2 below, the reference point definition of 38.133 in a specific cell of the terminal (SpCell / SCell) can be applied directly to the UL Rx point.

[0152]

[0153] Alt 2. The base station may set / instruct the terminal an offset value from the macro cell reference point to define the reference point of the UL Rx point.

[0154] Specifically, Alt 2 is about a method for defining / setting the reference point of the UL Rx point when there is a difference between the reference point of the Macro cell and the reference point of the UL Rx point.

[0155] The above offset value is N of the timing advance command 38.213 in Table 3 below. TA value(T A expressed as = 0, 1, 2, ..., 3846) or T in a relative TA command A = can be expressed as a value (multiple) of 0, 1, 2,..., 63. The above offset value can be set / instructed differently for multiple UL Rx points associated with a specific macro cell.

[0156] Alternatively, the above offset value may be defined as a specific value (e.g., a negative or positive real number) by the specification, and since there is no DL frame at the UL Rx point, the specific value may be defined as a UL reference point or a virtual point instead of a DL reference point.

[0157]

[0158] N TA It can be set i) via RAR or ii) via the Timing advance command (MAC-CE).

[0159] N TA,offset 1) a specific value may be set for each serving cell, or ii) a predefined value may be applied to the serving cell according to Duplex mode / FR.

[0160] A Timing Advance Group (TAG) is a group of multiple Serving Cells set by the RRC, meaning a group that uses the same timing reference cell and the same TA value for the cells on which the Uplink (UL) is set. A Timing Advance Group containing SpCells of a single MAC entity is called the Primary Timing Advance Group (PTAG), and the term Secondary Timing Advance Group (STAG) refers to the other TAGs.

[0161] Alt 3. The base station N for the UL Rx point for defining the reference point of the UL Rx point TA,offset You can define / set values.

[0162] Specifically, Alt 3 relates to a method for a base station to define / set the reference point of the UL Rx point when there is a difference between the reference point of the Macro cell and the reference point of the UL Rx point.

[0163] In the case of the legacy, N TA,offset is a TDD / FDD band-specific value, defined by standard specifications or signaled by base station settings. The base station is N for the UL Rx point. TA,offset A value can be set to the terminal. And / or, such a value may be defined by standard specifications. Likewise, N for the UL Rx point above. TA,offset The value can be defined / set differently for multiple UL Rx points associated with a specific macro cell.

[0164] In the above proposal 2-1, the base station may signal to the terminal which of the operations of Alt 1 to Alt 3 to perform depending on whether the reference point of the macro cell and the reference point of the UL Rx point are the same or different. In the above proposal 2-1, the base station may signal to the terminal information regarding the timing at which the offset values ​​in Alt 2 to Alt 3 for (multiple) UL Rx points are applied.

[0165] Proposal 2-2. A method for obtaining TA for UL Rx points and a method for indicating / updating TA for UL Rx points are proposed.

[0166] In the following, for managing the TA value for the UL Rx point, the TA value of the UL Rx point may be managed as a TAG different from the macro cell or as a specific offset value from the macro cell TA value.

[0167] Alt 1. If a reference point for uplink transmission to a UL Rx point is defined / configured as in Proposal 2-1, the base station may allow the terminal to transmit uplink transmission to the configured / instructed UL Rx point based on the reference point.

[0168] Specifically, the base station does not perform a separate operation for TA acquisition, and if a reference point for uplink transmission to a UL Rx point is defined / configured, the terminal can transmit uplink transmission to the configured / instructed UL Rx point based on the reference point.

[0169] Subsequently, the base station can execute a TA command for the UL Rx point by utilizing an absolute / relative TA command (MAC CE) to correct the TA value for the terminal's UL Rx point.

[0170] Alt 2. The terminal may transmit RACH to the UL Rx point. The RACH may be a RACH transmission by PDCCH order.

[0171] Afterward, the base station can perform a TA indication for the UL Rx point by utilizing the RAR (absolute TA command field) after receiving a RACH from the UL Rx point.

[0172] For example, a RAR corresponding to a RACH transmitted to a UL Rx point can be received from a macro cell, and in particular, can be received by utilizing a CORESET associated with a type-1 CSS.

[0173] In the above Alt 2, since the UL Rx point does not transmit SSB, there is a problem in that it is difficult to set power control and transmit beam information for RACH transmission. To solve this problem, the following methods i to iii may be applied.

[0174] - Method i. The base station directs a specific SSB of a macro cell via a PDCCH order, and the terminal can utilize the preamble / RACH resource associated with the SSB to transmit a RACH with the SSB as the transmit beam RS and / or pathloss RS.

[0175] - Method ii. Alternatively, the base station may direct a specific SSB of a macro cell via a PDCCH order, and the terminal may utilize the RACH preamble / RACH resource associated with the SSB, wherein the transmit beam RS and pathloss RS may apply the embodiments of Proposal 3 or / and Proposal 4.

[0176] - Method iii. Alternatively, without instructions from the SSB, the transmit beam RS and pathloss RS of the RACH may be applied according to embodiments of Proposal 3 or / and Proposal 4. In this case, the beam management SRS transmitted by the terminal in advance for the RACH transmit beam may be utilized as the transmit beam reference RS.

[0177] To switch / control such operations, when a PDCCH order triggering RACH transmission for a UL Rx point is executed, the base station may indicate via an ordering DCI whether to have the terminal i) transmit the RACH in alignment with the SSB receiving beam (e.g., method i above) or ii) transmit the RACH in a direction different from the SSB receiving beam (e.g., method ii above or method iii above). Accordingly, the QCL assumption may change when the terminal receives the RAR (RAR scheduling PDCCH, PDSCH RAR) for the corresponding RACH. For example, in the case of method i above, the indicated SSB may be utilized as the QCL RS for RAR reception. As another example, in the case of method ii or method iii above, the transmit beam RS according to Proposal 4 may be utilized for RAR reception. As yet another example, QCL information set in the CORESET associated with the type-1 CSS as described above may be utilized.

[0178] In addition, under the existing NR standard, when a terminal receives a RAR scheduling PDCCH after transmitting a RACH, it calculates the RA-RNTI based on the RACH occasion (RO) and then receives the PDCCH based on the corresponding ID. At this time, if the terminal triggers a RACH transmission based on a specific SSB as in method i or method ii above, the terminal can calculate the RA-RNTI based on the RO based on the corresponding macro cell SSB and receive the RAR scheduling PDCCH. On the other hand, in the case of a RACH transmission not based on a specific SSB as in method iii above, the terminal can receive the RAR scheduling PDCCH through a separate RA-RNTI calculation.

[0179] The calculation method for RA-RNTI and MSGB-RNTI related to the PRACH occasion in which the Random Access Preamble is transmitted can be seen in Table 4 below.

[0180]

[0181] For example, the operation of Alt 2 described above can also be applied at the stage where the terminal transmits RACH to perform initial access. For example, RACH information related to a UL Rx point (e.g., RACH resource information such as RACH-config including SSB index, RACH preamble, RACH occasion, etc.) may be included in a specific SIB, and when the terminal performs the initial access procedure, it may transmit RACH to the UL Rx point based on this RACH information related to the UL Rx point.

[0182] Alt 3. The base station may separately configure an SRS resource set and an SRS resource for a RACH-like SRS for the terminal, and may execute a TA command for the UL Rx point via an absolute / relative TA command (MAC CE) to correct the TA value for the terminal's UL Rx point based on the reception of the RACH-like SRS transmitted by the terminal. The specific SRS resource for the RACH-like SRS may be composed of a time / frequency domain resource with N symbols or more and a bandwidth of X kHz or more (N and X are positive natural numbers).

[0183] Through this operation, the base station can solve the problem where TA acquisition was inaccurate due to insufficient granularity in existing SRS reception.

[0184] Problem 2. In existing NR, the pathloss reference RS (hereinafter PL-RS) is set as an open-loop parameter for UL power control. However, since UL Rx points cannot transmit DL RS, there is a problem that it is difficult to set the PL-RS for pathloss compensation in open-loop power control.

[0185] To solve the above problem 2, the following proposal 3 may be considered.

[0186] Proposal 3

[0187] Below, we examine the terminal power control method for uplink transmission to the UL Rx point.

[0188] Proposal 3-1. A method for determining uplink power for the UL Rx point using only closed-loop power control is proposed.

[0189] A closed-loop index for closed-loop power control associated with a UL Rx point may, similar to Proposal 1 above, be associated with i) a specific SRI (field) associated with the UL Rx point, ii) a specific SRS resource set, iii) a specific CORESET pool index, iv) a specific TCI state, or v) a specific TAG. The TPC command for closed-loop power control associated with the UL Rx point may include the aforementioned specific indicator(s). And / or, the TPC of the UL Rx point may be indicated through a DCI that is scrambled with an RNTI different from the macro cell, where the same closed-loop index as the macro cell is indicated, or the target to which the TPC is to be applied (e.g., whether it is a macro cell or a UL Rx point) may be indicated through a separate 1-bit field within the DCI. The operation of executing a TPC command on a UL Rx point including these specific indicator(s) can also be utilized in a TPC command utilizing group-common DCI.

[0190] A method for determining the uplink transmission power for the initial UL Rx point of a terminal is proposed so that a base station can perform closed-loop power control for the terminal's UL Rx point. Before receiving a closed-loop TPC command from the base station, the terminal may transmit the uplink set / instructed with a minimum transmit power. Alternatively, before receiving a closed-loop TPC command from the base station, the terminal may transmit the uplink with a transmit power calculated using only the open-loop power control parameter of the macro cell for the set / instructed uplink channel / RS. Alternatively, before receiving a closed-loop TPC command from the base station, the terminal may transmit the uplink with a transmit power calculated using only P0, utilizing only the open-loop power control parameter of the macro cell for the set / instructed uplink channel / RS, without performing fractional pathloss compensation by PL-RS. Alternatively, the terminal may transmit an uplink set / instructed to a specific transmit power according to the base station's settings / definitions before receiving a closed-loop TPC command from the base station.

[0191] A specific method for TPC commands is proposed when a base station performs closed-loop power control on a terminal's UL Rx point.

[0192]

[0193] In the standard, as shown in Table 5 above, the power offset value to be applied for power control is defined according to the TPC command field for cases where tpc-Accumulation is set to on (or when the terminal has not received the RRC parameter tpc-Accumulation) and cases where tpc-Accumulation is set to disable (or when the terminal has received the RRC parameter tpc-Accumulation, in the case of absolute TPC operation).

[0194] When a base station performs a TPC command on a closed-loop index related to a UL Rx point, it may use a separate power offset value table as shown in Table 6 below, in which the offset value for a macro cell is doubled or n times (n is a natural number), rather than the power offset value table for a macro cell as shown in Table 5 above.

[0195]

[0196] And / or, in a scenario where the terminal moves away from the macro cell and moves in a direction closer to the UL Rx point depending on the terminal's mobility, the base station may dynamically change the offset value by i) reducing the absolute value of the power offset value of the TPC command field for the closed-loop index from the value of each TPC command field in Table 5, or ii) increasing the number of negative values ​​mapped to each field. For example, the base station may dynamically change the offset value in such a way through DCI / MAC-CE.

[0197] Similarly to the above, in a scenario where the terminal moves away from the UL Rx point while approaching the macro cell, the base station may dynamically change the offset value by i) increasing the absolute value of the power offset value of the TPC command field for the closed-loop index from the value of each TPC command field in Table 5, or ii) increasing the number of positive values ​​mapped to each field.

[0198] And / or, if the uplink reception level of the terminal changes due to terminal mobility and / or changes in the terminal's transmit beam, the base station may instruct the terminal (via DCI / MAC CE) a power offset correction value at a future uplink transmission time by utilizing a prediction by an AI / ML model. For example, the base station may instruct the terminal via DCI / MAC CE the power offset correction value at the future uplink transmission time.

[0199] Proposal 3-2. A method for setting open-loop power control parameters for UL Rx points is proposed.

[0200] The base station can set / instruct open-loop power control parameters for the terminal's UL Rx point by utilizing one or more of the following embodiments (Alt 1 to Alt 3).

[0201] Alt 1. The base station sets the PL-RS among the open-loop power control parameters for the terminal UL Rx point as a DL RS associated with the macro cell, and can newly define / set the alpha value associated with the UL Rx point for the alpha value, which is a parameter for fractional pathloss compensation relative to the pathloss value for the PL-RS.

[0202] For example, the alpha value associated with the above UL Rx point may be set commonly for the uplink transmission PUSCH / PUCCH / SRS / PRACH for the terminal's UL Rx point, or may be set independently (differently) for each uplink channel / RS. For example, the alpha value associated with the above UL Rx point may be set smaller than the alpha of the macro cell because the propagation range from the terminal to the UL Rx point is shorter than that of the macro cell.

[0203] Alt 2. The base station can set PL-RS among the open-loop power control parameters for the terminal's UL Rx point using DL RS associated with the macro cell. At this time, the open-loop parameter for the UL Rx point can be defined / set based on the setting / instruction of an offset value of Y [dB] (Y is a negative / positive integer or 0) with respect to the fractional pathloss compensation value compensated by the uplink channel / RS-specific alpha value set for the macro cell.

[0204] In this case, the Y value may be i) commonly set for the uplink transmission PUSCH / PUCCH / SRS / PRACH for the terminal's UL Rx point, or ii) independently (differently) set for each uplink channel / RS. For example, the Y value may be set as a negative integer because the propagation range from the terminal to the UL Rx point is shorter than that of the macro cell.

[0205] Alt 3. The base station can perform open-loop power control by newly setting the P0 value for the UL Rx point.

[0206] For example, the base station can perform open-loop power control by not setting PL-RS among the open-loop power control parameters for the UL Rx point, and by newly setting the P0 value for the UL Rx point to be different from the P0 value of the macro cell.

[0207] and / or, an offset value for the P0 value of a macro cell may be set to the terminal to set the P0 value for the UL Rx point. The new P0 value or offset value for the UL Rx point may be i) commonly set for the uplink transmission PUSCH / PUCCH / SRS / PRACH for the terminal's UL Rx point, or ii) independently (differently) set for each uplink channel / RS.

[0208] The correction values ​​of Alt 1 to Alt 3 for setting open-loop power control parameters for the UL Rx point of the terminal (e.g., the new alpha value, value Y, new P0 value, etc.) can be dynamically changed by increasing or decreasing the magnitude of the correction values ​​depending on whether the terminal approaches or moves away from the UL Rx point. For example, the base station can dynamically change the correction values ​​of Alt 1 to Alt 3 for setting open-loop power control parameters for the UL Rx point of the terminal through MAC CE / DCI.

[0209] And / or, if the uplink reception level of the terminal changes due to terminal mobility or / and a change in the terminal's transmit beam, the base station may indicate a correction value at a future uplink transmission time via DCI / MAC CE by utilizing a prediction by an AI / ML model.

[0210] The open-loop power control parameter setting for the UL Rx point of the above terminal may be associated with a specific SRI (field), a specific SRS resource set, a specific CORESET pool index, a specific TCI state, or a specific TAG associated with the UL Rx point.

[0211] In addition, we propose a method for dynamically updating open-loop power control parameters for UL Rx points via DCI using the above indicators.

[0212] Proposal 3-3. A power headroom report (PHR) method for the UL Rx point of a terminal is proposed.

[0213] Terminal PHR transmission is performed as an event-triggered operation by several events, and to indicate that the terminal is a report on a UL Rx point, a specific SRI (field), a specific SRS resource set, a specific CORESET pool index, a specific TCI state, or a specific TAG associated with the UL Rx point may be included in the PHR as an indicator, as in Proposal 3-1.

[0214] The embodiments of Proposal 3 above may operate by a combination of specific embodiments.

[0215] Problem 3. In NR FR2, i) the spatialRelation framework and ii) the joint TCI state and / or the UL separate TCI state can be utilized for setting the UL transmit beam. However, even if the terminal has the capability for beam correspondence, the UL Rx point cannot transmit the DL RS, so the base station cannot set the DL RS as the UL transmit beam reference RS and must search for / determine the optimal UL transmit beam for the UL Rx point solely through the terminal UL beam management operation (SRS beam sweeping).

[0216] To solve the above problem 3, the following proposal 4 may be considered.

[0217] Proposal 4

[0218] Below, we examine how to find the optimal UL transmission beam for the terminal's UL Rx point.

[0219] Proposal 4-1. When a base station performs UL beam management operations using a terminal's beam management SRS (e.g., when no spatial relation is established for the SRS resource(s) within the beam management SRS resource set), it may set a specific past BM SRS resource (e.g., the most recent BM SRS resource) or a past successful PUSCH transmission beam (e.g., the most recent successful PUSCH transmission beam) as an anchor beam for the SRS resource (set) intended for beam management purposes, and allow the terminal to utilize transmission beams close to the anchor beam when transmitting the SRS resource (set) intended for beam management purposes. When transmitting the SRS resource (set) intended for beam management purposes, the terminal may transmit the SRS resource (set) using beams that are close to the anchor beam and have a different beam direction as much as possible.

[0220] For the anchor beam, an SRS resource set for BM purposes that serves as a reference in advance can be set, and in the case of a P / SP SRS resource (set), the anchor beam can be set / activated through RRC / MAC CE, and in the case of an AP SRS, the SRS can be triggered by indicating an SRS resource within the BM SRS resource set to be referenced or a past successful PUSCH transmission beam (e.g., the most recent successful PUSCH transmission beam) through DCI.

[0221] Through this method, the base station has the advantage of reducing the delay / overhead associated with optimal beam search by utilizing the terminal's past successful transmission beams to search for the optimal beam.

[0222] Proposal 4-2. The base station may transmit a closed-loop command to perform uplink transmission by moving the beam vertically / horizontally and / or up / down / left / right based on the terminal's past successful PUSCH transmission beam (e.g., the most recent successful PUSCH transmission beam).

[0223] and / or, the base station may signal to the terminal an indicator of whether to utilize the trend of the amount / degree of change of past successful transmission beams based on n past successful PUSCH transmission beams (n is a natural number greater than or equal to 2) for future uplink transmission.

[0224] As another example, the base station can signal to the terminal transmission beam information to be used for future uplink transmission in the form of a linear combination of n transmission beams (e.g., 0.9 * most recent PUSCH transmission beam + 0.6 * second most recent PUSCH transmission beam + 0.7 * third most recent PUSCH transmission beam + ...) based on the terminal's past successful PUSCH transmission beams (n is a natural number greater than or equal to 2). To this end, coefficient values ​​for each most recent / second most recent / third most recent... PUSCH transmission beam can be signaled to the terminal.

[0225] As another example, the base station can signal to the terminal transmission beam information to be used for future uplink transmission in the form of a linear combination of previously transmitted SRS resources (e.g., the most recent SRS resource) in the SRS resource set used for BM purposes that serves as a reference standard. Similarly, coefficient values ​​for each SRS resource can be signaled to the terminal.

[0226] The above closed-loop command and / or the above indicator may be included in the PUSCH / PUCCH / SRS / PRACH uplink transmission setup / instruction.

[0227] The above closed-loop command and / or the above indicator may be applied i) to a specific indicated TCI in the unified TCI framework or ii) to an uplink transmission associated with a specific SRI (field) / CORESET pool index / TAG and / or a specific SRI (field) / CORESET pool index / TAG.

[0228] Through this method, the base station has the advantage of reducing delay / overhead associated with optimal beam search by utilizing the terminal's past successful transmission beams to transmit commands for the current optimal beam.

[0229] In the above proposal 4, a successful PUSCH transmission beam (e.g., the most recent successful PUSCH transmission beam) can be replaced with a successful RACH / PUCCH transmission beam (e.g., the most recent successful RACH / PUCCH transmission beam), etc.

[0230] Problem 4. As the terminal moves within the macro cell, the location of the optimal UL Rx point among multiple UL Rx points within the macro cell may change.

[0231] To solve the above problem 4, the following proposal 5 may be considered.

[0232] Proposal 5

[0233] The base station can pre-set / instruct the terminal with zone-based offsets related to the TA, PC, and transmission beam of Proposal 2 to Proposal 4, depending on the location of multiple UL Rx points, the location of the terminal, and / or whether the terminal is indoors or outdoors.

[0234] For example, offsets for the UL Rx point to which the terminal transmits the UL for each terminal location and the uplink-related parameters (e.g., TA, PC (power control), transmit beam) applied for each terminal location for the UL Rx point may be signaled to the terminal by the base station in advance.

[0235] In particular, in the case of TA, it operates as an accumulated TA in which the base station continuously updates with TA commands in the existing standard operation, but the base station can apply different TA values ​​for each UL Rx point by performing only TA updates without notifying the terminal (serving) of changes in the UL Rx point.

[0236] However, in the above case, since there may be a large difference in TA between different UL Rx points from the terminal, the range of TA fluctuation due to UL Rx point switching may not be covered by the accumulated TA method using a simple TA update as described above. To solve this problem, the base station may use the MAC-CE (header), etc., to indicate whether the TAC is a command for the TA accumulated so far or a command for an absolute value (e.g., a 1-bit flag), and thereby instruct a new absolute TA when the terminal's (serving) UL Rx point changes. Such an absolute TA command may mean to apply the absolute TA value based on the reference point related to the UL Rx point of Proposal 2 above.

[0237] Through this method, the terminal can transmit uplink to the nearest UL Rx point depending on the terminal's location, and can receive optimized TA, PC, and transmission beam related parameters from the base station even within the coverage of the UL Rx point.

[0238] The above embodiments may be operated by a combination of specific embodiments.

[0239] Expressions such as macro cell and UL Rx point above do not limit the concept of the invention, and macro cell can be replaced with a base station capable of operating both DL and UL, and UL Rx point can be replaced with a base station capable of operating only UL or an Rx only point, etc.

[0240] As shown in the standardization discussion in Table 7, discussions were held to apply the PL offset related to the indicated TCI to the pathloss compensation during the terminal's PRACH transmission when the base station triggers a PDCCH ordered RACH for the UL Rx point. In addition, at the RAN#105 meeting, the WID was modified to support two TA operations in a DL / UL asymmetric scenario where the UL Rx point is deployed, and standardization discussions are scheduled to proceed to enable two TA operations to be utilized in an S-DCI based M-TRP environment as well.

[0241]

[0242] This specification proposes a solution to the problem in the process of performing TA acquisition for UL Rx points using PDCCH ordered RACH.

[0243] Problem 5. As discussed in Proposal 2 above, since there is no DL transmission at the UL Rx point, the base station can trigger the terminal to transmit a PDCCH ordered RACH to the UL Rx point by utilizing the macro cell's SSB, the RACH occasion (hereinafter RO) associated with the macro cell SSB, and PRACH resources (e.g., preamble index, etc.). In this environment, the transmission beam and pathloss compensation of the PDCCH ordered RACH toward the UL Rx point, and the RAR reception method (including QCL estimation for RAR reception) were covered in Proposal 2. On the other hand, if multiple terminals that transmit PRACH to different TRPs (e.g., macro cell and / or UL Rx point) using the same RO select the same preamble index, a collision may occur in the PRACH transmission. For example, such collisions may primarily occur when two terminals perform contention-based random access (CBRA), and there are also cases in contention-free random access (CFRA) where the terminal directly selects the preamble index depending on whether the base station is signaling (e.g., when the preamble index field is indicated as “0b000000”). To solve this problem 5, the following proposal 6 may be considered.

[0244] Proposal 6

[0245] Below, we examine the solution for cases where collisions occur when different terminals use the same RO to send PRACH to different TRPs.

[0246] Alt 1. A base station may treat the preambles transmitted by multiple terminals as colliding when multiple terminals select the same preamble index, in the same manner as defined in existing standard specifications. In this case, the base station may transmit a RAR to a specific terminal among the multiple terminals.

[0247] Alt 2. Since the base station receives preambles with different TRPs, it can treat all preambles transmitted by two different terminals as successful, and to this end, the following options may be considered. This embodiment may be based on the premise that the base station can distinguish between preambles received with different TRPs.

[0248] Option 1) of Alt 2, through a 1-bit indicator within the RAR MAC CE, the base station can indicate whether the RO of the macro cell or the RO of the UL Rx point has been received, even if the RAPID is the same.

[0249] In this case, as described in Proposal 7 below, since the terminal can recognize whether the target of the PDCCH ordered RACH is a macro cell or a UL Rx point through a specific 1-bit field of the PDCCH order, even if the base station sends RARs to the two different terminals respectively, the collision can be handled in such a way that each terminal receives only the RAR corresponding to itself, resolves the RA procedure, and discards the remaining RARs.

[0250] After the terminal receives the settings for the (first) TAG ID associated with the macro cell and the (second) TAG ID for the UL Rx point in Option 2 of Alt 2, the base station may indicate whether the RO of the macro cell or the RO of the UL Rx point has been received, even if the RAPID is the same, depending on whether the TI field (see FIG. 7 and Table 8 below) for indicating the target TAG for the TA command operation within the RAR MAC CE indicates the TAG ID for the macro cell or the TAG ID for the UL Rx point. For example, the first TAG ID may be associated with the macro cell, and the second TAG ID may be associated with the UL Rx point.

[0251] Figure 7 illustrates a MAC payload for a random access response. The description of the fields of the random access response is as shown in Table 8 below.

[0252]

[0253] Similar to Option 1 of Alt 2 above, even if the base station sends RARs to each of the two different terminals, the collision can be handled in such a way that each terminal receives only the RAR corresponding to itself, resolves the RA procedure, and discards the remaining RARs.

[0254] Option 3) of Alt 2 can be defined so that the RA-RNTI value when the terminal uses the RO of the UL Rx point can be distinguished from the RA-RNTI value for the RO of the macro cell.

[0255] For example, when calculating the RA-RNTI associated with a UL Rx point, the s_id (symbol index) among the calculated RA-RNTI values ​​is defined as the second OFDM symbol (or last OFDM symbol) value rather than the first OFDM symbol value of the RO, thereby distinguishing it from the RA-RNTI calculation for the RO of a macro cell. Subsequently, a terminal that transmits a PRACH targeting a UL Rx point can use these enhanced RA-RNTI values ​​to monitor the RAR corresponding to itself through a CORESET associated with a type-1 CSS.

[0256] Alt 3. To solve problem 5 above, SSB and / or RACH occasions (and / or preamble index, mass index, etc.) are defined by dividing them into two or more groups, so that SSB index and / or RACH occasions corresponding to macro cells and SSB index and / or RACH occasions corresponding to UL Rx point(s) can be distinguished.

[0257] Through this method, it is possible to prevent cases where two different terminals use the same preamble index for the same RO to transmit PRACH to different TRPs.

[0258] As an additional embodiment of the above proposal 6, when acquiring a TA for a UL Rx point (or macro cell) using a PDCCH ordered RACH, the terminal does not expect the base station to trigger a CBRA in the PDCCH order (e.g., by indicating the preamble index field as “0b000000”). Alternatively, the base station may not trigger a CBRA in the PDCCH order (e.g., by indicating the preamble index field as “0b000000”). Through this method, when the base station triggers a CBRA when triggering a PDCCH ordered RACH to acquire a TA for a specific TRP, the terminal can prevent the base station from transmitting a CBRA PRACH for an SSB and / or RACH occasion related to a TRP other than the target TRP for which the base station intends to acquire a TA.

[0259] The operation of Proposal 6 above can be extended to general M-TRP operations (e.g., an M-TRP environment consisting of TRPs capable of transmitting and receiving both DL / UL) as well as DL / UL asymmetric scenarios.

[0260] Problem 6. As stated in the second agreement of Table 7 above, when a terminal transmits a PDCCH ordered RACH of a UL Rx point target, the PL offset associated with one of the indicated TCIs can be used for pathloss compensation for the PRACH. However, since the UL Rx point does not have a DL RS, there is a problem regarding which DL RS should be used to determine the PL RS of the PDCCH ordered RACH of the UL Rx point target.

[0261] To solve the above problem 6, the following proposal 7 may be considered.

[0262] Proposal 7

[0263] Below, we examine the method for determining PL-RS of the PDCCH ordered RACH of the UL Rx point target.

[0264] Alt 1. When a base station directs one of two indicated TCIs for a PDCCH order DCI for PL offset determination, the terminal may use the PL-RS associated with the indicated TCI (or set / connected to the TCI state) as the PL-RS of the PDCCH ordered RACH of the UL Rx point target.

[0265] Alt 2. When a terminal receives a PDCCH order, the DL RS associated with the DM-RS used to receive the corresponding DCI (e.g., the QCL reference RS set in the TCI state of the CORESET used to receive the DM-RS) can be used as the PL-RS of the PDCCH ordered RACH of the UL Rx point target.

[0266] Alt 3. When the base station triggers a PDCCH ordered RACH, the terminal can use the SSB index indicated by the corresponding ordering DCI as the PL-RS of the PDCCH ordered RACH of the UL Rx point target.

[0267] In Proposal 7 above, the indicated TCI may be indicated in the corresponding ordering DCI for determining the PL offset applied to the PDCCH ordered RACH of the UL Rx point target. In this case, the indicated TCI must be applied only when it is the PDCCH ordered RACH of the UL Rx point target so that accurate pathloss compensation can be performed for the PDCCH ordered RACH of the macro cell target. For this operation, the PRACH association indicator used for determining PL-RS in an inter-cell M-DCI environment in the Rel-18 two TA operation may be utilized.

[0268] As a specific example, if the PRACH association field is indicated as '0', the terminal recognizes that a PDCCH ordered RACH directed to a macro cell has been triggered, and may not use the PL offset associated with the indicated TCI in the PDCCH order when transmitting the RACH. Alternatively, if the PRACH association field is indicated as '0', the indicated TCI field for determining the PL offset in the PDCCH order may be reserved.

[0269] As another specific example, when the terminal indicates that the PRACH association field is '1', the indicated TCI indication field for determining the PL offset in the PDCCH order may be activated. Additionally, the terminal may perform a PRACH transmission by applying the PL offset value associated with the indicated TCI in the PDCCH order during pathloss compensation. Through this method, the target TRP of the PDCCH-ordered RACH can be switched according to the PRACH association field switching.

[0270] As another example, regarding the above operation, a method may be considered in which a separate 1-bit indicator is introduced instead of the PRACH association field. As the said 1-bit indicator switches between '0' and '1', the same operation as the above method can be performed.

[0271] For example, as the above PRACH association field or the above separate 1-bit indicator switches between '0' and '1', if the PDCCH ordered RACH is a macro cell target (or if it is instructed not to apply a PL offset), a legacy PRACH PL-RS determination rule may be utilized. As a specific example, if the PDCCH ordered RACH is a macro cell target (or if it is instructed not to apply a PL offset), as in Alt 2 of Proposal 7, the DL RS (i.e., QCL reference RS set in the TCI state (of CORESET) used to receive the DM-RS used to receive the corresponding DCI) when the terminal receives the PDCCH order may be utilized as the PL-RS of the PDCCH ordered RACH of the UL Rx point target, but the PL offset may not be applied.

[0272] As another example, when the PDCCH ordered RACH is a UL Rx point target (or is instructed to apply a PL offset), the terminal may utilize the PL-RS determination method (Alt 1 to Alt 3) of Proposal 7 above. In other words, depending on the 1-bit, i) whether or not to apply a PL offset and ii) the PL-RS determination method of the PDCCH ordered RACH may be determined.

[0273] For example, even if the PRACH association field or the separate 1-bit indicator for indicating whether the indicated PL offset is applied in a PDCCH ordered RACH is switched between '0' and '1', the QCL assumption for receiving RAR can remain unchanged and remain the same.

[0274] Referring to Table 9 below, in the case of the PRACH association field, which is intended to indicate the target TRP for PL-RS determination and RAR QCL assumption, it was possible to instruct the RAR QCL assumation according to the legacy operation or the RAR QCL assumation according to the Rel-18 enhanced RAR QCL assumption operation to be performed by 1-bit switching operation.

[0275]

[0276] However, in the UL Rx point related scenario, since the UL Rx point does not transmit DL, there is no reason for the QCL assumption to be changed according to the above 1-bit switching.

[0277] As a specific example, the QCL assumption for receiving the RAR can be performed by utilizing the same QCL information as the DM-RS used to receive the DCI when the terminal receives a PDCCH order.

[0278] As another specific example, the QCL assumption for receiving the RAR can be performed by utilizing the indicated SSB within the PDCCH order as the QCL reference RS.

[0279] As another specific example, the QCL assumption for receiving the RAR can be performed by utilizing the QCL information set in the CORESET associated with the type-1 CSS.

[0280] And / or, the RAR QCL assumption may be performed based on legacy rules without changing even if the PRACH association field or the separate 1-bit indicator is switched between '0' and '1'. Specifically, i) in SpCell, QCL information used when receiving DM-RS related to the PDCCH order is used for receiving RAR scheduling PDCCH, ii) the same QCL information as said PDCCH is used for receiving RAR PDSCH, and iii) in SCell, QCL information set in CORESET related to type-1 CSS is used for receiving RAR scheduling PDCCH, and SSB or CSI-RS used when transmitting PRACH may be used as QCL information for receiving RAR PDSCH.

[0281] Below, we examine how PL-RS is determined differently depending on an indication based on the PDCCH order (e.g., a new introduced 1-bit in PDCCH order). As a specific example, we examine a method to determine / indicate PL-RS by utilizing a new 1-bit field (e.g., pathloss offset indicator field) within the PDCCH order (e.g., DCI format 1_0).

[0282] As shown in Table 10 below, consensus was reached to apply the PL offset of the PDCCH ordered PRACH in an asymmetric DL / UL scenario (e.g., Asymmetric DL single-TRP and UL multi-TRP).

[0283]

[0284] In summary, in a Rel-17 unified TCI environment where only one indicated TCI is managed, a new 1-bit DCI field in DCI format 1_0 is used to indicate whether the terminal should use the PL offset set in the indicated TCI for PRACH power calculation when transmitting a PDCCH ordered PRACH (field index 1 or 0). Additionally, in a Rel-18 unified TCI environment where two indicated TCIs are managed, the 1-bit DCI field is used as follows: In the case of field index 0, the terminal uses the PL offset set in / associated with the first indicated TCI for PRACH power calculation when transmitting a PDCCH ordered PRACH. In the case of field index 1, the terminal uses the PL offset set in / associated with the second indicated TCI for PRACH power calculation when transmitting a PDCCH ordered PRACH.

[0285] Based on this background, a method is proposed below in which the PL-RS determination method of PDCCH ordered PRACH differs according to the corresponding 1-bit DCI field instruction.

[0286] Proposal 8

[0287] Below, we examine examples of a method in which the PL-RS of a PDCCH ordered PRACH is determined differently according to the instructions of the above new 1-bit DCI field in DCI format 1_0.

[0288] [1] When only one indicated TCI is managed, such as in a Rel-17 unified TCI environment

[0289] [1-1] The above new 1-bit DCI field in DCI format 1_0 indicates “0”: This means that no PL offset is applied to the PDCCH-ordered PRACH triggered by the corresponding DCI, which can be interpreted as triggering the PRACH directed toward the macro cell. The terminal can calculate the PRACH power by utilizing the RS based on the legacy PL-RS determination rule. Specifically, the RS for determining the PathLoss (PL) related to the transmission power for the PRACH can be determined as the DL RS related to the DM-RS used by the terminal to receive the DCI (PDCCH order) when receiving the DCI (PDCCH order). In other words, the RS for determining the PL can be determined as the DL RS related to the DM-RS of the PDCCH order (e.g., DL RS that DM-RS of the PDCCH order is quasi-collocated with). In other words, the RS for determining the above PL can be determined as the QCL reference RS set in the TCI state (of the CORESET) utilized to receive the above DM-RS.

[0290] [1-2] The above new 1-bit DCI field in DCI format 1_0 indicates “1”: Applying a PL offset to a PDCCH ordered PRACH triggered by the corresponding DCI can be interpreted as triggering a PRACH directed toward the UL TRP. The terminal may calculate the PRACH power by utilizing Alt 1 (PL RS set in the indicated TCI) or / and Alt 3 of Proposal 7 (i.e., an enhanced PL-RS determination rule). For example, the terminal may determine the RS for determining the PathLoss (PL) associated with the transmission power for the PRACH as the RS associated with the indicated TCI (e.g., the indicated DL RS based on QCL-info within the corresponding TCI state (TCI-state or TCI-UL-State)) (Alt 1 of Proposal 7). For example, the terminal may determine the RS for determining the PL as an SS / PBCH block indicated based on the PDCCH order (e.g., an SS / PBCH block indicated by the SS / PBCH index field of the PDCCH order) (Alt 3 of Proposal 7).

[0291] [2] When two indicated TCIs are managed, such as in a Rel-18 unified TCI environment

[0292] [2-1] When the above new 1-bit DCI field in DCI format 1_0 indicates “0” or “1” and the PL offset is not set in the indicated TCI: The fact that the PL offset is not set (in the indicated TCI) for a PDCCH ordered PRACH triggered by the corresponding DCI can be interpreted as triggering a PRACH directed toward a macro cell. The terminal can calculate the PRACH power by utilizing the legacy PL-RS determination rule (DL RS related to the DM-RS used to receive the corresponding DCI when the terminal receives the PDCCH order (i.e., QCL reference RS set in the TCI state (of the CORESET) used to receive the DM-RS)). Specifically, the RS for determining the PathLoss (PL) related to the transmission power for the PRACH can be determined by the DL RS related to the DM-RS used to receive the corresponding DCI (PDCCH order) when the terminal receives the DCI (PDCCH order). In other words, the RS for determining the PL may be determined as a DL RS associated with the DM-RS of the PDCCH order (e.g., a DL RS that DM-RS of the PDCCH order is quasi-collocated with). In other words, the RS for determining the PL may be determined as a QCL reference RS set in the TCI state (of the CORESET) utilized to receive the DM-RS.

[0293] [2-2] When the above new 1-bit DCI field in DCI format 1_0 indicates “0” or “1” and a PL offset is set in the indicated TCI: applying the PL offset (set in the indicated TCI) to a PDCCH ordered PRACH triggered by the corresponding DCI can be interpreted as triggering a PRACH directed toward the UL TRP. The terminal may calculate the PRACH power by utilizing Alt 1 (PL RS set in the indicated TCI) or / and Alt 3 of Proposal 7 (i.e., an enhanced PL-RS determination rule). For example, the terminal may determine the RS for determining the PathLoss (PL) related to the transmission power for the PRACH as the RS related to the first indicated TCI (or second indicated TCI) (e.g., the indicated DL RS based on QCL-info within the corresponding TCI state (TCI-state or TCI-UL-State)) (Alt 1 of Proposal 7). For example, the terminal may determine the RS for determining the PL as an SS / PBCH block indicated based on the PDCCH order (e.g., an SS / PBCH block indicated by the SS / PBCH index field of the PDCCH order) (Alt 3 of Proposal 7).

[0294] According to the above new 1-bit DCI field in DCI format 1_0, the target TRP of PDCCH ordered PRACH can be switched to a macro cell or UL TRP, and PL-RS can be adaptively changed based on the embodiments of Proposal 8.

[0295] The embodiments of the above proposal may be operated by one or more combinations.

[0296] The embodiments of the above proposal can be extended to asymmetric DL / UL scenarios as well as general M-TRP operations (e.g., an M-TRP environment consisting of TRPs capable of transmitting and receiving both DL / UL).

[0297] An example of a terminal (or base station) operation based on at least one of the embodiments described above (e.g., at least one of the embodiments of Proposals 1 to 7) is as follows.

[0298] 1) The terminal (or base station) receives (or transmits) settings related to the UL Rx point within a specific serving cell

[0299] The above settings may be based on Proposal 1 for UL Rx point operation.

[0300] The above settings may be based on Proposals 2 to 7 regarding TA, PC, and transmission beam settings related to the UL Rx point.

[0301] 2) The terminal (or base station) transmits (or receives) the uplink to the UL Rx point

[0302] Prior to the above uplink transmission, i) TA acquisition such as proposals 2, 6, and 7, ii) power control such as proposals 3 and 7, and / or iii) transmission beam setting such as proposal 4 may be performed.

[0303] The above terminal / base station operations are merely examples, and each operation (or step) is not necessarily essential; depending on the terminal / base station implementation method, operations related to uplink transmission of the terminal according to the aforementioned embodiments may be omitted or added.

[0304] In terms of implementation, operations of a base station / terminal according to the embodiments described above (e.g., operations related to uplink transmission of a terminal based on at least one of the embodiments of Proposals 1 to 8) can be processed by the device of FIG. 10 to be described later (e.g., the processor (110, 210) of FIG. 10).

[0305] In addition, operations of a base station / terminal according to the above-described embodiment (e.g., operations related to uplink transmission of a terminal based on at least one of the embodiments of Proposals 1 to 8) may be stored in memory (e.g., 140, 240 of FIG. 10) in the form of instructions / programs (e.g., instruction, executable code) for driving at least one processor (e.g., 110, 210 of FIG. 10).

[0306] The embodiments described above will be explained in detail below with reference to FIGS. 8 and FIG. 9 regarding the operation of the terminal and base station. The methods described below are distinguished only for convenience of explanation, and it is understood that a part of one method may be substituted with a part of another method or combined with one another and applied.

[0307] FIG. 8 is a flowchart illustrating a method according to one embodiment of the present specification.

[0308] Referring to FIG. 8, a method according to one embodiment of the present specification includes a DCI receiving step (S810) and a PRACH transmission step (S820).

[0309] In S810, the terminal receives Downlink Control Information (DCI) related to a Physical Downlink Control Channel (PDCCH) order from the base station. For example, the DCI may be replaced by a PDCCH order (or DCI format 1_0) containing a Pathloss offset indicator field. More specifically, DCI format 1_0 is used for scheduling a Physical Downlink Shared Channel (PDSCH), but in certain cases, it may be utilized to initiate a random access procedure (e.g., a contention-free random access procedure or a contention-based random access procedure) rather than PDSCH scheduling. In other words, the PDCCH order may refer to a DCI format 1_0 containing information (field(s)) related to a random access procedure. For example, the field(s) associated with the above random access procedure may include at least one of a Random Access Preamble index, an SS / PBCH index, a PRACH Mask index, a Cell indicator, a PRACH association indicator, a PRACH retransmission indicator, a Pathloss offset indicator, a PRACH resource indicator, and / or a RACH occasion indicator.

[0310] In S820, the terminal transmits a Physical Random Access Channel (PRACH) to the base station.

[0311] For example, the above PRACH may be related to an asymmetric DL single-TRP and UL multi-TRP operation. As a specific example, the above PRACH may be directed toward one of a plurality of Transmit / Receive Points. As a specific example, the above PRACH may be directed toward a UL TRP (the aforementioned UL Rx point). As a specific example, the above PRACH may be directed toward a TRP different from the UL TRP (e.g., a macro cell or a TRP capable of performing DL transmission).

[0312] For example, the transmission power for the above PRACH can be determined based on the path loss (PL). The PL can be determined based on the reference signal (RS). In other words, the above PRACH is transmitted based on the transmission power. The transmission power can be determined based on the PL, and the PL can be determined based on the RS. The above DCI may include a path loss offset indicator field related to the path loss offset for the above PRACH.

[0313] According to one embodiment, the RS may be determined based on at least one of i) the number of at least one indicated TCI state (indicated Transmission Configuration Indicator, TCI, state), ii) the value of the Pathloss offset indicator field, and iii) whether the path loss offset is set within the at least one indicated TCI state. This embodiment may be based on Proposal 8. Embodiments of Proposal 8 will be described in detail below.

[0314] According to one embodiment, it may be assumed that one indicated TCI state (e.g., one indicated joint / UL TCI state) exists and the value of the Pathloss offset indicator field is 0 (bit field index 0). In this case, the RS may be determined based on the legacy PL-RS determination rule. Specifically, based on i) the number of the at least one indicated TCI state is 1 and ii) the value of the Pathloss offset indicator field is 0: the RS may be determined as the DownLink Reference Signal (DL RS) associated with the DeModulation-Reference Signal (DM-RS) of the PDCCH order. This embodiment may be based on [1-1] of Proposal 8.

[0315] According to one embodiment, it may be assumed that one indicated TCI state (e.g., one indicated joint / UL TCI state) exists and the value of the Pathloss offset indicator field is 1 (bit field index 1). In this case, the RS may be determined based on Alt 1 and / or Alt 3 of Proposal 7 described above. Specifically, based on i) the number of the at least one indicated TCI state is 1 and ii) the value of the Pathloss offset indicator field is 1: the RS may be determined as the RS associated with the at least one indicated TCI state of the PDCCH order. This embodiment may be based on [1-2] of Proposal 8 (Alt 1 of Proposal 7).

[0316] According to one embodiment, it may be assumed that one indicated TCI state (e.g., one indicated joint / UL TCI state) exists and the value of the Pathloss offset indicator field is 1 (bit field index 1). In this case, the RS may be determined based on Alt 1 and / or Alt 3 of Proposal 7 described above. Specifically, based on i) the number of the at least one indicated TCI state is 1 and ii) the value of the Pathloss offset indicator field is 1: the RS may be determined as the Synchronization Signal / Physical Broadcast Channel block (SS / PBCH block) indicated based on the DCI. This embodiment may be based on [1-2] of Proposal 8 (Alt 3 of Proposal 7).

[0317] According to one embodiment, it may be assumed that there are two indicated TCI states (e.g., two indicated joint / UL TCI states) and that a pathloss offset is not set in at least one of the two indicated TCI states. In this case, the RS may be determined based on the legacy PL-RS determination rule. Specifically, based on i) that the number of the at least one indicated TCI state is 2, and ii) that the pathloss offset is not set in the at least one indicated TCI state (e.g., one indicated TCI state or two indicated TCI states): the RS may be determined as the DownLink Reference Signal (DL RS) associated with the DeModulation-Reference Signal (DM-RS) of the PDCCH order. This embodiment may be based on [2-1] of Proposal 8.

[0318] According to one embodiment, it may be assumed that there are two indicated TCI states (e.g., two indicated joint / UL TCI states) and that a pathloss offset is set in the two indicated TCI states. In this case, the RS may be determined based on Alt 1 and / or Alt 3 of Proposal 7 described above. Specifically, based on i) that the number of the at least one indicated TCI state is 2, and ii) that the pathloss offset is set within the at least one indicated TCI state: the RS may be determined as the RS associated with the at least one indicated TCI state (e.g., the first indicated TCI state or the second indicated state). This embodiment may be based on [2-2] of Proposal 8 (Alt 1 of Proposal 7).

[0319] For example, based on the fact that the value of the Pathloss offset indicator field is 0, the RS can be determined as the RS associated with the first indicated TCI state among the at least one indicated TCI state.

[0320] For example, based on the fact that the value of the Pathloss offset indicator field is 1, the RS can be determined as the RS associated with the second indicated TCI state (second indicated TCI state) among the at least one indicated TCI state.

[0321] According to one embodiment, it may be assumed that two indicated TCI states (e.g., two indicated joint / UL TCI states) exist and a pathloss offset is set in the two indicated TCI states. In this case, the RS may be determined based on Alt 1 and / or Alt 3 of Proposal 7 described above. Specifically, based on i) the number of the at least one indicated TCI state is 2, and ii) the pathloss offset is set within the at least one indicated TCI state: the RS may be determined as a Synchronization Signal / Physical Broadcast Channel block (SS / PBCH block) indicated based on the DCI. This embodiment may be based on [2-2] of Proposal 8 (Alt 3 of Proposal 7).

[0322] Operations based on S810 to S820 described above can be implemented by the device of FIG. 10. For example, referring to FIG. 10, the terminal (200) can control one or more transceivers (230) and / or one or more memories (240) to perform operations based on S810 to S820.

[0323] The embodiments described above will be explained in detail below in terms of base station operation.

[0324] S910 to S920 described below correspond to S810 to S820 described in FIG. 8. Considering the above correspondence, redundant descriptions are omitted. The specific description of the base station operation described below may be replaced by the description / embodiment of FIG. 8 corresponding to the operation.

[0325] FIG. 9 is a flowchart illustrating a method according to another embodiment of the present specification.

[0326] Referring to FIG. 9, a method according to another embodiment of the present specification may include a DCI transmission step (S910) and a PRACH reception step (S920).

[0327] In S910, the base station transmits Downlink Control Information (DCI) associated with the PDCCH (Physical Downlink Control Channel) order to the terminal.

[0328] In S920, the base station receives a Physical Random Access Channel (PRACH) from the terminal.

[0329] For example, the transmission power for the above PRACH may be determined based on PathLoss (PL). The PL may be determined based on a Reference Signal (RS). In other words, the base station receives the above PRACH (transmitted by the terminal based on the transmission power). The transmission power may be determined based on the PL, and the PL may be determined based on the RS. The DCI may include a PathLoss Offset Indicator field related to the PathLoss Offset for the above PRACH.

[0330] According to one embodiment, the RS may be determined based on at least one of i) the number of at least one indicated TCI state (indicated Transmission Configuration Indicator, TCI, state), ii) the value of the Pathloss offset indicator field, and iii) whether the path loss offset is set within the at least one indicated TCI state.

[0331] Operations based on the above-described S910 to S930 can be implemented by the device of FIG. 10. For example, referring to FIG. 10, a base station (100) can control one or more transceivers (130) and / or one or more memories (140) to perform operations based on S910 to S930.

[0332] The operations / terms based on the embodiments described above are described assuming a 5G system. However, this is for the convenience of explanation and is not intended to limit the scope of application of the technical problems and means for solving problems to be solved by this specification to a specific system. The technical problems / technical issues / problems mentioned in this specification may exist in other systems (e.g., 6G systems). It is evident that the embodiments of this specification can be extended to solve problems that exist in other systems as well. Therefore, for the extended application of the embodiments of this specification to other systems, terms defined / described based on a 5G system may be replaced / changed with terms defined in said other systems (or generalized terms not specific to one system). For example, PRACH, PUSCH, PUCCH, or SRS may be replaced / changed to uplink signals (or uplink channels). For example, SSB, CSI-RS, PDSCH, and PDCCH may be replaced / changed to downlink signals (or downlink channels).

[0333] Hereinafter, an apparatus to which the embodiments of the present specification can be applied (an apparatus implementing the method / operation according to the embodiments of the present specification) will be described with reference to FIG. 10.

[0334] FIG. 10 is a drawing showing the configuration of a first device and a second device according to an embodiment of the present specification.

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

[0336] 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, RRC layer, or higher upper layers. The physical layer processing unit (115) may process operations of the PHY layer. For example, if 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, if 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).

[0337] The antenna section (120) may include one or more physical antennas, and if it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (130) may include an RF (Radio Frequency) transmitter and an RF receiver. The memory (140) may store information processed by the processor (110) and software, operating systems, applications, etc. related to the operation of the first device (100), and may include components such as a buffer.

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

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

[0340] 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) may process operations of the MAC layer, RRC layer, or higher upper layers. The physical layer processing unit (215) may process operations of the PHY layer. For example, if the second device (200) is a terminal device in base station-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, etc. For example, if the second device (200) is a second terminal device in terminal-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, sidelink reception signal processing, etc. In addition to performing baseband-related signal processing, the processor (210) may also control the overall operation of the second device (210).

[0341] The antenna section (220) may include one or more physical antennas, and may support MIMO transmission and reception if it includes multiple antennas. 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, operating systems, applications, etc. related to the operation of the second device (200), and may include components such as a buffer.

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

[0343] In the operation of the first device (100) and the second device (200), the details described in the examples of the present disclosure regarding the base station and terminal (or the first terminal and the second terminal in terminal-to-terminal communication) in base station-to-terminal communication may be applied in the same way, and redundant descriptions are omitted.

[0344] Here, the wireless communication technology implemented in the device of the present disclosure may include LTE, NR, and 6G, as well as Narrowband Internet of Things (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of Low Power Wide Area Network (LPWAN) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above.

[0345] Additionally or alternatively, the wireless communication technology implemented in the device of the present disclosure may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication). For example, 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 names mentioned above.

[0346] Additionally or generally, the wireless communication technology implemented in the device of the present disclosure may include at least one of ZigBee, Bluetooth, and a Low Power Wide Area Network (LPWAN) for low-power communication, but is not limited to the names mentioned above. 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 referred to by various names.

Claims

1. Regarding the method, A step of receiving Downlink Control Information (DCI) related to a PDCCH (Physical Downlink Control Channel) order; and The step of transmitting a Physical Random Access Channel (PRACH); wherein The transmission power for the above PRACH is determined based on PathLoss (PL), and the PL is determined based on a Reference Signal (RS). The above DCI includes a Pathloss offset indicator field related to the pathloss offset for the above PRACH, and A method characterized in that the above RS is determined based on at least one of i) the number of at least one indicated TCI state (indicated Transmission Configuration Indicator, TCI, state), ii) the value of the Pathloss offset indicator field, and iii) whether the path loss offset is set within the at least one indicated TCI state.

2. In Paragraph 1, i) based on the fact that the number of at least one indicated TCI state is 1, and ii) the value of the Pathloss offset indicator field is 0: A method characterized in that the above RS is determined as a DownLink Reference Signal (DL RS) associated with the DeModulation-Reference Signal (DM-RS) of the above PDCCH order.

3. In Paragraph 1, i) based on the fact that the number of at least one indicated TCI state is 1, and ii) the value of the Pathloss offset indicator field is 1: A method characterized in that the above RS is determined as the RS associated with at least one indicated TCI state of the above PDCCH order.

4. In Paragraph 1, i) based on the fact that the number of at least one indicated TCI state is 1, and ii) the value of the Pathloss offset indicator field is 1: A method characterized in that the above RS is determined as a Synchronization Signal / Physical Broadcast Channel block (SS / PBCH block) indicated based on the above DCI.

5. In Paragraph 1, i) based on the fact that the number of at least one indicated TCI state is 2, and ii) the fact that the path loss offset is not set within at least one indicated TCI state: A method characterized in that the above RS is determined as a DownLink Reference Signal (DL RS) associated with the DeModulation-Reference Signal (DM-RS) of the above PDCCH order.

6. In Paragraph 1, i) based on the fact that the number of at least one indicated TCI state is 2, and ii) the path loss offset is set within at least one indicated TCI state: A method characterized in that the above RS is determined as an RS associated with at least one indicated TCI state.

7. In Paragraph 6, A method characterized in that, based on the fact that the value of the above Pathloss offset indicator field is 0, the above RS is determined to be the RS associated with the first indicated TCI state among the at least one indicated TCI state.

8. In Paragraph 6, A method characterized in that, based on the fact that the value of the above Pathloss offset indicator field is 1, the above RS is determined as the RS associated with the second indicated TCI state (second indicated TCI state) among the at least one indicated TCI state.

9. In Paragraph 1, i) based on the fact that the number of at least one indicated TCI state is 2, and ii) the path loss offset is set within at least one indicated TCI state: A method characterized in that the above RS is determined as a Synchronization Signal / Physical Broadcast Channel block (SS / PBCH block) indicated based on the above DCI.

10. In the terminal, One or more transmitters / receivers; One or more processors; and One or more memories connected to the above one or more processors and storing instructions; comprising, A terminal characterized by the above instructions, based on execution by the one or more processors, causing the terminal to perform all steps of the method according to any one of claims 1 to 9.

11. A device comprising one or more memories and one or more processors connected to the one or more memories, An apparatus characterized in that the above one or more memories store instructions that cause the apparatus to perform all steps of the method according to any one of claims 1 to 9, based on execution by the above one or more processors.

12. In a non-transitory computer-readable medium storing instructions, A non-transitory computer-readable medium characterized by instructions executable by one or more processors such that the terminal performs all steps of the method according to any one of claims 1 through 9.

13. Regarding the method, A step of transmitting downlink control information (DCI) related to a PDCCH (Physical Downlink Control Channel) order; and The method includes the step of receiving a Physical Random Access Channel (PRACH); The transmission power for the above PRACH is determined based on PathLoss (PL), and the PL is determined based on a Reference Signal (RS). The above DCI includes a Pathloss offset indicator field related to the pathloss offset for the above PRACH, and A method characterized in that the above RS is determined based on at least one of i) the number of at least one indicated TCI state (indicated Transmission Configuration Indicator, TCI, state), ii) the value of the Pathloss offset indicator field, and iii) whether the path loss offset is set within the at least one indicated TCI state.

14. Regarding base stations, One or more transmitters / receivers; One or more processors; and One or more memories connected to the above one or more processors and storing instructions; comprising, A base station characterized by the above instructions, based on execution by one or more processors, having the base station perform all steps of the method according to claim 13.

Images