Downlink reference timing determination for physical random access channels in multi-transmit-receive point communications

Abstract

Methods, systems, and devices are described for downlink reference timing determination for a physical random access channel in multi-transmit-receive point communications. A user equipment (UE) can receive control signaling indicating two control resource set pool index values in an active bandwidth portion of at least one serving cell. The two timing advance groups can each be associated with a timing advance offset for a serving cell. The UE can determine two downlink reference timings as reference timings for uplink transmissions. Each downlink reference timing can be associated with a timing advance group identity. The UE can then determine an uplink timing for a physical random access channel or a physical uplink shared channel of a message A based on one or both of the two timing advance offsets and one or both of the two downlink reference timings, and then transmit a preamble according to the determined uplink timing.

Description

Technical Field

[0001] The following relates to downlink reference timing determination for a physical random access channel in multi-transmission-reception-point communications, including downlink reference timing determination for a physical random access channel in multi-transmission-reception-point communications. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0003] The described technology relates to improved methods, systems, devices and apparatuses for supporting downlink reference timing determination for a physical random access channel in multi-transmission reception point communications. For example, the described technology enables a user equipment (UE) to receive control signaling indicating two control resource set pool index values ​​in an active bandwidth portion of at least one serving cell. Two timing advance groups can each be associated with a timing advance offset and configured for a serving cell. The UE can determine two downlink reference timings as reference timings for uplink transmission. Each downlink reference timing can be associated with a timing advance group identity. The UE can then determine the uplink timing for a physical random access channel (PRACH) or a physical uplink shared channel (PUSCH) of message A based at least in part on one or both of the two timing advance offsets and one or both of the two downlink reference timings. The UE can send a preamble in a valid PRACH opportunity for a random access procedure or send message A in a valid PUSCH opportunity based on the determined uplink timing.

[0004] A method for wireless communication at a user equipment (UE) is described. The method may include: determining two downlink reference timings for uplink transmissions within a serving cell, wherein two timing advance groups each associated with a corresponding timing advance offset are configured for the serving cell, and wherein each of the two downlink reference timings is associated with a corresponding timing advance group in the two timing advance groups; determining an uplink timing of a random access preamble for a physical random access channel (PRACH) or a message A for a physical uplink shared channel (PUSCH) based on at least one of the two timing advance offsets, at least one of the two downlink reference timings, or any combination thereof; and as part of a random access procedure, sending the random access preamble in a valid PRACH opportunity or sending the message A in a valid PUSCH opportunity according to the determined uplink timing.

[0005] An apparatus for wireless communication at a UE is described. The apparatus may include: a memory; a transceiver; and at least one processor, the at least one processor being coupled to the memory and the transceiver and configured to: determine two downlink reference timings for uplink transmission within a serving cell, wherein two timing advance groups each associated with a corresponding timing advance offset are configured for the serving cell, and wherein each of the two downlink reference timings is associated with a corresponding timing advance group in the two timing advance groups; determine an uplink timing of a random access preamble for a physical random access channel (PRACH) or a message A for a PUSCH based on at least one of the two timing advance offsets, at least one of the two downlink reference timings, or any combination thereof; and as part of a random access procedure, send the random access preamble in a valid PRACH opportunity or send the message A in a valid PUSCH opportunity according to the determined uplink timing.

[0006] Another apparatus for wireless communication at a UE is described. The apparatus may include: a component for determining two downlink reference timings for uplink transmissions within a serving cell, wherein two timing advance groups each associated with a corresponding timing advance offset are configured for the serving cell, and wherein each of the two downlink reference timings is associated with a corresponding timing advance group in the two timing advance groups; a component for determining an uplink timing of a random access preamble for a physical random access channel (PRACH) or a message A for a PUSCH based on at least one of the two timing advance offsets, at least one of the two downlink reference timings, or any combination thereof; and a component for sending the random access preamble in a valid PRACH opportunity or sending the message A in a valid PUSCH opportunity according to the determined uplink timing as part of a random access procedure.

[0007] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to perform the following operations: determine two downlink reference timings for uplink transmission within a serving cell, wherein two timing advance groups each associated with a corresponding timing advance offset are configured for the serving cell, and wherein each of the two downlink reference timings is associated with a corresponding timing advance group in the two timing advance groups; determine an uplink timing of a random access preamble for a physical random access channel (PRACH) or a message A for a PUSCH based on at least one of the two timing advance offsets, at least one of the two downlink reference timings, or any combination thereof; and as part of a random access procedure, send the random access preamble in a valid PRACH opportunity or send the message A in a valid PUSCH opportunity according to the determined uplink timing.

[0008] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining uplink timing may include operations, features, components, or instructions for determining a single uplink timing for a random access preamble or message A based on a single downlink reference timing of two downlink reference timings and a single timing advance offset of two timing advance offsets.

[0009] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: identifying a single timing advance offset based on a single downlink reference timing; and selecting the single downlink reference timing from the two downlink reference timings based on the single downlink reference timing being the earliest in time among the two downlink reference timings.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: identifying a single timing advance offset based on a single downlink reference timing; and selecting the single downlink reference timing from two downlink reference timings based on the single downlink reference timing corresponding to a selected control resource pool index value of two control resource pool index values ​​for an active bandwidth portion of a serving cell.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: selecting the single downlink reference timing from the two downlink reference timings and selecting the single timing advance offset from the two timing advance offsets based on the uplink timing and the single timing advance offset associated with the single downlink reference timing being earlier than another uplink timing associated with the other downlink reference timing of the two downlink reference timings and the other timing advance offset of the two timing advance offsets.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining a time gap in a symbol between an uplink resource and a valid PRACH opportunity or a valid PUSCH opportunity based on the uplink resource being associated with a downlink reference timing different from a single downlink reference timing, a timing advance offset different from a single timing advance offset, or both.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, transmission using the uplink resource in the same time slot as the PRACH opportunity or the PUSCH opportunity is suppressed based on the uplink resource being associated with different downlink reference timing or different timing advance offsets, or when the gap between a symbol of a PRACH opportunity or a PUSCH opportunity and a symbol of the uplink resource may be smaller than a determined time gap.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, based on identifying that simultaneous transmission using a PRACH opportunity or a PUSCH opportunity and an uplink resource allocated to the UE may not be supported, or when a gap between a symbol of the PRACH opportunity or the PUSCH opportunity and a symbol of the uplink resource may be smaller than a determined time gap, transmission using the uplink resource in the same time slot as the PRACH opportunity or the PUSCH opportunity is suppressed.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining a time gap in a symbol between a synchronization signal block opportunity and a first control resource pool index value and a valid PRACH opportunity or a valid PUSCH opportunity being associated with a second control resource pool index value different from the first control resource pool index value.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that the first PRACH opportunity may be a valid PRACH opportunity or the first PUSCH opportunity may be a valid PUSCH opportunity based on the first PRACH opportunity or the first PUSCH opportunity being at or after a synchronization signal block opportunity and at least a threshold number of symbols after a previously received synchronization signal block.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining a threshold number of symbols based on whether a valid PRACH opportunity or a valid PUSCH opportunity and a synchronization signal block opportunity can both be associated with the same control resource set pool index value.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining the uplink timing may include operations, features, components, or instructions for: determining the downlink reference timing based on a control resource pool index value that may be associated with the downlink reference timing in two downlink reference timings and being associated with the same control resource pool index value associated with a valid PRACH timing or a valid PUSCH timing, or being associated with a timing advance group in two timing advance groups corresponding to the downlink reference timing and being associated with the same control resource pool index value as the valid PRACH timing or the valid PUSCH timing, wherein the uplink timing may be determined based on the determined downlink reference timing.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, based on the fact that both the PRACH opportunity or the PUSCH opportunity and the uplink resource are associated with the same control resource set pool index value, or when the gap between the symbol of the PRACH opportunity or the PUSCH opportunity and the symbol of the uplink resource may be smaller than the time gap between the PRACH opportunity or the PUSCH opportunity and the uplink resource, which are both associated with the same control resource set pool index value, the uplink resource is suppressed from being transmitted in the same time slot as the PRACH opportunity or the PUSCH opportunity.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, based on the fact that both the PRACH opportunity or the PUSCH opportunity and the uplink resource are associated with different control resource set pool index values, or when the gap between the symbol of the PRACH opportunity or the PUSCH opportunity and the symbol of the uplink resource may be smaller than the time gap between the PRACH opportunity or the PUSCH opportunity and the uplink resource, which are both associated with different control resource set pool index values, the uplink resource is suppressed from being used for transmission in the same time slot as the PRACH opportunity or the PUSCH opportunity.

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining a first value of a time gap between a synchronization signal block opportunity and the valid PRACH opportunity or the valid PUSCH opportunity based on the synchronization signal block opportunity being associated with a first control resource pool index value and a valid PRACH opportunity or a valid PUSCH opportunity being associated with a second control resource pool index value different from the first control resource pool index value, the first value of the time gap being different from a second value of the time gap associated with the following situation: the synchronization signal block opportunity and the valid PRACH opportunity or the PUSCH opportunity are associated with the same control resource pool index value. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 An example of a wireless communication system supporting downlink reference timing determination for a physical random access channel in multi-transmission-reception-point communications according to one or more aspects of the present disclosure is illustrated.

[0023] Figure 2 An example of a network architecture supporting downlink reference timing determination for a physical random access channel in multi-transmission-reception-point communications according to one or more aspects of the present disclosure is illustrated.

[0024] Figure 3 An example of a wireless communication system supporting downlink reference timing determination for a physical random access channel in multi-transmission-reception-point communications according to one or more aspects of the present disclosure is illustrated.

[0025] Figure 4A and Figure 4B Each illustrates an example of a timing diagram supporting downlink reference timing determination for a physical random access channel in multi-transmission-reception-point communications according to one or more aspects of the present disclosure.

[0026] Figure 5An example of a timing diagram supporting downlink reference timing determination for a physical random access channel in multi-transmission-reception-point communications according to one or more aspects of the present disclosure is illustrated.

[0027] Fig. 6A and Figure 6B Each illustrates an example of a timing diagram supporting downlink reference timing determination for a physical random access channel in multi-transmission-reception-point communications according to one or more aspects of the present disclosure.

[0028] Figure 7 An example of a process flow supporting downlink reference timing determination for a physical random access channel in multi-transmission-reception-point communications according to one or more aspects of the present disclosure is illustrated.

[0029] Figure 8 and Fig. 9 A block diagram of an apparatus supporting downlink reference timing determination for a physical random access channel in multi-transmission-reception-point communications according to one or more aspects of the present disclosure is shown.

[0030] Fig.10 A block diagram of a communication manager supporting downlink reference timing determination for a physical random access channel in multi-transmission-reception-point communications is shown in accordance with one or more aspects of the present disclosure.

[0031] Fig.11 A diagram of a system including a device supporting downlink reference timing determination for a physical random access channel in multi-transmission-reception-point communications is shown in accordance with one or more aspects of the present disclosure.

[0032] Figure 12 to Figure 14 A flow chart illustrating a method of supporting downlink reference timing determination for a physical random access channel in multi-transmission-reception-point communications according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0033] To avoid interference between the downlink (DL) and the uplink (UL), the user equipment (UE) uses a timing advance (TA) applicable to its UL transmission. The network entity measures the time difference between receiving UL signals (e.g., physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), and / or sounding reference signal (SRS)) from the UE, and transmits a TA command to the UE based on a comparison of the time when the UL signal arrives at the base station and the time (e.g., subframe time) maintained at the network entity. The network entity may then transmit a TA command to the UE, each TA command indicating whether the delay is greater than or less than the current delay, i.e., whether to increase or decrease the TA. In multiple transmit receive point (mTRP) operation, the UE can communicate with two or more physically separated TRPs associated with a single serving cell of the network entity, each TRP using a different timing advance. The UE may also be configured to receive separate or distinct downlink control information (DCI) to schedule communications via each TRP. This mode is referred to as multi-DCI (mDCI).

[0034] When the UE performs a Random Access Channel procedure (also known as RACH) with the serving cell for mTRP operation, the first transmission of the RACH (e.g., Msg1 preamble (PRACH) for 4-step RACH or Message A preamble / PUSCH for 2-step RACH) may be transmitted to either TRP or both TRPs. The TA to be used is based on two values, TA and TA offset. For RACH, the TA used is 0. However, in the case of mTRP operation, the value of the TA offset to be used is unclear, where each TRP may use a different timing advance, for example due to different propagation delays.

[0035] The UE may be configured to operate according to the mTRP configuration using mDCI. The UE then learns the TA offset that the UE is to use, specific to the mDCI and mTRP configuration (or operation), based on the use of the mDCI and mTRP configuration. The UE may then proceed to perform RACH using the TA offset specific to the mDCI and mTRP configuration, specifically, sending the preamble / PRACH according to the timing based on the TA offset.

[0036] The TA offset for PRACH can be the same value shared across TRPs. For example, the gap between the preamble (e.g., RACH preamble) and the UL transmission (PUSCH / PUCCH / SRS) may depend on whether the preamble and the UL transmission are associated with the same DL reference timing and the same timing advance offset (e.g., n-TimingAdvanceOffset) value or with different values. Additionally or alternatively, the gap between the preamble (RACH preamble) and the synchronization signal block (SSB) may depend on whether the control resource set pool index (e.g., CORESETPoolIndex) value used for the SSB is different from the control resource set pool index value used for the preamble.

[0037] Additionally or alternatively, each TRP may have its own associated TA offset value for PRACH. In this case, the gap between the preamble and the UL transmission may depend on whether the preamble and the UL transmission are associated with the same control resource set pool index value or with different control resource set pool index values. For single cell operation (or carrier aggregation in the same frequency band), the gap between the preamble (e.g., RACH preamble) and the UL transmission may be at least a threshold number of symbols or time slots. In some examples, if separate reference timing is applied to preambles of different TRPs, the gap size may depend on whether the SSB and / or UL transmissions are associated with the same control resource set pool index value or with different control resource set pool index values.

[0038] Various aspects of the present disclosure are first described in the context of a wireless communication system. Various aspects of the present disclosure may be described with reference to timing diagrams associated with downlink reference timing determination for a physical random access channel in multiple transmission-reception-point communications. Various aspects of the present disclosure are further illustrated and described by and with reference to apparatus diagrams, system diagrams, and flow diagrams associated with downlink reference timing determination for a physical random access channel in multiple transmission-reception-point communications.

[0039] Figure 1 An example of a wireless communication system 100 that supports downlink reference timing determination for a physical random access channel in multi-transmission reception point communications according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0040] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0041] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

[0042] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0043] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0044] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a home Node B, a home evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0045] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0046] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functionalities, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 can be within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 can be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 that communicate via those communication links.

[0047] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0048] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol defining signaling messages (e.g., an F1AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) via an Xn-C interface (which may be an example of a portion of a backhaul link).

[0049] The IAB node 104 may refer to a RAN node that provides IAB functions (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). The DU 165 may act as a distributed scheduling node toward a child node associated with the IAB node 104, and the IAB-MT may act as a scheduled node toward a parent node associated with the IAB node 104. That is, the IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., the IAB donor may relay the UE's transmission through one or more other IAB nodes 104). Additionally or alternatively, the IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104, depending on the relay chain or configuration of the AN. Therefore, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104, and the DU interface (e.g., DU 165) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115.

[0050] For example, the IAB node 104 may be referred to as a parent node supporting communications for a child IAB node or as a child IAB node associated with an IAB donor, or both. The IAB donor may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay the transmission to the UE 115 through the IAB node 104, or may directly signal the transmission to the UE 115, or both. The CU 160 of the IAB donor may signal the IAB node 104 via the F1 interface that the communication link is established, and the IAB node 104 may schedule the transmission (e.g., the transmission relayed from the IAB donor to the UE 115) through the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling via the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0051] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support downlink reference timing determination for a physical random access channel in multi-transmission-reception-point communications as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0052] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0053] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 as shown in .

[0054] The UE 115 and the network entity 105 may use resources associated with one or more carriers to wirelessly communicate with each other via one or more communication links 125 (e.g., access links). The term "carrier" may refer to a collection of RF spectrum resources having a physical layer structure defined to support the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send", "receive", or "communicate" when referring to the network entity 105 may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0055] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified based on a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be made by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

[0056] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry downlink communications and uplink communications (e.g., in TDD mode).

[0057] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communications using a particular carrier bandwidth, or may be capable of being configured to support communications using one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0058] The signal waveform transmitted via the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0059] One or more parameter sets for a carrier may be supported, and the parameter sets may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0060] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0061] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of micro time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0062] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0063] Physical channels may be multiplexed according to various techniques in order to communicate using a carrier. For example, physical control channels and physical data channels may be multiplexed using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique to signal via a downlink carrier. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0064] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., using a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other identifier) ​​used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0065] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have a service subscription with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) (compared to a macro cell), and the small cell may operate using the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to a UE 115 that has a service subscription with a network provider, or may provide restricted access to a UE 115 associated with a small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

[0066] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0067] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0068] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and in some examples, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operation.

[0069] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0070] In some examples, the UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.

[0071] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0072] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than communications using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0073] The wireless communication system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz (also known as a centimeter band), or an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also known as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between a UE 115 and a network entity 105 (e.g., a base station 140, a RU 170), and the EHF antennas of the corresponding devices may be smaller and closer together than UHF antennas. In some examples, such techniques may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by even greater attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0074] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations performed using unlicensed bands may be based on carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations performed using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0075] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0076] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. The multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technologies include: single-user MIMO (SU-MIMO), for which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are sent to multiple devices.

[0077] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0078] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105), or by a receiving device (such as UE 115)) beam directions for later transmission or reception by the network entity 105.

[0079] Some signals, such as data signals associated with a particular receiving device, may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115)). In some examples, the beam direction associated with the transmission along the single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0080] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may or may not be precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0081] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0082] The UE may receive control signaling indicating two control resource set pool index values ​​in the active bandwidth portion of at least one serving cell. The two timing advance groups may each be associated with a timing advance offset for the serving cell. The UE may determine two downlink reference timings as reference timings for uplink transmissions. Each downlink reference timing may be associated with a timing advance group identity. The UE may then determine an uplink timing for a physical random access channel or a physical uplink shared channel of message A based on one or both of the two timing advance offsets and one or both of the two downlink reference timings, and then send a preamble according to the determined uplink timing.

[0083] Figure 2 An example of a network architecture 200 (e.g., a decomposed base station architecture, a decomposed RAN architecture) supporting downlink reference timing determination for a physical random access channel in multi-transmission reception point communications according to one or more aspects of the present disclosure is illustrated. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a, which may communicate directly with a core network 130-a via a backhaul communication link 120-a, or indirectly communicate with the core network 130-a through one or more decomposed network entities 105 (e.g., a near RTRIC 175-b via an E2 link or a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both. The CU 160-a may communicate with one or more DUs 165-a via a corresponding midhaul communication link 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via respective fronthaul communication links 168-a. The RUs 170-a may be associated with respective coverage areas 110-a and may communicate with the UEs 115-a via one or more communication links 125-a. In some implementations, the UEs 115-a may be served by multiple RUs 170-a simultaneously.

[0084] Each of the network entities 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or send signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via a transmission medium. For example, these network entities 105 may include a wired interface that is configured to receive signals on a wired transmission medium or to send signals to one or more of the other network entities 105 on a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals on a wireless transmission medium, or to send signals to one or more of the other network entities 105 on a wireless transmission medium, or both.

[0085] In some examples, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to process user plane functions (e.g., CU-UP), control plane functions (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.

[0086] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may at least partially host one or more of the RLC layer, the MAC layer, and one or more aspects of the PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), which depends at least in part on functional divisions, such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU160-a.

[0087] In some examples, lower layer functions may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both based at least in part on functional splitting (such as lower layer functional splitting). In this architecture, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a. In some examples, this configuration may enable the DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0088] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a may be configured to support the deployment of dedicated physical resources for RAN coverage purposes, which may be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., an O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a may communicate with components configured according to a 4G RAN (e.g., via an O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0089] The non-RT RIC 175-a may be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a may be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic functions that implement near real-time control and optimization of RAN elements and resources via data collection and actions on an interface connecting one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b (e.g., via an E2 interface).

[0090] In some examples, in order to generate an AI / ML model to be deployed in the near-RT RIC 175-b, the non-RT RIC 175-a may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 175-b and may be received from a non-network data source or from a network function at the SMO 180-a or the non-RT RIC 175-a. In some examples, the non-RT RIC 175-a or the near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the non-RT RIC 175-a may monitor long-term trends and patterns of performance and employ an AI model or ML model to perform corrective actions through the SMO 180-a (e.g., via reconfiguration of O1) or via the generation of a RAN management policy (such as an A1 policy).

[0091] Figure 3 An example of a wireless communication system 300 that supports downlink reference timing determination for a physical random access channel in multiple transmit receive point (mTRP) communications in accordance with one or more aspects of the present disclosure is illustrated.

[0092] The first TRP 305-a and the second TRP 305-b may be configured to communicate with the UE 115-b. The UE 115-b may use the first TA for uplink communication with the first TRP 305-a and use the second TA for uplink communication with the second TRP 305-b. According to some prior art techniques, for example in the case of mDCI for mTRP communication 345, support is provided for handling of very different propagation delays per TRP TA to two TRPs. For intra-cell and inter-cell multi-DCI (mDCI) and multi-TRP (mTRP) scenarios, it may be desirable to support techniques using two TAs.

[0093] For multi-DCI multi-TRP operation with two TAs, different scenarios can be considered. In one example, two reference timings can be used. In another example, one reference timing can be used. Therefore, for multi-DCI multi-TRP operation with two TAs, up to two timing advance offset values ​​(e.g., n-TimingAdvanceOffset values) per serving cell can be supported.

[0094] In one example, uplink frame 350 number i for transmission from a UE may start T before the corresponding downlink frame 355 number i starts at the UE. TA =(N TA +N TA,offset )T c , except for msgA sent on PUSCH, N TA,offsetmay have a preset value or a configured value, for example, indicated by a correspondence table known to UE 115-b, where the value N may be used. TA =0 (e.g., UE 115-b may use the value 0). For PRACH transmission, UE 115-1 may use (or need to use) N TA =0 in order to obtain or acquire the initial TA.

[0095] In some examples, for single-cell operation or for operation with carrier aggregation in the same frequency band, UE 115-b may not transmit PRACH and PUSCH / PUCCH / SRS in the same time slot or may not transmit PRACH and PUSCH / PUCCH / SRS in the first time slot when the gap between the first or last symbol of the PRACH transmission in the first time slot is less than N symbols from the last or first symbol of the PUSCH / PUCCH / SRS transmission in the second time slot, respectively, where N=2 when μ=0 or μ=1, N=4 when μ=2 or μ=3, N=16 when μ=5, N=32 when μ=6, and μ is the subcarrier spacing (SCS) configuration for the active UL BWP. For PUSCH transmissions with repetition type B, this may apply to each actual repetition for the PUSCH transmission. In some examples, the SCS for the active UL BWP may be 15 kHz. Therefore, in an example where the gap is less than 2 symbols, UE 115-b may not transmit PRACH and PUSCH / PUCCH / SRS. In another example where the gap is greater than 2 symbols, UE 115-b may transmit PRACH and PUSCH / PUCCH / SRS.

[0096] In some examples, for a single TA, the DL reference timing for PRACH / msgA PUSCH and PUSCH / PUCCH / SRS is the same, and the gap is related to the UL TA difference between PRACH / msgA PUSCH and PUSCH / PUCCH / SRS. For PRACH / msgA PUSCH, transmission may start T before the corresponding DL reference timing. TA1 =N TA,offset *T c For PUSCH / PUCCH / SRS, transmission can start T before the corresponding DL reference timing TA2 =(N TA +N TA,offset )*T cIn some examples, it is assumed that the last symbol of PRACH or msgA PUSCH ends at t1 and the first symbol of PUSCH / PUCCH / SRS starts at t2, where t1 and t2 are logical times. To avoid overlap between PRACH / msgA PUSCH and PUSCH / PUCCH / SRS, the actual end position of PRACH or msgA PUSCH may be no later than the start position of PUSCH / PUCCH / SRS, i.e., T Rx -T Tx1 +t1-T TA1 ≤T Rx -T Tx2 +t2-T TA2 Therefore, t2-t1≥(T TA2 -T TA1 )+(T Tx2 -T Tx1 ). In one example, for a single component carrier (CC), T Tx2 -T Tx1 = 0. Therefore, in some examples, if the gap is greater than 2 symbols, UE 115-b may send PRACH and PUSCH / PUCCH / SRS.

[0097] In some examples, for unpaired spectrum (e.g., unpaired radio frequency spectrum band), if tdd-UL-DL-ConfigurationCommmon is not provided to the UE, then the PRACH opportunity in the PRACH slot does not precede the SS / PBCH block in the PRACH slot and starts at least N after the last SS / PBCH block received symbol. gap It is valid when there are N symbols. gap Provided in Table 8.1-2, and if channelAccessMode="semiStatic" is provided, it does not overlap with a set of consecutive symbols before the start of the next channel occupancy time when the UE is not transmitting. In such examples, the candidate SS / PBCH block index of the SS / PBCH block may correspond to the SS / PBCH block index provided by SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon.

[0098] In some examples, these examples can be in the context of the gap between SSB and PRACH, if tdd-UL-DL-ConfigurationCommon is provided to the UE, then the PRACH opportunity in the PRACH slot is within the UL symbol, or it is not located before the SS / PBCH block in the PRACH slot and starts at least N after the last downlink symbol.gap symbols and starts at least N after the last SS / PBCH block symbol. gap It is valid when there are N symbols. gap Provided in Table 8.1-2, and if channelAccessMode="semiStatic" is provided, it does not overlap with a set of consecutive symbols before the start of the next channel occupancy time that may not have any transmission. In such examples, the candidate SS / PBCH block index of the SS / PBCH block corresponds to the SS / PBCH block index provided by SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon.

[0099] In some examples, which may be in the context of a gap between an SSB and msgA PUSCH, a PUSCH opportunity is valid if it does not overlap in time and frequency with any valid PRACH opportunity associated with a type 1 random access procedure or a type 2 random access procedure. Additionally, for unpaired spectrum and for SS / PBCH blocks with an index provided by ssb-PositionsInBurst in SIB1 or by ServingCellConfigCommon. In such examples, if tdd-UL-DL-ConfigurationCommon is not provided to the UE, the PUSCH opportunity may or may not be located before the SS / PBCH block in the PUSCH slot and starts at least N after the last SS / PBCH block symbol. gap It is valid when there are N symbols. gap For example, it is provided at UE 115-b by configuration, and if channelAccessMode="semiStatic" is provided, it does not overlap with a group of consecutive symbols before the start of the next channel occupancy time when the UE is not transmitting.

[0100] In some examples, if tdd-UL-DL-ConfigurationCommon is provided to the UE, the PUSCH opportunity is within the UL symbol at that PUSCH opportunity, or does not precede the SS / PBCH block in the PUSCH slot and starts at least N after the last downlink symbol. gap symbols and starts at least N after the last SS / PBCH block symbol. gap It is valid when there are N symbols. gapBy configuration or provided in a table, for example, and if channelAccessMode="semiStatic" is provided, then there is no overlap with a group of consecutive symbols before the start of the next channel occupancy time when the UE is not transmitting.

[0101] In some examples, to avoid DL to UL interference, the gap between SSB and PRACH / msgAPUSCH can take into account DL propagation delay and UL TA. For PRACH / msgAPUSCH, transmission starts T before the corresponding DL reference timing. TA =N TA,offset *T c Assume that the last symbol of SSB ends at t1 and the first symbol of PRACH / msgAPUSCH starts at t2, where t1 and t2 are logical times. To avoid DL to UL interference, the actual end position of SSB should not be later than the start position of PRACH / msgAPUSCH, that is, T Rx -T Tx1 +t1+d / c≤T Rx -T Tx2 +t2-T TA Therefore, t2-t1≥d / c+T TA +(T Tx2 -T Tx1 ), where d is the maximum distance between gNB and UE, and c is the speed of light. If SSB and PRACH / msgA are in the same carrier, then T Tx2 -T Tx1 =0.

[0102] In some additional examples, N gap The value can be configured as shown in Table 1 below:

[0103]

[0104] In the context of a wireless communication system 300, a UE 115-b may receive control signaling 315 indicating two control resource pool index values ​​in an active bandwidth portion of at least one serving cell. For example, TRP 305-a and TRP 305-b may be part of a serving cell, and a first control resource pool may be associated with TRP 305-a, and a second control resource pool may be associated with TRP 305-b. The two timing advance groups may each be associated with a timing advance offset for the serving cell. The UE 115-b may determine two downlink reference timings as reference timings for uplink transmissions. Each downlink reference timing may be associated with a timing advance group identity. The UE 115-b may then determine uplink timing for a physical uplink shared channel for a PRACH (e.g., a PRACH preamble) or message A based on at least one of the two timing advance offsets, at least one of the two downlink reference timings, or any combination thereof. UE 115-b may then send a preamble 320 (e.g., in a PRACH timing or msgA PUSCH) based on the determined uplink timing. Once the random access process is completed, UE 115-b may receive scheduling information for the serving cell (e.g., a first mDCI 325) via TRP 305-a and continue to communicate on the UL using UL communication 335, and UE 115-b may receive scheduling information for the serving cell (e.g., a second mDCI 330) via TRP 305-b and continue to communicate on the UL using UL communication 340.

[0105] Figure 4A An example of a timing diagram 401 for supporting downlink reference timing determination for a physical random access channel in multi-transmission reception point communications according to one or more aspects of the present disclosure is illustrated. The timing diagram 401 may be as described with respect to Figure 1 The described UE 115 and / or network entity 105 implements. More specifically, when the UE 115 is configured with two control resource set pool index values ​​in the active bandwidth portion of the serving cell, the UE may implement the timing diagram 401 to determine an initial timing advance for PRACH transmission and / or msgA transmission on PUSCH.

[0106] For PRACH transmission and msgA transmission, N TA=0. However, for the mDCI mTRP mode, as described herein, two downlink reference timings and two different timing advance offsets (e.g., n-TimingAdvanceOffset values) can be configured. Additionally, the device can implement PRACH for each TRP of the mTRP to identify the initial TA for each TRP. PRACH transmissions for different TRPs can be parallel or non-parallel. As noted, since each CC can support two timing advance offset values, two downlink reference timings for uplink transmissions can also be supported. Timing diagram 401 illustrates an example technique that can be used to determine uplink transmission timing for PRACH or msgA PUSCH.

[0107] According to a first option for determining uplink transmission timing for PRACH or msgA PUSCH transmissions associated with different CORSETPoolIndex values ​​(where each index corresponds to a corresponding TRP), the PRACH timing may be determined based on a single DL reference timing and a single timing advance offset value (e.g., n-TimingAdvanceOffset value). That is, even if there are two (or more) downlink reference timings and two (or more) timing advance offset values ​​for a CC, a single downlink reference timing and a single timing advance offset value may be used for PRACH or msgA PUSCH transmissions, which may support PRACH transmission alignment (between two TRPs) and reduce complexity at the UE. In such cases, there may be a variety of techniques for determining downlink reference timing and timing offset values ​​for PRACH or msgA PUSCH transmissions. According to a first example of this option, a single downlink reference timing is determined as the earlier downlink reference timing of the two downlink reference timings. The single timing advance offset value is associated with the same timing advance group (TAG) as the single downlink reference timing (the earliest downlink reference timing). According to a second example of this option, a single downlink reference timing is determined as a downlink reference timing associated with a specific CORSETPoolIndex value (e.g., a first CORSETPoolIndex value, a smaller CORSETPoolIndex value, a later CORSETPoolIndex value, or a larger CORSETPoolIndex value). In such a case, a single timing advance offset value may be determined as a timing advance offset value associated with the same TAG as the determined downlink reference timing. Thus, in both examples, the downlink reference timing is determined, and then the timing advance offset is determined based on the determined downlink reference timing.

[0108] As illustrated in timing diagram 401, the UE selects the downlink reference timing as the downlink reference timing 450 for TRP 1 or the downlink reference timing 455 for TRP 2 based on the earlier downlink reference timing or the downlink reference timing associated with the CORSETPoolIndex value (e.g., the first value or a smaller value). Therefore, in case the downlink reference timing 450 for TRP1 is selected, the UE selects the timing advance offset (e.g., N ) associated with the same TAG as TRP1. TA_offset，1 ). As described, the downlink reference timing 450 or 455 is based on the time at which the transmission is received from the TRP. Thus, TRP1 transmits a downlink transmission 405 at 425, which is received at the UE at the downlink reference timing 450 and is offset from the transmission time by T P1 Similarly, TRP2 transmits a downlink transmission 415 at 435, which is received at the UE at a downlink reference timing 455 and is offset from the transmission time by T P2 .

[0109] If the UE uses the downlink reference timing 450 (e.g., as the earliest downlink reference timing or the lowest CORSETPoolIndex value) and the corresponding timing advance offset, the UE can determine that the timing 430 of the PRACH transmission 410 for TRP1 and the timing 445 of the PRACH transmission 420 for TRP2 are aligned (e.g., the timing 430 and 445 are aligned). It should be noted that the downlink reference timing 455 and the corresponding timing advance offset for the downlink transmission 415 of TRP2 can also be used to determine the PRACH timing for the two TRPs. It should be noted that in the example of the timing diagram 401, the PRACH transmission 410 and the PRACH transmission 420 can be changed to msgA transmissions, and the timing of the msgA transmissions can be determined as described with respect to the timing diagram 401.

[0110] Figure 4B An example of a timing diagram 402 is illustrated to support downlink reference timing determination for a physical random access channel in multi-transmission reception point communications in accordance with one or more aspects of the present disclosure. Figure 4A As described, when a UE is configured with two control resource set pool index values ​​in the active bandwidth portion of a serving cell, the UE may implement timing diagram 402 to determine an initial timing advance for PRACH transmissions and / or msgA transmissions on a PUSCH.

[0111] Specifically, timing diagram 402 illustrates a third example of using a single downlink reference timing and a single timing advance offset value for PRACH transmission. In the illustrated example, the UE can use two sets of parameters (e.g., the first downlink reference timing and the second downlink reference timing and the first timing advance offset value and the second timing advance offset value) to calculate the timing of the PRACH transmission (or the timing of the msgA transmission), and then select the earliest (or latest) PRACH / msgA timing to send these two transmissions to each of these TRPs.

[0112] Similarly, as regards Figure 4A As described in the timing diagram 401 of FIG. 4 , the UE determines a downlink reference timing 450 for a downlink transmission 405 of TRP1 and a downlink reference timing 455 for a downlink transmission 415 corresponding to TRP2. The UE also determines a timing advance offset corresponding to the TAG of TRP1 and a timing advance offset corresponding to the TAG of TRP2. The UE then applies the timing advance offset for TRP1 to the downlink reference timing 450 and the timing advance offset for TRP2 to the downlink reference timing 455 to determine the corresponding PRACH (or msgA) timing (e.g., timing 430 using parameters corresponding to TRP1 and downlink reference timing 465 using parameters corresponding to TRP2). The UE then selects the earliest (or latest) timing of the two determined timings for the transmission of both the PRACH transmission 410 and the PRACH transmission 420. In the illustrated example, the UE selects the timing 430 for the transmission of both the PRACH transmission 410 and the PRACH transmission 420. Note that in the example of timing diagram 402, PRACH transmission 410 and PRACH transmission 420 may be changed to msgA transmission. Figure 4A As described, even if there are two (or more) downlink reference timings and two (or more) timing advance offset values ​​for a CC, a single downlink reference timing and a single timing advance offset value can be used for PRACH or msgAPUSCH transmission, which can support PRACH transmission alignment (between two TRPs) and reduce complexity at the UE.

[0113] Figure 5 An example of a timing diagram 500 for supporting downlink reference timing determination for a physical random access channel in multi-transmission reception point communications according to one or more aspects of the present disclosure is illustrated. The timing diagram 501 may be as described with respect to Figure 1The described UE 115 and / or network entity 105 implements. More specifically, when the UE 115 is configured with two control resource set pool index values ​​in the active bandwidth portion of the serving cell, the UE may implement the timing diagram 501 to determine the initial timing advance for PRACH transmission and / or msgA transmission on the PUSCH.

[0114] exist Figure 5 In the example of timing diagram 500 of FIG. 5 , the UE may be configured with different CORSETPoolIndex values ​​corresponding to separate TRPs. Instead of selecting a downlink timing reference and a timing advance offset value (such as Figure 4A and Figure 4B As described above, the UE can use each downlink timing reference and timing advance offset value to determine the separate PRACH transmission or msgA PUSCH timing corresponding to each TRP.

[0115] Thus, as described with respect to FIG. 4 , the UE determines a downlink reference timing 450 for a downlink transmission 405 of TRP1 and a downlink reference timing 455 for a downlink transmission 415 corresponding to TRP2. In the illustrated example, the downlink reference timing of a given CORESETPoolIndex value associated with a corresponding PRACH transmission or msgA transmission or a downlink reference timing associated with a TAG associated with the same CORESETPoolIndex value as the PRACH transmission or msgA transmission is used. Similarly, the timing of a PRACH or msgA PUSCH transmission is determined using a timing advance offset value of a given CORESETPoolIndex value associated with a corresponding PRACH transmission or msgA transmission or a timing advance offset associated with a given TAG associated with the same CORESETPoolIndex value as the PRACH transmission or msgA transmission. Therefore, the UE may determine the timing 430 for the PRACH transmission 410 corresponding to TRP1 and the timing 510 for the PRACH transmission 420 corresponding to TRP2. Figure 5 The example of may result in misaligned PRACH transmissions of TRP1 and TRP2, which may result in increased UE complexity and power control considerations as well as improved signal diversity.

[0116] Fig. 6A An example of a timing diagram 601 for supporting downlink reference timing determination for a physical random access channel in multi-transmission reception point communications according to one or more aspects of the present disclosure is illustrated. The timing diagram 601 may be as described with respect to Figure 1The described UE 115 and / or network entity 105 may implement the timing diagram 601. More specifically, the UE 115 may implement the timing diagram 601 to determine whether to send a PRACH transmission or a msgA PUSCH transmission when operating in the mDCI and mTRP modes.

[0117] When the UE uses a single downlink reference timing for mTRPPRACH or msgA PUSCH associated with the first CORESETPoolIndex value (as described in relation to Figure 4A and Figure 4B As described above) and two downlink reference timings are used for PUSCH, PUCCH and / or SRS, then the downlink reference timing (and timing advance offset) may be different for PRACH or msgA PUSCH associated with the second CORESETPoolIndex value and PUSCH, PUCCH or SRS. For PRACH or msgAPUSCH, the reference timing associated with the first CORESETPoolIndex value (e.g., the first reference timing) is used, while for PUSCH / PUCCH / SRS, the reference timing associated with the second CORESETPoolIndex value (e.g., the second reference timing) is used. In addition, the n-TimingAdvanceOffset values ​​between PRACH / msgA PUSCH and PUSCH / PUCCH / SRS may also be different. Taking the above into account, the gap between PRACH / msgA PUSCH and PUSCH / PUCCH / SRS may be different from how the UE may determine the gap in other cases.

[0118] For PRACH / msgA PUSCH, transmission starts T before the first DL reference timing TA1 =N TA,offset,1 *T c For PUSCH / PUCCH / SRS, the transmission starts before the second DL reference timing T TA2 =(N TA +N TA,offset,2 )*T c Assume that the last symbol of PRACH or msgA PUSCH ends at t1 and the first symbol of PUSCH / PUCCH / SRS starts at t2, where t1 and t2 are logical times. To avoid overlap between PRACH / msgA PUSCH and PUSCH / PUCCH / SRS, the actual end position of PRACH or msgAPUSCH should be no later than the start position of PUSCH / PUCCH / SRS, i.e., t1+T Rx1 -T Tx1 -T TA1 ≤t2+TRx2 -T Tx2 --T TA2 Therefore, t2-t1≥(T TA2 -T TA1 )+(T Tx2 -T Tx1 )-(T Rx2 -T Rx1 )=N TA *T c +(TT x2 -T Tx1 )+(N TA,offset,2 -N TA,offset,1 )*T c -(T Rx2 -T Rx1 ), where T Rx2 is the DL reference timing of PUSCH / PUCCH / SRS, T Rx1 is the DL reference timing of PRACH / msgA PUSCH, N TA，offset，2 is the timing advance offset value of PUSCH / PUCCH / SRS, and N TA，offset，1 It is the timing advance offset value of PRACH / msgA PUSCH.

[0119] Similarly, when PRACH / msgA uses a different reference timing detected from SSB, the gap between SSB and PRACH / msgAPUSCH may also be different from the existing specification. For PRACH / msgA PUSCH, transmission starts T before the corresponding DL reference timing. TA =N TA,offset，x *T c Assume that the last symbol of SSB ends at t1 and the first symbol of PRACH / msgA PUSCH starts at t2, where t1 and t2 are logical times. To avoid DL to UL interference, the actual end position of SSB should not be later than the start position of PRACH / msgA PUSCH, that is, t1+T Rx1 -T Tx1 +d / c≤t2+T Rx2 -T Tx2 -T TA Therefore, t2-t1≥d / c+T TA +(T Tx2 +T Tx1 )-(T Rx2 -T Rx1), where d is the maximum distance between the gNB and the UE, and c is the speed of light (e.g., d / c is the downlink propagation delay). Therefore, due to the difference in downlink reference timing, the gap between the SSB and the PRACH or msgA may be determined to be different from the gap between the SSB and the PRACH associated with the same downlink reference timing.

[0120] Therefore, in some cases, even when Figure 4A and Figure 4B When selecting between two downlink timing references for PRACH or msgAPUSCH transmission as described above, the PRACH or msgAPUSCH downlink timing reference is also the same as the downlink timing reference PUSCH, PUCCH or SRS. In such a case, the UE may select the same downlink timing reference as described herein. Figure 3 However, in some examples, the UE may use Figure 4A and Figure 4B The described techniques determine different downlink timing references for PRACH or msgA PUSCH transmissions and PUSCH, PUCCH or SRS. In such cases (e.g., PRACH / msgA PUSCH and PUSCH / PUCCH / SRS are associated with different downlink reference timings), the UE may not send PRACH / msgA PUSCH and uplink transmissions in the same time slot, or various techniques may be used to determine the gap (e.g., time gap value or threshold) used to determine whether to send PRACH / msgA PUSCH and uplink transmissions in different time slots.

[0121] According to one technique for determining the gap, a new value N' may be used, where N' is configurable for each SCS. TA,offset,2 -N TA,offset,1 )*T c -(T Rx2 -T Rx1 )<0, then N' is less than N, where N is the existing gap. TA,offset,2 -N TA,offset,1 )*T c -(T Rx2 -T Rx1 )>0, then N' is greater than N, where N is the existing gap. According to another technique, the additional gap value Δ N Used with the existing gap N between PRACH / msgA PUSCH and PUSCH / PUCCH / SRS. N Based on N TA,offset,2 -N TA,offset,1 and T Rx2 -T Rx1 To determine.N It is for each SCS or each frequency band. Therefore, when the UE determines different downlink reference timings for PRACH / msgA and PUSCH, PUCCH, SRS, the new gap is equal to N+Δ N .

[0122] Therefore, the UE may apply one of these gap values ​​(eg, N' or N+Δ N ) to determine whether to send PRACH / msgA PUSCH and PUSCH, PUCCH or SRS in different time slots. According to one specific implementation of single-cell operation or operation with carrier aggregation in the same frequency band, if PRACH / msgA PUSCH and PUSCH / PUCCH / SRS are associated with different downlink reference timing and / or different n-TimingAdvanceOffset values, the UE sends PRACH / msgA PUSCH and PUSCH / PUCCH / SRS when the gap between the first symbol or the last symbol of a PRACH transmission in a first time slot is less than N′ symbols away from the last symbol or the first symbol of a PUSCH / PUCCH / SRS transmission in a second time slot, respectively. According to a second specific implementation of single-cell operation or operation with carrier aggregation in the same frequency band, if PRACH / msgA PUSCH and PUSCH / PUCCH / SRS are associated with different downlink reference timings and / or different n-TimingAdvanceOffset values, the gap between the first symbol or the last symbol of a PRACH transmission that is not in the same time slot or that is not in the first time slot of the UE is separated from the last symbol or the first symbol of a PUSCH / PUCCH / SRS transmission in the second time slot, respectively, by less than N+Δ N If PRACH / msgA PUSCH and PUSCH / PUCCH / SRS are associated with different CORESETPoolIndex values ​​and different downlink reference timing, these rules are applicable when simultaneous transmission between PRACH / msgA PUSCH and PUSCH / PUCCH / SRS is not supported.

[0123] about Fig. 6A The application of these clearance rules is illustrated in Fig. 6AIn the timing diagram 601 of FIG. 6 , the slot boundary 615 is located between a set of RACH opportunities 605 and a set of uplink resources 610. According to the first scenario, the UE determines the same downlink reference timing between PRACH (or msgA) and PUSCH, PUCCH, or SRS transmissions, and the UE selects a RACH opportunity (RO) 625. In such a case, N=2, and the UE can send PRACH (or msgA) in RACH opportunity 625 and send PUSCH, PUCCH, or SRS in uplink resources 610 because the N=2 gap threshold is not violated. In the second scenario, the UE determines different downlink reference timing between PRACH (or msgA) and PUSCH, PUCCH, or SRS transmissions, and the UE selects a RACH opportunity (RO) 625. In this example, N'=3 (or N=2 and Δ N =1)), and the gap between RACH opportunities 625 is less than 3 symbols, and thus the UE does not send PRACH and PUSCH / PUCCH / SRS.

[0124] According to the third scenario, the UE determines different downlink reference timings between PRACH (or msgA) and PUSCH, PUCCH or SRS transmissions, and the UE selects RACH timing (RO) 620. In this example, N'=3 (or N=2 and Δ N =1)), and the gap between RACH opportunities 620 is greater than 3 symbols, and thus the UE sends PRACH in the RACH opportunities 620 and sends PUSCH / PUCCH / SRS in the uplink resources 610.

[0125] As about Figure 5 As described, the UE may apply TRP specific PRACH timing. For PRACH / msgA PUSCH and PUSCH / PUCCH / SRS associated with the same TRP or CORESETPoolIndex value, the same downlink reference timing (and the same timing advance offset) shall be used. For PRACH / msgA PUSCH and PUSCH / PUCCH / SRS associated with different TRP or CORESETPoolIndex values, different downlink reference timing may be used. Similar to the description of Fig. 6A As described, when PRACH / msgA is associated with different TRPs, a new gap between PRACH / msgA PUSCH and PUSCH / PUCCH / SRS and a gap between SSB and PRACH / msgA PUSCH may be introduced, as described with respect to Figure 6B as described.

[0126] Therefore, when PRACH / msgA and PUSCH / PUCCH / SRS are associated with different CORSETPoolIndex values, a gap threshold N or N+Δ may be used or applied. N . When PRACH / msgA and PUSCH / PUCCH / SRS are associated with the same CORESETPoolIndex value, a gap threshold N may be used or applied. That is, for single-cell operation or for operation with carrier aggregation in the same frequency band, if PRACH / msgA PUSCH and PUSCH / PUCCH / SRS are associated with the same CORESETPoolIndex value, the UE transmits PRACH / msgA PUSCH and PUSCH / PUCCH / SRS when the gap between the first symbol or the last symbol of a PRACH transmission in a first slot is not separated from the last symbol or the first symbol of a PUSCH / PUCCH / SRS transmission (e.g., uplink transmission) in a second slot, respectively, by less than N symbols. Furthermore, for single-cell operation or for operation with carrier aggregation in the same frequency band, if PRACH / msgA PUSCH and PUSCH / PUCCH / SRS are associated with different CORESETPoolIndex values, the gap between the first symbol or the last symbol of a PRACH transmission that is not in the same slot or that is not in the first slot of the UE is separated from the last symbol or the first symbol of a PUSCH / PUCCH / SRS transmission in the second slot, respectively, by less than N′ or N+Δ N This rule (e.g., new slot configuration and time slot consideration) may be applied when simultaneous transmission between PRACH / msgAPUSCH and PUSCH / PUCCH / SRS across different CORESETPoolIndex values ​​is not supported.

[0127] Therefore, in Fig. 6AIn the example, if the PRACH / msgA and uplink resources (e.g., PUSCH / PUCCH / SRS) of the RACH opportunity 625 are associated with the same CORSETPoolIndex value, the gap is equal to 2 symbols, and thus the UE can send PRACH in the RACH opportunity 625 and send PUSCH / PUCCH / SRS in the uplink resources 610. However, if the PRACH / msgA and uplink resources of the RACH opportunity 625 are associated with different CORESETPoolIndex values, the gap is less than three symbols (e.g., N'=3 or N=2 and ΔN=1), and the UE does not send PRACH in the RACH opportunity 625 and does not send PUSCH / PUCCH / SRS in the uplink resources 610. In another example, if the PRACH / msgA and the uplink resource of the RACH opportunity 620 are associated with different CORESETPoolIndex values, the gap is greater than three symbols (e.g., N'=3 or N=2 and ΔN=1), and the UE may send the PRACH in the RACH opportunity 620 and send the PUSCH / PUCCH / SRS in the uplink resource 610. Describing whether a RACH opportunity (e.g., RACH opportunity 620) is valid by considering whether the uplink transmission and the RACH opportunity are in the same time slot or whether the distance between the RACH opportunity and the uplink transmission is less than the gap threshold Fig. 6A However, it should be understood that these techniques are applicable to consider the validity of PUSCH opportunities (transmission of PUSCH for msgA) related to uplink transmissions (e.g., PUSCH, PUSCH or SRS).

[0128] Figure 6B An example of a timing diagram 602 for supporting downlink reference timing determination for a physical random access channel in multi-transmission reception point communications according to one or more aspects of the present disclosure is illustrated. The timing diagram 602 may be provided by Figure 1 The described UE 115 and / or network entity 105 implements. More specifically, the UE 115 may implement the timing diagram 602 to determine whether to send a PRACH transmission or a msgA PUSCH transmission when operating in mDCI and mTRP modes, and / or to determine whether a PRACH opportunity or a PUSCH opportunity is valid.

[0129] As described herein, the UE may determine to use a PRACH / msgA PUSCH reference timing that is the same as the reference timing detected from the SSB associated with the CORESETPoolIndex value or that is different from the CORESETPoolIndex value associated with the SSB. That is, the UE may use the downlink reference timing of the PRACH / msgA associated with the CORESETPoolIndex value that is different from the downlink reference timing of the CORESETPoolIndex value used for the detected SSB. In such a case, a new gap value N for the gap between the SSB and the PRACH / msgA PUSCH may be applied. gap ' or Δ gap To determine whether the determined PRACH opportunity is valid.

[0130] According to the first option, the new value N gap 'For the gap between SSB and PRACH / msgA PUSCH. Apply and / or configure N for each SCS gap If the reference timing of PRACH / msgA PUSCH is the earlier reference timing of the two reference timings, then N gap 'Less than N gap , where N gap If the reference timing of PRACH / msgA PUSCH is the later reference timing of the two reference timings, then N gap 'Greater than N gap , where N gap is the existing gap.

[0131] According to the second option, the new additional gap value Δ gap Applicable to the existing gap N between SSB and PRACH / msgA PUSCH gap In this example, Δ gap If the reference timing of PRACH / msgAPUSCH is an earlier reference timing, then Δ N If the reference timing of PRACH / msgA PUSCH is the later reference timing, then Δ N Is positive.

[0132] The UE may apply any of these new values ​​to determine whether a PRACH opportunity is valid. If the downlink reference timing associated with a given CORESETPoolIndex value is used for PRACH / msgA PUSCH, and if an SSB is associated with the same CORESETPoolIndex value, then a PRACH opportunity in a PRACH slot starts at least N times after the last SS / PBCH block received symbol if it does not precede an SS / PBCH block in the PRACH slot. gap It is valid when there are N symbols. gap If the downlink reference timing associated with a first CORESETPoolIndex value is used for PRACH / msgA PUSCH and if the SSB is associated with a second CORESETPoolIndex value different from the first CORESETPoolIndex value, then the PRACH opportunity in the PRACH slot does not precede an SS / PBCH block in the PRACH slot and starts at least N after the last SS / PBCH block received symbol. gap ' or N' gap +Δ gap It is valid when there are N symbols. gap ' or N' gap +Δ gap It's a new gap.

[0133] about Figure 6B The application of these clearance rules is illustrated in Figure 6B According to the first example, the determined downlink reference timing for PRACH / msgA is associated with CORSETPoolIndex 0, and SSB 635 is also associated with CORESETPoolIndex 0. In this example, N gap =2, and the gap 630 between the SSB 635 and the RACH opportunity 640 is two symbols. Therefore, the RACH opportunity 640 is valid. In the second example, the determined downlink reference timing for PRACH / msgA is associated with CORESETPoolIndex0, and the SSB 635 is associated with CORESETPoolIndex1. In this example, the UE applies a new gap configuration, such as N gap '=1, or N gap =2,Δ gap = -1. The gap 630 between the SSB 635 and the RACH opportunity 640 is two symbols, which is greater than one symbol and causes the RACH opportunity 640 to be valid.

[0134] As about Figure 5As described, the UE may determine to use a PRACH or msgA PUSCH transmission (for mTRP) associated with different downlink reference timing and timing advance values, such that the PRACH transmission is associated with a different CORESETPoolIndex value. In such a case, when the SS B and PRACH / msgA PUSCH are associated with different CORESETPoolIndex values, a new gap configuration (N gap ' or N gap +Δ gap ). Therefore, the UE considers whether the RACH timing is valid. gap =2 and N gap = 3 and SSB 635 is associated with CORSETPoolIndex 0, if PRACH is associated with the first CORESETPoolIndex value (eg, the same value as SSB 635) so that N gap , then RACH opportunity 640 is valid. In the same example, if PRACH is associated with a second CORESETPoolIndex value such that N gap ', then the RACH opportunity 640 is invalid (eg, the UE will not use the RACH opportunity 640). Describing whether a RACH opportunity (eg, RACH opportunity 640) is valid by considering whether the distance between the RACH opportunity and the SSB is less than the gap threshold Figure 6B However, it should be understood that these techniques are applicable to consider the effectiveness of PUSCH timing (transmission of PUSCH for msgA) related to SSB.

[0135] Figure 7 An example of a process flow 700 for supporting downlink reference timing determination for a physical random access channel in multi-transmission reception point communications according to one or more aspects of the present disclosure is illustrated. The process flow 700 includes a UE 115-c, a TRP 305-c, and a TRP 305-d. The UE 115-c may be a TRP 305-d. Figures 1 to 3 The example of UE 115 described above, and TRP 305-c and TRP 305-d may be as described with respect to Figure 3 The TRP 305 may be associated with the same network entity 105 as described above. Figure 1In the following description of process flow 700, operations between UE 115-c and TRPs 305-c and 305-d may be sent in an order different from the example order shown, or the operations may be performed in a different order or at a different time. Some operations may also be omitted from process flow 700, and other operations may be added to process flow 700.

[0136] At 705, UE 115-c may receive control signaling (from one or both of TRPs 305-c and 305-d) indicating two control resource set pool index values ​​(CORESETPoolIndex values) in an active bandwidth portion of at least one serving cell. Two timing advance groups, each associated with a timing advance offset, are configured for the serving cell.

[0137] At 710, the UE 115-c may determine two downlink reference timings for uplink transmissions within a serving cell. The two timing advance groups are each associated with a respective timing advance offset and configured for the serving cell. Each of the two downlink reference timings may be associated with a respective timing advance group of the two timing advance groups.

[0138] At 715, the UE 115-c may determine the uplink timing of a random access preamble for a physical random access channel (PRACH) or a message A for a physical uplink shared channel (PUSCH) based at least in part on at least one of the two timing advance offsets, at least one of the two downlink reference timings, or any combination thereof. In some examples, the UE 115-c may determine a single uplink timing for the PRACH or the message A PUSCH based on a single downlink reference timing value and a single timing advance offset value. In some examples, the UE 115-c may identify a single timing advance offset based on a single downlink reference timing value in the two downlink reference timings. The UE 115-c may also select a single downlink reference timing value in the two downlink references as the earliest downlink reference timing in time in the two downlink reference timings. In other cases, the UE 115-c selects a single downlink reference timing value in the two downlink references based on one of the two control resource pool index values ​​(e.g., the lowest value) in the two downlink reference timings. In other cases, the UE 115 - c may select the earliest uplink timing for the uplink timing determined using a corresponding set of downlink reference values ​​and timing advance offset values.

[0139] In some examples, at 720, the UE 115-c determines whether a RACH opportunity or a PUSCH opportunity for a random access procedure is valid. To determine whether these opportunities are valid, the UE can determine an applicable time gap threshold between the SSB and the RACH opportunity or the PUSCH opportunity and between the RACH opportunity or the PUSCH opportunity and the uplink resources used to carry PUSCH, PUCCH, or SRS.

[0140] The determination of the time gap threshold (in symbols) between the uplink resource and the PRACH opportunity and the PUSCH opportunity for message A may be based on whether the uplink resource is associated with a reference timing and timing advance offset different from the PRACH opportunity or the PUSCH opportunity for message A, or based on whether the uplink resource is associated with a control resource set pool index different from the control resource set pool index associated with the PRACH opportunity or the PUSCH opportunity for message A. If the gap between the RACH opportunity or the PUSCH opportunity for message A and the uplink resource is less than the determined time gap, the UE may refrain from transmitting using the uplink resource and the PRACH opportunity or the PUSCH opportunity. The UE may also refrain from transmitting in the same time slot when the PRACH opportunity or the message A PUSCH opportunity and the uplink resource are associated with different downlink reference timing and / or different timing advance offset values, or when the PRACH opportunity or the message A PUSCH opportunity and the uplink resource are associated with different control resource set index values.

[0141] Determination of a time gap threshold between an SSB opportunity and a PRACH opportunity or a PUSCH opportunity for message A may be based at least in part on whether the SSB and the PRACH opportunity or the PUSCH opportunity for message A are associated with different control resource set pool index values. If the gap between the SSB and the PRACH opportunity or the PUSCH opportunity for message A is less than the determined time gap, the UE may determine that the PRACH opportunity or the PUSCH opportunity for message A is invalid and refrain from transmitting in the PRACH opportunity or the PUSCH opportunity for message A.

[0142] At 715, as part of the random access procedure at 725, the UE 115-c may send a random access preamble in a valid PRACH opportunity or send message A in a valid PUSCH opportunity based on the determined uplink timing. At 730, as part of the random access procedure at 725, the UE 115-c and one or both of the TRPs 305-c and 305-d may exchange random access messages.

[0143] At 725, the UE 115-c may receive mDCI from the TRP 305-c (e.g., in response to a random access procedure), and at 730, the UE 115-c may receive mDCI from the TRP 305-d. At 735, the UE 115-c may send one or more uplink signals to the TRP 305-c based on the received mDCI (e.g., scheduling information in the mDCI). At 740, the UE 115-c may send one or more uplink signals to the TRP 305-d based on the mDCI.

[0144] Figure 8 A block diagram 800 of a device 805 supporting downlink reference timing determination for a physical random access channel in multi-transmission-reception-point communications according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of a UE 115 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0145] The receiver 810 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to downlink reference timing determination for physical random access channels in multi-transmission reception point communications). The information may be delivered to other components of the device 805. The receiver 810 may utilize a single antenna or a collection of multiple antennas.

[0146] The transmitter 815 may provide means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to downlink reference timing determination for physical random access channels in multi-transmission reception point communications), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 815 may be co-located with the receiver 810 in a transceiver module. The transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0147] The communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of downlink reference timing determination for a physical random access channel in multi-transmission-reception-point communications as described herein. For example, the communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0148] In some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof that is configured to or otherwise supports components for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0149] Additionally or alternatively, in some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0150] In some examples, the communication manager 820 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 810, the transmitter 815, or both. For example, the communication manager 820 can receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.

[0151] According to an example as disclosed herein, the communication manager 820 may support wireless communication at a UE. For example, the communication manager 820 may be configured to or otherwise support a component for determining two downlink reference timings for uplink transmissions within a serving cell, wherein two timing advance groups each associated with a corresponding timing advance offset are configured for the serving cell, and wherein each of the two downlink reference timings is associated with a corresponding timing advance group in the two timing advance groups. The communication manager 820 may be configured to or otherwise support a component for determining an uplink timing of a random access preamble for a physical random access channel (PRACH) or a message A for a physical uplink shared channel (PUSCH) based on at least one of the two timing advance offsets, at least one of the two downlink reference timings, or any combination thereof. The communication manager 820 may be configured to or otherwise support a component for sending a random access preamble in a valid PRACH opportunity or sending a message A in a valid PUSCH opportunity according to the determined uplink timing as part of a random access procedure.

[0152] By including or configuring a communication manager 820 according to the examples described herein, the device 805 (e.g., a processor controlling or otherwise coupled with the receiver 810, the transmitter 815, the communication manager 820, or a combination thereof) can support techniques for reducing processing by supporting the UE to determine a timing advance value for a random access preamble when the UE operates according to mDCI and MTRP modes.

[0153] Fig. 9 A block diagram 900 of a device 905 supporting downlink reference timing determination for a physical random access channel in multi-transmission-reception-point communications according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the device 805 or UE 115 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0154] The receiver 910 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to downlink reference timing determination for physical random access channels in multi-transmission reception point communications). The information may be delivered to other components of the device 905. The receiver 910 may utilize a single antenna or a collection of multiple antennas.

[0155] The transmitter 915 may provide means for transmitting signals generated by other components of the device 905. For example, the transmitter 915 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to downlink reference timing determination for physical random access channels in multi-transmission reception point communications), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 915 may be co-located with the receiver 910 in a transceiver module. The transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0156] The device 905 or its various components may be examples of components for performing various aspects of downlink reference timing determination for a physical random access channel in multi-transmission reception point communication as described herein. For example, the communication manager 920 may include a downlink reference timing component 930, an uplink timing manager 935, a random access manager 940, or any combination thereof. The communication manager 920 may be an example of various aspects of the communication manager 820 as described herein. In some examples, the communication manager 920 or its various components may be configured to use or otherwise cooperate with the receiver 910, the transmitter 915, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0157] According to examples as disclosed herein, the communication manager 920 may support wireless communications at the UE. The downlink reference timing component 930 may be configured to or otherwise support components for determining two downlink reference timings for uplink transmissions within a serving cell, wherein two timing advance groups each associated with a corresponding timing advance offset are configured for the serving cell, and wherein each of the two downlink reference timings is associated with a corresponding timing advance group in the two timing advance groups. The uplink timing manager 935 may be configured to or otherwise support components for determining uplink timing of a random access preamble for a physical random access channel (PRACH) or a message A for a physical uplink shared channel (PUSCH) based on at least one of the two timing advance offsets, at least one of the two downlink reference timings, or any combination thereof. The random access manager 940 may be configured to or otherwise support components for sending a random access preamble in a valid PRACH opportunity or sending message A in a valid PUSCH opportunity according to the determined uplink timing as part of a random access procedure.

[0158] Fig.10A block diagram 1000 of a communication manager 1020 supporting downlink reference timing determination for a physical random access channel in multi-transmission reception point communications is shown in accordance with one or more aspects of the present disclosure. The communication manager 1020 may be an example of aspects of the communication manager 820, the communication manager 920, or both as described herein. The communication manager 1020 or its various components may be examples of components for performing various aspects of downlink reference timing determination for a physical random access channel in multi-transmission reception point communications as described herein. For example, the communication manager 1020 may include a control resource set manager 1025, a downlink reference timing component 1030, an uplink timing manager 1035, a random access manager 1040, a time slot manager 1045, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0159] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a UE. The control resource set manager 1025 may be configured to or otherwise support a component for receiving control signaling indicating two control resource set pool index values ​​in an active bandwidth portion of at least one serving cell, wherein two timing advance groups, each associated with a timing advance offset, are configured for the serving cell. The downlink reference timing component 1030 may be configured to or otherwise support a component for determining two downlink reference timings for uplink transmissions within the serving cell, wherein two timing advance groups, each associated with a corresponding timing advance offset, are configured for the serving cell, and wherein each of the two downlink reference timings is associated with a corresponding timing advance group in the two timing advance groups. The uplink timing manager 1035 may be configured to or otherwise support a component for determining an uplink timing of a random access preamble for a physical random access channel (PRACH) or a message A for a physical uplink shared channel (PUSCH) based on at least one of the two timing advance offsets, at least one of the two downlink reference timings, or any combination thereof. The random access manager 1040 may be configured or otherwise support components for sending a random access preamble in a valid PRACH opportunity or sending message A in a valid PUSCH opportunity according to the determined uplink timing as part of the random access procedure.

[0160] In some examples, the uplink timing manager 1035 may be configured to or otherwise support components for determining a single uplink timing for a random access preamble or message A based on a single downlink reference timing of two downlink reference timings and a single timing advance offset of two timing advance offsets.

[0161] In some examples, uplink timing manager 1035 may be configured or otherwise support components for identifying a single timing advance offset based on a single downlink reference timing. In some examples, downlink reference timing component 1030 may be configured or otherwise support components for selecting a single downlink reference timing from two downlink reference timings based on the single downlink reference timing being the earliest in time of the two downlink reference timings.

[0162] In some examples, uplink timing manager 1035 may be configured or otherwise support components for identifying a single timing advance offset based on a single downlink reference timing. In some examples, downlink reference timing component 1030 may be configured or otherwise support components for selecting a single downlink reference timing from two downlink reference timings based on the single downlink reference timing corresponding to a selected one of two control resource set pool index values ​​for an active bandwidth portion of a serving cell.

[0163] In some examples, the downlink reference timing component 1030 may be configured to or otherwise support components for selecting the single downlink reference timing from the two downlink reference timings and selecting the single timing advance offset from the two timing advance offsets based on the uplink timing associated with the single downlink reference timing and the single timing advance offset being earlier than another uplink timing associated with the other downlink reference timing of the two downlink reference timings and the other timing advance offset of the two timing advance offsets.

[0164] In some examples, the time gap manager 1045 may be configured to or otherwise support components for determining a time gap in a symbol between an uplink resource and a valid PRACH opportunity or a valid PUSCH opportunity based on the uplink resource being associated with a downlink reference timing that is different from a single downlink reference timing, a timing advance offset that is different from a single timing advance offset, or both.

[0165] In some examples, the time slot manager 1045 may be configured to or otherwise support a component for suppressing use of the uplink resource for transmission in the same time slot as the PRACH opportunity or the PUSCH opportunity based on the uplink resource being associated with different downlink reference timing or different timing advance offsets, or when a gap between a symbol of the PRACH opportunity or the PUSCH opportunity and a symbol of the uplink resource is less than a determined time gap based at least in part on the PRACH opportunity or the PUSCH opportunity and the uplink resource being associated with the same control resource set pool index value.

[0166] In some examples, the time slot manager 1045 may be configured to or otherwise support components for suppressing use of the uplink resource for transmission in the same time slot as the PRACH opportunity or the PUSCH opportunity based on identifying that simultaneous transmission using the PRACH opportunity or the PUSCH opportunity and the uplink resource allocated to the UE is not supported, or when a gap between a symbol of the PRACH opportunity or the PUSCH opportunity and a symbol of the uplink resource is less than a determined time gap based at least in part on the PRACH opportunity or the PUSCH opportunity and the uplink resource, both of which are associated with different control resource set pool index values.

[0167] In some examples, the time gap manager 1045 may be configured to or otherwise support components for determining a time gap in a symbol between a synchronization signal block opportunity and a valid PRACH opportunity or a valid PUSCH opportunity based on the synchronization signal block opportunity being associated with a first control resource set pool index value and the valid PRACH opportunity or the valid PUSCH opportunity being associated with a second control resource set pool index value different from the first control resource set.

[0168] In some examples, the random access manager 1040 may be configured to or otherwise support components for determining that the first PRACH opportunity is a valid PRACH opportunity or the first PUSCH opportunity is a valid PUSCH opportunity based on the first PRACH opportunity or the first PUSCH opportunity being at or after a synchronization signal block opportunity and at least a threshold number of symbols after a previously received synchronization signal block.

[0169] In some examples, the random access manager 1040 may be configured to or otherwise support components for determining a threshold number of symbols based on whether valid PRACH opportunities or valid PUSCH opportunities and synchronization signal block opportunities are both associated with the same control resource set pool index value.

[0170] In some examples, the uplink timing manager 1035 may be configured to or otherwise support components for determining the downlink reference timing based on a control resource pool index value associated with the downlink reference timing in two downlink reference timings being associated with the same control resource pool index value associated with a valid PRACH timing or a valid PUSCH timing, or being associated with a timing advance group in two timing advance groups corresponding to the downlink reference timing and being associated with the same control resource pool index value as the valid PRACH timing or the valid PUSCH timing, wherein the uplink timing is determined at least in part based on the determined downlink reference timing.

[0171] In some examples, the time slot manager 1045 may be configured to or otherwise support a component for suppressing use of the uplink resource for transmission in the same time slot as the PRACH opportunity or the PUSCH opportunity based on the PRACH opportunity or the PUSCH opportunity and the uplink resource being associated with the same control resource set pool index value, or when the gap between the symbol of the PRACH opportunity or the PUSCH opportunity and the symbol of the uplink resource is less than the time gap.

[0172] In some examples, the time slot manager 1045 may be configured to or otherwise support a component for suppressing use of the uplink resource for transmission in the same time slot as the PRACH opportunity or the PUSCH opportunity based on the PRACH opportunity or the PUSCH opportunity and the uplink resource being associated with different control resource set pool index values, or when the gap between the symbol of the PRACH opportunity or the PUSCH opportunity and the symbol of the uplink resource is less than the time gap.

[0173] In some examples, the time gap manager 1045 may be configured to or otherwise support components for determining a first value of a time gap between a synchronization signal block opportunity and a first control resource pool index value and a valid PRACH opportunity or a valid PUSCH opportunity being associated with a second control resource pool index different from the first control resource pool index value, the first value of the time gap being different from a second value of the time gap associated with the following situation: the synchronization signal block opportunity and the valid PRACH opportunity or the PUSCH opportunity are associated with the same control resource pool index value.

[0174] Fig.11 A diagram of a system 1100 including a device 1105 supporting downlink reference timing determination for a physical random access channel in multi-transmission-reception-point communication according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of a device 805, a device 905, or a UE 115 as described herein, or include components thereof. The device 1105 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1105 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1120, an input / output (I / O) controller 1110, a transceiver 1115, an antenna 1125, a memory 1130, a code 1135, and a processor 1140. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1145).

[0175] I / O controller 1110 can manage input signals and output signals of device 1105. I / O controller 1110 can also manage peripheral devices that are not integrated into device 1105. In some cases, I / O controller 1110 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1110 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 1110 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1110 may be implemented as part of a processor (such as processor 1140). In some cases, a user may interact with device 1105 via I / O controller 1110 or via hardware components controlled by I / O controller 1110.

[0176] In some cases, the device 1105 may include a single antenna 1125. However, in some other cases, the device 1105 may have more than one antenna 1125, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1115 may communicate bidirectionally via one or more antennas 1125, a wired or wireless link, as described herein. For example, the transceiver 1115 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1115 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1125 for transmission; and demodulating packets received from one or more antennas 1125. The transceiver 1115 or the transceiver 1115 and one or more antennas 1125 may be examples of transmitters 815, transmitters 915, receivers 810, receivers 910, or any combination thereof or components thereof as described herein.

[0177] The memory 1130 may include random access memory (RAM) and read-only memory (ROM). The memory 1130 may store computer-readable, computer-executable code 1135 including instructions that, when executed by the processor 1140, cause the device 1105 to perform various functions described herein. The code 1135 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 1135 may not be directly executable by the processor 1140, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 1130 may also include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0178] The processor 1140 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1140 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1140. The processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1130) to enable the device 1105 to perform various functions (e.g., functions or tasks that support downlink reference timing determination for a physical random access channel in multi-transmission and reception point communications). For example, the device 1105 or a component of the device 1105 may include a processor 1140 and a memory 1130 coupled to or coupled to the processor 1140, and the processor 1140 and the memory 1130 are configured to perform the various functions described herein.

[0179] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a UE. For example, the communication manager 1120 may be configured to or otherwise support components for determining two downlink reference timings for uplink transmissions within a serving cell, wherein two timing advance groups each associated with a corresponding timing advance offset are configured for the serving cell, and wherein each of the two downlink reference timings is associated with a corresponding timing advance group in the two timing advance groups. The communication manager 1120 may be configured to or otherwise support components for determining uplink timing of a random access preamble for a physical random access channel (PRACH) or a message A for a physical uplink shared channel (PUSCH) based on at least one of the two timing advance offsets, at least one of the two downlink reference timings, or any combination thereof. The communication manager 1120 may be configured to or otherwise support components for sending a random access preamble in a valid PRACH opportunity or sending a message A in a valid PUSCH opportunity according to the determined uplink timing as part of a random access procedure.

[0180] By including or configuring the communication manager 1120 according to examples as described herein, the device 1105 may support techniques for reducing processing by supporting the UE in determining a timing advance value for a random access preamble when the UE operates according to mDCI and MTRP modes.

[0181] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1115, one or more antennas 1125, or any combination thereof. For example, the communication manager 1120 may be configured to receive or transmit messages or other signaling as described herein via the transceiver 1115. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by the processor 1140, the memory 1130, the code 1135, or any combination thereof. For example, the code 1135 may include instructions that may be executed by the processor 1140 to cause the device 1105 to perform various aspects of downlink reference timing determination for a physical random access channel in multi-transmission reception point communications as described herein, or the processor 1140 and the memory 1130 may be otherwise configured to perform or support such operations.

[0182] Fig.12 A flowchart illustrating a method 1200 for supporting downlink reference timing determination for a physical random access channel in multi-transmission-reception-point communications according to one or more aspects of the present disclosure is shown. The operations of the method 1200 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1200 may be implemented by a UE or a component thereof as described herein. Figures 1 to 11 The described UE 115 performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0183] At 1205, the method may include determining two downlink reference timings for uplink transmissions within a serving cell, wherein two timing advance groups, each associated with a respective timing advance offset, are configured for the serving cell, and wherein each of the two downlink reference timings is associated with a respective timing advance group of the two timing advance groups. The operations of 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed by Fig.10 1130, the downlink reference timing component 1030 described herein may be performed. Additionally or alternatively, means for performing 1205 may, but need not necessarily include, for example, an antenna 1125, a transceiver 1115, a communication manager 1120, a memory 1130 (including code 1135), a processor 1140, and / or a bus 1145.

[0184] At 1210, the method may include determining an uplink timing of a random access preamble for a physical random access channel (PRACH) or a message A for a physical uplink shared channel (PUSCH) based at least in part on at least one of the two timing advance offsets, at least one of the two downlink reference timings, or any combination thereof. The operations of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed by reference to Fig.10 The uplink timing manager 1035 described herein is executed. Additionally or alternatively, the means for executing 1210 may, but need not necessarily include, for example, an antenna 1125, a transceiver 1115, a communication manager 1120, a memory 1130 (including code 1135), a processor 1140, and / or a bus 1145.

[0185] At 1215, the method may include, as part of a random access procedure, sending a random access preamble in a valid PRACH opportunity or sending message A in a valid PUSCH opportunity according to the determined uplink timing. The operations of 1215 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1215 may be performed as described in reference to Fig.10 Additionally or alternatively, the means for performing 1215 may, but need not necessarily include, for example, an antenna 1125, a transceiver 1115, a communication manager 1120, a memory 1130 (including code 1135), a processor 1140, and / or a bus 1145.

[0186] Fig.13 A flowchart illustrating a method 1300 for supporting downlink reference timing determination for a physical random access channel in multi-transmission-reception-point communications according to one or more aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE or a component thereof as described herein. Figures 1 to 11 The described UE 115 performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0187] At 1310, the method may include determining two downlink reference timings for uplink transmissions within a serving cell, wherein two timing advance groups, each associated with a respective timing advance offset, are configured for the serving cell, and wherein each of the two downlink reference timings is associated with a respective timing advance group of the two timing advance groups. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed by Fig.10The described downlink reference timing component 1030 is performed. Additionally or alternatively, the means for performing 1310 may, but need not necessarily include, for example, an antenna 1125, a transceiver 1115, a communication manager 1120, a memory 1130 (including code 1135), a processor 1140, and / or a bus 1145.

[0188] At 1315, the method may include determining a single uplink timing for a random access preamble or message A based on a single downlink reference timing of the two downlink reference timings and a single timing advance offset of the two timing advance offsets. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed by Fig.10 The uplink timing manager 1035 described herein is executed. Additionally or alternatively, the means for executing 1315 may, but need not necessarily include, for example, an antenna 1125, a transceiver 1115, a communication manager 1120, a memory 1130 (including code 1135), a processor 1140, and / or a bus 1145.

[0189] At 1320, the method may include sending a preamble in a valid PRACH opportunity of a random access procedure or sending a message A in a valid PUSCH opportunity according to the determined single uplink timing. The operations of 1320 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1320 may be performed as described in reference to Fig.10 Additionally or alternatively, the means for performing 1320 may, but need not necessarily include, for example, antenna 1125, transceiver 1115, communication manager 1120, memory qq30 (including code 1135), processor 1140, and / or bus 1145.

[0190] Fig.14 A flowchart illustrating a method 1400 for supporting downlink reference timing determination for a physical random access channel in multi-transmission reception point communications according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described herein. Figures 1 to 11 The described UE 115 performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0191] At 1410, the method may include determining two downlink reference timings for uplink transmissions within a serving cell, wherein two timing advance groups, each associated with a respective timing advance offset, are configured for the serving cell, and wherein each of the two downlink reference timings is associated with a respective timing advance group of the two timing advance groups. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed by Fig.10 The described downlink reference timing component 1030 is performed. Additionally or alternatively, the means for performing 1410 may, but need not necessarily include, for example, an antenna 1125, a transceiver 1115, a communication manager 1120, a memory 1130 (including code 1135), a processor 1140, and / or a bus 1145.

[0192] At 1415, the method may include determining an uplink timing of a random access preamble for a physical random access channel (PRACH) or a message A for a physical uplink shared channel (PUSCH) based at least in part on at least one of the two timing advance offsets, at least one of the two downlink reference timings, or any combination thereof. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed by as described in reference to Fig.10 The uplink timing manager 1035 described herein is executed. Additionally or alternatively, the means for executing 1415 may, but need not necessarily include, for example, an antenna 1125, a transceiver 1115, a communication manager 1120, a memory 1130 (including code 1135), a processor 1140, and / or a bus 1145.

[0193] At 1420, the method may include determining a time gap in a symbol between the uplink resource and a valid PRACH opportunity or a valid PUSCH opportunity based at least in part on the uplink resource being associated with a downlink reference timing different from a single downlink reference timing, a timing advance offset different from a single timing advance offset, or both. The operations of 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed by as described in reference to Fig.10 Additionally or alternatively, means for performing 1420 may, but need not necessarily include, for example, antenna 1125, transceiver 1115, communication manager 1120, memory qq30 (including code 1135), processor 1140, and / or bus 1145.

[0194] At 1425, the method may include, as part of a random access procedure, sending a random access preamble in a valid PRACH opportunity or sending message A in a valid PUSCH opportunity according to the determined uplink timing. The operations of 1425 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1425 may be performed as described in reference to Fig.10 Additionally or alternatively, means for performing 1425 may, but need not necessarily include, for example, antenna 1125, transceiver 1115, communication manager 1120, memory qq30 (including code 1135), processor 1140, and / or bus 1145.

[0195] The following provides an overview of various aspects of the disclosure:

[0196] Aspect 1: A method for wireless communication at a UE, the method comprising: determining two downlink reference timings for uplink transmission within a serving cell, wherein two timing advance groups each associated with a corresponding timing advance offset are configured for the serving cell, and wherein each of the two downlink reference timings is associated with a corresponding timing advance group in the two timing advance groups; determining an uplink timing of a random access preamble for a physical random access channel (PRACH) or a message A for a PUSCH based at least in part on at least one of the two timing advance offsets, at least one of the two downlink reference timings, or any combination thereof; and as part of a random access procedure, sending the random access preamble in a valid PRACH opportunity or sending the message A in a valid PUSCH opportunity according to the determined uplink timing.

[0197] Aspect 2: A method according to Aspect 1, wherein determining the uplink timing further comprises: determining a single uplink timing for the random access preamble or the message A based on a single downlink reference timing among the two downlink reference timings and a single timing advance offset among the two timing advance offsets.

[0198] Aspect 3: According to the method described in Aspect 2, the method also includes: identifying the single timing advance offset based at least in part on the single downlink reference timing; and selecting the single downlink reference timing from the two downlink reference timings based at least in part on the single downlink reference timing being the earliest in time among the two downlink reference timings.

[0199] Aspect 4: According to the method described in any one of Aspects 2 to 4, the method further includes: identifying the single timing advance offset based at least in part on the single downlink reference timing; and selecting the single downlink reference timing from the two downlink reference timings based at least in part on the single downlink reference timing corresponding to a selected control resource pool index value of two control resource pool index values ​​for the active bandwidth part of the service cell.

[0200] Aspect 5: According to the method described in any one of Aspects 2 to 4, the method also includes: selecting the single downlink reference timing from the two downlink reference timings and selecting the single timing advance offset from the two timing advance offsets, at least in part based on the uplink timing associated with the single downlink reference timing and the single timing advance offset being earlier than another uplink timing associated with another downlink reference timing in the two downlink reference timings and another timing advance offset in the two timing advance offsets.

[0201] Aspect 6: According to the method described in any one of Aspects 2 to 5, the method also includes: determining the time gap in the symbol between the uplink resource and the valid PRACH opportunity or the valid PUSCH opportunity based at least in part on the uplink resource being associated with a downlink reference timing different from the single downlink reference timing, a timing advance offset different from the single timing advance offset, or both.

[0202] Aspect 7: According to the method described in Aspect 6, the method also includes: suppressing the use of the uplink resource for transmission in the same time slot as the PRACH opportunity or the PUSCH opportunity, at least in part based on the uplink resource being associated with different downlink reference timing or different timing advance offsets, or when the gap between the symbol of the PRACH opportunity or the PUSCH opportunity and the symbol of the uplink resource is less than the determined time gap.

[0203] Aspect 8: According to the method described in any one of Aspects 6 to 7, the method further includes: suppressing the use of the uplink resource for transmission in the same time slot as the PRACH opportunity or the PUSCH opportunity based at least in part on identifying that the simultaneous transmission of the PRACH opportunity or the PUSCH opportunity and the uplink resource allocated to the UE is not supported, or when the gap between the symbol of the PRACH opportunity or the PUSCH opportunity and the symbol of the uplink resource is less than the determined time gap.

[0204] Aspect 9: According to the method described in any one of Aspects 1 to 8, the method further includes: determining the time gap in the symbol between the synchronization signal block opportunity and the valid PRACH opportunity or the valid PUSCH opportunity based at least in part on the fact that the synchronization signal block opportunity is associated with a first control resource pool index value and the valid PRACH opportunity or the valid PUSCH opportunity is associated with a second control resource pool index value different from the first control resource pool index value.

[0205] Aspect 10: According to the method described in any one of Aspects 1 to 9, the method further includes: determining that the first PRACH opportunity is the valid PRACH opportunity or the first PUSCH opportunity is the valid PUSCH opportunity based at least in part on the first PRACH opportunity or the first PUSCH opportunity being at or after a synchronization signal block opportunity and at least a threshold number of symbols after a previously received synchronization signal block.

[0206] Aspect 11: According to the method according to Aspect 10, the method also includes: determining the threshold number of symbols based at least in part on whether the valid PRACH opportunity or the valid PUSCH opportunity and the synchronization signal block opportunity are both associated with the same control resource set pool index value.

[0207] Aspect 12: A method according to any one of Aspects 1 to 11, wherein determining the uplink timing further comprises: determining the downlink reference timing based at least in part on a control resource pool index value associated with the downlink reference timing in the two downlink reference timings being associated with the same control resource pool index value associated with the valid PRACH timing or the valid PUSCH timing, or being associated with the timing advance group corresponding to the downlink reference timing in the two timing advance groups, and being associated with the control resource pool index value that is the same as the valid PRACH timing or the valid PUSCH timing, wherein the uplink timing is determined at least in part based on the determined downlink reference timing.

[0208] Aspect 13: According to the method described in Aspect 12, the method further includes: suppressing the use of the uplink resource for transmission in the same time slot as the PRACH opportunity or the PUSCH opportunity, based at least in part on the fact that the PRACH opportunity or the PUSCH opportunity and the uplink resource are both associated with the same control resource pool index value, or when the gap between the symbol of the PRACH opportunity or the PUSCH opportunity and the symbol of the uplink resource is smaller than the time gap between the PRACH opportunity or the PUSCH opportunity and the uplink resource, based at least in part on the fact that the PRACH opportunity or the PUSCH opportunity and the uplink resource are both associated with the same control resource pool index value.

[0209] Aspect 14: According to the method described in Aspect 12, the method further includes: suppressing the use of the uplink resource for transmission in the same time slot as the PRACH opportunity or the PUSCH opportunity, based at least in part on the fact that the PRACH opportunity or the PUSCH opportunity and the uplink resource are both associated with different control resource pool index values, or when the gap between the symbol of the PRACH opportunity or the PUSCH opportunity and the symbol of the uplink resource is smaller than the time gap between the PRACH opportunity or the PUSCH opportunity and the uplink resource, based at least in part on the fact that the PRACH opportunity or the PUSCH opportunity and the uplink resource are both associated with different control resource pool index values.

[0210] Aspect 15: A method according to any one of Aspects 12 to 14, wherein the method further comprises: determining a first value of a time gap between the synchronization signal block opportunity and the valid PRACH opportunity or the valid PUSCH opportunity based at least in part on the fact that the synchronization signal block opportunity is associated with a first control resource pool index value and the valid PRACH opportunity or the valid PUSCH opportunity is associated with a second control resource pool index value different from the first control resource pool index value, the first value of the time gap being different from the second value of the time gap associated with the following situation: the synchronization signal block opportunity and the valid PRACH opportunity or PUSCH opportunity are associated with the same control resource pool index value.

[0211] Aspect 16: An apparatus for performing wireless communications at a UE, the apparatus comprising: a memory; a transceiver; and at least one processor of the UE, the at least one processor being coupled to the memory and the transceiver and configured to perform a method according to any one of Aspects 1 to 15.

[0212] Aspect 17: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing the method according to any one of aspects 1 to 15.

[0213] Aspect 18: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 15.

[0214] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0215] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0216] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0217] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0218] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using one or more instructions or codes of a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0219] Computer-readable medium includes both non-transient computer storage medium and communication medium, and the communication medium includes any medium that promotes the transfer of computer programs from one location to another location.Non-transient storage medium can be any available medium that can be accessed by a general or special computer.By way of example and not limitation, non-transient computer-readable medium may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code components and any other non-transient medium that can be accessed by a general or special computer or a general or special processor in the form of an instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from a website, a server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disks and optical disks include CDs, laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, and optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0220] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0221] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include parsing, retrieving, selecting, choosing, establishing, and other such similar actions.

[0222] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second or other subsequent reference labels.

[0223] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The detailed description includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0224] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), the method comprising: determining two downlink reference timings for uplink transmissions within a serving cell, wherein two timing advance groups, each associated with a respective timing advance offset, are configured for the serving cell, and wherein each of the two downlink reference timings is associated with a respective timing advance group of the two timing advance groups; determining an uplink timing of a random access preamble for a physical random access channel (PRACH) or a message A for a physical uplink shared channel (PUSCH) based at least in part on at least one of the two timing advance offsets, at least one of the two downlink reference timings, or any combination thereof; and As part of the random access procedure, the random access preamble is sent in a valid PRACH opportunity or the message A is sent in a valid PUSCH opportunity according to the determined uplink timing.

2. The method of claim 1 , wherein determining the uplink timing further comprises: A single uplink timing for the random access preamble or the message A is determined based on a single downlink reference timing of the two downlink reference timings and a single timing advance offset of the two timing advance offsets.

3. The method according to claim 2, further comprising: identifying the single timing advance offset based at least in part on the single downlink reference timing; as well as The single downlink reference timing is selected from the two downlink reference timings based at least in part on the single downlink reference timing being earliest in time among the two downlink reference timings.

4. The method according to claim 2, further comprising: identifying the single timing advance offset based at least in part on the single downlink reference timing; as well as The single downlink reference timing is selected from the two downlink reference timings based at least in part on the single downlink reference timing corresponding to a selected one of the two control resource set pool index values ​​for the active bandwidth portion of the serving cell.

5. The method according to claim 2, further comprising: The single downlink reference timing is selected from the two downlink reference timings and the single timing advance offset is selected from the two timing advance offsets based at least in part on the uplink timing associated with the single downlink reference timing and the single timing advance offset being earlier than another uplink timing associated with another downlink reference timing of the two downlink reference timings and the other timing advance offset of the two timing advance offsets.

6. The method according to claim 2, further comprising: A time gap in a symbol between the uplink resource and the valid PRACH opportunity or the valid PUSCH opportunity is determined based at least in part on the uplink resource being associated with a downlink reference timing different from the single downlink reference timing, a timing advance offset different from the single timing advance offset, or both.

7. The method according to claim 6, further comprising: Suppressing use of the uplink resource for transmission in the same time slot as the PRACH opportunity or the PUSCH opportunity based at least in part on the uplink resource being associated with a different downlink reference timing or a different timing advance offset, or when a gap between a symbol of a PRACH opportunity or a PUSCH opportunity and a symbol of the uplink resource is less than a determined time gap.

8. The method according to claim 6, further comprising: Suppressing transmission using the uplink resource in the same time slot as the PRACH opportunity or the PUSCH opportunity based at least in part on identifying that simultaneous transmission using a PRACH opportunity or a PUSCH opportunity and the uplink resource allocated to the UE is not supported, or when a gap between a symbol of the PRACH opportunity or the PUSCH opportunity and a symbol of the uplink resource is less than a determined time gap.

9. The method according to claim 1, further comprising: Based at least in part on the fact that the synchronization signal block opportunity is associated with a first control resource pool index value and the valid PRACH opportunity or the valid PUSCH opportunity is associated with a second control resource pool index value different from the first control resource pool index value, a time gap in a symbol between the synchronization signal block opportunity and the valid PRACH opportunity or the valid PUSCH opportunity is determined.

10. The method according to claim 1, further comprising: Determining that the first PRACH opportunity is the valid PRACH opportunity or the first PUSCH opportunity is the valid PUSCH opportunity based at least in part on the first PRACH opportunity or the first PUSCH opportunity being at or after a synchronization signal block opportunity and at least a threshold number of symbols after a previously received synchronization signal block.

11. The method according to claim 10, further comprising: The threshold number of symbols is determined based at least in part on whether the valid PRACH opportunity or the valid PUSCH opportunity and the synchronization signal block opportunity are both associated with a same control resource set pool index value.

12. The method of claim 1 , wherein determining the uplink timing further comprises: The downlink reference timing is determined at least in part based on the control resource pool index value associated with the downlink reference timing in the two downlink reference timings being associated with the same control resource pool index value associated with the valid PRACH timing or the valid PUSCH timing, or being associated with the timing advance group corresponding to the downlink reference timing in the two timing advance groups and being associated with the same control resource pool index value as the valid PRACH timing or the valid PUSCH timing, wherein the uplink timing is determined at least in part based on the determined downlink reference timing.

13. The method according to claim 12, further comprising: At least partially based on the fact that the PRACH opportunity or the PUSCH opportunity and the uplink resource are both associated with the same control resource set pool index value, or when the gap between the symbol of the PRACH opportunity or the PUSCH opportunity and the symbol of the uplink resource is smaller than the time gap between the PRACH opportunity or the PUSCH opportunity and the uplink resource, both of which are associated with the same control resource set pool index value, suppressing the use of the uplink resource for transmission in the same time slot as the PRACH opportunity or the PUSCH opportunity.

14. The method according to claim 12, further comprising: At least partially based on the fact that the PRACH opportunity or the PUSCH opportunity and the uplink resource are both associated with different control resource pool index values, or when the gap between the symbol of the PRACH opportunity or the PUSCH opportunity and the symbol of the uplink resource is smaller than the time gap between the PRACH opportunity or the PUSCH opportunity and the uplink resource, which are both associated with different control resource pool index values, suppressing the use of the uplink resource for transmission in the same time slot as the PRACH opportunity or the PUSCH opportunity.

15. The method according to claim 12, wherein the method further comprises: At least in part based on the fact that the synchronization signal block opportunity is associated with a first control resource pool index value and the valid PRACH opportunity or the valid PUSCH opportunity is associated with a second control resource pool index value different from the first control resource pool index value, determine a first value of the time gap between the synchronization signal block opportunity and the valid PRACH opportunity or the valid PUSCH opportunity, the first value of the time gap being different from the second value of the time gap associated with the following situation: the synchronization signal block opportunity and the valid PRACH opportunity or PUSCH opportunity are associated with the same control resource pool index value.

16. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; Transceiver; and At least one processor of a user equipment (UE), the at least one processor coupled with the memory and the transceiver and configured to: determining two downlink reference timings for uplink transmissions within a serving cell, wherein two timing advance groups, each associated with a respective timing advance offset, are configured for the serving cell, and wherein each of the two downlink reference timings is associated with a respective timing advance group of the two timing advance groups; determining uplink timing of a random access preamble for a physical random access channel (PRACH) or a message A for a physical uplink shared channel (PUSCH) based at least in part on at least one of the two timing advance offsets, at least one of the two downlink reference timings, or any combination thereof; and as part of a random access procedure, sending the random access preamble in a valid PRACH opportunity or sending the message A in a valid PUSCH opportunity via the transceiver according to the determined uplink timing.

17. The device according to claim 16, wherein: To determine the uplink timing, the at least one processor is further configured to: A single uplink timing for the random access preamble or the message A is determined based on a single downlink reference timing of the two downlink reference timings and a single timing advance offset of the two timing advance offsets.

18. The apparatus of claim 17, wherein the at least one processor is further configured to: identifying the single timing advance offset based at least in part on the single downlink reference timing; and The single downlink reference timing is selected from the two downlink reference timings based at least in part on the single downlink reference timing being earliest in time among the two downlink reference timings.

19. The apparatus of claim 17, wherein the at least one processor is further configured to: identifying the single timing advance offset based at least in part on the single downlink reference timing; and The single downlink reference timing is selected from the two downlink reference timings based at least in part on the single downlink reference timing corresponding to a selected one of the two control resource set pool index values ​​for the active bandwidth portion of the serving cell.

20. The apparatus of claim 17, wherein the at least one processor is further configured to: The single downlink reference timing is selected from the two downlink reference timings and the single timing advance offset is selected from the two timing advance offsets based at least in part on the uplink timing associated with the single downlink reference timing and the single timing advance offset being earlier than another uplink timing associated with another downlink reference timing of the two downlink reference timings and the other timing advance offset of the two timing advance offsets.

21. The apparatus of claim 17, wherein the at least one processor is further configured to: A time gap in a symbol between the uplink resource and the valid PRACH opportunity or the valid PUSCH opportunity is determined based at least in part on the uplink resource being associated with a downlink reference timing different from the single downlink reference timing, a timing advance offset different from the single timing advance offset, or both.

22. The apparatus of claim 21 , wherein the at least one processor is further configured to: Suppressing use of the uplink resource for transmission in the same time slot as the PRACH opportunity or the PUSCH opportunity based at least in part on the uplink resource being associated with a different downlink reference timing or a different timing advance offset, or when a gap between a symbol of a PRACH opportunity or a PUSCH opportunity and a symbol of the uplink resource is less than a determined time gap.

23. The apparatus of claim 21 , wherein the at least one processor is further configured to: Suppressing transmission using the uplink resource in the same time slot as the PRACH opportunity or the PUSCH opportunity based at least in part on identifying that simultaneous transmission using a PRACH opportunity or a PUSCH opportunity and the uplink resource allocated to the UE is not supported, or when a gap between a symbol of the PRACH opportunity or the PUSCH opportunity and a symbol of the uplink resource is less than a determined time gap.

24. The apparatus of claim 16, wherein the at least one processor is further configured to: Based at least in part on the fact that the synchronization signal block opportunity is associated with a first control resource pool index value and the valid PRACH opportunity or the valid PUSCH opportunity is associated with a second control resource pool index value different from the first control resource pool index value, a time gap in a symbol between the synchronization signal block opportunity and the valid PRACH opportunity or the valid PUSCH opportunity is determined.

25. The apparatus of claim 16, wherein the at least one processor is further configured to: Determining that the first PRACH opportunity is the valid PRACH opportunity or the first PUSCH opportunity is the valid PUSCH opportunity based at least in part on the first PRACH opportunity or the first PUSCH opportunity being at or after a synchronization signal block opportunity and at least a threshold number of symbols after a previously received synchronization signal block.

26. The apparatus of claim 25, wherein the at least one processor is further configured to: The threshold number of symbols is determined based at least in part on whether the valid PRACH opportunity or the valid PUSCH opportunity and the synchronization signal block opportunity are both associated with a same control resource set pool index.

27. The device according to claim 16, wherein: To determine the uplink timing, the at least one processor is further configured to: The downlink reference timing is determined at least in part based on the control resource pool index value associated with the downlink reference timing in the two downlink reference timings being associated with the same control resource pool index value associated with the valid PRACH timing or the valid PUSCH timing, or being associated with the timing advance group corresponding to the downlink reference timing in the two timing advance groups and being associated with the same control resource pool index value as the valid PRACH timing or the valid PUSCH timing, wherein the uplink timing is determined at least in part based on the determined downlink reference timing.

28. The apparatus of claim 27, wherein the at least one processor is further configured to: At least partially based on the fact that the PRACH opportunity or the PUSCH opportunity and the uplink resource are both associated with the same control resource set pool index value, or when the gap between the symbol of the PRACH opportunity or the PUSCH opportunity and the symbol of the uplink resource is smaller than the time gap between the PRACH opportunity or the PUSCH opportunity and the uplink resource, both of which are associated with the same control resource set pool index value, suppressing the use of the uplink resource for transmission in the same time slot as the PRACH opportunity or the PUSCH opportunity.

29. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: means for determining two downlink reference timings for uplink transmissions within a serving cell, wherein two timing advance groups, each associated with a respective timing advance offset, are configured for the serving cell, and wherein each of the two downlink reference timings is associated with a respective timing advance group of the two timing advance groups; means for determining uplink timing of a random access preamble for a physical random access channel (PRACH) or a message A for a physical uplink shared channel (PUSCH) based at least in part on at least one of the two timing advance offsets, at least one of the two downlink reference timings, or any combination thereof; and means for sending the random access preamble in a valid PRACH opportunity or sending the message A in a valid PUSCH opportunity according to the determined uplink timing as part of a random access procedure.

30. A non-transitory computer-readable medium storing code for wireless communication at a user equipment (UE), the code comprising instructions executable by a processor to: determining two downlink reference timings for uplink transmissions within a serving cell, wherein two timing advance groups, each associated with a respective timing advance offset, are configured for the serving cell, and wherein each of the two downlink reference timings is associated with a respective timing advance group of the two timing advance groups; determining an uplink timing of a random access preamble for a physical random access channel (PRACH) or a message A for a physical uplink shared channel (PUSCH) based at least in part on at least one of the two timing advance offsets, at least one of the two downlink reference timings, or any combination thereof; and As part of the random access procedure, the random access preamble is sent in a valid PRACH opportunity or the message A is sent in a valid PUSCH opportunity according to the determined uplink timing.

Images