METHOD AND DEVICES FOR DETERMINING QUASI-COLOCALIZATION (QCL) PROPERTIES IN TRIGGERED CROSS-TRIGGERED RANDOM ACCESS

Abstract

A method performed by a user equipment, including performing the steps of: receiving, from a network entity, a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) that includes an indication with configurations to trigger or initiate an uplink transmission of a random access procedure towards at least one target downlink reference signal; and determining a quasi co-location (QCL) assumption for reception of second downlink control information that schedules a random access response (RAR) for the uplink transmission of the random access procedure.

Description

1 / 32 METHOD AND DEVICES FOR DETERMINING QUASI-COLOCALIZATION (QCL) PROPERTIES IN TRIGGERED CROSS-TRIGGERED RANDOM ACCESS CROSS-REFERENCE TO RELATED ORDERS / INCORPORATION FOR REFERENCE PURPOSES

[0001] This application refers to and claims priority for U.S. Provisional Application (63 / 488,857), filed March 7, 2023. The contents of which are incorporated in their entirety. TECHNICAL FIELD:

[0002] Certain embodiments of the invention relate to the feMIMO evolution work item, a method, a terminal device and a network device for performing multiple timing advance (TA) maintenance / operation to facilitate ordered triggered transmission of Physical Random Access Channel (PRACH) of Physical Downlink Control Channel (PDCCH) in multi-TRP operations. BACKGROUND:

[0003] This section is intended to provide background or context for the invention, which is cited in the claims. The description in this document may include concepts that may be pursued, but are not necessarily those that were previously conceived or pursued. Therefore, unless otherwise indicated in this document, 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:

[0004] The invention relates to the feMIMO evolution workpiece in RANI. More specifically, it relates to multi-TA maintenance / operation.

[0005] According to an exemplary embodiment, a device may include at least one processor and at least one memory. The memory may store instructions that, when executed by the processor, perform the Petition 870250079646, dated 05 / 09 / 2025, p. 53 / 183 2 / 32 device receives, from a network entity, a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) that includes an indication with settings to trigger or initiate an uplink transmission of a random access procedure toward at least one target downlink reference signal; and determines a near colocation assumption (QCL) 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 means for receiving, from a network entity, a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) that includes an indication with settings to trigger or initiate an uplink transmission of a random access procedure toward at least one target downlink reference signal; and means for determining a near colocation assumption (QCL) 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 is performed by a user equipment that may include the steps of: receiving, from a network entity, a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) that includes an indication with settings to trigger or initiate an uplink transmission of a random access procedure toward at least one target downlink reference signal; and determining a quasi-colocation assumption (QCL) for receiving second downlink control information that schedules a random access response (RAR) for the uplink transmission of the random access procedure. Petition 870250079646, dated 05 / 09 / 2025, page 54 / 183 3 / 32

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

[0009] According to an exemplary embodiment, a network may include: at least one processor; and at least one memory that stores instructions that, when executed by at least one processor, cause the network entity to at least: send, to a user equipment (UE), a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) that includes an indication with settings to trigger or initiate on the UE, an uplink transmission of a random access procedure (e.g., a random access preamble) towards at least one target downlink reference signal transmitted by the device, wherein the indication configures the UE to determine a near colocation assumption (QCL) for receiving second downlink control information;and schedule the transmission of a Random Access Response (RAR) to the UE, based on downlink control information, in response to receiving PRACH preambles; Petition 870250079646, dated 05 / 09 / 2025, page 55 / 183 4 / 32 included in the random access procedure transmitted by the EU.

[0010] According to an exemplary embodiment, the network entity may include means for sending to a user equipment (UE) a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) which includes an indication with settings to trigger or initiate on the UE, an uplink transmission of a random access procedure toward at least one target downlink reference signal transmitted by the device, wherein the indication configures the UE to determine a near colocation assumption (QCL) for receiving 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 PRACH preambles comprised in the random access procedure transmitted by the UE.

[0011] According to an exemplary embodiment, a method is performed by a network entity that may include the steps of: sending, to a user equipment (UE), a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) which includes an indication with settings to trigger or initiate on the UE, an uplink transmission of a random access procedure towards at least one target downlink reference signal transmitted by the device, wherein the indication configures the UE to determine a near colocation assumption (QCL) for receiving second downlink control information; and scheduling transmission, of a random access response (RAR) to the UE, based on the second downlink control information, in response to receiving PRACH preambles comprised in the random access procedure transmitted by the UE.

[0012] According to an exemplary modality, a means of Petition 870250079646, dated 05 / 09 / 2025, page 56 / 183 5 / 32 non-transient computer-readable storage that stores an instruction that, when executed by at least one processor of a network entity, causes the network entity to at least: send, to a user device (UE), a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) that includes an indication with settings to trigger or initiate on the UE, an uplink transmission of a random access procedure toward at least one target downlink reference signal transmitted by the device, wherein the indication configures the UE to determine a near-colocation assumption (QCL) for receiving second downlink control information;and schedule transmission of a Random Access Response (RAR) to the UE, based on the second downlink control information, in response to receiving PRACH preambles included in the random access procedure transmitted by the UE.

[0013]

[13] Some examples of QCL assumptions can be described as follows: A target signal / channel can be received as DMRS from PDCCH / PDCCH. A source signal such as an S SB or CSI-RS or CSI-RS for tracking (TRS) can be used to provide UE QCL assumption(s) for receiving the target signal if the UE can assume that the source and target signals have similar characteristics in at least one of the following parameters: Doppler spread, Doppler shift, time delay, time spread, or beam.

[0014] The source signal can provide UE logic via TCI state. When the UE receives the source signal, the UE determines the above parameters to determine how channel estimation filters and then can receive a target signal such as PDCCH / PDCCH DMRS that applies the determined channel estimation filters and the received beam (if beam domain is applicable, typically only in FR2). Petition 870250079646, dated 05 / 09 / 2025, page 57 / 183 6 / 32

[0015] Certain exemplary embodiments may provide a non-transient, computer-readable storage medium that stores instructions which, when executed by at least one device processor, can cause the device to perform at least one or more of the methods in this document. Several exemplary embodiments may provide one or more computer programs that include instructions which, when executed by a device, can cause the device to perform one or more of the methods in this document. Some exemplary embodiments may provide a device that includes one or more sets of circuits configured to perform one or more of the methods in this document. BRIEF DESCRIPTION OF THE DRAWINGS:

[0016] For a proper understanding of the exemplary embodiments, reference should be made to the accompanying drawings, as follows:

[0017] FIG. 1 illustrates an example of a system diagram that illustrates an intracell multi-DCI cross-TRP RACH firing operation;

[0018] FIG. 2 illustrates an example of a system diagram that illustrates multi-DCI cross-TRP RACH firing operation both inter-cell and intra-cell;

[0019] FIG. 3 illustrates a set of devices, according to various exemplary modalities. DETAILED DESCRIPTION:

[0020] It will be readily understood that the components of certain exemplary embodiments, as described and illustrated generally in the figures in this document, may be arranged and designed in a wide variety of different configurations. 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 some exemplary embodiments of non-transient computer program systems, methods, apparatus, and products for performing multiple timing advance (TA) maintenance / operation to facilitate triggered transmission of Petition 870250079646, dated 05 / 09 / 2025, page 58 / 183 7 / 32 Random Access Physical Channel (PRACH) ordered from Downlink Control Physical Channel (PDCCH) in multi-point transmit / receive (TRP) operations.

[0021] Currently, ordered PDCCH-triggered cross-TRP RACH is being considered. Open questions are the QCL properties and / or power control issues associated with PRACH transmission. QCL properties refer to the reception assumption for subsequent messages in a contention-free random access procedure. One of the problems with QCL properties is that the Type I Common Search Space (which is used to monitor PDCCH scheduling RAR in PDSCH) may not be configured for the CORESETs of a specific CORESETpoolIndex. CORESETs under the same CORESETpoolIndex value may sometimes be referred to as TRP(s)). As an example, the CORESETpoolIndex (or TRP) that is the target for PRACH transmission and the target for monitoring the response may not have the search space (type 1 common) configured to monitor the random access response.Random access response is monitored in PDCCH, more specifically in a CORESET(s). The PDCCH provides the second DCI that schedules the RAR (and the RAR may be provided by the PDSCH scheduled by the second DCI) to monitor the response for transmission. In some instances, the CORESETpoolIndex may be referred to as one or more TRPs. In some instances, the CORESETpoolIndex is a value that is associated with a CORESET (control resource set). CORESETs that have the same CORESETpoolIndex value (e.g., 0 or 1) are considered grouped or clustered together. Thus, the CORESETpoolIndex may refer to one or more associated CORESETs. The CORESET(s) is / are used to monitor random access response (e.g., DCI that schedules the random access response). In addition to the QCL rules, the transmission power control assumption for PRACH needs to be determined.

[0022] FIG. 1 illustrates an example of a system diagram that illustrates Petition 870250079646, dated 05 / 09 / 2025, p. 59 / 183 8 / 32 Multi-DCI Cross TRP RACH triggering operation, both inter-cell and intra-cell. Referring to FIG. 1, in step 1, a user equipment (UE) 102 can receive, from a network entity (e.g., TRP 112), a physical downlink control channel (PDCCH) (e.g., space filter / beam 114), which carries first downlink control information (DCI) (see step 1) that includes an indication with settings to trigger or initiate an uplink transmission (e.g., see step 2) of a random access procedure towards at least one target downlink reference signal (DLRS1). In one example, the uplink transmission of a random access can use the target downlink reference signal (DL-RS1) (e.g., indicated in the first DCI that triggers the uplink transmission of a PRACH preamble) as a reference for the UL transmission.In a case of multiple intra-cell TRP operation, either target DL-RS1 or DL-RS2 can be used. In a case of both intra- and inter-cell operations, either DL-RS1 or DL-RS2 can be used. As an example, DL-RS2 can be provided by TRP 112 (referred to by CORESETpoolIndex No. 1) from the same (intra-cell mTRP) or a different PCI (inter-cell mTRP) than that of the service cell.

[0023] The UE 102 can determine a quasi-colocation assumption (QCL) for receiving second downlink control information (DCI) (see step 3 in FIG. 1), which is used to schedule a random access response (RAR) (see step 4) for uplink transmission of the random access procedure (e.g., PRACH preamble UL transmission via 104 spatial filter / beam). Any of the examples in this document are not limited to any specific QCL type assumption. As an example, the QCL assumption may be at least a QCLA type assumption (i.e., without typeD, which may mean that the UE 102 may not use beamforming).

[0024] In one example, the assumptions of QCL, that the types of almost Petition 870250079646, dated 05 / 09 / 2025, page 60 / 183 9 / 32 colocation corresponding to each DL RS are given by the qcl-Type top-layer parameter in QCL-Info and can take one of the following values: 'typeA': {Doppler shift, Doppler spread, mean delay, propagated delay} 'typeB': {Doppler shift, Doppler spread} 'typeC: {Doppler shift, mean delay} 'typeD': {Spatial X-ray parameter}.

[0025] Conventionally, in some exemplary cases, the ordered PDCCH RACH may have the following QCL assumptions: (a) the first DCI format indicating the ordered PDCCH RACH is typically transmitted using the same DL-RS1 as the reference as the target DL-RS for the PRACH transmission (e.g., DL-RS1 -> SSB index); (b) UE 102 determines to estimate the path loss for the UL power control for the RACH transmission based on the DL-RS 1 that is nearly colocalized (QCL'd) with the PDCCH DMRS carrying the PDCCH ORDER (DCI message); (c) the second DCI scheduling the RAR is assumed to be QCL'd with the DCI that triggers the PDCCH order (see step 1 in FIG. 1); and (d) the PDSCH that carries the RAR is QCL'D with the second DCI that schedules the RAR (see step 3 in FIG. 1).If UE 102 attempts to detect DCI 1 0 format with 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 that triggers a contention-free random access procedure for the special cell (SpCell) [11, TS 38.321], UE 102 can assume that the PDCCH that includes the second DCI 1 0 format and the PDCCH order may have the same properties of DM-RS antenna port quasi-colocation.

[0026] With reference to the PDCCH order (see step 1 in FIG. 1), the current problem for cross-triggered TRP firing may include the QCL power ratio / control after PRACH (see step 2) is triggered towards DL-RS 2 since if the UE assumes the response to PRACH transmission to be Petition 870250079646, dated 05 / 09 / 2025, page 61 / 183 10 / 32 is monitored according to the target DL RS of the PRACH transmission (targeted behavior / functionality), but the target CORESETpoolIndex may not be configured with the CORESET associated with the CSS of Typel -PDCCH (common search space). This may mean that UE 102 may not be able to monitor the response for the PRACH transmission consequently in the target CORESETpoolIndex CORESET(s). Also, there is ambiguity about how UE monitors the response when the order is triggered by the first TRP 112 (scheduled in the CORESETpoolIndex#0 CORESET) and the target is DL-RS of CORESETpoolIndex#1 (or vice versa). In other words, UE behavior may not be clear in these situations regarding inheritance rules.

[0027] As shown in FIG. 2, for Multi-TRP operation based on multi-DCI with two timing advance (TA) enhancements, support the case where a PDCCH order (i.e., PDCCH-ordered RACH procedure) sent by TRPx triggers a RACH procedure towards TRPx or TRPy for Multi-DCI both inter-cell and intra-cell. In one example, the development includes considering the PRACH power control details and a determination of PDCCH-ordered QCL, PDCCH RAR (which schedules) or PDSCH RAR.

[0028] In the implementation, there may be two CORESETpoolIndices, 0 and 1, which may be TRP indices (logical indices). If the PDCCH order is coming from a CORESET associated with CORESETpoolIndex 0, then the other index may refer to CORESETpoolIndex 1 (or vice versa).

[0029] In any of the examples in this document, the QCL assumption for the PDCCH may refer to the QCL assumption of the demodulation reference signal (DMRS) of the PDCCH. As an example, when a PDCCH is QCL'd with a DL-RS, the same may refer to the DMRS of the PDCCH that is QCL'd with the DL-RS. In some examples, the DL-RS may be included in a TCI state configuration. Thus, in some examples, the TCI state (or the DL-RS included in the TCI state) may be QCL'd with PDCCH or Petition 870250079646, dated 05 / 09 / 2025, p. 62 / 183 11 / 32 PDSCH (DMRS). In some examples, the DL-RS included in the TCI state configuration can be used as a reference for uplink transmission (e.g., PUCCH / PUSCH). A TCI state can include / comprise a DL-RS that has a first QCL type (e.g., type A) and / or two DL-RSs that have a first QCL type (e.g., type A) and a second DL-RS that has a second QCL type (e.g., type D). If the TCI state has two QCL types, the UE can use the one with QCL type D.

[0030] According to this modality, the first downlink control information may indicate a first value (e.g., = 0) that may cause UE 202 to determine the quasi-colocation assumption for the PDCCH that the second DCI that schedules the random access response to be the same as the first DCI that triggers or initiates the random access procedure.

[0031] For example, in step 1 of FIG. 2, if the downlink control information indicates a first value (e.g., = 0), UE 202 can assume the QCL assumption for the PDCCH (PDCCH DMRS) that carries the second DCI that schedules the random access response to be the same as the PDCCH (DMRS) that was used to transmit the first DCI that triggered the PDCCH order.

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

[0033] In another example (option 2), if the first downlink control information (DCI) indicates a second value (e.g., = 1), UE 202 can assume the QCL assumption for the PDCCH carrying the second DCI that schedules the random access response to be the same as the RS of Petition 870250079646, dated 05 / 09 / 2025, page 63 / 183 12 / 32 DL of one of the activated TCI states of the different CORESETpoolIndexes value that was indicated as the target RS for PRACH transmission.

[0034] In the implementation, one of the activated TCI states can include any of: a lower active TCI state identifier in the list of active TCI states, a more recently activated TCI state in the list of active TCI states, or a lower active TCI code point in the list of active TCI states.

[0035] In another example (option 3), downlink control information can indicate whether the first or second indicated TCI state is used as a QCL assumption for the PDCCH (DMRS) that is used to transmit the second DCI that schedules the random access response. In one example, if the random access response follows (i.e., the response is assumed to be transmitted), the indicated TCI state (as a QCL reference) can be configured (e.g., by RRC) and / or indicated in a field in 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 the assumption for the second DCI that schedules the random access response, the UE can determine the QCL assumption based on the indicated TCI state.

[0036] In another example (option 4), downlink control information can indicate whether the random access response is monitored at the CORESETpoolIndex value that triggered the transmission or at a CORESETpoolIndex that is different from the index that triggered the PDCCH order. CORESETpoolIndex can include one or more CORESETs.

[0037] In any of the above modes, if the first downlink control information indicates a second value (e.g., = 1), the QCL assumption for the PDSCH scheduled by the second DCI for which the QCL assumption is determined as above, may be the same as the QCL assumption determined for PDCCH (DMRS) that is used to schedule the second DCI that schedules the random access response. Petition 870250079646, dated 05 / 09 / 2025, page 64 / 183 13 / 32

[0038] In an additional embodiment, if the downlink control information indicates a second value (e.g., = 1) and the first DCI trigger is scheduled on the CORESET configured with a CORESETpoolIndex value of 0, and UE 202 determines the random access response to be monitored on CORESETs with poolindex#1 (or vice versa). In a further example, if either of the CORESETs (from poollndex#1 or poollndex#0, depending on the indication and which CORESETpoolindex#0 value was used to transmit the first DCI trigger) is not associated with CSS Type1 (search space used to monitor the RAR response), the UE may determine to monitor the random access response using C-RNTI (cellular radio network temporary identifier) ​​(or RA-RNTI) in the UE-specific search space (USS) or Type3-CSS of at least one CORESET ID associated with poolindex#1 (or poollndex#0).

[0039] In a further example, the UE can determine random access response monitoring using C-RNTI (or RA-RNTI) in the USS or Type3CSS of at least one CORESET ID associated with poolindex#1 (or poollndex#0). In a further example, the UE can determine random access response monitoring using C-RNTI (or RA-RNTI) in any CSS configured in at least one CORESET ID associated with CORESETpoolIndex#1 (or poollndex#0). Monitoring can be based on at least any one of: a minor CORESET ID, a CORESET ID (or a minor / major CORESET ID) that follows the indicated unified TCI state, or a CORESET ID (minor / major) that is not associated with the unified TCI state.

[0040] In an additional embodiment, if the information in the first DCI that triggers the PDCCH order indicates a first value, this may indicate that the UE monitors the random access response with the same QCL assumption as the PDCCH (DMRS) that was used to schedule the first triggering DCI. In an exemplary additional embodiment, if the information in the first DCI that triggers the PDCCH order indicates a second value, this may Petition 870250079646, dated 05 / 09 / 2025, page 65 / 183 14 / 32 indicates that the UE monitors the random access response with the QCL assumption of the target DL-RS indicated by the first trigger DCI. In a further exemplary embodiment, if the information in the first trigger DCI indicates a second value, this may indicate that the UE monitors the random access response with the QCL assumption determined by the CORESET of a different CORESETpoolIndex value than was used to transmit the first trigger DCI. The QCL assumption may be indicated by the activated TCI state associated with the different CORESETpoolIndex value of the PDCCH (DMRS) that was used to schedule the first trigger DCI that was used for t (e.g., = 1 or indicates that the UE uses a CORESET of another CORESETpoolIndex for response monitoring).

[0041] In an additional embodiment, if the first downlink control information indicates a second value (e.g., = 1) and the first DCI trigger is scheduled on the CORESET configured with a CORESETpoolIndex value of 0, and the UE determines the response to be monitored on CORESETs with poolIndex#1, and the CORESETs (of poolIndex#1) are not associated with CSS Type1 (search space used to monitor RAR response), the UE may determine the monitoring of the response using C-RNTI (or RA-RNTI) in the USS or Type3-CSS of at least one CORESET ID associated with poolIndex#1. Monitoring may be based on at least any one of: a lower CORESET ID, a CORESET ID (or a lower / higher CORESET ID) that follows the indicated unified TCI state, or a CORESET ID (lower / higher) that is not associated with the unified TCI state. The above approach can also be considered the reverse in terms of the CORESETpoolIndex# value.

[0042] In one embodiment, the interpretation of the first and second values ​​may depend on which CORESET (configured with the CORESETpoolIndex value) the first DCI that triggers the ordered random access procedure of PDCCH is scheduled for. Thus, the interpretation of the information field (which provides the first / second / one of the values) in the first DCI Petition 870250079646, dated 05 / 09 / 2025, page 66 / 183 15 / 32 can be conditionally interpreted or may depend on additional parameters or assumptions. For example, if the CORESET transmitting the PDCCH carrying the first DCI (PDCCH ORDER) is configured with CORESETPoolIndex#0, one of the values ​​(e.g., 1) in the information field might refer to CORESETPoolIndex#1. Thus, UE 202 can interpret the value in the first DCI (PDCCH ORDER) depending on the association of CORESETs to the CORESETpoolIndex. As a further example, the first value might indicate that the UE monitors the random access response (RAR) on the CORESET of the same CORESETpoolIndex that was used to transmit the first DCI (PDCCH order).The second value may indicate that UE 202 monitors the random access response in the CORESET from another / different CORESETpoolIndex that was used to transmit the DCI (PDCCH order).

[0043] In one embodiment, the value and association with the CORESETpoolIndex of the information field can be configurable. As an example, the first value (e.g., 0) is configured to indicate the first value of the CORESETpoolIndex (e.g., 0). In another example, the second value (e.g., 1) is configured to indicate a second value of the CORESETpoolIndex (e.g., 1). In one example, the first value might indicate that UE 202 monitors the random access response in the CORESET of the CORESETpoolindex associated with the value (e.g., 0). The second value might indicate that UE 202 monitors the random access response in the CORESET of the CORESETpoolindex associated with the second value (e.g., 1). Thus, random access response monitoring (and the selection of the CORESETpoolindex to determine the assumptions for random access response monitoring) is determined by UE 202 based on the information field that indicates the CORESETpoolindex value.

[0044] In one modality, a field in the first DCI that triggers access Petition 870250079646, dated 05 / 09 / 2025, p. 67 / 183 A 16 / 32 random sorted PDCCH can indicate whether the UE monitors the RA response in CSS (e.g., using RA-RNTI or C-RNTI) or in USS (using C-RNTI or RA-RNTI).

[0045] In an additional embodiment, if the information indicates a second value (e.g., = 1 or indicates that the UE uses CORESET from another CORESETpoolindex for response monitoring), UE 202 can determine path loss 204 for PRACH power control based on the SSB (or target DL-RS2) associated with the PRACH preamble, if the SSB (or target DL-RS2) is configured as the QCL source for one of the TCI states (e.g., TCI enabled states) or based on the PDCCH DMRS of the indicated TCI state, if the SSB (or target DL-RS2) is the QCL source for the TCI state. The target DL-RS2 can be one from an SSB or CSIRS.

[0046] In one embodiment, UE 202 can determine path loss 204 for PRACH power control based on the SSB (or DL-RS2) included in the indicated TCI state. In one example, UE 202 can base power control on the indicated TCI state for the CORESETPoolIndex value. In another example, UE can base power control on the indicated TCI state (the DL-RS2 included in the TCI State) for the CORESETPoolIndex value when the first DCI carrying the PDCCH order indicates that the random access response is monitored on CORESETs with a CORESETPoolIndex value different from the CORESET used to transmit DCI (PDCCH order).

[0047] In one example, the second value / one of the values ​​indicated by the first DCI (PDCCH order) may indicate that UE 202 monitors the DCI that schedules the random access response in CORESET(s) of a CORESETpoolindex different from the CORESETpoolIndex used to transmit the second DCI that triggered the random access transmission. If the indicated TCI state includes two DL-RS (i.e., DL-RS1, DL-RS2), UE 202 may use the one configured with a QCL-typeD. Petition 870250079646, dated 05 / 09 / 2025, page 68 / 183 17 / 32

[0048] In any of the embodiments in this document, the first DCI which includes the first and second values ​​may be provided in the form of a (bit) field in a first DCI message that triggers the ordered random access procedure of PDCCH. If the field is present, it may be configurable by the network (i.e., via RRC signaling). Instead of referring to the first and / or second values, the information may be referred to as “one of the values”. The first and second values ​​may also be interchangeable, vice versa (first = 1 and second = 0).

[0049] FIG. 3 illustrates a set of devices, according to various exemplary modalities.

[0050] According to certain exemplary embodiments, device 320 may be additionally triggered to perform multiple timing advance (TA) maintenance / operation to facilitate triggered transmission of ordered Physical Random Access Channel (PRACH) of Physical Downlink Control Channel (PDCCH) in multi-TRP operations.

[0051] FIG. 3 illustrates a set of 310 and 320 devices according to various exemplary embodiments for performing the steps and functions illustrated in FIGS. 1-2. In the various exemplary embodiments, the 310 device may be an element in or associated with such a communications network, such as a UE, RedCap UE, SL UE, mobile equipment (ME), mobile station, mobile device, stationary device, IoT device, or other device. For example, UEs 102 or 202, according to various exemplary embodiments as discussed above, may be examples of a 310 device. It should be noted that one with ordinary skill in the art would understand that a 310 device may include components or features not shown in FIG. 3. Furthermore, a 320 device may be a network, network entity, core network element, or element in or associated with such a communications network, such as a base station, a NE, or a gNB.For example, the network and gNB 112, 212, and 216, according to various exemplary embodiments discussed above, can be examples of apparatus 320. It should be noted that someone... Petition 870250079646, dated 05 / 09 / 2025, p. 69 / 183 18 / 32 with average skill in the technique would understand that device 320 may include components or features not shown in FIG. 6.

[0052] According to a first exemplary embodiment of the device 310 (i.e., user equipment 102, 202) as shown in FIGS. 1-2. The device 310 (i.e., user equipment 102, 202) may include at least one processor 312 and at least one memory 314, as shown in FIG. 3. The memory 314 may store instructions which, when executed by the processor 312, cause the device 310 to receive, from a network entity 320 (i.e., network entity 112 or 212 and 216 as shown in FIGS.1-2), a physical downlink control channel (PDCCH) that carries first downlink control information (DCI) which includes an indication with settings to trigger or initiate an uplink transmission of a random access procedure toward at least one target downlink reference signal; and determine a near colocation assumption (QCL) for receiving second downlink control information that schedules a random access response (RAR) for the uplink transmission of the random access procedure.

[0053] According to a second exemplary embodiment of device 310 (i.e., user equipment 102, 202) as shown in FIGS. 1-2, the downlink control information indicates a first value that causes the device to determine the quasi-colocation assumption for the PDCCH that carries the second DCI that schedules the random access response to be the same as the first DCI that triggers or initiates the random access procedure.

[0054] According to a third exemplary embodiment of device 310 (i.e., user equipment 102, 202) as shown in FIGS. 1-2, the first downlink control information indicates a second value that causes the device to determine the quasi-colocation assumption for the PDCCH that carries the second DCI that schedules the random access response for Petition 870250079646, dated 05 / 09 / 2025, page 70 / 183 19 / 32 being the same as at least one downlink reference signal indicated by the first received DCI carried by the PDCCH as the target reference signal to trigger the uplink transmission of the random access procedure.

[0055] According to a fourth exemplary embodiment of the 310 device (i.e., user equipment 102, 202) as shown in FIGS. 1-2, the first downlink control information indicates a second value that causes the device to determine the quasi-colocation assumption (QCL) for the PDCCH carrying the second DCI when scheduling the random access response to be the same as at least one downlink reference signal of a transmission control indicator (TCI) state indicated by a CORESETpoolIndex value that is different from an index value that was used to schedule the PDCCH comprising the indication to trigger the uplink transmission of the random access procedure.

[0056] According to a fifth exemplary embodiment of device 310 (i.e., user equipment 102, 202) as shown in FIGS. 1-2, the first downlink control information indicates a second value that causes the device to determine the quasi-colocation assumption for the PDCCH carrying the second DCI that schedules the random access response, to be the same as at least one downlink reference signal of at least one of the activated TCI states of a CORESETpoolIndex value that is different from the CORESETPoolIndex value that was used to trigger the uplink transmission of the random access procedure.

[0057] According to a sixth exemplary embodiment of device 310 (i.e., user equipment 102, 202) as shown in FIGS. 1-2, one of the activated TCI states includes any one of: a lower active TCI state identifier in the list of active TCI states, a more recently activated TCI state in the list of active TCI states, or a lower code point of Petition 870250079646, dated 05 / 09 / 2025, page 71 / 183 20 / 32 TCI active in the list of active TCI states.

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

[0059] According to an eighth exemplary embodiment of device 310 (i.e., user equipment 102, 202) as shown in FIGS. 1-2, the downlink control information indicates the second value that causes the device to determine that the quasi-colocation assumption for the PDCCH carrying the second DCI scheduling the random access response is based on the CORESETpoolIndex value associated with the PDCCH: wherein the first value indicates that the QCL assumption for response monitoring is determined to be at the same CORESETpoolIndex value that was used to trigger the first DCI indicating the RACH, and wherein the second value indicates that the QCL assumption for response monitoring is determined to be at the other CORESETpoolIndex value that was used to trigger the first DCI indicating the RACH.

[0060] According to a ninth exemplary embodiment of 310 (i.e., user equipment 102, 202) as shown in FIGS. 1-2, the first downlink control information indicates the second value that causes the device to determine that the quasi-colocation assumption for the PDCCH carrying the second DCI scheduling random access response is based on a configuration of whether a common polling space type used to monitor the second DCI scheduling random access response is configured.

[0061] According to a tenth exemplary embodiment of the device Petition 870250079646, dated 05 / 09 / 2025, page 72 / 183 21 / 32 310 (i.e., user equipment 102, 202) as shown in FIGS. 1-2, the device is configured to determine, when the search space type is not configured, the monitoring of the PDCCH that carries the scheduling command for the random access response on at least one of: a lower CORESET ID, a CORESET ID that follows unified TCI state, or a (lower) CORESET ID that is not associated with unified TCI state.

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

[0063] According to a twelfth exemplary embodiment of a network entity 320 (i.e., network entity 112, 212, 216) as shown in FIGS. 1-2. The network entity 320 may include: at least one processor 322; and at least one memory 324 that stores instructions that, when executed by at least one processor, cause the network entity to at least: send, to a user equipment (UE), a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) that includes an indication with settings to trigger or initiate on the UE, an uplink transmission of a random access procedure towards at least one target downlink reference signal transmitted by the device, wherein the indication configures the UE to determine a near colocation assumption (QCL) for the second downlink control information received;and schedule transmission of a Random Access Response (RAR) to the UE, based on the second downlink control information, in response to receiving PRACH preambles included in the random access procedure transmitted by the UE.

[0064] According to a thirteenth exemplary modality of Petition 870250079646, dated 05 / 09 / 2025, page 73 / 183 22 / 32 device 310 (i.e., user equipment 102, 202) as shown in FIGS. 1-2, 13. The device includes: means for receiving, from a network entity, a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) which includes an indication with settings to trigger or initiate an uplink transmission of a random access procedure toward at least one target downlink reference signal; and means for determining a near colocation assumption (QCL) for receiving second downlink control information which schedules a random access response (RAR) for the uplink transmission of the random access procedure.

[0065] According to a fourteenth exemplary embodiment of a method performed by an apparatus 310 (i.e., user equipment 102, 202) as shown in FIGS. 1-2, the method includes: receiving, from a network entity, a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) which may include an indication with settings to trigger or initiate an uplink transmission of a random access procedure toward at least one target downlink reference signal; and determining a quasi-colocation assumption (QCL) for receiving second downlink control information which schedules a random access response (RAR) for the uplink transmission of the random access procedure.

[0066] According to a fifteenth exemplary embodiment of a non-transient computer-readable storage medium that stores instructions which, when executed by at least one processor of an apparatus 310 (i.e., user equipment 102, 202) as shown in FIGS. 1-2, cause the apparatus to at least perform: receive, from a network entity, a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) that may Petition 870250079646, dated 05 / 09 / 2025, page 74 / 183 23 / 32 include an indication with settings to trigger or initiate an uplink transmission of a random access procedure toward at least one target downlink reference signal; and determine a near colocation (QCL) assumption for receiving the second downlink control information that schedules a random access response (RAR) for the uplink transmission of the random access procedure.

[0067] According to a sixteenth exemplary embodiment of a network entity 320 (i.e., network entity 112, 212, 216) as shown in FIGS. 1-2.A 320 network entity may include: means for sending to a user equipment (UE) a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) which may include an indication with settings to trigger or initiate on the UE, an uplink transmission of a random access procedure toward at least one target downlink reference signal transmitted by the device, wherein the indication configures the UE to determine a near colocation assumption (QCL) for 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 receiving PRACH preambles comprised in the random access procedure transmitted by the UE.

[0068] According to a seventeenth exemplary embodiment of a method performed by a network entity 320 (i.e., network entity 112, 212, 216) as shown in FIGS. 1-2. The method may include: sending, to a user equipment (UE), a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) which may include an indication with settings to trigger or initiate on the UE, an uplink transmission of a random access procedure towards at least one link reference signal Petition 870250079646, dated 05 / 09 / 2025, page 75 / 183 24 / 32 descending target transmitted by the device, wherein the indication configures the UE to determine a near colocalization assumption (QCL) for receiving second downlink control information; and schedule transmission of a random access response (RAR) to the UE, based on the second downlink control information, in response to receiving PRACH preambles included in the random access procedure transmitted by the UE.

[0069] According to an eighteenth exemplary embodiment of a non-transient computer-readable storage medium that stores instructions that, when executed by at least one processor of a network entity, causes the network entity to at least perform: sending, to a user equipment (UE), a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) that includes an indication with settings to trigger or initiate on the UE, an uplink transmission of a random access procedure towards at least one target downlink reference signal transmitted by the device, wherein the indication configures the UE to determine a near colocation assumption (QCL) for receiving second downlink control information;and schedule transmission of a Random Access Response (RAR) to the UE, based on the second downlink control information, in response to receiving PRACH preambles included in the random access procedure transmitted by the UE.

[0070] In some exemplary embodiments, 310 and / or 320 devices may include one or more processors, one or more computer-readable storage media (e.g., memory, storage or the like), one or more radio access components (e.g., a modem, a transceiver or the like) and / or a user interface. In some exemplary embodiments, 310 and / or 320 devices may be configured to operate using one or more radio access technologies, such as GSM, Petition 870250079646, dated 05 / 09 / 2025, page 76 / 183 25 / 32 LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MultiFire and / or any other radio access technologies.

[0071] As illustrated in the example in FIG. 3, devices 310 and / or 320 may include or be coupled with processors 312 and 322, respectively, to process information and execute instructions or operations. Processors 312 and 322 may be any type of general-purpose or special-purpose processor. In fact, processors 312 and 322 may include one or more general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture as examples. Although a single processor 312 (and 322) for each of the devices 310 and / or 320 is shown in FIG. 3, multiple processors may be used according to other exemplary embodiments.For example, it should be understood that, in certain exemplary embodiments, devices 310 and / or 320 may include two or more processors that can form a multiprocessor system (for example, in this case, processors 312 and 322 may represent a multiprocessor) that can support multiprocessing. According to certain exemplary embodiments, the multiprocessor system may be tightly coupled or loosely coupled to, for example, form a computer cluster.

[0072] Processors 312 and 322 can perform functions associated with the operation of devices 310 and / or 320, respectively, including, as some examples, antenna gain / phase parameter pre-coding, encoding and decoding of individual bits that form a communication message, information formatting, and general control of devices 310 and / or 320, including processes illustrated in FIGS. 1-2.

[0073] Devices 310 and / or 320 may additionally include or be fitted with memory 314 and / or 324 (internal or external), respectively, which may be fitted to processors 312 and 322, respectively, for storage. Petition 870250079646, dated 05 / 09 / 2025, p. 77 / 183 26 / 32 information and instructions that can be executed by 312 and 322 processors. 314 memory (and 324 memory) can be one or more memories and of any type suitable for the local application environment, and can be implemented using any suitable volatile or non-volatile data storage technology, such as a semiconductor-based memory device, a magnetic memory system and device, an optical memory system and device, fixed memory, and / or removable memory. For example, 314 memory (and 324 memory) can consist of any combination of random access memory (RAM), read-only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type 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 devices 310 and / or 320 to perform tasks as described in this document.

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

[0075] In some exemplary embodiments, device 310 may also include or be coupled to one or more antennas 315 to receive a downlink signal and to transmit via an uplink from device 310. Devices 310 and / or 320 may additionally include transceivers 316 and 326, respectively, configured to transmit and Petition 870250079646, dated 05 / 09 / 2025, p. 78 / 183 27 / 32 receive information. Transceivers 316 and 326 may also include a radio interface that may correspond to a plurality of radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB or similar. The radio interface may include other components such as filters, converters (e.g., digital-to-analog converters or similar), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module or similar, to process symbols such as OFDMA symbols carried by a downlink or an uplink.

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

[0077] In certain exemplary embodiments, memory 314 and memory 324 store software modules that provide functionality when executed by processors 312 and 322, respectively. The 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 an application or program, to provide additional 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. Petition 870250079646, dated 05 / 09 / 2025, page 79 / 183 28 / 32 In accordance with certain exemplary embodiments, device 310 may optionally be configured to communicate with device 320 via a wireless or wired communications link 330 in accordance with any radio access technology, such as NR.

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

[0079] As used in this document, the term “circuit set” may refer to hardware-only circuit set implementations (e.g., analog and / or digital circuit sets), combinations of hardware and software circuits, combinations of analog and / or digital hardware circuits with software / firmware, any portions of hardware processor(s) with software, including digital signal processors, that work together to make an appliance (e.g., 310 and / or 320 appliances) perform various functions, and / or hardware processor(s) and / or circuit(s), or portions thereof, that use software for operation, but the software may not be present when it is not required for operation.As a further example, as used in this document, the term "circuit assembly" may also cover an implementation of merely a hardware circuit or processor or multiple processors, or a portion of a hardware circuit or processor and the related software and / or firmware. The term circuit assembly may also cover, for example, a baseband integrated circuit in a server, cellular network device or node, or other network or computing device.

[0080] A computer program product may include one or more computer-executable components that, when the program is run, are configured to perform some modes. Petition 870250079646, dated 05 / 09 / 2025, page 80 / 183 29 / 32 illustrative examples. One or more computer-executable components may be at least one software code or portions thereof. Modifications and configurations necessary to implement functionality of certain illustrative embodiments may be performed as routine(s), which may be implemented as added or updated software routine(s). Software routine(s) may be transferred to the device by download.

[0081] As an example, software or computer program code or portions thereof may be in a source code form, object code form, or some intermediate form, and may be stored on some type of carrier, distribution medium, or computer-readable medium, which may be any entity or device capable of carrying the program. Such carriers may include a recording medium, computer memory, read-only memory, photoelectric and / or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power required, the computer program may run on a single electronic digital computer or may be distributed among multiple computers. The computer-readable medium or computer-readable storage medium may be a non-transient medium.

[0082] In other exemplary embodiments, the functionality may be implemented by hardware or a set of circuits included in an appliance (e.g., appliances 310 and / or 320), for example, through the use of 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 yet another exemplary embodiment, the functionality may be implemented as a signal, a non-tangible medium, which may be carried by an electromagnetic signal transferred by download from the Internet or another network.

[0083] According to certain exemplary embodiments, a device, Petition 870250079646, dated 05 / 09 / 2025, p. 81 / 183 30 / 32 as a node, device, or corresponding component, may be configured as a circuit assembly, a computer or microprocessor, as a single-chip computer element, or as a set of chips, including at least one memory to provide storage capacity used for arithmetic operation and an operation processor to execute the arithmetic operation.

[0084] The features, structures, or characteristics of exemplary modalities described throughout this descriptive report may be combined in any suitable manner into one or more exemplary modalities. For example, the use of expressions such as “certain modalities,” “an exemplary modality,” “some modalities,” or other similar language throughout this descriptive report refers to the fact that a particular feature, structure, or characteristic described in conjunction with a modality may be included in at least one modality.Thus, occurrences of the expressions “in certain modalities,” “an exemplary modality,” “in some modalities,” “in other modalities,” or other similar language throughout this descriptive report do not necessarily refer to the same group of modalities, and the resources, structures, or characteristics described may be combined in any suitable manner in one or more exemplary modalities. Furthermore, the terms “cell,” “node,” “gNB,” or other similar language throughout this descriptive report may be used interchangeably.

[0085] As used in this document, “at least one of the following:<uma lista de dois ou mais elementos> "and at least one of<uma lista de dois ou mais elementos> "And a similar phrase, where the list of two or more elements is joined 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."

[0086] A person with average skill in the technique would readily understand that the revelation as discussed above can be practiced with Petition 870250079646, dated 05 / 09 / 2025, page 82 / 183 31 / 32 procedures in a different order, and / or with hardware elements in configurations that are different from those disclosed. Therefore, although the disclosure has been described based on these exemplary embodiments, it would be evident to those skilled in the art that certain modifications, variations, and alternative constructions would be evident, remaining within the spirit and scope of exemplary embodiments. Although the above embodiments refer to 5G and LTE NR technology, the above embodiments may also apply to any other current or future 3GPP technology, such as LTE-enhanced and / or fourth-generation (4G) technology.

[0087] Partial Glossary: CSI Channel State Information CORESET Control Resource Set RS Channel State Information Reference Signal CSS Common Search Space Set DCI Downlink Control Information DL Downlink Control Signal DMRS Demodulation Reference Signal PDCCH Downlink Control Physical Channel PRACH Random Access Physical Channel QCL Quasi-Colocation RACH Random Access Channel RAR Radio Access Response RNTI Temporary Radio Network Identifier RA-RNTI Random Access - Temporary Radio Network Identifier RS ​​Reference Signal SSB Synchronization and Block Signal PBCH TCI Transmission Coordination Indicator TRP Transmission and Reception Point UE User Equipment UL Uplink Petition 870250079646, dated 05 / 09 / 2025, page 83 / 183 32 / 32 USS User-Specific Search Space Petition 870250079646, dated 05 / 09 / 2025, page 84 / 183

Claims

1 / 5 CLAIMS 1. Wireless communication apparatus characterized by comprising: at least one processor; and at least one memory that stores instructions which, when executed by the at least one processor, cause the apparatus to at least: receive, from a network entity, a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) comprising an indication with settings to trigger or initiate an uplink transmission of a random access procedure toward at least one target downlink reference signal, wherein the first downlink control information indicates a second value that causes the apparatus to determine the quasi-colocation assumption for the PDCCH carrying the second DCI when scheduling the random access response,to be the same as at least one downlink reference signal of a transmission control indicator (TCI) state indicated by a CORESETpoolIndex value, which is different from an index value that was used for the PDCCH comprising the indication to trigger the uplink transmission of the random access procedure; and to determine a near colocation assumption (QCL) for receiving second downlink control information that schedules a random access response (RAR) for the uplink transmission of the random access procedure.

2. Device, according to claim 1, characterized in that the first downlink control information indicates a first value that causes the device to determine the quasi-colocation assumption for the PDCCH carrying the second DCI that schedules the random access response, to be the same as the DCI that triggers or initiates the random access procedure. Petition 870250079646, dated 05 / 09 / 2025, p. 85 / 183 2 / 5 3. Device, according to claim 1, characterized in that the first downlink control information indicates a second value that causes the device to determine the quasi-colocation assumption for the PDCCH carrying the second DCI that schedules the random access response, to be the same as at least one downlink reference signal indicated by the received DCI carried by the PDCCH, as the target reference signal to trigger the uplink transmission of the random access procedure.

4. Device, according to claim 1, characterized in that the first downlink control information indicates a second value that causes the device to determine the quasi-colocation assumption for the PDCCH carrying the second DCI that schedules the random access response, to be the same as at least one downlink reference signal of at least one of the activated TCI states of a CORESETpoolIndex value that is different from the CORESETPoolIndex value that was used to trigger the uplink transmission of the random access procedure.

5. Device according to claim 5, characterized in that one of the activated TCI states comprises any one of: a lowest active TCI state identifier in the list of active TCI states, a most recently activated TCI state in the list of active TCI states, or a lowest active TCI code point in the list of active TCI states.

6. Device according to claim 5, characterized in that the first downlink control information indicates the first or second value that is used as the QCL assumption for the PDCCH carrying the second DCI that schedules the random access response to be the same as a first indicated TCI state when the indication indicates the first value and a second indicated TCI state when the indication indicates the second value.

7. Device according to claim 1, characterized in that the first downlink control information indicates the second value that causes the device to determine that the quasi-colocation assumption for the PDCCH carrying the second DCI scheduling the random access response is based on the CORESETpoolIndex value associated with the PDCCH: wherein the first value indicates that the QCL assumption for response monitoring is determined to be at the same CORESETpoolIndex value that was used to trigger the first DCI indicating the RACH, wherein the second value indicates that the QCL assumption for response monitoring is determined to be at the other CORESETpoolIndex value that was used to trigger the DCI indicating the RACH.

8. Device, according to claim 1, characterized in that the first downlink control information indicates the second value that causes the device to determine that the quasi-colocation assumption for the PDCCH carrying the second DCI that schedules the random access response is based on a configuration of whether a common search space type used to monitor the second DCI that schedules the random access response is configured.

9. Device according to claim 1, wherein the device is characterized by being further caused to determine, when the search space type is not configured, the monitoring of the PDCCH that carries the scheduling command for the random access response on at least one of: a minor CORESET ID, a CORESET ID that follows unified TCI state, or a (minor) CORESET ID that is not associated with unified TCI state. Petition 870250079646, dated 05 / 09 / 2025, p. 87 / 183 4 / 5 10. Apparatus, according to claim 1, characterized in that the uplink transmission of the random access procedure comprises the transmission of PRACH preambles associated with at least one target downlink reference signal.

11. A wireless communication method performed by a device characterized by comprising receiving, from a network entity, a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) comprising an indication with settings to trigger or initiate an uplink transmission of a random access procedure towards at least one target downlink reference signal, wherein the first downlink control information indicates a second value that causes the device to determine the quasi-colocation assumption for the PDCCH carrying the second DCI when scheduling the random access response, to be the same as at least one downlink reference signal of a transmission control indicator (TCI) state indicated by a CORESETpoolIndex value.which is different from an index value that was used for the PDCCH which comprises the indication to trigger the uplink transmission of the random access procedure; and determine a quasi-colocation assumption (QCL) for receiving second downlink control information that schedules a random access response (RAR) for the uplink transmission of the random access procedure.

12. Network entity for wireless communication characterized by comprising: at least one processor; and at least one memory that stores instructions that, when executed by at least one processor, cause the device to at least: send, to a user equipment (UE), a physical downlink control channel (PDCCH) carrying first downlink control information (DCI) comprising an indication with settings to trigger or initiate on the UE, an uplink transmission of a random access procedure towards at least one target downlink reference signal transmitted by the device, wherein the indication configures the UE to determine a near-colocation assumption (QCL) for receiving second downlink control information,wherein the first downlink control information indicates a second value that causes the device to determine the quasi-colocation assumption for the PDCCH carrying the second DCI when scheduling the random access response, to be the same as at least one downlink reference signal of a transmission control indicator (TCI) state indicated by a CORESETpoolIndex value, which is different from an index value that was used for the PDCCH comprising the indication to trigger the uplink transmission of the random access procedure; and schedule transmission, of a random access response (RAR) to the UE, based on the second downlink control information, in response to receiving PRACH preambles comprised in the random access procedure transmitted by the UE. Petition 870250079646, dated 05 / 09 / 2025, p. 89 / 183,

Images