Method and apparatus for transmitting and receiving RAR (Radio-Augmented Reality)

Abstract

A method according to the embodiments of this specification includes the steps of receiving a PDCCH ORDER, transmitting a PRACH, receiving a PDCCH associated with a RAR, and receiving a PDSCH associated with the RAR. The PDCCH and PDSCH are received based on a QCL characteristic, where the CORESET associated with the PDCCH order is based on a second physical cell ID different from the first physical cell ID. The QCL characteristic is characterized by being based on a CORESET associated with a Type1-PDCCH CSS set.

Description

Technical Field

[0001] This specification relates to a method and apparatus for transmitting and receiving RAR.

Background Art

[0002] Mobile communication systems have been developed to provide voice services while ensuring user mobility. However, mobile communication systems have expanded their scope to include not only voice but also data services, and currently, due to an explosive increase in traffic, a shortage of resources has occurred, and users are demanding faster services, so more advanced mobile communication systems are required.

[0003] The requirements for next-generation mobile communication systems are large, and they must support the accommodation of explosive data traffic, an epochal increase in the transmission rate per user, the accommodation of a greatly increased number of connected devices, a very low end-to-end latency, and high energy efficiency. Therefore, various technologies such as dual connectivity, massive MIMO (Massive Multiple Input Multiple Output), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking are being studied.

[0004] On the other hand, when a random access procedure is started by a PDCCH order and a PRACH is transmitted, the following QCL (Quasi Co-Location) properties are assumed for the PDCCH / PDSCH related to a random access response (RAR).

[0005] Specifically, PDCCH / PDSCH and the PDCCH order have the same QCL characteristics. More specifically, the DMRS port of the PDSCH and the DMRS port of the PDCCH order are assumed to be QCL (quasi co-located) with respect to the same SS / PBCH block or CSI-RS resource. The "same SS / PBCH block or CSI-RS resource" may be one used for PRACH associations. The above example may apply to SpCell.

[0006] In this case, if the control resource set (CORESET) associated with the PDCCH order is associated with a cell different from the serving cell (a second cell), it may not be suitable to apply it as a QCL characteristic related to the reception of the RAR(PDCCH / PDSCH). Specifically, the following ambiguities exist.

[0007] Although the PRACH is transmitted to the second cell, the RAR may be received from the serving cell. In such a case, the QCL characteristics associated with the PDCCH order are suitable for reception from the second cell, but the QCL characteristics for the existingly defined RAR(PDCCH / PDSCH) may not be suitable for receiving the RAR(PDCCH / PDSCH) from the serving cell. The second cell may be i) a candidate cell associated with L1 / L2 triggered mobility, or ii) an additional PCI associated with a different CORESET pool index than the serving cell. [Overview of the Initiative] [Problems that the invention aims to solve]

[0008] As mentioned above, if the PDCCH order / PRACH is associated with a cell different from the serving cell, and the RAR is received from the serving cell, the existing defined QCL characteristics may not be suitable for the reception of the RAR.

[0009] The purpose of this specification is to propose a method for solving the aforementioned problems.

[0010] The technical problems that this specification seeks to solve are not limited to those mentioned above, and another technical problem not mentioned can be clearly understood by a person skilled in the art to which this invention pertains from the following description. [Means for solving the problem]

[0011] A method performed by a terminal in a wireless communication system according to one embodiment of this specification includes the steps of receiving a Physical Downlink Control Channel (PDCCH) order related to the initiation of a Random Access Procedure, transmitting a Physical Random Access Channel (PRACH), receiving a Physical Downlink Control Channel (PDCCH) related to a Random Access Response (RAR), and receiving a Physical Downlink Shared Channel (PDSCH) related to the RAR.

[0012] Based on the fact that the control resource set (CORESET) associated with the PDCCH order is associated with a second physical cell ID different from the first physical cell ID, the PDCCH and PDSCH are received based on the Quasi Co-Location properties (QCL properties).

[0013] The aforementioned QCL characteristics are characterized by being based on a Control Resource Set (CORESET) associated with the Type1-PDCCH Common Search Space (CSS)set.

[0014] The DMRS (DeMoulation Reference Signal) port associated with the PDSCH may be quasi-co-located with the DMRS port for PDCCH reception in the CORESET associated with the Type1-PDCCH CSS set, with respect to the QCL characteristics.

[0015] The QCL characteristics may include at least one of the following: Doppler shift, Doppler spread, average delay, delay spread, and / or spatial Rx parameter.

[0016] The first physical cellID and the second physical cellID may be associated with different CORESET pool indices.

[0017] The first physical cell ID may be based on the serving cell's PCI (Physical Cell Identity), and the second physical cell ID may be based on an additional PCI.

[0018] The first physical cell ID may be associated with the first Timing Advance Group. The second physical cell ID may be associated with the second TAG.

[0019] The method may further include receiving a configuration of a Synchronization Signal Block (SSB) associated with the additional PCI.

[0020] The additional PCI may be indicated based on the PDCCH order.

[0021] The method may further include receiving a configuration of a Random Access Channel (RACH) associated with the additional PCI.

[0022] The random access procedure may be associated with a special cell (SpCell) in which two Timing Advance Groups (TAGs) are configured.

[0023] The Type1-PDCCH CSSset may be associated with the serving cell.

[0024] A terminal according to other embodiments of the present specification includes one or more transceivers, one or more processors, and one or more memories connected to the one or more processors and storing instructions.

[0025] The instructions are configured such that, when executed by the one or more processors, the one or more processors execute all steps of any one of the methods.

[0026] An apparatus according to still other embodiments of the present specification includes one or more memories and one or more processors functionally connected to the one or more memories.

[0027] The one or more memories are configured to store instructions that, when executed by the one or more processors, cause the one or more processors to execute all steps of any one of the methods.

[0028] One or more non-transitory computer-readable media according to other embodiments herein store instructions. The instructions executable by one or more processors are configured to cause the one or more processors to execute all steps of any one of the methods.

[0029] A method performed by a base station in a wireless communication system according to other embodiments herein includes transmitting a Physical Downlink Control Channel (PDCCH) order related to initiation of a Random Access procedure, receiving a Physical Random Access Channel (PRACH), transmitting a Physical Downlink Control Channel (PDCCH) related to a Random Access Response (RAR), and transmitting a Physical Downlink Shared Channel (PDSCH) related to the RAR.

[0030] Based on the control resource set (CORESET) associated with the PDCCH order being associated with a second physical cell ID different from the first physical cell ID, the PDCCH and PDSCH are transmitted based on the Quasi Co-Location properties (QCL properties).

[0031] The aforementioned QCL characteristics can be based on a control resource set (CORESET) associated with the Type1-PDCCH Common Search Space (CSS) set.

[0032] A base station according to yet another embodiment of this specification includes one or more transceivers, one or more processors, and one or more memories connected to the one or more processors for storing instructions.

[0033] The instructions are characterized in that, based on the fact that they are to be executed by one or more processors, the one or more processors are configured to perform all the steps of the method. [Effects of the Invention]

[0034] If the cells associated with PDCCH order transmission (e.g., additional PCI or candidate cell) and the cells associated with RAR transmission (e.g., PCI of the serving cell) are different, applying existing defined QCL characteristics (e.g., QCL characteristics associated with PDCCH order) may result in incorrect reception of the RAR. In embodiments of this specification, the CORESET associated with PDCCH order is based on a second physical cell ID different from the first physical cell ID, and the PDCCH and PDSCH associated with RAR are received based on QCL characteristics (QCL characteristics based on the CORESET associated with the Type1-PDCCH CSS set). Therefore, if the cells associated with PDCCH order transmission and the cells associated with RAR transmission are different in a random access procedure, more suitable characteristics can be utilized to receive the RAR.

[0035] Furthermore, since PRACH retransmission and / or RAR retransmission can be prevented by RAR reception failure, random access procedures performed based on PCI of non-serving cells (e.g., additional PCI or PCI of candidate cells) can be improved in terms of signaling overhead and latency.

[0036] Furthermore, by increasing the probability of successful RAR reception, the delay between the completion of PCI-based random access procedures in non-serving cells and the execution of subsequent procedures can be minimized. For example, the point at which UL transmission operations can be performed based on TAs obtained via i) LTM cell switch-related procedures or ii) random access procedures can be brought forward.

[0037] The effects described herein are not limited to those mentioned above, and other effects not mentioned can be clearly understood by a person skilled in the art to which the present invention pertains from the following description. [Brief explanation of the drawing]

[0038] [Figure 1] MAC RAR according to embodiments of this specification is illustrated. [Figure 2] An example of a Timing Advance Command MAC CE according to an embodiment of this specification is provided. [Figure 3] The following describes the steps related to LTM to which the methods according to the embodiments of this specification may be applied. [Figure 4] This is a flowchart illustrating a method performed by a terminal according to one embodiment of this specification. [Figure 5] This is a flowchart illustrating a method performed by a base station according to other embodiments of this specification. [Figure 6] This figure shows the configurations of the first and second apparatus according to embodiments of this specification. [Modes for carrying out the invention]

[0039] Preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings. The detailed description disclosed below, together with the accompanying drawings, is intended to describe exemplary embodiments of the present invention and not to show only the embodiments in which the invention can be carried out. The following detailed description includes specific details in order to provide a complete understanding of the invention. However, those skilled in the art will see that the invention can be carried out without such specific details.

[0040] In some cases, known structures and devices may be omitted or shown in the form of block diagrams focusing on the core function of each structure and device, in order to avoid ambiguity of the concept of the present invention.

[0041] In the following, downlink (DL) refers to communication from a base station to a terminal, and uplink (UL) refers to communication from a terminal to a base station. In downlink, the transmitter can be part of the base station, and the receiver can be part of the terminal. In uplink, the transmitter can be part of the terminal, and the receiver can be part of the base station. The base station can also be described as the first communication device, and the terminal as the second communication device. The term base station (BS) can be replaced with terms such as fixed station, NodeB, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP), network (5G network), AI system, RSU (roadside unit), vehicle, robot, drone (unmanned aerial vehicle, UAV), AR (Augmented Reality) device, and VR (Virtual Reality) device. Furthermore, a terminal can be fixed or mobile, and can 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) equipment, M2M (Machine-to-Machine) equipment, D2D (Device-to-Device) equipment, vehicle, robot, AI module, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) equipment, and VR (Virtual Reality) equipment.

[0042] TA(Timing advance) related procedure

[0043] The transmission of uplink frame number i from the terminal (User Equipment, UE) is from the start of the downlink frame at that terminal to TTA(T TA ) must be started before.

[0044] The uplink timing (e.g., uplink frame) related to TTA is based on Table 1 below.

[0045] [Table 1]

[0046] The TTA in Table 1 can be calculated / determined based on the NTA and NTA,offset. The NTA and NTA,offset are set / applied as follows:

[0047] NTA: 1) Configured via RAR (Random Access Response), 2) Configured via Timing Advance Command (MAC-CE)

[0048] NTA, offset: 1) Set a specific value for each serving cell, 2) Apply a predefined value according to the Duplex mode / FR to the serving cell.

[0049] The following sections will provide a detailed explanation of the NTA, offset, and how to configure / apply the NTA.

[0050] NTA, offset

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

[0052] For example, a terminal can receive configuration information (e.g., ServingCellConfigCommon Information) from a base station, which includes information about NTA and offset. This configuration information can be received based on RRC signaling. Table 2 illustrates an example of this configuration information.

[0053] [Table 2]

[0054] Case 2) A method of applying predefined values ​​to the serving cell according to the Duplex mode / FR.

[0055] For example, a terminal can apply predefined NTA and offset values ​​according to the serving cell, depending on the Duplex mode (TDD / FDD) / FR. Table 3 below shows examples of NTA and offset values.

[0056] [Table 3]

[0057] NTA

[0058] Case 1) How to configure via RAR (Random Access Response)

[0059] For example, in a random access procedure (e.g., a 2-step RACH procedure or a 4-step RACH procedure), the terminal receives a RAR from the base station. Based on the RAR, the NTA can be determined / set. Specifically, the RAR may include a timing advance command. The timing advance command specifies an index value (e.g., an index value TA) related to timing adjustment. Based on the index value, the NTA can be determined (see Table 5 below). The RAR may be based on a MAC RAR. The following explanation will be given with reference to Figure 1.

[0060] Figure 1 illustrates a MAC RAR according to an embodiment of this specification.

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

[0062] [Table 4]

[0063] Table 5 illustrates transmission timing adjustments based on the Timing advance command.

[0064] [Table 5] JPEG2026520092000007.jpg212148JPEG2026520092000008.jpg206147JPEG2026520092000009.jpg208146JPEG2026520092000010.jpg109147

[0065] JPEG2026520092000011.jpg8147

[0066] Case 2) How to configure via Timing advance command (MAC-CE)

[0067] For example, the NTA can be set / determined based on MAC-CE. Specifically, the NTA is determined based on the Timing Advance Command MAC CE. The Timing Advance Command MAC CE may include a timing advance command. The determination of the NTA based on the timing advance command is the same as described in Case 1, so a redundant explanation will be omitted (see Table 5). The Timing Advance Command MAC CE will be explained below with reference to Figure 2.

[0068] Figure 2 illustrates a Timing Advance Command MAC CE according to an embodiment of this specification.

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

[0070] [Table 6]

[0071] TAG (Timing advance group)

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

[0073] [Table 7] JPEG2026520092000014.jpg213147

[0074] JPEG2026520092000015.jpg27146

[0075] Floor

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

[0077] [Table 8]

[0078] JPEG2026520092000017.jpg186146

[0079] JPEG2026520092000018.jpg127146

[0080] The details described above may be applied in combination with the methods proposed herein, as described later, or may be supplemented to clarify the technical features of the methods proposed herein. The methods described below are separated only for the sake of explanation, and it goes without saying that some components of one method may be substituted for some components of another method, or that they may be applied in combination with each other.

[0081] According to 3GPP® standards up to NR Rel-17, terminal mobility-based handover operations are performed as follows: The terminal reports an (L3-based) RSRP measurement to a candidate serving cell, which is a non-serving cell. Based on this report, the base station determines the handover and triggers a handover to the terminal. At this time, the terminal detaches from the serving cell and performs the RACH procedure to synchronize with the new cell. The terminal can then obtain TA information for the cell it intends to attach to through RAR reception.

[0082] In Rel-18 mobility enhancement, discussions are underway regarding base station / terminal operations that reduce delay during handover execution (by omitting the RACH procedure) by having the base station / terminal acquire TA information for such candidate serving cells before the handover command is issued (see Table 9 below). Two approaches are being considered for acquiring TA information for the relevant candidate (serving) cell: a RACH-based approach and a RACH-less approach.

[0083] [Table 9]

[0084] On the other hand, the following agreements were reached in Rel-18 mobility-TAmanagement, as shown in Table 10 below.

[0085] [Table 10] JPEG2026520092000021.jpg85146

[0086] JPEG2026520092000022.jpg200147JPEG2026520092000023.jpg90146

[0087] JPEG2026520092000024.jpg87147

[0088] In summary, the RACH-based approach for TA acquisition of candidate cells can utilize the PDCCH ordered CFRA procedure. Whether or not a RAR exists for the relevant RACH transmission can be determined based on the RRC. For RACH transmission to a candidate cell, a PRACH configuration for the candidate cell can be pre-configured on the terminal. The ordering DCI (PDCCH order DCI) can trigger the terminal's RACH transmission to the candidate cell. As an example, the ID of the candidate cell and / or the RACH resource for the candidate cell can be specified based on the DCI. If a RAR exists, there is discussion as to whether the RAR is transmitted in the serving cell or the candidate cell.

[0089] On the other hand, the QCL assumptions for RAR scheduling DCI and RAR PDSCH included in RAR(MSG2) can be based on Tables 11 and 12 below.

[0090] [Table 11]

[0091] The QCL assumption of PDCCH for scheduling RARs after PDCCH orderedRACH can be based on Table 11.

[0092] For example, in the case of PRACH associated with SpCell, the PDCCH order and the RAR scheduling PDCCH can have the same QCL characteristics.

[0093] For example, in the case of a PRACH associated with SCell, the RAR scheduling PDCCH can follow QCL characteristics based on CORESET associated with the Type1-PDCCH CSS set.

[0094] [Table 12]

[0095] QCL requirements for RAR PDSCH can be based on Tables 11 and 12.

[0096] As an example, regardless of the QCL assumption that received the RAR scheduling PDCCH, the RAR PDSCH may be received based on the SSB or CSI-RS QCL properties used during PRACH transmission.

[0097] For example, in the case of a PRACH associated with a SpCell, the DM-RS port(S) of the RAR PDSCH and the DM-RS port of the PDCCH order can be assumed to have been QCL'd with the same SS / PBCH block or CSI-RS resource. The SS / PBCH block (or CSI-RS resource) may be the SS / PBCH block (or CSI-RS resource) used in the PRACH assumption.

[0098] For example, in the case of PRACH associated with SCell, the QCL characteristics associated with RAR PDSCH may be the same as those of the SS / PBCH block (or CSI-RS resource) used in the PRACH assembly.

[0099] Based on the PDCCH order relating to a cell other than the serving cell (e.g., a candidate cell or additional PCI), RAR may be received from the serving cell or a non-serving cell.

[0100] As an example, there are three possible cases regarding the reception of the aforementioned RAR.

[0101] # Case 0: Receive RAR from serving cell

[0102] ex1) PDCCH order is received from non-serving cells & RAR is received from serving cells

[0103] ex2) PDCCH order is received from the serving cell & RAR is received from the serving cell

[0104] # Case 1: Receiving RAR from a non-serving cell

[0105] ex1) PDCCH order is received from the serving cell & RAR is received from the non-serving cell

[0106] # Case 2: Received all PDCCH order and RAR from a non-serving cell.

[0107] As an example, the three cases mentioned above may be related to Rel-18 LTM or inter-cell M-DCI-based M-TRP operation. Specifically, the PDCCH order can be associated with candidate cells.

[0108] As an example, the three cases described above can be associated with intercell M-DCI-based M-TRP operation. Specifically, the PDCCH order may be associated with an additional PCI. More specifically, the CORESET for the PDCCH order can be associated with an additional PCI. The additional PCI can be associated with a different CORESET pool index than the serving cell's PCI. The serving cell's PCI may be associated with CORESET pool index 0 (or 1), and the additional PCI may be associated with CORESET pool index 1 (or 0).

[0109] If both the PDCCH order DCI and the RAR scheduling DCI are transmitted by a serving cell, the QCL assumption between the two signals is no different from the existingly defined QCL assumptions (Tables 11 and 12 above). Specifically, according to existing definitions (e.g., Tables 11 and 12), the RAR PDCCH / PDSCH and PDCCH order can have the same QCL characteristics (e.g., SS / PBCH blocks or CSI-RS resources used for the PRACH assumption). Therefore, no problems may occur in RAR reception.

[0110] However, problems can arise in RAR reception when the PDCCH orderDCI and RAR schedulingDCI are transmitted by different cells (e.g., non-serving cell & serving cell or serving cell & non-serving cell). In other words, the QCL characteristics according to existing definitions (Tables 11 and 12) may not be suitable for application to RAR reception. This will be explained in detail below.

[0111] The cells associated with PDCCH order transmission and the cells associated with RAR(PDCCH / PDSCH) transmission are different. Therefore, receiving RAR(PDCCH / PDSCH) based on the QCL characteristics associated with only one of the cells (e.g., the same QCL characteristics as the PDCCH order) can be inefficient and may cause problems with RAR reception.

[0112] As a specific example, referring to Tables 11 and 12, the QCL characteristics related to the PDCCH order can be based on the SS / PBCH block or CSI-RS resource used for the PRACHa association. If such existing definitions are applied as is, the SS / PBCH block or CSI-RS resource may be an SS / PBCH block (or CSI-RS resource) used for PRACH transmission targeting a non-serving cell (e.g., a candidate cell or additionalPCI). Therefore, if QCL characteristics based on an SS / PBCH block (or CSI-RS resource) used for PRACH targeting a non-serving cell are applied to RAR reception from a serving cell, problems may occur with RAR reception.

[0113] The aforementioned problem will be referred to as <Problem 1>.

[0114] Furthermore, in Case 1, an additional Type 1 CSS can be configured on a per-cell basis at the terminal to receive RAR scheduling DCI from non-serving cells. This CSS can be configured / connected to a specific CORESET on the terminal. In this case, there may be ambiguity regarding what QCL aspects the specific CORESET should have. This issue is referred to as Problem 2.

[0115] Based on this background, this specification describes how a base station can configure / instruct RACH transmissions in the direction of a terminal's non-serving cell (candidate serving cell or additionalPCI) and how to transmit RACH responses, and proposes related terminal operations.

[0116] In this specification, " / " may be interpreted as "and," "or," or "and / or" depending on the context. Non-serving cells that can be targeted for terminal handover may be referred to interchangeably as candidate serving cell, candidate cell, target cell, target candidate cell, etc.

[0117] Furthermore, the base station may configure one or more candidate cell information before the handover command for Rel-18 LTM. This configuration of candidate cell information may include PCI, RACH configuration (e.g., RACH preamble, RACH occasion, RACH resource, and / or SSB index associated with each candidate cell), etc., for each candidate cell that is a non-serving cell that could potentially become a serving cell. For example, the procedure related to LTM may be based on Figure 3.

[0118] Figure 3 illustrates a procedure related to LTM to which the method according to the embodiments of this specification may be applied. Specifically, the procedure related to LTM may be carried out based on Table 13 below.

[0119] [Table 13] JPEG2026520092000028.jpg59146

[0120] JPEG2026520092000029.jpg190146

[0121] JPEG2026520092000030.jpg197148JPEG2026520092000031.jpg42146

[0122] An embodiment for solving the aforementioned problem 1 will be examined in detail in Proposal 1.

[0123] Proposal 1

[0124] Below, we will carefully examine in detail how base stations transmit RAR PDSCH.

[0125] For example, if the serving cell transmits both the RAR scheduling DCI and the RAR PDSCH (as a response to the RACH transmitted to the candidate cell), the assumption that the terminal receives the RAR PDSCH with the same QCL properties as the SSB associated with the PRACH transmitted to the non-serving cell, according to existing definitions (Tables 11 and 12), can be made impossible.

[0126] When a serving cell transmits the RAR PDSCH to a terminal, it can transmit it with the following QCL assumption. That is, when the terminal receives the RAR PDSCH, it can expect / assume the following QCL assumption.

[0127] Method 1: The terminal expects that even if a RAR PDSCH is transmitted by a serving cell, the RAR PDSCH will have the same QCL properties as the SSB associated with the PRACH transmitted to a non-serving cell (e.g., a candidate cell or additional PCI) at a previous point in time.

[0128] Method 2: The terminal expects the RAR PDSCH to have the same QCL characteristics as the PDCCH (transmitted by the serving cell), including the PDCCH order DCI.

[0129] Method 3: The terminal expects the RAR PDSCH to have the same QCL characteristics as the PDCCH, including the RAR scheduling DCI (transmitted by the serving cell). For example, these same QCL characteristics can be based on existing defined QCL characteristics (e.g., Tables 11 and 12). Specifically, these QCL characteristics can be based on the CORESET associated with the Type1-PDCCH CSS set.

[0130] As an example, the QCL characteristics of Method 3 can be based on Table 14 below.

[0131] [Table 14] JPEG2026520092000033.jpg44146

[0132] As an example, a terminal can receive a RAR PDSCH based on one of the methods 1 / 2 / 3. As an example, two or more combinations of the methods 1 to 3 (e.g., method 1 / 2 / 3, method 1 / 2, method 2 / 3, or method 1 / 3) can be configured by the base station. A terminal can receive a RAR PDSCH based on one of the configured combinations of methods.

[0133] For method 1 described above, some of the SSBs associated with the serving cell may be pre-configured to be associated with candidate cells (or additional PCIs). For example, a terminal can receive the configuration (or RACH configuration) of the SSB associated with each candidate cell (or additional PCI). A terminal can receive the RACH configuration for each candidate cell (or additional PCI).

[0134] For example, the SSB used by a terminal when transmitting RACH to a candidate cell (or additionalPCI) is the SSB configured for the candidate cell (or additionalPCI) (by the RACH configuration), but in reality, it could be the SSB associated with the serving cell.

[0135] Through Proposal 1, the terminal can receive RAR (RAR scheduling DCI and / or RAR PDSCH) without ambiguity in the QCL agreement.

[0136] An embodiment for solving the aforementioned problem 2 will be examined in detail in Proposal 2.

[0137] Proposal 2

[0138] Below, we will carefully examine in detail how base stations transmit RAR scheduling DCI and RAR PDSCH.

[0139] As an example, both the RAR scheduling DCI and RAR PDSCH may be transmitted by a non-serving cell (e.g., a candidate cell or additionalPCI) as a response to a RACH transmitted to a non-serving cell. In this case, an additional type 1 CSS for receiving the RAR scheduling DCI may be configured on the terminal on a per-non-serving cell basis. This CSS may be configured / connected to a specific CORESET on the terminal. In this case, the QCL assumption for the terminal to receive the RAR scheduling DCI may follow the QCL assumption configured / instructed to the aforementioned specific CORESET. The related behavior is examined in detail below.

[0140] When a terminal receives the RAR scheduling DCI, it can receive it (from the additional type 1 CSS) by utilizing the SSB QCL properties that were used when performing a RACH transmission (CFRA-based) to a non-serving cell at a previous point in time. In this case, the following settings / operations can be applied. For example, the CORESET configured / connected to the additional type 1 CSS may not have a reference RS or TCI state set for the QCL properties. For example, even if the CORESET configured / connected to the additional type 1 CSS has a reference RS or TCI state set for the QCL properties, the terminal can ignore that setting.

[0141] Furthermore, a specific CORESET may be instructed based on the DCI associated with the PDCCH order. Based on this, a RAR scheduling DCI may be transmitted. As an example, a terminal may receive a RAR scheduling DCI from a serving cell or non-serving cell associated with the specific CORESET.

[0142] Furthermore, when a terminal receives the RAR PDSCH, it can receive it by utilizing the SSB QCL properties that were used when performing a (CFRA-based) RACH transmission to a non-serving cell at a previous point in time (similar to the existing definition).

[0143] Below, we will carefully examine additional embodiments of Proposals 1 and 2.

[0144] It can be assumed that the RAR scheduling DCI is transmitted by the serving cell, and the RAR PDSCH is transmitted by the non-serving cell. The terminal can operate as follows: The terminal can receive the RAR scheduling DCI, as in legacy operation. The terminal can receive the RAR PDSCH based on Proposal 2.

[0145] It can be assumed that the RAR scheduling DCI is transmitted by the non-serving cell, and the RAR PDSCH is transmitted by the serving cell. The terminal can operate as follows: The terminal can receive the RAR scheduling DCI based on Proposal 2. The terminal can receive the RAR PDSCH based on Proposal 1.

[0146] The embodiments of Proposal 1 to Proposal 2 described above are also applicable to Case 2 described above.

[0147] Furthermore, the embodiments of Proposal 1 and Proposal 2 can also be applied to Rel-18 MIMO-2TA when triggering PDCCH orderCFRA to acquire TAs of TRP / TAG / CORESETPoolIndex related to additional PCI in an intercell M-DCI-based M-TRP environment.

[0148] Here, CORESET pool index 0 may be associated with serving cells, and CORESET pool index 1 may be associated with non-serving cells (additional PCI). For example, in this case, in case 0 / 1 / 2, "serving cell" may mean "TRP / TAG associated with CORESET pool index 0", and "non-serving cell" may mean "TRP / TAG associated with CORESET pool index 1". The physical cell ID (PCI) of a serving cell can be associated with CORESET pool index 0. The PCI (additional PCI) of a cell different from a serving cell (non-serving cell) can be associated with CORESET pool index 1.

[0149] Furthermore, embodiments of Proposal 1 and Proposal 2 may also apply to cases in Rel-18 MIMO-2TA where a particular TRP executes a cross-TRP RACH trigger in an intra / intercell M-DCI-based M-TRP environment, triggering a PDCCH ordered CFRA (for TA acquisition) for other TRPs. For example, in this case, in cases 0 / 1 / 2, "serving cell" may mean "TRP executing the PDCCH order," and "non-serving cell" may mean "TRP receiving the PRACH."

[0150] The embodiments described above (Proposal 1 to Proposal 2) can be applied to terminal / base station operations in combination of one or more embodiments.

[0151] An example of terminal (or base station) operation based on at least one of the embodiments described above (for example, at least one of Proposals 1 to 2) is as follows:

[0152] 1) The terminal (base station) receives (transmits) the candidate cell configuration information.

[0153] The configuration information for the candidate cell may include information based on at least one of Proposals 1 to 2. For example, the configuration information may include PCI, C_id, TAG id, and / or PRACH settings (configuration) associated with each candidate cell.

[0154] 2) The terminal (base station) receives (sends) a message to the candidate cell to set / instruct RACH transmission. The message may be a PDCCH that triggers / orders CFRA-based RACH.

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

[0156] 4) The terminal (base station) receives (transmits) RAR based on the RAR window.

[0157] The RAR can be received from a serving cell or a candidate cell. That is, the cell involved in the transmission of the RAR may be a serving cell or a candidate cell.

[0158] The transmission method and configuration of the RAR scheduling DCI and RAR PDSCH related to the aforementioned RAR can be based on at least one of Proposals 1 to 2.

[0159] The aforementioned terminal / base station operations are merely examples, and each operation (or step) is not necessarily required. Depending on how the terminal / base station is implemented, operations related to the RACHprocedure according to the above embodiment may be omitted or added.

[0160] In terms of implementation, the operation of the base station / terminal according to the above embodiment (for example, operation based on at least one of Proposals 1 to 2) can be processed by the device shown in Figure 6 (for example, processors 110 and 210 in Figure 6), which will be described later.

[0161] Furthermore, the operation of the base station / terminal according to the above embodiment (for example, operation based on at least one of Proposal 1 to Proposal 2) may also be stored in memory (for example, 140, 240 in Figure 6) in the form of instructions / programs (e.g., instruction, executable code) for driving at least one processor (e.g., 110, 210 in Figure 6).

[0162] The embodiments described above will now be specifically explained below with reference to Figures 4 and 5, focusing on the operational aspects of the terminal and base station. It should be noted that, for the sake of clarity, some configurations of one method may be replaced by others, or they may be applied in combination.

[0163] Figure 4 is a flowchart illustrating a method performed by a terminal according to one embodiment of this specification.

[0164] Referring to Figure 4, a method performed by a terminal according to one embodiment of this specification may include a PDCCH order receiving step S410, a PRACH transmission step S420, a PDCCH receiving step S430 related to RAR, and a PDSCH receiving step S440 related to RAR.

[0165] In S410, the terminal receives a Physical Downlink Control Channel (PDCCH) order from the base station related to the initiation of a Random Access Procedure.

[0166] As an example, the PDCCH order can be based on Downlink Control Information (DCI).

[0167] As an example, the aforementioned random access procedure may be a non-competitive random access procedure (Contention Free Random Access, CFRA).

[0168] As an example, the random access procedure may be a Type-1 random access procedure (4-step RACH) or a Type-2 random access procedure (2-step RACH).

[0169] For example, the random access procedure may be for a Special Cell (SpCell) or a Secondary Cell (SCell). Specifically, the random access procedure may be for a Special Cell (SpCell) with two Timing Advance Groups (TAAGs) configured. The SpCell may be a serving cell. The first physical cell ID, described later, may be the physical cell ID of the serving cell. The second physical cell ID, described later, may be associated with the second CORESET pool index of the two CORESET pool indexes.

[0170] More specifically, a control resource set (CORESET) is configured for the bandwidth (BANDWidth Part, BWP) of the serving cell (e.g., DL BWP). The CORESET may include a first CORESET based on a first CORESET pool index and a second CORESET based on a second CORESET pool index. The secondary physical cell ID may be associated with the second CORESET based on the second CORESET pool index. The secondary physical cell ID may be a physical cell ID based on additionalPCI.

[0171] For example, the PDCCH order may be associated with i) a first cell or ii) a second cell different from the first cell. The first cell may be a serving cell, and the second cell may be a non-serving cell. Specifically, the Control Resource SET (CORESET) used to transmit the PDCCH order may be based on i) a first CORESET pool index associated with the first cell or ii) a second CORESET pool index associated with the second cell. That is, the CORESET used to transmit the PDCCH order may be i) a first CORESET based on the first CORESET pool index or ii) a second CORESET based on the second CORESET pool index.

[0172] For example, the non-serving cell may be a candidate cell. The candidate cell may be one of the candidate cells configured on the terminal. Specifically, the candidate cell may be one of the candidate cells configured based on step 2 (LTM candidate cell configuration) in Figure 3 and Table 9. For example, the non-serving cell may be based on a physical cell ID (additionalPCI) associated with a CORESET pool index that is different from the physical cell ID of the serving cell.

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

[0174] As an example, the PRACH may be associated with the PCI (Physical Cell Identity) of the first cell or the PCI of the second cell.

[0175] In S430, the terminal receives a Physical Downlink Control Channel (PDCCH) associated with a Random Access Response (RAR) from the base station.

[0176] In S440, the terminal receives a Physical Downlink Shared Channel (PDSCH) related to the RAR from the base station.

[0177] As an example, the RAR may be received based on the PDCCH and the PDSCH. The PDSCH is scheduled based on the DCI associated with the DCCH (e.g., the RAR scheduling DCI). A transport block received based on the PDSCH may include the RAR.

[0178] As mentioned above in Problem 1, if the cell associated with the transmission of the PDCCH order (e.g., an additionalPCI-based non-serving cell) is different from the cell associated with RAR(PDCCH / PDSCH) (e.g., a serving cell), then receiving the PDCCH and PDSCH based on predefined QCL characteristics (e.g., the same QCL characteristics as the PDCCH order) can be inefficient or cause problems in RAR reception. Embodiments to solve such problems are described below in detail.

[0179] In one embodiment, the control resource set (CORESET) associated with the PDCCH order is associated with a second physical cell ID that is different from the first physical cell ID: the PDCCH and PDSCH may be received based on QCL properties (Quasi Co-Location properties).

[0180] In other words, the PDCCH and PDSCH can be received based on the same QCL characteristics. This embodiment can be based on Method 3 of Proposal 1 (e.g., Table 14). The QCL characteristics can be based on a Control Resource Set (CORESET) associated with a Type1-PDCCH Common Search Space (CSS) set. The Type1-PDCCH CSS set can be associated with a serving cell.

[0181] As an example, the DMRS port associated with the PDSCH may be quasi-co-located with the DMRS port for PDCCH reception. More specifically, the DMRS (DeMoulation Reference Signal) port associated with the PDSCH may be quasi-co-located with the DMRS port for PDCCH reception in the CORESET associated with the Type1-PDCCH CSS set, with respect to the QCL characteristics.

[0182] As an example, the QCL characteristics may include at least one of the following: Doppler shift, Doppler spread, average delay, delay spread, and / or spatial Rx parameter.

[0183] For example, the CORESET associated with the PDCCH order may be the CORESET used for PDCCH order transmission. The CORESET may be associated with one of several different CORESET pool indices. The CORESET may be the first CORESET or the second CORESET.

[0184] As a specific example, the first CORESET associated with the first CORESET pool index may be associated with the first physical cell ID (serving cell physical cell ID). The second CORESET associated with the second CORESET pool index may be associated with the second physical cell ID (another physical cell ID). The serving cell physical cell ID may be a physical cell ID (e.g., physCellId) based on the serving cell configuration (e.g., ServingCellConfigCommon) (related to the SpCell). The other physical cell ID may be a physical cell ID based on additionalPCI.

[0185] The fact that the CORESET is associated with the second physical cell ID means that the CORESET is not associated with the first physical cell ID. In other words, the fact that the CORESET is associated with the second physical cell ID means that the CORESET is the second CORESET.

[0186] As an example, the Type1-PDCCH CSS set may be associated with the serving cell (e.g., SpCell). Specifically, the Type1-PDCCH CSS set may be configured based on configuration information related to the serving cell (e.g., SIB1->ServingCellConfigCommonSIB->DownlinkConfigCommonSIB->initialDownlinkBWP->BWP-DownlinkCommon->pdcch-ConfigCommon->ra-SearchSpace). That is, the Type1-PDCCH CSS set may be configured based on the ra-SearchSpace parameter in pdcch-ConfigCommon included in the configuration information related to the serving cell.

[0187] For example, the first physical cellID and the second physical cellID may be associated with different CORESET pool indexes.

[0188] The first physical cell ID can be based on the serving cell's PCI (Physical Cell Identity). The second physical cell ID can be based on an additional PCI.

[0189] The first physical cell ID can be associated with the first Timing Advance Group. The second physical cell ID can be associated with the second TAG.

[0190] The method may further include the step of receiving an SSB configuration related to an additional PCI. In this step, the terminal receives from the base station the configuration of a Signal Signal Block (SSB) related to the additional PCI. This step may be performed prior to S410.

[0191] As an example, the configuration may include information regarding the Measurement Timing Configuration (MTC) of the SSB related to the additional PCI. The MTC may be related to the timing occasion of the SSB. The configuration may be based on SSB-MTC-AdditionalPCI. The SSB may include additional SSBs not used for the Serving Cell Quality Derivation (Measurement Timing Configuration, MTC). The additional SSB may be associated with a PCI different from the Serving Cell PCI. That is, the additional PCI may be a PCI of an additional SSB different from the Serving Cell PCI.

[0192] For example, the additional PCI may be indicated based on the PDCCH order. Specifically, the PCI related to PRACH transmission may be indicated based on the PDCCH order. The indicated PCI may be the PCI of the serving cell or the additional PCI. For example, the DCI related to the PDCCH order may include a field (e.g., a PRACHassociation indicator field) that indicates the PCI related to PRACH transmission.

[0193] The method may further include a RACH configuration reception step. In this step, the terminal can receive a Random Access Channel (RACH) configuration related to the additional PCI from the base station. This step may be performed prior to S410. As an example, the RACH configuration may include random access parameters for the additional PCI. The RACH configuration may be based on RACH-ConfigTwoTA.

[0194] The SSB configuration reception step, RACH configuration reception step, and operations based on S410-S440 related to the additional PCI mentioned above can be implemented by the device shown in Figure 6. For example, terminal 200 can control one or more transceivers 230 and / or one or more memories 240 to perform the SSB configuration reception step, RACH configuration reception step, and operations based on S410-S440 related to the additional PCI.

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

[0196] The SSB configuration transmission step, RACH configuration transmission step, and operations based on S510-S540 related to the additional PCI described later correspond to the SSB configuration reception step, RACH configuration reception step, and operations based on S410-S440 related to the additional PCI described in Figure 4. Considering this correspondence, redundant explanations are omitted. That is, the specific explanation of the base station operation described later is replaced by the explanation / embodiment in Figure 4 that corresponds to that operation.

[0197] Figure 5 is a flowchart illustrating a method performed by a base station according to other embodiments of this specification.

[0198] Referring to Figure 5, in other embodiments of this specification, a method performed by a base station may include a PDCCH order transmission step S510, a PRACH reception step S520, a PDCCH transmission step S530 related to RAR, and a PDSCH transmission step S540 related to RAR.

[0199] In S510, the base station transmits a Physical Downlink Control Channel (PDCCH) order to the terminal related to the initiation of a Random Access Procedure.

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

[0201] In S530, the base station transmits a Physical Downlink Control Channel (PDCCH) related to the Random Access Response (RAR) to the terminal.

[0202] In S540, the base station transmits the Physical Downlink Shared Channel (PDSCH) associated with the RAR.

[0203] The method may further include an SSB configuration transmission step related to an additional PCI. In this step, the base station transmits the configuration of a Signal Signal Block (SSB) related to the additional PCI to the terminal. This may be performed prior to step S510.

[0204] The method may further include a RACH configuration transmission step. In this step, the base station may transmit the Random Access Channel (RACH) configuration associated with the additional PCI to the terminal. This step may be performed prior to S510.

[0205] The SSB configuration transmission step, RACH configuration transmission step, and operations based on S510-S540 related to the additional PCI mentioned above can be implemented by the device shown in Figure 6. For example, the base station 100 can control one or more transceivers 130 and / or one or more memories 140 to perform operations based on the SSB configuration transmission step, RACH configuration transmission step, and operations based on S510-S540 related to the additional PCI.

[0206] The operations / terminology based on the embodiments described above are written assuming a 5G system. However, this is for illustrative purposes only and is not intended to limit the scope of application of the technical issues and solutions that this specification seeks to address to any particular system. That is, the technical issues / problems / issues mentioned herein may also exist in other systems (e.g., 6G systems). It is clear that the embodiments of this specification can be extended to address problems that may also exist in such other systems. Therefore, for the extension of the embodiments of this specification to other systems, terms defined / described based on a 5G system may be replaced / modified with terms defined in such other systems (or generalized terms that are not specific to one system).

[0207] For example, PRACH can be replaced with the first uplink channel.

[0208] For example, RAR can be replaced with a response associated with the first uplink channel.

[0209] For example, PDCCH and PDSCH can be replaced with the first downlink channel and the second downlink channel, respectively.

[0210] For example, DCI can be replaced with control information.

[0211] For example, "QCL characteristics (Quasi Co-Location properties) for receiving the PDCCH and PDSCH" can be replaced with "characteristics, settings, or parameters for receiving the first downlink channel and the second downlink channel."

[0212] In the following section, the apparatus to which the embodiments of this specification can be applied (apparatus that realizes the methods / operations according to the embodiments of this specification) will be described with reference to Figure 6.

[0213] Figure 6 shows the configurations of the first and second apparatus according to the embodiments of this specification.

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

[0215] The processor 110 performs baseband-related signal processing and may include a higher-layer processing unit 111 and a physical layer processing unit 115. The higher-layer processing unit 111 can process the MAC layer, RRC layer, or higher layer operations. The physical layer processing unit 115 can process the PHY layer operations. For example, if the first device 100 is a base station device in base station-terminal communication, the physical layer processing unit 115 can perform uplink received signal processing, downlink transmitted 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 can perform downlink received signal processing, uplink transmitted signal processing, sidelink transmitted signal processing, etc. In addition to performing baseband-related signal processing, the processor 110 can also control the overall operation of the first device 100.

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

[0217] The processor 110 of the first device 100 can 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 herein.

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

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

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

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

[0222] In the operation of the first device 100 and the second device 200, the matters described in the examples of this disclosure regarding the base station and terminal in base station-terminal communication (or the first terminal and second terminal in terminal-terminal communication) can be applied in the same manner, and redundant explanations will be omitted.

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

[0224] Additionally or alternatively, the wireless communication technology implemented in the devices 100, 200 of this disclosure can communicate based on LTE-M technology. For example, LTE-M technology is an example of LPWAN technology and is known by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented using 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.

[0225] Additionally or alternatively, the wireless communication technologies implemented in the devices 100, 200 of this disclosure may include, but are not limited to, at least one of ZigBee, Bluetooth (registered trademark), and Low Power Wide Area Network (LPWAN) technologies, with regard to low-power communication. For example, ZigBee technology can generate personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be referred to by a variety of names.

[0226] [Claims when filing an international application] [Claim 1] A method that is performed by the terminal, The steps include receiving a Physical Downlink Control Channel (PDCCH) order associated with the initialization of a Random Access procedure; Steps include: transmitting a Physical Random Access Channel (PRACH); The steps include receiving a Physical Downlink Control Channel (PDCCH) associated with a Random Access Response (RAR); The process includes the step of receiving a Physical Downlink Shared Channel (PDSCH) associated with the RAR; Based on the fact that the Control Resource SET (CORESET) associated with the PDCCHorder is associated with a second physical cell ID that is different from the first physical cell ID, The PDCCH and PDSCH are received based on QCL characteristics (Quasi Co-Location properties). A method characterized in that the QCL attribute is based on a Control Resource Set (CORESET) associated with a Type1-PDCCH Common Search Space (CSS) set. [Claim 2] The method according to claim 1, wherein the DMRS (DeMoulation Reference Signal) port associated with the PDSCH is quasi-co-located with the DMRS port for PDCCH reception in the CORESET associated with the Type1-PDCCH CSS set with respect to the QCL characteristics. [Claim 3] The method according to claim 1, characterized in that the QCL characteristics include at least one of Doppler shift, Doppler spread, average delay, delay spread, and / or spatial Rx parameter. [Claim 4] The method according to claim 1, characterized in that the first physical cellID and the second physical cellID are associated with different CORESET pool indices. [Claim 5] The method according to claim 4, characterized in that the first physical cell ID is based on the PCI (Physical Cell Identity) of the serving cell, and the second physical cell ID is based on an additional PCI. [Claim 6] The aforementioned first physical cell ID is associated with the first Timing Advance Group. The method according to claim 4, characterized in that the second physical cell ID is related to the second TAG. [Claim 7] The method according to claim 5, further comprising the step of receiving the setting of a Signal Signal Block (SSB) associated with the additional PCI. [Claim 8] The method according to claim 7, characterized in that the additional PCI is directed based on the PDCCH order. [Claim 9] The method according to claim 5, further comprising the step of receiving a Random Access Channel (RACH) setting associated with the additional PCI. [Claim 10] The method according to claim 1, characterized in that the random access procedure relates to a special cell (SpCell) in which two Timing Advance Groups (TAGs) are set. [Claim 11] The method according to claim 5, characterized in that the Type1-PDCCH CSS set is associated with the serving cell. [Claim 12] It is a terminal, One or more transceivers; With one or more processors; The system comprises one or more memory connected to one or more processors for storing instructions; A terminal characterized in that, based on the fact that the instructions are performed by the one or more processors, the one or more processors are configured to perform all the steps of the method according to any one of claims 1 to 11. [Claim 13] It is a device, One or more memory locations; The system comprises one or more memory units and one or more processors functionally connected to them; The apparatus is characterized in that the one or more memory stores instructions that, based on being executed by the one or more processors, cause the one or more processors to perform all the steps of the method described in any one of claims 1 to 11. [Claim 14] One or more non-transitory computer-readable media, It stores instructions. One or more non-transitory computer-readable media, characterized in that the instructions, which can be executed by one or more processors, are configured to cause the one or more processors to perform all steps of the method according to any one of claims 1 to 11. [Claim 15] A method performed by a base station, The steps include transmitting a Physical Downlink Control Channel (PDCCH) order related to the initialization of a Random Access procedure; The steps include receiving a Physical Random Access Channel (PRACH); The steps include transmitting a Physical Downlink Control Channel (PDCCH) associated with a Random Access Response (RAR), The process includes the step of transmitting a Physical Downlink Shared Channel (PDSCH) associated with the RAR; Based on the Control Resource Set (CORESET) associated with the aforementioned PDCCH order being associated with a second physical cell ID that is different from the first physical cell ID, The PDCCH and PDSCH are transmitted based on QCL characteristics (Quasi Co-Location properties). The method is characterized in that the QCL characteristics are based on a Control Resource SET (CORESET) associated with a Typel-PDCCH Common Search Space (CSS) set. [Claim 16] It is a base station, One or more transceivers; With one or more processors; The system comprises one or more memory connected to one or more processors for storing instructions; A base station characterized in that, based on the fact that the instructions are performed by the one or more processors, the one or more processors are configured to perform all the steps of the method according to claim 15.

Claims

1. A method that is performed by the terminal, The steps include receiving a Physical Downlink Control Channel (PDCCH) order associated with the initiation of a Random Access procedure; The steps include: transmitting on a Physical Random Access Channel (PRACH); The steps include: receiving a Physical Downlink Control Channel (PDCCH) associated with a Random Access Response (RAR); The process includes: receiving a Physical Downlink Shared Channel (PDSCH) associated with the RAR; Based on the fact that the control resource set (CORESET) associated with the PDCCHorder is associated with a second physical cell ID that is different from the first physical cell ID, The PDCCH and PDSCH are received based on QCL characteristics (Quasi Co-Location properties), The method is characterized in that the QCL attribute is based on a Control Resource Set (CORESET) associated with a Type1-PDCCH Common Search Space (CSS) set.

2. The method according to claim 1, wherein the DMRS (Demolition Reference Signal) port associated with the PDSCH is characterized in that, with respect to the QCL characteristics, it is QCL-coordinated with the DMRS port for PDCCH reception in the CORESET associated with the Type1-PDCCH CSS set.

3. The method according to claim 1, characterized in that the QCL characteristics include at least one of Doppler shift, Doppler spread, average delay, delay spread, and / or spatial Rx parameter.

4. The method according to claim 1, characterized in that the first physical cellID and the second physical cellID are associated with different CORESET pool indexes.

5. The method according to claim 4, characterized in that the first physical cell ID is based on the PCI (Physical Cell Identity) of the serving cell, and the second physical cell ID is based on an additional PCI.

6. The aforementioned first physical cell ID is associated with the first Timing Advance Group. The method according to claim 4, characterized in that the second physical cell ID is related to the second TAG.

7. The method according to claim 5, further comprising the step of receiving the setting of a Signal Signal Block (SSB) associated with the additional PCI.

8. The method according to claim 7, characterized in that the additional PCI is directed based on the PDCCH order.

9. The method according to claim 5, further comprising the step of receiving a Random Access Channel (RACH) setting associated with the additional PCI.

10. The method according to claim 1, characterized in that the random access procedure relates to a Special Cell (SpCell) in which two Timing Advance Groups (TAGs) are set.

11. The method according to claim 5, characterized in that the Type1-PDCCH CSS set is associated with the serving cell.

12. It is a terminal, One or more transceivers; One or more processors; The system comprises: one or more memories connected to one or more processors for storing instructions; A terminal characterized in that, based on the fact that the instructions are executed by the one or more processors, the one or more processors are configured to perform all the steps of the method according to any one of claims 1 to 11.

13. It is a device, One or more memory locations; The system comprises one or more memory units and one or more processors functionally connected to them; The apparatus is characterized in that the one or more memory stores instructions that, on the basis that they are to be executed by the one or more processors, cause the one or more processors to perform all the steps of the method according to any one of claims 1 to 11.

14. One or more non-transitor computer-readable media, It stores instructions. One or more non-transitory computer-readable media, characterized in that the instructions, which can be executed by one or more processors, are configured to cause the one or more processors to perform all the steps of the method according to any one of claims 1 to 11.

15. A method performed by a base station, The steps include transmitting a Physical Downlink Control Channel (PDCCH) order related to the initiation of a Random Access procedure; The steps include: receiving a Physical Random Access Channel (PRACH); The steps include transmitting a Physical Downlink Control Channel (PDCCH) associated with a Random Access Response (RAR), The process includes the steps of: transmitting a Physical Downlink Shared Channel (PDSCH) associated with the RAR; Based on the fact that the control resource set (CORESET) associated with the PDCCH order is associated with a second physical cell ID that is different from the first physical cell ID, The PDCCH and PDSCH are transmitted based on QCL characteristics (Quasi Co-Location properties). The method is characterized in that the QCL characteristics are based on a Control Resource Set (CORESET) associated with a Type-PDCCH Common Search Space (CSS) set.

16. It is a base station, One or more transceivers; One or more processors; The system comprises: one or more memories connected to one or more processors for storing instructions; A base station characterized in that, based on the fact that the instructions are performed by the one or more processors, the one or more processors are configured to perform all the steps of the method according to claim 15.

Images