[go: up one dir, main page]

WO2025199786A1 - Émissions de canal d'accès aléatoire physique sur la base d'informations de commande de liaison descendante - Google Patents

Émissions de canal d'accès aléatoire physique sur la base d'informations de commande de liaison descendante

Info

Publication number
WO2025199786A1
WO2025199786A1 PCT/CN2024/084009 CN2024084009W WO2025199786A1 WO 2025199786 A1 WO2025199786 A1 WO 2025199786A1 CN 2024084009 W CN2024084009 W CN 2024084009W WO 2025199786 A1 WO2025199786 A1 WO 2025199786A1
Authority
WO
WIPO (PCT)
Prior art keywords
indicator
prach transmission
prach
transmission
uplink
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/084009
Other languages
English (en)
Inventor
Shaozhen GUO
Mostafa KHOSHNEVISAN
Yi Huang
Xiaoxia Zhang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Priority to PCT/CN2024/084009 priority Critical patent/WO2025199786A1/fr
Publication of WO2025199786A1 publication Critical patent/WO2025199786A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal

Definitions

  • 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, configured to cause the UE to: receive a configuration that includes a first preamble received target power value and a second preamble received target power value; and transmit a PRACH transmission using the first preamble received target power value or the second preamble received target power value depending on whether the PRACH transmission is to an uplink-only transmission-reception point (TRP) or a downlink TRP.
  • TRP transmission-reception point
  • An uplink dense deployment may be used to improve a coverage and/or a capacity of an uplink direction.
  • An uplink receive (Rx) point e.g., an uplink-only node
  • Downlink signals and/or downlink channels transmitted from a network node may be from a different node (e.g., a macro node, a central node, a serving cell, or a serving base station) .
  • Uplink Rx points may be connected to the network node via backhaul links.
  • the uplink dense deployment may help to reduce an uplink pathloss, which may be helpful when an uplink coverage is a bottleneck.
  • the uplink dense deployment may help in term of deployment cost and/or complexity since the uplink Rx points do not transmit any downlink signal.
  • the uplink Rx points simply receive an uplink signal and send the uplink signal to the network node with or without processing.
  • Such technological improvements may be associated with new frequency band expansion, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, disaggregated network architectures and network topology expansion, device aggregation, advanced duplex communication, sidelink and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced capability (RedCap) UE functionality, industrial connectivity, multiple-subscriber implementations, high-precision positioning, radio frequency (RF) sensing, and/or artificial intelligence or machine learning (AI/ML) , among other examples.
  • NTN non-terrestrial network
  • disaggregated network architectures and network topology expansion device aggregation
  • advanced duplex communication including passive or ambient IoT
  • RedCap reduced capability
  • industrial connectivity multiple-subscriber implementations
  • high-precision positioning radio frequency (RF) sensing
  • AI/ML artificial intelligence or machine learning
  • These technological improvements may support use cases such as wireless backhauls, wireless data centers, extended reality (XR) and metaverse applications, meta services for supporting vehicle connectivity, holographic and mixed reality communication, autonomous and collaborative robots, vehicle platooning and cooperative maneuvering, sensing networks, gesture monitoring, human-brain interfacing, digital twin applications, asset management, and universal coverage applications using non-terrestrial and/or aerial platforms, among other examples.
  • use cases such as wireless backhauls, wireless data centers, extended reality (XR) and metaverse applications, meta services for supporting vehicle connectivity, holographic and mixed reality communication, autonomous and collaborative robots, vehicle platooning and cooperative maneuvering, sensing networks, gesture monitoring, human-brain interfacing, digital twin applications, asset management, and universal coverage applications using non-terrestrial and/or aerial platforms, among other examples.
  • XR extended reality
  • metaverse applications meta services for supporting vehicle connectivity
  • holographic and mixed reality communication autonomous and collaborative robots
  • vehicle platooning and cooperative maneuvering sensing networks
  • gesture monitoring human-bra
  • Fig. 1 is a diagram illustrating an example of a wireless communication network 100 in accordance with the present disclosure.
  • the wireless communication network 100 may be or may include elements of a 5G (or NR) network or a 6G network, among other examples.
  • the wireless communication network 100 may include multiple network nodes 110, shown as a network node (NN) 110a, a network node 110b, a network node 110c, and a network node 110d.
  • the network nodes 110 may support communications with multiple UEs 120, shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e.
  • the network nodes 110 and the UEs 120 of the wireless communication network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, carriers, and/or channels. For example, devices of the wireless communication network 100 may communicate using one or more operating bands.
  • multiple wireless networks 100 may be deployed in a given geographic area.
  • Each wireless communication network 100 may support a particular RAT (which may also be referred to as an air interface) and may operate on one or more carrier frequencies in one or more frequency ranges.
  • RATs include a 4G RAT, a 5G/NR RAT, and/or a 6G RAT, among other examples.
  • each RAT in the geographic area may operate on different frequencies to avoid interference with one another.
  • FR1 frequency range designations FR1 (410 MHz through 7.125 GHz) , FR2 (24.25 GHz through 52.6 GHz) , FR3 (7.125 GHz through 24.25 GHz) , FR4a or FR4-1 (52.6 GHz through 71 GHz) , FR4 (52.6 GHz through 114.25 GHz) , and FR5 (114.25 GHz through 300 GHz) .
  • FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in some documents and articles.
  • FR2 is often referred to (interchangeably) as a “millimeter wave” band in some documents and articles, despite being different than the extremely high frequency (EHF) band (30 GHz through 300 GHz) , which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
  • EHF extremely high frequency
  • ITU International Telecommunications Union
  • the frequencies between FR1 and FR2 are often referred to as mid-band frequencies, which include FR3.
  • Frequency bands falling within FR3 may inherit FR1 characteristics or FR2 characteristics, and thus may effectively extend features of FR1 or FR2 into mid-band frequencies.
  • the wireless communication network 100 may implement dynamic spectrum sharing (DSS) , in which multiple RATs (for example, 4G/LTE and 5G/NR) are implemented with dynamic bandwidth allocation (for example, based on user demand) in a single frequency band.
  • DSS dynamic spectrum sharing
  • multiple RATs for example, 4G/LTE and 5G/NR
  • dynamic bandwidth allocation for example, based on user demand
  • a network node 110 may be implemented as a single physical node (for example, a single physical structure) or may be implemented as two or more physical nodes (for example, two or more distinct physical structures) .
  • a network node 110 may be a device or system that implements part of a radio protocol stack, a device or system that implements a full radio protocol stack (such as a full gNB protocol stack) , or a collection of devices or systems that collectively implement the full radio protocol stack.
  • a network node 110 may be an aggregated network node (having an aggregated architecture) , meaning that the network node 110 may implement a full radio protocol stack that is physically and logically integrated within a single node (for example, a single physical structure) in the wireless communication network 100.
  • an aggregated network node 110 may consist of a single standalone base station or a single TRP that uses a full radio protocol stack to enable or facilitate communication between a UE 120 and a core network of the wireless communication network 100.
  • a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station) , meaning that the network node 110 may implement a radio protocol stack that is physically distributed and/or logically distributed among two or more nodes in the same geographic location or in different geographic locations.
  • a disaggregated network node may have a disaggregated architecture.
  • disaggregated network nodes 110 may be used in an integrated access and backhaul (IAB) network, in an open radio access network (O-RAN) (such as a network configuration in compliance with the O-RAN Alliance) , or in a virtualized radio access network (vRAN) , also known as a cloud radio access network (C-RAN) , to facilitate scaling by separating base station functionality into multiple units that can be individually deployed.
  • IAB integrated access and backhaul
  • O-RAN open radio access network
  • vRAN virtualized radio access network
  • C-RAN cloud radio access network
  • Some network nodes 110 may provide communication coverage for a particular geographic area.
  • the term “cell” can refer to a coverage area of a network node 110 or to a network node 110 itself, depending on the context in which the term is used.
  • a network node 110 may support one or multiple (for example, three) cells.
  • a network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell.
  • a macro cell may cover a relatively large geographic area (for example, several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions.
  • a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions.
  • a femto cell may cover a relatively small geographic area (for example, a home) and may allow restricted access by UEs 120 having association with the femto cell (for example, UEs 120 in a closed subscriber group (CSG) ) .
  • a network node 110 for a macro cell may be referred to as a macro network node.
  • a network node 110 for a pico cell may be referred to as a pico network node.
  • a network node 110 for a femto cell may be referred to as a femto network node or an in-home network node.
  • a cell may not necessarily be stationary.
  • the geographic area of the cell may move according to the location of an associated mobile network node 110 (for example, a train, a satellite base station, an unmanned aerial vehicle, or an NTN network node) .
  • an associated mobile network node 110 for example, a train, a satellite base station, an unmanned aerial vehicle, or an NTN network node
  • the wireless communication network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, aggregated network nodes, and/or disaggregated network nodes, among other examples.
  • the network node 110a may be a macro network node for a macro cell 130a
  • the network node 110b may be a pico network node for a pico cell 130b
  • the network node 110c may be a femto network node for a femto cell 130c.
  • network nodes 110 may generally transmit at different power levels, serve different coverage areas, and/or have different impacts on interference in the wireless communication network 100 than other types of network nodes 110.
  • macro network nodes may have a high transmit power level (for example, 5 to 40 watts)
  • pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (for example, 0.1 to 2 watts) .
  • a network node 110 may be, may include, or may operate as an RU, a TRP, or a base station that communicates 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.
  • Downlink (or “DL” ) refers to a communication direction from a network node 110 to a UE 120
  • uplink or “UL”
  • Downlink channels may include one or more control channels and one or more data channels.
  • An uplink control channel may be used to transmit uplink control information (UCI) (for example, reference signals and/or feedback corresponding to one or more downlink transmissions) from a UE 120 to a network node 110.
  • UCI uplink control information
  • An uplink data channel may be used to transmit uplink data (for example, user data associated with a UE 120) from a UE 120 to a network node 110.
  • Uplink control channels may include one or more physical uplink control channels (PUCCHs)
  • uplink data channels may include one or more physical uplink shared channels (PUSCHs) .
  • the downlink and the uplink may each include a set of resources on which the network node 110 and the UE 120 may communicate.
  • Downlink and uplink resources may include time domain resources (frames, subframes, slots, and/or symbols) , frequency domain resources (frequency bands, component carriers, subcarriers, resource blocks, and/or resource elements) , and/or spatial domain resources (particular transmit directions and/or beam parameters) .
  • Frequency domain resources of some bands may be subdivided into bandwidth parts (BWPs) .
  • a BWP may be a continuous block of frequency domain resources (for example, a continuous block of resource blocks) that are allocated for one or more UEs 120.
  • a UE 120 may be configured with both an uplink BWP and a downlink BWP (where the uplink BWP and the downlink BWP may be the same BWP or different BWPs) .
  • a BWP may be dynamically configured (for example, by a network node 110 transmitting a DCI configuration to the one or more UEs 120) and/or reconfigured, which means that a BWP can 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 the one or more UEs 120.
  • This enables more efficient use of the available frequency domain resources in the wireless communication network 100 because fewer frequency domain resources may be allocated to a BWP for a UE 120 (which may reduce the quantity of frequency domain resources that a UE 120 is required to monitor) , leaving more frequency domain resources to be spread across multiple UEs 120.
  • BWPs may also assist in the implementation of lower-capability UEs 120 by facilitating the configuration of smaller bandwidths for communication by such UEs 120.
  • the wireless communication network 100 may be, may include, or may be included in, an IAB network.
  • at least one network node 110 is an anchor network node that communicates with a core network.
  • An anchor network node 110 may also be referred to as an IAB donor (or “IAB-donor” ) .
  • the anchor network node 110 may connect to the core network via a wired backhaul link.
  • an Ng interface of the anchor network node 110 may terminate at the core network.
  • an anchor network node 110 may connect to one or more devices of the core network that provide a core access and mobility management function (AMF) .
  • AMF core access and mobility management function
  • any network node 110 that relays communications may be referred to as a relay network node, a relay station, or simply as a relay.
  • a relay may receive a transmission of a communication from an upstream station (for example, another network node 110 or a UE 120) and transmit the communication to a downstream station (for example, a UE 120 or another network node 110) .
  • the wireless communication network 100 may include or be referred to as a “multi-hop network. ” In the example shown in Fig.
  • the network node 110d may communicate with the network node 110a (for example, a macro network node) and the UE 120d in order to facilitate communication between the network node 110a and the UE 120d.
  • a UE 120 may be or may operate as a relay station that can relay transmissions to or from other UEs 120.
  • a UE 120 that relays communications may be referred to as a UE relay or a relay UE, among other examples.
  • the UEs 120 may be physically dispersed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile.
  • a UE 120 may be, may include, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit.
  • a UE 120 may be, include, or be coupled with a cellular phone (for example, a smart phone) , 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, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (for example, a smart watch, smart clothing, smart glasses, a smart wristband, and/or smart jewelry, such as a smart ring or a smart bracelet) , an entertainment device (for example, a music device, a video device, and/or a satellite
  • a UE 120 and/or a network node 110 may include one or more chips, system-on-chips (SoCs) , chipsets, packages, or devices that individually or collectively constitute or comprise a processing system.
  • the processing system includes processor (or “processing” ) circuitry in the form of one or multiple 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 (ASIC) , programmable logic devices (PLDs) (such as field programmable gate arrays (FPGAs) ) , or other discrete gate or transistor logic or circuitry (all of which may be generally referred to herein individually as “processors” or collectively as “the processor” or “the processor circuitry” ) .
  • processors or “processing” circuitry in the form of one or multiple processors, microprocessors
  • One or more of the memories may be coupled (for example, operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) with one or more of the processors and may individually or collectively store processor-executable code (such as software) that, when executed by one or more of the processors, may configure one or more of the processors to perform various functions or operations described herein. Additionally or alternatively, in some examples, one or more of the processors may be preconfigured to perform various functions or operations described herein without requiring configuration by software.
  • the processing system may further include or be coupled with one or more modems (such as a Wi-Fi (for example, IEEE compliant) modem or a cellular (for example, 3GPP 4G LTE, 5G, or 6G compliant) modem) .
  • modems such as a Wi-Fi (for example, IEEE compliant) modem or a cellular (for example, 3GPP 4G LTE, 5G, or 6G compliant) modem
  • one or more processors of the processing system include or implement one or more of the modems.
  • the processing system may further include or be coupled with multiple radios (collectively “the radio” ) , multiple RF chains, or multiple transceivers, each of which may in turn be coupled with one or more of multiple antennas.
  • one or more processors of the processing system include or implement one or more of the radios, RF chains or transceivers.
  • the UE 120 may include or may be included in a housing that houses components associated with the UE 120 including the processing system.
  • 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 simply referred to as “MTC UEs” ) .
  • An MTC UE may be, may include, or may be included in or coupled with a robot, an uncrewed aerial vehicle, a remote device, a sensor, a meter, a monitor, and/or a location tag.
  • Some UEs 120 may be considered IoT devices and/or may be implemented as NB-IoT (narrowband IoT) devices.
  • Some UEs 120 may be classified according to different categories in association with different complexities and/or different capabilities.
  • UEs 120 in a first category may facilitate massive IoT in the wireless communication network 100, and may offer low complexity and/or cost relative to UEs 120 in a second category.
  • UEs 120 in a second category may include mission-critical IoT devices, legacy UEs, baseline UEs, high-tier UEs, advanced UEs, full-capability UEs, and/or premium UEs that are capable of URLLC, enhanced mobile broadband (eMBB) , and/or precise positioning in the wireless communication network 100, among other examples.
  • eMBB enhanced mobile broadband
  • a third category of UEs 120 may have mid-tier complexity and/or capability (for example, a capability between UEs 120 of the first category and UEs 120 of the second capability) .
  • a UE 120 of the third category may be referred to as a reduced capacity UE ( “RedCap UE” ) , a mid-tier UE, an NR-Light UE, and/or an NR-Lite UE, among other examples.
  • RedCap UEs may bridge a gap between the capability and complexity of NB-IoT devices and/or eMTC UEs, and mission-critical IoT devices and/or premium UEs.
  • RedCap UEs may include, for example, wearable devices, IoT devices, industrial sensors, and/or cameras that are associated with a limited bandwidth, power capacity, and/or transmission range, among other examples.
  • RedCap UEs may support healthcare environments, building automation, electrical distribution, process automation, transport and logistics, and/or smart city deployments, among other examples.
  • two or more UEs 120 may communicate directly with one another using sidelink communications (for example, without communicating by way of a network node 110 as an intermediary) .
  • the UE 120a may directly transmit data, control information, or other signaling as a sidelink communication to the UE 120e. This is in contrast to, for example, the UE 120a first transmitting data in an UL communication to a network node 110, which then transmits the data to the UE 120e in a DL communication.
  • the UEs 120 may transmit and receive sidelink communications 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.
  • a network node 110 may schedule and/or allocate resources for sidelink communications between UEs 120 in the wireless communication network 100.
  • a UE 120 (instead of a network node 110) may perform, or collaborate or negotiate with one or more other UEs to perform, scheduling operations, resource selection operations, and/or other operations for sidelink communications.
  • some of the network nodes 110 and the UEs 120 of the wireless communication network 100 may be configured for full-duplex operation in addition to half-duplex operation.
  • a network node 110 or a UE 120 operating in a half-duplex mode may perform only one of transmission or reception during particular time resources, such as during particular slots, symbols, or other time periods.
  • Half-duplex operation may involve time-division duplexing (TDD) , in which DL transmissions of the network node 110 and UL transmissions of the UE 120 do not occur in the same time resources (that is, the transmissions do not overlap in time) .
  • TDD time-division duplexing
  • a network node 110 or a UE 120 operating in a full-duplex mode can transmit and receive communications concurrently (for example, in the same time resources) .
  • network nodes 110 and/or UEs 120 may generally increase the capacity of the network and the radio access link.
  • full-duplex operation may involve frequency-division duplexing (FDD) , in which DL transmissions of the network node 110 are performed in a first frequency band or on a first component carrier and transmissions of the UE 120 are performed in a second frequency band or on a second component carrier different than the first frequency band or the first component carrier, respectively.
  • FDD frequency-division duplexing
  • full-duplex operation may be enabled for a UE 120 but not for a network node 110.
  • a UE 120 may simultaneously transmit an UL transmission to a first network node 110 and receive a DL transmission from a second network node 110 in the same time resources.
  • full-duplex operation may be enabled for a network node 110 but not for a UE 120.
  • a network node 110 may simultaneously transmit a DL transmission to a first UE 120 and receive an UL transmission from a second UE 120 in the same time resources.
  • full-duplex operation may be enabled for both a network node 110 and a UE 120.
  • the UEs 120 and the network nodes 110 may perform MIMO communication.
  • MIMO generally refers to transmitting or receiving multiple signals (such as multiple layers or multiple data streams) simultaneously over the same time and frequency resources.
  • MIMO techniques generally exploit multipath propagation.
  • MIMO may be implemented using various spatial processing or spatial multiplexing operations.
  • MIMO may support simultaneous transmission to multiple receivers, referred to as multi-user MIMO (MU-MIMO) .
  • MU-MIMO multi-user MIMO
  • Some RATs may employ advanced MIMO techniques, such as mTRP operation (including redundant transmission or reception on multiple TRPs) , reciprocity in the time domain or the frequency domain, single-frequency-network (SFN) transmission, or non-coherent joint transmission (NC-JT) .
  • mTRP operation including redundant transmission or reception on multiple TRPs
  • SFN single-frequency-network
  • NC-JT non-coherent joint transmission
  • a UE may include a communication manager 140.
  • the communication manager 140 may receive a PDCCH order DCI that includes an indicator to indicate whether a Tx beam of a PRACH transmission is based at least in part on a Tx beam of an associated SRS or based at least in part on an Rx beam of an associated SSB or CSI-RS;and transmit the PRACH transmission based at least in part on the indicator.
  • the communication manager 140 may receive a configuration that includes a first preamble received target power value and a second preamble received target power value; and transmit a PRACH transmission using the first preamble received target power value or the second preamble received target power value depending on whether the PRACH transmission is to an uplink-only TRP or a downlink TRP.
  • the communication manager 140 may receive a PDCCH order DCI that includes a TCI field to indicate a TCI state for a PDCCH ordered PRACH transmission; and transmit the PDCCH ordered PRACH transmission 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.
  • a network node may include a communication manager 150.
  • the communication manager 150 may transmit a PDCCH order DCI that includes an indicator to indicate whether a Tx beam of a PRACH transmission is based at least in part on a Tx beam of an associated SRS or based at least in part on an Rx beam of an associated SSB or CSI-RS; and receive the PRACH transmission based at least in part on the indicator.
  • the communication manager 150 may transmit a configuration that includes a first preamble received target power value and a second preamble received target power value; and receive a PRACH transmission using the first preamble received target power value or the second preamble received target power value depending on whether the PRACH transmission is to an uplink-only TRP or a downlink TRP.
  • the communication manager 150 may transmit a PDCCH order DCI that includes a TCI field to indicate a TCI state for a PDCCH ordered PRACH transmission; and receive the PDCCH ordered PRACH transmission 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.
  • Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.
  • Fig. 2 is a diagram illustrating an example network node 110 in communication with an example UE 120 in a wireless network in accordance with the present disclosure.
  • the 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 through 232t, where t ⁇ 1) , a set of antennas 234 (shown as 234a through 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, among other examples.
  • TX transmit
  • one or a combination of the antenna (s) 234, the modem (s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 214, and/or the TX MIMO processor 216 may be included in a transceiver of the network node 110.
  • the transceiver may be under control of and used by one or more processors, such as the controller/processor 240, and in some aspects in conjunction with processor-readable code stored in the memory 242, to perform aspects of the methods, processes, and/or operations described herein.
  • the network node 110 may include one or more interfaces, communication components, and/or other components that facilitate communication with the UE 120 or another network node.
  • processors may refer to one or more controllers and/or one or more processors.
  • processors may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and/or controller/processor 240.
  • processors of the UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and/or controller/processor 280.
  • a single processor may perform all of the operations described as being performed by the one or more processors.
  • a first set of (one or more) processors of the one or more processors may perform a first operation described as being performed by the one or more processors
  • a second set of (one or more) processors of the one or more processors may perform a second operation described as being performed by the one or more processors.
  • the first set of processors and the second set of processors may be the same set of processors or may be different sets of processors.
  • Reference to “one or more memories” should be understood to refer to any one or more memories of a corresponding device, such as the memory described in connection with Fig. 2. For example, operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or different subsets of the one or more memories.
  • the transmit processor 214 may receive data ( “downlink data” ) intended for the UE 120 (or a set of UEs that includes the UE 120) from the data source 212 (such as a data pipeline or a data queue) .
  • the transmit processor 214 may select one or more MCSs for the UE 120 in accordance with one or more channel quality indicators (CQIs) received from the UE 120.
  • the network node 110 may process the data (for example, including encoding the data) for transmission to the UE 120 on a downlink in accordance with the MCS (s) selected for the UE 120 to generate data symbols.
  • the transmit processor 214 may process system information (for example, semi-static resource partitioning information (SRPI) ) and/or control information (for example, CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and/or control symbols.
  • the transmit processor 214 may generate reference symbols for reference signals (for example, a cell-specific reference signal (CRS) , a demodulation reference signal (DMRS) , or a channel state information (CSI) reference signal (CSI-RS) ) and/or synchronization signals (for example, a primary synchronization signal (PSS) or a secondary synchronization signals (SSS) ) .
  • reference signals for example, a cell-specific reference signal (CRS) , a demodulation reference signal (DMRS) , or a channel state information (CSI) reference signal (CSI-RS)
  • CSI-RS channel state information reference signal
  • synchronization signals for example, a primary synchronization signal (PSS) or a secondary synchronization signals (SSS)
  • Each modem 232 may further use the respective modulator component to process (for example, convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain a time domain downlink signal.
  • the modems 232a through 232t may together transmit a set of downlink signals (for example, T downlink signals) via the corresponding set of antennas 234.
  • a downlink signal may include a DCI communication, a MAC control element (MAC-CE) communication, an RRC communication, a downlink reference signal, or another type of downlink communication.
  • Downlink signals may be transmitted on a PDCCH, a PDSCH, and/or on another downlink channel.
  • a downlink signal may carry one or more transport blocks (TBs) of data.
  • a TB may be a unit of data that is transmitted over an air interface in the wireless communication network 100.
  • a data stream (for example, from the data source 212) may be encoded into multiple TBs for transmission over the air interface. The quantity of TBs used to carry the data associated with a particular data stream may be associated with a TB size common to the multiple TBs.
  • the TB size may be based on or otherwise associated with radio channel conditions of the air interface, the MCS used for encoding the data, the downlink resources allocated for transmitting the data, and/or another parameter.
  • the larger the TB size the greater the amount of data that can be transmitted in a single transmission, which reduces signaling overhead.
  • larger TB sizes may be more prone to transmission and/or reception errors than smaller TB sizes, but such errors may be mitigated by more robust error correction techniques.
  • uplink signals from the UE 120 may be received by an antenna 234, may be processed by a modem 232 (for example, a demodulator component, shown as DEMOD, of a modem 232) , may be detected by the MIMO detector 236 (for example, an Rx MIMO processor) if applicable, and/or may be further processed by the receive processor 238 to obtain decoded data and/or control information.
  • the receive processor 238 may provide the decoded data to a data sink 239 (which may be a data pipeline, a data queue, and/or another type of data sink) and provide the decoded control information to a processor, such as the controller/processor 240.
  • the network node 110 may use the scheduler 246 to schedule one or more UEs 120 for downlink or uplink communications.
  • the scheduler 246 may use DCI to dynamically schedule DL transmissions to the UE 120 and/or UL transmissions from the UE 120.
  • the scheduler 246 may allocate recurring time domain resources and/or frequency domain resources that the UE 120 may use to transmit and/or receive communications using an RRC configuration (for example, a semi-static configuration) , for example, to perform semi-persistent scheduling (SPS) or to configure a configured grant (CG) for the UE 120.
  • RRC configuration for example, a semi-static configuration
  • SPS semi-persistent scheduling
  • CG configured grant
  • One or more of the transmit processor 214, the TX MIMO processor 216, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, and/or the controller/processor 240 may be included in an RF chain of the network node 110.
  • An RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs) , and/or other devices that convert between an analog signal (such as for transmission or reception via an air interface) and a digital signal (such as for processing by one or more processors of the network node 110) .
  • the RF chain may be or may be included in a transceiver of the network node 110.
  • the network node 110 may use the communication unit 244 to communicate with a core network and/or with other network nodes.
  • the communication unit 244 may support wired and/or wireless communication protocols and/or connections, such as Ethernet, optical fiber, common public radio interface (CPRI) , and/or a wired or wireless backhaul, among other examples.
  • the network node 110 may use the communication unit 244 to transmit and/or receive data associated with the UE 120 or to perform network control signaling, among other examples.
  • the communication unit 244 may include a transceiver and/or an interface, such as a network interface.
  • one or a combination of the antenna (s) 252, the modem (s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, or the TX MIMO processor 266 may be included in a transceiver that is included in the UE 120.
  • the transceiver may be under control of and used by one or more processors, such as the controller/processor 280, and in some aspects in conjunction with processor-readable code stored in the memory 282, to perform aspects of the methods, processes, or operations described herein.
  • the UE 120 may include another interface, another communication component, and/or another component that facilitates communication with the network node 110 and/or another UE 120.
  • the set of antennas 252 may receive the downlink communications or signals from the network node 110 and may provide a set of received downlink signals (for example, R received signals) to the set of modems 254.
  • each received signal may be provided to a respective demodulator component (shown as DEMOD) of a modem 254.
  • DEMOD demodulator component
  • Each modem 254 may use the respective demodulator component to condition (for example, filter, amplify, downconvert, and/or digitize) a received signal to obtain input samples.
  • Each modem 254 may use the respective demodulator component to further demodulate or process the input samples (for example, for OFDM) to obtain received symbols.
  • the MIMO detector 256 may obtain received symbols from the set of modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols.
  • the receive processor 258 may process (for example, decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260 (which may include a data pipeline, a data queue, and/or an application executed on the UE 120) , and may provide decoded control information and system information to the controller/processor 280.
  • the transmit processor 264 may receive and process data ( “uplink data” ) from a data source 262 (such as a data pipeline, a data queue, and/or an application executed on the UE 120) and control information from the 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.
  • the receive processor 258 and/or the controller/processor 280 may determine, for a received signal (such as received from the network node 110 or another UE) , one or more parameters relating to transmission of the uplink communication.
  • the 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, among other examples.
  • the control information may include an indication of the RSRP parameter, the RSSI parameter, the RSRQ parameter, the CQI parameter, the TPC parameter, and/or another parameter.
  • the control information may facilitate parameter selection and/or scheduling for the UE 120 by the network node 110.
  • the transmit processor 264 may generate reference symbols for one or more reference signals, such as an uplink DMRS, an uplink sounding reference signal (SRS) , and/or another type of reference signal.
  • the symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266, if applicable, and further processed by the set of modems 254 (for example, for DFT-s-OFDM or CP-OFDM) .
  • the TX MIMO processor 266 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (for example, U output symbol streams) to the set of modems 254.
  • each output symbol stream may be provided to a respective modulator component (shown as MOD) of a modem 254.
  • Each modem 254 may use the respective modulator component to process (for example, to modulate) a respective output symbol stream (for example, for OFDM) to obtain an output sample stream.
  • Each modem 254 may further use the respective modulator component to process (for example, convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain an uplink signal.
  • the modems 254a through 254u may transmit a set of uplink signals (for example, R uplink signals or U uplink symbols) via the corresponding set of antennas 252.
  • An uplink signal may include a UCI communication, a MAC-CE communication, an RRC communication, or another type of uplink communication.
  • Uplink signals may be transmitted on a PUSCH, a PUCCH, and/or another type of uplink channel.
  • An uplink signal may carry one or more TBs of data.
  • Sidelink data and control transmissions may generally use similar techniques as were described for uplink data and control transmission, and may use sidelink-specific channels such as a physical sidelink shared channel (PSSCH) , a physical sidelink control channel (PSCCH) , and/or a physical sidelink feedback channel (PSFCH) .
  • PSSCH physical sidelink shared channel
  • PSCCH physical sidelink control channel
  • PSFCH physical sidelink feedback channel
  • One or more antennas of the set of antennas 252 or the set of antennas 234 may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples.
  • An antenna panel, an antenna group, a set of antenna elements, or an antenna array may include one or more antenna elements (within a single housing or multiple housings) , a set of coplanar antenna elements, a set of non-coplanar antenna elements, or one or more antenna elements coupled with one or more transmission or reception components, such as one or more components of Fig. 2.
  • antenna can refer to one or more antennas, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays.
  • Antenna panel can refer to a group of antennas (such as antenna elements) arranged in an array or panel, which may facilitate beamforming by manipulating parameters of the group of antennas.
  • Antenna module may refer to circuitry including one or more antennas, which 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.
  • each of the antenna elements of an antenna 234 or an antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals.
  • a single antenna element may include a first sub-element cross-polarized with a second sub-element that can be used to independently transmit cross-polarized signals.
  • the 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.
  • a spacing between antenna elements may be such that signals with a desired wavelength transmitted separately by the antenna elements may interact or interfere constructively and destructively along various directions (such as to form a desired beam) .
  • the spacing may provide a quarter wavelength, a half wavelength, or another fraction of a wavelength of spacing between neighboring antenna elements to allow for the desired constructive and destructive interference patterns of signals transmitted by the separate antenna elements within that expected range.
  • the amplitudes and/or phases of signals transmitted via antenna elements and/or sub-elements may be modulated and shifted relative to each other (such as by manipulating phase shift, phase offset, and/or amplitude) to generate one or more beams, which is referred to as beamforming.
  • beam may refer to a directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction.
  • Beam may also generally refer to a direction associated with such a directional signal transmission, a set of directional resources associated with the signal transmission (for example, an angle of arrival, a horizontal direction, and/or a vertical direction) , and/or a set of parameters that indicate one or more aspects of a directional signal, a direction associated with the signal, and/or a set of directional resources associated with the signal.
  • antenna elements may be individually selected or deselected for directional transmission of a signal (or signals) by controlling amplitudes of one or more corresponding amplifiers and/or phases of the signal (s) to form one or more beams.
  • the shape of a beam (such as the amplitude, width, and/or presence of side lobes) and/or the direction of a beam (such as an angle of the beam relative to a surface of an antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and/or amplitudes of the multiple signals relative to each other.
  • Different UEs 120 or network nodes 110 may include different numbers of antenna elements.
  • a UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or a different number of antenna elements.
  • a network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or a different number of antenna elements.
  • a larger number of antenna elements may provide increased control over parameters for beam generation relative to a smaller number of antenna elements, whereas a smaller number of antenna elements may be less complex to implement and may use less power than a larger number of antenna elements.
  • Multiple antenna elements may support multiple-layer transmission, in which a first layer of a communication (which may include a first data stream) and a second layer of a communication (which may include a second data stream) are transmitted using the same time and frequency resources with spatial multiplexing.
  • Fig. 2 is provided as an example. Other examples may differ from what is described with regard to Fig. 2.
  • the CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via F1 interfaces.
  • Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links.
  • Each of the RUs 340 may communicate with one or more UEs 120 via respective RF access links.
  • a UE 120 may be simultaneously served by multiple RUs 340.
  • Each of the components of the disaggregated base station architecture 300 may include one or more interfaces or may be coupled with one or more interfaces for receiving or transmitting signals, such as data or information, via a wired or wireless transmission medium.
  • a DU 330 may host various layers, such as an RLC layer, a 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 also may be referred to as a module) may be implemented with an interface for communicating signals with other layers (and modules) hosted by the DU 330, or for communicating signals with the control functions hosted by the CU 310.
  • Each RU 340 may implement lower layer functionality. In some aspects, real-time and non-real-time aspects of control and user plane communication with the RU (s) 340 may be controlled by the corresponding DU 330.
  • the SMO Framework 360 may support RAN deployment and provisioning of non-virtualized and virtualized network elements.
  • the SMO Framework 360 may support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface, such as an O1 interface.
  • the SMO Framework 360 may interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface, such as an O2 interface.
  • a cloud computing platform such as an open cloud (O-Cloud) platform 390
  • network element life cycle management such as to instantiate virtualized network elements
  • a virtualized network element may include, but is not limited to, a CU 310, a DU 330, an RU 340, a non-RT RIC 350, and/or a Near-RT RIC 370.
  • the SMO Framework 360 may communicate with a hardware aspect of a 4G RAN, a 5G NR RAN, and/or a 6G RAN, such as an open eNB (O-eNB) 380, via an O1 interface. Additionally or alternatively, the SMO Framework 360 may communicate directly with each of one or more RUs 340 via a respective O1 interface. In some deployments, this configuration can enable each DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
  • the means for the UE to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller/processor 280, or memory 282.
  • a network node (e.g., the network node 110) includes means for transmitting a PDCCH order DCI that includes an indicator to indicate whether a Tx beam of a PRACH transmission is based at least in part on a Tx beam of an associated SRS or based at least in part on an Rx beam of an associated SSB or CSI-RS; and/or means for receiving the PRACH transmission based at least in part on the indicator.
  • the network node includes means for transmitting a configuration that includes a first preamble received target power value and a second preamble received target power value; and/or means for receiving a PRACH transmission using the first preamble received target power value or the second preamble received target power value depending on whether the PRACH transmission is to an uplink-only TRP or a downlink TRP.
  • the network node includes means for transmitting a PDCCH order DCI that includes a TCI field to indicate a TCI state for a PDCCH ordered PRACH transmission; and/or means for receiving the PDCCH ordered PRACH transmission based at least in part on the TCI field.
  • Fig. 4 is a diagram illustrating an example 400 of an uplink dense deployment, in accordance with the present disclosure.
  • an uplink dense deployment may be used to improve a coverage and/or a capacity of an uplink direction.
  • An uplink Rx point e.g., an uplink-only node
  • Downlink signals and/or downlink channels transmitted from a network node may be from a different node (e.g., a macro node, a central node, a serving cell, or a serving base station) .
  • Uplink Rx points may be connected to the network node via backhaul links.
  • the uplink dense deployment may help to reduce an uplink pathloss, which may be helpful when an uplink coverage is a bottleneck.
  • the uplink dense deployment may help in terms of deployment cost and/or complexity since the uplink Rx points do not transmit any downlink signal.
  • the uplink Rx points simply receive an uplink signal and send the uplink signal to the network node with or without processing.
  • Fig. 4 is provided as an example. Other examples may differ from what is described with regard to Fig. 4.
  • the uplink/SUL indicator field may indicate which uplink carrier in the cell to use for a PRACH transmission. Otherwise, the uplink/SUL indicator field may be reserved.
  • the DCI format 1_0 for the PDCCH order may include a synchronization signal (SS) or physical broadcast channel (PBCH) (SS/PBCH) index field (6 bits) .
  • SS/PBCH index field may indicate an SS/PBCH to be used to determine a random access channel (RACH) occasion for the PRACH transmission.
  • the SS/PBCH index field may be reserved.
  • the DCI format 1_0 for the PDCCH order may include a PRACH mask index field (4 bits) .
  • the PRACH mask index field may indicate a RACH occasion associated with an SS/PBCH indicated by an SS/PBCH index for the PRACH transmission. Otherwise, the PRACH mask index field may be reserved.
  • the UE may transmit the PRACH transmission based at least in part on the Rx beam of the associated SSB or CSI-RS.
  • the UE may transmit the PRACH transmission using the Tx beam, 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.
  • the UE may use an appropriate Tx beam to transmit the PRACH transmission.
  • the indicator in the PDCCH order DCI may allow the UE to distinguish whether the Tx beam of the PRACH transmission is based at least in part on the Tx beam of the SRS (e.g., indicated by an SRS resource indication field) or based at least in part on the Rx beam of the associated SSB or CSI-RS.
  • the UE may use the appropriate Tx beam, which may increase a likelihood that the PRACH transmission is successfully received by the network node.
  • the UE may use the appropriate Tx beam, which may increase a likelihood that the PRACH transmission is successfully received by the network node.
  • a retransmission of the PRACH transmission may not be needed, thereby reducing network resources and power consumption at the UE.
  • Fig. 5 is a diagram illustrating an example 500 associated with PRACH transmissions based at least in part on DCI, in accordance with the present disclosure.
  • example 500 includes communication between a UE (e.g., UE 120) and a network node (e.g., network node 110) .
  • 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 dense environment in which an uplink TRP is different than a downlink TRP.
  • the UE may receive, from the network node, a PDCCH order DCI that includes an indicator to indicate whether a Tx beam of a PRACH transmission is based at least in part on a Tx beam of an associated SRS or based at least in part on an Rx beam of an associated SSB or CSI-RS.
  • the indicator may be a single bit, and the indicator may be set to a first value to indicate that the Tx beam of the PRACH transmission is based at least in part on the Tx beam of the associated SRS, or the indicator may be set to a second value to indicate that the Tx beam of the PRACH transmission is based at least in part on the Rx beam of the associated SSB or CSI-RS.
  • the indicator may be associated with one or more reserved bits in the PDCCH order DCI.
  • the indicator may be associated with a PRACH association indicator in the PDCCH order DCI.
  • the PRACH association indicator may be set to a first value to indicate that the Tx beam of the PRACH transmission is based at least in part 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 of the PRACH transmission is based at least in part on the Rx beam of the associated SSB or CSI-RS.
  • the indicator may be associated with an SRS resource indication field, where a first codepoint in the SRS resource indication field may indicate that the Tx beam of the PRACH transmission is based at least in part on the Rx beam of the associated SSB or CSI-RS, and a second codepoint in the SRS resource indication field may indicate that the Tx beam of the PRACH transmission is based at least in part on the Tx beam of the associated SRS.
  • the indicator in the PDCCH order DCI may be used to indicate whether the Tx beam of the PRACH transmission is based at least in part on the Tx beam of the associated SRS or based at least in part on the Rx beam of the associated SSB/CSI-RS.
  • the indicator is set to the first value (e.g., 0)
  • the Tx beam of the PRACH transmission may be based at least in part on the Rx beam of the associated SSB/CSI-RS.
  • the indicator is set to the second value (e.g., 1)
  • the Tx beam of the PRACH transmission may be based at least in part on the Tx beam of the associated SRS.
  • the indicator in the PDCCH order DCI may be indicated in various manners.
  • one of the reserved bits may be used for the indicator.
  • the PRACH association indicator in the PDCCH order DCI may be reused for the indicator.
  • the PRACH association indicator may be reused when two timing advances (TAs) are supported for an asymmetric downlink single TRP (sTRP) or uplink multiple TRP (mTRP) scenario.
  • the UE may reinterpret the PRACH association indicator.
  • the PRACH association indicator is set to 0
  • the Tx beam of the PRACH transmission may be based at least in part on the Rx beam of the associated SSB/CSI-RS.
  • the PRACH association indicator is set to 1
  • the Tx beam of the PRACH transmission may be based at least in part on the Tx beam of the associated SRS.
  • the SRS resource indication field may be used to indicate whether a Tx beam of a PRACH transmission is based at least in part on a Tx beam of an associated SRS.
  • one of the codepoints in the SRS resource indication field may be used to indicate that the Tx beam of the PRACH transmission is based at least in part on an Rx beam of an associated SSB/CSI-RS.
  • Remaining codepoints may be used to indicate that the Tx beam of the PRACH transmission is based at least in part on the Tx beam of the associated SRS.
  • the UE may transmit, to the network node, the PRACH transmission based at least in part on the indicator.
  • the UE may transmit the PRACH transmission based at least in part on the Tx beam of the associated SRS.
  • the UE may transmit the PRACH transmission based at least in part on the Rx beam of the associated SSB or CSI-RS.
  • the UE may transmit the PRACH transmission using the Tx beam, 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.
  • the UE may receive, from the network node, a configuration that includes a first preamble received target power value and a second preamble received 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 a first preamble received target power value, a first maximum number of preamble transmissions, or a first power ramping step value.
  • the second set of parameters may include one or more of a second preamble received target power value, a second maximum number of preamble transmissions, or a second power ramping step.
  • the UE may transmit, to the network node, a PRACH transmission using the first preamble received target power value or the second preamble received target power value, depending on whether the PRACH transmission is to an uplink-only TRP or a downlink TRP.
  • the UE may select the first preamble received target power value or the second preamble received target power value.
  • the UE may determine a PRACH transmission power for the PRACH transmission based at least in part on the first preamble received target power value or the second preamble received target power value.
  • the UE may transmit, to the network node, a PRACH transmission using the first set of parameters or the second set of parameters, depending on whether the PRACH transmission is to an uplink-only TRP or a downlink TRP.
  • the UE may select the first set of parameters or the second set of parameters.
  • the UE may determine a PRACH transmission power for the PRACH transmission based at least in part on the first set of parameters or the second set of parameters.
  • a pathloss between the UE and the uplink-only TRP may be less than a pathloss between the UE and the downlink TRP.
  • a Tx power associated with a PRACH transmission to the uplink-only TRP may be less than a Tx power associated with a PRACH transmission to the downlink TRP.
  • different preamble received target power values may be configured.
  • different preambleTransMax values and powerRampingStep values may be configured.
  • the UE may receive, from the network node, a PDCCH order DCI that includes an indicator.
  • the UE may select the first preamble received target power value or the second preamble received 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 received target power value is to be used, or the indicator may be set to a second value to indicate that the second preamble received target power value is to be used.
  • the UE may select the first set of parameters or the 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 is to be used, or the indicator may be set to a second value to indicate that the second set of parameters is to be used.
  • the UE may select the first preamble received target power value or the second preamble received target power value based at least in part on a Tx beam of the PRACH transmission.
  • the first preamble received target power value may be selected based at least in part on the Tx beam of the PRACH transmission being based at least in part on an Rx beam of an associated SSB or CSI-RS.
  • the second preamble received target power value may be selected based at least in part on the Tx beam of the PRACH transmission being based at least in part on a Tx beam of an associated SRS.
  • the UE may select the first set of parameters or the second set of parameters based at least in part on a Tx beam of the PRACH transmission.
  • the first set of parameters may be selected based at least in part on the Tx beam of the PRACH transmission being based at least in part on an Rx beam of an associated SSB or CSI-RS.
  • the second set of parameters may be selected based at least in part on the Tx beam of the PRACH transmission being based at least in part on a Tx beam of an associated SRS.
  • the UE may receive, via a PDCCH order DCI that includes an SRS resource indication field, an indication to use an uplink pathloss associated with a TCI state of an indicated SRS resource or use a pathloss offset associated with the TCI state of the indicated SRS resource.
  • a smaller Tx power may be needed as compared to a PRACH transmission to the downlink TRP.
  • the network node may configure different preamble received target powers, and one of them may be used depending on whether the PRACH transmission is to the uplink-only TRP or to the downlink TRP. Additionally, different preambleTransMax values and powerRampingStep values may be configured.
  • the UE may be configured with two preamble received target power (preambleReceivedTargetPower) values via RRC signaling.
  • the UE may select one of the preamble received target power values to determine the PRACH transmission power.
  • the UE may be configured with two preambleReceivedTargetPower values instead of a single preambleReceivedTargetPower) value.
  • the UE may be configured with two maximum number of preamble transmissions (preambleTransMax) values and two power ramping step (powerRampingStep) values via RRC signaling.
  • the UE may be configured with the two preambleTransMax values and the two powerRampingStep values, instead of a single preambleTransMax value and a single powerRampingStep value.
  • a second preambleTransMax and/or a second powerRampingStep may be applied when a second preambleReceivedTargetPower value is applied.
  • a second set of parameters e.g., a second preambleReceivedTargetPower value, a second preambleTransMax value, and/or a second powerRampingStep value
  • the second set of parameters may be configured for only a four-step PRACH or for both a four-step PRACH and a two-step PRACH.
  • the UE may select one of the preambleReceivedTargetPower values based at least in part on an indication in a PDCCH order DCI.
  • one indicator in the PDCCH order DCI may be used by the UE to select one of the preambleReceivedTargetPower values.
  • the indicator is set to a first value (e.g., 0)
  • the UE may use a first preambleReceivedTargetPower value or a preambleReceivedTargetPower with a larger value.
  • the UE may select one of the preambleReceivedTargetPower values based at least in part on a Tx beam of the PRACH transmission.
  • the UE may use the first preambleReceivedTargetPower or the preambleReceivedTargetPower with the larger value.
  • the UE may use the second preambleReceivedTargetPower or the preambleReceivedTargetPower with the smaller value.
  • the UE may be indicated to use the uplink pathloss associated with the TCI state of the indicated SRS resource, or to use the pathloss offset associated with the TCI state of the indicated SRS resource, when the SRS resource indication field is present in the PDCCH order DCI.
  • a PL b, f, c in a PRACH power control formula may be replaced by the uplink pathloss.
  • the PL b, f, c in the PRACH power control formula may be replaced by a PL b, f, c –PL offset.
  • a PL-RS for a PL b, f, c determination may be based at least in part on a legacy DL RS for PRACH power control, or based at least in part on a PL-RS associated with a TCI state of the indicated SRS resource.
  • Fig. 6 is provided as an example. Other examples may differ from what is described with regard to Fig. 6.
  • Fig. 7 is a diagram illustrating an example 700 associated with PRACH transmissions based at least in part on DCI, in accordance with the present disclosure.
  • example 700 includes communication between a UE (e.g., UE 120) and a network node (e.g., network node 110) .
  • 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 dense environment in which an uplink TRP is different than a downlink TRP.
  • the UE may receive, from the network node, a PDCCH order DCI that includes a TCI field to indicate a TCI state for a PDCCH ordered PRACH transmission.
  • the TCI field may indicate a TCI state identifier.
  • the TCI field may indicate an active TCI state of one or more active TCI states, and the TCI field may indicate a TCI codepoint that maps to the active TCI state.
  • the UE may apply the TCI state by default, where the TCI state may be associated with an SSB, a CSI-RS, or an SRS, and a Tx beam and a power control for the PDCCH ordered PRACH transmission may be based at least in part on the TCI state.
  • the UE may apply the TCI state based at least in part on a one-bit indicator in the PDCCH order DCI, where the Tx beam and the power control for the PDCCH ordered PRACH transmission may be based at least in part on the TCI state.
  • the UE may apply a pathloss offset associated with the TCI state for the power control.
  • the UE may transmit, to the network node, the PDCCH ordered PRACH transmission based at least in part on the TCI field.
  • the UE may transmit the PDCCH ordered PRACH transmission based at least in part on the TCI state.
  • the UE may transmit the PDCCH ordered PRACH transmission based at least in part on the TCI state identifier or the active TCI state of the one or more active TCI states.
  • the UE may be indicated with the TCI state in the PDCCH order DCI.
  • a field e.g., the TCI field
  • some of the reserved bits in the PDCCH order DCI may be used to indicate the TCI state.
  • the field may directly indicate the TCI state ID.
  • the field may indicate the active TCI state of the one or more active TCI states.
  • the field may indicate the TCI codepoint, where the TCI codepoint may be mapped to the active TCI state based at least in part on a preestablished mapping (e.g., a mapping based at least in part on an activation MAC-CE) .
  • the UE when the TCI field is present in the PDCCH order DCI, the UE may always use an indicated TCI state.
  • the indicated TCI state may be associated with the SSB/CSI-RS or associated with the SRS.
  • a Tx beam of a PRACH transmission and a power of the PRACH transmission may be based at least in part on the indicated TCI state.
  • whether or not the indicated TCI state in the PDCCH order DCI is applied may be explicitly indicated by a 1-bit indicator in the PDCCH order (e.g., reusing one of the reserved bits) or indicated by using one codepoint in the TCI field in the PDCCH order DCI.
  • the Tx beam of the PRACH transmission and power control for the PRACH transmission may be based at least in part on a legacy rule.
  • the Tx beam of the PRACH transmission and the power control for the PRACH transmission may be based at least in part on the indicated TCI state.
  • process 800 may include receiving a PDCCH order DCI that includes an indicator to indicate whether a Tx beam of a PRACH transmission is based at least in part on a Tx beam of an associated SRS or based at least in part on an Rx beam of an associated SSB or CSI-RS (block 810) .
  • the UE e.g., using reception component 1402 and/or communication manager 1406, depicted in Fig.
  • process 800 may include transmitting the PRACH transmission based at least in part on the indicator (block 820) .
  • the UE e.g., using transmission component 1404 and/or communication manager 1406, depicted in Fig. 14
  • Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • the indicator is a single bit, and the indicator is set to a first value to indicate that the Tx beam of the PRACH transmission is based at least in part on the Tx beam of the associated SRS, or the indicator is set to a second value to indicate that the Tx beam of the PRACH transmission is based at least in part on the Rx beam of the associated SSB or CSI-RS.
  • the indicator is associated with one or more reserved bits in the PDCCH order DCI.
  • the indicator is associated with a PRACH association indicator in the PDCCH order DCI.
  • the PRACH association indicator is set to a first value to indicate that the Tx beam of the PRACH transmission is based at least in part 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 of the PRACH transmission is based at least in part on the Rx beam of the associated SSB or CSI-RS.
  • the indicator is associated with an SRS resource indication field, wherein a first codepoint in the SRS resource indication field indicates that the Tx beam of the PRACH transmission is based at least in part on the Rx beam of the associated SSB or CSI-RS, and a second codepoint in the SRS resource indication field indicates that the Tx beam of the PRACH transmission is based at least in part on the Tx beam of the associated SRS.
  • the UE is associated with an uplink dense environment in which an uplink TRP is different than a downlink TRP.
  • process 800 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 8. Additionally, or alternatively, two or more of the blocks of process 800 may be performed in parallel.
  • Fig. 9 is a diagram illustrating an example process 900 performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure.
  • Example process 900 is an example where the apparatus or the UE (e.g., UE 120) performs operations associated with PRACH transmissions based at least in part on DCI.
  • the apparatus or the UE e.g., UE 120
  • process 900 may include receiving a configuration that includes a first preamble received target power value and a second preamble received target power value (block 910) .
  • the UE e.g., using reception component 1402 and/or communication manager 1406, depicted in Fig. 14
  • process 900 may include transmitting a PRACH transmission using the first preamble received target power value or the second preamble received target power value, depending on whether the PRACH transmission is to an uplink-only TRP or a downlink TRP (block 920) .
  • the UE e.g., using transmission component 1404 and/or communication manager 1406, depicted in Fig. 14
  • Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • process 900 includes selecting the first preamble received target power value or the second preamble received target power value, and determining a PRACH transmission power for the PRACH transmission based at least in part on the first preamble received target power value or the second preamble received target power value.
  • a pathloss between the UE and the uplink-only TRP is less than a pathloss between the UE and the downlink TRP
  • a Tx power associated with a PRACH transmission to the uplink-only TRP is less than a Tx power associated with a PRACH transmission to the downlink TRP
  • 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 received target power value, a first maximum number of preamble transmissions, and a first power ramping step value, and the second set of parameters includes one or more of the second preamble received target power value, a second maximum number of preamble transmissions, or a second power ramping step.
  • the second set of parameters are applicable to only a PDCCH-ordered RACH, or the second set of parameters are applicable to the PDCCH-ordered RACH and other PRACH transmissions.
  • the second set of parameters are configured for only a four-step RACH procedure, or the second set of parameters are configured for the four-step RACH procedure and a two-step RACH procedure.
  • process 900 includes receiving a PDCCH order DCI that includes an indicator, and selecting the first set of parameters or the second set of parameters based at least in part on the indicator.
  • the indicator is set to a first value to indicate that the first set of parameters is to be used, or the indicator is set to a second value to indicate that the second set of parameters is to be used.
  • process 900 includes selecting the first set of parameters or the second set of parameters based at least in part on a Tx beam of the PRACH transmission, wherein the first set of parameters is selected based at least in part on the Tx beam of the PRACH transmission being based at least in part on an Rx beam of an associated SSB or CSI-RS, or the second set of parameters is selected based at least in part on the Tx beam of the PRACH transmission being based at least in part on a Tx beam of an associated SRS.
  • process 900 includes receiving, via a PDCCH order DCI that includes an SRS resource indication field, an indication to use an uplink pathloss associated with a TCI state of an indicated SRS resource or use a pathloss offset associated with the TCI state of the indicated SRS resource.
  • the UE is associated with an uplink dense environment in which an uplink TRP is different than a downlink TRP.
  • Fig. 10 is a diagram illustrating an example process 1000 performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure.
  • Example process 1000 is an example where the apparatus or the UE (e.g., UE 120) performs operations associated with PRACH transmissions based at least in part on DCI.
  • the apparatus or the UE e.g., UE 120
  • process 1000 may include receiving a PDCCH order DCI that includes a TCI field to indicate a TCI state for a PDCCH ordered PRACH transmission (block 1010) .
  • the UE e.g., using reception component 1402 and/or communication manager 1406, depicted in Fig. 14
  • process 1000 may include transmitting the PDCCH ordered PRACH transmission based at least in part on the TCI field (block 1020) .
  • the UE e.g., using transmission component 1404 and/or communication manager 1406, depicted in Fig. 14
  • Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • the TCI field indicates a TCI state identifier, or the TCI field indicates an active TCI state of one or more active TCI states, and the TCI field indicates a TCI codepoint that maps to the active TCI state.
  • process 1000 includes applying the TCI state by default, wherein the TCI state is associated with an SSB, a CSI-RS, or an SRS, and a Tx beam and a power control for the PDCCH ordered PRACH transmission are based at least in part on the TCI state, or applying the TCI state based at least in part on a one-bit indicator in the PDCCH order DCI, wherein the Tx beam and the power control for the PDCCH ordered PRACH transmission are based at least in part on the TCI state.
  • process 1000 includes applying a pathloss offset associated with the TCI state for the power control.
  • the UE is associated with an uplink dense environment in which an uplink TRP is different than a downlink TRP.
  • process 1000 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 10. Additionally, or alternatively, two or more of the blocks of process 1000 may be performed in parallel.
  • Fig. 11 is a diagram illustrating an example process 1100 performed, for example, at a network node or an apparatus of a network node, in accordance with the present disclosure.
  • Example process 1100 is an example where the apparatus or the network node (e.g., network node 110) performs operations associated with PRACH transmissions based at least in part on DCI.
  • the apparatus or the network node e.g., network node 110
  • process 1100 may include transmitting a PDCCH order DCI that includes an indicator to indicate whether a Tx beam of a PRACH transmission is based at least in part on a Tx beam of an associated SRS or based at least in part on an Rx beam of an associated SSB or CSI-RS (block 1110) .
  • the network node e.g., using transmission component 1504 and/or communication manager 1506, depicted in Fig.
  • a PDCCH order DCI that includes an indicator to indicate whether a Tx beam of a PRACH transmission is based at least in part on a Tx beam of an associated SRS or based at least in part on an Rx beam of an associated SSB or CSI-RS, as described above.
  • process 1100 may include receiving the PRACH transmission based at least in part on the indicator (block 1120) .
  • the network node e.g., using reception component 1502 and/or communication manager 1506, depicted in Fig. 15
  • Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • the indicator is a single bit, and the indicator is set to a first value to indicate that the Tx beam of the PRACH transmission is based at least in part on the Tx beam of the associated SRS, or the indicator is set to a second value to indicate that the Tx beam of the PRACH transmission is based at least in part on the Rx beam of the associated SSB or CSI-RS.
  • the indicator is associated with one or more reserved bits in the PDCCH order DCI.
  • the indicator is associated with a PRACH association indicator in the PDCCH order DCI.
  • the PRACH association indicator is set to a first value to indicate that the Tx beam of the PRACH transmission is based at least in part 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 of the PRACH transmission is based at least in part on the Rx beam of the associated SSB or CSI-RS.
  • the indicator is associated with an SRS resource indication field, wherein a first codepoint in the SRS resource indication field indicates that the Tx beam of the PRACH transmission is based at least in part on the Rx beam of the associated SSB or CSI-RS, and a second codepoint in the SRS resource indication field indicates that the Tx beam of the PRACH transmission is based at least in part on the Tx beam of the associated SRS.
  • the network node is associated with an uplink dense environment in which an uplink TRP is different than a downlink TRP.
  • process 1100 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 11. Additionally, or alternatively, two or more of the blocks of process 1100 may be performed in parallel.
  • Fig. 12 is a diagram illustrating an example process 1200 performed, for example, at a network node or an apparatus of a network node, in accordance with the present disclosure.
  • Example process 1200 is an example where the apparatus or the network node (e.g., network node 110) performs operations associated with PRACH transmissions based at least in part on DCI.
  • the apparatus or the network node e.g., network node 110
  • process 1200 may include transmitting a configuration that includes a first preamble received target power value and a second preamble received target power value (block 1210) .
  • the network node e.g., using transmission component 1504 and/or communication manager 1506, depicted in Fig. 15
  • process 1200 may include receiving a PRACH transmission using the first preamble received target power value or the second preamble received target power value depending on whether the PRACH transmission is to an uplink-only TRP or a downlink TRP (block 1220) .
  • the network node e.g., using reception component 1502 and/or communication manager 1506, depicted in Fig. 15
  • Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • a PRACH transmission power for the PRACH transmission is based at least in part on the first preamble received target power value or the second preamble received target power value.
  • 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 received target power value, a first maximum number of preamble transmissions, or a first power ramping step value, and the second set of parameters includes one or more of the second preamble received target power value, a second maximum number of preamble transmissions, or a second power ramping step.
  • the second set of parameters are applicable to only a PDCCH-ordered RACH, or the second set of parameters are applicable to the PDCCH-ordered RACH and other PRACH transmissions.
  • the second set of parameters are configured for only a four-step RACH procedure, or the second set of parameters are configured for the four-step RACH procedure and a two-step RACH procedure.
  • process 1200 includes transmitting a PDCCH order DCI that includes an indicator, wherein the first set of parameters or the second set of parameters is based at least in part on the indicator.
  • the indicator is set to a first value to indicate that the first set of parameters is to be used, or the indicator is set to a second value to indicate that the second set of parameters is to be used.
  • the first set of parameters or the second set of parameters is based at least in part on a Tx beam of the PRACH transmission, wherein the first set of parameters is selected based at least in part on the Tx beam of the PRACH transmission being based at least in part on an Rx beam of an associated SSB or CSI-RS, or the second set of parameters is selected based at least in part on the Tx beam of the PRACH transmission being based at least in part on a Tx beam of an associated SRS.
  • process 1200 includes transmitting, via a PDCCH order DCI that includes an SRS resource indication field, an indication to use an uplink pathloss associated with a TCI state of an indicated SRS resource or use a pathloss offset associated with the TCI state of the indicated SRS resource.
  • the network node is associated with an uplink dense environment in which an uplink TRP is different than a downlink TRP.
  • process 1200 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 12. Additionally, or alternatively, two or more of the blocks of process 1200 may be performed in parallel.
  • Fig. 13 is a diagram illustrating an example process 1300 performed, for example, at a network node or an apparatus of a network node, in accordance with the present disclosure.
  • Example process 1300 is an example where the apparatus or the network node (e.g., network node 110) performs operations associated with PRACH transmissions based at least in part on DCI.
  • the apparatus or the network node e.g., network node 110
  • process 1300 may include transmitting a PDCCH order DCI that includes a TCI field to indicate a TCI state for a PDCCH ordered PRACH transmission (block 1310) .
  • the network node e.g., using transmission component 1504 and/or communication manager 1506, depicted in Fig. 15
  • process 1300 may include receiving the PDCCH ordered PRACH transmission based at least in part on the TCI field (block 1320) .
  • the network node e.g., using reception component 1502 and/or communication manager 1506, depicted in Fig. 15
  • Process 1300 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • the TCI field indicates a TCI state identifier, or the TCI field indicates an active TCI state of one or more active TCI states, and the TCI field indicates a TCI codepoint that maps to the active TCI state.
  • the TCI state is applied by default, wherein the TCI state is associated with an SSB, a CSI-RS, or an SRS, and a Tx beam and a power control for the PDCCH ordered PRACH transmission are based at least in part on the TCI state, or the TCI state is applied based at least in part on a one-bit indicator in the PDCCH order DCI, wherein the Tx beam and the power control for the PDCCH ordered PRACH transmission are based at least in part on the TCI state.
  • a pathloss offset associated with the TCI state is applied for the power control.
  • the network node is associated with an uplink dense environment in which an uplink TRP is different than a downlink TRP.
  • process 1300 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 13. Additionally, or alternatively, two or more of the blocks of process 1300 may be performed in parallel.
  • Fig. 14 is a diagram of an example apparatus 1400 for wireless communication, in accordance with the present disclosure.
  • the apparatus 1400 may be a UE, or a UE may include the apparatus 1400.
  • the apparatus 1400 includes a reception component 1402, a transmission component 1404, and/or a communication manager 1406, which may be in communication with one another (for example, via one or more buses and/or one or more other components) .
  • the communication manager 1406 is the communication manager 140 described in connection with Fig. 1.
  • the apparatus 1400 may communicate with another apparatus 1408, such as a UE or a network node (such as a CU, a DU, an RU, or a base station) , using the reception component 1402 and the transmission component 1404.
  • another apparatus 1408 such as a UE or a network node (such as a CU, a DU, an RU, or a base station) , using the reception component 1402 and the transmission component 1404.
  • the apparatus 1400 may be configured to perform one or more operations described herein in connection with Figs. 5-7. Additionally, or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as process 800 of Fig. 8, process 900 of Fig. 9, process 1000 of Fig. 10, or a combination thereof.
  • the apparatus 1400 and/or one or more components shown in Fig. 14 may include one or more components of the UE described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 14 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) 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 functions or operations of the component.
  • the reception component 1402 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1408.
  • the reception component 1402 may provide received communications to one or more other components of the apparatus 1400.
  • the reception component 1402 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , and may provide the processed signals to the one or more other components of the apparatus 1400.
  • the reception component 1402 may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers/processors, one or more memories, or a combination thereof, of the UE described in connection with Fig. 2.
  • the transmission component 1404 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1408.
  • one or more other components of the apparatus 1400 may generate communications and may provide the generated communications to the transmission component 1404 for transmission to the apparatus 1408.
  • the transmission component 1404 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) , and may transmit the processed signals to the apparatus 1408.
  • the transmission component 1404 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 a combination thereof, of the UE described in connection with Fig. 2. In some aspects, the transmission component 1404 may be co-located with the reception component 1402 in one or more transceivers.
  • the communication manager 1406 may support operations of the reception component 1402 and/or the transmission component 1404. For example, the communication manager 1406 may receive information associated with configuring reception of communications by the reception component 1402 and/or transmission of communications by the transmission component 1404. Additionally, or alternatively, the communication manager 1406 may generate and/or provide control information to the reception component 1402 and/or the transmission component 1404 to control reception and/or transmission of communications.
  • the reception component 1402 may receive a PDCCH order DCI that includes an indicator to indicate whether a Tx beam of a PRACH transmission is based at least in part on a Tx beam of an associated SRS or based at least in part on an Rx beam of an associated SSB or CSI-RS.
  • the transmission component 1404 may transmit the PRACH transmission based at least in part on the indicator.
  • the communication manager 1406 may select the first preamble received target power value or the second preamble received target power value.
  • the communication manager 1406 may determine a PRACH transmission power for the PRACH transmission based at least in part on the first preamble received target power value or the second preamble received target power value.
  • the reception component 1402 may receive a PDCCH order DCI that includes an indicator.
  • the communication manager 1406 may select the first preamble received target power value or the second preamble received target power value based at least in part on the indicator.
  • the communication manager 1406 may apply the TCI state by default, wherein the TCI state is associated with an SSB, a CSI-RS, or an SRS, and a Tx beam and a power control for the PDCCH ordered PRACH transmission are based at least in part on the TCI state.
  • the communication manager 1406 may apply the TCI state based at least in part on a one-bit indicator in the PDCCH order DCI, wherein the Tx beam and the power control for the PDCCH ordered PRACH transmission are based at least in part on the TCI state.
  • the communication manager 1406 may apply a pathloss offset associated with the TCI state for the power control.
  • Fig. 14 The number and arrangement of components shown in Fig. 14 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 14. Furthermore, two or more components shown in Fig. 14 may be implemented within a single component, or a single component shown in Fig. 14 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 14 may perform one or more functions described as being performed by another set of components shown in Fig. 14.
  • the reception component 1502 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1508.
  • the reception component 1502 may provide received communications to one or more other components of the apparatus 1500.
  • the reception component 1502 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , and may provide the processed signals to the one or more other components of the apparatus 1500.
  • the transmission component 1504 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 a combination thereof, of the network node described in connection with Fig. 2. In some aspects, the transmission component 1504 may be co-located with the reception component 1502 in one or more transceivers.
  • the communication manager 1506 may support operations of the reception component 1502 and/or the transmission component 1504. For example, the communication manager 1506 may receive information associated with configuring reception of communications by the reception component 1502 and/or transmission of communications by the transmission component 1504. Additionally, or alternatively, the communication manager 1506 may generate and/or provide control information to the reception component 1502 and/or the transmission component 1504 to control reception and/or transmission of communications.
  • the transmission component 1504 may transmit a PDCCH order DCI that includes an indicator to indicate whether a Tx beam of a PRACH transmission is based at least in part on a Tx beam of an associated SRS or based at least in part on an Rx beam of an associated SSB or CSI-RS.
  • the reception component 1502 may receive the PRACH transmission based at least in part on the indicator.
  • the transmission component 1504 may transmit a configuration that includes a first preamble received target power value and a second preamble received target power value.
  • the reception component 1502 may receive a PRACH transmission using the first preamble received target power value or the second preamble received target power value depending on whether the PRACH transmission is to an uplink-only TRP or a downlink TRP.
  • the transmission component 1504 may transmit a PDCCH order DCI that includes an indicator, wherein the first preamble received target power value or the second preamble received target power value is based at least in part on the indicator.
  • the transmission component 1504 may transmit, via a PDCCH order DCI that includes an SRS resource indication field, an indication to use an uplink pathloss associated with a TCI state of an indicated SRS resource or use a pathloss offset associated with the TCI state of the indicated SRS resource.
  • the transmission component 1504 may transmit a PDCCH order DCI that includes a TCI field to indicate a TCI state for a PDCCH ordered PRACH transmission.
  • the reception component 1502 may receive the PDCCH ordered PRACH transmission based at least in part on the TCI field.
  • Fig. 15 The number and arrangement of components shown in Fig. 15 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 15. Furthermore, two or more components shown in Fig. 15 may be implemented within a single component, or a single component shown in Fig. 15 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 15 may perform one or more functions described as being performed by another set of components shown in Fig. 15.
  • a method of wireless communication performed by a user equipment comprising: receiving a physical downlink control channel (PDCCH) order downlink control information (DCI) that includes an indicator to indicate whether a transmit (Tx) beam of a physical random access channel (PRACH) transmission is based at least in part on a Tx beam of an associated sounding reference signal (SRS) or based at least in part on a receive (Rx) beam of an associated synchronization signal block (SSB) or channel state information reference signal (CSI-RS) ; and transmitting the PRACH transmission based at least in part on the indicator.
  • PDCCH physical downlink control channel
  • DCI downlink control information
  • Tx transmit
  • PRACH physical random access channel
  • SRS sounding reference signal
  • Rx receive
  • CSI-RS channel state information reference signal
  • Aspect 2 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 of the PRACH transmission is based at least in part on the Tx beam of the associated SRS; or the indicator is set to a second value to indicate that the Tx beam of the PRACH transmission is based at least in part on the Rx beam of the associated SSB or CSI-RS.
  • Aspect 3 The method of any of Aspects 1-2, wherein the indicator is associated with one or more reserved bits in the PDCCH order DCI.
  • Aspect 4 The method of any of Aspects 1-3, wherein the indicator is associated with a PRACH association indicator in the PDCCH order DCI.
  • Aspect 5 The method of Aspect 4, wherein: the PRACH association indicator is set to a first value to indicate that the Tx beam of the PRACH transmission is based at least in part 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 of the PRACH transmission is based at least in part on the Rx beam of the associated SSB or CSI-RS.
  • Aspect 6 The method of any of Aspects 1-5, wherein the indicator is associated with an SRS resource indication field, wherein a first codepoint in the SRS resource indication field indicates that the Tx beam of the PRACH transmission is based at least in part on the Rx beam of the associated SSB or CSI-RS, and a second codepoint in the SRS resource indication field indicates that the Tx beam of the PRACH transmission is based at least in part on the Tx beam of the associated SRS.
  • Aspect 7 The method of any of Aspects 1-6, wherein the UE is associated with an uplink dense environment in which an uplink transmission-reception point (TRP) is different than a downlink TRP.
  • TRP transmission-reception point
  • a method of wireless communication performed by a user equipment (UE) comprising: receiving a configuration that includes a first preamble received target power value and a second preamble received target power value; and transmitting a physical random access channel (PRACH) transmission using the first preamble received target power value or the second preamble received target power value depending on whether the PRACH transmission is to an uplink-only transmission-reception point (TRP) or a downlink TRP.
  • UE user equipment
  • PRACH physical random access channel
  • Aspect 9 The method of Aspect 8, further comprising: selecting the first preamble received target power value or the second preamble received target power value; and determining a PRACH transmission power for the PRACH transmission based at least in part on the first preamble received target power value or the second preamble received target power value.
  • Aspect 10 The method of any of Aspects 8-9, wherein a pathloss between the UE and the uplink-only TRP is less than a pathloss between the UE and the downlink TRP, and a transmit (Tx) power associated with a PRACH transmission to the uplink-only TRP is less than a Tx power associated with a PRACH transmission to the downlink TRP.
  • Tx transmit
  • Aspect 11 The method of any of Aspects 8-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 received target power value, a first maximum number of preamble transmissions, or a first power ramping step value, and the second set of parameters includes one or more of the second preamble received target power value, a second maximum number of preamble transmissions, or a second power ramping step.
  • Aspect 12 The method of Aspect 11, wherein the second set of parameters are applicable to only a PDCCH-ordered random access channel (RACH) , or the second set of parameters are applicable to the PDCCH-ordered RACH and other PRACH transmissions.
  • RACH PDCCH-ordered random access channel
  • Aspect 13 The method of Aspect 11, wherein the second set of parameters are configured for only a four-step RACH procedure, or the second set of parameters are configured for the four-step RACH procedure and a two-step RACH procedure.
  • Aspect 14 The method of Aspect 11, further comprising: receiving a physical downlink control channel (PDCCH) order downlink control information (DCI) that includes an indicator; and selecting the first set of parameters or the second set of parameters based at least in part on the indicator.
  • PDCCH physical downlink control channel
  • DCI downlink control information
  • Aspect 15 The method of Aspect 14, wherein: the indicator is set to a first value to indicate that the first set of parameters is to be used; or the indicator is set to a second value to indicate that the second set of parameters is to be used.
  • Aspect 16 The method of Aspect 11, further comprising: selecting the first set of parameters or the second set of parameters based at least in part on a transmit (Tx) beam of the PRACH transmission, wherein: the set of parameters is selected based at least in part on the Tx beam of the PRACH transmission being based at least in part on a receive (Rx) beam of an associated synchronization signal block (SSB) or channel state information reference signal (CSI-RS) , or the second set of parameters is selected based at least in part on the Tx beam of the PRACH transmission being based at least in part on a Tx beam of an associated sounding reference signal (SRS) .
  • Tx transmit
  • Rx receive
  • SSB synchronization signal block
  • CSI-RS channel state information reference signal
  • SRS sounding reference signal
  • Aspect 17 The method of any of Aspects 8-16, further comprising: receiving, via a physical downlink control channel (PDCCH) order downlink control information (DCI) that includes a sounding reference signal (SRS) resource indication field, an indication to use an uplink pathloss associated with a transmission configuration indicator (TCI) state of an indicated SRS resource or use a pathloss offset associated with the TCI state of the indicated SRS resource.
  • PDCCH physical downlink control channel
  • DCI sounding reference signal
  • TCI transmission configuration indicator
  • Aspect 18 The method of any of Aspects 8-17, wherein the UE is associated with an uplink dense environment in which an uplink transmission-reception point (TRP) is different than a downlink TRP.
  • TRP transmission-reception point
  • a method of wireless communication performed by a user equipment (UE) comprising: receiving a physical downlink control channel (PDCCH) order downlink control information (DCI) that includes a transmission configuration indicator (TCI) field to indicate a TCI state for a PDCCH ordered physical random access channel (PRACH) transmission; and transmitting the PDCCH ordered PRACH transmission based at least in part on the TCI field.
  • PDCCH physical downlink control channel
  • DCI downlink control information
  • TCI transmission configuration indicator
  • PRACH physical random access channel
  • Aspect 20 The method of Aspect 19, wherein: the TCI field indicates a TCI state identifier; or the TCI field indicates an active TCI state of one or more active TCI states, and the TCI field indicates a TCI codepoint that maps to the active TCI state.
  • Aspect 21 The method of any of Aspects 19-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 a transmit (Tx) beam and a power control for the PDCCH ordered PRACH transmission are based at least in part on the TCI state; or applying the TCI state based at least in part on a one-bit indicator in the PDCCH order DCI, wherein the Tx beam and the power control for the PDCCH ordered PRACH transmission are based at least in part on the TCI state.
  • SSB synchronization signal block
  • CSI-RS channel state information reference signal
  • SRS sounding reference signal
  • Aspect 22 The method of Aspect 21, further comprising: applying a pathloss offset associated with the TCI state for the power control.
  • Aspect 23 The method of any of Aspects 19-22, wherein the UE is associated with an uplink dense environment in which an uplink transmission-reception point (TRP) is different than a downlink TRP.
  • TRP transmission-reception point
  • a method of wireless communication performed by a network node comprising: transmitting a physical downlink control channel (PDCCH) order downlink control information (DCI) that includes an indicator to indicate whether a transmit (Tx) beam of a physical random access channel (PRACH) transmission is based at least in part on a Tx beam of an associated sounding reference signal (SRS) or based at least in part on a receive (Rx) beam of an associated synchronization signal block (SSB) or channel state information reference signal (CSI-RS) ; and receiving the PRACH transmission based at least in part on the indicator.
  • PDCCH physical downlink control channel
  • DCI downlink control information
  • Tx transmit
  • PRACH physical random access channel
  • SRS sounding reference signal
  • Rx receive
  • CSI-RS channel state information reference signal
  • Aspect 25 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 of the PRACH transmission is based at least in part on the Tx beam of the associated SRS; or the indicator is set to a second value to indicate that the Tx beam of the PRACH transmission is based at least in part on the Rx beam of the associated SSB or CSI-RS.
  • Aspect 26 The method of any of Aspects 24-25, wherein the indicator is associated with one or more reserved bits in the PDCCH order DCI.
  • Aspect 27 The method of any of Aspects 24-26, wherein the indicator is associated with a PRACH association indicator in the PDCCH order DCI.
  • Aspect 28 The method of Aspect 27, wherein: the PRACH association indicator is set to a first value to indicate that the Tx beam of the PRACH transmission is based at least in part 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 of the PRACH transmission is based at least in part on the Rx beam of the associated SSB or CSI-RS.
  • Aspect 29 The method of any of Aspects 24-28, wherein the indicator is associated with an SRS resource indication field, wherein a first codepoint in the SRS resource indication field indicates that the Tx beam of the PRACH transmission is based at least in part on the Rx beam of the associated SSB or CSI-RS, and a second codepoint in the SRS resource indication field indicates that the Tx beam of the PRACH transmission is based at least in part on the Tx beam of the associated SRS.
  • Aspect 30 The method of any of Aspects 24-29, wherein the network node is associated with an uplink dense environment in which an uplink transmission-reception point (TRP) is different than a downlink TRP.
  • TRP transmission-reception point
  • a method of wireless communication performed by a network node comprising: transmitting a configuration that includes a first preamble received target power value and a second preamble received target power value; and receiving a physical random access channel (PRACH) transmission using the first preamble received target power value or the second preamble received target power value depending on whether the PRACH transmission is to an uplink-only transmission-reception point (TRP) or a downlink TRP.
  • PRACH physical random access channel
  • Aspect 32 The method of Aspect 31, wherein a PRACH transmission power for the PRACH transmission is based at least in part on the first preamble received target power value or the second preamble received target power value.
  • Aspect 33 The method of any of Aspects 31-32, wherein a pathloss between a user equipment (UE) and the uplink-only TRP is less than a pathloss between the UE and the downlink TRP, and a transmit (Tx) power associated with a PRACH transmission to the uplink-only TRP is less than a Tx power associated with a PRACH transmission to the downlink TRP.
  • UE user equipment
  • Tx transmit
  • Aspect 34 The method of any of Aspects 31-33, wherein the configuration includes a first set of parameters and a second set of parameters, wherein the first set of parameters includes the first preamble received target power value, a first maximum number of preamble transmissions, and a first power ramping step value, and the second set of parameters includes the second preamble received target power value, a second maximum number of preamble transmissions, and a second power ramping step.
  • Aspect 35 The method of Aspect 34, wherein the second set of parameters are applicable to only a PDCCH-ordered random access channel (RACH) , or the second set of parameters are applicable to the PDCCH-ordered RACH and other PRACH transmissions.
  • RACH PDCCH-ordered random access channel
  • Aspect 36 The method of Aspect 34, wherein the second set of parameters are configured for only a four-step RACH procedure, or the second set of parameters are configured for the four-step RACH procedure and a two-step RACH procedure.
  • Aspect 37 The method of any of Aspects 31-36, further comprising: transmitting a physical downlink control channel (PDCCH) order downlink control information (DCI) that includes an indicator, wherein the first preamble received target power value or the second preamble received target power value is based at least in part on the indicator.
  • PDCCH physical downlink control channel
  • DCI downlink control information
  • Aspect 40 The method of any of Aspects 31-39, further comprising: transmitting, via a physical downlink control channel (PDCCH) order downlink control information (DCI) that includes a sounding reference signal (SRS) resource indication field, an indication to use an uplink pathloss associated with a transmission configuration indicator (TCI) state of an indicated SRS resource or use a pathloss offset associated with the TCI state of the indicated SRS resource.
  • PDCCH physical downlink control channel
  • DCI downlink control information
  • SRS sounding reference signal
  • TCI transmission configuration indicator
  • Aspect 41 The method of any of Aspects 31-40, wherein the network node is associated with an uplink dense environment in which an uplink transmission-reception point (TRP) is different than a downlink TRP.
  • TRP transmission-reception point
  • a method of wireless communication performed by a network node comprising: transmitting a physical downlink control channel (PDCCH) order downlink control information (DCI) that includes a transmission configuration indicator (TCI) field to indicate a TCI state for a PDCCH ordered physical random access channel (PRACH) transmission; and receiving the PDCCH ordered PRACH transmission based at least in part on the TCI field.
  • PDCCH physical downlink control channel
  • DCI downlink control information
  • TCI transmission configuration indicator
  • PRACH physical random access channel
  • Aspect 43 The method of Aspect 42, wherein: the TCI field indicates a TCI state identifier; or the TCI field indicates an active TCI state of one or more active TCI states, and the TCI field indicates a TCI codepoint that maps to the active TCI state.
  • Aspect 44 The method of any of Aspects 42-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 a transmit (Tx) beam and a power control for the PDCCH ordered PRACH transmission are based at least in part on the TCI state; or the TCI state is applied based at least in part on a one-bit indicator in the PDCCH order DCI, wherein the Tx beam and the power control for the PDCCH ordered PRACH transmission are based at least in part on the TCI state.
  • SSB synchronization signal block
  • CSI-RS channel state information reference signal
  • SRS sounding reference signal
  • Aspect 45 The method of Aspect 44, wherein a pathloss offset associated with the TCI state is applied for the power control.
  • Aspect 46 The method of any of Aspects 42-45, wherein the network node is associated with an uplink dense environment in which an uplink transmission-reception point (TRP) is different than a downlink TRP.
  • TRP transmission-reception point
  • Aspect 47 An apparatus for wireless communication at a device, the apparatus comprising one or more processors; one or more memories coupled with 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 of one or more of Aspects 1-23.
  • a device for wireless communication comprising a processing system that includes one or more processors and one or more memories coupled with the one or more processors, the processing system configured to cause the device to perform the method of one or more of Aspects 1-23.
  • 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 configured to cause the device to perform the method of one or more of Aspects 24-46.
  • 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 individually or collectively configured to cause the device to perform the method of one or more of Aspects 24-46.
  • a component being configured to perform a function means that the component has a capability to perform the function, and does not require the function to be actually performed by the component, unless noted otherwise.
  • a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members.
  • “at least one of: 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 multiples of the same element (for example, 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, or any other ordering of a, b, and c) .
  • the terms “has, ” “have, ” “having, ” and similar terms are intended to be open-ended terms that do not limit an element that they modify (for example, an element “having” A may also have B) .
  • the phrase “based on” is intended to mean “based on or otherwise in association with” unless explicitly stated otherwise.
  • the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or, ” unless explicitly stated otherwise (for example, if used in combination with “either” or “only one of” ) . It should be understood that “one or more” is equivalent to “at least one. ”

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Divers aspects de la présente divulgation se rapportent, de façon générale, à une communication sans fil. Selon certains aspects, un équipement utilisateur (UE) peut recevoir des informations de commande de liaison descendante (DCI) d'ordre de canal physique de contrôle descendant (PDCCH) qui comprennent un indicateur pour indiquer si un faisceau d'émission (Tx) d'une émission de canal physique à accès aléatoire (PRACH) est basé au moins en partie sur un faisceau Tx d'un signal de référence de sondage (SRS) associé ou sur la base, au moins en partie, d'un faisceau de réception (Rx) d'un bloc de signal de synchronisation (SSB) ou d'un signal de référence d'informations d'état de canal (CSI-RS) associé. L'UE peut émettre l'émission PRACH sur la base, au moins en partie, de l'indicateur. De nombreux autres aspects sont décrits.
PCT/CN2024/084009 2024-03-27 2024-03-27 Émissions de canal d'accès aléatoire physique sur la base d'informations de commande de liaison descendante Pending WO2025199786A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/084009 WO2025199786A1 (fr) 2024-03-27 2024-03-27 Émissions de canal d'accès aléatoire physique sur la base d'informations de commande de liaison descendante

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/084009 WO2025199786A1 (fr) 2024-03-27 2024-03-27 Émissions de canal d'accès aléatoire physique sur la base d'informations de commande de liaison descendante

Publications (1)

Publication Number Publication Date
WO2025199786A1 true WO2025199786A1 (fr) 2025-10-02

Family

ID=97218352

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/084009 Pending WO2025199786A1 (fr) 2024-03-27 2024-03-27 Émissions de canal d'accès aléatoire physique sur la base d'informations de commande de liaison descendante

Country Status (1)

Country Link
WO (1) WO2025199786A1 (fr)

Similar Documents

Publication Publication Date Title
WO2025199786A1 (fr) Émissions de canal d'accès aléatoire physique sur la base d'informations de commande de liaison descendante
WO2025222361A1 (fr) Sélection d'un état d'indication de configuration de transmission pour une transmission de canal physique d'accès aléatoire
US20250280301A1 (en) Beam combining in distributed antenna arrays
US20250280365A1 (en) Physical uplink shared channel power control
US20250159515A1 (en) On-demand synchronization signal block or system information block procedure
US20250350396A1 (en) Fidelity indications for wireless transmissions
WO2025166712A1 (fr) Commande de puissance en boucle fermée pour transmissions de signal de référence de sondage
US20250301308A1 (en) Limited transmission bandwidth capability
US20250317909A1 (en) Aggregation factor parameter for control plane
US20250386279A1 (en) System information blocks without downlink control information
US20250351182A1 (en) Random access channel power control
US20250294483A1 (en) Synchronization signal block communications
WO2025102231A1 (fr) Rapport de marge de puissance dans une opération de point d'émission et de réception multiple
WO2025231787A1 (fr) Synchronisation à la demande pour dispositif internet des objets ambiant
WO2025208550A1 (fr) Techniques destinées à un balayage de faisceau de réception lancé par un équipement utilisateur
WO2025091200A1 (fr) Commande de puissance séparée pour transmissions de signaux de référence de sondage
US20250142458A1 (en) Robust action frame transmission
US20250300777A1 (en) Inter-cell interference reduction and management
WO2025199790A1 (fr) Format de dci 2_3 brouillé par différents identifiants temporaires de réseau radio de signal de référence de sondage de commande de puissance d'émission
US20250294482A1 (en) Synchronization signal block transmissions in non-anchor cells
US20250247869A1 (en) Indication for full-duplex-aware devices
WO2025171537A1 (fr) Rapport de faisceau dans un élément de commande de commande d'accès au support
WO2025208567A1 (fr) Port bloqué pour transmission de signal de référence de sondage sur trois ports
WO2025231680A1 (fr) Contrôle d'accès aléatoire dans des symboles en duplex intégral de sous-bande
WO2025171571A1 (fr) Rapport d'informations d'état de canal associées à des résultats de prédiction de faisceau

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24932027

Country of ref document: EP

Kind code of ref document: A1