Method and apparatus for determining quasi co-location (QCL) attributes in triggered cross-TRP random access

Abstract

A method performed by a user equipment comprises performing the steps of: receiving a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) from a network entity, the first DCI comprises an indication having a configuration for triggering or initiating an uplink transmission of a random access procedure for at least one target downlink reference signal; and determining a quasi-co-location (QCL) hypothesis for receiving second downlink control information that schedules a random access response (RAR) for uplink transmissions of the random access procedure.

Description

Cross-references to related applications / registrations / merging via reference

[0001] This application references to and claims priority to U.S. Provisional Application No. 63 / 488,857, filed March 7, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0002] Some embodiments of the present invention relate to work items, methods, terminal devices, and network devices for performing multiple timing advance (TA) maintenance / operations in feMIMO evolution to facilitate the transmission of physical random access channel (PRACH) commands triggered in multiple TRP operations. Background Technology

[0003] This section is intended to provide background or context for the invention as set forth in the claims. The description herein may include concepts that may be pursued, but not necessarily concepts that have been previously conceived or pursued. Therefore, unless otherwise stated herein, what is described in this section is not prior art to the specification and claims of this application, and is not acknowledged as prior art by virtue of its inclusion in this section. Summary of the Invention

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

[0005] According to an exemplary embodiment, an apparatus may include at least one processor and at least one memory. The memory may store instructions that, when executed by the processor, cause the apparatus to: receive from a network entity a physical downlink control channel (PDCCH) carrying first downlink control information (DCI), the first DCI including an indication of an uplink transmission configured to trigger or initiate a random access procedure for at least one target downlink reference signal; and determine a quasi-co-location (QCL) assumption for receiving second downlink control information that schedules a random access response (RAR) for the uplink transmission of the random access procedure.

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

[0007] According to an exemplary embodiment, a method performed by a user equipment may include the following steps: receiving from a network entity a physical downlink control channel (PDCCH) carrying first downlink control information (DCI), the first DCI including an indication of an uplink transmission configured to trigger or initiate a random access procedure for at least one target downlink reference signal; and determining a quasi-co-location (QCL) assumption for receiving second downlink control information that schedules a random access response (RAR) for the uplink transmission of the random access procedure.

[0008] According to an exemplary embodiment, a non-transient computer-readable storage medium stores instructions that, when executed by at least one processor of the apparatus, cause the apparatus to at least: receive from a network entity a physical downlink control channel (PDCCH) carrying first downlink control information (DCI), the first DCI including an indication of an uplink transmission configured to trigger or initiate a random access procedure for at least one target downlink reference signal; and determine a quasi-co-address (QCL) assumption for receiving second downlink control information, the second downlink control information scheduling a random access response (RAR) for the uplink transmission of the random access procedure. The uplink transmission may refer to the transmission of PRACH preamble(s) included in a random access procedure performed by a UE.

[0009] According to an exemplary embodiment, the network may include: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause a network entity to at least: transmit a Physical Downlink Control Channel (PDCCH) carrying first Downlink Control Information (DCI), the first DCI including an indication having an uplink transmission (e.g., a random access preamble) configured for triggering or initiating a random access procedure in the UE for at least one target downlink reference signal transmitted by the device, wherein the indication configures the UE to determine a quasi-co-address (QCL) assumption for receiving second downlink control information; and, in response to receiving a PRACH preamble transmitted by the UE and included in the random access procedure, schedule a transmission of a Random Access Response (RAR) to the UE based on the downlink control information.

[0010] According to an exemplary embodiment, the network entity may include: components for transmitting a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) to a user equipment (UE), the first DCI including an indication having an uplink transmission configured for triggering or initiating a random access procedure in the UE for at least one target downlink reference signal transmitted by the means, wherein the indication configures the UE to determine a quasi-co-address (QCL) assumption for receiving second downlink control information; and components for scheduling a transmission of a random access response (RAR) to the UE based on the second downlink control information in response to receiving a PRACH preamble transmitted by the UE and included in the random access procedure.

[0011] According to an exemplary embodiment, a method performed by a network entity may include the following steps: sending a Physical Downlink Control Channel (PDCCH) carrying first Downlink Control Information (DCI) to a User Equipment (UE), the first DCI including an indication having an uplink transmission configured for triggering or initiating a random access procedure in the UE for at least one target downlink reference signal transmitted by the device, wherein the indication configures the UE to determine a Quasi-Co-location (QCL) assumption for receiving second downlink control information; and scheduling a transmission of a Random Access Response (RAR) to the UE based on the second downlink control information in response to receiving a PRACH preamble transmitted by the UE and included in the random access procedure.

[0012] According to an exemplary embodiment, a non-transient computer-readable storage medium stores instructions that, when executed by at least one processor of a network entity, cause the network entity to at least: transmit to a user equipment (UE) a physical downlink control channel (PDCCH) carrying first downlink control information (DCI), the first DCI including an indication having an uplink transmission configured for triggering or initiating a random access procedure in the UE for at least one target downlink reference signal transmitted by a device, wherein the indication configures the UE to determine a quasi-co-address (QCL) assumption for receiving second downlink control information; and, in response to receiving a PRACH preamble transmitted by the UE and included in the random access procedure, schedule a 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: a target signal / channel that can be received as a PDCCH / PDCCH DMRS. If the UE can assume that the source and target signals have similar characteristics in the form of at least one of the following parameters: Doppler spread, Doppler shift, time delay, time spread, or beamforming, the source signal, such as SSB or CSI-RS or CSI-RS (TRS) for tracking, can be used to provide the UE with (multiple) QCL assumptions for receiving the target signal.

[0014] The source signal can be provided to the UE logic via the TCI state. When the UE receives the source signal, the UE determines the above parameters to determine parameters such as the channel estimation filter, and can then receive the target signal, such as applying the determined channel estimation filter and the PDCCH / PDCCH DMRS of the received beam (typically only in FR2 if the beam domain is applicable).

[0015] Some exemplary embodiments may provide a non-transitory computer-readable storage medium storing instructions that, when executed by at least one processor of the apparatus, cause the apparatus to perform at least one or more methods described herein. Various exemplary embodiments may provide one or more computer programs including instructions that, when executed by the apparatus, cause the apparatus to perform one or more methods described herein. Some exemplary embodiments may provide an apparatus including one or more circuit systems configured to perform one or more methods described herein. Attached Figure Description

[0016] To correctly understand the example embodiments, please refer to the following figures:

[0017] Figure 1 An example system diagram illustrating multi-DCI cross-TRP RACH triggering operation within a cell is shown;

[0018] Figure 2 An example system diagram illustrating multi-DCI cross-TRP RACH triggering operations between cells and within a cell is shown;

[0019] Figure 3 A set of apparatuses according to various exemplary embodiments is shown. Detailed Implementation

[0020] It will be readily understood that components of certain example embodiments, as generally described and illustrated in the accompanying drawings, can be arranged and designed in a variety of different configurations. The same reference numerals may be used in multiple figures to denote the same elements or functions. The following is a detailed description of some exemplary embodiments of systems, methods, apparatuses, and non-transient computer program products for performing multiple timing advance (TA) maintenance / operations to trigger the transmission of Physical Random Access Channel (PRACH) commands in multiple transmit / receive point (TRP) operations.

[0021] RACH for PDCCH commands triggered across TRPs is currently under consideration. Unresolved issues include QCL attributes and / or power control problems associated with PRACH transports. QCL attributes refer to reception assumptions for subsequent messages during a non-contention-based random access process. One problem with QCL attributes is that for a given CORESET with a specific CORESETpoolIndex, a Type 1 common search space (used for monitoring the PDCCH that schedules RARs on the PDSCH) may not be configured. CORESETs under the same CORESETpoolIndex value can sometimes be referred to as (multiple) TRPs. As an example, the CORESETpoolIndex (or TRP) for the target of a PRACH transport and for the target of monitoring responses may not have a search space (Type 1 common) configured for monitoring random access responses. Random access responses are monitored on the PDCCH, and more specifically, on (multiple) CORESETs. The PDCCH provides a second DCI for scheduling RARs (and RARs can be provided by the PDSCH scheduled by the second DCI) for monitoring responses to transports. In some examples, the CORESETpoolIndex can refer to one or more TRPs. In some examples, CORESETpoolIndex is a value associated with a CORESET (Control Resource Set). CORESETs with the same value as CORESETpoolIndex (e.g., 0 or 1) are considered to be grouped or aggregated together. Therefore, CORESETpoolindex can refer to one or more associated CORESETs. Multiple CORESETs are used to monitor random access responses (e.g., DCI for scheduling random access responses). In addition to QCL rules, the transmission power control assumptions for PRACH need to be determined.

[0022] Figure 1 An example system diagram illustrating both inter-cell multi-DCI cross-TRP RACH triggering operations and intra-cell multi-DCI cross-TRP RACH triggering operations is shown. (Reference) Figure 1In 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). This first DCI includes an indication of a configuration for triggering or initiating an uplink transmission (e.g., see step 2) for at least one target downlink reference signal (DL-RS1). In one example, the uplink transmission for random access may use the target downlink reference signal (DL-RS1) (e.g., specified in the first DCI that triggers the PRACH preamble) as a reference for the UL transmission. In the case of intra-cell multi-TRP operation, either target DL-RS1 or DL-RS2 may be used. In both intra-cell and inter-cell operation, both DL-RS1 and DL-RS2 may be used. For example, DL-RS2 can be provided by TRP 112 (represented by CORESETpoolIndex#1) which has the same PCI (intra-cell mTRP) or a different PCI (inter-cell mTRP) as the serving cell.

[0023] UE 102 can determine the quasi-co-location (QCL) assumptions used to receive second downlink control information (DCI) (see [link]). Figure 1 In step 3), the second DCI is used to schedule the Random Access Response (RAR) for uplink transmissions (e.g., UL transmissions via the PRACH preamble of spatial filter / beam 104) for the random access procedure (see step 4). Any examples in this document are not limited to any particular QCL type assumption. As an example, the QCL assumption can be at least a Type A QCL assumption (i.e., no Type D, which could mean that UE 102 may not use beamforming). In one example, the QCL assumption corresponding to the quasi-co-location type of each DL RS is given by the higher-level parameter qcl-Type in the QCL information, and can take one of the following values: - "Type A": {Doppler frequency shift, Doppler spread, average delay, delay spread}; - "Type B": {Doppler frequency shift, Doppler spread}; - "Type C": {Doppler frequency shift, average delay}; - "Type D": {Space Rx parameter}.

[0024] Typically, in some example cases, the RACH of a PDCCH command may have the following QCL assumptions: (a) the first DCI format of the RACH indicating the PDCCH command is typically transmitted using the same DL-RS1 as the target DL-RS for the PRACH transmission as reference (e.g., DL-RS1 → SSB index); (b) UE 102 determines the path loss for UL power control for the RACH transmission based on the DL-RS1 of the DMRS quasi-co-address (QCL) with the PDCCH carrying the PDCCH command (DCI message); (c) the second DCI scheduling the RAR is assumed to be QCL with the DCI that triggered the PDCCH command (see [link to RAR]). Figure 1 (1) and (d) the PDSCH carrying the RAR and the second DCI scheduling the RAR are QCL (see step 1); Figure 1 (Step 3 in the process). If, in response to a PRACH transmission initiated by a PDCCH command, UE 102 attempts to detect a DCI format 1_0 with a cyclic redundancy check (CRC) scrambled by the corresponding random access radio network temporary identifier (RA-RNTI), and this PRACH transmission triggers a non-contention-free random access procedure for a special cell (SpCell) [11, TS38.321], then UE 102 may assume that the PDCCH including the second DCI format 1_0 and the PDCCH command can have the same DM-RS antenna port quasi-co-address attributes.

[0025] Refer to the PDCCH command (see...) Figure 1 Step 1 in the document addresses current issues related to cross-TRP triggering, potentially including QCL relationship / power control after triggering PRACH for DL-RS2 (see Step 2). This is because if the UE assumes a response to a PRACH transmission is monitored based on the target DL RS (target behavior / function) of the PRACH transmission, the target CORESETpoolIndex may not be configured with a CORESET associated with a Type 1-PDCCH CSS (Common Search Space). This could mean that UE 102 may not be able to monitor the response to a PRACH transmission accordingly on the CORESET(s) of the target CORESETpoolIndex. Furthermore, there is uncertainty as to how the UE monitors the response when the command is triggered by the first TRP 112 (scheduled on the CORESET of CORESETpoolIndex#0) and the target is the DL-RS of CORESETpoolIndex#1 (and vice versa). In other words, in these cases, the UE behavior may be unclear regarding conventional rules.

[0026] like Figure 2As shown, for multi-DCI-based multi-TRP operations with two timing advance (TA) enhancements, support is provided by TRP X The sent PDCCH command (i.e., the RACH procedure of the PDCCH command) triggers the orientation TRP for both inter-cell multi-DCI and intra-cell multi-DCI. X or TRP Y The disclosure includes details of the RACH process, taking into account PRACH power control, and QCL determination for PDCCH commands, PDCCH (scheduling) RARs, or PDSCH RARs.

[0027] In the implementation, there can be two CORESETpoolIndices 0 and 1, which can be TRP indices (logical indices). If the PDCCH command comes from a CORESET associated with CORESETpoolIndex 0, the other index can refer to CORESETpoolIndex 1 (and vice versa).

[0028] In any example in this document, the QCL assumption for PDCCH can refer to the QCL assumption for the PDCCH demodulation reference signal (DMRS). For example, when PDCCH and DL-RS are QCL, it can refer to PDCCH DMRS and DL-RS being QCL. In some examples, DL-RS can be included in the TCI state configuration. Therefore, in some examples, the TCI state (or the DL-RS included in the TCI state) can be QCL with either PDCCH or PDSCH (DMRS). In some examples, the DL-RS included in the TCI state configuration can be used as a reference for uplink transmissions (e.g., PUCCH / PUSCH). A TCI state can contain / include one DL-RS with a first QCL type (e.g., type A) and / or two DL-RS with a first QCL type (e.g., type A) and a second DL-RS with a second QCL type (e.g., type D). If the TCI state has two QCL types, the UE can use one QCL type with QCL type D.

[0029] According to this embodiment, the first downlink control information may specify a first value (e.g., =0), which may enable UE 202 to determine that the quasi-co-address assumption of the PDCCH used to carry the second DCI for scheduling random access response is the same as the first DCI that triggers or initiates the random access procedure.

[0030] For example, in Figure 2In step 1, if the downlink control information specifies a first value (e.g., =0), then UE 202 may assume that the QCL of the PDCCH (PDCCH DMRS) used to carry the scheduling random access response of the second DCI is the same as that of the PDCCH (DMRS) used to send the trigger PDCCH command.

[0031] In the example (Option 1), if the first downlink control information specifies a second value (e.g., =1), then UE 202 assumes that the QCL of the PDCCH used to carry the scheduling random access response for the second DCI is the same as the DL RS (or the DL RS associated with the PRACH transmission) specified as the target reference signal (RS) for PRACH transmission.

[0032] In another example (Option 2), if the first downlink control information (DCI) specifies a second value (e.g., =1), then UE 202 may assume that the QCL of the PDCCH used to carry the scheduling random access response of the second DCI is the same as the DLRS of one of the TCI states in the active TCI states that are specified as the target RS for PRACH transmission with a different CORESETpoolIndex value.

[0033] In the implementation, one of the TCI states in the active TCI state list can include any 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.

[0034] In another example (Option 3), the downlink control information may indicate whether the specified first or second TCI state is used as the QCL assumption for the PDCCH (DMRS) used to send the second DCI for scheduling the random access response. In one example, whether the random access response follows (i.e., assumes the response is sent) the specified TCI state (as a QCL reference) may be configured (e.g., via RRC) and / or specified in a field in the DCI that triggers the PDCCH command. In one example, if the random access response is configured to be monitored using the specified TCI state as an assumption for the second DCI used to schedule the random access response, the UE may determine the QCL assumption based on the specified TCI state.

[0035] In another example (Option 4), the downlink control information may indicate whether the random access response is based on the CORESETpoolIndex value that triggered the transmission or on a CORESETpoolIndex that was monitored at a different index than the one that triggered the PDCCH command. The CORESETpoolIndex may include one or more CORESETs.

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

[0037] In another embodiment, if the downlink control information specifies a second value (e.g., =1), and the first triggered DCI is scheduled on a CORESET configured with a CORESET poolIndex value of 0, the UE 202 determines to monitor random access responses on a CORESET with poolIndex#1 (or vice versa). In another example, if any of the (multiple) CORESETs (poolIndex#1 or poolIndex#0, depending on the indication and which CORESET poolIndex#0 value was used to send the first triggered DCI) is not associated with a CSS type 1 (search space for monitoring RAR responses), the UE may determine to monitor random access responses using a C-RNTI (Cell Radio Network Temporary Identifier) ​​(or RA-RNTI) on a UE-specific search space (USS) or type 3-CSS with at least one CORESET ID associated with poolIndex#1 (or poolIndex#0).

[0038] In another example, the UE may use a C-RNTI (or RA-RNTI) on a USS or Type 3-CSS associated with at least one CORESET ID associated with polindex#1 (or poolIndex#0) to determine the monitoring of random access responses. In yet another example, the UE may determine to monitor random access responses using a C-RNTI (or RA-RNTI) on any CSS configured on at least one CORESET ID associated with CORESETpoolIndex#1 (or poolIndex#0). This monitoring may be based on at least one of the following: the lowest CORESET ID, a CORESET ID following the specified uniform TCI state (or the lowest / highest CORESET ID), or a CORESET ID not associated with the uniform TCI state (the lowest / highest).

[0039] In another embodiment, if the information in the first DCI trigger of the PDCCH command specifies a first value, it may indicate that the UE uses the same QCL assumption as the PDCCH (DMRS) used to schedule the first trigger DCI to monitor the random access response. In another example embodiment, if the information in the first DCI triggering the PDCCH command specifies a second value, it may indicate that the UE uses the QCL assumption of the target DL-RS specified by the triggering first DCI to monitor the random access response. In another example embodiment, if the information in the first DCI triggering the PDCCH command specifies a second value, it may indicate that the UE uses the QCL assumption of the CORESET for sending the first trigger DCI with a different CORESETpoolIndex value to monitor the random access response. The QCL assumption may be a specified or activated TCI state associated with a CORESETpoolIndex value that is different from the PDCCH (DMRS) used to schedule the first trigger DCI for t (e.g., =1 or indicating that the UE uses a CORESET with a different CORESETpoolIndex for response monitoring).

[0040] In another embodiment, if the first downlink control information specifies a second value (e.g., =1), and the first triggered DCI is scheduled on a CORESET configured with a CORESETpoolIndex value of 0, and the UE determines to monitor a response on a CORESET with poolIndex#1, and the CORESET (with poolIndex#1) is not associated with CSS type 1 (the search space for monitoring RAR responses), then the UE can determine to monitor the response using C-RNTI (or RA-RNTI) on a USS or type 3-CSS of at least one CORESETID associated with poolIndex#1. This monitoring can be based on at least one of the following: the lowest CORESET ID, the CORESET ID following the specified uniform TCI state (or the lowest / highest CORESET ID), or the CORESET ID not associated with the uniform TCI state (the lowest / highest). The above embodiments can also be considered in reverse with respect to the CORESETpoolIndex# value.

[0041] In one embodiment, the interpretation of the first and second values ​​may depend on which CORESET (configured with a CORESETpoolIndex value) the first DCI, which triggers the random access procedure of the PDCCH command, is scheduled to. Therefore, the interpretation of the information fields in the first DCI (providing one of the first / second / values) may be conditional or dependent on other parameters or assumptions. In one example, if the CORESET transmitting the PDCCH (PDCCH command) carrying the first DCI is configured with CORESETPoolIndex#0, then one of the values ​​in the information fields (e.g., 1) may refer to CORESETPoolindex#1. In another example, if the CORESET is configured with CORESETPoolIndex#1, then one of the values ​​in the information fields (e.g., 1) may refer to CORESETPoolindex#0. Therefore, UE 202 can interpret the values ​​in the first DCI (PDCCH command) based on the association with the CORESET associated with the CORESETpoolIndex. As another example, the first value may indicate that the UE monitors the Random Access Response (RAR) on the same CORESET pool index used to send the first DCI (PDCCH command). The second value may indicate that the UE 202 monitors the Random Access Response on a different / different CORESET pool index used to send the DCI (PDCCH command).

[0042] In one embodiment, the value of the information field and its association with the CORESETpoolIndex can be configurable. As an example, a first value (e.g., 0) is configured to indicate a first value (e.g., 0) for the CORESETpoolIndex. In another instance, a second value (e.g., 1) is configured to indicate a second value (e.g., 1) for the CORESETpoolIndex. In this example, the first value may indicate that the UE monitors random access responses on the CORESET of the CORESETpoolindex associated with that value (e.g., 0). The second value may indicate that the UE 202 monitors random access responses on the CORESET of the CORESETpoolindex associated with the second value (e.g., 1). Therefore, the UE 202 determines random access response monitoring (and selects the CORESETpoolIndex used to determine the hypothesis for random access response monitoring) based on the information field indicating the CORESETpoolIndex value.

[0043] In one embodiment, a field in the first DCI of random access that triggers the PDCCH command can indicate whether the UE is monitoring the RA response on the CSS (e.g., using RA-RNTI or C-RNTI) or on the USS (using C-RNTI or RA-RNTI).

[0044] In another embodiment, if the information indicates a second value (e.g., =1 or it indicates that the UE uses a CORESET of another CORESETpoolIndex for response monitoring), if the SSB (or target DL-RS2) is configured as a QCL source for a TCI state (e.g., an active TCI state) or a PDCCHDMRS based on the indicated TCI state, and if the SSB (or target DL-RS2) is a QCL source for a TCI state, then UE 202 can determine the path loss 204 for PRACH power control based on the SSB (or target DL-RS2) associated with the PRACH preamble. The target DL-RS2 can be either an SSB or a CSI-RS.

[0045] In one embodiment, UE 202 may determine path loss 204 for PRACH power control based on the SSB (or DL-RS2) included in the specified TCI state. In one example, UE 202 may perform power control based on the specified TCI state for the CORESETPoolIndex value. In one example, when a first DCI carrying a PDCCH command indicates monitoring random access responses on a CORESET with a different CORESETPoolIndex value used by the CORESET to transmit the DCI (PDCCH command), the UE may perform power control based on the specified TCI state for the CORESETPoolIndex value (DL-RS2 included in the TCI state).

[0046] In one example, one of the second values / values ​​specified by the first DCI (PDCCH command) can indicate that UE 202 monitors the DCI that schedules a random access response on (multiple) CORESETs in the CORESETpoolIndex, which is different from the CORESETpoolIndex used to send the second DCI to trigger the random access transmission. If the specified TCI state includes two DL-RSs (i.e., DL-RS1, DL-RS2), then UE 202 can use the DL-RS configured with QCL-type D.

[0047] In any embodiment herein, the first DCI, including a first value and a second value, may be provided as a (bit) field in the first DCI message of the random access procedure that triggers the PDCCH command. The presence of this field may be configurable by the network (i.e., via RRC signaling). This information may be referred to as "one of the values" rather than referring to the first value and / or the second value. The first value and the second value may also be interchanged, or vice versa (first value = 1 and second value = 0).

[0048] Figure 3 A set of apparatuses according to various exemplary embodiments is shown.

[0049] According to certain exemplary embodiments, the apparatus 320 may also be configured to perform multiple timing advance (TA) maintenance / operations to facilitate the transmission of physical random access channel (PRACH) commands for physical downlink control channel (PDCCH) triggered in multiple TRP operations.

[0050] Figure 3 The following are examples illustrating the methods for performing various exemplary embodiments. Figures 1 to 2 A set of devices 310 and 320 are shown, illustrating the steps and functions. In various exemplary embodiments, device 310 may be an element in or associated with such a communication network, such as a UE, RedCap UE, SL UE, mobile device (ME), mobile station, mobile device, fixed device, IoT device, or other user equipment. For example, UE 102 or 202 may be an example of device 310 according to the various exemplary embodiments discussed above. It should be noted that those skilled in the art will understand that device 310 may include... Figure 3 Components or features not shown in FIG. 6. Furthermore, device 320 may be a network, a network entity, an element of a core network, or an element in or associated with such a communication network, such as a base station, NE, or gNB. For example, networks and gNBs 112, 212, and 216 may be examples of device 320 according to the various exemplary embodiments discussed above. It should be noted that those skilled in the art will understand that device 320 may include components or features not shown in FIG. 6.

[0051] According to such Figures 1 to 2 A first exemplary embodiment of the device 310 (i.e., user equipment 102, 202) shown. The device 310 (i.e., user equipment 102, 202) may include, for example... Figure 3 The diagram shows at least one processor 312 and at least one memory 314. The memory 314 may store instructions that, when executed by the processor 312, cause the device 310 to: [the following text appears to be incomplete and requires further context: "from network entity 320 (i.e...."]) Figures 1 to 2The network entities 112 or 212 and 216 shown receive a physical downlink control channel (PDCCH) carrying first downlink control information (DCI), the first DCI including an indication of an uplink transmission configuration for triggering or initiating a random access procedure for at least one target downlink reference signal; and determining a quasi-co-location (QCL) assumption for receiving second downlink control information, the second downlink control information scheduling a random access response (RAR) for the uplink transmission of the random access procedure.

[0052] According to such Figures 1 to 2 In a second exemplary embodiment of the apparatus 310 (i.e., user equipment 102, 202) shown, downlink control information indicates a first value that causes the apparatus to determine that the quasi-co-address assumption of the PDCCH used to carry the second DCI for scheduling random access response is the same as the first DCI that triggers or initiates the random access procedure.

[0053] According to such Figures 1 to 2 In a third exemplary embodiment of the apparatus 310 (i.e., user equipment 102, 202) shown, the first downlink control information specifies a second value that causes the apparatus to determine that the quasi-co-address assumption of the PDCCH used to carry the second DCI for scheduling random access response is the same as at least one downlink reference signal specified by the first DCI carried by the received PDCCH, the at least one downlink reference signal serving as a target reference signal for uplink transmission to trigger the random access procedure.

[0054] According to such Figures 1 to 2 In a fourth exemplary embodiment of the apparatus 310 (i.e., user equipment 102, 202) shown, the first downlink control information indicates a second value that causes the apparatus to: determine, when scheduling a random access response, that the quasi-co-location (QCL) assumption of the PDCCH carrying the second DCI is the same as at least one downlink reference signal indicating the state of the Transmission Control Indicator (TCI) value specified by the CORESETpoolIndex value, which is different from the index value of the PDCCH used to schedule an indication including an uplink transmission to trigger a random access procedure.

[0055] According to such Figures 1 to 2In a fifth exemplary embodiment of the apparatus 310 (i.e., user equipment 102, 202), the first downlink control information specifies a second value that causes the apparatus to: determine that the quasi-co-address assumption of the PDCCH for carrying the second DCI for scheduling a random access response is the same as at least one downlink reference signal of at least one active TCI state with a CORESETpoolIndex value that is different from the CORESETPoolIndex value used to trigger the uplink transmission for the random access procedure.

[0056] According to such Figures 1 to 2 In a sixth exemplary embodiment of the device 310 (i.e., user equipment 102, 202) shown, one of the active TCI states includes any 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.

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

[0058] According to such Figures 1 to 2 In an eighth exemplary embodiment of the apparatus 310 (i.e., user equipment 102, 202), downlink control information specifies a second value that causes the apparatus to: determine that the quasi-co-location assumption of the PDCCH for carrying the second DCI for scheduling random access response will be based on the CORESETpoolIndex value associated with the PDCCH: wherein the first value indicates that the QCL assumption for monitoring the response is determined based on the same CORESETpoolIndex value used to trigger the first DCI for indicating the RACH, and wherein the second value indicates that the QCL assumption for monitoring the response is determined based on another CORESETpoolIndex value used to trigger the first DCI for indicating the RACH.

[0059] According to such Figures 1 to 2In the ninth exemplary embodiment of 310 (i.e., user equipment 102, 202) shown, the first downlink control information indicates a second value that causes the apparatus to: determine the quasi-co-location assumption of the PDCCH used to carry the scheduling random access response of the second DCI to be based on whether the common search space type of the second DCI used to monitor the scheduling random access response is configured.

[0060] According to such Figures 1 to 2 A tenth exemplary embodiment of the apparatus 310 (i.e., user equipment 102, 202) shown is configured to: when the search space type is not configured, determine that the PDCCH carrying the scheduling command for random access response is monitored on at least one of the following: the lowest CORESET ID, the CORESET ID that follows the unified TCI state, or the lowest CORESET ID that is not associated with the unified TCI state.

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

[0062] According to such Figures 1 to 2 A twelfth exemplary embodiment of network entity 320 (i.e., network entities 112, 212, 216) is shown. Network entity 320 may include: at least one processor 322; and at least one memory 324 storing instructions that, when executed by the at least one processor, cause the network entity to at least: transmit to a user equipment (UE) a physical downlink control channel (PDCCH) carrying first downlink control information (DCI), the first DCI including an indication having an uplink transmission configured for triggering or initiating a random access procedure in the UE for at least one target downlink reference signal transmitted by the device, wherein the indication configures the UE to determine a quasi-co-address (QCL) assumption for the received second downlink control information; and, in response to receiving a PRACH preamble transmitted by the UE and included in the random access procedure, schedule the transmission of a random access response (RAR) to the UE based on the second downlink control information.

[0063] According to such Figures 1 to 2A thirteenth exemplary embodiment of the apparatus 310 (i.e., user equipment 102, 202) shown. The apparatus includes: components for receiving from a network entity a physical downlink control channel (PDCCH) carrying first downlink control information (DCI), the first DCI including an indication of an uplink transmission configuration for triggering or initiating a random access procedure for at least one target downlink reference signal; and components for determining a quasi-co-location (QCL) assumption for receiving second downlink control information that schedules a random access response (RAR) for the uplink transmission of the random access procedure.

[0064] According to such Figures 1 to 2 A fourteenth exemplary embodiment of the method performed by apparatus 310 (i.e., user equipment 102, 202) is shown, the method comprising: receiving from a network entity a physical downlink control channel (PDCCH) carrying first downlink control information (DCI), the first DCI including an indication having an uplink transmission configured to trigger or initiate a random access procedure for at least one target downlink reference signal; and determining a quasi-co-location (QCL) assumption for receiving second downlink control information, the second downlink control information scheduling a random access response (RAR) for the uplink transmission of the random access procedure.

[0065] According to a fifteenth exemplary embodiment of a non-transient computer-readable storage medium for storing instructions, the instructions are stored in a manner such as... Figures 1 to 2 When at least one processor of the illustrated apparatus 310 (i.e., user equipment 102, 202) is executed, the apparatus at least performs: receiving from a network entity a physical downlink control channel (PDCCH) carrying first downlink control information (DCI), the first DCI may include an indication having an uplink transmission configuration for triggering or initiating a random access procedure for at least one target downlink reference signal; and determining a quasi-co-location (QCL) assumption for receiving second downlink control information, the second downlink control information scheduling a random access response (RAR) for uplink transmissions for the random access procedure.

[0066] According to such Figures 1 to 2A sixteenth exemplary embodiment of the network entity 320 (i.e., network entities 112, 212, 216) shown. Network entity 320 may include: components for transmitting a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) to a user equipment (UE), the first DCI including an indication having a configuration for triggering or initiating an uplink transmission in the UE for at least one target downlink reference signal transmitted by the means, wherein the indication configures the UE to determine a quasi-co-address (QCL) assumption for receiving second downlink control information; and components for scheduling a transmission of a random access response (RAR) to the UE based on the second downlink control information in response to receiving a PRACH preamble transmitted by the UE and included in the random access process.

[0067] According to such Figures 1 to 2 The seventeenth exemplary embodiment of the method performed by network entity 320 (i.e., network entities 112, 212, 216) is shown. The method may include: sending a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) to a user equipment (UE), the first DCI including an indication having a configuration for triggering or initiating a random access procedure in the UE for at least one target downlink reference signal transmitted by the means, wherein the indication configures the UE to determine a quasi-co-location (QCL) assumption for receiving 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 transmitted by the UE and included in the random access procedure.

[0068] According to an eighteenth exemplary embodiment of a non-transient computer-readable storage medium storing instructions, when executed by at least one processor of a network entity, the instructions cause the network entity to at least: transmit a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) to a user equipment (UE), the first DCI including an indication having an uplink transmission configured for triggering or initiating a random access procedure in the UE for at least one target downlink reference signal transmitted by a device, wherein the indication configures the UE to determine a quasi-co-address (QCL) assumption for receiving second downlink control information; and, in response to receiving a PRACH preamble transmitted by the UE and included in the random access procedure, schedule the transmission of a random access response (RAR) to the UE based on the second downlink control information.

[0069] In some example embodiments, apparatus 310 and / or 320 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage device, etc.), one or more radio access components (e.g., modem, transceiver, etc.), and / or a user interface. In some example embodiments, apparatus 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, MulteFire, and / or any other radio access technology.

[0070] like Figure 3 As illustrated in the example, devices 310 and / or 320 may respectively include or be coupled to processors 312 and 322 for processing information and executing instructions or operations. Processors 312 and 322 can be any type of general-purpose or special-purpose processor. In practice, as an example, processors 312 and 322 may include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although Figure 3 The diagram illustrates individual processors 312 (and 322) for each of devices 310 and / or 320, but multiple processors may be used according to other example embodiments. For example, it should be understood that in some example embodiments, devices 310 and / or 320 may include two or more processors that can form a multiprocessor system (e.g., in this case, processors 312 and 322 may represent multiple processors) that can support multiprocessing. According to some example embodiments, the multiprocessor system may be tightly coupled or loosely coupled, for example, forming a computer cluster.

[0071] Processors 312 and 322 can respectively perform functions associated with the operation of devices 310 and / or 320, including, as some examples, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of devices 310 and / or 320, including... Figures 1 to 2 The process is shown in the figure.

[0072] Devices 310 and / or 320 may also include or be coupled to memories 314 and / or 324 (internal or external), which may be coupled to processors 312 and 322, respectively, for storing information and instructions executable by processors 312 and 322. Memory 314 (and memory 324) may be one or more memories and may be of any type suitable for the local application environment, and may be implemented using any suitable volatile or non-volatile data storage technology, such as 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 (RAM), read-only memory (ROM), static storage such as a disk or optical disk, a hard disk drive (HDD), or any other combination of non-transient machine or computer-readable media. The instructions stored in memory 314 and memory 324 may include program instructions or computer program code, which, when executed by processors 312 and 322, enable device 310 and / or 320 to perform the tasks described herein.

[0073] In some example embodiments, devices 310 and / or 320 may further include or be coupled to an (internal or external) drive or port configured to accept and read external computer-readable storage media, such as an optical disc, USB drive, flash drive, or any other storage media. For example, the external computer-readable storage medium may store computer programs or software for execution by processors 312 and 322 and / or devices 310 and / or 320 to perform... Figures 1 to 2 Any method shown in the document.

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

[0075] For example, transceivers 316 and 326 may be configured to modulate information onto a carrier waveform for transmission and demodulate received information for further processing by other elements of device 310 and / or 320. In other example embodiments, transceivers 316 and 326 may be able to directly transmit and receive signals or data. Additionally or alternatively, in some example embodiments, device 310 and / or 320 may include input and / or output devices (I / O devices). In some example embodiments, device 310 and / or 320 may also include a user interface, such as a graphical user interface or a touchscreen.

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

[0077] According to some example embodiments, processors 312 and 322, and memories 314 and 324 may be included in, or may form part of, a processing circuit system or a control circuit system. Furthermore, in some example embodiments, transceivers 313 and 326 may be included in, or may form part of, a transceiver circuit system.

[0078] As used herein, the term "circuit system" can refer to a hardware circuit system implementation only (e.g., analog and / or digital circuit systems), a combination of hardware circuitry and software, a combination of analog and / or digital hardware circuitry with software / firmware, any portion (including digital signal processors) of a hardware processor(s) that works with software to enable a device (e.g., device 310 and / or 320) to perform various functions, and / or a hardware circuit(s) and / or a processor(s) or a portion thereof that operates using software, but the software may be absent when operation is not required. As another example, as used herein, the term "circuit system" can also encompass an implementation of hardware circuitry or a processor(s) or multiple processor(s) or a portion thereof, along with accompanying software and / or firmware. The term "circuit system" can also encompass, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or networking device.

[0079] A computer program product may include one or more computer-executable components that, when the program runs, are configured to perform some example embodiments. The 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 certain example embodiments may be executed as a routine(s), which may be implemented as added or updated software(s). The software(s) may be downloaded to the device.

[0080] As an example, software or computer program code, or portions thereof, may be in the form of source code, object code, or some intermediate form, and may be stored in some carrier, distribution medium, or computer-readable medium, which may be any entity or device capable of carrying the program. Such a carrier 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 required processing power, the computer program may be executed in a single electronic digital computer, or it may be distributed among multiple computers. The computer-readable medium or computer-readable storage medium may be a non-transient medium.

[0081] In other example embodiments, this function may be performed by hardware or circuitry included in the device (e.g., device 310 and / or 320), for example, by using an application-specific integrated circuit (ASIC), a programmable gate array (PGA), a field-programmable gate array (FPGA), or any other combination of hardware and software. In another example embodiment, this function may be implemented as a signal, a non-tangible component that may be carried by an electromagnetic signal downloaded from the Internet or other networks.

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

[0083] The features, structures, or characteristics of the exemplary embodiments described in this specification can be combined in any suitable manner in one or more exemplary embodiments. For example, the use of phrases such as "certain embodiments," "exemplary embodiments," "some embodiments," or other similar language in this specification means that a particular feature, structure, or characteristic described in connection with an embodiment can be included in at least one embodiment. Therefore, the phrases "in some embodiments," "exemplary embodiments," "in some embodiments," "in other embodiments," or other similar language appearing in this specification do not necessarily refer to the same set of embodiments, and the described features, structures, or characteristics can be combined in any suitable manner in one or more exemplary embodiments. Furthermore, the terms "cell," "node," "gNB," or other similar language are used interchangeably in this specification.

[0084] As used herein, “at least one of the following: ” and “at least one of ” and similar wording (where the list of two or more elements is connected by “and” or “or”) means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0085] It will be readily understood by those skilled in the art that the disclosures discussed above can be practiced using processes in a different order and / or configurations different from those of the disclosed hardware components. Therefore, although this disclosure has been described based on these exemplary embodiments, certain modifications, variations, and alternative constructions will be apparent to those skilled in the art, while remaining within the spirit and scope of the exemplary embodiments. While the above embodiments relate to 5G NR and LTE technologies, they can also be applied to any other current or future 3GPP technologies, such as Advanced LTE and / or fourth-generation (4G) technologies.

[0086] Partial Glossary CSI Channel State Information CORESET Control Resource Set CSI-RS Channel State Information Reference Signal CSS Public Search Space Collection DCI Downlink Control Information DL downlink DMRS demodulation reference signal PDCCH (Physical Downlink Control Channel) PRACH (Physical Random Access Channel) QCL Quasi-co-located 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 Transmit and Receive Points UE User Equipment UL uplink USS User-Specific Search Space

Claims

1. An apparatus comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the device to at least: Receive from a network entity a physical downlink control channel (PDCCH) carrying first downlink control information (DCI), the first DCI including an indication of an uplink transmission configuration for triggering or initiating a random access procedure for at least one target downlink reference signal. as well as A quasi-co-address (QCL) assumption is determined for receiving second downlink control information, which schedules a random access response (RAR) for the uplink transmission of the random access procedure.

2. The apparatus of claim 1, wherein the first downlink control information specifies a first value, the first value causing the apparatus to: determine that the quasi-co-location assumption of the PDCCH used to carry the second DCI for scheduling the random access response is the same as the DCI that triggers or initiates the random access procedure.

3. The apparatus of claim 1, wherein the first downlink control information specifies a second value, the second value causing the apparatus to: determine that the quasi-co-location assumption of the PDCCH carrying the second DCI for scheduling the random access response is the same as the at least one downlink reference signal indicated by the DCI carried by the PDCCH, the at least one downlink reference signal serving as the target reference signal for triggering the uplink transmission of the random access procedure.

4. The apparatus of claim 1, wherein the first downlink control information specifies a second value, the second value causing the apparatus to: determine, when scheduling the random access response, that the quasi-co-address assumption of the PDCCH carrying the second DCI is the same as the at least one downlink reference signal of the Transmission Control Indicator (TCI) state indicated by the CORESETpoolIndex value, the CORESETpoolIndex value being different from the index value of the PDCCH used to include the indication for triggering the uplink transmission of the random access procedure.

5. The apparatus of claim 1, wherein the first downlink control information specifies a second value, the second value causing the apparatus to: determine that the quasi-co-location assumption of the PDCCH for carrying the second DCI for scheduling the random access response is the same as the at least one downlink reference signal of at least one active TCI state of the CORESETpoolIndex value, the CORESETpoolIndex value being different from the CORESETPoolIndex value used to trigger the uplink transmission of the random access procedure.

6. The apparatus according to claims 1 to 5, wherein one of the activated TCI states includes any one of the following: The lowest active TCI status identifier in the active TCI status list, The most recently activated TCI state in the list of active TCI states, or The lowest active TCI code point in the active TCI status list.

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

8. The apparatus of claims 1 to 7, wherein the first downlink control information indicates the second value, the second value causing the apparatus to: determine that the quasi-co-location assumption of the PDCCH for carrying the second DCI for scheduling the random access response will be based on the CORESETpoolIndex value associated with the PDCCH: The first value indicates that the QCL hypothesis used for monitoring the response is determined to be based on the same CORESETpoolIndex value used to trigger the first DCI indicating the RACH. The second value indicates that the QCL assumption used for monitoring the response is determined to be based on another CORESETpoolIndex value of the DCI used to trigger the RACH.

9. The apparatus of claims 1 to 8, wherein the first downlink control information indicates the second value, the second value causing the apparatus to: determine that the quasi-co-location assumption of the PDCCH for carrying the second DCI for scheduling the random access response will be based on a configuration used to monitor whether the common search space type of the second DCI for scheduling the random access response is configured.

10. The apparatus of claims 1 to 9, wherein the apparatus is further configured to: when the search space type is not configured, determine that the PDCCH carrying a scheduling command for the random access response is monitored on at least one of the following: Minimum CORESET ID, Follows the CORESET ID of the unified TCI status, or CORESET ID (lowest) that is not related to the unified TCI status.

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

12. An apparatus comprising: Components for receiving from a network entity a physical downlink control channel (PDCCH) carrying first downlink control information (DCI), the first DCI including an indication of an uplink transmission configuration for triggering or initiating a random access procedure for at least one target downlink reference signal. as well as Components for determining the quasi-co-location (QCL) assumption for receiving second downlink control information, which schedules a random access response (RAR) for the uplink transmission of the random access procedure.

13. A method performed by an apparatus, comprising: Receive from a network entity a physical downlink control channel (PDCCH) carrying first downlink control information (DCI), the first DCI including an indication of an uplink transmission configuration for triggering or initiating a random access procedure for at least one target downlink reference signal. as well as A quasi-co-address (QCL) assumption is determined for receiving second downlink control information, which schedules a random access response (RAR) for the uplink transmission of the random access procedure.

14. A non-transient computer-readable storage medium storing instructions, which, when executed by at least one processor of a device, cause the device to perform at least: Receive from a network entity a Physical Downlink Control Channel (PDCCH) carrying first Downlink Control Information (DCI), the first DCI including an indication of an uplink transmission configuration for triggering or initiating a random access procedure for at least one target downlink reference signal; and A quasi-co-address (QCL) assumption is determined for receiving second downlink control information, which schedules a random access response (RAR) for the uplink transmission of the random access procedure.

15. A network entity, comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the device to at least: A physical downlink control channel (PDCCH) carrying first downlink control information (DCI) is sent to a user equipment (UE), the first DCI including an indication having an uplink transmission configuration for triggering or initiating a random access procedure in the UE for at least one target downlink reference signal transmitted by the device, wherein the indication configures the UE to determine a quasi-co-address (QCL) assumption for receiving second downlink control information. as well as In response to receiving a PRACH preamble sent by the UE and included in the random access procedure, the transmission of a random access response (RAR) is scheduled to the UE based on the second downlink control information.

16. A network entity, comprising: Components for transmitting a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) to a user equipment (UE), the first DCI including an indication having an uplink transmission configuration for triggering or initiating a random access procedure in the UE for at least one target downlink reference signal transmitted by the means, wherein the indication configures the UE to determine a quasi-co-location (QCL) assumption for receiving second downlink control information. as well as A component 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 sent by the UE and included in the random access procedure.

17. A method performed by a network entity, comprising: A physical downlink control channel (PDCCH) carrying first downlink control information (DCI) is sent to a user equipment (UE), the first DCI including an indication having an uplink transmission configuration for triggering or initiating a random access procedure in the UE for at least one target downlink reference signal transmitted by the device, wherein the indication configures the UE to determine a quasi-co-address (QCL) assumption for receiving second downlink control information. as well as In response to receiving a PRACH preamble sent by the UE and included in the random access procedure, the transmission of a random access response (RAR) is scheduled to the UE based on the second downlink control information.

18. A non-transient computer-readable storage medium storing instructions that, when executed by at least one processor of a network entity, cause the network entity to perform at least the following: A physical downlink control channel (PDCCH) carrying first downlink control information (DCI) is transmitted to a user equipment (UE). The first DCI includes an indication having a configuration for triggering or initiating a random access procedure in the UE for at least one target downlink reference signal transmitted by the device, wherein the indication configures the UE to determine a quasi-co-location (QCL) assumption for receiving second downlink control information; and In response to receiving a PRACH preamble sent by the UE and included in the random access procedure, the transmission of a random access response (RAR) is scheduled to the UE based on the second downlink control information.

Images