Physical random access channel transmission based on downlink control information

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) can receive a physical downlink control channel (PDCCH) order downlink control information (DCI) including an indicator to indicate whether a transmit (Tx) beam of a physical random access channel (PRACH) transmission is based at least in part on an associated sounding reference signal (SRS) Tx beam or a receive (Rx) beam based at least in part on an associated synchronization signal block (SSB) or channel state information reference signal (CSI-RS). The UE can transmit the PRACH transmission based at least in part on the indicator. Numerous other aspects are described.

Description

Technical Field

[0001] All aspects of this disclosure relate to wireless communication in general, and more particularly to techniques, apparatus and methods for transmitting physical random access channels based at least in part on downlink control information. Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of services, including voice, text, messaging, video, data, and / or other services. Services may include unicast, multicast, and / or broadcast services, etc. Typical wireless communication systems employ multiple access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (e.g., time-domain resources, frequency-domain resources, spatial-domain resources, and / or device transmit power, etc.). Examples of such multiple access RATs include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0003] The aforementioned Multiple Access RATs have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, national, regional, or global level. An example telecommunications standard is New Radio (NR). NR (also known as 5G) is part of the continuous evolution of mobile broadband announced by the 3rd Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) can be designed to better support the Internet of Things (IoT) and reduced-capacity device deployments, industrial connectivity, millimeter-wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployments, sidelinks and other device-to-device direct communication technologies (e.g., cellular vehicle-to-everything (CV2X) communications), massive MIMO, decomposed network architectures and network topology expansion, multi-subscriber implementations, high-precision positioning and / or radio frequency (RF) sensing, and more. As the demand for mobile broadband access continues to grow, further improvements to NR can be implemented, and other radio access technologies (such as 6G) can be introduced to further advance mobile broadband evolution. Summary of the Invention

[0004] In some specific implementations, an apparatus for wireless communication at a user equipment (UE) includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the UE to: receive Physical Downlink Control Channel (PDCCH) command downlink control information (DCI) including an indicator for indicating whether a transmit (Tx) beam of a Physical Random Access Channel (PRACH) transmission is at least partially based on a Tx beam of an associated sounding reference signal (SRS) or at least partially based on an associated synchronization block (SSB) or channel state information reference signal (CSI-RS); and transmit the PRACH transmission at least partially based on the indicator.

[0005] In some specific implementations, an apparatus for wireless communication at a UE includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the UE to: receive a configuration including a first preamble receive target power value and a second preamble receive target power value; and, depending on whether the PRACH transmission is directed to an uplink transmit-receive point (TRP) or a downlink TRP, transmit the PRACH transmission using the first preamble receive target power value or the second preamble receive target power value.

[0006] In some specific implementations, an apparatus for wireless communication at a UE includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the UE to: receive a PDCCH command DCI including a Transmission Configuration Indicator (TCI) field, the TCI field indicating a TCI state for PRACH transmission via the PDCCH command; and transmit the PRACH transmission via the PDCCH command based at least in part on the TCI field.

[0007] In some specific implementations, an apparatus for wireless communication at a network node includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the network node to: transmit a PDCCH command DCI including an indicator for indicating whether the Tx beam of the PRACH transmission is at least partially based on the Tx beam of an associated SRS or at least partially based on the Rx beam of an associated SSB or CSI-RS; and receive the PRACH transmission at least partially based on the indicator.

[0008] In some specific implementations, an apparatus for wireless communication at a network node includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the network node to: transmit a configuration including a first preamble receive target power value and a second preamble receive target power value; and receive the PRACH transmission using the first preamble receive target power value or the second preamble receive target power value, depending on whether the PRACH transmission is destined for an uplink-only TRP or a downlink-only TRP.

[0009] In some specific implementations, an apparatus for wireless communication at a network node includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the network node to: transmit a PDCCH command DCI including a TCI field, the TCI field indicating a TCI state for a PRACH transmission via the PDCCH command; and receive the PRACH transmission via the PDCCH command based at least in part on the TCI field.

[0010] In some specific implementations, a method of wireless communication performed by a UE includes: receiving a PDCCH command DCI including an indicator for indicating whether the Tx beam of the PRACH transmission is at least partially based on the Tx beam of the associated SRS or at least partially based on the Rx beam of the associated SSB or CSI-RS; and transmitting the PRACH transmission at least partially based on the indicator.

[0011] In some specific implementations, a wireless communication method performed by a UE includes: receiving a configuration including a first preamble receive target power value and a second preamble receive target power value; and, depending on whether the PRACH transmission is directed to an uplink-only TRP or a downlink-only TRP, transmitting the PRACH transmission using the first preamble receive target power value or the second preamble receive target power value.

[0012] In some specific implementations, a method of wireless communication performed by a UE includes: receiving a PDCCH command DCI including a TCI field, the TCI field being used to indicate the TCI status for PRACH transmission via the PDCCH command; and transmitting the PRACH transmission via the PDCCH command based at least in part on the TCI field.

[0013] In some specific implementations, a method of wireless communication performed by a network node includes: transmitting a PDCCH command DCI including an indicator for indicating whether the Tx beam of the PRACH transmission is at least partially based on the Tx beam of the associated SRS or at least partially based on the Rx beam of the associated SSB or CSI-RS; and receiving the PRACH transmission at least partially based on the indicator.

[0014] In some specific implementations, a method of wireless communication performed by a network node includes: transmitting a configuration including a first preamble receive target power value and a second preamble receive target power value; and receiving the PRACH transmission using the first preamble receive target power value or the second preamble receive target power value, depending on whether the PRACH transmission is destined for an uplink-only TRP or a downlink TRP.

[0015] In some specific implementations, a method of wireless communication performed by a network node includes: transmitting a PDCCH command DCI including a TCI field, the TCI field being used to indicate the TCI status for PRACH transmission via the PDCCH command; and receiving the PRACH transmission via the PDCCH command based at least in part on the TCI field.

[0016] In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: receive a PDCCH command DCI including an indicator indicating whether the Tx beam of a PRACH transmission is at least partially based on the Tx beam of an associated SRS or at least partially based on the Rx beam of an associated SSB or CSI-RS; and transmit the PRACH transmission at least partially based on the indicator.

[0017] In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: receive a configuration including a first preamble receive target power value and a second preamble receive target power value; and, depending on whether the PRACH transmission is directed to an uplink-only TRP or a downlink-only TRP, transmit the PRACH transmission using the first preamble receive target power value or the second preamble receive target power value.

[0018] In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: receive a PDCCH command DCI including a TCI field indicating a TCI state for PRACH transmission via the PDCCH command; and transmit the PRACH transmission via the PDCCH command based at least in part on the TCI field.

[0019] In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a network node, cause the network node to: transmit a PDCCH command DCI including an indicator indicating whether the Tx beam of the PRACH transmission is at least partially based on the Tx beam of the associated SRS or at least partially based on the Rx beam of the associated SSB or CSI-RS; and receive the PRACH transmission at least partially based on the indicator.

[0020] In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a network node, cause the network node to: transmit a configuration including a first preamble receive target power value and a second preamble receive target power value; and, depending on whether the PRACH transmission is destined for an uplink-only TRP or a downlink-only TRP, receive the PRACH transmission using the first preamble receive target power value or the second preamble receive target power value.

[0021] In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a network node, cause the network node to: send a PDCCH command DCI including a TCI field indicating the TCI status for a PRACH transmission via the PDCCH command; and receive the PRACH transmission via the PDCCH command based at least in part on the TCI field.

[0022] In some specific implementations, an apparatus for wireless communication includes: a component for receiving a PDCCH command DCI including an indicator for indicating whether a Tx beam of a PRACH transmission is at least partially based on a Tx beam of an associated SRS or at least partially based on an Rx beam of an associated SSB or CSI-RS; and a component for transmitting the PRACH transmission at least partially based on the indicator.

[0023] In some specific implementations, an apparatus for wireless communication includes: components for receiving a configuration including a first preamble receive target power value and a second preamble receive target power value; and components for transmitting the PRACH transmission using the first preamble receive target power value or the second preamble receive target power value, depending on whether the PRACH transmission is destined for an uplink-only TRP or a downlink TRP.

[0024] In some specific implementations, an apparatus for wireless communication includes: a component for receiving a PDCCH command DCI including a TCI field for indicating a TCI status for PRACH transmission via the PDCCH command; and a component for transmitting the PRACH transmission via the PDCCH command based at least in part on the TCI field.

[0025] In some specific implementations, an apparatus for wireless communication includes: a component for transmitting a PDCCH command DCI including an indicator for indicating whether the Tx beam of the PRACH transmission is at least partially based on the Tx beam of an associated SRS or at least partially based on the Rx beam of an associated SSB or CSI-RS; and a component for receiving the PRACH transmission at least partially based on the indicator.

[0026] In some specific implementations, an apparatus for wireless communication includes: components for transmitting a configuration including a first preamble receive target power value and a second preamble receive target power value; and components for receiving the PRACH transmission using the first preamble receive target power value or the second preamble receive target power value, depending on whether the PRACH transmission is destined for an uplink-only TRP or a downlink TRP.

[0027] In some specific implementations, an apparatus for wireless communication includes: a component for transmitting a PDCCH command DCI including a TCI field for indicating a TCI state for a PRACH transmission via the PDCCH command; and a component for receiving the PRACH transmission via the PDCCH command based at least in part on the TCI field.

[0028] Various aspects of this disclosure may be implemented or be implemented as described in whole by or embodied in the methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices and / or processing systems as fully described in the specification and drawings and illustrated in the specification and drawings.

[0029] The preceding paragraphs of this section have broadly summarized some aspects of this disclosure. These and additional aspects and their associated advantages will be described below. The disclosed aspects can serve as the basis for modifying or designing other aspects for performing the same or similar purposes of this disclosure. Such equivalent aspects do not depart from the scope of the appended claims. The characteristics of the aspects disclosed herein, their organization and operation, and their associated advantages will be better understood from the following description taken in conjunction with the accompanying drawings. Attached Figure Description

[0030] The accompanying drawings illustrate some aspects of this disclosure but do not limit its scope, as other aspects can be achieved through this description. Each drawing in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Identical or similar reference numerals in different drawings may identify identical or similar elements.

[0031] Figure 1 This is a diagram illustrating an example of a wireless network according to the present disclosure.

[0032] Figure 2 This is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0033] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0034] Figure 4 This is a diagram illustrating an example of a dense uplink deployment according to this disclosure.

[0035] Figures 5 to 7 This is a diagram illustrating an example of transmission associated with a Physical Random Access Channel (PRACH) based at least in part on downlink control information (DCI) according to this disclosure.

[0036] Figures 8 to 13 This is a diagram illustrating an example process associated with PRACH transmission based at least in part on DCI, according to this disclosure.

[0037] Figures 14 to 15 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0038] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, aspects of this disclosure may be embodied in many different forms and should not be construed as limited to any specific aspect illustrated or described with reference to the drawings or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of protection of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, various combinations or numbers of aspects set forth herein may be used to implement an apparatus or a practice. Furthermore, the scope of this disclosure is intended to cover apparatuses having structures and / or functionalities other than those available for practicing the various aspects of this disclosure set forth herein, or methods practiced using these other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0039] Various methods, operations, apparatuses, and techniques will now be presented with reference to them. These methods, operations, apparatuses, and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0040] Uplink dense deployment can be used to improve uplink coverage and / or capacity. Uplink receive (Rx) points (e.g., uplink-only nodes) receive uplink signals and / or uplink channels from user equipment (UE). Downlink signals and / or downlink channels transmitted from network nodes may originate from different nodes (e.g., macro nodes, central nodes, serving cells, or serving base stations). Uplink Rx points can be connected to network nodes via backhaul links. Uplink dense deployment can help reduce uplink path loss, which can be helpful when uplink coverage is a bottleneck. Since uplink Rx points do not transmit any downlink signals, uplink dense deployment can help in terms of deployment cost and / or complexity. Uplink Rx points simply receive uplink signals and, with or without processing, transmit them to network nodes.

[0041] In Supplemental Uplink (SUL), a UE can be configured using two uplink carriers that share a downlink carrier for the same serving cell, and uplink transmissions on these two uplink carriers can be asynchronous. For example, for Time Division Duplex (TDD) bands and SUL, the UE can transmit uplink signals on the TDD band (e.g., a non-supplemental uplink band) or on the SUL carrier. For both uplink dense deployment and SUL, the downlink beam and uplink beam can be separate.

[0042] During a two-step or four-step RACH process, for the transmission of Message 1 (MSG 1) (PRACH), the transmission of Message 3 (MSG 3), or the payload of Message A (MSG A), the same spatial domain transmit filter (Tx beam) used for the reception (Rx beam) of the corresponding Synchronization Signal Block (SSB) or Channel State Information Reference Signal (CSI-RS) can be used. The mapping between the SSB (or the CSI-RS resource in the case of Contention-Free Random Access (CFRA)) and the RACH timing can be defined, at least in part, based on the configuration and rule set in the specification. However, the Tx beam for PRACH transmission may not be explicitly defined / specified in the specification. For UEs with beam correspondence, the UE can follow the Rx beam of the associated SSB / CSI-RS. For UEs without beam correspondence, multiple Tx beams around the Rx beam corresponding to the SSB / CSI-RS can be tried for multiple PRACH attempts.

[0043] In cases of dense uplink deployment (e.g., where the uplink TRP differs from the downlink TRP) or when the uplink carrier is SUL (e.g., in FR2 or higher frequency bands), the Rx beam of the downlink signal / channel (corresponding to the downlink TRP / carrier) should not be used for the Tx beam of PRACH transmission when PRACH transmission will also be received by the uplink TRP / carrier. Identifying and indicating a good Tx beam for PRACH transmission can be difficult in the case of a random access procedure for initial access. However, in other cases where the UE is in RRC connection mode (e.g., for random access due to beam fault recovery (BFR) or PDCCH command), a previous uplink beam scan (e.g., SRS) may have already occurred. In these cases, a good uplink beam for the Tx beam used for PRACH transmission (or MSG 3 transmission or MSG A payload) can be identified and indicated by the network node.

[0044] The Tx beam transmitted via PRACH toward the uplink TRP can be determined. To determine the Tx beam transmitted via PRACH toward the uplink TRP, the Tx beam transmitted via PRACH can be indicated in the PDCCH command DCI by pointing to the SRS resource identifier (ID), and some reserved bits in the PDCCH command DCI can be used to indicate the Tx beam transmitted via PRACH. However, when a field for SRS resource index indication (e.g., the SRS resource indication field) is introduced, the SSB / PBCH index field may still be needed to indicate the PRACH timing. In this case, the UE may not be able to distinguish whether the Tx beam transmitted via PRACH is at least partially based on the SRS Tx beam (e.g., indicated by the SRS resource indication field) or at least partially based on the associated SSB / CSI-RS Rx beam.

[0045] Various aspects generally involve PRACH transmission based at least partially on DCI. Some aspects more specifically involve PRACH transmission based at least partially on DCI in dense uplink deployments. In some examples, the UE may receive a PDCCH command DCI, including an indicator, from a network node associated with a dense uplink deployment where the uplink TRP differs from the downlink TRP. This indicator indicates whether the Tx beam of the PRACH transmission is based at least partially on the Tx beam of the associated SRS or at least partially on the Rx beam of the associated SSB or CSI-RS. The UE may transmit PRACH transmissions to the network node at least partially based on the indicator. The UE may transmit PRACH transmissions at least partially based on the Tx beam of the associated SRS. Alternatively, the UE may transmit PRACH transmissions at least partially based on the Rx beam of the associated SSB or CSI-RS. In other words, the UE can use the Tx beam to transmit PRACH, and the Tx beam can be associated with the Tx beam of the associated SRS, or the Tx beam can be associated with the Rx beam of the associated SSB or CSI-RS.

[0046] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to enable the UE to use an appropriate Tx beam for PRACH transmission by indicating whether the Tx beam of the PRACH transmission is at least partially based on the Tx beam of the associated SRS or at least partially based on the Rx beam of the associated SSB or CSI-RS. Indicators in the PDCCH command DCI allow the UE to distinguish whether the Tx beam of the PRACH transmission is at least partially based on the Tx beam of the SRS (e.g., indicated by the SRS resource indication field) or at least partially based on the Rx beam of the associated SSB or CSI-RS. Therefore, the UE can use an appropriate Tx beam, which increases the likelihood that the PRACH transmission will be successfully received by the network node. By increasing the likelihood of successful reception of the PRACH transmission, retransmission of the PRACH transmission can be eliminated, thereby saving network resources and reducing power consumption at the UE.

[0047] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables different wireless communication devices to communicate at the city, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution program released by the 3rd Generation Partnership Project (3GPP). 5G NR supports a variety of technologies and use cases, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).

[0048] With increasing demand for broadband access and the evolution of technologies supported by wireless communication networks, further technological improvements can be adopted or implemented in 5G NR or future RATs (such as 6G) to further advance the evolution of wireless communication for a variety of existing and new use cases and applications. Such technological improvements can be associated with new frequency band extensions, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, decomposed network architectures and network topology extensions, device aggregation, advanced duplex communication, sidelinks and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced-capacity (RedCap) UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, radio frequency (RF) sensing and / or artificial intelligence or machine learning (AI / ML), and more. Such technological improvements can support use cases such as wireless backhaul, wireless data centers, extended reality (XR) and metaverse applications, meta-services for supporting vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and collaborative manipulation, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and general coverage applications using off-ground and / or aerial platforms, etc. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0049] Figure 1 This is a diagram illustrating an example of a wireless communication network 100 according to the present disclosure. The wireless communication network 100 may be a 5G (or NR) network or a 6G network, or may include elements of a 5G (or NR) network or a 6G network, etc. The wireless communication network 100 may include a plurality of network nodes 110, shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. Network nodes 110 may support communication with a plurality of UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e).

[0050] Network nodes 110 and UEs 120 of wireless communication network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, frequency bands, carriers, and / or channels according to frequency or wavelength. For example, devices of wireless communication network 100 can communicate using one or more operating frequency bands. In some aspects, multiple wireless networks 100 can be deployed in a given geographical area. Each wireless communication network 100 can support a specific RAT (which may also be referred to as an air interface) and can operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include 4G RATs, 5G / NRRATs, and / or 6G RATs, etc. In some examples, when multiple RATs are deployed in a given geographical area, each RAT in that geographical area can operate on a different frequency to avoid interference with each other.

[0051] Various operating frequency bands have been defined as frequency ranges designated FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Although a portion of FR1 is greater than 6 GHz, in some documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Similarly, in some documents and articles, FR2 is often (interchangeably) referred to as the “millimeter wave” band, but this is different from the Very High Frequency (EHF) band (30 GHz to 300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are often referred to as the mid-band frequencies, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 into mid-band frequencies. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in mid-band frequencies. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in mid-band frequencies, within FR2, FR4, FR4-a, FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operation, 6G operation, and / or other RATs above 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 can implement dynamic spectrum sharing (DSS), where multiple RATs (e.g., 4G / LTE and 5G / NR) are implemented within a single frequency band using dynamic bandwidth allocation (e.g., based on user demand). It is conceivable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1 and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0052] Network node 110 may include one or more devices, components, or systems that enable communication between UE 120 and one or more devices, components, or systems of wireless communication network 100. Network node 110 may be, may include, or may be referred to as: NR network node, 5G network node, 6G network node, node B, eNB, gNB, access point (AP), transmit / receive point (TRP), mobility element, core, network entity, network element, network equipment, and / or another type of device, component, or system included in the radio access network (RAN).

[0053] Network node 110 may be implemented as a single physical node (e.g., a single physical structure) or as two or more physical nodes (e.g., two or more different physical structures). For example, network node 110 may be a device or system implementing a portion of a radio protocol stack, a device or system implementing a complete protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete protocol stack. For example, and as shown, network node 110 may be an aggregated network node (with an aggregated architecture), meaning that network node 110 can implement a complete radio protocol stack physically and logically integrated within a single node (e.g., a single physical structure) in the wireless communication network 100. For example, aggregated network node 110 may consist of a single standalone base station or a single TRP that uses a complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

[0054] Alternatively, and also as shown, network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 may use protocol stacks that are physically distributed and / or logically distributed across two or more nodes in the same or different geographic locations. For example, a decomposed network node may have a decomposed architecture. In some deployments, decomposed network node 110 may be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as network configurations compliant with the O-RAN Alliance), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling by decomposing base station functionality into multiple individually deployable units.

[0055] Network nodes 110 of wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). CUs may host one or more higher-layer control functions, such as Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, and / or Service Data Adaptation Protocol (SDAP) functions, etc. DUs may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and / or one or more higher physical (PHY) layers, at least in part, according to functional splits (such as those defined by 3GPP). In some examples, DUs may also host one or more low-PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, Physical Random Access Channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or low-PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, etc., according to functional splits (such as lower-layer functional splits). In this type of architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[0056] In some aspects, a single network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, network node 110 may include one or more near real-time (near RT) RAN Intelligent Controllers (RICs) and / or one or more non-real-time (non-RT) RICs. In some examples, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.

[0057] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for specific geographic areas. In 3GPP, the term "cell" can refer to the coverage area of ​​network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 can support one or more (e.g., three) cells. In some examples, network node 110 can provide communication coverage for macro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). The network node 110 used for a macro cell may be referred to as a macro network node. Network node 110 used for a picocell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of ​​the cell may move depending on the location of the associated mobile network node 110 (e.g., a train, satellite base station, drone, or NTN network node).

[0058] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Compared to other types of network nodes 110, the various types of network nodes 110 typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0059] In some examples, network node 110 may be, may include, or operate as a RU, TRP, or base station communicating with one or more UEs 120 via a radio access link (which may be referred to as a "Uu" link). The radio access link may include a downlink and an uplink. A "downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and an "uplink" (or "UL") refers to the communication direction from UE 120 to network node 110. Downlink channels may include one or more control channels and one or more data channels. Downlink control channels may be used to transmit downlink control information (DCI) (e.g., scheduling information, reference signals, and / or configuration information) from network node 110 to UE 120. Downlink data channels may be used to transmit downlink data (e.g., user data associated with UE 120) from network node 110 to UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCH), and downlink data channels may include one or more physical downlink shared channels (PDSCH). The uplink channel may similarly include one or more control channels and one or more data channels. The uplink control channel can be used to transmit uplink control information (UCI) from UE 120 to network node 110 (e.g., transmitting corresponding reference signals and / or feedback with one or more downlinks). The uplink data channel can be used to transmit uplink data (e.g., user data associated with UE 120) from UE 120 to network node 110. The uplink control channel may include one or more physical uplink control channels (PUCCH), and the uplink data channel may include one or more physical uplink shared channels (PUSCH). The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.

[0060] Downlink and uplink resources may include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial-domain resources (specific transmission directions and / or beam parameters). Frequency-domain resources in some bands may be subdivided into bandwidth portions (BWPs). A BWP may be a contiguous block of frequency-domain resources allocated to one or more UEs 120 (e.g., a contiguous block of resource blocks). UEs 120 may be configured using both uplink and downlink BWPs (where the uplink and downlink BWPs may be the same BWP or different BWPs). BWPs may be dynamically configured and / or reconfigured (e.g., by sending DCI configuration to one or more UEs 120 via network node 110), meaning that BWPs may be adjusted in real-time (or near real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of one or more UEs 120. This allows for more efficient use of available frequency domain resources in the wireless communication network 100, as fewer frequency domain resources can be allocated to the BWP for UE 120 (which reduces the number of frequency domain resources that UE 120 needs to monitor), thus allowing more frequency domain resources to be distributed across multiple UE 120s. Therefore, the BWP can also assist in the implementation of such UE 120s by facilitating the configuration of smaller bandwidths for communications performed by lower-capacity UE 120s.

[0061] As described above, in some aspects, the wireless communication network 100 may be an IAB network, may include an IAB network, or may be included in an IAB network. In an IAB network, at least one network node 110 is an anchor network node communicating with a core network. The anchor network node 110 may also be referred to as an IAB donor (or "IAB donor"). The anchor network node 110 may be connected to the core network via a wired backhaul link. For example, the Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, the anchor network node 110 may be connected to one or more devices in the core network that provide core access and mobility management functions (AMF). An IAB network typically also includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply IAB nodes (or "IAB-nodes"). Each non-anchor network node 110 can directly communicate with the anchor network node 110 via a wireless backhaul link to access the core network, or can indirectly communicate with the anchor network node 110 via one or more other non-anchor network nodes 110 and an associated wireless backhaul link forming a backhaul path to the core network. Some anchor network nodes 110 or other non-anchor network nodes 110 can also directly communicate with one or more UEs 120 via a wireless access link carrying access services. For example, network resources used for wireless communication (such as time resources, frequency resources, and / or spatial resources) can be shared between the access link and the backhaul link.

[0062] In some examples, any network node 110 relaying communication may be referred to as a relay network node, a relay station, or simply a repeater. A repeater may receive communications from an upstream station (e.g., another network node 110 or UE 120) and transmit communications to a downstream station (e.g., UE 120 or another network node 110). In this case, the wireless communication network 100 may include or be referred to as a "multi-hop network." Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. Additionally or alternatively, UE 120 can be a relay station capable of relaying transmissions to or from other UE 120s, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE, etc.

[0063] UE 120 may be physically distributed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, an access terminal, another terminal, a mobile station, or a subscriber unit, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. UE 120 may be, or may include, a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an XR device, a vehicle component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that can communicate via a wireless medium, or may be coupled to them.

[0064] UE 120 and / or network node 110 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs), and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. A group of processors that can be configured or configured to perform a set of functions may include a first processor that can be configured or configured to perform a first function in the set, and a second processor that can be configured or configured to perform a second function in the set, or may include the entire group of processors that are configured or configured to perform the set of functions.

[0065] The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuits, each of which may include tangible storage media such as random access memory (RAM) or read-only memory (ROM) or combinations thereof (all of which are generally referred to herein individually as "memory" or collectively as "memory" or "memory circuitry"). One or more of these memories may be coupled to one or more processors in the processor (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) and may store processor-executable code (such as software) individually or collectively, which, when executed by one or more processors in the processor, may configure one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors in the processor may be pre-configured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled to one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some embodiments, one or more processors of the processing system include or implement one or more modems among the modems. The processing system may also include, or be coupled to, multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas among multiple antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. UE 120 may be included or may be contained in a housing that houses components associated with UE 120, including the processing system.

[0066] Some UEs 120 may be considered Machine Type Communication (MTC) UEs, Evolved or Enhanced Machine Type Communication (eMTC) UEs, Further Enhanced eMTC (feMTC) UEs or Enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be collectively referred to as "MTC UEs". MTC UEs may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices may be, may include, or may be included in or coupled with the following: industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or lighting fixtures, etc. Some UEs 120 may be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider’s network (such as being included in or communicating with the wireless communication network 100).

[0067] Some UEs 120 can be categorized according to different categories associated with varying levels of complexity and / or capabilities. Category 1 UEs 120 facilitate large-scale IoT within the wireless communication network 100 and offer lower complexity and / or cost compared to Category 2 UEs 120. Category 2 UEs 120 may include mission-critical IoT devices capable of URLLC, enhanced mobile broadband (eMBB), and / or precise positioning within the wireless communication network 100, legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or premium UEs. Category 3 UEs 120 may possess intermediate-level complexity and / or capabilities (e.g., capabilities between Category 1 and Category 2 UEs 120). Category 3 UEs 120 may be referred to as reduced-capability UEs (“RedCap UEs”), intermediate-level UEs, NR lightweight UEs, and / or NR simplified UEs, etc. RedCap UEs bridge the gap in capabilities and complexity between NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or premium UEs. RedCap UEs can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UEs can support healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart city deployments, among others.

[0068] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communication through a network node 110 acting as an intermediary). As an example, UE 120a can directly send data, control information, or other signaling to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can send and receive sidelink communication using peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols. In some deployments and configurations, network node 110 may schedule and / or allocate resources for sidelink communication between UEs 120 in the wireless communication network 100. In some other deployments and configurations, UE 120 (instead of network node 110) may perform or cooperate with or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communication.

[0069] In various examples, in addition to half-duplex operation, some network nodes and UEs in the wireless communication network 100, including network node 110 and UE 120, can also be configured for full-duplex operation. Network node 110 or UE 120 operating in half-duplex mode can perform only one of transmission or reception during a specific time resource period (such as a specific time slot, symbol, or other time period). Half-duplex operation may involve time division duplex (TDD), where the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., the transmissions do not overlap in time). In contrast, network node 110 or UE 120 operating in full-duplex mode can transmit and receive communications concurrently (e.g., within the same time resource). By operating in full-duplex mode, network node 110 and / or UE 120 can generally increase the capacity of the network and radio access links. In some examples, full-duplex operation may involve frequency division duplex (FDD), in which network node 110 performs DL transmission in a first frequency band or on a first component carrier, and UE 120 performs transmission in a second frequency band or on a second component carrier, the second frequency band or the second component carrier being different from the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for UE 120 but not for network node 110. For example, UE 120 may simultaneously transmit UL to the first network node 110 and receive DL transmissions from the second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for network node 110 but not for UE 120. For example, network node 110 may simultaneously transmit DL to the first UE 120 and receive UL transmissions from the second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both network node 110 and UE 120.

[0070] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) using the same time and frequency resources. MIMO techniques typically utilize multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some RATs can employ advanced MIMO techniques such as mTRP operations (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).

[0071] In some aspects, the UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive a PDCCH command DCI including an indicator for indicating whether the Tx beam of the PRACH transmission is at least partially based on the Tx beam of the associated SRS or at least partially based on the Rx beam of the associated SSB or CSI-RS; and transmit the PRACH transmission at least partially based on the indicator. As described in more detail elsewhere herein, the communication manager 140 may receive a configuration including a first preamble receive target power value and a second preamble receive target power value; and transmit the PRACH transmission using either the first preamble receive target power value or the second preamble receive target power value, depending on whether the PRACH transmission is directed to an uplink-only TRP or a downlink TRP. As described in more detail elsewhere herein, the communication manager 140 may receive a PDCCH command DCI including a TCI field indicating the TCI status for PRACH transmission via the PDCCH command; and transmit PRACH transmission via the PDCCH command based at least in part on the TCI field. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0072] In some aspects, a network node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send a PDCCH command DCI including an indicator indicating whether the Tx beam of the PRACH transmission is at least partially based on the Tx beam of the associated SRS or at least partially based on the Rx beam of the associated SSB or CSI-RS; and receive the PRACH transmission at least partially based on the indicator. As described in more detail elsewhere herein, the communication manager 150 may send a configuration including a first preamble receive target power value and a second preamble receive target power value; and receive the PRACH transmission using either the first preamble receive target power value or the second preamble receive target power value, depending on whether the PRACH transmission is destined for an uplink-only TRP or a downlink TRP. As described in more detail elsewhere herein, the communication manager 150 may send a PDCCH command DCI including a TCI field indicating the TCI status for PRACH transmission via the PDCCH command; and receive PRACH transmissions via the PDCCH command based at least in part on the TCI field. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0073] As pointed out above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0074] Figure 2 This is a diagram illustrating communication between an example network node 110 and an example UE 120 in a wireless network according to the present disclosure.

[0075] like Figure 2 As shown, network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a to 232t, where t≥1), a set of antennas 234 (shown as 234a to 234v, where v≥1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, etc. In some configurations, one or a combination of antennas 234, modems 232, MIMO detectors 236, receive processors 238, transmit processors 214, and / or TX MIMO processors 216 may be included in the transceiver of network node 110. The transceiver may be under the control of and used by one or more processors (such as controller / processor 240), and in some respects, may perform aspects of the methods, procedures and / or operations described herein in conjunction with processor-readable code stored in memory 242. In some respects, network node 110 may include one or more interfaces, communication components and / or other components that facilitate communication with UE 120 or another network node.

[0076] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “a / the processor,” “a / the controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2 The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as a combination of references. Figure 2 Any one or more processors described herein. For example, one or more processors of network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0077] In some aspects, a single processor can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors can perform a first operation described as being performed by that one or more processors, and a second set of one or more processors can perform a second operation described as being performed by that one or more processors. The first set of processors and the second set of processors can be the same set of processors or can be different sets of processors. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as those in combination. Figure 2 The memory described. For example, an operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0078] For downlink communication from network node 110 to UE 120, transmitting processor 214 may receive data (“downlink data”) intended for use by UE 120 (or a set of UEs including UE 120) from data source 212 (such as a data pipeline or data queue). In some examples, transmitting processor 214 may select one or more MCSs for UE 120 based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process the data (e.g., including encoding the data) based on the MCS selected for UE 120 for transmission to UE 120 on the downlink, thereby generating data symbols. Transmitting processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and / or control symbols. The transmitting processor 214 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), or channel state information (CSI) reference signals (CSI-RS)) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).

[0079] The TX MIMO processor 216 can perform space processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., TA set of output symbol streams is provided to modem 232. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t may transmit the set of downlink signals (e.g., via a set of corresponding antennas 234) together. T (One downlink signal).

[0080] Downlink signals may include DCI communication, MAC control element (MAC-CE) communication, RRC communication, downlink reference signals, or another type of downlink communication. Downlink signals may be transmitted on the PDCCH, PDSCH, and / or on another downlink channel. Downlink signals may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in the wireless communication network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated through more robust error correction techniques.

[0081] For uplink communication from UE 120 to network node 110, the uplink signal from UE 120 may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected where applicable by MIMO detector 236 (e.g., Rx MIMO processor), and / or further processed by receiver processor 238 to obtain decoded data and / or control information. Receiver processor 238 may provide the decoded data to data sink 239 (which may be a data pipeline, data queue, and / or another type of data sink) and provide the decoded control information to processors such as controller / processor 240.

[0082] Network node 110 may use scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 120. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use for transmission and / or reception of communication with RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or configuration grant (CG) configuration for UE 120.

[0083] One or more of the following may be included in the RF chain of network node 110: transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, and / or controller / processor 240. The RF chain may include filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices for converting analog signals (such as those used for transmission or reception via an air interface) to digital signals (such as those used for processing by one or more processors of network node 110). In some aspects, the RF chain may be a transceiver of network node 110, or may be included in such a transceiver.

[0084] In some examples, network node 110 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to execute network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0085] UE 120 may include a collection of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a collection of modems 254 (shown as modems 254a to 254u, where u ≥ 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, etc. One or more components of UE 120 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 120. The transceiver may be under the control of and used by one or more processors (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 120 may include another interface, another communication component, and / or another component that facilitates communication with network node 110 and / or another UE 120.

[0086] For downlink communication from network node 110 to UE 120, the set of antennas 252 can receive downlink communication or signals from network node 110, and can receive the set of downlink signals (e.g., R Each received signal is provided to a set of modems 254. For example, each received signal may be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use the corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from the set of modems 254, may perform MIMO detection on the received symbols where applicable, and may provide the detected symbols. Receiver processor 258 may process (e.g., decode) the detected symbols, may provide the decoded data for UE 120 to data sink 260 (such as a data pipeline, data queue, and / or application executed on UE 120), and may provide the decoded control information and system information to controller / processor 280.

[0087] For uplink communication from UE 120 to network node 110, the transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 120) and control information from controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 110 or another UE). One or more parameters may include a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, a CQI parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of the RSRP parameter, RSSI parameter, RSRQ parameter, CQI parameter, TPC parameter, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0088] Transmit processor 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink sounding reference signal (SRS), and / or another type of reference signal. Symbols from transmit processor 264 can be pre-decoded by TX MIMO processor 266 where applicable, and further processed by a set of modems 254 (e.g., for DFT-s-OFDM or CP-OFDM). TX MIMO processor 266 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., ... U A set of output symbol streams is provided to modem 254. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0089] Modems 254a to 254u can transmit uplink signal sets (e.g., via a set of corresponding antennas 252) R One uplink signal or UUplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals may be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals may carry one or more TBs of data. Sidelink data and control transmission (i.e., transmission directly between two or more UEs 120) may typically use techniques similar to those described for uplink data and control transmission, and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0090] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, or with one or more transmitting or receiving components (such as...) Figure 2 An antenna module is a combination of one or more antenna elements coupled to one or more components. As used herein, "antenna" can mean one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can mean a group of antennas (such as antenna elements) arranged in an array or panel that can facilitate beamforming by manipulating the parameters of that group of antennas. "Antenna module" can mean a circuit that includes one or more antennas, and may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0091] In some examples, each antenna element of antenna 234 or antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element that can be used to independently transmit the cross-polarized signal. Antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements can allow signals with a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam) in various directions. For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference modes of signals transmitted by individual antenna elements within that desired range.

[0092] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.

[0093] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally speaking, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).

[0094] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0095] As pointed out above, Figure 2 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 2 The examples described are different.

[0096] Figure 3 This is an illustration of an example decomposed base station architecture 300 according to the present disclosure. One or more components of the example decomposed base station architecture 300 may be, may include, or may be included in one or more network nodes (such as one or more network nodes 110). The decomposed base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or may communicate indirectly with the core network 320 via one or more decomposed control units (such as non-RT RIC 350 and / or near-RT RIC 370 associated with a Service Management and Orchestration (SMO) framework 360) (e.g., via an E2 link). The CU 310 may communicate with one or more DU 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120 via a corresponding RF access link. In some deployments, a UE 120 may be served simultaneously by multiple RU 340s.

[0097] Each component in the components of the decomposed base station architecture 300 (including CU 310, DU 330, RU 340, near-RT RIC 370, non-RT RIC 350, and SMO frame 360) may include one or more interfaces or may be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

[0098] In some respects, the CU 310 can be logically divided into one or more CU user plane (CU-UP) units and one or more CU control plane (CU-CP) units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be deployed to communicate with one or more DU 330s for network control and signaling, as needed. Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340s. For example, the DU 330 may host various layers, such as the RLC layer, MAC layer, or one or more PHY layers (such as one or more high PHY layers or one or more low PHY layers). Each layer (which may also be referred to as a module) can be implemented using an interface for signaling to other layers (and modules) hosted by the DU 330, or for signaling to control functions hosted by the CU 310. Each RU 340 may implement lower-layer functionality. In some respects, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330.

[0099] The SMO framework 360 supports RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 360 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 360 can interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 350, and / or near-RT RIC 370. In some aspects, the SMO framework 360 can communicate with hardware aspects of the 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 380) via the O1 interface. Additionally or alternatively, the SMO framework 360 can communicate directly with each of one or more RUs 340 via the corresponding O1 interface. In some deployments, this configuration enables each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0100] The non-RT RIC 350 may include or implement logic functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, and / or policy-based guidance of applications and / or features in the near-RT RIC 370. The non-RT RIC 350 may be coupled to or communicate with the near-RT RIC 370, such as via an A1 interface. The near-RT RIC 370 may include or implement logic functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.

[0101] In some aspects, to generate AI / ML models to be deployed in the near-RT RIC 370, the non-RT RIC 350 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 370 and can be received from non-network data sources or network functions at the SMO framework 360 or the non-RT RIC 350. In some examples, the non-RT RIC 350 or near-RT RIC 370 may modulate RAN behavior or performance. For example, the non-RT RIC 350 may monitor long-term trends and patterns in performance and may employ AI / ML models to perform corrective actions via the SMO framework 360 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0102] Figure 1 , Figure 2 or Figure 3 Network node 110, its controller / processor 240, UE 120, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies associated with at least partially DCI-based PRACH transmission or perform one or more operations associated with at least partially DCI-based PRACH transmission, as described in more detail elsewhere herein. For example, network node 110's controller / processor 240, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies associated with at least partially DCI-based PRACH transmission or perform one or more operations associated with at least partially DCI-based PRACH transmission. Figure 2 Any other component, CU 310, DU 330, or RU 340, may (alone or in conjunction with one or more other processors) perform or direct, for example... Figure 8 The process 800 Figure 9 The process 900 Figure 10 Process 1000 Figure 11 Process 1100 Figure 12 Process 1200 Figure 13The operation of process 1300 or other processes as described herein. Memory 242 may store data and program code for network node 110, CU 310, DU 330, or RU 340. Memory 282 may store data and program code for UE 120. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing instruction sets (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the instruction set may be made to be executed by one or more processors of network node 110, UE 120, CU 310, DU 330, or RU 340 (e.g., directly, or after compilation, transformation, or interpretation). Figure 8 The process 800 Figure 9 The process 900 Figure 10 Process 1000 Figure 11 Process 1100 Figure 12 Process 1200 Figure 13 The process 1300 or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions, and / or interpret instructions, etc.

[0103] In some aspects, the UE (e.g., UE 120) includes components for receiving a PDCCH command DCI including an indicator for indicating whether the Tx beam of the PRACH transmission is at least partially based on the Tx beam of the associated SRS or at least partially based on the Rx beam of the associated SSB or CSI-RS; and / or components for transmitting the PRACH transmission at least partially based on the indicator. In some aspects, the UE includes components for receiving a configuration including a first preamble receive target power value and a second preamble receive target power value; and / or components for transmitting the PRACH transmission using the first preamble receive target power value or the second preamble receive target power value depending on whether the PRACH transmission is destined for an uplink-only TRP or a downlink TRP. In some aspects, the UE includes components for receiving a PDCCH command DCI including a TCI field, the TCI field indicating the TCI status for PRACH transmission via the PDCCH command; and / or components for transmitting PRACH transmission via the PDCCH command based at least in part on the TCI field. Components for the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0104] In some aspects, a network node (e.g., network node 110) includes components for transmitting a PDCCH command DCI including an indicator for indicating whether the Tx beam of the PRACH transmission is at least partially based on the Tx beam of the associated SRS or at least partially based on the Rx beam of the associated SSB or CSI-RS; and / or components for receiving the PRACH transmission at least partially based on the indicator. In some aspects, the network node includes components for transmitting a configuration including a first preamble receive target power value and a second preamble receive target power value; and / or components for receiving the PRACH transmission using the first preamble receive target power value or the second preamble receive target power value depending on whether the PRACH transmission is destined for an uplink-only TRP or a downlink TRP. In some aspects, the network node includes components for transmitting a PDCCH command DCI including a TCI field indicating the TCI status for a PRACH transmission via the PDCCH command; and / or components for receiving a PRACH transmission via the PDCCH command, at least in part based on the TCI field. Components enabling the network node to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 214, a TX MIMO processor 216, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0105] As pointed out above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0106] Figure 4 This is a diagram illustrating example 400 of an uplink-intensive deployment according to this disclosure.

[0107] like Figure 4 As shown, dense uplink deployment can be used to improve uplink coverage and / or capacity. Uplink Rx points (e.g., uplink-only nodes) can receive uplink signals and / or uplink channels from the UE. Downlink signals and / or downlink channels transmitted from the network node can originate from different nodes (e.g., macro nodes, central nodes, serving cells, or serving base stations). Uplink Rx points can be connected to the network node via backhaul links. Dense uplink deployment can help reduce uplink path loss, which can be helpful when uplink coverage is a bottleneck. Since uplink Rx points do not transmit any downlink signals, dense uplink deployment can help in terms of deployment cost and / or complexity. Uplink Rx points simply receive uplink signals and, with or without processing, transmit them to the network node.

[0108] In SUL (Supplemental Uplink Utility), a UE can be configured using two uplink carriers on a single downlink carrier serving the same cell, and uplink transmissions on these two uplink carriers are not simultaneous. For example, for both TDD (Telematics Directed Access) and SUL, the UE can transmit uplink signals on the TDD band (e.g., a non-supplementary uplink band) or on the SUL carrier. For both uplink-intensive deployment and SUL, the downlink and uplink beams can be separate.

[0109] As pointed out above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0110] A DCI format 1_0 scrambled with the Cell Radio Network Temporary Identifier (C-RNTI) (where the corresponding Frequency Domain Resource Allocation (FDRA) field is set to all one) can be used in a random access procedure initiated by a PDCCH command. The DCI format 1_0 for the PDCCH command may include various fields. The DCI format 1_0 for the PDCCH command may include a random access preamble index field (6 bits). The DCI format 1_0 for the PDCCH command may include an uplink / SUL indicator field (1 bit). When the value of the random access preamble index is not all zero, and when the UE is configured using SUL in the serving cell configuration within the cell, the uplink / SUL indicator field may indicate which uplink carrier in the cell is used for PRACH transmission. Otherwise, the uplink / SUL indicator field may be reserved. The DCI format 1_0 for the PDCCH command may include a synchronization signal (SS) or physical broadcast channel (PBCH) (SS / PBCH) index field (6 bits). When the value of the random access preamble index is not all zeros, the SS / PBCH index field may indicate the SS / PBCH to be used to determine the timing of the random access channel (RACH) for PRACH transmission. Otherwise, the SS / PBCH index field may be reserved. The DCI format 1_0 for the PDCCH command may include a PRACH mask index field (4 bits). When the value of the random access preamble index is not all zeros, the PRACH mask index field may indicate the RACH timing associated with the SS / PBCH indicated by the SS / PBCH index used for PRACH transmission. Otherwise, the PRACH mask index field may be reserved.

[0111] The DCI format 1_0 used for PDCCH commands may include a PRACH association indicator field (0 bits or 1 bit). When the UE is provided with a tag identifier ( tag-Id2 ), and the UE was not provided with a control resource set (CORESET) pool index ( coresetPoolIndexThe PRACH association indicator field can be 1 bit when provided with a CORESET pool index of value 0 for the first CORESET and a CORESET pool index of value 1 for the second CORESET. When the UE is provided with the SSB MTC Additional Physical Cell Identifier (PCI)... SSB-MTC-AdditionalPCI When the UE is not provided with the SSB MTC additional PCI parameter, the PRACH association indicator field can indicate the PCI associated with the PRACH transmission. Bit field index 0 of the PRACH association indicator field can be mapped to the PCI of the serving cell, and bit field index 1 of the PRACH association indicator field can be mapped to the active additional PCI. When the UE is not provided with the SSB MTC additional PCI parameter, the PRACH association indicator field can indicate the path loss reference signal (PL-RS) used for PRACH transmission. Bit field index 0 of the PRACH association indicator field can be mapped to the downlink reference signal (DL-RS) that the DMRS of the PDCCH command quasi-co-located with it, and bit field index 1 of the PRACH association indicator field can be mapped to the SS / PBCH indicated by the SS / PBCH index field in the DCI format 1_0 for the PDCCH command. Otherwise, the PRACH association indicator field can be 0 bits. The DCI format 1_0 for the PDCCH command may include reserved bits.

[0112] During a two-step or four-step RACH procedure, for MSG 1 (PRACH) transmission, MSG 3 transmission, or MSGA payload, the same spatial domain transmit filter (Tx beam) used for the corresponding SSB or CSI-RS reception (Rx beam) can be used. The mapping between the SSB (or CSI-RS resource in the case of CFRA) and the RACH timing can be defined, at least in part, based on the configuration and rule set in the specification. However, the Tx beam for PRACH transmission may not be explicitly defined / specified in the specification. For UEs with beam correspondence, the UE can follow the associated SSB / CSI-RS Rx beam. For UEs without beam correspondence, multiple Tx beams around the corresponding SSB / CSI-RS Rx beam can be tried for multiple PRACH attempts.

[0113] In cases of dense uplink deployment (e.g., where the uplink TRP differs from the downlink TRP) or when the uplink carrier is SUL (e.g., in FR2 or higher frequency bands), the Rx beam of the downlink signal / channel (corresponding to the downlink TRP / carrier) should not be used for the Tx beam of PRACH transmission when PRACH transmission will also be received by the uplink TRP / carrier. Identifying and indicating a good Tx beam for PRACH transmission can be difficult in the case of a random access procedure for initial access. However, in other cases where the UE is in RRC connection mode (e.g., for random access due to beam fault recovery (BFR) or PDCCH command), a previous uplink beam scan (e.g., SRS) may have already occurred. In these cases, a good uplink beam for the Tx beam used for PRACH transmission (or MSG 3 transmission or MSG A payload) can be identified and indicated by the network node.

[0114] Path loss offset can be applied to PRACH transmissions via PDCCH commands. The Tx beam for PRACH transmissions toward the uplink TRP can be determined. To determine the Tx beam for PRACH transmissions toward the uplink TRP, the Tx beam for PRACH transmissions can be indicated in the PDCCH command DCI by pointing to the SRS resource ID, and some reserved bits in the PDCCH command DCI can be used to indicate the Tx beam for PRACH transmissions. However, when a field for SRS resource index indication (e.g., the SRS resource indication field) is introduced, the SSB / PBCH index field may still be needed to indicate the PRACH timing. In this case, the UE may not be able to distinguish whether the Tx beam for PRACH transmissions is at least partially based on the SRS Tx beam (e.g., indicated by the SRS resource indication field) or at least partially based on the associated SSB / CSI-RS Rx beam. Furthermore, in some cases, path loss offset may not be required. When path loss offset is not required, the UE may not be able to determine the Tx power used for PRACH transmissions toward an uplink-only TRP. When path loss offset is required, a design for indicating path loss offset may be needed.

[0115] In various aspects of the technologies and apparatus described herein, a UE can receive a PDCCH command DCI, including an indicator, from a network node associated with a dense uplink deployment in which the uplink TRP differs from the downlink TRP. This indicator indicates whether the Tx beam of the PRACH transmission is at least partially based on the Tx beam of the associated SRS or at least partially based on the Rx beam of the associated SSB or CSI-RS. The UE can transmit PRACH to the network node at least partially based on the indicator. The UE can transmit PRACH at least partially based on the Tx beam of the associated SRS. Alternatively, the UE can transmit PRACH at least partially based on the Rx beam of the associated SSB or CSI-RS. In other words, the UE can use a Tx beam to transmit PRACH, and the Tx beam can be associated with the Tx beam of the associated SRS, or the Tx beam can be associated with the Rx beam of the associated SSB or CSI-RS.

[0116] In some respects, by indicating whether the Tx beam for PRACH transmission is at least partially based on the associated SRS Tx beam or at least partially based on the associated SSB or CSI-RS Rx beam, the UE can use the appropriate Tx beam for PRACH transmission. Indicators in the PDCCH command DCI allow the UE to distinguish whether the Tx beam for PRACH transmission is at least partially based on the SRS Tx beam (e.g., indicated by the SRS resource indication field) or at least partially based on the associated SSB or CSI-RS Rx beam. Therefore, the UE can use the appropriate Tx beam, which increases the likelihood that the PRACH transmission will be successfully received by the network node. By increasing the likelihood of successful reception of PRACH transmissions, retransmissions of PRACH transmissions can be avoided, thereby reducing network resource and power consumption at the UE.

[0117] Figure 5 This is an illustration of example 500 associated with PRACH transmission based at least in part on DCI, according to this disclosure. Figure 5 As shown, Example 500 includes communication between a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the UE and the network node may be included in a wireless network (such as wireless network 100). The UE and the network node may be associated with an uplink-intensive environment where the uplink TRP differs from the downlink TRP.

[0118] As shown by reference numeral 502 in the attached figure, the UE can receive a PDCCH command DCI from a network node, which includes an indicator used to indicate whether the Tx beam transmitted by the PRACH is at least partially based on the Tx beam of the associated SRS or at least partially based on the Rx beam of the associated SSB or CSI-RS. The indicator can be a single bit, and the indicator can be set to a first value to indicate that the Tx beam transmitted by the PRACH is at least partially based on the Tx beam of the associated SRS, or the indicator can be set to a second value to indicate that the Tx beam transmitted by the PRACH is at least partially based on the Rx beam of the associated SSB or CSI-RS. The indicator can be associated with one or more reserved bits in the PDCCH command DCI. The indicator can also be associated with a PRACH association indicator in the PDCCH command DCI.

[0119] In some aspects, the PRACH association indicator may be set to a first value to indicate that the Tx beam transmitted by the PRACH is at least partially based on the Tx beam of the associated SRS, or the PRACH association indicator may be set to a second value to indicate that the Tx beam transmitted by the PRACH is at least partially based on the Rx beam of the associated SSB or CSI-RS. In some aspects, the indicator may be associated with an SRS resource indication field, wherein a first code point in the SRS resource indication field indicates that the Tx beam transmitted by the PRACH is at least partially based on the Rx beam of the associated SSB or CSI-RS, and a second code point in the SRS resource indication field indicates that the Tx beam transmitted by the PRACH is at least partially based on the Tx beam of the associated SRS.

[0120] In some respects, indicators in the PDCCH command DCI can be used to indicate whether the Tx beam transmitted by PRACH is at least partially based on the Tx beam of the associated SRS or at least partially based on the Rx beam of the associated SSB / CSI-RS. When the indicator is set to a first value (e.g., 0), the Tx beam transmitted by PRACH may be at least partially based on the Rx beam of the associated SSB / CSI-RS. When the indicator is set to a second value (e.g., 1), the Tx beam transmitted by PRACH may be at least partially based on the Tx beam of the associated SRS.

[0121] In some aspects, indicators in the PDCCH command DCI can be indicated in various ways. In the first option, one of the reserved bits can be used for the indicator. In the second option, the PRACH association indicator in the PDCCH command DCI can be reused. The PRACH association indicator can be reused when two timing advances (TAs) are supported for asymmetric downlink single TRP (sTRP) or uplink multiple TRP (mTRP) scenarios. In this case, the UE can reinterpret the PRACH association indicator. When the PRACH association indicator is set to 0, the Tx beam transmitted by PRACH can be at least partially based on the Rx beam of the associated SSB / CSI-RS. When the PRACH association indicator is set to 1, the Tx beam transmitted by PRACH can be at least partially based on the Tx beam of the associated SRS.

[0122] In some respects, the SRS Resource Indication field can be used to indicate whether a Tx beam transmitted by PRACH is at least partially based on the Tx beam of the associated SRS. In this case, one code point in the SRS Resource Indication field can be used to indicate that the Tx beam transmitted by PRACH is at least partially based on the Rx beam of the associated SSB / CSI-RS. The remaining code points can be used to indicate that the Tx beam transmitted by PRACH is at least partially based on the Tx beam of the associated SRS.

[0123] As shown by reference numeral 504 in the attached figure, the UE may transmit PRACH to the network node at least in part based on an indicator. The UE may transmit PRACH at least in part based on the Tx beam of the associated SRS. Alternatively, the UE may transmit PRACH at least in part based on the Rx beam of the associated SSB or CSI-RS. In other words, the UE may use a Tx beam to transmit PRACH, and the Tx beam may be associated with the Tx beam of the associated SRS, or the Tx beam may be associated with the Rx beam of the associated SSB or CSI-RS.

[0124] As pointed out above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0125] Figure 6 This is an illustration of example 600 associated with PRACH transmission based at least in part on DCI, according to this disclosure. Figure 6As shown, Example 600 includes communication between a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the UE and the network node may be included in a wireless network (such as wireless network 100). The UE and the network node may be associated with an uplink-intensive environment where the uplink TRP differs from the downlink TRP.

[0126] As shown by reference numeral 602 in the attached figure, the UE can receive a configuration from the network node including a first preamble reception target power value and a second preamble reception target power value. The configuration may include a first set of parameters and a second set of parameters. The first set of parameters may include one or more of the following: the first preamble reception target power value, a first maximum number of preamble transmissions, or a first power ramp step size value. The second set of parameters may include one or more of the following: the second preamble reception target power value, a second maximum number of preamble transmissions, or a second power ramp step size.

[0127] In some respects, the second set of parameters may apply only to RACH transmitted via PDCCH commands, or the second set of parameters may apply to RACH transmitted via PDCCH commands and other PRACH transmissions. In some respects, the second set of parameters may be configured for only four-step RACH procedures, or the second set of parameters may be configured for both four-step and two-step RACH procedures.

[0128] As shown by reference numeral 604 in the attached figure, depending on whether the PRACH transmission is directed to an uplink-only TRP or a downlink-only TRP, the UE can use a first preamble receive target power value or a second preamble receive target power value to transmit the PRACH to the network node. The UE can choose either the first preamble receive target power value or the second preamble receive target power value. The UE can determine the PRACH transmission power used for PRACH transmission based at least in part on the first preamble receive target power value or the second preamble receive target power value. Alternatively, depending on whether the PRACH transmission is directed to an uplink-only TRP or a downlink-only TRP, the UE can use a first set of parameters or a second set of parameters to transmit the PRACH to the network node. The UE can choose either the first set of parameters or the second set of parameters. The UE can determine the PRACH transmission power used for PRACH transmission based at least in part on the first set of parameters or the second set of parameters. The path loss between the UE and the uplink-only TRP may be less than the path loss between the UE and the downlink TRP. The Tx power associated with PRACH transmissions to uplink-only TRPs can be less than the Tx power associated with PRACH transmissions to downlink TRPs. To support different Tx powers for PRACH transmissions to uplink-only and downlink TRPs, different preamble receive target power values ​​can be configured. Additionally, different... preambleTransMax Value and powerRampingStep value.

[0129] In some aspects, the UE may receive a PDCCH command DCI including an indicator from a network node. The UE may select a first preamble receive target power value or a second preamble receive target power value based at least in part on the indicator. The indicator may be set to a first value to indicate that the first preamble receive target power value should be used, or the indicator may be set to a second value to indicate that the second preamble receive target power value should be used. In some aspects, the UE may select a first set of parameters or a second set of parameters based at least in part on the indicator. The indicator may be set to a first value to indicate that the first set of parameters should be used, or the indicator may be set to a second value to indicate that the second set of parameters should be used.

[0130] In some aspects, the UE may select a first preamble receive target power value or a second preamble receive target power value based at least partially on the Tx beam transmitted via PRACH. The first preamble receive target power value may be selected at least partially based on the Tx beam transmitted via PRACH and at least partially based on the Rx beam of the associated SSB or CSI-RS. The second preamble receive target power value may be selected at least partially based on the Tx beam transmitted via PRACH and at least partially based on the Tx beam of the associated SRS. In some aspects, the UE may select a first set of parameters or a second set of parameters based at least partially on the Tx beam transmitted via PRACH. The first set of parameters may be selected at least partially based on the Tx beam transmitted via PRACH and at least partially based on the Rx beam of the associated SSB or CSI-RS. The second set of parameters may be selected at least partially based on the Tx beam transmitted via PRACH and at least partially based on the Tx beam of the associated SRS.

[0131] In some respects, the UE may receive an indication via a PDCCH command DCI that includes an SRS resource indication field for using uplink path loss associated with the TCI state of the indicated SRS resource or for using path loss offset associated with the TCI state of the indicated SRS resource.

[0132] In some respects, the PRACH transmit power can be determined based on the following: P PRACH,b,f,c (i) = min{P CMAX,f,c (i), P PRACH,target,f,c + PL b,f,c } [dBm], where b Indicates uplink BWP, f Indicates carrier frequency, c Instructions for service communities, P CMAX,f,c (i) Indicates the serving cell in each time slot c carrier f The configured maximum UE output power, P PRACH,target,f,c Indicate the target receive power of PRACH, and PL b,f,c The instructions are at least in part based on the serving cell c The PRACH transmission on the active downlink BWP transmits the associated DL RS carrier. f Activity uplink BWP bThe path loss. For PRACH transmissions to an uplink-only TRP, since the path loss between the UE and the uplink-only TRP may be lower than the path loss between the UE and the downlink TRP, a lower Tx power may be required compared to PRACH transmissions to a downlink TRP. To achieve lower Tx power, network nodes can configure different preamble receive target powers and can use one of these preamble receive target powers depending on whether the PRACH transmission is to an uplink-only TRP or a downlink TRP. Additionally, different... preambleTransMax Value and powerRampingStep value.

[0133] In some aspects, the target power can be received via RRC signaling using two preambles. preambleReceivedTargetPower The UE is configured with a preamble receive target power value. The UE can select one of the preamble receive target power values ​​to determine the PRACH transmit power. Two values ​​can be used. preambleReceivedTargetPower Values ​​rather than a single preambleReceivedTargetPower The UE is configured with a value of ) . In some respects, the maximum number of ( ) that can be sent via RRC signaling using two preambles ( preambleTransMax ) value and two power ramp step sizes ( powerRampingStep ) value configuration UE. Two can be used preambleTransMax Value and two powerRampingStep Values, not a single preambleTransMax Values ​​and Singles powerRampingStep Value configuration UE. For example, when applying the second preambleReceivedTargetPower When the value is reached, the second one can be applied. preambleTransMax and / or the second powerRampingStep The second set of parameters (e.g., the second...) preambleReceivedTargetPower Value, Second preambleTransMax Value and / or second powerRampingStep The value can be applied only to PRACH transmissions via PDCCH commands, or to both PRACH transmissions via PDCCH commands and other PRACH transmissions. The second set of parameters can be configured for only four-step PRACH or for both four-step and two-step PRACH.

[0134] In some respects, the UE can select based at least in part on the indications in the PDCCH command DCI. preambleReceivedTargetPower One of the values. In this case, the UE can use an indicator in the PDCCH command DCI to select. preambleReceivedTargetPower One of the values. When the indicator is set to the first value (e.g., 0), the UE can use the first value. preambleReceivedTargetPower Value or having a large value preambleReceivedTargetPower When the indicator is set to a second value (e.g., 1), the UE can use the second... preambleReceivedTargetPowervalue or having a smaller value preambleReceivedTargetPower Either the reserved bit or an existing PRACH association indicator can be reused. Alternatively, the PRACH association indicator in the PDCCH command DCI can be reused to transmit two... preambleReceivedTargetPower One of the values ​​is provided for use by the UE.

[0135] In some respects, the UE can select, at least in part, the Tx beam transmitted via PRACH. preambleReceivedTargetPower One of the values. When the Tx beam transmitted by PRACH is at least partially based on the Rx beam of the associated SSB / CSI-RS, the UE can use the first one. preambleReceivedTargetPower Or have a large value preambleReceivedTargetPower When the Tx beam transmitted by PRACH is at least partially based on the Tx beam of the associated SRS, the UE can use a second preambleReceivedTargetPower Or with a smaller value preambleReceivedTargetPower .

[0136] In some aspects, for PRACH power control, when an SRS resource indication field exists in the PDCCH command DCI, the UE can be instructed to use either the uplink path loss associated with the TCI state of the indicated SRS resource, or the path loss offset associated with the TCI state of the indicated SRS resource. When using uplink path loss, the PL in the PRACH power control formula... b,f,c This can be replaced by uplink path loss. When using path loss offset, the PL in the PRACH power control formula... b,f,c Can be generated by PL b,f,c –PL offset instead. In this case, PL is used. b,f,c The determined PL-RS may be based at least in part on the legacy DL RS for PRACH power control, or at least in part on the PL-RS associated with the TCI state of the indicated SRS resource.

[0137] As pointed out above, Figure 6 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 6 The examples described are different.

[0138] Figure 7 This is an illustration of example 700 associated with PRACH transmission based at least in part on DCI, according to this disclosure. Figure 7 As shown, Example 700 includes communication between a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the UE and the network node may be included in a wireless network (such as wireless network 100). The UE and the network node may be associated with an uplink-intensive environment where the uplink TRP differs from the downlink TRP.

[0139] As shown by reference numeral 702 in the attached figure, the UE can receive a PDCCH command DCI from a network node, which includes a TCI field indicating the TCI state for PRACH transmission via the PDCCH command. The TCI field may indicate a TCI state identifier. The TCI field may indicate an active TCI state among one or more active TCI states, and the TCI field may indicate a TCI code point mapped to the active TCI state. The UE may apply the TCI state by default, wherein the TCI state may be associated with an SSB, CSI-RS, or SRS, and Tx beaming and power control for PRACH transmission via the PDCCH command may be at least partially based on the TCI state. Alternatively, the UE may apply the TCI state at least partially based on a single indicator in the PDCCH command DCI, wherein Tx beaming and power control for PRACH transmission via the PDCCH command may be at least partially based on the TCI state. The UE may apply a path loss offset associated with the TCI state to power control.

[0140] As shown by reference numeral 704 in the attached figure, the UE may send PRACH transmissions via PDCCH commands to the network node based at least in part on the TCI field. The UE may also send PRACH transmissions via PDCCH commands based at least in part on the TCI state. For example, the UE may send PRACH transmissions via PDCCH commands based at least in part on the TCI state identifier or the active TCI state in one or more active TCI states.

[0141] In some respects, for PRACH via PDCCH commands, the TCI status can be used to indicate the UE in the PDCCH command DCI. In this case, a field (e.g., a TCI field) can be introduced in the PDCCH command DCI, and some reserved bits in the PDCCH command DCI can be used to indicate the TCI status. The field can directly indicate the TCI status ID. Alternatively, the field can indicate an active TCI status among one or more active TCI states. In this case, the field can indicate a TCI code point, where the TCI code point can be mapped to the active TCI status at least in part based on a pre-established mapping (e.g., at least in part based on the mapping of the active MAC-CE).

[0142] In some aspects, when a TCI field is present in the PDCCH command DCI, the UE may always use the indicated TCI state. In this case, the indicated TCI state may be associated with the SSB / CSI-RS or with the SRS. The Tx beam transmitted by PRACH and the power transmitted by PRACH may be based at least in part on the indicated TCI state. In some aspects, when a TCI field is present in the PDCCH command DCI, whether the indicated TCI state in the PDCCH command DCI is applied may be explicitly indicated by a 1-bit indicator in the PDCCH command (e.g., reusing a reserved bit), or indicated by using a code point in the TCI field of the PDCCH command DCI. In this case, when the UE is indicated not to use the indicated TCI state, the Tx beam transmitted by PRACH and the power control for PRACH transmission may be based at least in part on legacy rules. When the UE is instructed to use the indicated TCI state, the Tx beam for PRACH transmission and the power control for PRACH transmission may be based at least in part on the indicated TCI state.

[0143] In some respects, when an indicated TCI state is applied, the path loss offset associated with the indicated TCI state can be used for PRACH power control. In this case, the PL in the PRACH power control formula... b,f,c Can be generated by PL b,f,c -PL offset instead, where the path loss offset is the path loss offset associated with the indicated TCI state. Used for PL b,f,c The determined PL-RS may be based at least in part on the legacy DL RS used for PRACH power control, or at least in part on the PL-RS associated with the indicated TCI state. When the indicated TCI state is not associated with the path loss offset, the default path loss offset value may be assumed to be 0.

[0144] As pointed out above, Figure 7 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 7 The examples described are different.

[0145] Figure 8 This is a diagram illustrating an example process 800 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 800 is an example in which a device or UE (e.g., UE 120) performs operations associated with PRACH transmission at least in part based on DCI.

[0146] like Figure 8As shown, in some aspects, process 800 may include receiving a PDCCH command DCI including an indicator for indicating whether the Tx beam transmitted by PRACH is at least partially based on the Tx beam of the associated SRS or at least partially based on the Rx beam of the associated SSB or CSI-RS (box 810). For example, the UE (e.g., using...) Figure 14 The receiving component 1402 and / or communication manager 1406 depicted herein may receive a PDCCH command DCI including an indicator for indicating whether the Tx beam transmitted by PRACH is at least partially based on the Tx beam of the associated SRS or at least partially based on the Rx beam of the associated SSB or CSI-RS, as described above.

[0147] like Figure 8 As further shown, in some aspects, process 800 may include sending PRACH transmissions at least in part based on indicators (box 820). For example, the UE (e.g., using...) Figure 14 The transmitting component 1404 and / or communication manager 1406 depicted herein may transmit PRACH transmissions at least in part based on indicators, as described above.

[0148] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0149] In the first aspect, the indicator is a single bit, and the indicator is set to a first value to indicate that the Tx beam transmitted by PRACH is at least partially based on the Tx beam of the associated SRS, or the indicator is set to a second value to indicate that the Tx beam transmitted by PRACH is at least partially based on the Rx beam of the associated SSB or CSI-RS.

[0150] In the second aspect, either alone or in combination with the first aspect, the indicator is associated with one or more reserved bits in the PDCCH command DCI.

[0151] In the third aspect, either alone or in combination with one or more of the first and second aspects, the indicator is associated with the PRACH associated indicator in the PDCCH command DCI.

[0152] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the PRACH association indicator is set to a first value to indicate that the Tx beam transmitted by the PRACH is at least partially based on the Tx beam of the associated SRS, or the PRACH association indicator is set to a second value to indicate that the Tx beam transmitted by the PRACH is at least partially based on the Rx beam of the associated SSB or CSI-RS.

[0153] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the indicator is associated with an SRS resource indication field, wherein a first code point in the SRS resource indication field indicates that the Tx beam transmitted by the PRACH is at least partially based on the Rx beam of the associated SSB or CSI-RS, and a second code point in the SRS resource indication field indicates that the Tx beam transmitted by the PRACH is at least partially based on the Tx beam of the associated SRS.

[0154] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the UE is associated with an uplink-intensive environment in which the uplink TRP differs from the downlink TRP.

[0155] although Figure 8 An example box of process 800 is shown, but in some respects, process 800 may include... Figure 8 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 800 may be executed in parallel.

[0156] Figure 9 This is a diagram illustrating an example process 900 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 900 is an example in which a device or UE (e.g., UE 120) performs operations associated with PRACH transmission at least in part based on DCI.

[0157] like Figure 9 As shown, in some aspects, process 900 may include receiving a configuration including a first preamble receive target power value and a second preamble receive target power value (block 910). For example, the UE (e.g., using...) Figure 14 The receiving component 1402 and / or communication manager 1406 depicted herein can receive configurations including a first preamble receive target power value and a second preamble receive target power value, as described above.

[0158] like Figure 9 Further, as shown, in some aspects, process 900 may include transmitting the PRACH using a first preamble to receive the target power value or a second preamble to receive the target power value, depending on whether the PRACH transmission is destined for an uplink-only TRP or a downlink TRP (box 920). For example, the UE (e.g., using...) Figure 14The transmitting component 1404 and / or communication manager 1406 described above may transmit the PRACH transmission using a first preamble to receive the target power value or a second preamble to receive the target power value, depending on whether the PRACH transmission is destined for an uplink-only TRP or a downlink TRP.

[0159] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0160] In a first aspect, process 900 includes: selecting a first preamble received target power value or a second preamble received target power value; and determining a PRACH transmission power for PRACH transmission based at least in part on the first preamble received target power value or the second preamble received target power value.

[0161] In the second aspect, either alone or in combination with the first aspect, the path loss between the UE and the uplink-only TRP is less than the path loss between the UE and the downlink TRP, and the Tx power associated with PRACH transmissions to the uplink-only TRP is less than the Tx power associated with PRACH transmissions to the downlink TRP.

[0162] In a third aspect, either alone or in combination with one or more of the first and second aspects, a configuration is made including a first set of parameters and a second set of parameters, wherein the first set of parameters includes one or more of a first preamble reception target power value, a first maximum number of preamble transmissions, and a first power ramp step value, and the second set of parameters includes one or more of a second preamble reception target power value, a second maximum number of preamble transmissions, or a second power ramp step value.

[0163] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the second set of parameters applies only to RACH transmitted via PDCCH command, or the second set of parameters applies to RACH and other PRACH transmissions transmitted via PDCCH command.

[0164] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the second set of parameters is configured for a four-step RACH process only, or the second set of parameters is configured for both a four-step RACH process and a two-step RACH process.

[0165] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, process 900 includes: receiving a PDCCH command DCI including an indicator; and selecting a first set of parameters or a second set of parameters based at least in part on the indicator.

[0166] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the indicator is set to a first value to indicate the use of a first set of parameters, or the indicator is set to a second value to indicate the use of a second set of parameters.

[0167] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 900 includes selecting a first set of parameters or a second set of parameters based at least partially on the Tx beam transmitted by PRACH, wherein the first set of parameters is selected at least partially based on the Tx beam transmitted by PRACH and at least partially based on the Rx beam of the associated SSB or CSI-RS, or the second set of parameters is selected at least partially based on the Tx beam transmitted by PRACH and at least partially based on the Tx beam of the associated SRS.

[0168] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, process 900 includes receiving, via a PDCCH command DCI including an SRS resource indication field, an indication for using uplink path loss associated with the TCI state of the indicated SRS resource or for using path loss offset associated with the TCI state of the indicated SRS resource.

[0169] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the UE is associated with an uplink-intensive environment in which the uplink TRP differs from the downlink TRP.

[0170] although Figure 9 An example box of process 900 is shown, but in some respects, process 900 may include... Figure 9 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 900 may be executed in parallel.

[0171] Figure 10 This is a diagram illustrating an example process 1000 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 1000 is an example in which a device or UE (e.g., UE 120) performs operations associated with PRACH transmission at least in part based on DCI.

[0172] like Figure 10 As shown, in some aspects, process 1000 may include receiving a PDCCH command DCI that includes a TCI field used to indicate the TCI status for PRACH transmission via the PDCCH command (box 1010). For example, the UE (e.g., using...) Figure 14The receiving component 1402 and / or communication manager 1406 depicted herein may receive a PDCCH command DCI including a TCI field, which is used to indicate the TCI status for PRACH transmission via the PDCCH command, as described above.

[0173] like Figure 10 As further shown, in some aspects, process 1000 may include transmitting PRACH via PDCCH command based at least in part on the TCI field (box 1020). For example, the UE (e.g., using...) Figure 14 The transmitting component 1404 and / or the communication manager 1406 described herein can transmit PRACH commands via PDCCH commands, at least in part, based on the TCI field, as described above.

[0174] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0175] In the first aspect, the TCI field indicates a TCI state identifier, or the TCI field indicates an active TCI state among one or more active TCI states, and the TCI field indicates a TCI code point mapped to the active TCI state.

[0176] In a second aspect, either alone or in combination with the first aspect, process 1000 includes: applying a TCI state by default, wherein the TCI state is associated with an SSB, CSI-RS, or SRS, and Tx beam and power control for PRACH transmission via PDCCH command is at least partially based on the TCI state; or applying the TCI state at least partially based on a single indicator in the PDCCH command DCI, wherein Tx beam and power control for PRACH transmission via PDCCH command is at least partially based on the TCI state.

[0177] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 1000 includes applying a path loss offset associated with the TCI state used for power control.

[0178] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the UE is associated with an uplink-intensive environment in which the uplink TRP differs from the downlink TRP.

[0179] although Figure 10 An example box of process 1000 is shown, but in some aspects, process 1000 may include... Figure 10The boxes depicted in the process are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in the process 1000 may be executed in parallel.

[0180] Figure 11 This is a diagram illustrating an example process 1100 performed, for example, at a network node or a device of a network node, according to the present disclosure. Example process 1100 is an example in which a device or network node (e.g., network node 110) performs operations associated with PRACH transmission at least in part based on DCI.

[0181] like Figure 11 As shown, in some aspects, process 1100 may include transmitting a PDCCH command DCI including an indicator for indicating whether the Tx beam transmitted by PRACH is at least partially based on the Tx beam of the associated SRS or at least partially based on the Rx beam of the associated SSB or CSI-RS (box 1110). For example, network nodes (e.g., using...) Figure 15 The transmitting component 1504 and / or communication manager 1506 depicted herein may transmit a PDCCH command DCI including an indicator for indicating whether the Tx beam transmitted by PRACH is at least partially based on the Tx beam of the associated SRS or at least partially based on the Rx beam of the associated SSB or CSI-RS, as described above.

[0182] like Figure 11 As further shown, in some aspects, process 1100 may include receiving PRACH transmissions at least in part based on an indicator (box 1120). For example, a network node (e.g., using...) Figure 15 The receiving component 1502 and / or communication manager 1506 described herein can receive PRACH transmissions at least in part based on indicators, as described above.

[0183] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0184] In the first aspect, the indicator is a single bit, and the indicator is set to a first value to indicate that the Tx beam transmitted by PRACH is at least partially based on the Tx beam of the associated SRS, or the indicator is set to a second value to indicate that the Tx beam transmitted by PRACH is at least partially based on the Rx beam of the associated SSB or CSI-RS.

[0185] In the second aspect, either alone or in combination with the first aspect, the indicator is associated with one or more reserved bits in the PDCCH command DCI.

[0186] In the third aspect, either alone or in combination with one or more of the first and second aspects, the indicator is associated with the PRACH associated indicator in the PDCCH command DCI.

[0187] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the PRACH association indicator is set to a first value to indicate that the Tx beam transmitted by the PRACH is at least partially based on the Tx beam of the associated SRS, or the PRACH association indicator is set to a second value to indicate that the Tx beam transmitted by the PRACH is at least partially based on the Rx beam of the associated SSB or CSI-RS.

[0188] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the indicator is associated with an SRS resource indication field, wherein a first code point in the SRS resource indication field indicates that the Tx beam transmitted by the PRACH is at least partially based on the Rx beam of the associated SSB or CSI-RS, and a second code point in the SRS resource indication field indicates that the Tx beam transmitted by the PRACH is at least partially based on the Tx beam of the associated SRS.

[0189] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, network nodes are associated with an uplink-intensive environment in which the uplink TRP differs from the downlink TRP.

[0190] although Figure 11 An example box of process 1100 is shown, but in some respects, process 1100 may include... Figure 11 The boxes depicted herein are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in the process 1100 may be executed in parallel.

[0191] Figure 12 This is a diagram illustrating an example process 1200 performed, for example, at a network node or a device of a network node, according to the present disclosure. Example process 1200 is an example in which a device or network node (e.g., network node 110) performs operations associated with PRACH transmission at least in part based on DCI.

[0192] like Figure 12 Further shown, in some aspects, process 1200 may include sending a configuration (block 1210) including a first preamble receive target power value and a second preamble receive target power value. For example, a network node (e.g., using...) Figure 15The transmitting component 1504 and / or communication manager 1506 depicted herein can transmit configurations including a first preamble receive target power value and a second preamble receive target power value, as described above.

[0193] like Figure 12 Further, in some aspects, process 1200 may include receiving the PRACH transmission using a first preamble to receive the target power value or a second preamble to receive the target power value, depending on whether the PRACH transmission is destined for an uplink-only TRP or a downlink TRP (box 1220). For example, network nodes (e.g., using...) Figure 15 The receiving component 1502 and / or communication manager 1506 described above may receive the PRACH transmission using a first preamble to receive the target power value or a second preamble to receive the target power value, depending on whether the PRACH transmission is destined for an uplink-only TRP or a downlink TRP.

[0194] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0195] In the first aspect, the PRACH transmission power used for PRACH transmission is based at least in part on a first preamble receive target power value or a second preamble receive target power value.

[0196] In the second aspect, either alone or in combination with the first aspect, the path loss between the UE and the uplink-only TRP is less than the path loss between the UE and the downlink TRP, and the Tx power associated with PRACH transmissions to the uplink-only TRP is less than the Tx power associated with PRACH transmissions to the downlink TRP.

[0197] In a third aspect, either alone or in combination with one or more of the first and second aspects, a configuration is made including a first set of parameters and a second set of parameters, wherein the first set of parameters includes one or more of a first preamble reception target power value, a first maximum number of preamble transmissions, or a first power ramp step value, and the second set of parameters includes one or more of a second preamble reception target power value, a second maximum number of preamble transmissions, or a second power ramp step value.

[0198] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the second set of parameters applies only to RACH transmitted via PDCCH command, or the second set of parameters applies to RACH and other PRACH transmissions transmitted via PDCCH command.

[0199] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the second set of parameters is configured for a four-step RACH process only, or the second set of parameters is configured for both a four-step RACH process and a two-step RACH process.

[0200] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, process 1200 includes: sending a PDCCH command DCI including an indicator, wherein a first set of parameters or a second set of parameters is at least partially based on the indicator.

[0201] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the indicator is set to a first value to indicate the use of a first set of parameters, or the indicator is set to a second value to indicate the use of a second set of parameters.

[0202] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the first set of parameters or the second set of parameters is at least partially based on the Tx beam transmitted by PRACH, wherein the first set of parameters is selected at least partially based on the Tx beam transmitted by PRACH and at least partially based on the Rx beam of the associated SSB or CSI-RS, or the second set of parameters is selected at least partially based on the Tx beam transmitted by PRACH and at least partially based on the Tx beam of the associated SRS.

[0203] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, process 1200 includes sending an indication via a PDCCH command DCI including an SRS resource indication field for using uplink path loss associated with the TCI state of the indicated SRS resource or for using path loss offset associated with the TCI state of the indicated SRS resource.

[0204] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the network node is associated with an uplink-intensive environment in which the uplink TRP differs from the downlink TRP.

[0205] although Figure 12 An example box of process 1200 is shown, but in some respects, process 1200 may include... Figure 12 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes, boxes, or boxes in a different manner. Alternatively, two or more boxes in the process 1200 may be executed in parallel.

[0206] Figure 13This is a diagram illustrating an example process 1300 performed, for example, at a network node or a device of a network node, according to the present disclosure. Example process 1300 is an example in which a device or network node (e.g., network node 110) performs operations associated with PRACH transmission at least in part based on DCI.

[0207] like Figure 13 As shown, in some aspects, process 1300 may include sending a PDCCH command DCI that includes a TCI field, which is used to indicate the TCI status for PRACH transmission via the PDCCH command (box 1310). For example, a network node (e.g., using...) Figure 15 The transmitting component 1504 and / or the communication manager 1506 depicted herein can transmit a PDCCH command DCI including a TCI field, which is used to indicate the TCI status for PRACH transmission via the PDCCH command, as described above.

[0208] like Figure 13 As further shown, in some aspects, process 1300 may include receiving PRACH transmissions via PDCCH commands (box 1320) at least in part based on the TCI field. For example, network nodes (e.g., using...) Figure 15 The receiving component 1502 and / or communication manager 1506 described herein can receive PRACH transmissions via PDCCH commands, at least in part, based on the TCI field, as described above.

[0209] Process 1300 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0210] In the first aspect, the TCI field indicates a TCI state identifier, or the TCI field indicates an active TCI state among one or more active TCI states, and the TCI field indicates a TCI code point mapped to the active TCI state.

[0211] In the second aspect, either alone or in combination with the first aspect, the TCI state is applied by default, wherein the TCI state is associated with the SSB, CSI-RS, or SRS, and the Tx beam and power control for PRACH transmission via PDCCH command is based at least in part on the TCI state, or the TCI state is applied at least in part on a single indicator in the PDCCH command DCI, wherein the Tx beam and power control for PRACH transmission via PDCCH command is based at least in part on the TCI state.

[0212] In the third aspect, either alone or in combination with one or more of the first and second aspects, the path loss offset associated with the TCI state is applied to power control.

[0213] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, network nodes are associated with an uplink-intensive environment in which the uplink TRP differs from the downlink TRP.

[0214] although Figure 13 An example box of process 1300 is shown, but in some respects, process 1300 may include... Figure 13 The boxes depicted in the text are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in the process 1300 may be executed in parallel.

[0215] Figure 14 This is a diagram of an example device 1400 for wireless communication according to the present disclosure. Device 1400 may be a UE, or a UE may include device 1400. In some aspects, device 1400 includes a receiving component 1402, a transmitting component 1404, and / or a communication manager 1406 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1406 is combined with... Figure 1 The described communication manager 140. As shown, device 1400 can communicate with another device 1408 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1402 and transmitting component 1404.

[0216] In some respects, device 1400 can be configured to perform the functions described herein. Figures 5 to 7 One or more operations described herein. Additionally or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as Figure 8 The process 800 Figure 9 The process 900 Figure 10 The process 1000 or a combination thereof. In some respects, Figure 14 The illustrated device 1400 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 14 One or more components shown can be combined Figure 2Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0217] Receiver 1402 may receive communications from device 1408, such as reference signals, control information, data communications, or combinations thereof. Receiver 1402 may provide the received communications to one or more other components of device 1400. In some aspects, receiver 1402 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications, and may provide the processed signals to the one or more other components of device 1400. In some aspects, receiver 1402 may include combinations of... Figure 2 The described UE includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0218] Transmitting component 1404 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1408. In some aspects, one or more other components of device 1400 may generate communications and provide the generated communications to transmitting component 1404 for transmission to device 1408. In some aspects, transmitting component 1404 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1408. In some aspects, transmitting component 1404 may include combinations of... Figure 2 The described UE may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1404 may co-located with the receive component 1402 in one or more transceivers.

[0219] The communication manager 1406 may support the operation of the receiving component 1402 and / or the transmitting component 1404. For example, the communication manager 1406 may receive information associated with configuring the reception of communications by the receiving component 1402 and / or the transmission of communications by the transmitting component 1404. Additionally or alternatively, the communication manager 1406 may generate control information and / or provide control information to the receiving component 1402 and / or the transmitting component 1404 to control the reception and / or transmission of communications.

[0220] The receiving component 1402 can receive a PDCCH command DCI including an indicator used to indicate whether the Tx beam of the PRACH transmission is at least partially based on the Tx beam of the associated SRS or at least partially based on the Rx beam of the associated SSB or CSI-RS. The transmitting component 1404 can transmit PRACH transmissions at least partially based on the indicator.

[0221] The receiving component 1402 can receive a configuration including a first preamble receive target power value and a second preamble receive target power value. The transmitting component 1404 can transmit PRACH using either the first preamble receive target power value or the second preamble receive target power value, depending on whether the PRACH transmission is destined for an uplink-only TRP or a downlink TRP.

[0222] Communication manager 1406 can select a first preamble receive target power value or a second preamble receive target power value. Communication manager 1406 can determine the PRACH transmit power for PRACH transmission based at least in part on the first preamble receive target power value or the second preamble receive target power value. Receiver component 1402 can receive a PDCCH command DCI including an indicator. Communication manager 1406 can select the first preamble receive target power value or the second preamble receive target power value based at least in part on the indicator. The communication manager 1406 can select a first preamble receive target power value or a second preamble receive target power value based at least partially on the Tx beam transmitted via PRACH, wherein the first preamble receive target power value is selected at least partially based on the Tx beam transmitted via PRACH and at least partially based on the Rx beam of the associated SSB or CSI-RS, or the second preamble receive target power value is selected at least partially based on the Tx beam transmitted via PRACH and at least partially based on the Tx beam of the associated SRS. The receiving component 1402 can receive an indication via a PDCCH command DCI including an SRS resource indication field for using uplink path loss associated with the TCI state of the indicated SRS resource or using path loss offset associated with the TCI state of the indicated SRS resource.

[0223] The receiving component 1402 can receive a PDCCH command DCI including a TCI field, which indicates the TCI status for PRACH transmission via the PDCCH command. The transmitting component 1404 can transmit PRACH transmission via the PDCCH command based at least in part on the TCI field.

[0224] The communication manager 1406 may apply the TCI state by default, wherein the TCI state is associated with SSB, CSI-RS, or SRS, and the Tx beam and power control for PRACH transmission via PDCCH command is at least partially based on the TCI state. The communication manager 1406 may also apply the TCI state at least partially based on a single indicator in the PDCCH command DCI, wherein the Tx beam and power control for PRACH transmission via PDCCH command is at least partially based on the TCI state. The communication manager 1406 may apply the path loss offset associated with the TCI state to the power control.

[0225] Figure 14 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 14 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 14 The two or more components shown can be implemented within a single component, or Figure 14 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 14 The executable description of the collection of (one or more) components shown is composed of Figure 14 Another set of components shown performs one or more functions.

[0226] Figure 15 This is a diagram of an example device 1500 for wireless communication according to the present disclosure. Device 1500 may be a network node, or a network node may include device 1500. In some aspects, device 1500 includes a receiving component 1502, a transmitting component 1504, and / or a communication manager 1506 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 1506 is combined with... Figure 1 The described communication manager 150. As shown, device 1500 can communicate with another device 1508 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1502 and transmitting component 1504.

[0227] In some respects, device 1500 can be configured to perform the functions described herein. Figures 5 to 7One or more operations described herein. Additionally or alternatively, the apparatus 1500 may be configured to perform one or more processes described herein, such as Figure 11 Process 1100 Figure 12 Process 1200 Figure 13 The process 1300 or a combination thereof. In some respects, Figure 15 The illustrated device 1500 and / or one or more components may include a combination Figure 2 One or more components of the described network node. Additionally or alternatively, Figure 15 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0228] Receiver 1502 may receive communications from device 1508, such as reference signals, control information, data communications, or combinations thereof. Receiver 1502 may provide the received communications to one or more other components of device 1500. In some aspects, receiver 1502 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications, and may provide the processed signals to the one or more other components of device 1500. In some aspects, receiver 1502 may include combinations of... Figure 2 The described network node may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, receiver component 1502 and / or transmitter component 1504 may include or be included in a network interface. The network interface may be configured to acquire and / or output signals for device 1500 via one or more communication links, such as backhaul links, midhaul links, and / or fronthaul links.

[0229] Transmitting component 1504 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1508. In some aspects, one or more other components of device 1500 may generate communications and provide the generated communications to transmitting component 1504 for transmission to device 1508. In some aspects, transmitting component 1504 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1508. In some aspects, transmitting component 1504 may include combinations of... Figure 2 The described network node includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1504 may co-located with the receive component 1502 in one or more transceivers.

[0230] The communication manager 1506 may support the operation of the receiving component 1502 and / or the transmitting component 1504. For example, the communication manager 1506 may receive information associated with configuring the reception of communications by the receiving component 1502 and / or the transmission of communications by the transmitting component 1504. Additionally or alternatively, the communication manager 1506 may generate control information and / or provide control information to the receiving component 1502 and / or the transmitting component 1504 to control the reception and / or transmission of communications.

[0231] Transmitting component 1504 can transmit a PDCCH command DCI including an indicator indicating whether the Tx beam of the PRACH transmission is at least partially based on the Tx beam of the associated SRS or at least partially based on the Rx beam of the associated SSB or CSI-RS. Receiving component 1502 can receive the PRACH transmission at least partially based on the indicator.

[0232] Transmitting component 1504 can transmit a configuration including a first preamble receive target power value and a second preamble receive target power value. Receiving component 1502 can receive PRACH transmissions using either the first preamble receive target power value or the second preamble receive target power value, depending on whether the PRACH transmission is destined for an uplink-only TRP or a downlink TRP.

[0233] Transmitting component 1504 may transmit a PDCCH command DCI including an indicator, wherein a first preamble receive target power value or a second preamble receive target power value is at least partially based on the indicator. Transmitting component 1504 may transmit an indication via a PDCCH command DCI including an SRS resource indication field for using uplink path loss associated with the TCI state of the indicated SRS resource or using path loss offset associated with the TCI state of the indicated SRS resource.

[0234] Transmitting component 1504 can transmit a PDCCH command DCI including a TCI field, which indicates the TCI status for PRACH transmission via the PDCCH command. Receiving component 1502 can receive PRACH transmissions via the PDCCH command based at least in part on the TCI field.

[0235] Figure 15 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 15 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 15 The two or more components shown can be implemented within a single component, or Figure 15 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 15 The executable description of the collection of (one or more) components shown is composed of Figure 15 Another set of components shown performs one or more functions.

[0236] The following provides an overview of some aspects of this disclosure.

[0237] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving physical downlink control channel (PDCCH) command downlink control information (DCI) including an indicator for indicating whether a transmit (Tx) beam of a physical random access channel (PRACH) transmission is at least partially based on an associated sounding reference signal (SRS) Tx beam or at least partially based on an associated synchronization block (SSB) or channel state information reference signal (CSI-RS) receive (Rx) beam; and transmitting the PRACH transmission at least partially based on the indicator.

[0238] Aspect 2: According to the method of aspect 1, wherein the indicator is a single bit, and: the indicator is set to a first value to indicate that the Tx beam transmitted by the PRACH is at least partially based on the Tx beam of the associated SRS; or the indicator is set to a second value to indicate that the Tx beam transmitted by the PRACH is at least partially based on the Rx beam of the associated SSB or CSI-RS.

[0239] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the indicator is associated with one or more reserved bits in the PDCCH command DCI.

[0240] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the indicator is associated with the PRACH association indicator in the PDCCH command DCI.

[0241] Aspect 5: The method according to aspect 4, wherein: the PRACH association indicator is set to a first value to indicate that the Tx beam transmitted by the PRACH is at least partially based on the Tx beam of the associated SRS; or the PRACH association indicator is set to a second value to indicate that the Tx beam transmitted by the PRACH is at least partially based on the Rx beam of the associated SSB or CSI-RS.

[0242] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the indicator is associated with an SRS resource indication field, wherein a first code point in the SRS resource indication field indicates that the Tx beam transmitted by the PRACH is at least partially based on the Rx beam of the associated SSB or CSI-RS, and a second code point in the SRS resource indication field indicates that the Tx beam transmitted by the PRACH is at least partially based on the Tx beam of the associated SRS.

[0243] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the UE is associated with an uplink-intensive environment in which the uplink transmit / receive point (TRP) is different from the downlink TRP.

[0244] Aspect 8: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a configuration including a first preamble receive target power value and a second preamble receive target power value; and, depending on whether a physical random access channel (PRACH) transmission is directed to an uplink transmit-receive point (TRP) or a downlink TRP, transmitting the PRACH transmission using the first preamble receive target power value or the second preamble receive target power value.

[0245] Aspect 9: According to the method of aspect 8, the method further includes: selecting a first preamble receive target power value or a second preamble receive target power value; and determining a PRACH transmit power for the PRACH transmit at least in part based on the first preamble receive target power value or the second preamble receive target power value.

[0246] Aspect 10: The method according to any one of Aspects 8 to 9, wherein the path loss between the UE and the uplink-only TRP is less than the path loss between the UE and the downlink TRP, and the transmit (Tx) power associated with the PRACH transmission to the uplink-only TRP is less than the Tx power associated with the PRACH transmission to the downlink TRP.

[0247] Aspect 11: The method according to any one of Aspects 8 to 10, wherein the configuration includes a first set of parameters and a second set of parameters, wherein the first set of parameters includes one or more of the first preamble reception target power value, the first maximum number of preamble transmissions, or the first power ramp step value, and the second set of parameters includes one or more of the second preamble reception target power value, the second maximum number of preamble transmissions, or the second power ramp step value.

[0248] Aspect 12: According to the method of aspect 11, the second set of parameters applies only to random access channels (RACH) via PDCCH commands, or the second set of parameters applies to RACH and other PRACH transmissions via PDCCH commands.

[0249] Aspect 13: According to the method of aspect 11, the second set of parameters is configured for a four-step RACH process only, or the second set of parameters is configured for both the four-step RACH process and a two-step RACH process.

[0250] Aspect 14: The method according to aspect 11, the method further comprising: receiving physical downlink control channel (PDCCH) command downlink control information (DCI) including an indicator; and selecting either the first set of parameters or the second set of parameters based at least in part on the indicator.

[0251] Aspect 15: The method according to aspect 14, wherein: the indicator is set to a first value to indicate the first set of parameters to be used; or the indicator is set to a second value to indicate the second set of parameters to be used.

[0252] Aspect 16: The method according to aspect 11, the method further comprising: selecting either the first set of parameters or the second set of parameters based at least in part on the transmit (Tx) beam transmitted by the PRACH, wherein: the set of parameters is selected at least in part on the Tx beam transmitted by the PRACH based at least in part on the receive (Rx) beam of an associated synchronization block (SSB) or channel state information reference signal (CSI-RS), or the second set of parameters is selected at least in part on the Tx beam transmitted by the PRACH based at least in part on the Tx beam of an associated sounding reference signal (SRS).

[0253] Aspect 17: The method according to any one of Aspects 8 to 16, the method further comprising: receiving, via a Physical Downlink Control Channel (PDCCH) command downlink control information (DCI) including a probe reference signal (SRS) resource indication field, an indication for using uplink path loss associated with the transmit configuration indicator (TCI) state of the indicated SRS resource or using path loss offset associated with the TCI state of the indicated SRS resource.

[0254] Aspect 18: The method according to any one of Aspects 8 to 17, wherein the UE is associated with an uplink-intensive environment in which the uplink transmit / receive point (TRP) is different from the downlink TRP.

[0255] Aspect 19: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving physical downlink control information (DCI) including a transmission configuration indicator (TCI) field for indicating a TCI state for physical random access channel (PRACH) transmission via PDCCH command; and transmitting the PRACH transmission via PDCCH command based at least in part on the TCI field.

[0256] Aspect 20: The method according to aspect 19, wherein: the TCI field indicates a TCI state identifier; or the TCI field indicates an active TCI state among one or more active TCI states, and the TCI field indicates a TCI code point mapped to the active TCI state.

[0257] Aspect 21: The method according to any one of Aspects 19 to 20, further comprising: applying the TCI state by default, wherein the TCI state is associated with a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), or a sounding reference signal (SRS), and the transmit (Tx) beam and power control for the PRACH transmission via PDCCH command is based at least in part on the TCI state; or applying the TCI state at least in part on a bit indicator in the PDCCH command DCI, wherein the Tx beam and power control for the PRACH transmission via PDCCH command are based at least in part on the TCI state.

[0258] Aspect 22: According to the method of aspect 21, the method further includes: applying a path loss offset associated with the TCI state to the power control.

[0259] Aspect 23: The method according to any one of Aspects 19 to 22, wherein the UE is associated with an uplink-intensive environment in which the uplink transmit / receive point (TRP) is different from the downlink TRP.

[0260] Aspect 24: A method of wireless communication performed by a network node, the method comprising: transmitting Physical Downlink Control Channel (PDCCH) command downlink control information (DCI) including an indicator for indicating whether a transmit (Tx) beam of a Physical Random Access Channel (PRACH) transmission is at least partially based on an associated sounding reference signal (SRS) Tx beam or at least partially based on an associated synchronization block (SSB) or channel state information reference signal (CSI-RS) receive (Rx) beam; and receiving the PRACH transmission at least partially based on the indicator.

[0261] Aspect 25: According to the method of aspect 24, wherein the indicator is a single bit, and: the indicator is set to a first value to indicate that the Tx beam transmitted by the PRACH is at least partially based on the Tx beam of the associated SRS; or the indicator is set to a second value to indicate that the Tx beam transmitted by the PRACH is at least partially based on the Rx beam of the associated SSB or CSI-RS.

[0262] Aspect 26: The method according to any one of Aspects 24 to 25, wherein the indicator is associated with one or more reserved bits in the PDCCH command DCI.

[0263] Aspect 27: The method according to any one of Aspects 24 to 26, wherein the indicator is associated with a PRACH associated indicator in the PDCCH command DCI.

[0264] Aspect 28: The method according to aspect 27, wherein: the PRACH association indicator is set to a first value to indicate that the Tx beam transmitted by the PRACH is at least partially based on the Tx beam of the associated SRS; or the PRACH association indicator is set to a second value to indicate that the Tx beam transmitted by the PRACH is at least partially based on the Rx beam of the associated SSB or CSI-RS.

[0265] Aspect 29: The method according to any one of Aspects 24 to 28, wherein the indicator is associated with an SRS resource indication field, wherein a first code point in the SRS resource indication field indicates that the Tx beam transmitted by the PRACH is at least partially based on the Rx beam of the associated SSB or CSI-RS, and a second code point in the SRS resource indication field indicates that the Tx beam transmitted by the PRACH is at least partially based on the Tx beam of the associated SRS.

[0266] Aspect 30: The method according to any one of Aspects 24 to 29, wherein the network node is associated with an uplink-intensive environment in which the uplink transmit / receive point (TRP) is different from the downlink TRP.

[0267] Aspect 31: A method for wireless communication performed by a network node, the method comprising: transmitting a configuration including a first preamble receive target power value and a second preamble receive target power value; and receiving the PRACH transmission using the first preamble receive target power value or the second preamble receive target power value, depending on whether the physical random access channel (PRACH) transmission is directed to an uplink transmit-receive point (TRP) or a downlink TRP.

[0268] Aspect 32: According to the method of aspect 31, wherein the PRACH transmission power for the PRACH transmission is at least partially based on the first preamble receive target power value or the second preamble receive target power value.

[0269] Aspect 33: The method according to any one of Aspects 31 to 32, wherein the path loss between the user equipment (UE) and the uplink-only TRP is less than the path loss between the UE and the downlink TRP, and the transmit (Tx) power associated with the PRACH transmission to the uplink-only TRP is less than the Tx power associated with the PRACH transmission to the downlink TRP.

[0270] Aspect 34: The method according to any one of Aspects 31 to 33, wherein the configuration includes a first set of parameters and a second set of parameters, wherein the first set of parameters includes a first preamble reception target power value, a first maximum number of preamble transmissions and a first power ramp step value, and the second set of parameters includes a second preamble reception target power value, a second maximum number of preamble transmissions and a second power ramp step.

[0271] Aspect 35: According to the method of aspect 34, the second set of parameters applies only to random access channels (RACH) via PDCCH commands, or the second set of parameters applies to RACH and other PRACH transmissions via PDCCH commands.

[0272] Aspect 36: According to the method of aspect 34, the second set of parameters is configured for a four-step RACH process only, or the second set of parameters is configured for both the four-step RACH process and a two-step RACH process.

[0273] Aspect 37: The method according to any one of Aspects 31 to 36, the method further comprising: transmitting Physical Downlink Control Channel (PDCCH) command downlink control information (DCI) including an indicator, wherein the first preamble receiving target power value or the second preamble receiving target power value is at least partially based on the indicator.

[0274] Aspect 38: The method according to aspect 37, wherein: the indicator is set to a first value to indicate that the target power value is to be received using the first preamble; or the indicator is set to a second value to indicate that the target power value is to be received using the second preamble.

[0275] Aspect 39: The method according to any one of Aspects 31 to 38, wherein: the first preamble receive target power value or the second preamble receive target power value is at least partially based on the transmit (Tx) beam transmitted by the PRACH, wherein: the first preamble receive target power value is selected at least partially based on the Tx beam transmitted by the PRACH and at least partially based on the receive (Rx) beam of the associated synchronization block (SSB) or channel state information reference signal (CSI-RS), or the second preamble receive target power value is selected at least partially based on the Tx beam transmitted by the PRACH and at least partially based on the Tx beam of the associated sounding reference signal (SRS).

[0276] Aspect 40: The method according to any one of aspects 31 to 39, the method further comprising: transmitting an indication for using uplink path loss associated with the transmit configuration indicator (TCI) state of the indicated SRS resource or using path loss offset associated with the TCI state of the indicated SRS resource via a physical downlink control channel (PDCCH) command downlink control information (DCI) including a probe reference signal (SRS) resource indication field.

[0277] Aspect 41: The method according to any one of Aspects 31 to 40, wherein the network node is associated with an uplink-intensive environment in which the uplink transmit / receive point (TRP) is different from the downlink TRP.

[0278] Aspect 42: A method of wireless communication performed by a network node, the method comprising: transmitting Physical Downlink Control Channel (PDCCH) command downlink control information (DCI) including a transmission configuration indicator (TCI) field, the transmission configuration indicator (TCI) field indicating a TCI state for transmission via Physical Random Access Channel (PRACH) commanded by the PDCCH; and receiving the PRACH transmission via the PDCCH command based at least in part on the TCI field.

[0279] Aspect 43: The method according to aspect 42, wherein: the TCI field indicates a TCI state identifier; or the TCI field indicates an active TCI state among one or more active TCI states, and the TCI field indicates a TCI code point mapped to the active TCI state.

[0280] Aspect 44: The method according to any one of Aspects 42 to 43, wherein: the TCI state is applied by default, wherein the TCI state is associated with a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), or a sounding reference signal (SRS), and the transmit (Tx) beam and power control for the PRACH transmission via PDCCH command are based at least in part on the TCI state; or the TCI state is applied at least in part on a single indicator in the PDCCH command DCI, wherein the Tx beam and power control for the PRACH transmission via PDCCH command are based at least in part on the TCI state.

[0281] Aspect 45: The method according to aspect 44, wherein the path loss offset associated with the TCI state is applied to the power control.

[0282] Aspect 46: The method according to any one of Aspects 42 to 45, wherein the network node is associated with an uplink-intensive environment in which the uplink transmit / receive point (TRP) is different from the downlink TRP.

[0283] Aspect 47: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more aspects of aspects 1 to 23.

[0284] Aspect 48: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 23.

[0285] Aspect 49: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 23.

[0286] Aspect 50: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the methods described in accordance with one or more aspects 1 to 23.

[0287] Aspect 51: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more aspects 1 to 23.

[0288] Aspect 52: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more aspects 1 to 23.

[0289] Aspect 53: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more aspects of aspects 1 to 23.

[0290] Aspect 54: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more aspects of aspects 24 to 46.

[0291] Aspect 55: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more aspects 24 to 46.

[0292] Aspect 56: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 24 to 46.

[0293] Aspect 57: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the methods described in one or more of aspects 24 to 46.

[0294] Aspect 58: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more aspects 24 to 46.

[0295] Aspect 59: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more aspects of aspects 24 to 46.

[0296] Aspect 60: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more aspects of aspects 24 to 46.

[0297] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit aspects to the precise forms disclosed. Modifications and variations can be made based on the foregoing disclosure, or from various aspects of practice.

[0298] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and at least one of software or firmware. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in various forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods, at least in part, based on the description herein. Unless otherwise stated, a component configured to perform a function means that the component has the capability to perform that function, but it is not necessary for the component to actually perform that function.

[0299] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0300] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of the following: a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0301] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are interchangeable with “one or more.” Similarly, as used herein, the article “the” is intended to include one or more items mentioned in connection with the article “the” and is interchangeable with “one or more.” Furthermore, as used herein, the terms “collection” and “group” are intended to include one or more items and are interchangeable with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Moreover, as used herein, the terms “having” and similar terms are intended as open-ended terms that do not limit the elements they modify (e.g., “having” A may also have B). Additionally, the phrase “based on” is intended to mean “based on or otherwise related to” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either of the two” or “only one of them”). It should be understood that “one or more” is equivalent to “at least one”.

[0302] Although specific combinations of features are set forth in the claims or disclosed in the description, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically stated in the claims or disclosed in the description. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being configured to individually or jointly enable the UE: Receive Physical Downlink Control Channel (PDCCH) command downlink control information (DCI) including an indicator used to indicate whether the transmit (Tx) beam transmitted by the Physical Random Access Channel (PRACH) is a Tx beam at least partially based on an associated sounding reference signal (SRS) or a receive (Rx) beam at least partially based on an associated synchronization block (SSB) or channel state information reference signal (CSI-RS); and The PRACH transmission is sent at least in part based on the indicator.

2. The apparatus of claim 1, wherein the indicator is a single bit, and: The indicator is set to a first value to indicate that the Tx beam transmitted by the PRACH is at least partially based on the Tx beam of the associated SRS; or The indicator is set to a second value to indicate that the Tx beam transmitted by the PRACH is at least partially based on the Rx beam of the associated SSB or CSI-RS.

3. The apparatus of claim 1, wherein the indicator is associated with one or more reserved bits in the PDCCH command DCI.

4. The apparatus of claim 1, wherein the indicator is associated with a PRACH association indicator in the PDCCH command DCI.

5. The apparatus according to claim 4, wherein: The PRACH association indicator is set to a first value to indicate that the Tx beam transmitted by the PRACH is at least partially based on the Tx beam of the associated SRS; or The PRACH association indicator is set to a second value to indicate that the Tx beam transmitted by the PRACH is at least partially based on the Rx beam of the associated SSB or CSI-RS.

6. The apparatus of claim 1, wherein the indicator is associated with an SRS resource indication field, wherein a first code point in the SRS resource indication field indicates that the Tx beam transmitted by the PRACH is at least partially based on the Rx beam of the associated SSB or CSI-RS, and a second code point in the SRS resource indication field indicates that the Tx beam transmitted by the PRACH is at least partially based on the Tx beam of the associated SRS.

7. The apparatus of claim 1, wherein the UE is associated with an uplink-intensive environment, wherein the uplink transmit / receive point (TRP) is different from the downlink TRP.

8. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being configured to individually or jointly enable the UE: The configuration includes receiving a first preamble target power value and a second preamble target power value. as well as Depending on whether the Physical Random Access Channel (PRACH) transmission is directed to an uplink-only transmit-receive point (TRP) or a downlink TRP, the PRACH transmission is performed using either the first preamble receive target power value or the second preamble receive target power value.

9. The apparatus of claim 8, wherein the one or more processors are configured to individually or jointly cause the UE to: Select either the first preamble receive target power value or the second preamble receive target power value; and The PRACH transmission power for the PRACH transmission is determined at least in part based on the first preamble receive target power value or the second preamble receive target power value.

10. The apparatus of claim 8, wherein the configuration includes a first set of parameters and a second set of parameters, wherein the first set of parameters includes one or more of the first preamble reception target power value, the first maximum number of preamble transmissions, or the first power ramp step value, and the second set of parameters includes one or more of the second preamble reception target power value, the second maximum number of preamble transmissions, or the second power ramp step value.

11. The apparatus of claim 10, wherein the second set of parameters applies only to random access channels (RACH) via PDCCH commands, or the second set of parameters applies to RACH and other PRACH transmissions via PDCCH commands.

12. The apparatus of claim 10, wherein the second set of parameters is configured for a four-step RACH process only, or the second set of parameters is configured for both the four-step RACH process and a two-step RACH process.

13. The apparatus of claim 10, wherein the one or more processors are configured to individually or jointly cause the UE to: Receive Physical Downlink Control Channel (PDCCH) commands and Downlink Control Information (DCI) including indicators; and The first set of parameters or the second set of parameters is selected at least in part based on the indicator, wherein: The indicator is set to a first value to indicate the first set of parameters to be used; or The indicator is set to a second value to indicate the second set of parameters to be used.

14. The apparatus of claim 10, wherein the one or more processors are configured to individually or jointly cause the UE to: The first set of parameters or the second set of parameters is selected at least in part based on the transmit (Tx) beam transmitted by the PRACH, wherein: The first set of parameters is selected at least in part based on the Tx beam transmitted by the PRACH, and at least in part based on the received (Rx) beam of the associated synchronization signal block (SSB) or channel state information reference signal (CSI-RS), or The second set of parameters is selected at least in part based on the Tx beam transmitted by the PRACH and at least in part based on the Tx beam of the associated sounding reference signal (SRS).

15. The apparatus of claim 8, wherein the one or more processors are configured to individually or jointly cause the UE to: The Physical Downlink Control Channel (PDCCH) commands downlink control information (DCI) via a probe reference signal (SRS) resource indication field, and receives an indication for using uplink path loss associated with the transmit configuration indicator (TCI) state of the indicated SRS resource or for using path loss offset associated with the TCI state of the indicated SRS resource.

16. An apparatus for conducting wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being configured to individually or jointly enable the UE: Receive Physical Downlink Control Channel (PDCCH) command downlink control information (DCI) including a Transmission Configuration Indicator (TCI) field, the TCI field indicating the TCI status for transmission via the Physical Random Access Channel (PRACH) through the PDCCH command; and The PRACH transmission via the PDCCH command is sent at least in part based on the TCI field.

17. The apparatus of claim 16, wherein the TCI field indicates a TCI status identifier.

18. The apparatus of claim 16, wherein the TCI field indicates an active TCI state in one or more active TCI states, and the TCI field indicates a TCI code point mapped to the active TCI state.

19. The apparatus of claim 16, wherein the one or more processors are configured to individually or jointly cause the UE to: The TCI state is applied by default, wherein the TCI state is associated with a synchronization signal block (SSB), channel state information reference signal (CSI-RS), or sounding reference signal (SRS), and the transmit (Tx) beam and power control for the PRACH transmission commanded by the PDCCH is based at least in part on the TCI state; or The TCI state is applied at least in part based on a single indicator in the PDCCH command DCI, wherein the Tx beam and the power control for the PRACH transmitted via the PDCCH command are at least in part based on the TCI state.

20. The apparatus of claim 19, wherein the one or more processors are configured to individually or jointly cause the UE to: The path loss offset associated with the TCI state is applied to the power control.

Images