Method and device for determining pseudo-collocation (QCL) characteristics in triggered cross-TRP random access

Abstract

A method performed by user equipment, comprising the steps of: receiving from a network entity a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) including an indication having a configuration for triggering or initiating an uplink transmission of a random access procedure to at least one target downlink reference signal; and determining a pseudo-collocation (QCL) assumption for the receipt of second downlink control information for scheduling a random access response (RAR) for an uplink transmission of a random access procedure.

Description

Technical Field

[0001] This application claims priority to and incorporates by reference in its entirety a U.S. Provisional Application (63 / 488,857) filed on Mar. 7, 2023.

[0002] Certain embodiments of the present invention relate to a feMIMO evolution work item in RAN1 and, more specifically, to multi-TA maintenance / operation for facilitating physical random access channel (PRACH) transmission triggered by a physical downlink control channel (PDCCH) order in multi-TRP operation.

Background Art

[0003] This section is intended to provide background or context for the present invention as claimed. The description herein may include concepts that might be pursued, but are not necessarily concepts that have been perceived or pursued in the past. Thus, unless otherwise indicated herein, what is described in this section is not prior art to the description and claims in this application and is not admitted to be prior art by inclusion in this section.

Summary of the Invention

Problems to be Solved by the Invention

[0004] The present invention relates to a feMIMO evolution work item in RAN1. More specifically, the present invention relates to multi-TA maintenance / operation.

Means for Solving the Problems

[0005] According to one exemplary embodiment, the device may include at least one processor and at least one memory. The memory may store instructions, which, when executed by the processor, cause the device to receive a physical downlink control channel (PDCCH) from a network entity that carries first downlink control information (DCI) having an indication that triggers or initiates an uplink transmission of a random access procedure to at least one target downlink reference signal; Determine a pseudo-collocation (QCL) assumption for the reception of second downlink control information that schedules a Random Access Response (RAR) for uplink transmission of a random access procedure.

[0006] According to one exemplary embodiment, the apparatus may include means for receiving from a network entity a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) having an indication configured to trigger or initiate an uplink transmission of a random access procedure to at least one target downlink reference signal; and means for determining a pseudo-collocation (QCL) assumption for receiving second downlink control information that schedules a random access response (RAR) for an uplink transmission of a random access procedure.

[0007] According to one exemplary embodiment, a method performed by user equipment may include: receiving a physical downlink control channel (PDCCH) from a network entity that carries first downlink control information (DCI) including an indication having a configuration that triggers or initiates an uplink transmission of a random access procedure to at least one target downlink reference signal; and determining a pseudo-collocation (QCL) assumption for the receipt of second downlink control information that schedules a random access response (RAR) for an uplink transmission of a random access procedure.

[0008] According to one exemplary embodiment, a non-temporary computer-readable storage medium stores instructions, and when the instructions are executed by at least one processor of the device, the device causes the device to: receive a physical downlink control channel (PDCCH) from a network entity, which includes first downlink control information (DCI) having an indication configured to trigger or initiate an uplink transmission of a random access procedure to at least one target downlink reference signal; and determine a pseudo-collocation (QCL) assumption for receiving second downlink control information that schedules a random access response (RAR) for an uplink transmission of a random access procedure. The uplink transmission may refer to the transmission of a PRACH preamble included in a random access procedure performed by the UE.

[0009] According to one exemplary embodiment, the network may include: at least one processor; and at least one memory for storing instructions, wherein when the instructions are executed by at least one processor, the network entity causes the UE to send a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) which includes an indication having a configuration that triggers or initiates at least one uplink transmission of a random access procedure (e.g., a random access preamble) to a target downlink reference signal transmitted by the device, wherein the indication is configured to determine a quasi-collocation (QCL) assumption for the reception of second downlink control information, and in response to receiving the PRACH preamble contained in the random access procedure transmitted by the UE, causes the UE to schedule the transmission of a random access response (RAR) to the UE based on the downlink control information.

[0010] According to one exemplary embodiment, the network entity comprises means for sending a physical downlink control channel (PDCCH) to a user equipment (UE) having an indication that triggers or initiates at the UE an uplink transmission of a random access procedure to at least one target downlink reference signal transmitted by a device, wherein the indication configures the UE to determine a pseudo-collocation (QCL) assumption for the reception of a second downlink control information; and means for scheduling the transmission of a random access response (RAR) to the UE based on the second downlink control information in response to receiving a PRACH preamble contained in a random access procedure transmitted by the UE.

[0011] According to one exemplary embodiment, a method performed by a network entity may include: sending a physical downlink control channel (PDCCH) to a user equipment (UE) having an indication that triggers or initiates an uplink transmission of a random access procedure to at least one target downlink reference signal transmitted by a device, wherein the indication configures the UE to determine a pseudo-collocation (QCL) assumption for the reception of a second downlink control information; and scheduling the transmission of a random access response (RAR) to the UE based on the second downlink control information in response to receiving a PRACH preamble contained in the random access procedure transmitted by the UE.

[0012] According to one exemplary embodiment, a non-temporary computer-readable storage medium stores an instruction, and when the instruction is executed by at least one processor of a network entity, the network entity sends a physical downlink control channel (PDCCH) to the UE, which has a configuration that triggers or initiates at least: a first downlink control information (DCI) at the user equipment (UE) for an uplink transmission of a random access procedure to at least one target downlink reference signal transmitted by the device, wherein the indication configures the UE to determine a quasi-collocation (QCL) assumption for the reception of a second downlink control information; and, in response to receiving a PRACH preamble contained in a random access procedure transmitted by the UE, schedules the transmission of a random access response (RAR) to the UE based on the second downlink control information.

[0013] Some examples of QCL assumptions can be described as follows: The target signal / channel may be received as PDCCH / PDCCH DMRS. If the UE can assume that the source and target signals have similar characteristics in at least one form of the following parameters: Doppler spread, Doppler shift, time delay, time spread, or beam, then the source signal, such as SSB or CSI-RS or CSI-RS for tracking (TRS), may be used to provide the UE with a QCL assumption about the reception of the target signal.

[0014] The source signal may provide UE logic via the TCI state. Upon receiving the source signal, the UE determines the above parameters to determine the channel estimation filter, and may then receive a target signal such as PDCCH / PDCCH DMRS and apply the determined channel estimation filter and the received beam (if the beam domain is applicable typically only in FR2).

[0015] Certain exemplary embodiments may provide a non-temporary computer-readable storage medium for storing instructions, which, when executed by at least one processor of the device, may cause the device to perform at least one or more of the methods herein. Various exemplary embodiments may provide one or more computer programs containing instructions, which, when executed by the device, may cause the device to perform one or more of the methods herein. Some exemplary embodiments may provide a device containing one or more circuits configured to perform one or more of the methods herein.

[0016] For a proper understanding of the exemplary embodiments, reference should be made to the accompanying drawings. [Brief explanation of the drawing]

[0017] [Figure 1] This figure shows an example of a system diagram illustrating the intra-cell multi-DCI cross-TRP RACH triggering operation. [Figure 2] This figure shows an example system diagram illustrating both inter-cell and intra-cell multi-DCI cross-TRP RACH triggering operation. [Figure 3] A diagram showing a set of devices according to various exemplary embodiments. [Modes for carrying out the invention]

[0018] It will be readily apparent that components of a particular exemplary embodiment may be arranged and designed in various different configurations, as generally described and shown in the figures herein. The same reference designation may be used in multiple figures to refer to the same element or function. The following is a detailed description of several exemplary embodiments of systems, methods, apparatus, and non-temporary computer program products for performing multi-timing advance (TA) maintenance / operation to facilitate physical random access channel (PRACH) transmissions (triggered PDCCH ordered PRCH) in multi-transmit / receive point (TRP) operation.

[0019] Currently, a cross-TRP, PDCCH-triggered RACH is being considered. Unresolved issues are the QCL characteristics and / or power control problems associated with PRACH transmissions. QCL characteristics refer to the receive assumptions about subsequent messages in a no-contradiction random access procedure. One problem with QCL characteristics is that a Type 1 common search space (used to monitor PDCCHs scheduling RARs on PDSCHs) does not necessarily have to be configured for a CORESET of a particular CORESET pool index. A CORESET under the same value of a CORESET pool index may sometimes be called a TRP. For example, a CORESET pool index (or TRP), which is the target for PRACH transmissions and the target for monitoring responses, does not necessarily have a search space (Type 1 common) configured to monitor random access responses. Random access responses are monitored on PDCCHs, more specifically on CORESETs. The PDCCH provides a second DCI that schedules a RAR to monitor the response for transmission (and the RAR may be scheduled by the second DCI and provided by the PDSCH). In some examples, the CORESET pool index may be called one or more TRPs. In some examples, the CORESET pool index is a value associated with a CORESET (Control Resource Set). CORESETs having the same value of CORESET pool index (e.g., 0 or 1) are considered to be grouped or pooled together. Therefore, the CORESET pool index may be called one or more associated CORESETs. CORESETs are used to monitor random access responses (e.g., DCIs that schedule random access responses). In addition to the QCL rules, transmit power control assumptions about PRACH need to be determined.

[0020] Figure 1 shows an example system diagram illustrating both inter-cell and intra-cell multi-DCI cross-TRP RACH triggering operation. Referring to Figure 1, in step 1, user equipment (UE) 102 may receive from a network entity (e.g., TRP 112) a physical downlink control channel (PDCCH) (e.g., spatial filter / beam 114) carrying first downlink control information (DCI) (see step 1) which includes an indication having a configuration to trigger or initiate an uplink transmission of a random access procedure (e.g., see step 2) to at least one target downlink reference signal (DL-RS1). In one example, the uplink transmission of random access may use a target downlink reference signal (DL-RS1) (e.g., shown in the first DCI that triggers the uplink transmission of the PRACH preamble) as a reference for the UL transmission. For multiple TRP operations within a cell, target DL-RS1 or DL-RS2 may be used. For both intra-cell and inter-cell operations, both DL-RS1 and DL-RS2 may be used. For example, DL-RS2 may be provided by a TRP112 (referenced in CORESET pool index #1) of the same PCI as the serving cell (intra-cell mTRP) or a different PCI (inter-cell mTRP).

[0021] UE102 may determine a pseudo-collocation (QCL) assumption for the reception of a second downlink control information (DCI) (see step 3 in Figure 1), which is used to schedule a random access response (RAR) (see step 4) for uplink transmission of a random access procedure (e.g., UL transmission of a PRACH preamble over a spatial filter / beam 104). Any example in this specification is not limited to any particular QCL type assumption. For example, the QCL assumption may be at least a type A QCL assumption (i.e., no type D, which may mean that UE102 does not need to use beamforming).

[0022] In one example, the QCL assumptions corresponding to each DL RS for the pseudo-collocation type are given by the higher layer parameter qcl type in QCL-Info and may take on one of the following values: - "Type A": {Doppler shift, Doppler spread, average delay, delay spread} - "Type B": {Doppler shift, Doppler spread} - "Type C": {Doppler shift, average delay} - "Type D": {Spatial Rx parameter}

[0023] Conventionally, in some exemplary cases, RACH according to a PDCCH order may have the following QCL assumptions: (a) The first DCI format indicating RACH according to the PDCCH order is typically transmitted using the same DL-RS1 as a reference for the target DL-RS for PRACH transmission (e.g., DL-RS1 -> SSB index); (b) UE102 determines to estimate the path loss for UL power control for RACH transmission based on DL-RS1 that is quasi-collocated (QCL’d) with the DMRS of the PDCCH carrying the PDCCH order (DCI message); (c) The second DCI scheduling the RAR is assumed to be QCL’d with the DCI triggering the PDCCH order (see step 1 of FIG. 1); (d) The PDSCH carrying the RAR is QCL’D with the second DCI scheduling the RAR (see step 3 of FIG. 1). When UE102 attempts to detect DCI format 1_0 using a cyclic redundancy check (CRC) scrambled by the corresponding random access radio network temporary identifier (RA-RNTI) in response to a PRACH transmission initiated by a PDCCH order triggering a contention-free random access procedure for a special cell (SpCell) [11, TS 38.321], UE102 may assume that the PDCCH containing the second DCI format 1_0 and the PDCCH order may have the same DM-RS antenna port quasi-collocation characteristics.

[0024] Referring to the PDCCH order (see Step 1 in Figure 1), the current problem with cross-TRP triggering is that if the UE assumes that the response to a PRACH transmission is monitored according to the target DL-RS (targeted behavior / functionality) of the PRACH transmission, then after the PRACH (see Step 2) is triggered for DL-RS2, there may be QCL relations / power control, but the target CORESET pool index does not have to be configured with a CORESET related to type 1-PDCCH CSS (common search space). This could mean that UE102 may not be able to monitor the response to a PRACH transmission according to the CORESET of the target CORESET pool index. Similarly, when the order is triggered by a first TRP112 (scheduled with respect to the CORESET of CORESET pool index #0) and the target is DL-RS of CORESET pool index #1 (or vice versa), there is ambiguity as to how the UE monitors the response. In other words, the UE behavior may not be clear in these situations with respect to legacy rules.

[0025] As shown in Figure 2, multi-DCI based multi-TRP operation using two timing advance (TA) enhancements is TRP X The PDCCH order sent by (i.e., the RACH procedure by the PDCCH order) will TRP for both inter-cell and intra-cell multi-DCIs. X or TRP Y This provides support for triggering the RACH procedure. In one example, this disclosure includes considering the details of PRACH power control and QCL determination of the PDCHH order, PDCCH RAR (scheduling RAR), or PDSCH RAR.

[0026] In the implementation, there may be two CORESET pool indexes, 0 and 1, which may be TRP indexes (logical indexes). If the PDCCH order originates from a CORESET associated with CORESET pool index 0, the other index may refer to CORESET pool index 1 (and vice versa).

[0027] In any example of the examples herein, the QCL assumption for a PDCCH may refer to the QCL assumption for a PDCCH demodulation reference signal (DMRS). For example, when a PDCCH is DL-RS and QCL'd, it may refer to PDCCH DMRS being DL-RS and QCL'd. In some examples, DL-RS may be included in a TCI state configuration. Thus, in some examples, a TCI state (or a DL-RS included in a TCI state) may be a PDCCH or PDSCH (DMRS) and QCL'd. In some examples, a DL-RS included in a TCI state configuration may be used as a reference for uplink transmission (e.g., PUCCH / PUSCH). A TCI state may include / consist of one DL-RS having a first QCL type (e.g., type A) and / or two DL-RS having a first QCL type (e.g., type A) and a second DL-RS having a second QCL type (e.g., type D). If the TCI state has two QCL types, the UE may use a DL-RS with QCL type D.

[0028] According to this embodiment, the first downlink control information may indicate a first value (e.g., = 0) which may cause the UE102 to determine a pseudo-collocation assumption for the PDCCH carrying a second DCI that schedules a random access response, such that it is the same as the first DCI that triggers or initiates a random access procedure.

[0029] For example, in step 1 of Figure 2, if the downlink control information indicates a first value (e.g., = 0), UE202 may assume that the QCL assumption for the PDCCH (PDCCH DMRS) carrying the second DCI that schedules the random access response is the same as the PDCCH (DMRS) used to transmit the first DCI that triggered the PDCCH order.

[0030] In one example (Option 1), if the first downlink control information indicates a second value (e.g., =1), the UE202 assumes that the QCL assumption for the PDCCH carrying the second DCI that schedules the random access response is the same as the DL RS indicated as the target reference signal (RS) for the PRACH transmission (or DL ​​RS associated with the PRACH transmission).

[0031] In another example (Option 2), if the first downlink control information (DCI) indicates a second value (e.g., =1), the UE202 may assume that the QCL assumption for the PDCCH carrying the second DCI that schedules the random access response is the same as the DL RS of one TCI state with an activated TCI state of a different CORESET pool index value indicated as the target RS for the PRACH transmission.

[0032] In the implementation, one TCI state of an activated TCI state may include one of the following: the lowest active TCI state identifier in the active TCI state list, the most recently activated TCI state in the active TCI state list, or the lowest active TCI code point in the active TCI state list.

[0033] In another example (Option 3), the downlink control information may indicate whether a first or second indicated TCI state is used as a QCL assumption for the PDCCH (DMRS) used to transmit a second DCI that schedules the random access response. In one example, whether the random access response follows the indicated TCI state (i.e., is assumed to be transmitted) (as a QCL criterion) may be configured (e.g., by RRC) and / or indicated in a field within the DCI that triggers the PDCCH order. In one example, if the random access response is configured to be monitored using the indicated TCI state as an assumption for the second DCI that schedules the random access response, the UE may determine the QCL assumption based on the indicated TCI state.

[0034] In another example (Option 4), downlink control information may indicate whether a random access response is monitored with respect to the CORESET pool index value that triggered the transmission, or whether the PDCCH order is monitored with respect to a different CORESET pool index than the index on which it was triggered. A CORESET pool index may contain one or more CORESETs.

[0035] In any of the above embodiments, if the first downlink control information indicates a second value (e.g., =1), the QCL assumption for the PDSCH scheduled by the second DCI, whose QCL assumption is determined as described above, may be the same as the determined QCL assumption for the PDCCH(DMRS) used to schedule the second DCI that schedules the random access response.

[0036] In one further embodiment, if the downlink control information indicates a second value (e.g., =1), the first triggering DCI is scheduled with respect to a CORESET configured with CORESET pool index value 0, and the UE202 determines that the random access response is to be monitored with respect to the CORESET having pool index #1 (or vice versa). In one further example, if either CORESET (with pool index #1 or pool index #0, depending on the indication used to send the first triggering DCI) is not associated with CSS type 1 (the search space used to monitor RAR responses), the UE may decide to monitor the random access response using a C-RNTI (cell radio network temporary identifier) ​​(or RA-RNTI) on the UE-specific search space (USS), or a type 3 CSS of at least one CORESET ID associated with pool index #1 (or pool index #0).

[0037] In a further example, the UE may decide to monitor random access responses using a Type 3 CSS on at least one CORESET ID associated with a C-RNTI (or RA-RNTI) or pool index #1 (or pool index #0) on the USS. In a further example, the UE may decide to monitor random access responses using a C-RNTI (or RA-RNTI) on any of the CSSs consisting of at least one CORESET ID associated with pool index #1 (or pool index #0). Monitoring may be based on at least one of the following: the lowest CORESET ID, a CORESET ID that follows an indicated unified TCI state (or the lowest / highest CORESET ID), or a CORESET ID (lowest / highest) that is not associated with a unified TCI state.

[0038] In one further embodiment, if the information in the first DCI triggering of a PDCCH order indicates a first value, it may indicate that the UE monitors the random access response using the same QCL assumption as the PDCCH(DMRS) used to schedule the first triggering DCI. In one further exemplary embodiment, if the information in the first DCI triggering of a PDCCH order indicates a second value, it may indicate that the UE monitors the random access response using the QCL assumption of the target DL-RS indicated by the first triggering DCI. In one further embodiment, if the information in the first DCI triggering of a PDCCH order indicates a second value, it may indicate that the UE monitors the random access response using the determined QCL assumption of the CORESET for a different CORESET pool index value used to send the first triggering DCI. The QCL assumption may be a indicated or activated TCI state associated with a different CORESET pool index value than the PDCCH(DMRS) used to schedule the first triggering DCI, which was used to be t (for example, = 1, or it indicates that the UE will use a CORESET of another CORESET pool index for response monitoring).

[0039] In one further embodiment, if the first downlink control information indicates a second value (e.g., =1), and the first triggering DCI is scheduled with respect to a CORESET configured with CORESET pool index value 0, and the UE decides to monitor the response with respect to a CORESET having pool index #1, and the CORESET (of pool index #1) is not associated with CSS type 1 (the search space used to monitor RAR responses), then the UE may decide to monitor the response using a C-RNTI (or RA-RNTI) on the USS or a type 3 CSS of at least one CORESET ID associated with pool index #1. Monitoring may be based on: the lowest CORESET ID, a CORESET ID following the indicated unified TCI state (or the lowest / highest CORESET ID), or a CORESET ID (lowest / highest) not associated with the unified TCI state. The above embodiments may also be considered to be the reverse with respect to the CORESET pool index # value.

[0040] In one embodiment, the interpretation of the first and second values ​​may depend on the CORESET (configured using the CORESET pool index value) on which the first DCI triggering of the random access procedure by the PDCCH order is scheduled. Therefore, the interpretation of the information fields in the first DCI (providing the first value / second value / single value of the value) may be conditionally interpreted or have a dependency on further parameters or assumptions. For example, if the CORESET transmitting the PDCCH carrying the first DCI (PDCCH order) is configured using the CORESET pool index #0, one of the values ​​in the information field (e.g., 1) may point to the CORESET pool index #1. For example, if the CORESET is configured using the CORESET pool index #1, one of the values ​​in the information field (e.g., 1) may point to the CORESET pool index #0. Therefore, the UE202 may interpret the values ​​in the first DCI (PDCCH order) depending on the CORESET's relevance to the CORESET pool index. As a further example, the first value may indicate that the UE monitors the Random Access Response (RAR) for the CORESET of the same CORESET pool index used to send the first DCI (PDCCH order). The second value may indicate that UE202 monitors the Random Access Response for the CORESET of other / different CORESET pool indexes used to send the DCI (PDCCH order).

[0041] In one embodiment, the association of the value and information field with respect to the CORESET pool index may be configurable. For example, a first value (e.g., 0) is configured to indicate a first value (e.g., 0) of the CORESET pool index. In another example, a second value (e.g., 1) is configured to indicate a second value (e.g., 1) of the CORESET pool index. In one example, the first value may indicate that the UE monitors random access responses with respect to the CORESET of the CORESET pool index associated with the value (e.g., 0). The second value may indicate that UE202 monitors random access responses with respect to the CORESET of the CORESET pool index associated with the second value (e.g., 1). Thus, random access response monitoring (and the selection of the CORESET pool index for determining assumptions for random access response monitoring) is determined by UE202 based on the information field indicating the CORESET pool index value.

[0042] In one embodiment, one field in a first DCI that triggers random access by PDCCH order may indicate whether the UE is monitoring the RA response with respect to CSS (e.g., using RA-RNTI or C-RNTI) or monitoring the RA response with respect to USS (e.g., using C-RNTI or RA-RNTI).

[0043] In one further embodiment, if the information indicates a second value (e.g., = 1, or the information indicates that the UE will use a CORESET from another CORESET pool index for response monitoring), and the SSB (or target DL-RS2) is configured as a QCL source for one TCI state (e.g., an activated TCI state), the UE 202 may determine the path loss 204 for PRACH power control based on the SSB (or target DL-RS2) associated with the PRACH preamble, or, if the SSB (or target DL-RS2) is a QCL source for a TCI state, based on the PDCCH DMRS for the indicated TCI state. The target DL-RS2 may be either the SSB or the CSI-RS.

[0044] In one embodiment, UE202 may determine the path loss 204 for PRACH power control based on the SSB (or DL-RS2) included in the indicated TCI state. In one example, UE202 may base power control on the indicated TCI state for the CORESET pool index. In one example, UE may base power control on the indicated TCI (DL-RS2 included in the TCI state) state for the CORESET pool index value when a first DCI carrying a PDCCH order indicates that a random access response is being monitored for a CORESET with a different CORESET pool index value used by the CORESET to transmit the DCI (PDCCH order).

[0045] In one example, the second value / one value of the value indicated by the first DCI (PDCCH order) may indicate that UE202 is monitoring a DCI that schedules a random access response for a CORESET of a different CORESET pool index than the CORESET pool index used to send the second DCI that triggered the random access transmission. If the indicated TCI state includes two DL-RSs (i.e., DL-RS1, DL-RS2), UE202 may use DL-RSs configured with QCL type D.

[0046] In any embodiment of this specification, the first DCI includes first and second values, which may be provided in the form of (bit) fields within a first DCI message that triggers a random access procedure by PDCCH order. The presence or absence of the fields may be configurable by the network (i.e., via RRC signaling). Instead of referring to them as first and / or second values, the information may be referred to as "one of the values." The values, first and second, may also be interchangeable with each other and vice versa (first = 1 and second = 0).

[0047] Figure 3 shows a set of devices according to various exemplary embodiments.

[0048] According to certain exemplary embodiments, the device 320 may be further prompted to perform multi-timing advance (TA) maintenance / operations in multi-TRP operation to facilitate triggered physical random access channel (PRACH) transmissions in physical downlink control channel (PDCCH) order.

[0049] Figure 3 shows a set of apparatuses 310 and 320 in various exemplary embodiments that perform the steps and functions shown in Figures 1-2. In various exemplary embodiments, apparatus 310 may be an element in or related to a communication network, such as a UE, RedCap UE, SL UE, mobile equipment (ME), mobile station, mobile device, fixed device, IoT device, or other user device. For example, UE 102 or 202 may be an example of apparatus 310 according to the various exemplary embodiments discussed above. It should be noted that those skilled in the art will understand that apparatus 310 may include components or features not shown in Figure 3. Furthermore, apparatus 320 may be a network, network entity, core network element, or an element in or related to a communication network, such as a base station, NE, or gNB. For example, the network and gNBs 112, 212, and 216 may be examples of apparatus 320 according to the various exemplary embodiments discussed above. It should be noted that those skilled in the art will understand that the apparatus 320 may include components or features not shown in Figure 6.

[0050] According to a first exemplary embodiment of the device 310 (i.e., user devices 102, 202) shown in Figure 1-2, the device 310 (i.e., user devices 102, 202) may include at least one processor 312 and at least one memory 314, as shown in Figure 3. The memory 314 may store instructions, which, when executed by the processor 312, cause the device 310 to receive a physical downlink control channel (PDCCH) from a network entity 320 (i.e., network entities 112 or 212 and 216 shown in Figure 1-2) carrying first downlink control information (DCI) having an indication configured to trigger or initiate an uplink transmission of a random access procedure to at least one target downlink reference signal; and cause the device 310 to determine a pseudo-collocation (QCL) assumption for the reception of second downlink control information that schedules a random access response (RAR) for an uplink transmission of a random access procedure.

[0051] According to a second exemplary embodiment of the apparatus 310 (i.e., user equipment 102, 202) shown in Figure 1-2, the downlink control information indicates a first value that causes the apparatus to determine a pseudo-collocation assumption for the PDCCH carrying a second DCI that schedules the random access response, such that it is the same as the first DCI that triggers or initiates the random access procedure.

[0052] According to a third exemplary embodiment of the apparatus 310 (i.e., user equipment 102, 202) shown in Figure 1-2, the first downlink control information indicates a second value that causes the apparatus to determine a pseudo-collocation assumption for the PDCCH carrying a second DCI that schedules a random access response, such that it is the same as at least one downlink reference signal indicated by the received first DCI, carried by the PDCCH, as a target reference signal that triggers the uplink transmission of the random access procedure.

[0053] According to a fourth exemplary embodiment of the apparatus 310 (i.e., user equipment 102, 202) shown in Figure 1-2, the first downlink control information indicates a second value which causes the apparatus to determine a pseudo-collocation (QCL) assumption for a PDCCH carrying a second DCI when scheduling a random access response, such that it is the same as at least one downlink reference signal of a Transmit Control Indicator (TCI) state indicated by a CORESET pool index value different from the index value used to schedule the PDCCH, which includes an indication that triggers an uplink transmission of the random access procedure.

[0054] According to a fifth exemplary embodiment of the apparatus 310 (i.e., user equipment 102, 202) shown in Figure 1-2, the first downlink control information indicates a second value which causes the apparatus to determine a pseudo-collocation assumption for a PDCCH carrying a second DCI that schedules a random access response, such that it is the same as at least one downlink reference signal of at least one TCI state with an activated CORESET pool index value different from the CORESET pool index value used to trigger the uplink transmission of the random access procedure.

[0055] According to a sixth exemplary embodiment of the device 310 (i.e., user devices 102, 202) shown in Figure 1-2, one TCI state of an activated TCI state includes: one of the following: the lowest active TCI state identifier in the active TCI state list, the most recently activated TCI state in the active TCI state list, or the lowest active TCI code point in the active TCI state list.

[0056] According to a seventh exemplary embodiment of the apparatus 310 (i.e., user equipment 102, 202) shown in Figure 1-2, the downlink control information indicates a first or second value used as a QCL assumption for a PDCCH carrying a second DCI that schedules a random access response, such that the indication is the same as a first indicated TCI state when the indication shows a first value and a second indicated TCI state when the indication shows a second value.

[0057] According to an eighth exemplary embodiment of the device 310 (i.e., user devices 102, 202) shown in Figure 1-2, the downlink control information indicates a second value that causes the device to determine a pseudo-collocation assumption for a PDCCH carrying a second DCI that schedules a random access response, based on a CORESET pool index value associated with the PDCCH, the first value indicating that the QCL assumption for monitoring the response is determined to be in the same CORESET pool index value used to trigger the first DCI indicating RACH, and the second value indicating that the QCL assumption for monitoring the response is determined to be in a different CORESET pool index value used to trigger the first DCI indicating RACH.

[0058] According to the ninth exemplary embodiment of 310 (i.e., user devices 102, 202) shown in Figure 1-2, the first downlink control information indicates a second value that causes the device to determine a pseudo-collocation assumption for the PDCCH carrying a second DCI that schedules random access responses, based on a configuration of whether or not a common search space type used to monitor the second DCI that schedules random access responses is configured.

[0059] According to a tenth exemplary embodiment of the device 310 (i.e., user devices 102, 202) shown in Figure 1-2, the device is configured to decide to monitor the PDCCH carrying scheduling commands for random access responses with respect to at least one of the following: the lowest CORESET ID, a CORESET ID that follows a unified TCI state, or a CORESET ID (lowest) that is not related to a unified TCI state.

[0060] According to an eleventh exemplary embodiment of the apparatus 310 (i.e., user equipment 102, 202) shown in Figure 1-2, the uplink transmission of the random access procedure includes the transmission of a PRACH preamble associated with at least one target downlink reference signal.

[0061] According to a twelfth exemplary embodiment of the network entity 320 shown in Figure 1-2 (i.e., network entities 112, 212, 216), the network entity 320 may include: at least one processor 322; and at least one memory 324 for storing instructions, where, when executed by at least one processor, the network entity causes the UE to send a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) which includes an indication having a configuration that triggers or initiates at least one uplink transmission of a random access procedure to a user equipment (UE) for at least one target downlink reference signal transmitted by the device; the indication configures the UE to determine a pseudo-collocation (QCL) assumption for the reception of second downlink control information; and in response to receiving a PRACH preamble contained in the random access procedure transmitted by the UE, causes the UE to schedule the transmission of a random access response (RAR) to the UE based on the second downlink control information.

[0062] According to a thirteenth exemplary embodiment of the device 310 (i.e., user devices 102, 202) shown in Figure 1-2, the device includes means for receiving from a network entity a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) having an indication configured to trigger or initiate an uplink transmission of a random access procedure to at least one target downlink reference signal, and means for determining a pseudo-collocation (QCL) assumption for receiving second downlink control information that schedules a random access response (RAR) for an uplink transmission of a random access procedure.

[0063] According to a fourteenth exemplary embodiment of the method performed by the apparatus 310 (i.e., user equipment 102, 202) shown in Figure 1-2, the method includes: receiving a physical downlink control channel (PDCCH) from a network entity carrying first downlink control information (DCI) which may include an indication having a configuration for triggering or initiating an uplink transmission of a random access procedure to at least one target downlink reference signal; and determining a pseudo-collocation (QCL) assumption for the reception of second downlink control information which schedules a random access response (RAR) for an uplink transmission of a random access procedure.

[0064] According to a 15th exemplary embodiment of a non-temporary computer-readable storage medium, the non-temporary computer-readable storage medium stores instructions, and when the instructions are executed by at least one processor of the device 310 shown in Figure 1-2 (i.e., user devices 102, 202), the device causes the device to: receive a physical downlink control channel (PDCCH) from a network entity, which may include first downlink control information (DCI) having a configuration that triggers or initiates an uplink transmission of a random access procedure to at least one target downlink reference signal; and determine a pseudo-collocation (QCL) assumption for receiving second downlink control information that schedules a random access response (RAR) for an uplink transmission of a random access procedure.

[0065] According to a sixteenth exemplary embodiment of the network entity 320 shown in Figure 1-2 (i.e., network entities 112, 212, 216), the network entity 320 may include means for sending a physical downlink control channel (PDCCH) to a user equipment (UE) that carries first downlink control information (DCI), which may include an indication having a configuration that triggers or initiates at the UE an uplink transmission of a random access procedure to at least one target downlink reference signal transmitted by the device, wherein the indication configures the UE to determine a quasi-collocation (QCL) assumption for the reception of second downlink control information; and means for scheduling the transmission of a random access response (RAR) to the UE based on the second downlink control information in response to the reception of a PRACH preamble contained in a random access procedure transmitted by the UE.

[0066] According to a 17th exemplary embodiment of the method performed by network entity 320 (i.e., network entities 112, 212, 216) shown in Figure 1-2, the method may include: sending a physical downlink control channel (PDCCH) to a user equipment (UE) carrying first downlink control information (DCI) which may include an indication having a configuration that triggers or initiates an uplink transmission of a random access procedure to at least one target downlink reference signal transmitted by the device, wherein the indication configures the UE to determine a quasi-collocation (QCL) assumption for the reception of second downlink control information; and scheduling the transmission of a random access response (RAR) to the UE based on the second downlink control information in response to receiving a PRACH preamble contained in the random access procedure transmitted by the UE.

[0067] According to an 18th exemplary embodiment of a non-temporary computer-readable storage medium, the non-temporary computer-readable storage medium stores instructions, and when the instructions are executed by at least one processor of a network entity, the network entity sends a physical downlink control channel (PDCCH) to the UE, which may include an indication that triggers or initiates at the user equipment (UE) an uplink transmission of a random access procedure to at least one target downlink reference signal transmitted by the device, wherein the indication configures the UE to determine a quasi-collocation (QCL) assumption for the reception of a second downlink control information; and, in response to receiving a PRACH preamble contained in a random access procedure transmitted by the UE, schedules the transmission of a random access response (RAR) to the UE based on the second downlink control information.

[0068] In some exemplary embodiments, the devices 310 and / or 320 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage, etc.), one or more radio access components (e.g., modems, transceivers, etc.), and / or user interfaces. In some exemplary embodiments, the devices 310 and / or 320 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MultiFire, and / or any other radio access technologies.

[0069] As shown in the example in Figure 3, devices 310 and / or 320 may include or be coupled to processors 312 and 322, respectively, for processing information and executing instructions or operations. Processors 312 and 322 may be any type of general-purpose or dedicated processor. In practice, processors 312 and 322 may include, for example, one or more general-purpose computers, dedicated computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on multicore processor architectures. A single processor 312 (and 322) for each of devices 310 and / or 320 is shown in Figure 3, but multiple processors may be utilized according to other exemplary embodiments. For example, it should be understood that in certain exemplary embodiments, the device 310 and / or 320 may include two or more processors that may form a multiprocessor system capable of supporting multiple processes (for example, in this case, processors 312 and 322 may represent multiprocessors). According to certain exemplary embodiments, the multiprocessor system may be tightly coupled or loosely coupled, for example, to form a computer cluster.

[0070] Processors 312 and 322 may perform functions related to the operation of devices 310 and / or 320, respectively, including, as some examples, precoding antenna gain / phase parameters, encoding and decoding individual bits that form a communication message, formatting information, and overall control of devices 310 and / or 320, including the processes shown in Figure 1-2.

[0071] Devices 310 and / or 320 may further include, or be coupled to, memories 314 and / or 324 (internal or external), respectively, for storing information and instructions that may be executed by processors 312 and 322. Memory 314 (and memory 324) may be one or more of any type suitable for the local application environment and may be implemented using any suitable volatile or non-volatile data storage technology, e.g., semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, memory 314 (and memory 324) may include random access memory (DRAM), read-only memory (ROM), static storage such as magnetic or optical disks, hard disk drives (HDDs), or any other type of non-temporary machine or computer-readable media in any combination. Instructions stored in memory 314 and memory 324 may include program instructions or computer program code that, when executed by processors 312 and 322, enable the devices 310 and / or 320 to perform the tasks described herein.

[0072] In certain exemplary embodiments, the apparatus 310 and / or 320 may further include, or be coupled to, a drive or port (internal or external) configured to accept and read an external computer-readable storage medium, such as an optical disc, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store a computer program or software for execution by the processors 312 and 322 and / or the apparatus 310 and / or 320 in order to perform one of the methods shown in Figure 1-2.

[0073] In some exemplary embodiments, the device 310 may also include or be coupled to one or more antennas 315 for receiving downlink signals and transmitting from the device 310 over the uplink. The devices 310 and / or 320 may further include transceivers 316 and 326, respectively, configured to transmit and receive information. The transceivers 316 and 326 may also include a radio interface which may be accommodating multiple radio access technologies, including one or more such as GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, and UWB. The radio interface may include other components, such as filters, converters (e.g., digital-to-analog converters), symbol demappers, signal shaping components, and inverse fast fourier transform (IFFT) modules, for processing symbols such as OFDMA symbols carried over the downlink or uplink.

[0074] For example, transceivers 316 and 326 may be configured, respectively, to modulate information onto a carrier wave for transmission and to demodulate received information for further processing by other elements of the apparatus 310 and / or 320. In other exemplary embodiments, transceivers 316 and 326 may be capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some exemplary embodiments, the apparatus 310 and / or 320 may include input and / or output devices (I / O devices). In certain exemplary embodiments, the apparatus 310 and / or 320 may further include a user interface, such as a graphical user interface or a touchscreen.

[0075] In certain exemplary embodiments, memory 314 and memory 324 store software modules that, when executed by processors 312 and 322, provide functionality. These modules may include, for example, an operating system that provides operating system functionality for devices 310 and / or 320. The memory may also store one or more functional modules, such as applications or programs, to provide further functionality for devices 310 and / or 320. The components of devices 310 and / or 320 may be implemented in hardware or as any suitable combination of hardware and software. According to certain exemplary embodiments, device 310 may optionally be configured to communicate with device 320 by a wireless or wired communication link 330, using any radio access technology such as NR.

[0076] According to certain exemplary embodiments, processors 312 and 322 and memories 314 and 324 may be included in or form part of a processing circuit or control circuit. Furthermore, in some exemplary embodiments, transceivers 313 and 326 may be included in or form part of a transmitting and receiving circuit.

[0077] As used herein, the term “circuitry” can refer to a hardware-only circuit implementation (e.g., analog and / or digital circuitry), a combination of hardware circuitry and software, a combination of analog and / or digital hardware circuitry and software / firmware, any part of a hardware processor with software, including a digital signal processor that works together to cause a device (e.g., device 310 and / or 320) to perform various functions, and / or a hardware circuit and / or processor, or a part thereof, that uses software for operation, but where the software may not be present if the software is not required for operation. In further examples, as used herein, the term “circuitry” can also cover simply a hardware circuit or processor, or multiple processors, or a part of a hardware circuit or processor, and the accompanying software and / or firmware implementation. The term “circuitry” can also cover, for example, a server, a cellular network node or device, or a baseband integrated circuit in other computing or network devices.

[0078] A computer program product may include one or more computer executable components configured to perform several exemplary embodiments when the program is executed. One or more computer executable components may be at least one piece of software code or a portion thereof. Modifications and configurations required to implement the functionality of a particular exemplary embodiment may be implemented as routines, which may be added or updated as software routines. Software routines may be downloaded to the device.

[0079] For example, software or computer program code or a portion thereof may be in source code format, object code format, or some intermediate format, and may be stored on some kind of carrier, distribution medium, or computer-readable medium, which may be any entity or device capable of carrying the program. Such carriers may include, for example, recording media, computer memory, read-only memory, photoelectric and / or electrical carrier signals, telecommunication signals, and software distribution packages. Depending on the processing power required, the computer program may run on a single electronic digital computer, or the computer program may be distributed among many computers. The computer-readable medium or computer-readable storage medium may be a non-temporary medium.

[0080] In other exemplary embodiments, the function may be performed by hardware or circuitry included in the device (e.g., device 310 and / or 320), for example, through the use of application-specific integrated circuits (ASICs), programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), or any other combination of hardware and software. In yet another exemplary embodiment, the function may be implemented by intangible means that can be carried by signals, electromagnetic signals downloaded from the Internet or other networks.

[0081] According to certain exemplary embodiments, the apparatus, such as a node, device, or corresponding component, may be configured as a circuit, computer, or microprocessor, such as a single-chip computer element, or as a chipset including at least memory for providing storage capacity used for arithmetic operations and an arithmetic processor for performing arithmetic operations.

[0082] The features, structures, or characteristics of the exemplary embodiments described throughout this Spec. may be combined in any suitable way in one or more embodiments. For example, the use of the phrases “certain embodiment,” “an example embodiment,” “some embodiments,” or other similar language throughout this Spec. means that certain features, structures, or characteristics described in relation to a particular embodiment may be included in at least one embodiment. Thus, the appearance of the phrases “in certain embidiments,” “in an example embodiment,” “in some embodiments,” “in other embidiments,” or other similar language throughout this Spec. does not necessarily refer to the same group of embodiments, and the features, structures, or characteristics described may be combined in any suitable way in one or more exemplary embodiments. Furthermore, the terms “cell,” “node,” “gNB,” or other similar language may be used interchangeably throughout this Spec.

[0083] When used herein, "at least one of the following: <list of two or more elements>" ) and at least one of )" and similar expressions where a list of two or more elements is joined by "and" or "or" mean at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0084] Those skilled in the art will readily understand that the disclosures discussed above may be implemented by procedures of a different order and / or by hardware elements of a configuration different from the disclosed configuration. Therefore, although the disclosures have been described based on these exemplary embodiments, it will be apparent to those skilled in the art that certain modifications, variations, and alternative configurations may become apparent, while remaining within the spirit and scope of the exemplary embodiments. While the above embodiments refer to 5G NR and LTE technologies, the above embodiments may also apply to any other current or future 3GPP technologies, such as LTE Advanced and / or 4G technologies.

[0085] Partial glossary: CSI Channel State Information CORESET Control Resource Set CSI-RS Channel State Information Reference Signal CSS Common Search Space Set DCI Downlink Control Information DL Downlink DMRS Demodulation Reference Signal PDCCH Physical Downlink Control Channel PRACH (Physical Random Access Channel) QCL (Quasi-Colocation) RACH (Random Access Channel) RAR (Random Access Response) RNTI (Radio Network Temporary Identifier) RA-RNTI: Random Access - Radio Network Temporary Identifier RS Reference Signal SSB Synchronization Signal and PBCH Block TCI Transmission Coordination Indicator TRP (Transmission and Reception Point) UE (User Equipment) UL Uplink USS (User Specific Search Space)

Claims

1. At least one processor, At least one memory for storing instructions and A device comprising, where an instruction is executed by at least one processor, the device provides at least, A physical downlink control channel (PDCCH) carrying first downlink control information (DCI) including an indication having a configuration that triggers or initiates an uplink transmission of a random access procedure to at least one target downlink reference signal is received from a network entity. A device that determines a pseudo-collocation (QCL) assumption for the reception of second downlink control information that schedules a Random Access Response (RAR) for uplink transmission of a Random Access Procedure.

2. The apparatus according to claim 1, wherein the first downlink control information indicates a first value that causes the apparatus to determine a pseudo-collocation assumption for a PDCCH carrying a second DCI that schedules a random access response, such that it is the same as a DCI that triggers or initiates a random access procedure.

3. The apparatus according to claim 1, wherein the first downlink control information indicates a second value that causes the apparatus to determine such a pseudo-collocation assumption for a PDCCH carrying a second DCI for scheduling a random access response is the same as at least one downlink reference signal indicated by a received DCI carried by the PDCCH, which triggers an uplink transmission of a random access procedure.

4. The apparatus according to claim 1, wherein the first downlink control information indicates a second value that causes the apparatus to determine a pseudo-collocation assumption for a PDCCH carrying a second DCI when scheduling a random access response, which is the same as at least one downlink reference signal of a transmit control indicator (TCI) state indicated by a CORESET pool index value different from the index value used for the PDCCH, which includes an indication for triggering an uplink transmission of a random access procedure.

5. The apparatus according to claim 1, wherein the first downlink control information indicates a second value which causes the apparatus to determine a pseudo-collocation assumption for a PDCCH carrying a second DCI that schedules a random access response, which is the same as at least one downlink reference signal for at least one TCI state of an activated TCI state that is different from the CORESET pool index value used to trigger the uplink transmission of the random access procedure.

6. One of the activated TCI states is: The lowest active TCI state identifier in the active TCI state list, The most recently activated TCI state in the active TCI state list, or Lowest active TCI code point in the active TCI status list The apparatus according to any one of claims 1 to 5, comprising any one of the above.

7. The apparatus according to any one of claims 2 to 5, wherein the first downlink control information indicates a first or second value used as a QCL assumption for a PDCCH carrying a second DCI that schedules a random access response, such that the first downlink control information is the same as a first indicated TCI state when the indication indicates a first value and a second indicated TCI state when the indication indicates a second value.

8. The first downlink control information indicates a second value that causes the device to determine a pseudo-collocation assumption for the PDCCH carrying the second DCI that schedules the random access response, based on the CORESET pool index value associated with the PDCCH. The first value indicates that the QCL assumption for monitoring the response is determined to be at the same CORESET pool index value used to trigger the first DCI indicating RACH. The apparatus according to any one of claims 1 to 7, wherein a second value indicates that the QCL assumption for monitoring the response is determined to be in another CORESET pool index value used to trigger a DCI indicating RACH.

9. The apparatus according to any one of claims 1 to 8, wherein the first downlink control information indicates a second value which causes the apparatus to determine a pseudo-collocation assumption for a PDCCH carrying a second DCI that schedules random access responses, based on a configuration of whether or not a common search space type used to monitor the second DCI that schedules random access responses is configured.

10. Furthermore, when the device does not configure a search space type, Minimum CORESET ID, A CORESET ID that conforms to the unified TCI status, or CORESET ID (minimum) unrelated to Unified TCI status The apparatus according to any one of claims 1 to 9, wherein it is determined to monitor a PDCCH carrying scheduling commands for random access responses with respect to at least one of the following.

11. The apparatus according to any one of claims 1 to 10, wherein the uplink transmission of a random access procedure includes the transmission of a PRACH preamble associated with at least one target downlink reference signal.

12. Means for receiving from a network entity a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) including an indication having a configuration for triggering or initiating an uplink transmission of a random access procedure to at least one target downlink reference signal, Means for determining a pseudo-collocation (QCL) assumption for the reception of second downlink control information that schedules a Random Access Response (RAR) for uplink transmission of a random access procedure, and A device equipped with the following features.

13. A method performed by an apparatus, Receiving from a network entity a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) including an indication having a configuration that triggers or initiates uplink transmission of a random access procedure to at least one target downlink reference signal, To determine a pseudo-collocation (QCL) assumption for the reception of second downlink control information that schedules a Random Access Response (RAR) for uplink transmission of a random access procedure, and Methods that include...

14. A non-temporary computer-readable storage medium for storing instructions, wherein when an instruction is executed by at least one processor of the device, the device has at least, Receiving from a network entity a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) including an indication having a configuration that triggers or initiates uplink transmission of a random access procedure to at least one target downlink reference signal, To determine a pseudo-collocation (QCL) assumption for the reception of second downlink control information that schedules a Random Access Response (RAR) for uplink transmission of a random access procedure, and A non-temporary computer-readable storage medium that enables the following.

15. At least one processor, At least one memory for storing instructions and A network entity comprising, where an instruction, when executed by at least one processor, provides to the device at least, A physical downlink control channel (PDCCH) is provided to a user device (UE) that sends out first downlink control information (DCI) including an indication that has a configuration to trigger or initiate an uplink transmission of a random access procedure to at least one target downlink reference signal transmitted by the device, and the UE is configured such that the indication determines a quasi-collocation (QCL) assumption for the reception of second downlink control information. A network entity, upon receiving a PRACH preamble contained in a random access procedure sent by a UE, schedules to send a random access response (RAR) to the UE based on second downlink control information.

16. Means for sending a physical downlink control channel (PDCCH) to a user equipment (UE) that carries first downlink control information (DCI), which includes an indication configured to trigger or initiate an uplink transmission of a random access procedure to at least one target downlink reference signal transmitted by a device, wherein the indication configures the UE to determine a quasi-collocation (QCL) assumption for the reception of second downlink control information; In response to receiving a PRACH preamble contained in a random access procedure transmitted by the UE, means for scheduling the transmission of a random access response (RAR) to the UE based on second downlink control information; A network entity that includes the following features.

17. A method performed by a network entity, Sending a physical downlink control channel (PDCCH) to a user equipment (UE) that carries first downlink control information (DCI), including an indication configured to trigger or initiate an uplink transmission of a random access procedure to at least one target downlink reference signal transmitted by the device, wherein the UE is configured such that the indication determines a quasi-collocation (QCL) assumption for the reception of second downlink control information, In response to receiving the PRACH preamble contained in the random access procedure sent by the UE, the system schedules the transmission of a random access response (RAR) to the UE based on second downlink control information. Methods that include...

18. A non-temporary computer-readable storage medium for storing instructions, wherein when an instruction is executed by at least one processor of a network entity, the network entity receives at least: Sending a physical downlink control channel (PDCCH) to a user equipment (UE) that carries first downlink control information (DCI), including an indication configured to trigger or initiate an uplink transmission of a random access procedure to at least one target downlink reference signal transmitted by the device, wherein the UE is configured such that the indication determines a quasi-collocation (QCL) assumption for the reception of second downlink control information, In response to receiving the PRACH preamble contained in the random access procedure sent by the UE, the system schedules the transmission of a random access response (RAR) to the UE based on second downlink control information. A non-temporary computer-readable storage medium that enables the following.

Images