[go: up one dir, main page]

WO2025171575A1 - Techniques for two-step random access procedures using dedicated sub-band full duplex resources - Google Patents

Techniques for two-step random access procedures using dedicated sub-band full duplex resources

Info

Publication number
WO2025171575A1
WO2025171575A1 PCT/CN2024/077262 CN2024077262W WO2025171575A1 WO 2025171575 A1 WO2025171575 A1 WO 2025171575A1 CN 2024077262 W CN2024077262 W CN 2024077262W WO 2025171575 A1 WO2025171575 A1 WO 2025171575A1
Authority
WO
WIPO (PCT)
Prior art keywords
duplex
pusch
full
rach
occasions
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/077262
Other languages
French (fr)
Inventor
Muhammad Sayed Khairy Abdelghaffar
Ahmed Attia ABOTABL
Chiranjib Saha
Abdelrahman Mohamed Ahmed Mohamed IBRAHIM
Shankar Krishnan
Ruiming Zheng
Umesh PHUYAL
Prasad Reddy KADIRI
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/077262 priority Critical patent/WO2025171575A1/en
Publication of WO2025171575A1 publication Critical patent/WO2025171575A1/en
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
    • H04W74/0836—Random access procedures, e.g. with 4-step access with 2-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/14—Two-way operation using the same type of signal, i.e. duplex

Definitions

  • the following relates to wireless communications, including techniques for two-step random access channel procedures using dedicated sub-band full-duplex (SBFD) resources.
  • SBFD sub-band full-duplex
  • Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) .
  • Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems.
  • 4G systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems
  • 5G systems which may be referred to as New Radio (NR) systems.
  • a wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE) .
  • UE user equipment
  • Different networks may utilize different types of access procedures to enable wireless devices (e.g., UEs) to connect to and access the networks, such as four-step random access channel (RACH) procedures and two-step RACH procedures.
  • RACH random access channel
  • current RACH procedures only utilize resources configured within legacy half-duplex slots.
  • conventional RACH procedures have no mechanisms for utilizing full-duplex slots for transmitting MsgA, such as sub-band full-duplex (SBFD) uplink bands positioned within downlink slots.
  • SBFD sub-band full-duplex
  • the described techniques relate to improved methods, systems, devices, and apparatuses that support techniques for two-step random access channel procedures using dedicated sub-band full-duplex (SBFD) resources. That is, aspects of the present disclosure are directed to signaling and configurations that utilize full-duplex slots (e.g., SBFD slots) to communicate messages associated with RACH procedures.
  • SBFD sub-band full-duplex
  • aspects of the present disclosure are directed to RACH configurations that configure wireless devices with dedicated full-duplex RACH occasions (ROs) (e.g., SBFD ROs) and/or dedicated full-duplex physical uplink shared channel (PUSCH) occasions (POs) (e.g., SBFD POs) to enable the UEs to perform at least a portion of a first message (e.g., MsgA) of a two-step RACH procedure within full-duplex slots.
  • ROs full-duplex RACH occasions
  • PUSCH physical uplink shared channel
  • a method by a UE may include receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a RACH configuration including a set of multiple common RACH occasions within a first half-duplex uplink slot, receiving, via the first control signaling, second control signaling, or both, a first physical uplink shared channel (PUSCH) configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or more full-duplex slots, transmitting a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the set of multiple common RACH occasions, transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PU
  • the UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories.
  • the one or more processors may individually or collectively be operable to execute the code to cause the UE to receive, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a RACH configuration including a set of multiple common RACH occasions within a first half-duplex uplink slot, receive, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or more full-duplex slots, transmit a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion
  • the UE may include means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a RACH configuration including a set of multiple common RACH occasions within a first half-duplex uplink slot, means for receiving, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or more full-duplex slots, means for transmitting a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the set of multiple common RACH occasions, means for transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH
  • a non-transitory computer-readable medium storing code is described.
  • the code may include instructions executable by one or more processors to receive, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a RACH configuration including a set of multiple common RACH occasions within a first half-duplex uplink slot, receive, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or more full-duplex slots, transmit a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the set of multiple common RACH occasions, transmit a payload of the first message of the two-step random access procedure
  • Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of multiple common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the set of multiple preambles of the set of multiple common RACH occasions and the set of full-duplex PUSCH occasions and selecting one of the common PUSCH occasion or the full-duplex PUSCH occasion that maps to the common RACH occasion used to transmit the preamble in accordance with the first mapping configuration or the second mapping configuration, where the payload of the first message may be transmitted via the selected one of the common PUSCH occasion or the full-duplex PUSCH occasion.
  • each common RACH occasion from the set of multiple common RACH occasions may be mapped to a set of multiple full-duplex PUSCH occasions from the set of full-duplex PUSCH occasions.
  • the second PUSCH configuration includes a first sub-configuration associated with a first preamble group including the set of full-duplex PUSCH occasions, and a second sub-configuration associated with a second preamble group including an additional set of full-duplex PUSCH occasions.
  • Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for selecting one of the common PUSCH occasion or the full-duplex PUSCH occasion that maps to the common RACH occasion based on a relative timing of the common PUSCH occasion and the full-duplex PUSCH occasion in a time domain, one or more measured or predicted downlink signal quality metrics associated with slots that include the common PUSCH occasion and the full-duplex PUSCH occasion, a radio resource control configuration, a PUSCH transmission power relative to a transmission power threshold associated with the one or more full-duplex slots, a type of UE, or any combination thereof, where the payload of the first message of the two-step random access procedure may be transmitted via the selected one of the common PUSCH occasion or the full-duplex PUSCH occasion.
  • Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining a validity of each full-duplex PUSCH occasion within the set of full-duplex PUSCH occasions based on a type of slot corresponding to each of the set of full-duplex PUSCH occasions, the type of slot including a full-duplex slot type or a half-duplex slot type.
  • determining the validity of each full-duplex PUSCH occasion may include operations, features, means, or instructions for determining that each full-duplex PUSCH occasion of the set of full-duplex PUSCH occasions may be valid regardless of the type of slot in accordance with a first validity rule and determining that a subset of PUSCH occasions from the set of full-duplex PUSCH occasions may be invalid based on the subset of PUSCH occasions being positioned within non-full-duplex slots and in accordance with a second validity rule.
  • Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for monitoring a set of multiple synchronization signal blocks, the set of multiple synchronization signal blocks corresponding with the set of multiple common RACH occasions and selecting the common RACH occasion from the set of multiple common RACH occasions based on the monitoring.
  • the set of full-duplex PUSCH occasions include SBFD PUSCH occasions and the one or more full-duplex slots include one or more SBFD slots.
  • the first PUSCH configuration indicates a first quantity of frequency-division multiplexed PUSCH occasions associated with the set of common PUSCH occasions within the one or more second half-duplex uplink slots and the second PUSCH configuration indicates a second quantity of frequency-division multiplexed PUSCH occasions associated with the set of full-duplex PUSCH occasions within the one or more full-duplex slots.
  • the set of multiple common RACH occasions and the set of common PUSCH occasions may be usable by full-duplex-aware UEs and non-full-duplex-aware UEs and the set of full-duplex PUSCH occasions may be usable by full-duplex-aware UEs but unusable by non-full-duplex-aware UEs.
  • a method by a UE may include receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, receiving, via the first control signaling, second control signaling, or both, a PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the set of multiple PUSCH occasions including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of
  • the UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories.
  • the one or more processors may individually or collectively be operable to execute the code to cause the UE to receive, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, receive, via the first control signaling, second control signaling, or both, a PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the set of multiple PUSCH occasions including a set of common PUSCH occasions within one or
  • the UE may include means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, means for receiving, via the first control signaling, second control signaling, or both, a PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the set of multiple PUSCH occasions including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, means for transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from
  • a non-transitory computer-readable medium storing code is described.
  • the code may include instructions executable by one or more processors to receive, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, receive, via the first control signaling, second control signaling, or both, a PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the set of multiple PUSCH occasions including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, transmit a preamble of a first message of the two-step random
  • the first half-duplex uplink slot including the set of common RACH occasions includes a PRACH slot and the PUSCH configuration includes a first time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common PUSCH occasions, and a second time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common PUSCH occasions.
  • Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the set of multiple preambles of the set of full-duplex RACH occasions and the set of common PUSCH occasions.
  • each common PUSCH occasion from the set of common PUSCH occasions may be mapped to at least one common RACH occasion from the set of common RACH occasions and at least one full-duplex RACH occasion from the set of full-duplex RACH occasions.
  • Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for selecting one of the common RACH occasion or the full-duplex RACH occasion based on a relative timing of the common RACH occasion and the full-duplex RACH occasion in a time domain, one or more measured or predicted signal quality metrics associated with slots that include the common RACH occasion and the full-duplex RACH occasion, a PUSCH transmission power relative to a transmission power threshold associated with the one or more full-duplex slots, a radio resource control configuration, a type of UE, or any combination thereof, where the preamble of the first message of the two-step random access procedure may be transmitted via the selected one of the common RACH occasion or the full-duplex RACH occasion.
  • Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining a validity of each full-duplex RACH occasion within the set of full-duplex RACH occasions based on a type of slot corresponding to each of the set of full-duplex RACH occasions, the type of slot including a full-duplex slot type or a half-duplex slot type.
  • determining the validity of each full-duplex RACH occasion may include operations, features, means, or instructions for determining that each full-duplex RACH occasion of the set of full-duplex RACH occasions may be valid regardless of the type of slot in accordance with a first validity rule and determining that a subset of RACH occasions from the set of full-duplex RACH occasions may be invalid based on the subset of RACH occasions being positioned within non-full-duplex slots and in accordance with a second validity rule.
  • the set of full-duplex RACH occasions include a first subset of full-duplex RACH occasions within the one or more full-duplex slots, and a second subset of full-duplex RACH occasions that overlap in a time domain with the set of common RACH occasions within the first half-duplex uplink slot
  • the set of common RACH occasions and the set of full-duplex RACH occasions may be associated with a set of multiple preambles such that temporally overlapping pairs of RACH occasions map to one or more common preambles of the set of multiple preambles
  • each temporally overlapping pair of RACH occasions include one of the second subset of full-duplex RACH occasions and one of the set of common RACH occasions.
  • the set of full-duplex RACH occasions include SBFD RACH occasions and the one or more full-duplex slots include one or more SBFD slots.
  • a method by a UE may include receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, receiving, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or additional more full-duplex slots, where the set of common RACH occasions are mapped to the set of common PUSCH occasions, and where the set of full-duplex RACH occasions mapped to
  • the UE may include means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, means for receiving, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or additional more full-duplex slots, where the set of common RACH occasions are mapped to the set of common PUSCH occasions, and where the set of full-duplex RACH occasions mapped
  • a non-transitory computer-readable medium storing code is described.
  • the code may include instructions executable by one or more processors to receive, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, receive, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or additional more full-duplex slots, where the set of common RACH occasions are mapped to the set of common
  • Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the set of multiple preambles of the set of full-duplex RACH occasions and the set of full-duplex PUSCH occasions.
  • Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the first control signaling, the second control signaling, or both, an indication that the first RACH configuration, second RACH configuration, the first PUSCH configuration, the second PUSCH configuration, or any combination thereof, may be usable for performing random access procedures associated with system information requests, physical downlink control channel ordering, beam failure recovery, mobility, or any combination thereof.
  • Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the first control signaling, the second control signaling, or both, an indication that the second RACH configuration, the second PUSCH configuration, or both, include UE-specific configurations or cell-specific configurations.
  • Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the first control signaling, the second control signaling, third control signaling, or any combination thereof, a common random access configuration associated with one or more operations different from the two-step random access procedure and performing the one or more operations in accordance with either the common random access configuration, or in accordance with the second RACH configuration and the second PUSCH configuration.
  • Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that the UE may have not been configured with a common random access configuration associated with one or more operations different from the two-step random access procedure and performing the one or more operations in accordance with the first RACH configuration and the first PUSCH configuration, or in accordance with the second RACH configuration and the second PUSCH configuration.
  • a method by a network entity may include transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a RACH configuration including a set of multiple common RACH occasions within a first half-duplex uplink slot, transmitting, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or more full-duplex slots, receiving a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the set of multiple common RACH occasions, receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion
  • the network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories.
  • the one or more processors may individually or collectively be operable to execute the code to cause the network entity to transmit, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a RACH configuration including a set of multiple common RACH occasions within a first half-duplex uplink slot, transmit, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or more full-duplex slots, receive a preamble of a first message of the two-step random access procedure to the network entity via a
  • the network entity may include means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a RACH configuration including a set of multiple common RACH occasions within a first half-duplex uplink slot, means for transmitting, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or more full-duplex slots, means for receiving a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the set of multiple common RACH occasions, means for receiving a payload of the first message of the two-step random access procedure to the network entity either via a
  • a non-transitory computer-readable medium storing code is described.
  • the code may include instructions executable by one or more processors to transmit, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a RACH configuration including a set of multiple common RACH occasions within a first half-duplex uplink slot, transmit, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or more full-duplex slots, receive a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the set of multiple common RACH occasions, receive a payload of the first message of the two-
  • Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of multiple common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the set of multiple preambles of the set of multiple common RACH occasions and the set of full-duplex PUSCH occasions and identifying one of the common PUSCH occasion or the full-duplex PUSCH occasion that maps to the common RACH occasion used to transmit the preamble in accordance with the first mapping configuration or the second mapping configuration, where the payload of the first message may be received via the identified one of the common PUSCH occasion or the full-duplex PUSCH occasion.
  • the second PUSCH configuration includes a first sub-configuration associated with a first preamble group including the set of full-duplex PUSCH occasions, and a second sub-configuration associated with a second preamble group including an additional set of full-duplex PUSCH occasions.
  • Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying one of the common PUSCH occasion or the full-duplex PUSCH occasion that maps to the common RACH occasion based on a relative timing of the common PUSCH occasion and the full-duplex PUSCH occasion in a time domain, one or more measured or predicted downlink signal quality metrics associated with slots that include the common PUSCH occasion and the full-duplex PUSCH occasion, a radio resource control configuration, a PUSCH transmission power relative to a transmission power threshold associated with the one or more full-duplex slots, a type of UE, or any combination thereof, where the payload of the first message of the two-step random access procedure may be received via the identified one of the common PUSCH occasion or the full-duplex PUSCH occasion.
  • Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining a validity of each full-duplex PUSCH occasion within the set of full-duplex PUSCH occasions based on a type of slot corresponding to each of the set of full-duplex PUSCH occasions, the type of slot including a full-duplex slot type or a half-duplex slot type.
  • determining the validity of each full-duplex PUSCH occasion may include operations, features, means, or instructions for determining that each full-duplex PUSCH occasion of the set of full-duplex PUSCH occasions may be valid regardless of the type of slot in accordance with a first validity rule and determining that a subset of PUSCH occasions from the set of full-duplex PUSCH occasions may be invalid based on the subset of PUSCH occasions being positioned within non-full-duplex slots and in accordance with a second validity rule.
  • the set of full-duplex PUSCH occasions include a first subset of full-duplex PUSCH occasions within the one or more full-duplex slots, and a second subset of full-duplex PUSCH occasions that overlap in a time domain with the set of common PUSCH occasions within the one or more second half-duplex uplink slots
  • the set of multiple common RACH occasions may be associated with a set of multiple preambles
  • the set of multiple preambles may be mapped to the set of common PUSCH occasions and the set of full-duplex PUSCH occasions such that temporally overlapping pairs of PUSCH occasions may be associated with one or more common preambles of the set of multiple preambles
  • each temporally overlapping pair of PUSCH occasions include one of the second subset of full-duplex PUSCH occasions and one of the set of common PUSCH occasions.
  • the set of full-duplex PUSCH occasions include SBFD PUSCH occasions and the one or more full-duplex slots include one or more SBFD slots.
  • the first PUSCH configuration indicates a first starting resource block frequency configuration associated with the set of common PUSCH occasions and the second PUSCH configuration indicates a second starting resource block frequency configuration associated with the set of full-duplex PUSCH occasions.
  • the first PUSCH configuration indicates a first quantity of frequency-division multiplexed PUSCH occasions associated with the set of common PUSCH occasions within the one or more second half-duplex uplink slots and the second PUSCH configuration indicates a second quantity of frequency-division multiplexed PUSCH occasions associated with the set of full-duplex PUSCH occasions within the one or more full-duplex slots.
  • the set of multiple common RACH occasions and the set of common PUSCH occasions may be usable by full-duplex-aware UEs and non-full-duplex-aware UEs and the set of full-duplex PUSCH occasions may be usable by full-duplex-aware UEs but unusable by non-full-duplex-aware UEs.
  • a method by a network entity may include transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, transmitting, via the first control signaling, second control signaling, or both, a PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the set of multiple PUSCH occasions including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH
  • the network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories.
  • the one or more processors may individually or collectively be operable to execute the code to cause the network entity to transmit, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, transmit, via the first control signaling, second control signaling, or both, a PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the set of multiple PUSCH occasions including a set of common PUSCH
  • the network entity may include means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, means for transmitting, via the first control signaling, second control signaling, or both, a PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the set of multiple PUSCH occasions including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, means for receiving a preamble of a first message of the two-step random access procedure to the network entity either via a
  • a non-transitory computer-readable medium storing code is described.
  • the code may include instructions executable by one or more processors to transmit, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, transmit, via the first control signaling, second control signaling, or both, a PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the set of multiple PUSCH occasions including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, receive a preamble of a first message of the
  • the first half-duplex uplink slot including the set of common RACH occasions includes a PRACH slot and the PUSCH configuration includes a first time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common PUSCH occasions, and a second time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common PUSCH occasions.
  • Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the set of multiple preambles of the set of full-duplex RACH occasions and the set of common PUSCH occasions.
  • each common PUSCH occasion from the set of common PUSCH occasions may be mapped to at least one common RACH occasion from the set of common RACH occasions and at least one full-duplex RACH occasion from the set of full-duplex RACH occasions.
  • Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying one of the common RACH occasion or the full-duplex RACH occasion based on a relative timing of the common RACH occasion and the full-duplex RACH occasion in a time domain, one or more measured or predicted signal quality metrics associated with slots that include the common RACH occasion and the full-duplex RACH occasion, a PUSCH transmission power relative to a transmission power threshold associated with the one or more full-duplex slots, a radio resource control configuration, a type of UE, or any combination thereof, where the preamble of the first message of the two-step random access procedure may be received via the identified one of the common RACH occasion or the full-duplex RACH occasion.
  • Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining a validity of each full-duplex RACH occasion within the set of full-duplex RACH occasions based on a type of slot corresponding to each of the set of full-duplex RACH occasions, the type of slot including a full-duplex slot type or a half-duplex slot type.
  • determining the validity of each full-duplex RACH occasion may include operations, features, means, or instructions for determining that each full-duplex RACH occasion of the set of full-duplex RACH occasions may be valid regardless of the type of slot in accordance with a first validity rule and determining that a subset of RACH occasions from the set of full-duplex RACH occasions may be invalid based on the subset of RACH occasions being positioned within non-full-duplex slots and in accordance with a second validity rule.
  • the set of full-duplex RACH occasions include a first subset of full-duplex RACH occasions within the one or more full-duplex slots, and a second subset of full-duplex RACH occasions that overlap in a time domain with the set of common RACH occasions within the first half-duplex uplink slot
  • the set of common RACH occasions and the set of full-duplex RACH occasions may be associated with a set of multiple preambles such that temporally overlapping pairs of RACH occasions map to one or more common preambles of the set of multiple preambles
  • each temporally overlapping pair of RACH occasions include one of the second subset of full-duplex RACH occasions and one of the set of common RACH occasions.
  • the set of full-duplex RACH occasions include SBFD RACH occasions and the one or more full-duplex slots include one or more SBFD slots.
  • a method by a network entity may include transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, transmitting, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or additional more full-duplex slots, where the set of common RACH occasions are mapped to the set of common PUSCH occasions, and where the set of full-duplex
  • the network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories.
  • the one or more processors may individually or collectively be operable to execute the code to cause the network entity to transmit, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, transmit, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex
  • a non-transitory computer-readable medium storing code is described.
  • the code may include instructions executable by one or more processors to transmit, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, transmit, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or additional more full-duplex slots, where the set of common RACH occasions are mapped to the
  • Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the set of multiple preambles of the set of full-duplex RACH occasions and the set of full-duplex PUSCH occasions.
  • Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, via the first control signaling, the second control signaling, or both, a third mapping configuration between the set of multiple preambles of set of common RACH occasions and the set of full-duplex PUSCH occasions, a fourth mapping configuration between the set of multiple preambles of the set of full-duplex RACH occasions and the set of common PUSCH occasions, or both.
  • the set of full-duplex RACH occasions include SBFD RACH occasions
  • the set of full-duplex PUSCH occasions include SBFD PUSCH occasions
  • the one or more full-duplex slots, the one or more additional full-duplex slots, or both include one or more SBFD slots.
  • Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, via the first control signaling, the second control signaling, or both, an indication that the first RACH configuration, second RACH configuration, the first PUSCH configuration, the second PUSCH configuration, or any combination thereof, may be usable for performing random access procedures associated with system information requests, physical downlink control channel ordering, beam failure recovery, mobility, or any combination thereof.
  • Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, via the first control signaling, the second control signaling, or both, an indication that the second RACH configuration, the second PUSCH configuration, or both, include UE-specific configurations or cell-specific configurations.
  • FIG. 2 shows an example of a two-step random access channel (RACH) procedure configuration that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • RACH random access channel
  • FIG. 3 shows an example of a wireless communications system that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • FIG. 4 shows an example of a resource configuration that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • FIG. 7 shows an example of a resource configuration that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • FIGs. 9 and 10 show block diagrams of devices that support techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • FIG. 11 shows a block diagram of a communications manager that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • FIG. 12 shows a diagram of a system including a device that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • FIGs. 13 and 14 show block diagrams of devices that support techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • FIG. 15 shows a block diagram of a communications manager that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • FIGs. 17 through 19 show flowcharts illustrating methods that support techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • Different networks may utilize different types of access procedures to enable wireless devices (e.g., user equipments (UEs) ) to connect to and access the networks, such as four-step random access channel (RACH) procedures and two-step RACH procedures.
  • RACH random access channel
  • some networks have implemented a two-step RACH procedure, where a UE transmits a first message (MsgA) , and receives a second message (MsgB) back from the network to complete the RACH procedure.
  • the first message (MsgA) transmitted via the UE may include a preamble transmitted within a configured RACH occasion (RO) , and a payload transmitted within a configured physical uplink shared channel (PUSCH) occasion (PO) that maps to the RO used to transmit the preamble.
  • RO RACH occasion
  • PUSCH physical uplink shared channel
  • RACH procedures only utilize ROs and POs configured within legacy half-duplex uplink slots.
  • conventional RACH procedures have no mechanisms for utilizing full-duplex slots for transmitting MsgA, such as sub-band full-duplex (SBFD) uplink bands positioned within downlink slots.
  • SBFD sub-band full-duplex
  • the inability to utilize SBFD slots to perform signaling used for RACH procedures may increase the latency of RACH procedures.
  • requiring all devices to use the same resources within half-duplex slots to perform RACH procedures may increase collisions and noise within such resources, thereby decreasing the efficiency and success probability of such RACH procedures.
  • aspects of the present disclosure are directed to signaling and configurations that utilize full-duplex slots (e.g., SBFD slots) to communicate messages associated with RACH procedures.
  • aspects of the present disclosure are directed to random access configurations that configure UEs with dedicated full-duplex ROs (e.g., SBFD ROs) and/or dedicated full-duplex POs (e.g., SBFD POs) to enable the UEs to perform at least a portion of a MsgA of a two-step RACH procedure within full-duplex slots.
  • dedicated full-duplex ROs e.g., SBFD ROs
  • dedicated full-duplex POs e.g., SBFD POs
  • a random access configuration for a two-step RACH procedure may include (1) dedicated SBFD ROs within full-duplex slots, and/or (2) dedicated POs within full-duplex slots.
  • the random access configuration may indicate mappings between the preambles of legacy ROs, the legacy POs, the SBFD ROs, and/or the SBFD POs.
  • aspects of the disclosure are initially described in the context of wireless communications systems. Additional aspects of the disclosure are described in the context of an example RACH procedure configuration, example resource configurations, and an example process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to techniques for two-step random access procedures using dedicated SBFD resources.
  • FIG. 1 shows an example of a wireless communications system 100 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • the wireless communications system 100 may include one or more devices, such as one or more network devices (e.g., network entities 105) , one or more UEs 115, and a core network 130.
  • the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-A Pro
  • NR New Radio
  • the network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities.
  • a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature.
  • network entities 105 and UEs 115 may wirelessly communicate via communication link (s) 125 (e.g., a radio frequency (RF) access link) .
  • a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish the communication link (s) 125.
  • the coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs) .
  • RATs radio access technologies
  • the UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times.
  • the UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1.
  • the UEs 115 described herein may be capable of supporting communications with various types of devices in the wireless communications system 100 (e.g., other wireless communication devices, including UEs 115 or network entities 105) , as shown in FIG. 1.
  • a node of the wireless communications system 100 which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein) , a UE 115 (e.g., any UE described herein) , a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein.
  • a node may be a UE 115.
  • a node may be a network entity 105.
  • a first node may be configured to communicate with a second node or a third node.
  • the first node may be a UE 115
  • the second node may be a network entity 105
  • the third node may be a UE 115.
  • the first node may be a UE 115
  • the second node may be a network entity 105
  • the third node may be a network entity 105.
  • the first, second, and third nodes may be different relative to these examples.
  • reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node.
  • disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.
  • network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol) , or any combination thereof.
  • the backhaul communication link (s) 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) or one or more wireless links (e.g., a radio link, a wireless optical link) , among other examples or various combinations thereof.
  • a UE 115 may communicate with the core network 130 via a communication link 155.
  • One or more of the network entities 105 or network equipment described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB) , a 5G NB, a next-generation eNB (ng-eNB) , a Home NodeB, a Home eNodeB, or other suitable terminology) .
  • a base station 140 e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or giga-NodeB (either of which may be referred
  • a network entity 105 may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within one network entity (e.g., a network entity 105 or a single RAN node, such as a base station 140) .
  • a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) , which may be configured to utilize a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 105) , such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) .
  • a disaggregated architecture e.g., a disaggregated base station architecture, a disaggregated RAN architecture
  • a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 105) , such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by
  • a network entity 105 may include one or more of a central unit (CU) , such as a CU 160, a distributed unit (DU) , such as a DU 165, a radio unit (RU) , such as an RU 170, a RAN Intelligent Controller (RIC) , such as an RIC 175 (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, such as an SMO system 180, or any combination thereof.
  • a central unit such as a CU 160
  • DU distributed unit
  • RU such as an RU 170
  • a RAN Intelligent Controller (RIC) such as an RIC 175
  • a Near-Real Time RIC Near-RT RIC
  • Non-RT RIC Non-Real Time RIC
  • SMO Service Management and Orchestration
  • An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) .
  • One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations) .
  • one or more of the network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .
  • VCU virtual CU
  • VDU virtual DU
  • VRU virtual RU
  • the split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170.
  • functions e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof
  • a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack.
  • the CU 160 may host upper protocol layer (e.g., layer 3 (L3) , layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) .
  • RRC Radio Resource Control
  • SDAP service data adaption protocol
  • PDCP Packet Data Convergence Protocol
  • the CU 160 may be connected to a DU 165 (e.g., one or more DUs) or an RU 170 (e.g., one or more RUs) , or some combination thereof, and the DUs 165, RUs 170, or both may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.
  • L1 e.g., physical (PHY) layer
  • L2 e.g., radio link control (RLC) layer, medium access control (MAC) layer
  • RLC radio link control
  • MAC medium access control
  • a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack.
  • the DU 165 may support one or multiple different cells (e.g., via one or multiple different RUs, such as an RU 170) .
  • a functional split between a CU 160 and a DU 165 or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170) .
  • a CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions.
  • CU-CP CU control plane
  • CU-UP CU user plane
  • a CU 160 may be connected to a DU 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u) , and a DU 165 may be connected to an RU 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface) .
  • a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities (e.g., one or more of the network entities 105) that are in communication via such communication links.
  • infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130) .
  • IAB network architecture e.g., to a core network 130
  • one or more of the network entities 105 may be partially controlled by each other.
  • the IAB node (s) 104 may be referred to as a donor entity or an IAB donor.
  • a DU 165 or an RU 170 may be partially controlled by a CU 160 associated with a network entity 105 or base station 140 (such as a donor network entity or a donor base station) .
  • the one or more donor entities may be in communication with one or more additional devices (e.g., IAB node (s) 104) via supported access and backhaul links (e.g., backhaul communication link (s) 120) .
  • IAB node (s) 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DUs 165) of a coupled IAB donor.
  • IAB-MT IAB mobile termination
  • An IAB-MT may be equipped with an independent set of antennas for relay of communications with UEs 115 or may share the same antennas (e.g., of an RU 170) of IAB node (s) 104 used for access via the DU 165 of the IAB node (s) 104 (e.g., referred to as virtual IAB-MT (vIAB-MT) ) .
  • the IAB node (s) 104 may include one or more DUs (e.g., DUs 165) that support communication links with additional entities (e.g., IAB node (s) 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream) .
  • one or more components of the disaggregated RAN architecture e.g., the IAB node (s) 104 or components of the IAB node (s) 104) may be configured to operate according to the techniques described herein.
  • an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor) , IAB node (s) 104, and one or more UEs 115.
  • the IAB donor may facilitate connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130) . That is, an IAB donor may refer to a RAN node with a wired or wireless connection to the core network 130.
  • the IAB donor may include one or more of a CU 160, a DU 165, and an RU 170, in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link) .
  • the IAB donor and IAB node (s) 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol) .
  • the CU 160 may communicate with the core network 130 via an interface, which may be an example of a portion of a backhaul link, and may communicate with other CUs (e.g., including a CU 160 associated with an alternative IAB donor) via an Xn-C interface, which may be an example of another portion of a backhaul link.
  • IAB node (s) 104 may refer to RAN nodes that provide IAB functionality (e.g., access for UEs 115, wireless self-backhauling capabilities) .
  • a DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node (s) 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with IAB node (s) 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through other IAB node (s) 104) .
  • IAB node (s) 104 may also be referred to as parent nodes or child nodes to other IAB node (s) 104, depending on the relay chain or configuration of the AN.
  • the IAB-MT entity of IAB node (s) 104 may provide a Uu interface for a child IAB node (e.g., the IAB node (s) 104) to receive signaling from a parent IAB node (e.g., the IAB node (s) 104) , and a DU interface (e.g., a DU 165) may provide a Uu interface for a parent IAB node to signal to a child IAB node or UE 115.
  • a DU interface e.g., a DU 165
  • IAB node (s) 104 may be referred to as parent nodes that support communications for child IAB nodes, or may be referred to as child IAB nodes associated with IAB donors, or both.
  • An IAB donor may include a CU 160 with a wired or wireless connection (e.g., backhaul communication link (s) 120) to the core network 130 and may act as a parent node to IAB node (s) 104.
  • the DU 165 of an IAB donor may relay transmissions to UEs 115 through IAB node (s) 104, or may directly signal transmissions to a UE 115, or both.
  • the CU 160 of the IAB donor may signal communication link establishment via an F1 interface to IAB node (s) 104, and the IAB node (s) 104 may schedule transmissions (e.g., transmissions to the UEs 115 relayed from the IAB donor) through one or more DUs (e.g., DUs 165) . That is, data may be relayed to and from IAB node (s) 104 via signaling via an NR Uu interface to MT of IAB node (s) 104 (e.g., other IAB node (s) ) . Communications with IAB node (s) 104 may be scheduled by a DU 165 of the IAB donor or of IAB node (s) 104.
  • DUs e.g., DUs 165
  • one or more components of the disaggregated RAN architecture may be configured to support test as described herein.
  • some operations described as being performed by a UE 115 or a network entity 105 may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180) .
  • a UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples.
  • a UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA) , a tablet computer, a laptop computer, or a personal computer.
  • PDA personal digital assistant
  • a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, vehicles, or meters, among other examples.
  • WLL wireless local loop
  • IoT Internet of Things
  • IoE Internet of Everything
  • MTC machine type communications
  • the UEs 115 described herein may be able to communicate with various types of devices, such as UEs 115 that may sometimes operate as relays, as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
  • devices such as UEs 115 that may sometimes operate as relays, as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
  • the UEs 115 and the network entities 105 may wirelessly communicate with one another via the communication link (s) 125 (e.g., one or more access links) using resources associated with one or more carriers.
  • the term “carrier” may refer to a set of RF spectrum resources having a defined PHY layer structure for supporting the communication link (s) 125.
  • a carrier used for the communication link (s) 125 may include a portion of an RF spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR) .
  • a given RAT e.g., LTE, LTE-A, LTE-A Pro, NR
  • Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information (SI) ) , control signaling that coordinates operation for the carrier, user data, or other signaling.
  • the wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation.
  • a UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration.
  • Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers.
  • Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105.
  • a carrier may have acquisition signaling or control signaling that coordinates operations for other carriers.
  • a carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN) ) and may be identified according to a channel raster for discovery by the UEs 115.
  • E-UTRA evolved universal mobile telecommunication system terrestrial radio access
  • a carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different RAT) .
  • a carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100.
  • the carrier bandwidth may be one of a set of bandwidths for carriers of a particular RAT (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz) ) .
  • Devices of the wireless communications system 100 e.g., the network entities 105, the UEs 115, or both
  • the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths.
  • each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.
  • Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) ) .
  • MCM multi-carrier modulation
  • OFDM orthogonal frequency division multiplexing
  • DFT-S-OFDM discrete Fourier transform spread OFDM
  • a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related.
  • the quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) , such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication.
  • a wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam) , and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.
  • One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing ( ⁇ f) and a cyclic prefix.
  • a carrier may be divided into one or more BWPs having the same or different numerologies.
  • a UE 115 may be configured with multiple BWPs.
  • a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.
  • Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms) ) .
  • Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023) .
  • SFN system frame number
  • Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration.
  • a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots.
  • each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing.
  • Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) .
  • a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f ) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.
  • a subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI) .
  • TTI duration e.g., a quantity of symbol periods in a TTI
  • the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) ) .
  • Physical channels may be multiplexed for communication using a carrier according to various techniques.
  • a physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques.
  • a control region e.g., a control resource set (CORESET)
  • CORESET control resource set
  • One or more control regions may be configured for a set of the UEs 115.
  • one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner.
  • An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs) ) associated with encoded information for a control information format having a given payload size.
  • Search space sets may include common search space sets configured for sending control information to UEs 115 (e.g., one or more UEs) or may include UE-specific search space sets for sending control information to a UE 115 (e.g., a specific UE) .
  • Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105.
  • a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.
  • Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG) , the UEs 115 associated with users in a home or office) .
  • a network entity 105 may support one or more cells and may also support communications via the one or more cells using one or multiple component carriers.
  • a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB) ) that may provide access for different types of devices.
  • protocol types e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB)
  • NB-IoT narrowband IoT
  • eMBB enhanced mobile broadband
  • a network entity 105 may be movable and therefore provide communication coverage for a moving coverage area, such as the coverage area 110.
  • coverage areas 110 e.g., different coverage areas
  • coverage areas 110 may overlap, but the coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., a network entity 105) .
  • overlapping coverage areas, such as a coverage area 110, associated with different technologies may be supported by different network entities (e.g., the network entities 105) .
  • the wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 support communications for coverage areas 110 (e.g., different coverage areas) using the same or different RATs.
  • the wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof.
  • the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) .
  • the UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions.
  • Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data.
  • Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications.
  • the terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.
  • a UE 115 may be configured to support communicating directly with other UEs (e.g., one or more of the UEs 115) via a device-to-device (D2D) communication link, such as a D2D communication link 135 (e.g., in accordance with a peer-to-peer (P2P) , D2D, or sidelink protocol) .
  • D2D device-to-device
  • P2P peer-to-peer
  • one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170) , which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105.
  • one or more UEs 115 of such a group may be outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105.
  • groups of the UEs 115 communicating via D2D communications may support a one-to-many (1: M) system in which each UE 115 transmits to one or more of the UEs 115 in the group.
  • a network entity 105 may facilitate the scheduling of resources for D2D communications.
  • D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.
  • a D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115) .
  • vehicles may communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these.
  • V2X vehicle-to-everything
  • V2V vehicle-to-vehicle
  • a vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system.
  • vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., network entities 105, base stations 140, RUs 170) using vehicle-to-network (V2N) communications, or with both.
  • roadside infrastructure such as roadside units
  • network nodes e.g., network entities 105, base stations 140, RUs 170
  • V2N vehicle-to-network
  • the core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions.
  • the core network 130 may be an evolved packet core (EPC) or 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management function
  • S-GW serving gateway
  • PDN Packet Data Network gateway
  • UPF user plane function
  • the control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130.
  • NAS non-access stratum
  • User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions.
  • the user plane entity may be connected to IP services 150 for one or more network operators.
  • the IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.
  • IMS IP Multimedia Subsystem
  • the wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) .
  • the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length.
  • UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.
  • HF high frequency
  • VHF very high frequency
  • the wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands.
  • the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) RAT, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
  • LAA License Assisted Access
  • LTE-U LTE-Unlicensed
  • NR NR technology
  • an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
  • devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance.
  • operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA) .
  • Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.
  • a network entity 105 e.g., a base station 140, an RU 170
  • a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming.
  • the antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming.
  • one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower.
  • antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations.
  • a network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115.
  • a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations.
  • an antenna panel may support RF beamforming for a signal transmitted via an antenna port.
  • the network entities 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers.
  • Such techniques may be referred to as spatial multiplexing.
  • the multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas.
  • Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords) .
  • Different spatial layers may be associated with different antenna ports used for channel measurement and reporting.
  • MIMO techniques include single-user MIMO (SU-MIMO) , for which multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO) , for which multiple spatial layers are transmitted to multiple devices.
  • SU-MIMO single-user MIMO
  • Beamforming which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device.
  • Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference.
  • the adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device.
  • the adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .
  • a network entity 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations.
  • a network entity 105 e.g., a base station 140, an RU 170
  • Some signals e.g., synchronization signals, reference signals, beam selection signals, or other control signals
  • the network entity 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission.
  • Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network entity 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the network entity 105.
  • a transmitting device such as a network entity 105
  • a receiving device such as a UE 115
  • transmissions by a device may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network entity 105 to a UE 115) .
  • the UE 115 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands.
  • the network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS) , a channel state information reference signal (CSI-RS) ) , which may be precoded or unprecoded.
  • a reference signal e.g., a cell-specific reference signal (CRS) , a channel state information reference signal (CSI-RS)
  • the UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook) .
  • PMI precoding matrix indicator
  • codebook-based feedback e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook
  • these techniques are described with reference to signals transmitted along one or more directions by a network entity 105 (e.g., a base station 140, an RU 170)
  • a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device) .
  • a receiving device may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a transmitting device (e.g., a network entity 105) , such as synchronization signals, reference signals, beam selection signals, or other control signals.
  • a transmitting device e.g., a network entity 105
  • a receiving device may perform reception in accordance with multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions.
  • a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal) .
  • the single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR) , or otherwise acceptable signal quality based on listening according to multiple beam directions) .
  • receive configuration directions e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR) , or otherwise acceptable signal quality based on listening according to multiple beam directions
  • the wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack.
  • communications at the bearer or PDCP layer may be IP-based.
  • An RLC layer may perform packet segmentation and reassembly to communicate via logical channels.
  • a MAC layer may perform priority handling and multiplexing of logical channels into transport channels.
  • the MAC layer also may implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency.
  • an RRC layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network entity 105 or a core network 130 supporting radio bearers for user plane data.
  • a PHY layer may map transport channels to physical channels.
  • the UEs 115 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully.
  • Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., the communication link (s) 125, a D2D communication link 135) .
  • HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC) ) , forward error correction (FEC) , and retransmission (e.g., automatic repeat request (ARQ) ) .
  • FEC forward error correction
  • ARQ automatic repeat request
  • HARQ may improve throughput at the MAC layer in relatively poor radio conditions (e.g., low signal-to-noise conditions) .
  • a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.
  • the respective wireless devices of the wireless communications system 100 may support signaling and configurations that utilize full-duplex slots (e.g., SBFD slots) to communicate messages associated with RACH procedures.
  • full-duplex slots e.g., SBFD slots
  • aspects of the present disclosure are directed to RACH configurations for two-step RACH procedures to be performed between UEs 115 and network entities 105, where the RACH procedures configure UEs 115 with dedicated full-duplex ROs (e.g., SBFD ROs) and/or dedicated full-duplex POs (e.g., SBFD POs) to enable the UEs 115 to perform at least a portion of a MsgA of a two-step RACH procedure within full-duplex slots.
  • dedicated full-duplex ROs e.g., SBFD ROs
  • POs e.g., SBFD POs
  • a RACH configuration for a two-step RACH procedure may include (1) dedicated SBFD ROs within full-duplex slots, and/or (2) dedicated POs within full-duplex slots.
  • the RACH configuration may indicate mappings between the legacy ROs, the legacy POs, the SBFD ROs, and/or the SBFD POs.
  • the full-duplex aware UEs 115 may be able to select whether to use the legacy or SBFD resources based on a number of factors, including a relative timing of resources (e.g., select the earliest RO/PO to reduce latency) , the uplink transmit power relative to a maximum threshold of transmit power in SBFD slots, based on channel qualities of the resources, RRC pre-configuration, and/or based on the type of UE 115 (e.g., full-duplex UEs 115 select SBFD ROs/POs, and half-duplex UEs 115 select legacy ROs/POs) .
  • a relative timing of resources e.g., select the earliest RO/PO to reduce latency
  • the uplink transmit power relative to a maximum threshold of transmit power in SBFD slots based on channel qualities of the resources, RRC pre-configuration, and/or based on the type of UE 115 (e.g., full-duplex UEs 115 select SBFD ROs/POs, and half
  • Techniques described herein may facilitate faster and more efficient RACH procedures (e.g., two-step RACH procedures) .
  • RACH procedures e.g., two-step RACH procedures
  • techniques described herein may reduce a latency of two-step RACH procedures, and alleviate congestion/collisions within conventional RACH procedure resources within half-duplex slots.
  • the UE 115-a may receive RRC and/or SI signaling from the network entity 105-a.
  • the signaling at 205 may indicate an SSB configuration and/or a RACH configuration for performing the two-step RACH procedure with the network entity 105-a.
  • the RRC signaling at 205 may indicate a random access configuration for performing a two-step RACH procedure, where the random access configuration includes (1) a RACH configuration, and (2) a PUSCH configuration. That is, the signaling may indicate resources (e.g., PUCCH, PUSCH, PDCCH, and/or PDSCH resources) that are usable for exchanging messages associated with the two-step RACH procedure.
  • resources e.g., PUCCH, PUSCH, PDCCH, and/or PDSCH resources
  • the UE 115-a may transmit a payload of the first message (e.g., MsgA) of the two-step RACH procedure.
  • the payload may be transmitted via PUSCH resources configured via the signaling at 205.
  • the MsgA payload 255 may be transmitted via a PO configured via the PUSCH configuration indicated via the signaling at 205.
  • the MsgA payload 255 may be transmitted via a PO that maps to (e.g., corresponds to) the RO used to communicate the MsgA preamble 250.
  • the respective sets of PRACH and PUSCH resources in the diagram 201 may be separated (e.g., preceded and/or followed) by guard time (GT) and/or guard band (GB) intervals or resources.
  • GT guard time
  • GB guard band
  • the term “RO” may be used to refer to time and frequency resources allocated for MsgA preamble 250 transmission. Multiple two-step RACH UEs 115 may share the same RO in transmitting their MsgA preambles 250. Further, different UEs 115 may select different preamble sequences (e.g., code domain multiplexing) . Comparatively, for the purposes of the present disclosure, the term “PO” may be used to refer to time and frequency resources allocated for MsgA PUSCH transmission (e.g., MsgA payload 255) .
  • POs may be used to support asynchronous uplink transmission in two-step RACH procedures, where the GT and GB resources (shown in diagram 201) may be configured for each PO to mitigate inter-symbol interference (ISI) and/or inter-cell interference (ICI) .
  • ISI inter-symbol interference
  • ICI inter-cell interference
  • the diagram 202 shown in FIG. 2 illustrates the MsgA resource configuration and mapping for CBRA.
  • the diagram 202 illustrates a MsgA RO 260, such as the RO used to communicate the MsgA preamble 250 shown in diagram 201.
  • MsgA RO 260 such as the RO used to communicate the MsgA preamble 250 shown in diagram 201.
  • up to two MsgA PUSCH configurations can be pre-configured by the network (e.g., network entity 105-a) within an initial/active uplink BWP at the UE 115-a.
  • the MsgA RO 260 may include a first MsgA preamble group 265-a (e.g., MsgA Preamble Group A) , and a second MsgA preamble group 265-b (e.g., MsgA Preamble Group B) .
  • each preamble group 265 may be mapped to (e.g., correspond to) respective sets of MsgA POs 270.
  • the first preamble group 265-a may be mapped to a first set of MsgA POs 270-a via a first mapping configuration 275-a
  • the second preamble group 265-b may be mapped to a second set of MsgA POs 270-b via a second mapping configuration 275-b
  • the respective MsgA POs 270 may include examples of the PO used to communicate the MsgA payload 255 in diagram 201.
  • each MsgA PO 270 may include a set of resources for DMRS and a set of resources for MsgA PUSCH.
  • Each respective preamble group 265 may include separate sets of configuration parameters (e.g., group-specific configuration parameters) , including: slot-level offset between MsgA PRACH resources (e.g., ROs) and MsgA PUSCH resources (e.g., POs) , a number of FDMed MsgA POs, TDRA and FDRA values, MCS values, TBS values, preamble-to-PUSCH mapping ratios, DMRS resource configurations (e.g., sequence and port) , intra-slot frequency hopping patterns (configurable) , PRB-level guard bands (configurable) , symbol-level guard period after MsgA PUSCH (configurable) , or any combination thereof.
  • group-specific configuration parameters including: slot-level offset between MsgA PRACH resources (e.g., ROs) and MsgA PUSCH resources (e.g., POs) , a number of FDMed MsgA POs, TDRA and
  • multiple UEs 115 may share the same ROs, preamble groups 265, DMRS resources, and POs for performing RACH procedures (e.g., CBRA) with the network (for both TA-free and grant-free RACH procedures) .
  • RACH procedures e.g., CBRA
  • the preambles communicated within the MsgA ROs 260 may be mapped to respective PRUs (e.g., in accordance with respective mapping configurations 275) .
  • each consecutive number of N Preamble preamble indexes from a valid PRACH occasion in a valid PRACH slot may be mapped to PRUs in accordance with the following: (1) first, in creasing order of preamble indexes within a single PRACH occasion, (2) second, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions, and (3) third, in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH slot.
  • each consecutive number of N Preamble preamble indexes from a valid PRACH occasion (e.g., PO) in a valid PRACH slot (e.g., PO slot) may be mapped to a valid PO and the associated DMRS resource (shown in the sets of MsgA POs 270-a, 270-b) in accordance with the following: (1) first, in increasing order of frequency resource indexes f id for frequency multiplexed POs, (2) second, in increasing order of DMRS resource indexes within a PO, where a DMRS resource index DMRS id is determined in an ascending order of a DMRS port index and in an ascending order of a DMRS sequence index, (3) third, in increasing order of time resource indexes t id for time multiplexed POs within a PUSCH slot, and (4) fourth, in increasing order of indexes N S PUSCH slots.
  • N Preamble ceil (T Preamble /T PUSCH )
  • T Preamble is a total number of valid PRACH occasions per association pattern period multiplied by the number of preambles per valid PRACH occasion provided by rach-ConfigCommonTwoStepRA
  • T PUSCH is a total number of valid POs per PUSCH configuration per association pattern period multiplied by the number of DMRS resource indexes per valid PO provided by msgA-DMRS-Config.
  • Preamble indexes from valid PRACH occasion in a PRACH slot may be mapped to a valid PO (e.g., MsgA PO 270-a, 270-b) and the associated DMRS resource.
  • a PO 270 may be said to be valid if it does not overlap in time and frequency with any valid PRACH occasion associated with either a Type-1 or Type-2 RACH procedure.
  • PBCH physical broadcast channel
  • the network entity 105-a may decode the MsgA payload 255.
  • the network entity 105-a may receive the MsgA preamble 250, and may monitor the PO corresponding to the RO in which the MsgA preamble 250 was received in order to decode the MsgA payload 255.
  • the network entity 105-a may transmit a MsgB PDCCH portion to the UE 115-a.
  • the MsgB PDCCH portion may include C-RNTI, MsgB-RNTI, or both.
  • the network entity 105-a may transmit a MsgB PDSCH portion to the UE 115-a.
  • MsgB 245 of the two-step RACH procedure may include the information that is included within Msg2 and Msg4 of a four-step RACH procedure.
  • the MsgB PDSCH may indicate a success random access response (RAR) .
  • RAR success random access response
  • the MsgB PDSCH may indicate a successful completion of the two-step RACH procedure.
  • the UE 115-a may identify a valid TA and PUCCH resource/timing based on the successful completion of the two-step RACH procedure. That is, the UE 115-a may identify a valid TA and/or PUCCH resources/timing based on the MsgB PDCCH and/or MsgB PDSCH received at 225 and/or 230.
  • the UE 115-a may transmit a HARQ message to the network entity 105-a, where the HARQ message includes an ACK/NACK responsive to the MsgB received at 225 and 230. Subsequently, the UE 115-a and the network entity 105-a may communicate with one another based on the successful completion of the two-step RACH procedure.
  • conventional RACH procedures (including two-step RACH procedures) only utilize ROs and POs configured within legacy half-duplex uplink slots.
  • conventional RACH procedures have no mechanisms for utilizing full-duplex slots for transmitting MsgA 245, such as SBFD uplink bands positioned within downlink slots.
  • MsgA 245, such as SBFD uplink bands positioned within downlink slots.
  • the inability to utilize SBFD slots to perform signaling used for RACH procedures may increase the latency of RACH procedures.
  • requiring all devices to use the same resources within half-duplex slots to perform RACH procedures increases collisions and noise within such resources, thereby decreasing the efficiency and success probability of such RACH procedures.
  • aspects of the present disclosure are directed to signaling and configurations that utilize full-duplex slots (e.g., SBFD slots) to communicate messages associated with RACH procedures.
  • aspects of the present disclosure are directed to RACH configurations that configure UEs 115 with dedicated full-duplex ROs (e.g., SBFD ROs) and/or dedicated full-duplex POs (e.g., SBFD POs) to enable the UEs 115 to perform at least a portion of a MsgA of a two-step RACH procedure within full-duplex slots.
  • FIG. 3 shows an example of a wireless communications system 300 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • aspects of the wireless communications system 300 may implement, or be implemented by, aspects of the wireless communications system 100, the two-step RACH procedure configuration 200, or both.
  • the wireless communications system 300 illustrates signaling and configurations for a two-step RACH procedure that utilizes dedicated SBFD resources, as described previously herein.
  • the wireless communications system 300 may include a UE 115-b and a network entity 105-b, which may be examples of wireless devices as described herein.
  • the UE 115-b and the network entity 105-b shown in FIG. 3 may include examples of the UE 115-a and the network entity 105-a, respectively, as shown in FIG. 2.
  • the UE 115-b and the network entity 105-b may communicate with one another using a communication link 305, which may be an example of an NR or LTE link, a sidelink (e.g., PC5 link) , and the like, between the respective devices.
  • a communication link 305 which may be an example of an NR or LTE link, a sidelink (e.g., PC5 link) , and the like, between the respective devices.
  • the communication link 305 may include an example of an access link (e.g., Uu link) which may include a bi-directional link that enables both uplink and downlink communication.
  • the UE 115-b may transmit uplink signals, such as uplink control signals or uplink data signals, to one or more components of the network entity 105-b using the communication link 305, and one or more components of the network entity 105-b may transmit downlink signals, such as downlink control signals or downlink data signals, to the UE 115-b using the communication link 305.
  • uplink signals such as uplink control signals or uplink data signals
  • downlink signals such as downlink control signals or downlink data signals
  • different networks may utilize different types of access procedures to enable wireless devices (e.g., UEs) to connect to and access the networks, such as four-step RACH procedures and two-step RACH procedures (as shown and described in FIG. 2) .
  • the UE 115-b may receive control signaling (e.g., RRC signaling, SI signaling) from the network entity 105-b, where the control signaling indicates a random access configuration 310 for performing a two-step RACH procedure with the network entity 105-b.
  • control signaling e.g., RRC signaling, SI signaling
  • the random access configuration 310 may include or indicate/allocate resources that are usable for performing the various signaling of the two-step RACH procedure.
  • the random access configuration 310 may include a RACH configuration (s) that includes resources for ROs usable for transmitting a preamble for MsgA of a two-step RACH procedure, and a PUSCH configuration (s) that includes resources for POs usable for transmitting a payload for MsgA of the two-step RACH procedure.
  • a RACH configuration (s) that includes resources for ROs usable for transmitting a preamble for MsgA of a two-step RACH procedure
  • PUSCH configuration s
  • the random access configuration 310 may allocate resources within a set of slots 325 or TTIs that are usable for exchanging signaling associated with a two-step RACH procedure.
  • the resources of the random access configuration 310 may be spread across any number of slots 325 or TTIs, such as a first slot 325-a, a second slot 325-b, a third slot 325-c, a fourth slot 325-d, and a fifth slot 325-e.
  • the UE 115-b may utilize the random access configuration 310 to transmit a first message (e.g., MsgA 315) of the two-step RACH procedure. Subsequently, the UE 115-b may receive a second message (e.g., MsgB 320) of the two-step RACH procedure to complete the two-step RACH procedure and begin communicating with the network entity 105-b.
  • a first message e.g., MsgA 315
  • MsgB 320 e.g., MsgB 320
  • RACH procedures only utilize ROs and POs configured within legacy half-duplex uplink slots.
  • conventional RACH procedures have no mechanisms for utilizing full-duplex slots for transmitting MsgA 315.
  • the UE 115- may only be able to utilize allocated uplink resources 335 within the fifth slot 325-e (e.g., half-duplex uplink slot) to transmit MsgA 315.
  • requiring all devices e.g., UE 115-b, other UEs 115
  • to use the same resources increases the probability of collisions and noise within such resources, thereby decreasing the efficiency and success probability of such RACH procedures.
  • aspects of the present disclosure are directed to signaling and configurations that utilize resources 340 within the full-duplex slots 325-b, 325-c, 325-d (e.g., SBFD slots) to communicate messages (e.g., MsgA 315) associated with RACH procedures.
  • aspects of the present disclosure are directed to random access configurations 310 that configure UEs 115 with dedicated SBFD resources 340 within SBFD slots 325 that may be used for RACH procedures.
  • aspects of the present disclosure are directed to random access configurations 310 that include/allocate full-duplex ROs (e.g., SBFD ROs) and/or dedicated full-duplex POs (e.g., SBFD POs) to enable UEs 115 to perform at least a portion of a MsgA 315 of a two-step RACH procedure within full-duplex slots 325.
  • full-duplex ROs e.g., SBFD ROs
  • dedicated full-duplex POs e.g., SBFD POs
  • Such configurations and signaling described herein may enable the UE 115-b to perform RACH procedures for random access (and/or other use cases) within SBFD slots/symbols while in RRC connected, RRC idle, and/or RRC inactive states.
  • the random access configuration 310 may include a RACH configuration that includes/allocates a set of full-duplex (e.g., SBFD) ROs within the uplink sub-band 330 of the second slot 325-b. Additionally, or alternatively, the random access configuration 310 may include a PUSCH configuration that includes/allocates a set of full-duplex (e.g., SBFD) POs (e.g., PUSCH resources) within the uplink sub-band 330 of the third slot 325-c.
  • a RACH configuration that includes/allocates a set of full-duplex (e.g., SBFD) ROs within the uplink sub-band 330 of the second slot 325-b.
  • the random access configuration 310 may include a PUSCH configuration that includes/allocates a set of full-duplex (e.g., SBFD) POs (e.g., PUSCH resources) within the uplink sub-band 330 of the third slot 325-c.
  • the random access configuration 310 may enable the UE 115-a to transmit a preamble of MsgA 315 within an RO of the second slot 325-b, and to transmit a payload of MsgA 315 within a PO of the PUSCH resources within the third slot 325-c.
  • the UE 115-b may be able to transmit (at least a portion) of MsgA 315 within the SBFD slots 325-b, 325-c, 325-d, instead of having to wait to transmit MsgA 315 within the half-duplex uplink slot 325-e.
  • aspects of the present disclosure may enable RACH procedures to be performed (at least partially) within SBFD symbols (e.g., uplink sub-band 330) .
  • Enabling RACH messages e.g., MsgA 315, MsgB 320
  • full-duplex slots 325 e.g., SBFD slots 325
  • UEs 115 may be able to utilize the uplink sub-band 330 in consecutive SBFD slots 325 to enable RACH and MsgA 315 PUSCH repetition and frequency hopping, which may enhance uplink coverage for initial access.
  • techniques described herein may improve RACH capacity.
  • configuring additional ROs within the uplink sub-band 330 may improve RACH capacity (e.g., improve a quantity of devices that are able to perform RACH procedures) .
  • configuring additional ROs within the uplink sub-band 330 may reduce the probability of contention-based collisions within the resources 335 of the half-duplex uplink slot 325-e, thereby enabling more UEs 115 to perform RACH procedures and access the network.
  • techniques described herein may reduce latency associated with RACH procedures and initial access and handover, particularly when Layer 1 (L1) and/or Layer 2 (L2) mobility is adopted.
  • allocating resources 340 within the SBFD slots 325 may enable the UE 115-b to transmit MsgA 315 earlier (e.g., prior to the half-duplex uplink slot 325-e) , thereby reducing a latency of the RACH procedure.
  • FIG. 4 shows an example of a resource configuration 400 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • aspects of the resource configuration 400 may implement, or be implemented by, aspects of the wireless communications system 100, the two-step RACH procedure configuration 200, the wireless communications systems 300, or any combination thereof.
  • the resource configuration 400 illustrates various implementations 405 for a two-step RACH procedure that utilize dedicated SBFD resources, as described previously herein. That is, the resource configuration 400 illustrates different implementations 405 of the random access configuration 310 shown and described in FIG. 3 that utilize SBFD-dedicated MsgA resource configurations.
  • the first implementation 405-a of the random access configuration for SBFD-dedicated MsgA resources includes SBFD-dedicated PUSCH resources for POs (e.g., SBFD-dedicated PO resources within SBFD slots for transmitting payloads of MsgA) .
  • a random access configuration in accordance with the first implementation 405-a may include an SBFD-dedicated PUSCH configuration including POs within SBFD slots in addition to the common (e.g., legacy, TDD/half-duplex) RACH configuration including ROs within half-duplex uplink slots, the PUSCH configuration including POs within legacy/TDD half-duplex uplink slots.
  • the second implementation 405-b includes additional SBFD-dedicated RACH resources for ROs (e.g., SBFD-dedicated RO resources within SBFD slots for transmitting preambles of MsgA) .
  • a random access configuration in accordance with the second implementation 405-b may include an SBFD-dedicated RACH configuration including ROs within SBFD slots (in addition to a common RACH configuration including ROs within legacy/TDD half-duplex slots) , as well as a common (e.g., legacy, TDD/half-duplex) PUSCH configuration including POs within half-duplex uplink slots.
  • the third implementation 405-c includes both (1) SBFD-dedicated RACH resources for ROs, and (2) SBFD-dedicated PUSCH resources for POs (e.g., SBFD-dedicated RO/PO resources within SBFD slots for transmitting preambles and payloads of MsgA) .
  • a random access configuration in accordance with the third implementation 405-c may include a common RACH configuration that includes common ROs within half-duplex uplink slots, an SBFD RACH configuration that includes SBFD-dedicated ROs within SBFD slots, a common PUSCH configuration that includes common POs within half-duplex uplink slots, and an SBFD PUSCH configuration that includes SBFD-dedicated POs within SBFD slots.
  • common RO may be used to refer to resources within half-duplex TDD slots that may be used by both half-duplex (e.g., “legacy” ) and full-duplex (e.g., SBFD-aware) UEs 115.
  • “common ROs/POs” may also be referred to as “legacy/TDD” ROs/POs.
  • full-duplex RO, ” “full-duplex PO, ” “SBFD RO, ” “SBFD PO, ” and like terms may be used to refer to resources within full-duplex slots (e.g., SBFD slots) that may be used by full-duplex-aware UEs 115.
  • full-duplex ROs/POs are located within full-duplex slots (e.g., SBFD slots) , such “full-duplex ROs/POs” may not be usable by half-duplex (e.g., “legacy” ) UEs 115.
  • the first implementation 405-a of a random access configuration may allocate resources within a set of slots 410 or TTIs that are usable for exchanging signaling associated with a two-step RACH procedure, such as a first slot 410-a, a second slot 410-b, a third slot 410-c, a fourth slot 410-d, and a fifth slot 410-e.
  • the first slot 410-a and the fifth slot 410-e may include half-duplex uplink slots (e.g., TDD UL slots) that include only uplink resources.
  • the second slot 410-b, the third slot 410-c, and the fourth slot 410-d may include full-duplex slots (e.g., FDD UL/DL slots) that include both uplink and downlink resources (e.g., SBFD slots) .
  • the slots 410-b, 410-c, and 410-d may include downlink resources that are split by an uplink sub-band that includes uplink resources (e.g., uplink sub-band 330 illustrated in FIG. 3) .
  • a random access configuration in accordance with the first implementation 405-a may include a RACH configuration that includes resources for common ROs 415 within the half-duplex uplink slot 410-a.
  • the random access configuration may further include one or more PUSCH configurations (e.g., common PUSCH configuration and SBFD PUSCH configuration) that include (1) common POs 420 within the half-duplex uplink slot 410-e, and (2) full-duplex POs (e.g., SBFD POs 425-a) within the full duplex slot 410-b and/or the full-duplex slot 410-c.
  • PUSCH configurations e.g., common PUSCH configuration and SBFD PUSCH configuration
  • full-duplex POs e.g., SBFD POs 425-a
  • Preambles of the set of common ROs 415 may be mapped to both the set of common POs 420 and the set of SBFD POs 425-a, as shown in the first implementation 405-a.
  • the PUSCH slots 410-b and 410-c including the earliest SBFD POs 425-a may be associated with a first time domain offset 430-a relative to the PRACH slot 410-a including common ROs 415
  • the PUSCH slot 410-e including the set of common POs 420 may be associated with a second time domain offset 430-b relative to the PRACH slot 410-a including the common ROs 415.
  • a random access configuration in accordance with the second implementation 405-b may include a PUSCH configuration that includes resources for common POs 420 within the half-duplex uplink slot 410-e.
  • the random access configuration may further include one or more RACH configurations (e.g., common RACH configuration and SBFD RACH configuration) that includes (1) common ROs 415 within the half-duplex uplink slot 410-a, and (2) full-duplex ROs (e.g., SBFD ROs 435-a) within the full-duplex slot 410-c.
  • RACH configurations e.g., common RACH configuration and SBFD RACH configuration
  • Preambles of the set of common POs 420 may be mapped to both the set of common ROs 415 and the set of SBFD ROs 435-a, as shown in the second implementation 405-b.
  • the PUSCH slots 410 and PRACH slots 410 associated with the set of common ROs 415 and the set of SBFD ROs 435-a may be associated with different time domain offsets 430-b, 430-c, as described previously herein.
  • a random access configuration in accordance with the third implementation 405-c may include one or more RACH configurations (e.g., common RACH configuration and SBFD RACH configuration) that include (1) common ROs 415 within the half-duplex uplink slot 410-a, and (2) full-duplex ROs (e.g., SBFD ROs 435-a) within the full-duplex slot 410-b.
  • RACH configurations e.g., common RACH configuration and SBFD RACH configuration
  • the random access configuration may further include one or more PUSCH configurations (e.g., common PUSCH configuration and SBFD PUSCH configuration) that include (1) common POs 420 within the half-duplex uplink slot 410-e, and (2) full-duplex POs (e.g., SBFD POs 425-b) within the full-duplex slot 410-c.
  • PUSCH configurations e.g., common PUSCH configuration and SBFD PUSCH configuration
  • preambles of the set of common ROs 415 may be mapped to the set of common POs 420, where the preambles of the set of SBFD ROs 435-b may be mapped to the set of SBFD POs 425-b.
  • the random access configuration may define separate time domain offsets 430-b, 430-d between the PUSCH/PRACH slots 410 of the common ROs 415 and the common POs 420, and between the PUSCH/PRACH slots 410 of the SBFD ROs 435-b and the SBFD POs 425-b, as described previously herein.
  • the PUSCH slots 410 and PRACH slots 410 associated with the respective ROs and POs may be associated with different time domain offsets 430-b, 430-d, as described previously herein.
  • each of the respective implementations 405 shown in FIG. 4 and Table 1 above are described in further detail herein.
  • the first implementation 405-a is further shown and described in FIG. 5
  • the second implementation 405-b is further shown and described in FIG. 6,
  • the third implementation is further shown and described in FIG. 7.
  • the resource configuration 500 shown and described in FIG. 5 illustrates example resource configurations associated with the first implementation 405-a shown and described in FIG. 4.
  • the first implementation 405-a of the random access configuration for SBFD-dedicated MsgA resources includes SBFD-dedicated PUSCH resources for POs (e.g., SBFD-dedicated PO resources within SBFD slots for transmitting payloads of MsgA) .
  • a random access configuration in accordance with the first implementation 405-a may include a common (e.g., legacy, TDD/half-duplex) RACH configuration including ROs within half-duplex uplink slots, as well as an SBFD-dedicated PUSCH configuration including POs within SBFD slots (in addition to a common PUSCH configuration including POs within legacy/TDD half-duplex uplink slots) .
  • a common RACH configuration including ROs within half-duplex uplink slots
  • SBFD-dedicated PUSCH configuration including POs within SBFD slots
  • the first implementation 405-a of a random access configuration may allocate resources within a set of slots 510 or TTIs that are usable for exchanging signaling associated with a two-step RACH procedure, such as a first slot 510-a, a second slot 510-b, a third slot 510-c, a fourth slot 510-d, and a fifth slot 510-e.
  • the first slot 510-a and the fifth slot 510-e may include half-duplex uplink slots (e.g., TDD UL slots) that include only uplink resources.
  • the second slot 510-b, the third slot 510-c, and the fourth slot 510-d may include full-duplex slots (e.g., FDD UL/DL slots) that include both uplink and downlink resources (e.g., SBFD slots) .
  • the slots 510-b, 510-c, and 510-d may include downlink resources that are split by an uplink sub-band that includes uplink resources (e.g., uplink sub-band 330 illustrated in FIG. 3) .
  • a random access configuration in accordance with the first implementation 405-a may include a RACH configuration that includes resources for common ROs 515-a within the half-duplex uplink slot 510-a.
  • the random access configuration may further include a common PUSCH configuration that includes common POs 520-a within the half-duplex uplink slot 510-e, and an SBFD PUSCH configuration that includes full-duplex POs (e.g., SBFD POs 525-a) within the full duplex slot 510-c and/or the full-duplex slot 510-d.
  • Preambles of the set of common ROs 515-a may be mapped to both the set of common POs 520-a and the set of SBFD POs 525-a, as shown in diagram 505-a.
  • the PUSCH slot 510-c including the earliest SBFD POs 525-a may be associated with a first time domain offset 530-a relative to the PRACH slot 510-a including the common ROs 515-a
  • the PUSCH slot 510-e including the set of common POs 520-a may be associated with a second time domain offset 530-b relative to the PRACH slot 510-a including the common ROs 515-a.
  • an SBFD-aware UE 115 may be configured with SBFD-dedicated MsgA-PUSCH configuration (s) , as shown in diagram 505-a. Further, SBFD PUSCH configurations may be associated with sub-configurations corresponding to different preamble groups. In particular, a UE 115 may be configured with up to two MsgA-PUSCH configurations associated with the respective preamble groups (e.g., first PUSCH sub-configuration associated with MsgA-preamble Group A, and a second PUSCH sub-configuration associated with MsgA-preamble Group B) .
  • the SBFD-dedicated MsgA PUSCH configuration (s) (e.g., SBFD POs 525-a) and legacy TDD MsgA-PUSCH configuration (s) (e.g., common POs 520-a) may be associated with (e.g., mapped to) the same/common pool of preambles of MsgA RACH (e.g., common ROs 515-a) .
  • the mapping between one or multiple PRACH preambles and a valid PO 520-a, 525-a associated with a DMRS resource is each per PUSCH configuration.
  • the number of preamble (s) mapped to a valid PO (N Preamble ) may be determined for each PUSCH configuration (e.g., TDD/half-duplex PUSCH configuration, SBFD PUSCH configuration) within the same RACH association pattern period, as illustrated in Equation 1 and Equation 2 below:
  • N preamble (TDD) ceil (T preamble /T PUSCH ) (1)
  • N preamble (SBFD) ceil (T preamble /T PUSCH-SBFD ) (2)
  • T PUSCH is a total number of valid SBFD POs 525-a per association pattern period multiplied by the number of DMRS resource indexes per valid PO.
  • PUSCH configuration (s) for the SBFD POs 525-a and the common POs 520-a of the first implementation 405-a may be signaled or otherwise configured at a UE 115 in a number of ways.
  • the configuration of the SBFD-dedicated MsgA PUSCH configuration e.g., PUSCH configuration for the SBFD POs 525-a
  • the configuration of the SBFD-dedicated MsgA PUSCH configuration e.g., PUSCH configuration for the SBFD POs 525-a
  • the first implementation 405-a may be signaled/configured via an additional IE for MsgA-PUSCH within the MsgA-common configuration, as shown below:
  • the configuration of the SBFD-dedicated MsgA PUSCH configuration (e.g., PUSCH configuration for the SBFD POs 525-a) for the first implementation 405-a may be signaled/configured via an additional IE for Msg-PUSCH-Resource Group A/B, as shown below:
  • each of the respective common ROs 515-a, common POs 520-a, and the SBFD POs 525-a may be mapped to one or more SSBs and/or preambles.
  • a UE 115 may monitor resources associated with a set of SSBs (e.g., SSB #0, SSB #1, and SSB #2) , and may determine channel quality metrics associated with the respective SSBs.
  • the UE 115 may identify the SSB with the highest quality, and may transmit a preamble of MsgA via a common RO 515 of the set of common ROs 515-a that corresponds to the selected SSB.
  • the UE 115-a may use a common PO 520 of the set of common POs 520-a that is associated with the preamble transmitted in the common RO 515, and/or an SBFD PO 525 of the set of SBFD POs 525-a that is associated with the preamble transmitted in the common RO 515. That is, the UE 115 may use an RO and PO that pair that corresponds to the same SSB/preamble in order to transmit MsgA.
  • the selection to use a PO from either the set of common POs 520-a or the set of SBFD POs 525-a may be based on a number of criteria, including a relative timing of the common POs 520-a and SBFD POs 525-a in the time domain, based on measured/predicted channel quality metrics of the slots 510 including the respective POs, based on RRC configuration (e.g., pre-configuration by the network) , based on a type of UE 115 (e.g., full-duplex UE 115, half-duplex UE 115) , based on PUSCH transmission (Tx) power relative to a threshold PUSCH Tx power, or any combination thereof.
  • RRC configuration e.g., pre-configuration by the network
  • Tx PUSCH transmission
  • the SBFD-aware UE 115 may select to transmit the MsgA payload within SBFD PO3 and/or SBFD PO4 based on such SBFD POs occurring before the common POs 520-a in the time domain.
  • the UE 115 may select whether to use common POs 520-a or SBFD POs 525-a based on an RSRP threshold and/or measured RSRP of the selected SSB-index.
  • the selection between common POs 520-a or SBFD POs 525-a may be based on UE type, where SBFD-aware UEs 115 select SBFD POs 525-a, and half-duplex UEs 115 select common POs 520-a.
  • the validity (or lack thereof) of SBFD POs 525 may be based on the type of slot/TTI that the respective SBFD POs 525 are positioned within.
  • SBFD POs 525 may be determined to be valid only when they are positioned within an uplink sub-band of an SBFD slot 510 (such as the set of SBFD POs 525-a within slots 510-c and 510-d) .
  • a PUSCH configuration may include a set of SBFD POs 525-b within the SBFD slot 510-d and the half-duplex uplink slot 510-e.
  • SBFD POs 1–3 may be determined to be valid based on POs 1–3 being positioned within uplink symbols of the SBFD slot 510-d, where SBFD POs 4–6 may be determined to be invalid based on POs 4–6 being positioned within the half-duplex uplink slot 510-e.
  • SBFD POs 525 may be determined to be valid regardless of whether they are positioned within SBFD-symbols/slots or half-duplex uplink symbols/slots.
  • SBFD POs 1–6 may be valid in accordance with the second option (regardless of the type of slot 510-d, 510-e) .
  • preamble mapping to legacy TDD POs e.g., common POs 520-a
  • the preamble mapping may be first performed for overlapping SBFD POs 525 as a subset of preambles associated with the same SSB (objective to have consistent mapping with legacy POs) , were remaining preamble mapping may for non-overlapping SBFD POs 525 may be performed next.
  • the common POs 520-a may be mapped to SSBs/preambles first such that common PO1 maps to SSB #0 and preambles (0, 1, 2, 3) , common PO2 maps to SSB #1 and preambles (4, 5, 6, 7) , and common PO3 maps to SSB #2 and preambles (8, 9, 10, 11) .
  • SBFD POs 525-b that overlap in time with the common POs 520-a may be mapped next, such that SBFD PO4 maps to SSB #0 and preambles (0, 1) , SBFD PO5 maps to SSB #1 and preambles (4, 5) , and SBFD PO6 maps to SSB #2 and preambles (8, 9) .
  • SBFD POs 525-b within the SBFD slot 510-d may be performed last, such that SBFD PO1 maps to SSB #0 and preambles (2, 3) , SBFD PO2 maps to SSB #1 and preambles (6, 7) , and SBFD PO3 maps to SSB #2 and preambles (10, 11) .
  • mapping scheme e.g., by mapping common POs 520-a first, then temporally-overlapping SBFD POs 525-b, then non-overlapping SBFD POs 525-b
  • MsgA payloads received in temporally-overlapping POs e.g., within common PO1 and SBFD PO4
  • SSB subset of common PO1 and SBFD PO4
  • the RB start of the dedicated SBFD POs 525 occurring in non-SBFD symbols may be configured with a different RB start/offset as compared to SBFD POs 525 within SBFD slots. For example, referring to the third diagram 505-c in FIG.
  • a PUSCH configuration may include a set of SBFD POs 525-c, including a first subset of SBFD POs 525 (e.g., POs 1–6) within an SBFD slot 510-f, and a second subset of SBFD POs 525 (e.g., POs 7–18) within a half-duplex uplink slot 510-g.
  • SBFD POs 525-c including a first subset of SBFD POs 525 (e.g., POs 1–6) within an SBFD slot 510-f, and a second subset of SBFD POs 525 (e.g., POs 7–18) within a half-duplex uplink slot 510-g.
  • the first subset of SBFD POs 525 may be associated with a first frequency start 530-a (e.g., SBFD RB start/offset in the frequency domain)
  • the second subset of SBFD POs 525 e.g., POs 7–18
  • a second frequency start 530-b e.g., TDD/common RB start/offset in the frequency domain
  • the MsgA-PUSCH may be configured with two parameters for half-duplex and SBFD slots (e.g., to indicate the different quantities) .
  • the SBFD slot 510-f may include two FDMed POs (e.g., two rows of SBFD POs)
  • the half-duplex uplink slot 510-g may include four FDMed POs (e.g., four rows of SBFD POs) .
  • the respective PUSCH configurations may indicate the RB frequency start/offset values and/or the quantities of FDMed POs within the TDD/SBFD slots 510.
  • FIG. 6 shows an example of a resource configuration 600 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • aspects of the resource configuration 600 may implement, or be implemented by, aspects of the wireless communications system 100, the two-step RACH procedure configuration 200, the wireless communications systems 300, the resource configurations 400-500, or any combination thereof.
  • resource configuration 600 shown and described in FIG. 6 illustrates example resource configurations associated with the second implementation 405-b shown and described in FIG. 4.
  • the second implementation 405-b includes SBFD-dedicated RACH resources for ROs (e.g., SBFD-dedicated RO resources within SBFD slots for transmitting preambles of MsgA) .
  • a random access configuration in accordance with the second implementation 405-b may include an SBFD-dedicated RACH configuration including ROs within SBFD slots (in addition to a common RACH configuration including ROs within legacy/TDD half-duplex slots) , as well as a common (e.g., legacy, TDD/half-duplex) PUSCH configuration including POs within half-duplex uplink slots.
  • the second implementation 405-b of a random access configuration may allocate resources within a set of slots 610 or TTIs that are usable for exchanging signaling associated with a two-step RACH procedure, such as a first slot 610-a, a second slot 610-b, a third slot 610-c, a fourth slot 610-d, and a fifth slot 610-e.
  • the first slot 610-a and the fifth slot 610-e may include half-duplex uplink slots (e.g., TDD UL slots) that include only uplink resources.
  • the second slot 610-b, the third slot 610-c, and the fourth slot 610-d may include full-duplex slots (e.g., FDD UL/DL slots) that include both uplink and downlink resources (e.g., SBFD slots) .
  • the slots 610-b, 610-c, and 610-d may include downlink resources that are split by an uplink sub-band that includes uplink resources (e.g., uplink sub-band 330 illustrated in FIG. 3) .
  • a random access configuration in accordance with the second implementation 405-b may include a common RACH configuration that includes resources for common ROs 615-a within the half-duplex uplink slot 610-a, and an SBFD RACH configuration including SBFD ROs 635-a within the SBFD slot 610-b.
  • the random access configuration may further include a PUSCH configuration that includes common POs 620-a within the half-duplex uplink slot 610-e. Preambles of the set of common POs 620-a may be mapped to both the set of common ROs 615-a and the set of SBFD ROs 635-a, as shown in diagram 605-a.
  • the PUSCH slot 610-e including the set of common POs 620-a may be associated with a first time domain offset 630-a relative to the PRACH slot including the SBFD ROs 635-a, and a second time domain offset 630-b relative to the PRACH slot 610-a including the common ROs 615-a, as described previously herein.
  • an SBFD-aware UE 115 may be configured with SBFD-dedicated MsgA-RACH configuration (s) for two-step RACH random access procedures.
  • the use of different preamble sequences (e.g., long sequence) in SBFD symbols/slots 610 may improve coverage and reduce preamble collision in legacy/TDD ROs (e.g., common ROs 615) .
  • the preambles of the SBFD-dedicated RACH configuration (s) (e.g., preambles of the SBFD ROs 635-a) and the preambles of legacy/TDD MsgA-RACH (e.g., preambles of the common ROs 615-a) may be mapped to the same resources of MsgA-POs (e.g., common POs 620-a) .
  • the mapping of the TDD/SBFD preambles to a PUSCH resource of a common PO 620 may be performed to ensure that selected preambles of both ROs (e.g., preambles of the common ROs 615-a and the SBFD ROs 635-a) are associated with the same SSB index.
  • the common RO1 615 and the SBFD RO1 635 may be mapped to the same common PO1 620, and may therefore be associated with the same SSB index (e.g., SSB #0) .
  • the mapping between one or multiple PRACH preambles of RO and a PO associated with a DMRS resource may be done in sequence (e.g., TDD/common ROs 615 mapped first, followed by mapping for SBFD ROs 635) .
  • the number of preamble (s) mapped to a valid PO N preamble may be determined separately for common ROs 615-a and SBFD ROs 635-a within each RACH association pattern period.
  • RACH configuration (s) for the common ROs 615-a and the SBFD ROs 635-a of the second implementation 405-b may be signaled or otherwise configured at a UE 115 in a number of ways.
  • the configuration of the SBFD-dedicated MsgA RACH configuration e.g., RACH configuration for the SBFD ROs 635-a
  • the configuration of the SBFD-dedicated MsgA RACH configuration e.g., RACH configuration for the SBFD ROs 635-a
  • the second implementation 405-b may be signaled/configured via an additional IE for MsgA-RACH within the MsgA-common configuration, as shown below:
  • the configuration of the SBFD-dedicated MsgA RACH configuration (e.g., RACH configuration for the SBFD ROs 635-a) for the second implementation 405-b may be signaled/configured via the same IE for RACH-ConfigCommonTwoStepRA and some duplicated parameters (e.g., rach-ConfigGenericTwoStepRA or power control parameters) for SBFD-dedicated configuration, as shown below:
  • each of the respective common ROs 615-a, SBFD ROs 635-a, and common POs 620-a may be mapped to one or more SSBs and/or preambles.
  • a UE 115 may monitor resources associated with a set of SSBs (e.g., SSB #0, SSB #1, and SSB #2) , and may determine channel quality metrics associated with the respective SSBs.
  • the UE 115 may identify the SSB with the highest quality, and may transmit a preamble of MsgA via (1) a common RO of the set of common ROs 615-a that corresponds to the selected SSB, or (2) an SBFD RO of the set of SBFD Ros 635-a that corresponds to the selected SSB. Subsequently, to transmit the payload of MsgA, the UE 115 may use a common PO of the set of common POs 620-a that corresponds to the common RO used to transmit the preamble. That is, the UE 115 may use an RO and PO that pair that corresponds to the same SSB in order to transmit MsgA.
  • the selection to use an RO from either the set of common ROs 615-a or the set of SBFD ROs 635-a may be based on a number of criteria, including a relative timing of the common ROs 615-a and SBFD ROs 635-a in the time domain, based on measured/predicted channel quality metrics of the slots 610 including the respective ROs, based on RRC configuration (e.g., pre-configuration by the network) , based on a type of UE 115 (e.g., full-duplex UE 115, half-duplex UE 115) , PUSCH Tx power relative to a threshold PUSCH Tx power, or any combination thereof.
  • RRC configuration e.g., pre-configuration by the network
  • the SBFD-aware UE 115 may select to transmit the MsgA preamble within common RO3 (instead of SBFD RO3) based on the common RO3 occurring before the SBFD RO3 in the time domain.
  • the UE 115 may select whether to use common ROs 615-a or SBFD ROs 635-a based on an RSRP threshold and/or measured RSRP of the selected SSB-index.
  • the selection between common ROs 615-a or SBFD ROs 635-a may be based on UE type, where SBFD-aware UEs 115 select SBFD ROs 635-a, and half-duplex UEs 115 select common ROs 615-a.
  • the validity (or lack thereof) of SBFD ROs 635 may be based on the type of slot/TTI that the respective SBFD ROs 635 are positioned within.
  • SBFD ROs 635 may be determined to be valid only when they are positioned within an uplink sub-band of an SBFD slot 610 (such as the set of SBFD ROs 635-a within slot 610-b) .
  • a RACH configuration may include a set of SBFD ROs 635-b within the SBFD slot 610-f and the half-duplex uplink slot 610-g.
  • SBFD ROs 1–3 may be determined to be valid based on ROs 1–3 being positioned within uplink symbols of the SBFD slot 610-f, where SBFD ROs 4–6 may be determined to be invalid based on ROs 4–6 being positioned within the half-duplex uplink slot 610-g.
  • SBFD ROs 635 may be determined to be valid regardless of whether they are positioned within SBFD-symbols/slots or half-duplex uplink symbols/slots. For example, referring to the second diagram 605-b in FIG. 6, all the SBFD ROs 1–6 may be valid in accordance with the second option (regardless of the type of slot 610-f, 610-g) .
  • the preamble mapping to the respective ROs may be performed such that SSB-to-RO mapping to legacy/TDD ROs (e.g., common ROs 615) are done first, then SSB-to-RO mapping to SBFD-dedicated ROs (e.g., SBFD ROs 635) are done next, and where non-overlapping SBFD ROs 635 are performed last.
  • the temporally-overlapping SBFD ROs 635 may be performed prior to non-overlapping SBFD ROs 635 to ensure consistent SSB mappings (e.g., so that temporally-overlapping ROs are mapped to the same SSBs) .
  • the mapping for the set of common ROs 615-b may be done first, such that common RO1 maps to SSB #0, common RO2 maps to SSB #1, and common RO3 maps to SSB #2.
  • the mapping for the set of temporally-overlapping SBFD ROs 635 e.g., ROs 4–6
  • the mapping for the non-overlapping SBFD ROs 635 may be performed (e.g., independent mapping or distribution) .
  • FIG. 7 shows an example of a resource configuration 700 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • aspects of the resource configuration 700 may implement, or be implemented by, aspects of the wireless communications system 100, the two-step RACH procedure configuration 200, the wireless communications systems 300, the resource configurations 400-600, or any combination thereof.
  • the resource configuration 700 shown and described in FIG. 7 illustrates example resource configurations associated with the third implementation 405-c shown and described in FIG. 4.
  • the third implementation 405-c the third implementation 405-c includes both (1) SBFD-dedicated RACH resources for ROs, and (2) SBFD-dedicated PUSCH resources for POs (e.g., SBFD-dedicated RO/PO resources within SBFD slots for transmitting preambles and payloads of MsgA) .
  • a random access configuration in accordance with the third implementation 405-c may include a RACH configuration that includes both (1) SBFD-dedicated ROs within SBFD slots, and (2) common ROs within half-duplex uplink slots, as well as a PUSCH configuration that includes both (1) SBFD-dedicated POs within SBFD slots, and (2) common POs within half-duplex uplink slots.
  • the second slot 710-b, the third slot 710-c, and the fourth slot 710-d may include full-duplex slots (e.g., FDD UL/DL slots) that include both uplink and downlink resources (e.g., SBFD slots) .
  • the slots 710-b, 710-c, and 710-d may include downlink resources that are split by an uplink sub-band that includes uplink resources (e.g., uplink sub-band 330 illustrated in FIG. 3) .
  • a random access configuration in accordance with the third implementation 405-c may include a first RACH configuration (e.g., legacy/TDD RACH configuration) that includes resources for common ROs 715 within the half-duplex uplink slot 710-a, and a second RACH configuration (e.g., SBFD RACH configuration) that includes resources for full-duplex ROs 735 within the SBFD slot 710-b.
  • a first RACH configuration e.g., legacy/TDD RACH configuration
  • SBFD RACH configuration e.g., SBFD RACH configuration
  • an SBFD-aware UE 115 may be configured with an SBFD-dedicated MsgA configuration (e.g., SBFD RACH configuration, SBFD PUSCH configuration) for two-step RACH random access procedures (Type-2 Random access) .
  • the SBFD-dedicated MsgA configuration may include (1) an SBFD-dedicated MsgA-RACH configuration, and (2) an SBFD-dedicated MsgA-PUSCH configuration.
  • the SBFD-dedicated MsgA-PUSCH configuration may include or be associated with two sub-configurations for respective preamble groups.
  • the SBFD-dedicated MsgA-PUSCH configuration may include up to two MsgA PUSCH resource configurations (e.g., up to two sub-configuration) associated with the SBFD dedicated MsgA preamble Group A (e.g., first sub-configuration for preamble Group A) and MsgA-preamble Group B (e.g., second sub-configuration for preamble Group B) .
  • the RACH configuration (s) and the PUSCH configuration (s) for the third implementation 405-c may be signaled or otherwise configured at a UE 115 in a number of ways.
  • the respective configurations for the third implementation may be configured as part of a common random access configuration for MsgA, as shown below:
  • preambles of SBFD-dedicated ROs 735 may additionally or alternatively be mapped to the common (e.g., TDD/legacy) POs 720, as shown in the second diagram 705-b.
  • a SBFD-aware UE 115 may be able to send PRACH (e.g., MsgA preamble) in the SBFD-dedicated ROs 715, and then send the MsgA-PUSCH (e.g., MsgA payload) in either SBFD-dedicated POs 725 or common POs 720 (e.g., the UE 115 may select the earliest PO 720, 725 to transmit the MsgA payload) .
  • PRACH e.g., MsgA preamble
  • MsgA-PUSCH e.g., MsgA payload
  • preambles of the SBFD-dedicated ROs 735 may be mapped to (1) SBFD-dedicated POs 725 (diagram 705-a) , (2) common POs 720 (diagram 705-b) , or both.
  • preambles of common ROs 715 can be mapped to SBFD-dedicated POs 725, as shown in diagram 705-c.
  • SBFD-aware UEs 115 may be able to send PRACH (e.g., MsgA preambles) via the common ROs 715 (e.g., if common ROs 715 are earlier than SBFD ROs 735) , and transmit Msg-A PUSCH (e.g., MsgA payload) via the SBFD POs 725.
  • PRACH e.g., MsgA preambles
  • MsgA PUSCH e.g., MsgA payload
  • preambles of the common ROs 715 may be mapped to (1) common POs 720 (diagram 705-a) , (2) SBFD POs 725 (diagram 705-c) , or both.
  • the UE 115 may be configured to use any combination of a common RACH configuration (e.g., legacy/TDD RACH configuration) , an SBFD-dedicated RACH configuration, common PUSCH configuration (e.g., legacy/TDD PUSCH configuration) , and an SBFD-dedicated PUSCH configuration.
  • a common RACH configuration e.g., legacy/TDD RACH configuration
  • SBFD-dedicated RACH configuration e.g., common PUSCH configuration
  • SBFD-dedicated PUSCH configuration e.g., legacy/TDD PUSCH configuration
  • a UE 115 configured according to the third implementation 405-c may have four separate combinations for performing a two-step RACH procedure: (Option 1 –Legacy) : TDD-MsgA-PRACH configuration + TDD-MsgA-PUSCH configuration (shown in diagram 705-a) , (Option 2 –SBFD) : SBFD-MsgA-PRACH configuration + SBFD-MsgA-PUSCH configuration (shown in diagram 705-a) , (Option 3 -Mixed #1) : SBFD-MsgA-PRACH configuration + TDD-MsgA-PUSCH configuration (shown in diagram 705-b) , and (Option 4-Mixed #2) : TDD-MsgA-PRACH configuration + SBFD-MsgA-PUSCH configuration (shown in diagram 705-c) .
  • an SBFD-dedicated MsgA configuration may not include both an SBFD-dedicated RACH configuration and an SBFD-dedicated PUSCH configuration.
  • the UE 115 may be configured to “fall back” to common (e.g., TDD/legacy) configurations for the RACH or PUSCH configuration.
  • common e.g., TDD/legacy
  • the SBFD-aware UE 115 may be configured to share the same MsgA-RACH configuration of the common RACH configuration.
  • the UE 115 may be configured to “read in” the common (e.g., legacy/TDD) MsgA RACH configuration into the SBFD-dedicated MsgA configuration.
  • the SBFD-aware UE 115 may be configured to share the same MsgA-PUSCH configuration of common PUSCH configuration.
  • the UE 115 may be configured to “read in” the common (e.g., legacy/TDD) MsgA PUSCH configuration into the SBFD-dedicated MsgA configuration.
  • the respective configurations may be UE-specific (e.g., UE-dedicated) such that each UE 115 utilizes dedicated configurations, or cell-specific (e.g., cell-dedicated) such that all UEs 115 within the given cell utilize the same cell-specific configurations.
  • the network may indicate whether indicated configurations (e.g., RACH configurations, PUSCH configurations) are UE-specific or cell-specific.
  • SBFD-aware UEs 115 may additionally be configured with UE-dedicated two-step RACH procedures in SBFD symbols for the additional operations or use-cases, such as SI requests, PDCCH orders (e.g., CFRA or CBRA) , beam failure recovery (BFR) , mobility, and the like.
  • the UE 115 may be configured with different random access configurations that are usable for different operations, procedures, or use cases.
  • a UE 115 may be configured to apply or extend indicated random access configurations to other operations, procedures, or use cases. For example, if an SBFD-aware UE 115 is configured with only a TDD dedicated two-step RA configuration for BFR, SI, mobility, etc., then the SBFD-aware UE 115 may be configured to use only the TDD msgA-RACH/msgA-PUSCH configuration (e.g., TDD msgA random access configuration) for performing BFR, SI, mobility, etc.
  • TDD msgA-RACH/msgA-PUSCH configuration e.g., TDD msgA random access configuration
  • the SBFD-aware UE 115 may be able to use the cell-specific SBFD msgARACH configuration for performing BFR, SI, mobility, etc.
  • an SBFD-aware UE 115 may be configured to use only the cell-specific TDD RACH configuration for performing BFR, SI, mobility, etc.
  • the SBFD-aware can UE 115 may be able to either the cell-specific SBFD RACH configuration or the cell-specific TDD RACH configuration for performing BFR, SI, mobility, etc.
  • FIG. 8 shows an example of a process flow 800 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • aspects of the process flow 800 may implement, or be implemented by, aspects of the wireless communications system 100, the two-step RACH procedure configuration 200, the wireless communications systems 300, the resource configurations 400-700, or any combination thereof.
  • the process flow 800 illustrates signaling and configurations for two-step RACH procedures that utilize dedicated SBFD resources, as described previously herein.
  • the process flow 800 includes a UE 115-c and a network entity 105-c, which may be examples of wireless devices as described herein.
  • the UE 115-c and the network entity 105-c illustrated in FIG. 8 may include examples of the UEs 115-a, 115-b and the network entities 105-a, 105-b, respectively, as illustrated in FIGs. 2 and 3.
  • the UE 115-c may be an example of an SBFD-aware UE 115 (e.g., a UE 115 capable of performing full-duplex communications, or otherwise capable of communicating within full-duplex slots) .
  • process flow 800 may be performed by hardware (e.g., including circuitry, processing blocks, logic components, and other components) , code (e.g., software or firmware) executed by a processor, or any combination thereof.
  • code e.g., software or firmware
  • Alternative examples of the following may be implemented, where some steps are performed in a different order than described or are not performed at all. In some cases, steps may include additional features not mentioned below, or further steps may be added.
  • the UE 115-c may receive control signaling (e.g., RRC, SI) from the network entity 105-c, where the control signaling includes a random access configuration for performing a two-step RACH procedure with the network entity 105-c.
  • control signaling may indicate one or more RACH configurations and one or more PUSCH configurations for performing a two-step RACH procedure.
  • the RACH configuration (s) indicated via the control signaling at 805 may be associated with common ROs (e.g., legacy/TDD ROs) used to transmit MsgA preambles, as shown and described in FIGs. 4–7.
  • the PUSCH configuration (s) indicated via the control signaling at 805 may be associated with common POs (e.g., legacy/TDD ROs) used to transmit MsgA payloads, as shown and described in FIGs. 4–7.
  • the network may utilize various implementations that include different combinations of common ROs/POs and full-duplex ROs/POs.
  • the control signaling at 805 may configure the UE 115 according to the first implementation 405-a shown in FIG. 5, where the UE 115 receives a common RACH configuration, a common PUSCH configuration, and an SBFD PUSCH configuration.
  • the control signaling at 805 may configure the UE 115 according to the second implementation 405-b shown in FIG. 6, where the UE 115 receives a common RACH configuration, an SBFD RACH configuration, and a common PUSCH configuration.
  • the control signaling at 805 may configure the UE 115 according to the third implementation 405-c shown in FIG. 7, where the UE 115 receives a common RACH configuration, an SBFD RACH configuration, a common PUSCH configuration, and an SBFD PUSCH configuration.
  • the UE 115-c may monitor a set of SSBs associated with the configured ROs/POs. That is, the UE 115-c may perform measurements to evaluate channel quality metrics associated with the respective SSBs. As such, the UE 115-c may monitor the SSBs at 810 based on receiving the control signaling at 805.
  • the UE 115-c may select an SSB/preamble that will be used for a two-step RACH procedure.
  • the UE 115-c may select the SSB/preamble at 815 based on receiving the control signaling at 805, monitoring the SSB at 815, or both. For example, referring to FIG. 5, the UE 115-c may determine that SSB #1 has the highest channel quality, and may therefore select the preambles corresponding to SSB #1 to perform the two-step RACH procedure.
  • the UE 115-c may select/identify whether to use the common ROs/POs, or the SBFD ROs/POs. In some cases, the UE 115-c may select whether to use common or SBFD resources based on receiving the control signaling at 805, monitoring the SSB at 815, selecting the SSB/preamble at 815, or any combination thereof.
  • the UE 115-a may select whether to use common or SBFD ROs/POs based on a number of criteria, including a relative timing of the common ROs 615-a and SBFD ROs 635-a in the time domain, based on measured/predicted channel quality metrics of the slots 610 including the respective ROs, based on RRC configuration (e.g., pre-configuration by the network) , based on a type of UE 115 (e.g., full-duplex UE 115, half-duplex UE 115) , PUSCH Tx power relative to a threshold PUSCH Tx power, or any combination thereof.
  • the UE 115-c may select to use one of the SBFD POs 525 corresponding to SSB #1 (instead of common PO2 520 corresponding to SSB #1) based on the SBFD POs 525 occurring earlier in time.
  • the UE 115-c may transmit a preamble of a first message (e.g., MsgA) of the two-step RACH procedure.
  • the UE 115-c may transmit the MsgA preamble at 825 based on receiving the control signaling at 805, monitoring the SSB at 815, selecting the SSB/preamble at 815, selecting/identifying whether to use common or SBFD resources at 820, or any combination thereof.
  • the UE 115-c may transmit the preamble via an RO associated with a RACH configuration indicated via the control signaling at 805. For instance, continuing with the same example above, upon identifying that SSB #1 has the highest channel quality, the UE 115-c may transmit the MsgA preamble using the common RO2 515 corresponding to SSB #1.
  • the UE 115-a may transmit a payload of the first message (e.g., MsgA) of the two-step RACH procedure.
  • the UE 115-c may transmit the MsgA payload at 830 based on receiving the control signaling at 805, monitoring the SSB at 815, selecting the SSB/preamble at 815, selecting/identifying whether to use common or SBFD resources at 820, transmitting the MsgA preamble at 825, or any combination thereof.
  • the UE 115-c may transmit the MsgA payload via a PO associated with a PUSCH configuration indicated via the control signaling at 805, and using a PO that maps to the preamble/SSB of the RO used to transmit the MsgA preamble at 825.
  • the UE 115-c may transmit the MsgA payload via the SBFD POs 3–4 that maps to the preamble of common RO2 515, or via the common PO2 520 that maps to the preamble of common RO2 515.
  • the network entity 105-c may decode the MsgA payload.
  • the network entity 105-c may receive the MsgA preamble at 825, and may monitor the PO (s) corresponding to the RO in which the MsgA preamble was received in order to decode the MsgA payload.
  • the network entity 105-c may transmit a MsgB PDCCH portion to the UE 115-c.
  • the MsgB PDCCH portion may include C-RNTI, MsgB-RNTI, or both.
  • the network entity 105-c may transmit a MsgB PDSCH portion to the UE 115-c.
  • MsgB of the two-step RACH procedure (shown at 225 and 230) may include the information that is included within Msg2 and Msg4 of a four-step RACH procedure.
  • the MsgB PDSCH may indicate a success random access response (RAR) .
  • RAR success random access response
  • the MsgB PDSCH may indicate a successful completion of the two-step RACH procedure.
  • the UE 115-c may identify a valid TA and PUCCH resource/timing based on the successful completion of the two-step RACH procedure. That is, the UE 115-c may identify a valid TA and/or PUCCH resources/timing based on the MsgB PDCCH and/or MsgB PDSCH received at 840 and/or 845.
  • the UE 115-c may transmit a HARQ message to the network entity 105-c, where the HARQ message includes an ACK/NACK responsive to the MsgB received at 840 and 845. Subsequently, the UE 115-c and the network entity 105-c may communicate with one another based on the successful completion of the two-step RACH procedure.
  • FIG. 9 shows a block diagram 900 of a device 905 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • the device 905 may be an example of aspects of a UE 115 as described herein.
  • the device 905 may include a receiver 910, a transmitter 915, and a communications manager 920.
  • the device 905, or one or more components of the device 905 may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 910 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for two-step random access procedures using dedicated SBFD resources) . Information may be passed on to other components of the device 905.
  • the receiver 910 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 915 may provide a means for transmitting signals generated by other components of the device 905.
  • the transmitter 915 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for two-step random access procedures using dedicated SBFD resources) .
  • the transmitter 915 may be co-located with a receiver 910 in a transceiver module.
  • the transmitter 915 may utilize a single antenna or a set of multiple antennas.
  • the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be examples of means for performing various aspects of techniques for two-step random access procedures using dedicated SBFD resources as described herein.
  • the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be capable of performing one or more of the functions described herein.
  • the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include at least one of a processor, a digital signal processor (DSP) , a central processing unit (CPU) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure.
  • DSP digital signal processor
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • microcontroller discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure.
  • At least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .
  • the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code) . If implemented in code executed by at least one processor, the functions of the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure) .
  • a general-purpose processor e.g., a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions
  • the communications manager 920 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 915, or both.
  • the communications manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 920 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a RACH configuration including a set of multiple common ROs within a first half-duplex uplink slot.
  • the communications manager 920 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or more full-duplex slots.
  • the communications manager 920 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity via a common RO of the set of multiple common ROs.
  • the communications manager 920 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that is associated with the common RO, or via a full-duplex PO from the set of full-duplex POs that is associated with the common RO used to transmit the preamble.
  • the communications manager 920 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
  • the communications manager 920 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots.
  • the communications manager 920 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, an PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple POs associated with the set of common ROs and the set of full-duplex ROs, the set of multiple POs including a set of common POs within one or more additional half-duplex uplink slots.
  • the communications manager 920 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO of the set of full-duplex ROs.
  • the communications manager 920 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity via a common PO of the set of common POs that maps to the common RO or the full-duplex RO that was used to transmit the preamble.
  • the communications manager 920 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
  • the communications manager 920 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots.
  • the communications manager 920 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or additional more full-duplex slots, where the set of common ROs are mapped to the set of common POs, and where the set of full-duplex ROs mapped to the set of full-duplex POs.
  • the communications manager 920 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO from the set of full-duplex ROs.
  • the communications manager 920 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that maps to the common RO based on transmitting the preamble via the common RO, or via a full-duplex PO from the set of full-duplex POs that maps to the common RO used to transmit the preamble based on transmitting the preamble via the full-duplex RO.
  • the communications manager 920 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
  • the device 905 may support signaling and configurations that facilitate faster and more efficient RACH procedures (e.g., two-step RACH procedures) .
  • RACH procedures e.g., two-step RACH procedures
  • techniques described herein may reduce a latency of two-step RACH procedures, and alleviate congestion/collisions within conventional RACH procedure resources within half-duplex slots.
  • FIG. 10 shows a block diagram 1000 of a device 1005 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • the device 1005 may be an example of aspects of a device 905 or a UE 115 as described herein.
  • the device 1005 may include a receiver 1010, a transmitter 1015, and a communications manager 1020.
  • the device 1005, or one or more components of the device 1005 may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 1010 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for two-step random access procedures using dedicated SBFD resources) . Information may be passed on to other components of the device 1005.
  • the receiver 1010 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 1015 may provide a means for transmitting signals generated by other components of the device 1005.
  • the transmitter 1015 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for two-step random access procedures using dedicated SBFD resources) .
  • the transmitter 1015 may be co-located with a receiver 1010 in a transceiver module.
  • the transmitter 1015 may utilize a single antenna or a set of multiple antennas.
  • the device 1005, or various components thereof, may be an example of means for performing various aspects of techniques for two-step random access procedures using dedicated SBFD resources as described herein.
  • the communications manager 1020 may include a control signaling receiving manager 1025, a preamble transmitting manager 1030, a payload transmitting manager 1035, a RACH procedure manager 1040, or any combination thereof.
  • the communications manager 1020 may be an example of aspects of a communications manager 920 as described herein.
  • the communications manager 1020, or various components thereof may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both.
  • the communications manager 1020 may receive information from the receiver 1010, send information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.
  • the control signaling receiving manager 1025 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a RACH configuration including a set of multiple common ROs within a first half-duplex uplink slot.
  • the control signaling receiving manager 1025 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or more full-duplex slots.
  • the preamble transmitting manager 1030 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity via a common RO of the set of multiple common ROs.
  • the payload transmitting manager 1035 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that is associated with the common RO, or via a full-duplex PO from the set of full-duplex POs that is associated with the common RO used to transmit the preamble.
  • the RACH procedure manager 1040 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
  • the control signaling receiving manager 1025 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots.
  • the control signaling receiving manager 1025 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, an PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple POs associated with the set of common ROs and the set of full-duplex ROs, the set of multiple POs including a set of common POs within one or more additional half-duplex uplink slots.
  • the preamble transmitting manager 1030 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO of the set of full-duplex ROs.
  • the payload transmitting manager 1035 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity via a common PO of the set of common POs that maps to the common RO or the full-duplex RO that was used to transmit the preamble.
  • the RACH procedure manager 1040 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
  • the control signaling receiving manager 1025 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots.
  • the control signaling receiving manager 1025 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or additional more full-duplex slots, where the set of common ROs are mapped to the set of common POs, and where the set of full-duplex ROs mapped to the set of full-duplex POs.
  • the preamble transmitting manager 1030 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO from the set of full-duplex ROs.
  • the payload transmitting manager 1035 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that maps to the common RO based on transmitting the preamble via the common RO, or via a full-duplex PO from the set of full-duplex POs that maps to the common RO used to transmit the preamble based on transmitting the preamble via the full-duplex RO.
  • the RACH procedure manager 1040 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
  • FIG. 11 shows a block diagram 1100 of a communications manager 1120 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • the communications manager 1120 may be an example of aspects of a communications manager 920, a communications manager 1020, or both, as described herein.
  • the communications manager 1120, or various components thereof, may be an example of means for performing various aspects of techniques for two-step random access procedures using dedicated SBFD resources as described herein.
  • the communications manager 1120 may include a control signaling receiving manager 1125, a preamble transmitting manager 1130, a payload transmitting manager 1135, a RACH procedure manager 1140, a PO selection manager 1145, a validity manager 1150, an SSB monitoring manager 1155, a RO selection manager 1160, or any combination thereof.
  • Each of these components, or components or subcomponents thereof e.g., one or more processors, one or more memories
  • the control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a RACH configuration including a set of multiple common ROs within a first half-duplex uplink slot.
  • control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or more full-duplex slots.
  • the preamble transmitting manager 1130 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity via a common RO of the set of multiple common ROs.
  • the payload transmitting manager 1135 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that is associated with the common RO, or via a full-duplex PO from the set of full-duplex POs that is associated with the common RO used to transmit the preamble.
  • the RACH procedure manager 1140 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
  • control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of multiple common ROs and the set of common POs, and a second mapping configuration between the set of multiple preambles of the set of multiple common ROs and the set of full-duplex POs.
  • the PO selection manager 1145 is capable of, configured to, or operable to support a means for selecting one of the common PO or the full-duplex PO that maps to the common RO used to transmit the preamble in accordance with the first mapping configuration or the second mapping configuration, where the payload of the first message is transmitted via the selected one of the common PO or the full-duplex PO.
  • each common RO from the set of multiple common ROs is mapped to a set of multiple full-duplex POs from the set of full-duplex POs.
  • the second PUSCH configuration includes a first sub-configuration associated with a first preamble group including the set of full-duplex POs, and a second sub-configuration associated with a second preamble group including an additional set of full-duplex POs.
  • the PO selection manager 1145 is capable of, configured to, or operable to support a means for selecting one of the common PO or the full-duplex PO that maps to the common RO based on a relative timing of the common PO and the full-duplex PO in a time domain, one or more measured or predicted downlink signal quality metrics associated with slots that include the common PO and the full-duplex PO, an RRC configuration, a PUSCH Tx power relative to a Tx power threshold associated with the one or more full-duplex slots, a type of UE, or any combination thereof, where the payload of the first message of the two-step random access procedure is transmitted via the selected one of the common PO or the full-duplex PO.
  • the validity manager 1150 is capable of, configured to, or operable to support a means for determining a validity of each full-duplex PO within the set of full-duplex POs based on a type of slot corresponding to each of the set of full-duplex POs, the type of slot including a full-duplex slot type or a half-duplex slot type.
  • the validity manager 1150 is capable of, configured to, or operable to support a means for determining that each full-duplex PO of the set of full-duplex POs is valid regardless of the type of slot in accordance with a first validity rule. In some examples, to support determining the validity of each full-duplex PO, the validity manager 1150 is capable of, configured to, or operable to support a means for determining that a subset of POs from the set of full-duplex POs are invalid based on the subset of POs being positioned within non-full-duplex slots and in accordance with a second validity rule.
  • the set of full-duplex POs include a first subset of full-duplex POs within the one or more full-duplex slots, and a second subset of full-duplex POs that overlap in a time domain with the set of common POs within the one or more second half-duplex uplink slots.
  • the set of multiple common ROs are associated with a set of multiple preambles .
  • the set of multiple preambles are mapped to the set of common POs and the set of full-duplex POs such that temporally overlapping pairs of POs are associated with one or more common preambles of the set of multiple preambles.
  • each temporally overlapping pair of POs include one of the second subset of full-duplex POs and one of the set of common POs.
  • the SSB monitoring manager 1155 is capable of, configured to, or operable to support a means for monitoring a set of multiple synchronization signal blocks, the set of multiple synchronization signal blocks corresponding with the set of multiple common ROs.
  • the RO selection manager 1160 is capable of, configured to, or operable to support a means for selecting the common RO from the set of multiple common ROs based on the monitoring.
  • the set of full-duplex POs include SBFD POs.
  • the one or more full-duplex slots include one or more SBFD slots.
  • the first PUSCH configuration indicates a first starting resource block frequency configuration associated with the set of common POs.
  • the second PUSCH configuration indicates a second starting resource block frequency configuration associated with the set of full-duplex POs.
  • the first PUSCH configuration indicates a first quantity of frequency-division multiplexed POs associated with the set of common POs within the one or more second half-duplex uplink slots.
  • the second PUSCH configuration indicates a second quantity of frequency-division multiplexed POs associated with the set of full-duplex POs within the one or more full-duplex slots.
  • the set of multiple common ROs and the set of common POs are usable by full-duplex-aware UEs and non-full-duplex-aware UEs.
  • the set of full-duplex POs are usable by full-duplex-aware UEs but unusable by non-full-duplex-aware UEs.
  • control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots.
  • control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, an PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple POs associated with the set of common ROs and the set of full-duplex ROs, the set of multiple POs including a set of common POs within one or more additional half-duplex uplink slots.
  • the preamble transmitting manager 1130 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO of the set of full-duplex ROs.
  • the payload transmitting manager 1135 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity via a common PO of the set of common POs that maps to the common RO or the full-duplex RO that was used to transmit the preamble.
  • the RACH procedure manager 1140 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
  • the first half-duplex uplink slot including the set of common ROs includes a PRACH slot.
  • the PUSCH configuration includes a first time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common POs, and a second time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common POs.
  • control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of common ROs and the set of common POs, and a second mapping configuration between the set of multiple preambles of the set of full-duplex ROs and the set of common POs.
  • each common PO from the set of common POs is mapped to at least one common RO from the set of common ROs and at least one full-duplex RO from the set of full-duplex ROs.
  • the RO selection manager 1160 is capable of, configured to, or operable to support a means for selecting one of the common RO or the full-duplex RO based on a relative timing of the common RO and the full-duplex RO in a time domain, one or more measured or predicted signal quality metrics associated with slots that include the common RO and the full-duplex RO, a PUSCH Tx power relative to a Tx power threshold associated with the one or more full-duplex slots, an RRC configuration, a type of UE, or any combination thereof, where the preamble of the first message of the two-step random access procedure is transmitted via the selected one of the common RO or the full-duplex RO.
  • the validity manager 1150 is capable of, configured to, or operable to support a means for determining a validity of each full-duplex RO within the set of full-duplex ROs based on a type of slot corresponding to each of the set of full-duplex ROs, the type of slot including a full-duplex slot type or a half-duplex slot type.
  • the validity manager 1150 is capable of, configured to, or operable to support a means for determining that each full-duplex RO of the set of full-duplex ROs is valid regardless of the type of slot in accordance with a first validity rule. In some examples, to support determining the validity of each full-duplex RO, the validity manager 1150 is capable of, configured to, or operable to support a means for determining that a subset of ROs from the set of full-duplex ROs are invalid based on the subset of ROs being positioned within non-full-duplex slots and in accordance with a second validity rule.
  • the set of full-duplex ROs include a first subset of full-duplex ROs within the one or more full-duplex slots, and a second subset of full-duplex ROs that overlap in a time domain with the set of common ROs within the first half-duplex uplink slot.
  • the set of common ROs and the set of full-duplex ROs are associated with a set of multiple preambles such that temporally overlapping pairs of ROs map to one or more common preambles of the set of multiple preambles.
  • each temporally overlapping pair of ROs include one of the second subset of full-duplex ROs and one of the set of common ROs.
  • the set of full-duplex ROs include SBFD ROs.
  • the one or more full-duplex slots include one or more SBFD slots.
  • control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots.
  • control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or additional more full-duplex slots, where the set of common ROs are mapped to the set of common POs, and where the set of full-duplex ROs mapped to the set of full-duplex POs.
  • the preamble transmitting manager 1130 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO from the set of full-duplex ROs.
  • the payload transmitting manager 1135 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that maps to the common RO based on transmitting the preamble via the common RO, or via a full-duplex PO from the set of full-duplex POs that maps to the common RO used to transmit the preamble based on transmitting the preamble via the full-duplex RO.
  • the RACH procedure manager 1140 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
  • control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of common ROs and the set of common POs, and a second mapping configuration between the set of multiple preambles of the set of full-duplex ROs and the set of full-duplex POs.
  • control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, the second control signaling, or both, a third mapping configuration between the set of multiple preambles of set of common ROs and the set of full-duplex POs, a fourth mapping configuration between the set of multiple preambles of the set of full-duplex ROs and the set of common POs, or both.
  • the set of full-duplex ROs include SBFD ROs.
  • the set of full-duplex POs include SBFD POs.
  • the one or more full-duplex slots, the one or more additional full-duplex slots, or both include one or more SBFD slots.
  • control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, the second control signaling, or both, an indication that the first RACH configuration, second RACH configuration, the first PUSCH configuration, the second PUSCH configuration, or any combination thereof, are usable for performing random access procedures associated with SI requests, physical downlink control channel ordering, BFR, mobility, or any combination thereof.
  • control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, the second control signaling, or both, an indication that the second RACH configuration, the second PUSCH configuration, or both, include UE-specific configurations or cell-specific configurations.
  • control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, the second control signaling, third control signaling, or any combination thereof, a common random access configuration associated with one or more operations different from the two-step random access procedure. In some examples, the control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for performing the one or more operations in accordance with either the common random access configuration, or in accordance with the second RACH configuration and the second PUSCH configuration.
  • the RACH procedure manager 1140 is capable of, configured to, or operable to support a means for determining that the UE has not been configured with a common random access configuration associated with one or more operations different from the two-step random access procedure. In some examples, the RACH procedure manager 1140 is capable of, configured to, or operable to support a means for performing the one or more operations in accordance with the first RACH configuration and the first PUSCH configuration, or in accordance with the second RACH configuration and the second PUSCH configuration.
  • FIG. 12 shows a diagram of a system 1200 including a device 1205 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • the device 1205 may be an example of or include components of a device 905, a device 1005, or a UE 115 as described herein.
  • the device 1205 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entities 105, UEs 115, or a combination thereof) .
  • the device 1205 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1220, an input/output (I/O) controller, such as an I/O controller 1210, a transceiver 1215, one or more antennas 1225, at least one memory 1230, code 1235, and at least one processor 1240. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1245) .
  • a bus 1245 e.g., a bus 1245
  • the I/O controller 1210 may manage input and output signals for the device 1205.
  • the I/O controller 1210 may also manage peripherals not integrated into the device 1205.
  • the I/O controller 1210 may represent a physical connection or port to an external peripheral.
  • the I/O controller 1210 may utilize an operating system such as or another known operating system.
  • the I/O controller 1210 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device.
  • the I/O controller 1210 may be implemented as part of one or more processors, such as the at least one processor 1240.
  • a user may interact with the device 1205 via the I/O controller 1210 or via hardware components controlled by the I/O controller 1210.
  • the device 1205 may include a single antenna. However, in some other cases, the device 1205 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 1215 may communicate bi-directionally via the one or more antennas 1225 using wired or wireless links as described herein.
  • the transceiver 1215 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1215 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1225 for transmission, and to demodulate packets received from the one or more antennas 1225.
  • the transceiver 1215 may be an example of a transmitter 915, a transmitter 1015, a receiver 910, a receiver 1010, or any combination thereof or component thereof, as described herein.
  • the at least one memory 1230 may include random access memory (RAM) and read-only memory (ROM) .
  • the at least one memory 1230 may store computer-readable, computer-executable, or processor-executable code, such as the code 1235.
  • the code 1235 may include instructions that, when executed by the at least one processor 1240, cause the device 1205 to perform various functions described herein.
  • the code 1235 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code 1235 may not be directly executable by the at least one processor 1240 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the at least one memory 1230 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the at least one processor 1240 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs) , one or more graphics processing units (GPUs) , one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs) ) , one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof) .
  • the at least one processor 1240 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the at least one processor 1240.
  • the at least one processor 1240 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 1230) to cause the device 1205 to perform various functions (e.g., functions or tasks supporting techniques for two-step random access procedures using dedicated SBFD resources) .
  • the device 1205 or a component of the device 1205 may include at least one processor 1240 and at least one memory 1230 coupled with or to the at least one processor 1240, the at least one processor 1240 and the at least one memory 1230 configured to perform various functions described herein.
  • the at least one processor 1240 may include multiple processors and the at least one memory 1230 may include multiple memories.
  • the at least one processor 1240 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1240) and memory circuitry (which may include the at least one memory 1230) ) , or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs.
  • the processing system may be configured to perform one or more of the functions described herein.
  • the at least one processor 1240 or a processing system including the at least one processor 1240 may be configured to, configurable to, or operable to cause the device 1205 to perform one or more of the functions described herein.
  • being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code 1235 (e.g., processor-executable code) stored in the at least one memory 1230 or otherwise, to perform one or more of the functions described herein.
  • code 1235 e.g., processor-executable code
  • the communications manager 1220 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a RACH configuration including a set of multiple common ROs within a first half-duplex uplink slot.
  • the communications manager 1220 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or more full-duplex slots.
  • the communications manager 1220 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity via a common RO of the set of multiple common ROs.
  • the communications manager 1220 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that is associated with the common RO, or via a full-duplex PO from the set of full-duplex POs that is associated with the common RO used to transmit the preamble.
  • the communications manager 1220 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
  • the communications manager 1220 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots.
  • the communications manager 1220 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, an PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple POs associated with the set of common ROs and the set of full-duplex ROs, the set of multiple POs including a set of common POs within one or more additional half-duplex uplink slots.
  • the communications manager 1220 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO of the set of full-duplex ROs.
  • the communications manager 1220 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity via a common PO of the set of common POs that maps to the common RO or the full-duplex RO that was used to transmit the preamble.
  • the communications manager 1220 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
  • the communications manager 1220 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots.
  • the communications manager 1220 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or additional more full-duplex slots, where the set of common ROs are mapped to the set of common POs, and where the set of full-duplex ROs mapped to the set of full-duplex POs.
  • the communications manager 1220 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO from the set of full-duplex ROs.
  • the communications manager 1220 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that maps to the common RO based on transmitting the preamble via the common RO, or via a full-duplex PO from the set of full-duplex POs that maps to the common RO used to transmit the preamble based on transmitting the preamble via the full-duplex RO.
  • the communications manager 1220 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
  • the device 1205 may support signaling and configurations that facilitate faster and more efficient RACH procedures (e.g., two-step RACH procedures) .
  • RACH procedures e.g., two-step RACH procedures
  • techniques described herein may reduce a latency of two-step RACH procedures, and alleviate congestion/collisions within conventional RACH procedure resources within half-duplex slots.
  • the communications manager 1220 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 1215, the one or more antennas 1225, or any combination thereof.
  • the communications manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1220 may be supported by or performed by the at least one processor 1240, the at least one memory 1230, the code 1235, or any combination thereof.
  • the code 1235 may include instructions executable by the at least one processor 1240 to cause the device 1205 to perform various aspects of techniques for two-step random access procedures using dedicated SBFD resources as described herein, or the at least one processor 1240 and the at least one memory 1230 may be otherwise configured to, individually or collectively, perform or support such operations.
  • FIG. 13 shows a block diagram 1300 of a device 1305 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • the device 1305 may be an example of aspects of a network entity 105 as described herein.
  • the device 1305 may include a receiver 1310, a transmitter 1315, and a communications manager 1320.
  • the device 1305, or one or more components of the device 1305 may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 1310 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
  • Information may be passed on to other components of the device 1305.
  • the receiver 1310 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1310 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 1315 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1305.
  • the transmitter 1315 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
  • the transmitter 1315 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1315 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 1315 and the receiver 1310 may be co-located in a transceiver, which may include or be coupled with a modem.
  • the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be examples of means for performing various aspects of techniques for two-step random access procedures using dedicated SBFD resources as described herein.
  • the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be capable of performing one or more of the functions described herein.
  • the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure.
  • at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .
  • the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code) . If implemented in code executed by at least one processor, the functions of the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure) .
  • a general-purpose processor e.g., a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions
  • the communications manager 1320 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1310, the transmitter 1315, or both.
  • the communications manager 1320 may receive information from the receiver 1310, send information to the transmitter 1315, or be integrated in combination with the receiver 1310, the transmitter 1315, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 1320 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a RACH configuration including a set of multiple common ROs within a first half-duplex uplink slot.
  • the communications manager 1320 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or more full-duplex slots.
  • the communications manager 1320 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity via a common RO of the set of multiple common ROs.
  • the communications manager 1320 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that is associated with the common RO, or via a full-duplex PO from the set of full-duplex POs that is associated with the common RO used to receive the preamble.
  • the communications manager 1320 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
  • the communications manager 1320 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots.
  • the communications manager 1320 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, an PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple POs associated with the set of common ROs and the set of full-duplex ROs, the set of multiple POs including a set of common POs within one or more additional half-duplex uplink slots.
  • the communications manager 1320 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO of the set of full-duplex ROs.
  • the communications manager 1320 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity via a common PO of the set of common POs that maps to the common RO or the full-duplex RO that was used to receive the preamble.
  • the communications manager 1320 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
  • the communications manager 1320 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots.
  • the communications manager 1320 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or additional more full-duplex slots, where the set of common ROs are mapped to the set of common POs, and where the set of full-duplex ROs mapped to the set of full-duplex POs.
  • the communications manager 1320 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO from the set of full-duplex ROs.
  • the communications manager 1320 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that maps to the common RO based on transmitting the preamble via the common RO, or via a full-duplex PO from the set of full-duplex POs that maps to the common RO used to receive the preamble based on receiving the preamble via the full-duplex RO.
  • the communications manager 1320 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
  • the device 1305 may support signaling and configurations that facilitate faster and more efficient RACH procedures (e.g., two-step RACH procedures) .
  • RACH procedures e.g., two-step RACH procedures
  • techniques described herein may reduce a latency of two-step RACH procedures, and alleviate congestion/collisions within conventional RACH procedure resources within half-duplex slots.
  • FIG. 14 shows a block diagram 1400 of a device 1405 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • the device 1405 may be an example of aspects of a device 1305 or a network entity 105 as described herein.
  • the device 1405 may include a receiver 1410, a transmitter 1415, and a communications manager 1420.
  • the device 1405, or one or more components of the device 1405 may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 1410 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
  • Information may be passed on to other components of the device 1405.
  • the receiver 1410 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1410 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 1415 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1405.
  • the transmitter 1415 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
  • the transmitter 1415 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1415 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 1415 and the receiver 1410 may be co-located in a transceiver, which may include or be coupled with a modem.
  • the device 1405, or various components thereof may be an example of means for performing various aspects of techniques for two-step random access procedures using dedicated SBFD resources as described herein.
  • the communications manager 1420 may include a control signaling transmitting manager 1425, a preamble receiving manager 1430, a payload receiving manager 1435, a RACH procedure manager 1440, or any combination thereof.
  • the communications manager 1420 may be an example of aspects of a communications manager 1320 as described herein.
  • the communications manager 1420, or various components thereof may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1410, the transmitter 1415, or both.
  • the communications manager 1420 may receive information from the receiver 1410, send information to the transmitter 1415, or be integrated in combination with the receiver 1410, the transmitter 1415, or both to obtain information, output information, or perform various other operations as described herein.
  • the control signaling transmitting manager 1425 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a RACH configuration including a set of multiple common ROs within a first half-duplex uplink slot.
  • the control signaling transmitting manager 1425 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or more full-duplex slots.
  • the preamble receiving manager 1430 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity via a common RO of the set of multiple common ROs.
  • the payload receiving manager 1435 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that is associated with the common RO, or via a full-duplex PO from the set of full-duplex POs that is associated with the common RO used to receive the preamble.
  • the RACH procedure manager 1440 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
  • the control signaling transmitting manager 1425 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots.
  • the control signaling transmitting manager 1425 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, an PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple POs associated with the set of common ROs and the set of full-duplex ROs, the set of multiple POs including a set of common POs within one or more additional half-duplex uplink slots.
  • the preamble receiving manager 1430 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO of the set of full-duplex ROs.
  • the payload receiving manager 1435 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity via a common PO of the set of common POs that maps to the common RO or the full-duplex RO that was used to receive the preamble.
  • the RACH procedure manager 1440 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
  • the control signaling transmitting manager 1425 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots.
  • the control signaling transmitting manager 1425 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or additional more full-duplex slots, where the set of common ROs are mapped to the set of common POs, and where the set of full-duplex ROs mapped to the set of full-duplex POs.
  • the preamble receiving manager 1430 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO from the set of full-duplex ROs.
  • the payload receiving manager 1435 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that maps to the common RO based on transmitting the preamble via the common RO, or via a full-duplex PO from the set of full-duplex POs that maps to the common RO used to receive the preamble based on receiving the preamble via the full-duplex RO.
  • the RACH procedure manager 1440 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
  • FIG. 15 shows a block diagram 1500 of a communications manager 1520 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • the communications manager 1520 may be an example of aspects of a communications manager 1320, a communications manager 1420, or both, as described herein.
  • the communications manager 1520, or various components thereof, may be an example of means for performing various aspects of techniques for two-step random access procedures using dedicated SBFD resources as described herein.
  • the communications manager 1520 may include a control signaling transmitting manager 1525, a preamble receiving manager 1530, a payload receiving manager 1535, a RACH procedure manager 1540, a PO identification manager 1545, a validity manager 1550, a RO identification manager 1555, or any combination thereof.
  • Each of these components, or components or subcomponents thereof e.g., one or more processors, one or more memories
  • the communications may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105) , or any combination thereof.
  • the control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a RACH configuration including a set of multiple common ROs within a first half-duplex uplink slot.
  • control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or more full-duplex slots.
  • the preamble receiving manager 1530 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity via a common RO of the set of multiple common ROs.
  • the payload receiving manager 1535 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that is associated with the common RO, or via a full-duplex PO from the set of full-duplex POs that is associated with the common RO used to receive the preamble.
  • the RACH procedure manager 1540 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
  • control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of multiple common ROs and the set of common POs, and a second mapping configuration between the set of multiple preambles of the set of multiple common ROs and the set of full-duplex POs.
  • the PO identification manager 1545 is capable of, configured to, or operable to support a means for identifying one of the common PO or the full-duplex PO that maps to the common RO used to transmit the preamble in accordance with the first mapping configuration or the second mapping configuration, where the payload of the first message is received via the identified one of the common PO or the full-duplex PO.
  • each common RO from the set of multiple common ROs is mapped to a set of multiple full-duplex POs from the set of full-duplex POs.
  • the second PUSCH configuration includes a first sub-configuration associated with a first preamble group including the set of full-duplex POs, and a second sub-configuration associated with a second preamble group including an additional set of full-duplex POs.
  • the PO identification manager 1545 is capable of, configured to, or operable to support a means for identifying one of the common PO or the full-duplex PO that maps to the common RO based on a relative timing of the common PO and the full-duplex PO in a time domain, one or more measured or predicted downlink signal quality metrics associated with slots that include the common PO and the full-duplex PO, an RRC configuration, a PUSCH Tx power relative to a Tx power threshold associated with the one or more full-duplex slots, a type of UE, or any combination thereof, where the payload of the first message of the two-step random access procedure is received via the identified one of the common PO or the full-duplex PO.
  • the validity manager 1550 is capable of, configured to, or operable to support a means for determining a validity of each full-duplex PO within the set of full-duplex POs based on a type of slot corresponding to each of the set of full-duplex POs, the type of slot including a full-duplex slot type or a half-duplex slot type.
  • the validity manager 1550 is capable of, configured to, or operable to support a means for determining that each full-duplex PO of the set of full-duplex POs is valid regardless of the type of slot in accordance with a first validity rule. In some examples, to support determining the validity of each full-duplex PO, the validity manager 1550 is capable of, configured to, or operable to support a means for determining that a subset of POs from the set of full-duplex POs are invalid based on the subset of POs being positioned within non-full-duplex slots and in accordance with a second validity rule.
  • the set of full-duplex POs include a first subset of full-duplex POs within the one or more full-duplex slots, and a second subset of full-duplex POs that overlap in a time domain with the set of common POs within the one or more second half-duplex uplink slots.
  • the set of multiple common ROs are associated with a set of multiple preambles .
  • the set of multiple preambles are mapped to the set of common POs and the set of full-duplex POs such that temporally overlapping pairs of POs are associated with one or more common preambles of the set of multiple preambles.
  • each temporally overlapping pair of POs include one of the second subset of full-duplex POs and one of the set of common POs.
  • the set of full-duplex POs include SBFD POs.
  • the one or more full-duplex slots include one or more SBFD slots.
  • the first PUSCH configuration indicates a first starting resource block frequency configuration associated with the set of common POs.
  • the second PUSCH configuration indicates a second starting resource block frequency configuration associated with the set of full-duplex POs.
  • the first PUSCH configuration indicates a first quantity of frequency-division multiplexed POs associated with the set of common POs within the one or more second half-duplex uplink slots.
  • the second PUSCH configuration indicates a second quantity of frequency-division multiplexed POs associated with the set of full-duplex POs within the one or more full-duplex slots.
  • the set of multiple common ROs and the set of common POs are usable by full-duplex-aware UEs and non-full-duplex-aware UEs.
  • the set of full-duplex POs are usable by full-duplex-aware UEs but unusable by non-full-duplex-aware UEs.
  • control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots.
  • control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, an PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple POs associated with the set of common ROs and the set of full-duplex ROs, the set of multiple POs including a set of common POs within one or more additional half-duplex uplink slots.
  • the preamble receiving manager 1530 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO of the set of full-duplex ROs.
  • the payload receiving manager 1535 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity via a common PO of the set of common POs that maps to the common RO or the full-duplex RO that was used to receive the preamble.
  • the RACH procedure manager 1540 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
  • the first half-duplex uplink slot including the set of common ROs includes a PRACH slot.
  • the PUSCH configuration includes a first time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common POs, and a second time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common POs.
  • control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of common ROs and the set of common POs, and a second mapping configuration between the set of multiple preambles of the set of full-duplex ROs and the set of common POs.
  • the RO identification manager 1555 is capable of, configured to, or operable to support a means for identifying one of the common RO or the full-duplex RO based on a relative timing of the common RO and the full-duplex RO in a time domain, one or more measured or predicted signal quality metrics associated with slots that include the common RO and the full-duplex RO, a PUSCH Tx power relative to a Tx power threshold associated with the one or more full-duplex slots, an RRC configuration, a type of UE, or any combination thereof, where the preamble of the first message of the two-step random access procedure is received via the identified one of the common RO or the full-duplex RO.
  • the validity manager 1550 is capable of, configured to, or operable to support a means for determining a validity of each full-duplex RO within the set of full-duplex ROs based on a type of slot corresponding to each of the set of full-duplex ROs, the type of slot including a full-duplex slot type or a half-duplex slot type.
  • the validity manager 1550 is capable of, configured to, or operable to support a means for determining that each full-duplex RO of the set of full-duplex ROs is valid regardless of the type of slot in accordance with a first validity rule. In some examples, to support determining the validity of each full-duplex RO, the validity manager 1550 is capable of, configured to, or operable to support a means for determining that a subset of ROs from the set of full-duplex ROs are invalid based on the subset of ROs being positioned within non-full-duplex slots and in accordance with a second validity rule.
  • control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots.
  • control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or additional more full-duplex slots, where the set of common ROs are mapped to the set of common POs, and where the set of full-duplex ROs mapped to the set of full-duplex POs.
  • the preamble receiving manager 1530 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO from the set of full-duplex ROs.
  • the payload receiving manager 1535 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that maps to the common RO based on transmitting the preamble via the common RO, or via a full-duplex PO from the set of full-duplex POs that maps to the common RO used to receive the preamble based on receiving the preamble via the full-duplex RO.
  • control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of common ROs and the set of common POs, and a second mapping configuration between the set of multiple preambles of the set of full-duplex ROs and the set of full-duplex POs.
  • control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, the second control signaling, or both, a third mapping configuration between the set of multiple preambles of set of common ROs and the set of full-duplex POs, a fourth mapping configuration between the set of multiple preambles of the set of full-duplex ROs and the set of common POs, or both.
  • the set of full-duplex ROs include SBFD ROs.
  • the set of full-duplex POs include SBFD POs.
  • the one or more full-duplex slots, the one or more additional full-duplex slots, or both include one or more SBFD slots.
  • control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, the second control signaling, or both, an indication that the first RACH configuration, second RACH configuration, the first PUSCH configuration, the second PUSCH configuration, or any combination thereof, are usable for performing random access procedures associated with SI requests, physical downlink control channel ordering, BFR, mobility, or any combination thereof.
  • control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, the second control signaling, or both, an indication that the second RACH configuration, the second PUSCH configuration, or both, include UE-specific configurations or cell-specific configurations.
  • FIG. 16 shows a diagram of a system 1600 including a device 1605 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • the device 1605 may be an example of or include components of a device 1305, a device 1405, or a network entity 105 as described herein.
  • the device 1605 may communicate with other network devices or network equipment such as one or more of the network entities 105, UEs 115, or any combination thereof.
  • the communications may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof.
  • the device 1605 may include components that support outputting and obtaining communications, such as a communications manager 1620, a transceiver 1610, one or more antennas 1615, at least one memory 1625, code 1630, and at least one processor 1635. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1640) .
  • a communications manager 1620 e.g., operatively, communicatively, functionally, electronically, electrically
  • buses e.g., a bus 1640
  • the transceiver 1610 may support bi-directional communications via wired links, wireless links, or both as described herein.
  • the transceiver 1610 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1610 may include a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the device 1605 may include one or more antennas 1615, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently) .
  • the transceiver 1610 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1615, by a wired transmitter) , to receive modulated signals (e.g., from one or more antennas 1615, from a wired receiver) , and to demodulate signals.
  • the transceiver 1610 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1615 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1615 that are configured to support various transmitting or outputting operations, or a combination thereof.
  • the transceiver 1610 may include or be configured for coupling with one or more processors or one or more memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof.
  • the transceiver 1610, or the transceiver 1610 and the one or more antennas 1615, or the transceiver 1610 and the one or more antennas 1615 and one or more processors or one or more memory components may be included in a chip or chip assembly that is installed in the device 1605.
  • the transceiver 1610 may be operable to support communications via one or more communications links (e.g., communication link (s) 125, backhaul communication link (s) 120, a midhaul communication link 162, a fronthaul communication link 168) .
  • communications links e.g., communication link (s) 125, backhaul communication link (s) 120, a midhaul communication link 162, a fronthaul communication link 168) .
  • the at least one memory 1625 may include RAM, ROM, or any combination thereof.
  • the at least one memory 1625 may store computer-readable, computer-executable, or processor-executable code, such as the code 1630.
  • the code 1630 may include instructions that, when executed by one or more of the at least one processor 1635, cause the device 1605 to perform various functions described herein.
  • the code 1630 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1630 may not be directly executable by a processor of the at least one processor 1635 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the at least one memory 1625 may include, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • the at least one processor 1635 may include multiple processors and the at least one memory 1625 may include multiple memories.
  • One or more of the multiple processors may be coupled with one or more of the multiple memories which may, individually or collectively, be configured to perform various functions herein (for example, as part of a processing system) .
  • the at least one processor 1635 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs) , one or more graphics processing units (GPUs) , one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs) ) , one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof) .
  • the at least one processor 1635 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into one or more of the at least one processor 1635.
  • the at least one processor 1635 may be configured to execute computer-readable instructions stored in a memory (e.g., one or more of the at least one memory 1625) to cause the device 1605 to perform various functions (e.g., functions or tasks supporting techniques for two-step random access procedures using dedicated SBFD resources) .
  • the device 1605 or a component of the device 1605 may include at least one processor 1635 and at least one memory 1625 coupled with one or more of the at least one processor 1635, the at least one processor 1635 and the at least one memory 1625 configured to perform various functions described herein.
  • the at least one processor 1635 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1630) to perform the functions of the device 1605.
  • the at least one processor 1635 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1605 (such as within one or more of the at least one memory 1625) .
  • the at least one processor 1635 may include multiple processors and the at least one memory 1625 may include multiple memories.
  • the at least one processor 1635 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1635) and memory circuitry (which may include the at least one memory 1625) ) , or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs.
  • the processing system may be configured to perform one or more of the functions described herein.
  • the at least one processor 1635 or a processing system including the at least one processor 1635 may be configured to, configurable to, or operable to cause the device 1605 to perform one or more of the functions described herein.
  • being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 1625 or otherwise, to perform one or more of the functions described herein.
  • a bus 1640 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1640 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack) , which may include communications performed within a component of the device 1605, or between different components of the device 1605 that may be co-located or located in different locations (e.g., where the device 1605 may refer to a system in which one or more of the communications manager 1620, the transceiver 1610, the at least one memory 1625, the code 1630, and the at least one processor 1635 may be located in one of the different components or divided between different components) .
  • the communications manager 1620 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links) .
  • the communications manager 1620 may manage the transfer of data communications for client devices, such as one or more UEs 115.
  • the communications manager 1620 may manage communications with one or more other network devices, and may include a controller or scheduler for controlling communications with UEs 115 (e.g., in cooperation with the one or more other network devices) .
  • the communications manager 1620 may support an X2 interface within an LTE/LTE-A wireless communications network technology to provide communication between network entities 105.
  • the communications manager 1620 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a RACH configuration including a set of multiple common ROs within a first half-duplex uplink slot.
  • the communications manager 1620 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or more full-duplex slots.
  • the communications manager 1620 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity via a common RO of the set of multiple common ROs.
  • the communications manager 1620 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that is associated with the common RO, or via a full-duplex PO from the set of full-duplex POs that is associated with the common RO used to receive the preamble.
  • the communications manager 1620 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
  • the communications manager 1620 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots.
  • the communications manager 1620 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, an PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple POs associated with the set of common ROs and the set of full-duplex ROs, the set of multiple POs including a set of common POs within one or more additional half-duplex uplink slots.
  • the communications manager 1620 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO of the set of full-duplex ROs.
  • the communications manager 1620 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity via a common PO of the set of common POs that maps to the common RO or the full-duplex RO that was used to receive the preamble.
  • the communications manager 1620 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
  • the communications manager 1620 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots.
  • the communications manager 1620 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or additional more full-duplex slots, where the set of common ROs are mapped to the set of common POs, and where the set of full-duplex ROs mapped to the set of full-duplex POs.
  • the communications manager 1620 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO from the set of full-duplex ROs.
  • the communications manager 1620 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that maps to the common RO based on transmitting the preamble via the common RO, or via a full-duplex PO from the set of full-duplex POs that maps to the common RO used to receive the preamble based on receiving the preamble via the full-duplex RO.
  • the communications manager 1620 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
  • the device 1605 may support signaling and configurations that facilitate faster and more efficient RACH procedures (e.g., two-step RACH procedures) .
  • RACH procedures e.g., two-step RACH procedures
  • techniques described herein may reduce a latency of two-step RACH procedures, and alleviate congestion/collisions within conventional RACH procedure resources within half-duplex slots.
  • the communications manager 1620 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1610, the one or more antennas 1615 (e.g., where applicable) , or any combination thereof.
  • the communications manager 1620 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1620 may be supported by or performed by the transceiver 1610, one or more of the at least one processor 1635, one or more of the at least one memory 1625, the code 1630, or any combination thereof (for example, by a processing system including at least a portion of the at least one processor 1635, the at least one memory 1625, the code 1630, or any combination thereof) .
  • the code 1630 may include instructions executable by one or more of the at least one processor 1635 to cause the device 1605 to perform various aspects of techniques for two-step random access procedures using dedicated SBFD resources as described herein, or the at least one processor 1635 and the at least one memory 1625 may be otherwise configured to, individually or collectively, perform or support such operations.
  • FIG. 17 shows a flowchart illustrating a method 1700 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1700 may be implemented by a UE or its components as described herein.
  • the operations of the method 1700 may be performed by a UE 115 as described with reference to FIGs. 1 through 12.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a RACH configuration including a set of multiple common ROs within a first half-duplex uplink slot.
  • the operations of 1705 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed by a control signaling receiving manager 1125 as described with reference to FIG. 11.
  • the method may include receiving, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or more full-duplex slots.
  • the operations of 1710 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed by a control signaling receiving manager 1125 as described with reference to FIG. 11.
  • the method may include transmitting a preamble of a first message of the two-step random access procedure to the network entity via a common RO of the set of multiple common ROs.
  • the operations of 1715 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed by a preamble transmitting manager 1130 as described with reference to FIG. 11.
  • the method may include transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that is associated with the common RO, or via a full-duplex PO from the set of full-duplex POs that is associated with the common RO used to transmit the preamble.
  • the operations of 1720 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed by a payload transmitting manager 1135 as described with reference to FIG. 11.
  • the method may include receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
  • the operations of 1725 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1725 may be performed by a RACH procedure manager 1140 as described with reference to FIG. 11.
  • FIG. 18 shows a flowchart illustrating a method 1800 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1800 may be implemented by a UE or its components as described herein.
  • the operations of the method 1800 may be performed by a UE 115 as described with reference to FIGs. 1 through 12.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots.
  • the operations of 1805 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed by a control signaling receiving manager 1125 as described with reference to FIG. 11.
  • the method may include receiving, via the first control signaling, second control signaling, or both, an PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple POs associated with the set of common ROs and the set of full-duplex ROs, the set of multiple POs including a set of common POs within one or more additional half-duplex uplink slots.
  • the operations of 1810 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed by a control signaling receiving manager 1125 as described with reference to FIG. 11.
  • the method may include transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO of the set of full-duplex ROs.
  • the operations of 1815 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed by a preamble transmitting manager 1130 as described with reference to FIG. 11.
  • the method may include transmitting a payload of the first message of the two-step random access procedure to the network entity via a common PO of the set of common POs that maps to the common RO or the full-duplex RO that was used to transmit the preamble.
  • the operations of 1820 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed by a payload transmitting manager 1135 as described with reference to FIG. 11.
  • the method may include receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
  • the operations of 1825 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1825 may be performed by a RACH procedure manager 1140 as described with reference to FIG. 11.
  • FIG. 19 shows a flowchart illustrating a method 1900 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1900 may be implemented by a UE or its components as described herein.
  • the operations of the method 1900 may be performed by a UE 115 as described with reference to FIGs. 1 through 12.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots.
  • the operations of 1905 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed by a control signaling receiving manager 1125 as described with reference to FIG. 11.
  • the method may include receiving, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or additional more full-duplex slots, where the set of common ROs are mapped to the set of common POs, and where the set of full-duplex ROs mapped to the set of full-duplex POs.
  • the operations of 1910 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed by a control signaling receiving manager 1125 as described with reference to FIG. 11.
  • the method may include transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO from the set of full-duplex ROs.
  • the operations of 1915 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed by a preamble transmitting manager 1130 as described with reference to FIG. 11.
  • the method may include transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that maps to the common RO based on transmitting the preamble via the common RO, or via a full-duplex PO from the set of full-duplex POs that maps to the common RO used to transmit the preamble based on transmitting the preamble via the full-duplex RO.
  • the operations of 1920 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1920 may be performed by a payload transmitting manager 1135 as described with reference to FIG. 11.
  • the method may include receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
  • the operations of 1925 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1925 may be performed by a RACH procedure manager 1140 as described with reference to FIG. 11.
  • a method for wireless communications at a UE comprising: receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, wherein the random access configuration is associated with a RACH configuration comprising a plurality of common RACH occasions within a first half-duplex uplink slot; receiving, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration comprising a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration comprising a set of full-duplex PUSCH occasions within one or more full-duplex slots; transmitting a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the plurality of common RACH occasions; transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common
  • Aspect 2 The method of aspect 1, wherein the plurality of common RACH occasions are associated with a plurality of preambles, the method further comprising: receiving, via the first control signaling, the second control signaling, or both, a first mapping configuration between the plurality of preambles of the plurality of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the plurality of preambles of the plurality of common RACH occasions and the set of full-duplex PUSCH occasions; and selecting one of the common PUSCH occasion or the full-duplex PUSCH occasion that maps to the common RACH occasion used to transmit the preamble in accordance with the first mapping configuration or the second mapping configuration, wherein the payload of the first message is transmitted via the selected one of the common PUSCH occasion or the full-duplex PUSCH occasion.
  • Aspect 3 The method of any of aspects 1 through 2, wherein each common RACH occasion from the plurality of common RACH occasions is mapped to a plurality of full-duplex PUSCH occasions from the set of full-duplex PUSCH occasions.
  • Aspect 4 The method of any of aspects 1 through 3, wherein the second PUSCH configuration comprises a first sub-configuration associated with a first preamble group comprising the set of full-duplex PUSCH occasions, and a second sub-configuration associated with a second preamble group comprising an additional set of full-duplex PUSCH occasions.
  • Aspect 5 The method of any of aspects 1 through 4, further comprising: selecting one of the common PUSCH occasion or the full-duplex PUSCH occasion that maps to the common RACH occasion based at least in part on a relative timing of the common PUSCH occasion and the full-duplex PUSCH occasion in a time domain, one or more measured or predicted downlink signal quality metrics associated with slots that include the common PUSCH occasion and the full-duplex PUSCH occasion, a radio resource control configuration, a PUSCH transmission power relative to a transmission power threshold associated with the one or more full-duplex slots, a type of UE, or any combination thereof, wherein the payload of the first message of the two-step random access procedure is transmitted via the selected one of the common PUSCH occasion or the full-duplex PUSCH occasion.
  • Aspect 6 The method of any of aspects 1 through 5, further comprising: determining a validity of each full-duplex PUSCH occasion within the set of full-duplex PUSCH occasions based at least in part on a type of slot corresponding to each of the set of full-duplex PUSCH occasions, the type of slot comprising a full-duplex slot type or a half-duplex slot type.
  • Aspect 7 The method of aspect 6, wherein determining the validity of each full-duplex PUSCH occasion comprises: determining that each full-duplex PUSCH occasion of the set of full-duplex PUSCH occasions is valid regardless of the type of slot in accordance with a first validity rule; or determining that a subset of PUSCH occasions from the set of full-duplex PUSCH occasions are invalid based at least in part on the subset of PUSCH occasions being positioned within non-full-duplex slots and in accordance with a second validity rule.
  • Aspect 8 The method of any of aspects 1 through 7, wherein the set of full-duplex PUSCH occasions comprise a first subset of full-duplex PUSCH occasions within the one or more full-duplex slots, and a second subset of full-duplex PUSCH occasions that overlap in a time domain with the set of common PUSCH occasions within the one or more second half-duplex uplink slots, and the plurality of common RACH occasions are associated with a plurality of preambles , the plurality of preambles are mapped to the set of common PUSCH occasions and the set of full-duplex PUSCH occasions such that temporally overlapping pairs of PUSCH occasions are associated with one or more common preambles of the plurality of preambles, each temporally overlapping pair of PUSCH occasions comprise one of the second subset of full-duplex PUSCH occasions and one of the set of common PUSCH occasions.
  • Aspect 9 The method of any of aspects 1 through 8, further comprising: monitoring a plurality of synchronization signal blocks, the plurality of synchronization signal blocks corresponding with the plurality of common RACH occasions; and selecting the common RACH occasion from the plurality of common RACH occasions based at least in part on the monitoring.
  • Aspect 10 The method of any of aspects 1 through 9, wherein the set of full-duplex PUSCH occasions comprise SBFD PUSCH occasions, and the one or more full-duplex slots comprise one or more SBFD slots.
  • Aspect 11 The method of any of aspects 1 through 10, wherein the first PUSCH configuration indicates a first starting resource block frequency configuration associated with the set of common PUSCH occasions, and the second PUSCH configuration indicates a second starting resource block frequency configuration associated with the set of full-duplex PUSCH occasions.
  • Aspect 12 The method of any of aspects 1 through 11, wherein the first PUSCH configuration indicates a first quantity of frequency-division multiplexed PUSCH occasions associated with the set of common PUSCH occasions within the one or more second half-duplex uplink slots, and the second PUSCH configuration indicates a second quantity of frequency-division multiplexed PUSCH occasions associated with the set of full-duplex PUSCH occasions within the one or more full-duplex slots.
  • Aspect 13 The method of any of aspects 1 through 12, wherein the plurality of common RACH occasions and the set of common PUSCH occasions are usable by full-duplex-aware UEs and non-full-duplex-aware UEs, and the set of full-duplex PUSCH occasions are usable by full-duplex-aware UEs but unusable by non-full-duplex-aware UEs.
  • a method for wireless communications at a UE comprising: receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, wherein the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration comprising a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration comprising a set of full-duplex RACH occasions within one or more full-duplex slots; receiving, via the first control signaling, second control signaling, or both, a PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration comprising a plurality of PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the plurality of PUSCH occasions comprising a set of common PUSCH occasions within one or more additional half-duplex uplink slots; transmitting a preamble of a first message of the two-step random access procedure to the network entity either via
  • Aspect 15 The method of aspect 14, wherein the first half-duplex uplink slot including the set of common RACH occasions comprises a PRACH slot, the PUSCH configuration comprises a first time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common PUSCH occasions, and a second time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common PUSCH occasions.
  • Aspect 16 The method of any of aspects 14 through 15, wherein the set of common RACH occasions and the set of full-duplex RACH occasions are associated with a plurality of preambles, the method further comprising: receiving, via the first control signaling, the second control signaling, or both, a first mapping configuration between the plurality of preambles of the set of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the plurality of preambles of the set of full-duplex RACH occasions and the set of common PUSCH occasions.
  • Aspect 17 The method of any of aspects 14 through 16, wherein each common PUSCH occasion from the set of common PUSCH occasions is mapped to at least one common RACH occasion from the set of common RACH occasions and at least one full-duplex RACH occasion from the set of full-duplex RACH occasions.
  • Aspect 18 The method of any of aspects 14 through 17, further comprising: selecting one of the common RACH occasion or the full-duplex RACH occasion based at least in part on a relative timing of the common RACH occasion and the full-duplex RACH occasion in a time domain, one or more measured or predicted signal quality metrics associated with slots that include the common RACH occasion and the full-duplex RACH occasion, a PUSCH transmission power relative to a transmission power threshold associated with the one or more full-duplex slots, a radio resource control configuration, a type of UE, or any combination thereof, wherein the preamble of the first message of the two-step random access procedure is transmitted via the selected one of the common RACH occasion or the full-duplex RACH occasion.
  • Aspect 19 The method of any of aspects 14 through 18, further comprising: determining a validity of each full-duplex RACH occasion within the set of full-duplex RACH occasions based at least in part on a type of slot corresponding to each of the set of full-duplex RACH occasions, the type of slot comprising a full-duplex slot type or a half-duplex slot type.
  • Aspect 20 The method of aspect 19, wherein determining the validity of each full-duplex RACH occasion comprises: determining that each full-duplex RACH occasion of the set of full-duplex RACH occasions is valid regardless of the type of slot in accordance with a first validity rule; or determining that a subset of RACH occasions from the set of full-duplex RACH occasions are invalid based at least in part on the subset of RACH occasions being positioned within non-full-duplex slots and in accordance with a second validity rule.
  • Aspect 21 The method of any of aspects 14 through 20, wherein the set of full-duplex RACH occasions comprise a first subset of full-duplex RACH occasions within the one or more full-duplex slots, and a second subset of full-duplex RACH occasions that overlap in a time domain with the set of common RACH occasions within the first half-duplex uplink slot, and the set of common RACH occasions and the set of full-duplex RACH occasions are associated with a plurality of preambles such that temporally overlapping pairs of RACH occasions map to one or more common preambles of the plurality of preambles, each temporally overlapping pair of RACH occasions comprise one of the second subset of full-duplex RACH occasions and one of the set of common RACH occasions.
  • Aspect 22 The method of any of aspects 14 through 21, wherein the set of full-duplex RACH occasions comprise SBFD RACH occasions, and the one or more full-duplex slots comprise one or more SBFD slots.
  • a method for wireless communications at a UE comprising: receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, wherein the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration comprising a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration comprising a set of full-duplex RACH occasions within one or more full-duplex slots; receiving, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration comprising a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration comprising a set of full-duplex PUSCH occasions within one or additional more full-duplex slots, wherein the set of common RACH occasions are mapped to the set of common PUSCH occasions, and wherein the set of common RACH
  • Aspect 24 The method of aspect 23, , wherein the set of common RACH occasions and the set of full-duplex RACH occasions are associated with a plurality of preambles, the method further comprising: receiving, via the first control signaling, the second control signaling, or both, a first mapping configuration between the plurality of preambles of the set of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the plurality of preambles of the set of full-duplex RACH occasions and the set of full-duplex PUSCH occasions.
  • Aspect 25 The method of aspect 24, further comprising: receiving, via the first control signaling, the second control signaling, or both, a third mapping configuration between the plurality of preambles of set of common RACH occasions and the set of full-duplex PUSCH occasions, a fourth mapping configuration between the plurality of preambles of the set of full-duplex RACH occasions and the set of common PUSCH occasions, or both.
  • Aspect 26 The method of any of aspects 23 through 25, wherein the set of full-duplex RACH occasions comprise SBFD RACH occasions, and the set of full-duplex PUSCH occasions comprise SBFD PUSCH occasions, the one or more full-duplex slots, the one or more additional full-duplex slots, or both, comprise one or more SBFD slots.
  • Aspect 27 The method of any of aspects 23 through 26, further comprising: receiving, via the first control signaling, the second control signaling, or both, an indication that the first RACH configuration, second RACH configuration, the first PUSCH configuration, the second PUSCH configuration, or any combination thereof, are usable for performing random access procedures associated with system information requests, physical downlink control channel ordering, beam failure recovery, mobility, or any combination thereof.
  • Aspect 28 The method of any of aspects 23 through 27, further comprising: receiving, via the first control signaling, the second control signaling, or both, an indication that the second RACH configuration, the second PUSCH configuration, or both, comprise UE-specific configurations or cell-specific configurations.
  • Aspect 29 The method of any of aspects 23 through 28, further comprising: receiving, via the first control signaling, the second control signaling, third control signaling, or any combination thereof, a common random access configuration associated with one or more operations different from the two-step random access procedure; and performing the one or more operations in accordance with either the common random access configuration, or in accordance with the second RACH configuration and the second PUSCH configuration.
  • Aspect 30 The method of any of aspects 23 through 29, further comprising: determining that the UE has not been configured with a common random access configuration associated with one or more operations different from the two-step random access procedure; and performing the one or more operations in accordance with the first RACH configuration and the first PUSCH configuration, or in accordance with the second RACH configuration and the second PUSCH configuration.
  • a method for wireless communications at a network entity comprising: transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, wherein the random access configuration is associated with a RACH configuration comprising a plurality of common RACH occasions within a first half-duplex uplink slot; transmitting, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration comprising a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration comprising a set of full-duplex PUSCH occasions within one or more full-duplex slots; receiving a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the plurality of common RACH occasions; receiving a payload of the first message of the two-step random access procedure to the network entity either
  • Aspect 32 The method of aspect 31, wherein the plurality of common RACH occasions are associated with a plurality of preambles, the method further comprising: transmitting, via the first control signaling, the second control signaling, or both, a first mapping configuration between the plurality of preambles of the plurality of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the plurality of preambles of the plurality of common RACH occasions and the set of full-duplex PUSCH occasions; and identifying one of the common PUSCH occasion or the full-duplex PUSCH occasion that maps to the common RACH occasion used to transmit the preamble in accordance with the first mapping configuration or the second mapping configuration, wherein the payload of the first message is received via the identified one of the common PUSCH occasion or the full-duplex PUSCH occasion.
  • Aspect 33 The method of any of aspects 31 through 32, wherein each common RACH occasion from the plurality of common RACH occasions is mapped to a plurality of full-duplex PUSCH occasions from the set of full-duplex PUSCH occasions.
  • Aspect 34 The method of any of aspects 31 through 33, wherein the second PUSCH configuration comprises a first sub-configuration associated with a first preamble group comprising the set of full-duplex PUSCH occasions, and a second sub-configuration associated with a second preamble group comprising an additional set of full-duplex PUSCH occasions.
  • Aspect 35 The method of any of aspects 31 through 34, further comprising: identifying one of the common PUSCH occasion or the full-duplex PUSCH occasion that maps to the common RACH occasion based at least in part on a relative timing of the common PUSCH occasion and the full-duplex PUSCH occasion in a time domain, one or more measured or predicted downlink signal quality metrics associated with slots that include the common PUSCH occasion and the full-duplex PUSCH occasion, a radio resource control configuration, a PUSCH transmission power relative to a transmission power threshold associated with the one or more full-duplex slots, a type of UE, or any combination thereof, wherein the payload of the first message of the two-step random access procedure is received via the identified one of the common PUSCH occasion or the full-duplex PUSCH occasion.
  • Aspect 36 The method of any of aspects 31 through 35, further comprising: determining a validity of each full-duplex PUSCH occasion within the set of full-duplex PUSCH occasions based at least in part on a type of slot corresponding to each of the set of full-duplex PUSCH occasions, the type of slot comprising a full-duplex slot type or a half-duplex slot type.
  • Aspect 37 The method of aspect 36, wherein determining the validity of each full-duplex PUSCH occasion comprises: determining that each full-duplex PUSCH occasion of the set of full-duplex PUSCH occasions is valid regardless of the type of slot in accordance with a first validity rule; or determining that a subset of PUSCH occasions from the set of full-duplex PUSCH occasions are invalid based at least in part on the subset of PUSCH occasions being positioned within non-full-duplex slots and in accordance with a second validity rule.
  • Aspect 38 The method of any of aspects 31 through 37, wherein the set of full-duplex PUSCH occasions comprise a first subset of full-duplex PUSCH occasions within the one or more full-duplex slots, and a second subset of full-duplex PUSCH occasions that overlap in a time domain with the set of common PUSCH occasions within the one or more second half-duplex uplink slots, and the plurality of common RACH occasions are associated with a plurality of preambles , the plurality of preambles are mapped to the set of common PUSCH occasions and the set of full-duplex PUSCH occasions such that temporally overlapping pairs of PUSCH occasions are associated with one or more common preambles of the plurality of preambles, each temporally overlapping pair of PUSCH occasions comprise one of the second subset of full-duplex PUSCH occasions and one of the set of common PUSCH occasions,
  • Aspect 39 The method of any of aspects 31 through 38, wherein the set of full-duplex PUSCH occasions comprise SBFD PUSCH occasions, and the one or more full-duplex slots comprise one or more SBFD slots.
  • Aspect 40 The method of any of aspects 31 through 39, wherein the first PUSCH configuration indicates a first starting resource block frequency configuration associated with the set of common PUSCH occasions, and the second PUSCH configuration indicates a second starting resource block frequency configuration associated with the set of full-duplex PUSCH occasions.
  • Aspect 41 The method of any of aspects 31 through 40, wherein the first PUSCH configuration indicates a first quantity of frequency-division multiplexed PUSCH occasions associated with the set of common PUSCH occasions within the one or more second half-duplex uplink slots, and the second PUSCH configuration indicates a second quantity of frequency-division multiplexed PUSCH occasions associated with the set of full-duplex PUSCH occasions within the one or more full-duplex slots.
  • Aspect 42 The method of any of aspects 31 through 41, wherein the plurality of common RACH occasions and the set of common PUSCH occasions are usable by full-duplex-aware UEs and non-full-duplex-aware UEs, and the set of full-duplex PUSCH occasions are usable by full-duplex-aware UEs but unusable by non-full-duplex-aware UEs.
  • a method for wireless communications at a network entity comprising: transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, wherein the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration comprising a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration comprising a set of full-duplex RACH occasions within one or more full-duplex slots; transmitting, via the first control signaling, second control signaling, or both, a PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration comprising a plurality of PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the plurality of PUSCH occasions comprising a set of common PUSCH occasions within one or more additional half-duplex uplink slots; receiving a preamble of a first message of the two-step random access procedure to the
  • Aspect 44 The method of aspect 43, wherein the first half-duplex uplink slot including the set of common RACH occasions comprises a PRACH slot, the PUSCH configuration comprises a first time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common PUSCH occasions, and a second time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common PUSCH occasions.
  • Aspect 45 The method of any of aspects 43 through 44, wherein the set of common RACH occasions and the set of full-duplex RACH occasions are associated with a plurality of preambles, the method further comprising: transmitting, via the first control signaling, the second control signaling, or both, a first mapping configuration between the plurality of preambles of the set of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the plurality of preambles of the set of full-duplex RACH occasions and the set of common PUSCH occasions.
  • Aspect 46 The method of any of aspects 43 through 45, wherein each common PUSCH occasion from the set of common PUSCH occasions is mapped to at least one common RACH occasion from the set of common RACH occasions and at least one full-duplex RACH occasion from the set of full-duplex RACH occasions.
  • Aspect 47 The method of any of aspects 43 through 46, further comprising: identifying one of the common RACH occasion or the full-duplex RACH occasion based at least in part on a relative timing of the common RACH occasion and the full-duplex RACH occasion in a time domain, one or more measured or predicted signal quality metrics associated with slots that include the common RACH occasion and the full-duplex RACH occasion, a PUSCH transmission power relative to a transmission power threshold associated with the one or more full-duplex slots, a radio resource control configuration, a type of UE, or any combination thereof, wherein the preamble of the first message of the two-step random access procedure is received via the identified one of the common RACH occasion or the full-duplex RACH occasion.
  • Aspect 48 The method of any of aspects 43 through 47, further comprising: determining a validity of each full-duplex RACH occasion within the set of full-duplex RACH occasions based at least in part on a type of slot corresponding to each of the set of full-duplex RACH occasions, the type of slot comprising a full-duplex slot type or a half-duplex slot type.
  • Aspect 49 The method of aspect 48, wherein determining the validity of each full-duplex RACH occasion comprises: determining that each full-duplex RACH occasion of the set of full-duplex RACH occasions is valid regardless of the type of slot in accordance with a first validity rule; or determining that a subset of RACH occasions from the set of full-duplex RACH occasions are invalid based at least in part on the subset of RACH occasions being positioned within non-full-duplex slots and in accordance with a second validity rule.
  • Aspect 50 The method of any of aspects 43 through 49, wherein the set of full-duplex RACH occasions comprise a first subset of full-duplex RACH occasions within the one or more full-duplex slots, and a second subset of full-duplex RACH occasions that overlap in a time domain with the set of common RACH occasions within the first half-duplex uplink slot, and the set of common RACH occasions and the set of full-duplex RACH occasions are associated with a plurality of preambles such that temporally overlapping pairs of RACH occasions map to one or more common preambles of the plurality of preambles, each temporally overlapping pair of RACH occasions comprise one of the second subset of full-duplex RACH occasions and one of the set of common RACH occasions.
  • Aspect 51 The method of any of aspects 43 through 50, wherein the set of full-duplex RACH occasions comprise SBFD RACH occasions, and the one or more full-duplex slots comprise one or more SBFD slots.
  • a method for wireless communications at a network entity comprising: transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, wherein the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration comprising a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration comprising a set of full-duplex RACH occasions within one or more full-duplex slots; transmitting, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration comprising a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration comprising a set of full-duplex PUSCH occasions within one or additional more full-duplex slots, wherein the set of common RACH occasions are mapped to the set of common PUSCH occasions
  • Aspect 53 The method of aspect 52, wherein the set of common RACH occasions and the set of full-duplex RACH occasions are associated with a plurality of preambles, the method further comprising: transmitting, via the first control signaling, the second control signaling, or both, a first mapping configuration between the plurality of preambles of the set of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the plurality of preambles of the set of full-duplex RACH occasions and the set of full-duplex PUSCH occasions.
  • Aspect 54 The method of any of aspects 52 through 53, further comprising: transmitting, via the first control signaling, the second control signaling, or both, a third mapping configuration between the plurality of preambles of set of common RACH occasions and the set of full-duplex PUSCH occasions, a fourth mapping configuration between the plurality of preambles of the set of full-duplex RACH occasions and the set of common PUSCH occasions, or both.
  • Aspect 55 The method of any of aspects 52 through 54, wherein the set of full-duplex RACH occasions comprise SBFD RACH occasions, and the set of full-duplex PUSCH occasions comprise SBFD PUSCH occasions, the one or more full-duplex slots, the one or more additional full-duplex slots, or both, comprise one or more SBFD slots.
  • Aspect 56 The method of any of aspects 52 through 55, further comprising: transmitting, via the first control signaling, the second control signaling, or both, an indication that the first RACH configuration, second RACH configuration, the first PUSCH configuration, the second PUSCH configuration, or any combination thereof, are usable for performing random access procedures associated with system information requests, physical downlink control channel ordering, beam failure recovery, mobility, or any combination thereof.
  • Aspect 57 The method of any of aspects 52 through 56, further comprising: transmitting, via the first control signaling, the second control signaling, or both, an indication that the second RACH configuration, the second PUSCH configuration, or both, comprise UE-specific configurations or cell-specific configurations.
  • a UE comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 1 through 13.
  • a UE comprising at least one means for performing a method of any of aspects 1 through 13.
  • Aspect 60 A non-transitory computer-readable medium storing code the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 13.
  • a UE comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 14 through 22.
  • a UE comprising at least one means for performing a method of any of aspects 14 through 22.
  • Aspect 63 A non-transitory computer-readable medium storing code the code comprising instructions executable by one or more processors to perform a method of any of aspects 14 through 22.
  • a UE comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 23 through 30.
  • a UE comprising at least one means for performing a method of any of aspects 23 through 30.
  • Aspect 66 A non-transitory computer-readable medium storing code the code comprising instructions executable by one or more processors to perform a method of any of aspects 23 through 30.
  • a network entity comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method of any of aspects 31 through 42.
  • a network entity comprising at least one means for performing a method of any of aspects 31 through 42.
  • Aspect 69 A non-transitory computer-readable medium storing code the code comprising instructions executable by one or more processors to perform a method of any of aspects 31 through 42.
  • a network entity comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method of any of aspects 43 through 51.
  • a network entity comprising at least one means for performing a method of any of aspects 43 through 51.
  • Aspect 72 A non-transitory computer-readable medium storing code the code comprising instructions executable by one or more processors to perform a method of any of aspects 43 through 51.
  • a network entity comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method of any of aspects 52 through 57.
  • a network entity comprising at least one means for performing a method of any of aspects 52 through 57.
  • Aspect 75 A non-transitory computer-readable medium storing code the code comprising instructions executable by one or more processors to perform a method of any of aspects 52 through 57.
  • LTE, LTE-A, LTE-A Pro, or NR may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks.
  • the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.
  • UMB Ultra Mobile Broadband
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Institute of Electrical and Electronics Engineers
  • WiMAX IEEE 802.16
  • IEEE 802.20 Flash-OFDM
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • a general-purpose processor may be a microprocessor but, in the alternative, the processor may be any processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration) . Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.
  • the functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor.
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium.
  • Disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.
  • the article “a” before a noun is open-ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns.
  • the terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable.
  • a claim recites “a component” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components.
  • the term “a component” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function.
  • a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components.
  • a component introduced with the article “a” may be understood to mean “one or more components, ” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.
  • subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components.
  • referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ”
  • determining encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database, or another data structure) , ascertaining, and the like. Also, “determining” can include receiving (e.g., receiving information) , accessing (e.g., accessing data stored in memory) , and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

Landscapes

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

Abstract

Methods, systems, and devices for wireless communications are described. A user equipment (UE) may receive one or more random access channel (RACH) configurations and one or more physical uplink channel (PUSCH) configurations for performing a two-step RACH procedure with the network. The RACH configurations and PUSCH configurations may include common RACH occasions (ROs) and common PUSCH occasions (POs) within half-duplex slots usable by both legacy UEs and full-duplex UEs, as well as full-duplex ROs and full-duplex POs within full-duplex slots (e.g., sub-band full-duplex (SBFD) slots) usable only by full-duplex UEs. The UE may then perform a two-step RACH procedure using the common ROs or the full-duplex ROs, and using either the common POs or the full-duplex POs. The use of full-duplex ROs and full-duplex POs may enable signaling of the two-step RACH procedure to be performed within SBFD slots.

Description

TECHNIQUES FOR TWO-STEP RANDOM ACCESS PROCEDURES USING DEDICATED SUB-BAND FULL DUPLEX RESOURCES
FIELD OF TECHNOLOGY
The following relates to wireless communications, including techniques for two-step random access channel procedures using dedicated sub-band full-duplex (SBFD) resources.
BACKGROUND
Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) . Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems. These systems may employ technologies such as code division multiple access (CDMA) , time division multiple access (TDMA) , frequency division multiple access (FDMA) , orthogonal FDMA (OFDMA) , or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM) . A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE) .
Different networks may utilize different types of access procedures to enable wireless devices (e.g., UEs) to connect to and access the networks, such as four-step random access channel (RACH) procedures and two-step RACH procedures. However, current RACH procedures only utilize resources configured within legacy half-duplex slots. In other words, conventional RACH procedures have no mechanisms for utilizing full-duplex slots for transmitting MsgA, such as sub-band full-duplex (SBFD) uplink bands positioned within downlink slots.
SUMMARY
The described techniques relate to improved methods, systems, devices, and apparatuses that support techniques for two-step random access channel procedures using dedicated sub-band full-duplex (SBFD) resources. That is, aspects of the present disclosure are directed to signaling and configurations that utilize full-duplex slots (e.g., SBFD slots) to communicate messages associated with RACH procedures. In particular, aspects of the present disclosure are directed to RACH configurations that configure wireless devices with dedicated full-duplex RACH occasions (ROs) (e.g., SBFD ROs) and/or dedicated full-duplex physical uplink shared channel (PUSCH) occasions (POs) (e.g., SBFD POs) to enable the UEs to perform at least a portion of a first message (e.g., MsgA) of a two-step RACH procedure within full-duplex slots. As such, by enabling UEs to transmit RACH procedure signaling within full-duplex slots, techniques described herein may reduce a latency of two-step RACH procedures, and alleviate congestion/collisions within conventional RACH procedure resources within half-duplex slots.
A method by a UE is described. The method may include receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a RACH configuration including a set of multiple common RACH occasions within a first half-duplex uplink slot, receiving, via the first control signaling, second control signaling, or both, a first physical uplink shared channel (PUSCH) configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or more full-duplex slots, transmitting a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the set of multiple common RACH occasions, transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that is associated with the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that is associated with the common RACH occasion used to transmit the preamble, and receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
A UE is described. The UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the UE to receive, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a RACH configuration including a set of multiple common RACH occasions within a first half-duplex uplink slot, receive, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or more full-duplex slots, transmit a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the set of multiple common RACH occasions, transmit a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that is associated with the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that is associated with the common RACH occasion used to transmit the preamble, and receive, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
Another UE is described. The UE may include means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a RACH configuration including a set of multiple common RACH occasions within a first half-duplex uplink slot, means for receiving, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or more full-duplex slots, means for transmitting a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the set of multiple common RACH occasions, means for transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that is associated with the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that is associated with the common RACH occasion used to transmit the preamble, and means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
A non-transitory computer-readable medium storing code is described. The code may include instructions executable by one or more processors to receive, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a RACH configuration including a set of multiple common RACH occasions within a first half-duplex uplink slot, receive, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or more full-duplex slots, transmit a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the set of multiple common RACH occasions, transmit a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that is associated with the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that is associated with the common RACH occasion used to transmit the preamble, and receive, from the network entity, a second message of the two-step random access procedure based on  transmitting the preamble and the payload of the first message of the two-step random access procedure.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of multiple common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the set of multiple preambles of the set of multiple common RACH occasions and the set of full-duplex PUSCH occasions and selecting one of the common PUSCH occasion or the full-duplex PUSCH occasion that maps to the common RACH occasion used to transmit the preamble in accordance with the first mapping configuration or the second mapping configuration, where the payload of the first message may be transmitted via the selected one of the common PUSCH occasion or the full-duplex PUSCH occasion.
In some examples of the method, UEs, and non-transitory computer-readable medium described herein, each common RACH occasion from the set of multiple common RACH occasions may be mapped to a set of multiple full-duplex PUSCH occasions from the set of full-duplex PUSCH occasions.
In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the second PUSCH configuration includes a first sub-configuration associated with a first preamble group including the set of full-duplex PUSCH occasions, and a second sub-configuration associated with a second preamble group including an additional set of full-duplex PUSCH occasions.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for selecting one of the common PUSCH occasion or the full-duplex PUSCH occasion that maps to the common RACH occasion based on a relative timing of the common PUSCH occasion and the full-duplex PUSCH occasion in a time domain, one or more measured or predicted downlink signal quality metrics associated with slots that include the common PUSCH occasion and the full-duplex PUSCH occasion, a radio resource control configuration, a PUSCH transmission power relative to a transmission power threshold associated with the one or more full-duplex slots, a type of UE, or any combination thereof, where the payload of the first message of the two-step random access procedure may be transmitted via the selected one of the common PUSCH occasion or the full-duplex PUSCH occasion.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining a validity of each full-duplex PUSCH occasion within the set of full-duplex PUSCH occasions based on a type of slot corresponding to each of the set of full-duplex PUSCH occasions, the type of slot including a full-duplex slot type or a half-duplex slot type.
In some examples of the method, UEs, and non-transitory computer-readable medium described herein, determining the validity of each full-duplex PUSCH occasion may include operations, features, means, or instructions for determining that each full-duplex PUSCH occasion of the set of full-duplex PUSCH occasions may be valid regardless of the type of slot in accordance with a first validity rule and determining that a subset of PUSCH occasions from the set of full-duplex PUSCH occasions may be invalid based on the subset of PUSCH occasions being positioned within non-full-duplex slots and in accordance with a second validity rule.
In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the set of full-duplex PUSCH occasions include a first subset of full-duplex PUSCH occasions within the one or more full-duplex slots, and a second subset of full-duplex PUSCH occasions that overlap in a time domain with the set of common PUSCH occasions within the one or more second half-duplex uplink slots, the set of multiple common RACH occasions may be associated with a set of multiple preambles, the set of multiple preambles may be mapped to the set of common PUSCH occasions and the set of full-duplex PUSCH occasions such that temporally overlapping pairs of PUSCH occasions may be associated with one or more common preambles of the set of multiple preambles, and each temporally overlapping pair of PUSCH occasions include one of the second subset of full-duplex PUSCH occasions and one of the set of common PUSCH occasions.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for monitoring a set of multiple synchronization signal blocks, the set of multiple synchronization signal blocks corresponding with the set of multiple common RACH occasions and selecting the common RACH occasion from the set of multiple common RACH occasions based on the monitoring.
In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the set of full-duplex PUSCH occasions include SBFD PUSCH occasions and the one or more full-duplex slots include one or more SBFD slots.
In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the first PUSCH configuration indicates a first starting resource block frequency configuration associated with the set of common PUSCH occasions and the second PUSCH configuration indicates a second starting resource block frequency configuration associated with the set of full-duplex PUSCH occasions.
In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the first PUSCH configuration indicates a first quantity of frequency-division multiplexed PUSCH occasions associated with the set of common PUSCH occasions within the one or more second half-duplex uplink slots and the second PUSCH configuration indicates a second quantity of frequency-division multiplexed PUSCH occasions associated with the set of full-duplex PUSCH occasions within the one or more full-duplex slots.
In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the set of multiple common RACH occasions and the set of common PUSCH occasions may be usable by full-duplex-aware UEs and non-full-duplex-aware UEs and the set of full-duplex PUSCH occasions may be usable by full-duplex-aware UEs but unusable by non-full-duplex-aware UEs.
A method by a UE is described. The method may include receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, receiving, via the first control signaling, second control signaling, or both, a PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the set of multiple PUSCH occasions including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion of the set of full-duplex RACH occasions, transmitting a payload of the first message of the two-step random access procedure to the network entity via a common PUSCH occasion of the set of common PUSCH occasions that maps to the common RACH occasion or the full-duplex RACH occasion that was used to transmit the preamble, and receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
A UE is described. The UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the UE to receive, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, receive, via the first control signaling, second control signaling, or both, a PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the set of multiple PUSCH occasions including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, transmit a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion of the set of full-duplex RACH occasions, transmit a payload of the first message of the two-step random access procedure to the network entity via a common PUSCH occasion of the set of common PUSCH occasions that maps to the common RACH occasion or the full-duplex RACH occasion that was used to transmit the preamble, and receive, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
Another UE is described. The UE may include means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, means for receiving, via the first control signaling, second control signaling, or both, a PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the set of multiple PUSCH occasions including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, means for transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion of the set of full-duplex RACH occasions, means for transmitting a payload of the first message of the two-step random access procedure to the network entity via a common PUSCH occasion of the set of common PUSCH occasions that maps to the common RACH occasion or the full-duplex RACH occasion that was used to transmit the preamble, and means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
A non-transitory computer-readable medium storing code is described. The code may include instructions executable by one or more processors to receive, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, receive, via the first control signaling, second control signaling, or both, a PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the set of multiple PUSCH occasions including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, transmit a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion of the set of full-duplex RACH occasions, transmit a payload of the first message of the two-step random access procedure to the network entity via a common PUSCH occasion of the set of common PUSCH occasions that maps to the common RACH occasion or the full-duplex RACH occasion that was used to transmit the preamble, and receive, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the first half-duplex uplink slot including the set of common RACH occasions includes a PRACH slot and the PUSCH configuration includes a first time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common PUSCH occasions, and a second time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common PUSCH occasions.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the set of multiple preambles of the set of full-duplex RACH occasions and the set of common PUSCH occasions.
In some examples of the method, UEs, and non-transitory computer-readable medium described herein, each common PUSCH occasion from the set of common PUSCH occasions may be mapped to at least one common RACH occasion from the set of common RACH occasions and at least one full-duplex RACH occasion from the set of full-duplex RACH occasions.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for selecting one of the common RACH occasion or the full-duplex RACH occasion based on a relative timing of the common RACH occasion and the full-duplex RACH occasion in a time domain, one or more measured or predicted signal quality metrics associated with slots that include the common RACH occasion and the full-duplex RACH occasion, a PUSCH transmission power relative to a transmission power threshold associated with the one or more full-duplex slots, a radio resource control configuration, a type of UE, or any combination thereof, where the preamble of the first message of the two-step random access procedure may be transmitted via the selected one of the common RACH occasion or the full-duplex RACH occasion.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining a validity of each full-duplex RACH occasion within the set of full-duplex RACH occasions based on a type of slot corresponding to each of the set of full-duplex RACH occasions, the type of slot including a full-duplex slot type or a half-duplex slot type.
In some examples of the method, UEs, and non-transitory computer-readable medium described herein, determining the validity of each full-duplex RACH occasion may include operations, features, means, or instructions for determining that each full-duplex RACH occasion of the set of full-duplex RACH occasions may be valid regardless of the type of slot in accordance with a first validity rule and determining that a subset of RACH occasions from the set of full-duplex RACH occasions may be invalid based on the subset of RACH occasions being positioned within non-full-duplex slots and in accordance with a second validity rule.
In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the set of full-duplex RACH occasions include a first subset of full-duplex RACH occasions within the one or more full-duplex slots, and a second subset of full-duplex RACH occasions that overlap in a time domain with the set of common RACH occasions within the first half-duplex uplink slot, the set of common RACH occasions and the set of full-duplex RACH occasions may be associated with a set of multiple preambles such that temporally overlapping pairs of RACH occasions map to one or more common preambles of the set of multiple preambles, and each temporally overlapping pair of RACH occasions include one of the second subset of full-duplex RACH occasions and one of the set of common RACH occasions.
In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the set of full-duplex RACH occasions include SBFD RACH occasions and the one or more full-duplex slots include one or more SBFD slots.
A method by a UE is described. The method may include receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, receiving, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or additional more full-duplex slots, where the set of common RACH occasions are mapped to the set of common PUSCH occasions, and where the set of full-duplex RACH occasions mapped to the set of full-duplex PUSCH occasions, transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion from the set of full-duplex RACH occasions, transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that maps to the common RACH occasion based on transmitting the preamble via the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that maps to the common RACH occasion used to transmit the preamble based on transmitting the preamble via the full-duplex RACH occasion, and receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
A UE is described. The UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the UE to receive, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, receive, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or additional more full-duplex slots, where the set of common RACH occasions are mapped to the set of common PUSCH occasions, and where the set of full-duplex RACH occasions mapped to the set of full-duplex PUSCH occasions, transmit a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion from the set of full-duplex RACH occasions, transmit a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that maps to the common RACH occasion based on transmitting the preamble via the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that maps to the common RACH occasion used to transmit the preamble based on transmitting the preamble via the full-duplex RACH occasion, and receive, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
Another UE is described. The UE may include means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, means for receiving, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or additional more full-duplex slots, where the set of common RACH occasions are mapped to the set of common PUSCH occasions, and where the set of full-duplex RACH occasions mapped to the set of full-duplex PUSCH occasions, means for transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion from the set of full-duplex RACH occasions, means for transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that maps to the common RACH occasion based on transmitting the preamble via the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that maps to the common RACH occasion used to transmit the preamble based on transmitting the preamble via the full-duplex RACH occasion, and means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
A non-transitory computer-readable medium storing code is described. The code may include instructions executable by one or more processors to receive, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, receive, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or additional more full-duplex slots, where the set of common RACH occasions are mapped to the set of common PUSCH occasions, and where the set of full-duplex RACH occasions mapped to the set of full-duplex PUSCH occasions, transmit a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion from the set of full-duplex RACH occasions, transmit a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that maps to the common RACH occasion based on transmitting the preamble via the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that maps to the common RACH occasion used to transmit the preamble based on transmitting the preamble via the full-duplex RACH occasion, and receive, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the set of multiple preambles of the set of full-duplex RACH occasions and the set of full-duplex PUSCH occasions.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the first control signaling, the second control signaling, or both, a third mapping configuration between the set of multiple preambles of set of common RACH occasions and the set of full-duplex PUSCH occasions, a fourth mapping configuration between the set of multiple preambles of the set of full-duplex RACH occasions and the set of common PUSCH occasions, or both.
In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the set of full-duplex RACH occasions include SBFD RACH occasions, the set of full-duplex PUSCH occasions include SBFD PUSCH occasions, and the one or more full-duplex slots, the one or more additional full-duplex slots, or both, include one or more SBFD slots.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the first control signaling, the second control signaling, or both, an indication that the first RACH configuration, second RACH configuration, the first PUSCH configuration, the second PUSCH configuration, or any combination thereof, may be usable for performing random access procedures associated with system information requests, physical downlink control channel ordering, beam failure recovery, mobility, or any combination thereof.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the first control signaling, the second control signaling, or both, an indication that the second RACH configuration, the second PUSCH configuration, or both, include UE-specific configurations or cell-specific configurations.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the first control signaling, the second control signaling, third control signaling, or any combination thereof, a common random access configuration associated with one or more operations different from the two-step random access procedure and performing the one or more operations in accordance with either the common random access configuration, or in accordance with the second RACH configuration and the second PUSCH configuration.
Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that the UE may have not been configured with a common random access configuration associated with one or more operations different from the two-step random access procedure and performing the one or more operations in accordance with the first RACH configuration and the first PUSCH configuration, or in accordance with the second RACH configuration and the second PUSCH configuration.
A method by a network entity is described. The method may include transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a RACH configuration including a set of multiple common RACH occasions within a first half-duplex uplink slot, transmitting, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or more full-duplex slots, receiving a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the set of multiple common RACH occasions, receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that is associated with the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that is associated with the common RACH occasion used to receive the preamble, and transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
A network entity is described. The network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the network entity to transmit, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a RACH configuration including a set of multiple common RACH occasions within a first half-duplex uplink slot, transmit, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or more full-duplex slots, receive a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the set of multiple common RACH occasions, receive a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that is associated with the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that is associated with the common RACH occasion used to receive the preamble, and transmit, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
Another network entity is described. The network entity may include means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a RACH configuration including a set of multiple common RACH occasions within a first half-duplex uplink slot, means for transmitting, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or more full-duplex slots, means for receiving a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the set of multiple common RACH occasions, means for receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that is associated with the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that is associated with the common RACH occasion used to receive the preamble, and means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
A non-transitory computer-readable medium storing code is described. The code may include instructions executable by one or more processors to transmit, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a RACH configuration including a set of multiple common RACH occasions within a first half-duplex uplink slot, transmit, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or more full-duplex slots, receive a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the set of multiple common RACH occasions, receive a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that is associated with the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that is associated with the common RACH occasion used to receive the preamble, and transmit, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of multiple common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the set of multiple preambles of the set of multiple common RACH occasions and the set of full-duplex PUSCH occasions and identifying one of the common PUSCH occasion or the full-duplex PUSCH occasion that maps to the common RACH occasion used to transmit the preamble in accordance with the first mapping configuration or the second mapping configuration, where the payload of the first message may be received via the identified one of the common PUSCH occasion or the full-duplex PUSCH occasion.
In some examples of the method, network entities, and non-transitory computer-readable medium described herein, each common RACH occasion from the set of multiple common RACH occasions may be mapped to a set of multiple full-duplex PUSCH occasions from the set of full-duplex PUSCH occasions.
In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the second PUSCH configuration includes a first sub-configuration associated with a first preamble group including the set of full-duplex PUSCH occasions, and a second sub-configuration associated with a second preamble group including an additional set of full-duplex PUSCH occasions.
Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying one of the common PUSCH occasion or the full-duplex PUSCH occasion that maps to the common RACH occasion based on a relative timing of the common PUSCH occasion and the full-duplex PUSCH occasion in a time domain, one or more measured or predicted downlink signal quality metrics associated with slots that include the common PUSCH occasion and the full-duplex PUSCH occasion, a radio resource control configuration, a PUSCH transmission power relative to a transmission power threshold associated with the one or more full-duplex slots, a type of UE, or any combination thereof, where the payload of the first message of the two-step random access procedure may be received via the identified one of the common PUSCH occasion or the full-duplex PUSCH occasion.
Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining a validity of each full-duplex PUSCH occasion within the set of full-duplex PUSCH occasions based on a type of slot corresponding to each of the set of full-duplex PUSCH occasions, the type of slot including a full-duplex slot type or a half-duplex slot type.
In some examples of the method, network entities, and non-transitory computer-readable medium described herein, determining the validity of each full-duplex PUSCH occasion may include operations, features, means, or instructions for determining that each full-duplex PUSCH occasion of the set of full-duplex PUSCH occasions may be valid regardless of the type of slot in accordance with a first validity rule and determining that a subset of PUSCH occasions from the set of full-duplex PUSCH occasions may be invalid based on the subset of PUSCH occasions being positioned within non-full-duplex slots and in accordance with a second validity rule.
In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the set of full-duplex PUSCH occasions include a first subset of full-duplex PUSCH occasions within the one or more full-duplex slots, and a second subset of full-duplex PUSCH occasions that overlap in a time domain with the set of common PUSCH occasions within the one or more second half-duplex uplink slots, the set of multiple common RACH occasions may be associated with a set of multiple preambles, the set of multiple preambles may be mapped to the set of common PUSCH occasions and the set of full-duplex PUSCH occasions such that temporally overlapping pairs of PUSCH occasions may be associated with one or more common preambles of the set of multiple preambles, and each temporally overlapping pair of PUSCH occasions include one of the second subset of full-duplex PUSCH occasions and one of the set of common PUSCH occasions.
In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the set of full-duplex PUSCH occasions include SBFD PUSCH occasions and the one or more full-duplex slots include one or more SBFD slots.
In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the first PUSCH configuration indicates a first starting resource block frequency configuration associated with the set of common PUSCH occasions and the second PUSCH configuration indicates a second starting resource block frequency configuration associated with the set of full-duplex PUSCH occasions.
In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the first PUSCH configuration indicates a first quantity of frequency-division multiplexed PUSCH occasions associated with the set of common PUSCH occasions within the one or more second half-duplex uplink slots and the second PUSCH configuration indicates a second quantity of frequency-division multiplexed PUSCH occasions associated with the set of full-duplex PUSCH occasions within the one or more full-duplex slots.
In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the set of multiple common RACH occasions and the set of common PUSCH occasions may be usable by full-duplex-aware UEs and non-full-duplex-aware UEs and the set of full-duplex PUSCH occasions may be usable by full-duplex-aware UEs but unusable by non-full-duplex-aware UEs.
A method by a network entity is described. The method may include transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, transmitting, via the first control signaling, second control signaling, or both, a PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the set of multiple PUSCH occasions including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion of the set of full-duplex RACH occasions, receiving a payload of the first message of the two-step random access procedure to the network entity via a common PUSCH occasion of the set of common PUSCH occasions that maps to the common RACH occasion or the full-duplex RACH occasion that was used to receive the preamble, and transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
A network entity is described. The network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the network entity to transmit, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, transmit, via the first control signaling, second control signaling, or both, a PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the set of multiple PUSCH occasions including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, receive a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion of the set of full-duplex RACH occasions, receive a payload of the first message of the two-step random access procedure to the network entity via a common PUSCH occasion of the set of common PUSCH occasions that maps to the common RACH occasion or the full-duplex RACH occasion that was used to receive the preamble, and transmit, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
Another network entity is described. The network entity may include means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, means for transmitting, via the first control signaling, second control signaling, or both, a PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the set of multiple PUSCH occasions including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, means for receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion of the set of full-duplex RACH occasions, means for receiving a payload of the first message of the two-step random access procedure to the network entity via a common PUSCH occasion of the set of common PUSCH occasions that maps to the common RACH occasion or the full-duplex RACH occasion that was used to receive the preamble, and means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
A non-transitory computer-readable medium storing code is described. The code may include instructions executable by one or more processors to transmit, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, transmit, via the first control signaling, second control signaling, or both, a PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the set of multiple PUSCH occasions including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, receive a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion of the set of full-duplex RACH occasions, receive a payload of the first message of the two-step random access procedure to the network entity via a common PUSCH occasion of the set of common PUSCH occasions that maps to the common RACH occasion or the full-duplex RACH occasion that was used to receive the preamble, and transmit, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the first half-duplex uplink slot including the set of common RACH occasions includes a PRACH slot and the PUSCH configuration includes a first time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common PUSCH occasions, and a second time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common PUSCH occasions.
Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the set of multiple preambles of the set of full-duplex RACH occasions and the set of common PUSCH occasions.
In some examples of the method, network entities, and non-transitory computer-readable medium described herein, each common PUSCH occasion from the set of common PUSCH occasions may be mapped to at least one common RACH occasion from the set of common RACH occasions and at least one full-duplex RACH occasion from the set of full-duplex RACH occasions.
Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying one of the common RACH occasion or the full-duplex RACH occasion based on a relative timing of the common RACH occasion and the full-duplex RACH occasion in a time domain, one or more measured or predicted signal quality metrics associated with slots that include the common RACH occasion and the full-duplex RACH occasion, a PUSCH transmission power relative to a transmission power threshold associated with the one or more full-duplex slots, a radio resource control configuration, a type of UE, or any combination thereof, where the preamble of the first message of the two-step random access procedure may be received via the identified one of the common RACH occasion or the full-duplex RACH occasion.
Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining a validity of each full-duplex RACH occasion within the set of full-duplex RACH occasions based on a type of slot corresponding to each of the set of full-duplex RACH occasions, the type of slot including a full-duplex slot type or a half-duplex slot type.
In some examples of the method, network entities, and non-transitory computer-readable medium described herein, determining the validity of each full-duplex RACH occasion may include operations, features, means, or instructions for determining that each full-duplex RACH occasion of the set of full-duplex RACH occasions may be valid regardless of the type of slot in accordance with a first validity rule and determining that a subset of RACH occasions from the set of full-duplex RACH occasions may be invalid based on the subset of RACH occasions being positioned within non-full-duplex slots and in accordance with a second validity rule.
In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the set of full-duplex RACH occasions include a first subset of full-duplex RACH occasions within the one or more full-duplex slots, and a second subset of full-duplex RACH occasions that overlap in a time domain with the set of common RACH occasions within the first half-duplex uplink slot, the set of common RACH occasions and the set of full-duplex RACH occasions may be associated with a set of multiple preambles such that temporally overlapping pairs of RACH occasions map to one or more common preambles of the set of multiple preambles, and each temporally overlapping pair of RACH occasions include one of the second subset of full-duplex RACH occasions and one of the set of common RACH occasions.
In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the set of full-duplex RACH occasions include SBFD RACH occasions and the one or more full-duplex slots include one or more SBFD slots.
A method by a network entity is described. The method may include transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, transmitting, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or additional more full-duplex slots, where the set of common RACH occasions are mapped to the set of common PUSCH occasions, and where the set of full-duplex RACH occasions mapped to the set of full-duplex PUSCH occasions, receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion from the set of full-duplex RACH occasions, receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that maps to the common RACH occasion based on transmitting the preamble via the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that maps to the common RACH occasion used to receive the preamble based on receiving the preamble via the full-duplex RACH occasion, and transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
A network entity is described. The network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the network entity to transmit, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, transmit, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or additional more full-duplex slots, where the set of common RACH occasions are mapped to the set of common PUSCH occasions, and where the set of full-duplex RACH occasions mapped to the set of full-duplex PUSCH occasions, receive a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion from the set of full-duplex RACH occasions, receive a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion  from the set of common PUSCH occasions that maps to the common RACH occasion based on transmitting the preamble via the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that maps to the common RACH occasion used to receive the preamble based on receiving the preamble via the full-duplex RACH occasion, and transmit, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
Another network entity is described. The network entity may include means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, means for transmitting, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or additional more full-duplex slots, where the set of common RACH occasions are mapped to the set of common PUSCH occasions, and where the set of full-duplex RACH occasions mapped to the set of full-duplex PUSCH occasions, means for receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion from the set of full-duplex RACH occasions, means for receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that maps to the common RACH occasion based on transmitting the preamble via the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that maps to the common RACH occasion used to receive the preamble based on receiving the preamble via the full-duplex RACH occasion, and means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
A non-transitory computer-readable medium storing code is described. The code may include instructions executable by one or more processors to transmit, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex RACH occasions within one or more full-duplex slots, transmit, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex PUSCH occasions within one or additional more full-duplex slots, where the set of common RACH occasions are mapped to the set of common PUSCH occasions, and where the set of full-duplex RACH occasions mapped to the set of full-duplex PUSCH occasions, receive a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion from the set of full-duplex RACH occasions, receive a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that maps to the common RACH occasion based on transmitting the preamble via the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that maps to the common RACH occasion used to receive the preamble based on receiving the preamble via the full-duplex RACH occasion, and transmit, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the set of multiple preambles of the set of full-duplex RACH occasions and the set of full-duplex PUSCH occasions.
Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, via the first control signaling, the second control signaling, or both, a third mapping configuration between the set of multiple preambles of set of common RACH occasions and the set of full-duplex PUSCH occasions, a fourth mapping configuration between the set of multiple preambles of the set of full-duplex RACH occasions and the set of common PUSCH occasions, or both.
In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the set of full-duplex RACH occasions include SBFD RACH occasions, the set of full-duplex PUSCH occasions include SBFD PUSCH occasions, and the one or more full-duplex slots, the one or more additional full-duplex slots, or both, include one or more SBFD slots.
Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, via the first control signaling, the second control signaling, or both, an indication that the first RACH configuration, second RACH configuration, the first PUSCH configuration, the second PUSCH configuration, or any combination thereof, may be usable for performing random access procedures associated with system information requests, physical downlink control channel ordering, beam failure recovery, mobility, or any combination thereof.
Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, via the first control signaling, the second control signaling, or both, an indication that the second RACH configuration, the second PUSCH configuration, or both, include UE-specific configurations or cell-specific configurations.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 shows an example of a wireless communications system that supports techniques for two-step random access procedures using dedicated sub-band full-duplex (SBFD) resources in accordance with one or more aspects of the present disclosure.
FIG. 2 shows an example of a two-step random access channel (RACH) procedure configuration that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
FIG. 3 shows an example of a wireless communications system that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
FIG. 4 shows an example of a resource configuration that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
FIG. 5 shows an example of a resource configuration that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
FIG. 6 shows an example of a resource configuration that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
FIG. 7 shows an example of a resource configuration that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
FIG. 8 shows an example of a process flow that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
FIGs. 9 and 10 show block diagrams of devices that support techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
FIG. 11 shows a block diagram of a communications manager that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
FIG. 12 shows a diagram of a system including a device that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
FIGs. 13 and 14 show block diagrams of devices that support techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
FIG. 15 shows a block diagram of a communications manager that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
FIG. 16 shows a diagram of a system including a device that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
FIGs. 17 through 19 show flowcharts illustrating methods that support techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
DETAILED DESCRIPTION
Different networks may utilize different types of access procedures to enable wireless devices (e.g., user equipments (UEs) ) to connect to and access the networks, such as four-step random access channel (RACH) procedures and two-step RACH procedures. For example, some networks have implemented a two-step RACH procedure, where a UE transmits a first message (MsgA) , and receives a second message (MsgB) back from the network to complete the RACH procedure. The first message (MsgA) transmitted via the UE may include a preamble transmitted within a configured RACH occasion (RO) , and a payload transmitted within a configured physical uplink shared channel (PUSCH) occasion (PO) that maps to the RO used to transmit the preamble. MsgA may include Msg1 and Msg3 and MsgB may include Msg2 and Msg4 from conventional four-step RACH procedures. Two-step RACH  procedures are intended to reduce latency and signaling overhead relative to the conventional four-step RACH procedures.
However, current RACH procedures only utilize ROs and POs configured within legacy half-duplex uplink slots. In other words, conventional RACH procedures have no mechanisms for utilizing full-duplex slots for transmitting MsgA, such as sub-band full-duplex (SBFD) uplink bands positioned within downlink slots. The inability to utilize SBFD slots to perform signaling used for RACH procedures may increase the latency of RACH procedures. Moreover, requiring all devices to use the same resources within half-duplex slots to perform RACH procedures may increase collisions and noise within such resources, thereby decreasing the efficiency and success probability of such RACH procedures.
Accordingly, aspects of the present disclosure are directed to signaling and configurations that utilize full-duplex slots (e.g., SBFD slots) to communicate messages associated with RACH procedures. In particular, aspects of the present disclosure are directed to random access configurations that configure UEs with dedicated full-duplex ROs (e.g., SBFD ROs) and/or dedicated full-duplex POs (e.g., SBFD POs) to enable the UEs to perform at least a portion of a MsgA of a two-step RACH procedure within full-duplex slots. As such, by enabling UEs to transmit RACH procedure signaling within full-duplex slots, techniques described herein may reduce a latency of two-step RACH procedures, and alleviate congestion/collisions within conventional RACH procedure resources within half-duplex slots.
For example, in addition to legacy ROs and legacy POs within half-duplex uplink slots, a random access configuration for a two-step RACH procedure may include (1) dedicated SBFD ROs within full-duplex slots, and/or (2) dedicated POs within full-duplex slots. In such cases, the random access configuration may indicate mappings between the preambles of legacy ROs, the legacy POs, the SBFD ROs, and/or the SBFD POs. In cases where full-duplex aware UEs are configured with both legacy and SBFD ROs (and/or legacy and SBFD POs) , the full-duplex aware UEs may be able to select whether to use the legacy or SBFD resources based on a number of factors, including a relative timing of resources (e.g., select the earliest RO/PO to reduce latency) , based on channel qualities of the resources, RRC pre-configuration, the uplink transmit power relative to a maximum threshold of transmit power in SBFD slots, and/or based on the type of UE (e.g., full-duplex UEs select SBFD ROs/POs, and half-duplex UEs select legacy ROs/POs) .
Aspects of the disclosure are initially described in the context of wireless communications systems. Additional aspects of the disclosure are described in the context of an example RACH procedure configuration, example resource configurations, and an example process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to techniques for two-step random access procedures using dedicated SBFD resources.
FIG. 1 shows an example of a wireless communications system 100 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more devices, such as one or more network devices (e.g., network entities 105) , one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.
The network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities. In various examples, a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network entities 105 and UEs 115 may wirelessly communicate via communication link (s) 125 (e.g., a radio frequency (RF) access link) . For example, a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish the communication link (s) 125. The coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs) .
The UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times. The UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices in the wireless communications system 100 (e.g., other wireless communication devices, including UEs 115 or network entities 105) , as shown in FIG. 1.
As described herein, a node of the wireless communications system 100, which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein) , a UE 115 (e.g., any UE described herein) , a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be a UE 115. As another example, a node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.
In some examples, network entities 105 may communicate with a core network 130, or with one another, or both. For example, network entities 105 may communicate with the core network 130 via backhaul communication link (s) 120 (e.g., in accordance with an S1, N2, N3, or other interface protocol) . In some examples, network entities 105 may communicate with one another via backhaul communication link (s) 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via the core network 130) . In some examples, network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol) , or any combination thereof. The backhaul communication link (s) 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) or one or more wireless links (e.g., a radio link, a wireless optical link) , among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.
One or more of the network entities 105 or network equipment described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB) , a 5G NB, a next-generation eNB (ng-eNB) , a Home NodeB, a Home eNodeB, or other suitable terminology) . In some examples, a network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within one network entity (e.g., a network entity 105 or a single RAN node, such as a base station 140) .
In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) , which may be configured to utilize a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 105) , such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) . For example, a network entity 105 may include one or more of a central unit (CU) , such as a CU 160, a distributed unit (DU) , such as a DU 165, a radio unit (RU) , such as an RU 170, a RAN Intelligent Controller (RIC) , such as an RIC 175 (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, such as an SMO system 180, or any combination thereof. An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote  radio unit (RRU) , or a transmission reception point (TRP) . One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations) . In some examples, one or more of the network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .
The split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (e.g., layer 3 (L3) , layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) . The CU 160 (e.g., one or more CUs) may be connected to a DU 165 (e.g., one or more DUs) or an RU 170 (e.g., one or more RUs) , or some combination thereof, and the DUs 165, RUs 170, or both may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or multiple different cells (e.g., via one or multiple different RUs, such as an RU 170) . In some cases, a functional split between a CU 160 and a DU 165 or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170) . A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to a DU 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u) , and a DU 165 may be connected to an RU 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface) . In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities (e.g., one or more of the network entities 105) that are in communication via such communication links.
In some wireless communications systems (e.g., the wireless communications system 100) , infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130) . In some cases, in an IAB network, one or more of the network entities 105 (e.g., network entities 105 or IAB node (s) 104) may be partially controlled by each other. The IAB node (s) 104 may be referred to as a donor entity or an IAB donor. A DU 165 or an RU 170 may be partially controlled by a CU 160 associated with a network entity 105 or base station 140 (such as a donor network entity or a donor base station) . The one or more donor entities (e.g., IAB donors) may be in communication with one or more additional devices (e.g., IAB node (s) 104) via supported access and backhaul links (e.g., backhaul communication link (s) 120) . IAB node (s) 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DUs 165) of a coupled IAB donor. An IAB-MT may be equipped with an independent set of antennas for relay of communications with UEs 115 or may share the same antennas (e.g., of an RU 170) of IAB node (s) 104 used for access via the DU 165 of the IAB node (s) 104 (e.g., referred to as virtual IAB-MT (vIAB-MT) ) . In some examples, the IAB node (s) 104 may include one or more DUs (e.g., DUs 165) that support communication links with additional entities (e.g., IAB node (s) 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream) . In such cases, one or more components of the disaggregated RAN architecture (e.g., the IAB node (s) 104 or components of the IAB node (s) 104) may be configured to operate according to the techniques described herein.
For instance, an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor) , IAB node (s) 104, and one or more UEs 115. The IAB donor may facilitate connection between the core network 130 and the AN  (e.g., via a wired or wireless connection to the core network 130) . That is, an IAB donor may refer to a RAN node with a wired or wireless connection to the core network 130. The IAB donor may include one or more of a CU 160, a DU 165, and an RU 170, in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link) . The IAB donor and IAB node (s) 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol) . Additionally, or alternatively, the CU 160 may communicate with the core network 130 via an interface, which may be an example of a portion of a backhaul link, and may communicate with other CUs (e.g., including a CU 160 associated with an alternative IAB donor) via an Xn-C interface, which may be an example of another portion of a backhaul link.
IAB node (s) 104 may refer to RAN nodes that provide IAB functionality (e.g., access for UEs 115, wireless self-backhauling capabilities) . A DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node (s) 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with IAB node (s) 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through other IAB node (s) 104) . Additionally, or alternatively, IAB node (s) 104 may also be referred to as parent nodes or child nodes to other IAB node (s) 104, depending on the relay chain or configuration of the AN. The IAB-MT entity of IAB node (s) 104 may provide a Uu interface for a child IAB node (e.g., the IAB node (s) 104) to receive signaling from a parent IAB node (e.g., the IAB node (s) 104) , and a DU interface (e.g., a DU 165) may provide a Uu interface for a parent IAB node to signal to a child IAB node or UE 115.
For example, IAB node (s) 104 may be referred to as parent nodes that support communications for child IAB nodes, or may be referred to as child IAB nodes associated with IAB donors, or both. An IAB donor may include a CU 160 with a wired or wireless connection (e.g., backhaul communication link (s) 120) to the core network 130 and may act as a parent node to IAB node (s) 104. For example, the DU 165 of an IAB donor may relay transmissions to UEs 115 through IAB node (s) 104, or may directly signal transmissions to a UE 115, or both. The CU 160 of the IAB donor may signal communication link establishment via an F1 interface to IAB node (s) 104, and the IAB node (s) 104 may schedule transmissions (e.g., transmissions to the UEs 115 relayed from the IAB donor) through one or more DUs (e.g., DUs 165) . That is, data may be relayed to and from IAB node (s) 104 via signaling via an NR Uu interface to MT of IAB node (s) 104 (e.g., other IAB node (s) ) . Communications with IAB node (s) 104 may be scheduled by a DU 165 of the IAB donor or of IAB node (s) 104.
In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support test as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180) .
A UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA) , a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, vehicles, or meters, among other examples.
The UEs 115 described herein may be able to communicate with various types of devices, such as UEs 115 that may sometimes operate as relays, as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
The UEs 115 and the network entities 105 may wirelessly communicate with one another via the communication link (s) 125 (e.g., one or more access links) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined PHY layer structure for supporting the communication link (s) 125. For example, a carrier used for the communication link (s) 125 may include a portion of an RF spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR) . Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information (SI) ) , control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105. For example, the terms “transmitting, ” “receiving, ” or “communicating, ” when referring to a network entity 105, may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities, such as one or more of the network entities 105) .
In some examples, such as in a carrier aggregation configuration, a carrier may have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN) ) and may be identified according to a channel raster for discovery by the UEs 115. A carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different RAT) .
The communication link (s) 125 of the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions. Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode) .
A carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular RAT (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz) ) . Devices of the wireless communications system 100 (e.g., the network entities 105, the UEs 115, or both) may have hardware configurations that support communications using a particular carrier bandwidth or may be configurable to support communications using one of a set of carrier bandwidths. In some examples, the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.
Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) ) . In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) , such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam) , and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.
One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.
The time intervals for the network entities 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts=1/ (Δfmax·Nf) seconds, for which Δfmax may represent a supported subcarrier spacing, and Nf may represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms) ) . Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023) .
Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) . In some wireless communications systems, such as the wireless communications system 100, a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., Nf) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.
A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI) . In some examples, the TTI duration (e.g., a quantity of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) ) .
Physical channels may be multiplexed for communication using a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET) ) for a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115. For example, one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs) ) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to UEs 115 (e.g., one or more UEs) or may include UE-specific search space sets for sending control information to a UE 115 (e.g., a specific UE) .
A network entity 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID) , a virtual cell identifier (VCID) ) . In some examples, a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates. Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105. For example, a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.
A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a network entity 105 operating with lower power (e.g., a base station 140 operating with lower power) relative to a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG) , the UEs 115 associated with users in a home or office) . A network entity 105 may support one or more cells and may also support communications via the one or more cells using one or multiple component carriers.
In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB) ) that may provide access for different types of devices.
In some examples, a network entity 105 (e.g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area, such as the coverage area 110. In some examples, coverage areas 110 (e.g., different coverage areas) associated with different technologies may overlap, but the coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., a network entity 105) . In some other examples, overlapping coverage areas, such as a coverage area 110, associated with different technologies may be supported by different network entities (e.g., the network entities 105) . The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 support communications for coverage areas 110 (e.g., different coverage areas) using the same or different RATs.
The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) . The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.
In some examples, a UE 115 may be configured to support communicating directly with other UEs (e.g., one or more of the UEs 115) via a device-to-device (D2D) communication link, such as a D2D communication link 135 (e.g., in accordance with a peer-to-peer (P2P) , D2D, or sidelink protocol) . In some examples, one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170) , which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105. In some examples, one or more UEs 115 of such a group may be outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105. In some examples, groups of the UEs 115 communicating via D2D communications may support a one-to-many (1: M) system in which each UE 115 transmits to one or more of the UEs 115 in the group. In some examples, a network entity 105 may facilitate the scheduling of resources for D2D communications. In some other examples, D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.
In some systems, a D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115) . In some examples, vehicles may communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. A vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., network entities 105, base stations 140, RUs 170) using vehicle-to-network (V2N) communications, or with both.
The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.
The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) . Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.
The wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) RAT, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA) . Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.
A network entity 105 (e.g., a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations. A network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.
The network entities 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords) . Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) , for which multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO) , for which multiple spatial layers are transmitted to multiple devices.
Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .
A network entity 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations. For example, a network entity 105 (e.g., a base station 140, an RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to conduct beamforming operations for directional communications with a UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a network entity 105 multiple times along different directions. For example, the network entity 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network entity 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the network entity 105.
Some signals, such as data signals associated with a particular receiving device, may be transmitted by a transmitting device (e.g., a network entity 105 or a UE 115) along a single beam direction (e.g., a direction associated with the receiving device, such as another network entity 105 or UE 115) . In some examples, the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted along one or more beam directions. For example, a UE 115 may receive one or more of the signals transmitted by the network entity 105 along different directions and may report to the network entity 105 an indication of the signal that the UE 115 received with a highest signal quality or an otherwise acceptable signal quality.
In some examples, transmissions by a device (e.g., by a network entity 105 or a UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network entity 105 to a UE 115) . The UE 115 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands. The network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS) , a channel state information reference signal (CSI-RS) ) , which may be precoded or unprecoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook) . Although these techniques are described with reference to signals transmitted along one or more directions by a network entity 105 (e.g., a base station 140, an RU 170) , a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device) .
A receiving device (e.g., a UE 115) may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a transmitting device (e.g., a network entity 105) , such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device may perform reception in accordance with multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions. In some examples, a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal) . The single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR) , or otherwise acceptable signal quality based on listening according to multiple beam directions) .
The wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. An RLC layer may perform packet segmentation and reassembly to communicate via logical channels. A MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer also may implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency. In the control plane, an RRC layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network entity 105 or a core network 130 supporting radio bearers for user plane data. A PHY layer may map transport channels to physical channels.
The UEs 115 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., the communication link (s) 125, a D2D communication link 135) . HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC) ) , forward error correction (FEC) , and retransmission (e.g., automatic repeat request (ARQ) ) . HARQ may improve throughput at the MAC layer in relatively poor radio conditions (e.g., low signal-to-noise conditions) . In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.
In some aspects, the respective wireless devices of the wireless communications system 100 (e.g., UEs 115, network entities 105, IAB nodes, etc. ) may support signaling and configurations that utilize full-duplex slots (e.g., SBFD slots) to communicate messages associated with RACH procedures. In particular, aspects of the present disclosure are directed to RACH configurations for two-step RACH procedures to be performed between UEs 115 and network entities 105, where the RACH procedures configure UEs 115 with dedicated full-duplex ROs (e.g., SBFD ROs) and/or dedicated full-duplex POs (e.g., SBFD POs) to enable the UEs 115 to perform at least a portion of a MsgA of a two-step RACH procedure within full-duplex slots.
For example, in addition to legacy ROs and legacy POs within half-duplex uplink slots, a RACH configuration for a two-step RACH procedure may include (1) dedicated SBFD ROs within full-duplex slots, and/or (2) dedicated POs within full-duplex slots. In such cases, the RACH configuration may indicate mappings between the legacy ROs, the legacy POs, the SBFD ROs, and/or the SBFD POs. In cases where full-duplex aware UEs 115 are configured with both legacy and SBFD ROs (and/or legacy and SBFD POs) , the full-duplex aware UEs 115 may be able to select whether to use the legacy or SBFD resources based on a number of factors, including a relative timing of resources (e.g., select the earliest RO/PO to reduce latency) , the uplink transmit power relative to a maximum threshold of transmit power in SBFD slots, based on channel qualities of the resources, RRC pre-configuration, and/or based on the type of UE 115 (e.g., full-duplex UEs 115 select SBFD ROs/POs, and half-duplex UEs 115 select legacy ROs/POs) .
Techniques described herein may facilitate faster and more efficient RACH procedures (e.g., two-step RACH procedures) . In particular, by enabling UEs 115 to transmit RACH procedure signaling within full-duplex slots, techniques described herein may reduce a latency of two-step RACH procedures, and alleviate congestion/collisions within conventional RACH procedure resources within half-duplex slots.
FIG. 2 shows an example of a two-step RACH procedure configuration 200 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure.
The two-step RACH procedure configuration 200 illustrates signaling associated with a two-step RACH procedure performed between a UE 115-a and a network entity 105-a. As described previously herein, different networks may utilize different types of access procedures to enable wireless devices (e.g., UEs 115) to connect to and access the networks, such as four-step random access channel (RACH) procedures and two-step RACH procedures.
Two-step RACH procedures may be associated with several benefits over four-step RACH procedures. In particular, two-step RACH procedures may be used to reduce latency and signaling overhead as compared to four-step RACH procedures. Moreover, two-step RACH procedures may support timing advance (TA) -free and grant-free small uplink packet transmission with different transport block sizes (TBSs) and/or modulation and coding schemes (MCSs) . Further, two-step RACH procedures may improve the capacity and power efficiency relative to four-step contention-based random access (CBRA) procedures, and may replace RACH-less handover procedures.
The various steps and signaling of a two-step RACH procedure are further described with reference to the process flow shown in FIG. 2.
At 205, the UE 115-a may receive RRC and/or SI signaling from the network entity 105-a. The signaling at 205 may indicate an SSB configuration and/or a RACH configuration for performing the two-step RACH procedure with the network entity 105-a. For example, the RRC signaling at 205 may indicate a random access configuration for performing a two-step RACH procedure, where the random access configuration includes (1) a RACH configuration, and (2) a PUSCH configuration. That is, the signaling may indicate resources (e.g., PUCCH, PUSCH, PDCCH, and/or PDSCH resources) that are usable for exchanging messages associated with the two-step RACH procedure.
At 210, the UE 115-a may transmit a preamble of a first message (e.g., MsgA) of the two-step RACH procedure. The preamble may be transmitted via PUCCH resources (e.g., RACH, PRACH resources) configured via the signaling at 205. As noted previously herein, MsgA of the two-step RACH procedure may include the information that is included within Msg1 and Msg3 of a four-step RACH procedure.
At 215, the UE 115-a may transmit a payload of the first message (e.g., MsgA) of the two-step RACH procedure. The payload may be transmitted via PUSCH resources configured via the signaling at 205.
The diagram 201 shown in FIG. 2 illustrates an example of the MsgA 245 of the two-step RACH procedure that is transmitted at 210 and 215. MsgA 245 of the two-step RACH procedure may include the information that is included within Msg1 and Msg3 of a four-step RACH procedure. As shown in diagram 201, MsgA 245 may include a MsgA preamble 250 and a MsgA payload 255. The MsgA preamble 250 may be transmitted within PRACH resources. In particular, the MsgA preamble 250 may be transmitted via an RO configured via the RACH configuration indicated via the signaling at 205. Comparatively, the MsgA payload 255 may be transmitted within DMRS/PUSCH resources. That is, the MsgA payload 255 may be transmitted via a PO configured via the PUSCH configuration indicated via the signaling at 205. In particular, the MsgA payload 255 may be transmitted via a PO that maps to (e.g., corresponds to) the RO used to communicate the MsgA preamble 250. The respective sets of PRACH and PUSCH resources in the diagram 201 may be separated (e.g., preceded and/or followed) by guard time (GT) and/or guard band (GB) intervals or resources.
For the purposes of the present disclosure, the term “RO” may be used to refer to time and frequency resources allocated for MsgA preamble 250 transmission. Multiple two-step RACH UEs 115 may share the same RO in transmitting their MsgA preambles 250. Further, different UEs 115 may select different preamble sequences (e.g., code domain multiplexing) . Comparatively, for the purposes of the present disclosure, the term “PO” may be used to refer to time and frequency resources allocated for MsgA PUSCH transmission (e.g., MsgA payload 255) . POs may be used to support asynchronous uplink transmission in two-step RACH procedures, where the GT and GB resources (shown in diagram 201) may be configured for each PO to mitigate inter-symbol interference (ISI) and/or inter-cell interference (ICI) .
Further, the term “PUSCH resource unit” (PRU) may be used to refer to the PO and the DMRS port/sequence used for MsgA payload 255 transmission. Certain resource allocation considerations for the MsgA payload 255 may be taken into account. In particular, the contents and payload size of MsgA 245 may depend on the particular  use case for the two-step RACH procedure, as well as link qualities between the UE 115-a and the network entity 105-a. For instance, in cases where the UE 115-a performs the two-step RACH procedure while in an RRC idle or RRC inactive state, the MsgA payload 255 may include a unique UE identifier, RRC requests, small data, etc. Comparatively, in cases where the UE 115-a performs the two-step RACH procedure while in an RRC connected state, the MsgA payload 255 may include MAC-CE data, data from a user plane (UP) and/or control plane (CP) , etc. In some cases, networks may support multiple PO format to accommodate different use cases and coverage requirements. Further, busty traffic patterns of MsgA 245 may make “fixed” resource allocation inefficient for a given payload size.
The diagram 202 shown in FIG. 2 illustrates the MsgA resource configuration and mapping for CBRA. The diagram 202 illustrates a MsgA RO 260, such as the RO used to communicate the MsgA preamble 250 shown in diagram 201. For each RRC state, up to two MsgA PUSCH configurations can be pre-configured by the network (e.g., network entity 105-a) within an initial/active uplink BWP at the UE 115-a.
For instance, as shown in diagram 202, the MsgA RO 260 may include a first MsgA preamble group 265-a (e.g., MsgA Preamble Group A) , and a second MsgA preamble group 265-b (e.g., MsgA Preamble Group B) . As shown in diagram 202, each preamble group 265 may be mapped to (e.g., correspond to) respective sets of MsgA POs 270. For example, the first preamble group 265-a may be mapped to a first set of MsgA POs 270-a via a first mapping configuration 275-a, and the second preamble group 265-b may be mapped to a second set of MsgA POs 270-b via a second mapping configuration 275-b. The respective MsgA POs 270 may include examples of the PO used to communicate the MsgA payload 255 in diagram 201. In this regard, each MsgA PO 270 may include a set of resources for DMRS and a set of resources for MsgA PUSCH.
Each respective preamble group 265 may include separate sets of configuration parameters (e.g., group-specific configuration parameters) , including: slot-level offset between MsgA PRACH resources (e.g., ROs) and MsgA PUSCH resources (e.g., POs) , a number of FDMed MsgA POs, TDRA and FDRA values, MCS values, TBS values, preamble-to-PUSCH mapping ratios, DMRS resource configurations (e.g., sequence and port) , intra-slot frequency hopping patterns (configurable) , PRB-level guard bands (configurable) , symbol-level guard period after MsgA PUSCH (configurable) , or any combination thereof. In some aspects, multiple UEs 115 may share the same ROs, preamble groups 265, DMRS resources, and POs for performing RACH procedures (e.g., CBRA) with the network (for both TA-free and grant-free RACH procedures) .
The preambles communicated within the MsgA ROs 260 may be mapped to respective PRUs (e.g., in accordance with respective mapping configurations 275) . For example, each consecutive number of NPreamble preamble indexes from a valid PRACH occasion in a valid PRACH slot may be mapped to PRUs in accordance with the following: (1) first, in creasing order of preamble indexes within a single PRACH occasion, (2) second, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions, and (3) third, in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH slot.
Further, each consecutive number of NPreamble preamble indexes from a valid PRACH occasion (e.g., PO) in a valid PRACH slot (e.g., PO slot) may be mapped to a valid PO and the associated DMRS resource (shown in the sets of MsgA POs 270-a, 270-b) in accordance with the following: (1) first, in increasing order of frequency resource indexes fid for frequency multiplexed POs, (2) second, in increasing order of DMRS resource indexes within a PO, where a DMRS resource index DMRSid is determined in an ascending order of a DMRS port index and in an ascending order of a DMRS sequence index, (3) third, in increasing order of time resource indexes tid for time multiplexed POs within a PUSCH slot, and (4) fourth, in increasing order of indexes NS PUSCH slots.
In the above mapping schemes, the term NPreamble=ceil (TPreamble/TPUSCH) , where TPreamble is a total number of valid PRACH occasions per association pattern period multiplied by the number of preambles per valid PRACH occasion provided by rach-ConfigCommonTwoStepRA, and TPUSCH is a total number of valid POs per PUSCH configuration per association pattern period multiplied by the number of DMRS resource indexes per valid PO provided by msgA-DMRS-Config.
Each consecutive number of NPreamble indexes from valid PRACH occasion in a PRACH slot may be mapped to a valid PO (e.g., MsgA PO 270-a, 270-b) and the associated DMRS resource. A PO 270 may be said to be valid if it does not overlap in time and frequency with any valid PRACH occasion associated with either a Type-1 or Type-2 RACH procedure. Additionally, for unpaired spectrum and for synchronization signal and/or physical broadcast channel (PBCH) blocks with indexes provided by ssb-PositionsInBurst in SIB1 or by ServingCellConfigCommon.
If a UE 115 (e.g., UE 115-a) is not provided with tdd-UL-DL-ConfigurationCommon, a PO 270 is valid if the PO 270: (1) does not precede a SS/PBCH block in the PUSCH slot, and (2) starts at least NGap symbols after a last SS/PBCH block symbol, and, if channelAccessMode= “semiStatic” is provided, the PO 270 does not overlap with a set of consecutive symbols before the start of a next channel occupancy time where the UE 115 does not transmit.
Conversely, if a UE 115 (e.g., UE 115-a) is provided with tdd-UL-DL-ConfigurationCommon, a PO 270 is valid if the PO: (1) is within UL symbols, or (2) does not precede a SS/PBCH block in the PUSCH slot, and (3) starts at least NGap symbols after a last downlink symbol and at least NGap symbols after a last SS/PBCH block symbol, and, if channelAccessMode= “semiStatic” is provided, the PO 270 does not overlap with a set of consecutive symbols before the start of a next channel occupancy time where the UE 115 does not transmit.
At 220, the network entity 105-a may decode the MsgA payload 255. In particular, the network entity 105-a may receive the MsgA preamble 250, and may monitor the PO corresponding to the RO in which the MsgA preamble 250 was received in order to decode the MsgA payload 255. At 225, the network entity 105-a may transmit a MsgB PDCCH portion to the UE 115-a. The MsgB PDCCH portion may include C-RNTI, MsgB-RNTI, or both. At 230, the network entity 105-a may transmit a MsgB PDSCH portion to the UE 115-a. MsgB 245 of the two-step RACH procedure (shown at 225 and 230) may include the information that is included within Msg2 and Msg4 of a four-step RACH procedure. The MsgB PDSCH may indicate a success random access response (RAR) . In other words, the MsgB PDSCH may indicate a successful completion of the two-step RACH procedure.
At 235, the UE 115-a may identify a valid TA and PUCCH resource/timing based on the successful completion of the two-step RACH procedure. That is, the UE 115-a may identify a valid TA and/or PUCCH resources/timing based on the MsgB PDCCH and/or MsgB PDSCH received at 225 and/or 230.
At 240, the UE 115-a may transmit a HARQ message to the network entity 105-a, where the HARQ message includes an ACK/NACK responsive to the MsgB received at 225 and 230. Subsequently, the UE 115-a and the network entity 105-a may communicate with one another based on the successful completion of the two-step RACH procedure.
However, as noted previously herein, conventional RACH procedures (including two-step RACH procedures) only utilize ROs and POs configured within legacy half-duplex uplink slots. In other words, conventional RACH procedures have no mechanisms for utilizing full-duplex slots for transmitting MsgA 245, such as SBFD uplink bands positioned within downlink slots. The inability to utilize SBFD slots to perform signaling used for RACH procedures may increase the latency of RACH procedures. Moreover, requiring all devices to use the same resources within half-duplex slots to perform RACH procedures increases collisions and noise within such resources, thereby decreasing the efficiency and success probability of such RACH procedures.
Accordingly, aspects of the present disclosure are directed to signaling and configurations that utilize full-duplex slots (e.g., SBFD slots) to communicate messages associated with RACH procedures. In particular, aspects of the present disclosure are directed to RACH configurations that configure UEs 115 with dedicated full-duplex ROs (e.g., SBFD ROs) and/or dedicated full-duplex POs (e.g., SBFD POs) to enable the UEs 115 to perform at least a portion of a MsgA of a two-step RACH procedure within full-duplex slots.
Attendant advantages of the present disclosure are further shown and described with reference to FIG. 3.
FIG. 3 shows an example of a wireless communications system 300 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure. In some examples, aspects of the wireless communications system 300 may implement, or be implemented by, aspects of the wireless communications system 100, the two-step RACH procedure configuration 200, or both. In particular, the wireless communications system 300 illustrates signaling and configurations for a two-step RACH procedure that utilizes dedicated SBFD resources, as described previously herein.
The wireless communications system 300 may include a UE 115-b and a network entity 105-b, which may be examples of wireless devices as described herein. For example, the UE 115-b and the network entity 105-b shown in FIG. 3 may include examples of the UE 115-a and the network entity 105-a, respectively, as shown in FIG. 2. In some aspects, the UE 115-b and the network entity 105-b may communicate with one another using a communication link 305, which may be an example of an NR or LTE link, a sidelink (e.g., PC5 link) , and the like, between the respective devices. In some cases, the communication link 305 may include an example of an access link (e.g., Uu link) which may include a bi-directional link that enables both uplink and downlink communication. For example, the UE 115-b may transmit uplink signals, such as uplink control signals or uplink data signals, to one or more components of the network entity 105-b using the communication link 305, and one or more components of the network entity 105-b may transmit downlink signals, such as downlink control signals or downlink data signals, to the UE 115-b using the communication link 305.
As noted previously herein, different networks may utilize different types of access procedures to enable wireless devices (e.g., UEs) to connect to and access the networks, such as four-step RACH procedures and two-step RACH procedures (as shown and described in FIG. 2) .
For example, referring to the wireless communications system 300, the UE 115-b may receive control signaling (e.g., RRC signaling, SI signaling) from the network entity 105-b, where the control signaling indicates a random access configuration 310 for performing a two-step RACH procedure with the network entity 105-b. In some aspects, the random access configuration 310 may include or indicate/allocate resources that are usable for performing the various signaling of the two-step RACH procedure. For example, the random access configuration 310 may include a RACH configuration (s) that includes resources for ROs usable for transmitting a preamble for MsgA of a two-step RACH procedure, and a PUSCH configuration (s) that includes resources for POs usable for transmitting a payload for MsgA of the two-step RACH procedure.
For instance, as shown in FIG. 2, the random access configuration 310 may allocate resources within a set of slots 325 or TTIs that are usable for exchanging signaling associated with a two-step RACH procedure. The resources of the random access configuration 310 may be spread across any number of slots 325 or TTIs, such as a first slot 325-a, a second slot 325-b, a third slot 325-c, a fourth slot 325-d, and a fifth slot 325-e. In this example, the first slot 325-a may include a half-duplex downlink slot (e.g., TDD DL slot) that includes only downlink resources, and the fifth slot 325-e may include a half-duplex uplink slot (e.g., TDD UL slot) that includes only uplink resources. Comparatively, the second slot 325-b, the third slot 325-c, and the fourth slot 325-d may include full-duplex slots (e.g., FDD UL/DL slots) that include both uplink and downlink resources (e.g., SBFD slots) . For example, as shown in FIG. 3, the slots 325-b, 325-c, and 325-d may include downlink resources that are split by an uplink sub-band 330 that includes uplink resources.
As described in FIG. 2, the UE 115-b may utilize the random access configuration 310 to transmit a first message (e.g., MsgA 315) of the two-step RACH procedure. Subsequently, the UE 115-b may receive a second message (e.g., MsgB 320) of the two-step RACH procedure to complete the two-step RACH procedure and begin communicating with the network entity 105-b.
As noted previously herein, current RACH procedures only utilize ROs and POs configured within legacy half-duplex uplink slots. In other words, conventional RACH procedures have no mechanisms for utilizing full-duplex slots for transmitting MsgA 315. For example, referring to the random access configuration 310 shown in FIG. 3, according to conventional RACH procedures, the UE 115-may only be able to utilize allocated uplink resources 335 within the fifth slot 325-e (e.g., half-duplex uplink slot) to transmit MsgA 315. As such, according to conventional RACH procedures, the UE 115-b may be unable to use any of the uplink resources within the uplink sub-band 330 to transmit MsgA 315, and may instead have to wait to use the uplink resources 335 within the fifth uplink slot 325-e to transmit MsgA 315. The inability to utilize SBFD slots (e.g., slots 325-b, 325-c, 325-d) to perform signaling used for RACH procedures may increase the latency of RACH procedures. Moreover, requiring all devices (e.g.,  UE 115-b, other UEs 115) to use the same resources within half-duplex slots (e.g., to perform RACH procedures) increases the probability of collisions and noise within such resources, thereby decreasing the efficiency and success probability of such RACH procedures.
Accordingly, aspects of the present disclosure are directed to signaling and configurations that utilize resources 340 within the full-duplex slots 325-b, 325-c, 325-d (e.g., SBFD slots) to communicate messages (e.g., MsgA 315) associated with RACH procedures. In particular, aspects of the present disclosure are directed to random access configurations 310 that configure UEs 115 with dedicated SBFD resources 340 within SBFD slots 325 that may be used for RACH procedures. That is, aspects of the present disclosure are directed to random access configurations 310 that include/allocate full-duplex ROs (e.g., SBFD ROs) and/or dedicated full-duplex POs (e.g., SBFD POs) to enable UEs 115 to perform at least a portion of a MsgA 315 of a two-step RACH procedure within full-duplex slots 325. Such configurations and signaling described herein may enable the UE 115-b to perform RACH procedures for random access (and/or other use cases) within SBFD slots/symbols while in RRC connected, RRC idle, and/or RRC inactive states.
For example, as shown in FIG. 3, the random access configuration 310 may include a RACH configuration that includes/allocates a set of full-duplex (e.g., SBFD) ROs within the uplink sub-band 330 of the second slot 325-b. Additionally, or alternatively, the random access configuration 310 may include a PUSCH configuration that includes/allocates a set of full-duplex (e.g., SBFD) POs (e.g., PUSCH resources) within the uplink sub-band 330 of the third slot 325-c. In this regard, the random access configuration 310 may enable the UE 115-a to transmit a preamble of MsgA 315 within an RO of the second slot 325-b, and to transmit a payload of MsgA 315 within a PO of the PUSCH resources within the third slot 325-c. Thus, according to aspects described herein, the UE 115-b may be able to transmit (at least a portion) of MsgA 315 within the SBFD slots 325-b, 325-c, 325-d, instead of having to wait to transmit MsgA 315 within the half-duplex uplink slot 325-e.
In this regard, aspects of the present disclosure may enable RACH procedures to be performed (at least partially) within SBFD symbols (e.g., uplink sub-band 330) . Enabling RACH messages (e.g., MsgA 315, MsgB 320) to be communicated within full-duplex slots 325 (e.g., SBFD slots 325) may improve uplink coverage enhancement, as UEs 115 may be able to utilize the uplink sub-band 330 in consecutive SBFD slots 325 to enable RACH and MsgA 315 PUSCH repetition and frequency hopping, which may enhance uplink coverage for initial access. Further, techniques described herein may improve RACH capacity. In particular, configuring additional ROs within the uplink sub-band 330 may improve RACH capacity (e.g., improve a quantity of devices that are able to perform RACH procedures) . Moreover, configuring additional ROs within the uplink sub-band 330 may reduce the probability of contention-based collisions within the resources 335 of the half-duplex uplink slot 325-e, thereby enabling more UEs 115 to perform RACH procedures and access the network. Lastly, techniques described herein may reduce latency associated with RACH procedures and initial access and handover, particularly when Layer 1 (L1) and/or Layer 2 (L2) mobility is adopted. In particular, allocating resources 340 within the SBFD slots 325 may enable the UE 115-b to transmit MsgA 315 earlier (e.g., prior to the half-duplex uplink slot 325-e) , thereby reducing a latency of the RACH procedure.
Details regarding the example random access configurations 310 that enable RACH procedures to be performed within full-duplex slots (e.g., SBFD slots) are further shown and described in FIG. 4.
FIG. 4 shows an example of a resource configuration 400 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure. In some examples, aspects of the resource configuration 400 may implement, or be implemented by, aspects of the wireless communications system 100, the two-step RACH procedure configuration 200, the wireless communications systems 300, or any combination thereof.
In particular, the resource configuration 400 illustrates various implementations 405 for a two-step RACH procedure that utilize dedicated SBFD resources, as described previously herein. That is, the resource configuration 400 illustrates different implementations 405 of the random access configuration 310 shown and described in FIG. 3 that utilize SBFD-dedicated MsgA resource configurations.
At a high level, the first implementation 405-a of the random access configuration for SBFD-dedicated MsgA resources includes SBFD-dedicated PUSCH resources for POs (e.g., SBFD-dedicated PO resources within SBFD slots for transmitting payloads of MsgA) . That is, a random access configuration in accordance with the first implementation 405-a may include an SBFD-dedicated PUSCH configuration including POs within SBFD slots in addition to the common (e.g., legacy, TDD/half-duplex) RACH configuration including ROs within half-duplex uplink slots, the PUSCH configuration including POs within legacy/TDD half-duplex uplink slots.
Comparatively, the second implementation 405-b includes additional SBFD-dedicated RACH resources for ROs (e.g., SBFD-dedicated RO resources within SBFD slots for transmitting preambles of MsgA) . That is, a random access configuration in accordance with the second implementation 405-b may include an SBFD-dedicated RACH configuration including ROs within SBFD slots (in addition to a common RACH configuration including ROs within legacy/TDD half-duplex slots) , as well as a common (e.g., legacy, TDD/half-duplex) PUSCH configuration including POs within half-duplex uplink slots.
Lastly, the third implementation 405-c includes both (1) SBFD-dedicated RACH resources for ROs, and (2) SBFD-dedicated PUSCH resources for POs (e.g., SBFD-dedicated RO/PO resources within SBFD slots for transmitting preambles and payloads of MsgA) . That is, a random access configuration in accordance with the third implementation 405-c may include a common RACH configuration that includes common ROs within half-duplex uplink slots, an SBFD RACH configuration that includes SBFD-dedicated ROs within SBFD slots, a common PUSCH configuration that includes common POs within half-duplex uplink slots, and an SBFD PUSCH configuration that includes SBFD-dedicated POs within SBFD slots.
For the purposes of the present disclosure, the terms “common RO, ” “common PO, ” and like terms, may be used to refer to resources within half-duplex TDD slots that may be used by both half-duplex (e.g., “legacy” ) and full-duplex (e.g., SBFD-aware) UEs 115. As such, “common ROs/POs” may also be referred to as “legacy/TDD” ROs/POs. Comparatively, the terms “full-duplex RO, ” “full-duplex PO, ” “SBFD RO, ” “SBFD PO, ” and like terms, may be used to refer to resources within full-duplex slots (e.g., SBFD slots) that may be used by full-duplex-aware UEs 115. In this regard, because “full-duplex ROs/POs” are located within full-duplex slots (e.g., SBFD slots) , such “full-duplex ROs/POs” may not be usable by half-duplex (e.g., “legacy” ) UEs 115.
Each of the respective implementations 405 of the random access configuration for SBFD-dedicated MsgA resources will are described in further detail herein.
Reference will now be made to the first implementation 405-a illustrated in FIG. 4. As described previously herein, the first implementation 405-a of a random access configuration may allocate resources within a set of slots 410 or TTIs that are usable for exchanging signaling associated with a two-step RACH procedure, such as a first slot 410-a, a second slot 410-b, a third slot 410-c, a fourth slot 410-d, and a fifth slot 410-e. In this example, the first slot 410-a and the fifth slot 410-e may include half-duplex uplink slots (e.g., TDD UL slots) that include only uplink resources. Comparatively, the second slot 410-b, the third slot 410-c, and the fourth slot 410-d may include full-duplex slots (e.g., FDD UL/DL slots) that include both uplink and downlink resources (e.g., SBFD slots) . For example, as shown in FIG. 4, the slots 410-b, 410-c, and 410-d may include downlink resources that are split by an uplink sub-band that includes uplink resources (e.g., uplink sub-band 330 illustrated in FIG. 3) .
A random access configuration in accordance with the first implementation 405-a may include a RACH configuration that includes resources for common ROs 415 within the half-duplex uplink slot 410-a. In accordance with the first implementation 405-a, the random access configuration may further include one or more PUSCH configurations (e.g., common PUSCH configuration and SBFD PUSCH configuration) that include (1) common POs 420 within the half-duplex uplink slot 410-e, and (2) full-duplex POs (e.g., SBFD POs 425-a) within the full duplex slot 410-b and/or the full-duplex slot 410-c. Preambles of the set of common ROs 415 may be mapped to both the set of common POs 420 and the set of SBFD POs 425-a, as shown in the first implementation 405-a. In this example, the PUSCH slots 410-b and 410-c including the earliest SBFD POs 425-a may be associated with a first time domain offset 430-a relative to the PRACH slot 410-a including common ROs 415, and the PUSCH slot 410-e including the set of common POs 420 may be associated with a second time domain offset 430-b relative to the PRACH slot 410-a including the common ROs 415.
Reference will now be made to the second implementation 405-b illustrated in FIG. 4. A random access configuration in accordance with the second implementation 405-b may include a PUSCH configuration that includes resources for common POs 420 within the half-duplex uplink slot 410-e. In accordance with the second implementation 405-b, the random access configuration may further include one or more RACH configurations (e.g., common RACH configuration and SBFD RACH configuration) that includes (1) common ROs 415 within the half-duplex uplink slot 410-a, and (2) full-duplex ROs (e.g., SBFD ROs 435-a) within the full-duplex slot 410-c. Preambles of the set of common POs 420 may be mapped to both the set of common ROs 415 and the set of SBFD ROs 435-a, as shown in the second implementation 405-b. In this example, the PUSCH slots 410 and PRACH slots 410 associated with the set of common ROs 415 and the set of SBFD ROs 435-a may be associated with different time domain offsets 430-b, 430-c, as described previously herein.
Reference will now be made to the third implementation 405-c illustrated in FIG. 4. A random access configuration in accordance with the third implementation 405-c may include one or more RACH configurations (e.g., common RACH configuration and SBFD RACH configuration) that include (1) common ROs 415 within the half-duplex uplink slot 410-a, and (2) full-duplex ROs (e.g., SBFD ROs 435-a) within the full-duplex slot 410-b. In accordance with the third implementation 405-c, the random access configuration may further include one or more PUSCH configurations (e.g., common PUSCH configuration and SBFD PUSCH configuration) that include (1) common POs 420 within the half-duplex uplink slot 410-e, and (2) full-duplex POs (e.g., SBFD POs 425-b) within the full-duplex slot 410-c. In some cases, preambles of the set of common ROs 415 may be mapped to the set of common POs 420, where the preambles of the set of SBFD ROs 435-b may be mapped to the set of SBFD POs 425-b. In this example, the random access configuration may define separate time domain offsets 430-b, 430-d between the PUSCH/PRACH slots 410 of the common ROs 415 and the common POs 420, and between the PUSCH/PRACH slots 410 of the SBFD ROs 435-b and the SBFD POs 425-b, as described previously herein. In this example, the PUSCH slots 410 and PRACH slots 410 associated with the respective ROs and POs may be associated with different time domain offsets 430-b, 430-d, as described previously herein.
The various implementations 405 are associated with respective advantages and disadvantages. For example, because the first implementation 405-a includes the extra set of SBFD POs 425-a, the first implementation 405-a may reduce MsgA-PUSCH collisions (e.g., reduce collisions of MsgA payloads) . Moreover, the first implementation 405-a may reduce the latency of MsgA-PUSCH by enabling SBFD-aware UEs 115 to transmit MsgA-PUSCH (e.g., MsgA payload) within the set of SBFD POs 425-a rather than within the common POs 420. Further, the first implementation 405-a may enable UEs 115 to use different MCS values, frequency resources, and/or Tx powers for PUSCH in SBFD symbols, and may improve PUSCH coverage (e.g., PUSCH repetition) across multiple slots 410.
Comparatively, because the second implementation 405-b includes the extra set of SBFD ROs 435-a, the second implementation 405-b may reduce MsgA-RACH collisions (e.g., reduce collisions of MsgA preambles) . Moreover, the second implementation 405-b may reduce the latency of MsgA-PRACH and improve coverage (e.g., long sequences) or repetition. Finally, because the third implementation 405-c includes extra sets of SBFD ROs 435-b and SBFD POs 425-b, the third implementation 405-c may be associated with the same advantages as those applicable to the first implementation 405-a and the second implementation 405-b.
The RACH configurations (e.g., configurations of ROs 415, 435) and the PUSCH configurations (e.g., configurations of POs 420, 425) of the respective implementations 405-a, 405-b, and 405-c are summarized in Table 1 below:

Table 1: Summary of Implementations for SBFD-Dedicated Random Access Configurations
Each of the respective implementations 405 shown in FIG. 4 and Table 1 above are described in further detail herein. In particular, the first implementation 405-a is further shown and described in FIG. 5, the second implementation 405-b is further shown and described in FIG. 6, and the third implementation is further shown and described in FIG. 7.
FIG. 5 shows an example of a resource configuration 500 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure. In some examples, aspects of the resource configuration 500 may implement, or be implemented by, aspects of the wireless communications system 100, the two-step RACH procedure configuration 200, the wireless communications systems 300, the resource configuration 400, or any combination thereof.
In particular, the resource configuration 500 shown and described in FIG. 5 illustrates example resource configurations associated with the first implementation 405-a shown and described in FIG. 4. At a high level, the first implementation 405-a of the random access configuration for SBFD-dedicated MsgA resources includes SBFD-dedicated PUSCH resources for POs (e.g., SBFD-dedicated PO resources within SBFD slots for transmitting payloads of MsgA) . That is, a random access configuration in accordance with the first implementation 405-a may include a common (e.g., legacy, TDD/half-duplex) RACH configuration including ROs within half-duplex uplink slots, as well as an SBFD-dedicated PUSCH configuration including POs within SBFD slots (in addition to a common PUSCH configuration including POs within legacy/TDD half-duplex uplink slots) .
Referring to diagram 505-a in FIG. 5, the first implementation 405-a of a random access configuration may allocate resources within a set of slots 510 or TTIs that are usable for exchanging signaling associated with a two-step RACH procedure, such as a first slot 510-a, a second slot 510-b, a third slot 510-c, a fourth slot 510-d, and a fifth slot 510-e. In this example, the first slot 510-a and the fifth slot 510-e may include half-duplex uplink slots (e.g., TDD UL slots) that include only uplink resources. Comparatively, the second slot 510-b, the third slot 510-c, and the fourth slot 510-d may include full-duplex slots (e.g., FDD UL/DL slots) that include both uplink and downlink resources (e.g., SBFD slots) . For example, as shown in FIG. 5, the slots 510-b, 510-c, and 510-d may include downlink resources that are split by an uplink sub-band that includes uplink resources (e.g., uplink sub-band 330 illustrated in FIG. 3) .
Continuing with reference to the diagram 505-a in FIG. 5, a random access configuration in accordance with the first implementation 405-a may include a RACH configuration that includes resources for common ROs 515-a within the half-duplex uplink slot 510-a. In accordance with the first implementation 405-a, the random access configuration may further include a common PUSCH configuration that includes common POs 520-a within the half-duplex uplink slot 510-e, and an SBFD PUSCH configuration that includes full-duplex POs (e.g., SBFD POs 525-a) within the full duplex slot 510-c and/or the full-duplex slot 510-d. Preambles of the set of common ROs 515-a may be mapped to both the set of common POs 520-a and the set of SBFD POs 525-a, as shown in diagram 505-a. In this example, the PUSCH slot 510-c including the earliest SBFD POs 525-a may be associated with a first time domain offset 530-a relative to the PRACH slot 510-a including the common ROs 515-a, and the PUSCH slot 510-e including the set of common POs 520-a may be associated with a second time domain offset 530-b relative to the PRACH slot 510-a including the common ROs 515-a.
Continuing with reference to diagram 505-a in FIG. 5, an SBFD-aware UE 115 may be configured with SBFD-dedicated MsgA-PUSCH configuration (s) , as shown in diagram 505-a. Further, SBFD PUSCH configurations may be associated with sub-configurations corresponding to different preamble groups. In particular, a UE 115 may be configured with up to two MsgA-PUSCH configurations associated with the respective preamble groups (e.g., first PUSCH sub-configuration associated with MsgA-preamble Group A, and a second PUSCH sub-configuration associated with MsgA-preamble Group B) . As shown in the diagram 505-a, the SBFD-dedicated MsgA PUSCH configuration (s) (e.g., SBFD POs 525-a) and legacy TDD MsgA-PUSCH configuration (s) (e.g., common POs 520-a) may be associated with (e.g., mapped to) the same/common pool of preambles of MsgA RACH (e.g., common ROs 515-a) .
In some aspects, the mapping between one or multiple PRACH preambles and a valid PO 520-a, 525-a associated with a DMRS resource is each per PUSCH configuration. The number of preamble (s) mapped to a valid PO (NPreamble) may be determined for each PUSCH configuration (e.g., TDD/half-duplex PUSCH configuration, SBFD PUSCH configuration) within the same RACH association pattern period, as illustrated in Equation 1 and Equation 2 below:
Npreamble (TDD) =ceil (Tpreamble/TPUSCH)            (1)
Npreamble (SBFD) =ceil (Tpreamble/TPUSCH-SBFD)               (2)
where TPUSCH (SBFD) is a total number of valid SBFD POs 525-a per association pattern period multiplied by the number of DMRS resource indexes per valid PO.
In some aspects, PUSCH configuration (s) for the SBFD POs 525-a and the common POs 520-a of the first implementation 405-a may be signaled or otherwise configured at a UE 115 in a number of ways. For example, in accordance with a first option, the configuration of the SBFD-dedicated MsgA PUSCH configuration (e.g., PUSCH configuration for the SBFD POs 525-a) for the first implementation 405-a may be signaled/configured via an additional IE for MsgA-PUSCH within the MsgA-common configuration, as shown below:
MsgA-ConfigCommon-r16: : = SEQUENCE {
· rach-ConfigCommonTwoStepRA-r16 ---RACH-ConfigCommonTwoStepRA-r16,
· msgA-PUSCH-Config-r16 ---MsgA-PUSCH-Config-r16 ---OPTIONAL --Cond InitialBWPConfig
· msgA-PUSCH-Config-SBFD ---MsgA-PUSCH-Config-r16 ---OPTIONAL --Cond InitialBWPConfig}
Comparatively, in accordance with a second option, the configuration of the SBFD-dedicated MsgA PUSCH configuration (e.g., PUSCH configuration for the SBFD POs 525-a) for the first implementation 405-a may be signaled/configured via an additional IE for Msg-PUSCH-Resource Group A/B, as shown below:
MsgA-PUSCH-Config-r16: : = SEQUENCE {
· msgA-PUSCH-ResourceGroupA-r16 ---MsgA-PUSCH-Resource-r16 ---OPTIONAL, --Cond InitialBWPConfig
· msgA-PUSCH-ResourceGroupB-r16 ---MsgA-PUSCH-Resource-r16 ---OPTIONAL, --Cond GroupBConfigured
· msgA-PUSCH-ResourceGroupA-SBFD ---MsgA-PUSCH-Resource-r16 ---OPTIONAL, --Cond InitialBWPConfig
· msgA-PUSCH-ResourceGroupB-SBFD ---MsgA-PUSCH-Resource-r16 ---OPTIONAL, --Cond GroupBConfigured
· msgA-TransformPrecoder-r16 ---ENUMERATED {enabled, disabled} OPTIONAL, --Need R
· msgA-DataScramblingIndex-r16 ---INTEGER (0.1023) ---OPTIONAL,--Need S
· msgA-DeltaPreamble-r16 ---INTEGER (-1.6) ---OPTIONAL --NeedR}
In some aspects, each of the respective common ROs 515-a, common POs 520-a, and the SBFD POs 525-a may be mapped to one or more SSBs and/or preambles. When performing a RACH procedure, a UE 115 may monitor resources associated with a set of SSBs (e.g., SSB #0, SSB #1, and SSB #2) , and may determine channel quality metrics associated with the respective SSBs. The UE 115 may identify the SSB with the highest quality, and may transmit a preamble of MsgA via a common RO 515 of the set of common ROs 515-a that corresponds to the selected SSB. Subsequently, to transmit the payload of MsgA, the UE 115-a may use a common PO 520 of the set of common POs 520-a that is associated with the preamble transmitted in the common RO 515, and/or an SBFD PO 525 of the set of SBFD POs 525-a that is associated with the preamble transmitted in the common RO 515. That is, the UE 115 may use an RO and PO that pair that corresponds to the same SSB/preamble in order to transmit MsgA.
For SBFD-aware UEs 115, the selection to use a PO from either the set of common POs 520-a or the set of SBFD POs 525-a may be based on a number of criteria, including a relative timing of the common POs 520-a and SBFD POs 525-a in the time domain, based on measured/predicted channel quality metrics of the slots 510 including the respective POs, based on RRC configuration (e.g., pre-configuration by the network) , based on a type of UE 115 (e.g., full-duplex UE 115, half-duplex UE 115) , based on PUSCH transmission (Tx) power relative to a threshold PUSCH Tx power, or any combination thereof. For example, in cases where the UE 115 transmits the MsgA preamble in common RO2, the SBFD-aware UE 115 may select to transmit the MsgA payload within SBFD PO3 and/or SBFD PO4 based on such SBFD POs occurring before the common POs 520-a in the time domain. By way of another example, the UE 115 may select whether to use common POs 520-a or SBFD POs 525-a based on an RSRP threshold and/or measured RSRP of the selected SSB-index. By way of another example, the selection between common POs 520-a or SBFD POs 525-a may be based on UE type, where SBFD-aware UEs 115 select SBFD POs 525-a, and half-duplex UEs 115 select common POs 520-a.
In some aspects, the validity (or lack thereof) of SBFD POs 525 may be based on the type of slot/TTI that the respective SBFD POs 525 are positioned within.  For example, in accordance with a first option, SBFD POs 525 may be determined to be valid only when they are positioned within an uplink sub-band of an SBFD slot 510 (such as the set of SBFD POs 525-a within slots 510-c and 510-d) . For example, referring to the second diagram 505-b in FIG. 5, a PUSCH configuration may include a set of SBFD POs 525-b within the SBFD slot 510-d and the half-duplex uplink slot 510-e. In accordance with the first option, SBFD POs 1–3 may be determined to be valid based on POs 1–3 being positioned within uplink symbols of the SBFD slot 510-d, where SBFD POs 4–6 may be determined to be invalid based on POs 4–6 being positioned within the half-duplex uplink slot 510-e.
Comparatively, in accordance with a second option, SBFD POs 525 may be determined to be valid regardless of whether they are positioned within SBFD-symbols/slots or half-duplex uplink symbols/slots. For example, referring to the second diagram 505-b in FIG. 5, all the SBFD POs 1–6 may be valid in accordance with the second option (regardless of the type of slot 510-d, 510-e) .
In some cases, if there are valid SBFD POs 525 that overlap in the time domain with TDD/common POs 520 (as shown in the second diagram 505-b) , then the preamble mapping to the respective POs may be performed such that preamble mapping to legacy TDD POs (e.g., common POs 520-a) are done first (e.g., NPreamble to PO PRU=4) , and where preamble mapping to SBFD-dedicated POs (e.g., SBFD POs 525) are done next (e.g., NPreamble to PO PRU=2) . For the preamble mapping to SBFD POs 525, the preamble mapping may be first performed for overlapping SBFD POs 525 as a subset of preambles associated with the same SSB (objective to have consistent mapping with legacy POs) , were remaining preamble mapping may for non-overlapping SBFD POs 525 may be performed next.
For instance, referring to the second diagram 505-b, the common POs 520-a may be mapped to SSBs/preambles first such that common PO1 maps to SSB #0 and preambles (0, 1, 2, 3) , common PO2 maps to SSB #1 and preambles (4, 5, 6, 7) , and common PO3 maps to SSB #2 and preambles (8, 9, 10, 11) . Subsequently, the SBFD POs 525-b that overlap in time with the common POs 520-a (e.g., SBFD POs 4–6) may be mapped next, such that SBFD PO4 maps to SSB #0 and preambles (0, 1) , SBFD PO5 maps to SSB #1 and preambles (4, 5) , and SBFD PO6 maps to SSB #2 and preambles (8, 9) . Then the SBFD POs 525-b within the SBFD slot 510-d may be performed last, such that SBFD PO1 maps to SSB #0 and preambles (2, 3) , SBFD PO2 maps to SSB #1 and preambles (6, 7) , and SBFD PO3 maps to SSB #2 and preambles (10, 11) . Using this mapping scheme (e.g., by mapping common POs 520-a first, then temporally-overlapping SBFD POs 525-b, then non-overlapping SBFD POs 525-b) , it may be ensured that MsgA payloads received in temporally-overlapping POs (e.g., within common PO1 and SBFD PO4) correspond to the same SSB and preambles (and therefore to the same common RO 515) .
In some aspects, in order to prevent uplink resource fragmentation, the RB start of the dedicated SBFD POs 525 occurring in non-SBFD symbols (e.g., SBFD POs within half-duplex uplink slots) may be configured with a different RB start/offset as compared to SBFD POs 525 within SBFD slots. For example, referring to the third diagram 505-c in FIG. 5, a PUSCH configuration may include a set of SBFD POs 525-c, including a first subset of SBFD POs 525 (e.g., POs 1–6) within an SBFD slot 510-f, and a second subset of SBFD POs 525 (e.g., POs 7–18) within a half-duplex uplink slot 510-g. In this case, the first subset of SBFD POs 525 (e.g., POs 1–6) may be associated with a first frequency start 530-a (e.g., SBFD RB start/offset in the frequency domain) , and the second subset of SBFD POs 525 (e.g., POs 7–18) may be associated with a second frequency start 530-b (e.g., TDD/common RB start/offset in the frequency domain) .
In addition, in cases where the quantity of SBFD POs 525 in SBFD slots is different from the quantity of SBFD POs 525 in half-duplex uplink slots, then the MsgA-PUSCH may be configured with two parameters for half-duplex and SBFD slots (e.g., to indicate the different quantities) . For example, as shown in the third diagram 505-c, the SBFD slot 510-f may include two FDMed POs (e.g., two rows of SBFD POs) , and the half-duplex uplink slot 510-g may include four FDMed POs (e.g., four rows of SBFD POs) . In some cases, the respective PUSCH configurations may indicate the RB frequency start/offset values and/or the quantities of FDMed POs within the TDD/SBFD slots 510.
FIG. 6 shows an example of a resource configuration 600 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure. In some examples, aspects of the resource configuration 600 may implement, or be implemented by, aspects of the wireless communications system 100, the two-step RACH procedure configuration 200, the wireless communications systems 300, the resource configurations 400-500, or any combination thereof.
In particular, the resource configuration 600 shown and described in FIG. 6 illustrates example resource configurations associated with the second implementation 405-b shown and described in FIG. 4.
At a high level, the second implementation 405-b includes SBFD-dedicated RACH resources for ROs (e.g., SBFD-dedicated RO resources within SBFD slots for transmitting preambles of MsgA) . That is, a random access configuration in accordance with the second implementation 405-b may include an SBFD-dedicated RACH configuration including ROs within SBFD slots (in addition to a common RACH configuration including ROs within legacy/TDD half-duplex slots) , as well as a common (e.g., legacy, TDD/half-duplex) PUSCH configuration including POs within half-duplex uplink slots.
Referring to diagram 605-a in FIG. 6, the second implementation 405-b of a random access configuration may allocate resources within a set of slots 610 or TTIs that are usable for exchanging signaling associated with a two-step RACH procedure, such as a first slot 610-a, a second slot 610-b, a third slot 610-c, a fourth slot 610-d, and a fifth slot 610-e. In this example, the first slot 610-a and the fifth slot 610-e may include half-duplex uplink slots (e.g., TDD UL slots) that include only uplink resources. Comparatively, the second slot 610-b, the third slot 610-c, and the fourth slot 610-d may include full-duplex slots (e.g., FDD UL/DL slots) that include both uplink and downlink resources (e.g., SBFD slots) . For example, as shown in FIG. 6, the slots 610-b, 610-c, and 610-d may include downlink resources that are split by an uplink sub-band that includes uplink resources (e.g., uplink sub-band 330 illustrated in FIG. 3) .
Continuing with reference to the diagram 605-a in FIG. 6, a random access configuration in accordance with the second implementation 405-b may include a common RACH configuration that includes resources for common ROs 615-a within the half-duplex uplink slot 610-a, and an SBFD RACH configuration including SBFD ROs 635-a within the SBFD slot 610-b. In accordance with the second implementation 405-b, the random access configuration may further include a PUSCH configuration that includes common POs 620-a within the half-duplex uplink slot 610-e. Preambles of the set of common POs 620-a may be mapped to both the set of common ROs 615-a and the set of SBFD ROs 635-a, as shown in diagram 605-a. In this example, the PUSCH slot 610-e including the set of common POs 620-a may be associated with a first time domain offset 630-a relative to the PRACH slot including the SBFD ROs 635-a, and a second time domain offset 630-b relative to the PRACH slot 610-a including the common ROs 615-a, as described previously herein.
Continuing with reference to diagram 605-b, an SBFD-aware UE 115 may be configured with SBFD-dedicated MsgA-RACH configuration (s) for two-step RACH random access procedures. The use of different preamble sequences (e.g., long sequence) in SBFD symbols/slots 610 (e.g., the inclusion of SBFD ROs 635-a) may improve coverage and reduce preamble collision in legacy/TDD ROs (e.g., common ROs 615) . The preambles of the SBFD-dedicated RACH configuration (s) (e.g., preambles of the SBFD ROs 635-a) and the preambles of legacy/TDD MsgA-RACH (e.g., preambles of the common ROs 615-a) may be mapped to the same resources of MsgA-POs (e.g., common POs 620-a) . The mapping of the TDD/SBFD preambles to a PUSCH resource of a common PO 620 may be performed to ensure that selected preambles of both ROs (e.g., preambles of the common ROs 615-a and the SBFD ROs 635-a) are associated with the same SSB index. For example, the common RO1 615 and the SBFD RO1 635 may be mapped to the same common PO1 620, and may therefore be associated with the same SSB index (e.g., SSB #0) .
For each RACH configuration or set of RACH resources (e.g., set of common ROs 615-a, set of SBFD ROs 635-a) , the mapping between one or multiple PRACH preambles of RO and a PO associated with a DMRS resource may be done in sequence (e.g., TDD/common ROs 615 mapped first, followed by mapping for SBFD ROs 635) . The number of preamble (s) mapped to a valid PO Npreamble may be determined separately for common ROs 615-a and SBFD ROs 635-a within each RACH association pattern period.
In some aspects, RACH configuration (s) for the common ROs 615-a and the SBFD ROs 635-a of the second implementation 405-b may be signaled or otherwise configured at a UE 115 in a number of ways. For example, in accordance with a first option, the configuration of the SBFD-dedicated MsgA RACH configuration (e.g., RACH configuration for the SBFD ROs 635-a) for the second implementation 405-b may be signaled/configured via an additional IE for MsgA-RACH within the MsgA-common configuration, as shown below:
MsgA-ConfigCommon-r16: : = SEQUENCE {
· rach-ConfigCommonTwoStepRA-r16 ---RACH-ConfigCommonTwoStepRA-r16,
· rach-ConfigCommonTwoStepRA-SBFD ---RACH-ConfigCommonTwoStepRA-r16,
· msgA-PUSCH-Config-r16 ---MsgA-PUSCH-Config-r16 ---OPTIONAL --Cond InitialBWPConfig}
Comparatively, in accordance with a second option, the configuration of the SBFD-dedicated MsgA RACH configuration (e.g., RACH configuration for the SBFD ROs 635-a) for the second implementation 405-b may be signaled/configured via the same IE for RACH-ConfigCommonTwoStepRA and some duplicated parameters (e.g., rach-ConfigGenericTwoStepRA or power control parameters) for SBFD-dedicated configuration, as shown below:
RACH-ConfigCommonTwoStepRA-r16: : = SEQUENCE {
· rach-ConfigGenericTwoStepRA-r16 ---RACH-ConfigGenericTwoStepRA-r16,
· rach-ConfigGenericTwoStepRA-SBFD ---RACH-ConfigGenericTwoStepRA-r16,
· msgA-TotalNumberOfRA-Preambles-r16 ---INTEGER (1.63) ---OPTIONAL, --Need S}
In some aspects, each of the respective common ROs 615-a, SBFD ROs 635-a, and common POs 620-a may be mapped to one or more SSBs and/or preambles. When performing a RACH procedure, a UE 115 may monitor resources associated with a set of SSBs (e.g., SSB #0, SSB #1, and SSB #2) , and may determine channel quality metrics associated with the respective SSBs. The UE 115 may identify the SSB with the highest quality, and may transmit a preamble of MsgA via (1) a common RO of the set  of common ROs 615-a that corresponds to the selected SSB, or (2) an SBFD RO of the set of SBFD Ros 635-a that corresponds to the selected SSB. Subsequently, to transmit the payload of MsgA, the UE 115 may use a common PO of the set of common POs 620-a that corresponds to the common RO used to transmit the preamble. That is, the UE 115 may use an RO and PO that pair that corresponds to the same SSB in order to transmit MsgA.
For SBFD-aware UEs 115, the selection to use an RO from either the set of common ROs 615-a or the set of SBFD ROs 635-a may be based on a number of criteria, including a relative timing of the common ROs 615-a and SBFD ROs 635-a in the time domain, based on measured/predicted channel quality metrics of the slots 610 including the respective ROs, based on RRC configuration (e.g., pre-configuration by the network) , based on a type of UE 115 (e.g., full-duplex UE 115, half-duplex UE 115) , PUSCH Tx power relative to a threshold PUSCH Tx power, or any combination thereof. For example, the SBFD-aware UE 115 may select to transmit the MsgA preamble within common RO3 (instead of SBFD RO3) based on the common RO3 occurring before the SBFD RO3 in the time domain. By way of another example, the UE 115 may select whether to use common ROs 615-a or SBFD ROs 635-a based on an RSRP threshold and/or measured RSRP of the selected SSB-index. By way of another example, the selection between common ROs 615-a or SBFD ROs 635-a may be based on UE type, where SBFD-aware UEs 115 select SBFD ROs 635-a, and half-duplex UEs 115 select common ROs 615-a.
In some aspects, the validity (or lack thereof) of SBFD ROs 635 may be based on the type of slot/TTI that the respective SBFD ROs 635 are positioned within. For example, in accordance with a first option, SBFD ROs 635 may be determined to be valid only when they are positioned within an uplink sub-band of an SBFD slot 610 (such as the set of SBFD ROs 635-a within slot 610-b) . For example, referring to the second diagram 605-b in FIG. 6, a RACH configuration (s) may include a set of SBFD ROs 635-b within the SBFD slot 610-f and the half-duplex uplink slot 610-g. In accordance with the first option, SBFD ROs 1–3 may be determined to be valid based on ROs 1–3 being positioned within uplink symbols of the SBFD slot 610-f, where SBFD ROs 4–6 may be determined to be invalid based on ROs 4–6 being positioned within the half-duplex uplink slot 610-g.
Comparatively, in accordance with a second option, SBFD ROs 635 may be determined to be valid regardless of whether they are positioned within SBFD-symbols/slots or half-duplex uplink symbols/slots. For example, referring to the second diagram 605-b in FIG. 6, all the SBFD ROs 1–6 may be valid in accordance with the second option (regardless of the type of slot 610-f, 610-g) .
In some cases, if there are valid SBFD ROs 635 that overlap in the time domain with TDD/common ROs 615 (as shown in the second diagram 605-b) , then the preamble mapping to the respective ROs may be performed such that SSB-to-RO mapping to legacy/TDD ROs (e.g., common ROs 615) are done first, then SSB-to-RO mapping to SBFD-dedicated ROs (e.g., SBFD ROs 635) are done next, and where non-overlapping SBFD ROs 635 are performed last. The temporally-overlapping SBFD ROs 635 may be performed prior to non-overlapping SBFD ROs 635 to ensure consistent SSB mappings (e.g., so that temporally-overlapping ROs are mapped to the same SSBs) .
For instance, referring to the second diagram 605-b, and assuming single SSB-RO mapping, the mapping for the set of common ROs 615-b may be done first, such that common RO1 maps to SSB #0, common RO2 maps to SSB #1, and common RO3 maps to SSB #2. Subsequently, the mapping for the set of temporally-overlapping SBFD ROs 635 (e.g., ROs 4–6) may be performed next to guarantee the same SSBs are mapped to the temporally-overlapping ROs (e.g., such that SBFD RO4 maps to SSB #0, SBFD RO5 maps to SSB #1, and SBFD RO6 maps to SSB #2) . Finally, the mapping for the non-overlapping SBFD ROs 635 (e.g., ROs 1–3) may be performed (e.g., independent mapping or distribution) .
FIG. 7 shows an example of a resource configuration 700 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure. In some examples, aspects of the resource configuration 700 may implement, or be implemented by, aspects of the wireless communications system 100, the two-step RACH procedure configuration 200, the wireless communications systems 300, the resource configurations 400-600, or any combination thereof.
In particular, the resource configuration 700 shown and described in FIG. 7 illustrates example resource configurations associated with the third implementation 405-c shown and described in FIG. 4. At a high level, the third implementation 405-c the third implementation 405-c includes both (1) SBFD-dedicated RACH resources for ROs, and (2) SBFD-dedicated PUSCH resources for POs (e.g., SBFD-dedicated RO/PO resources within SBFD slots for transmitting preambles and payloads of MsgA) . That is, a random access configuration in accordance with the third implementation 405-c may include a RACH configuration that includes both (1) SBFD-dedicated ROs within SBFD slots, and (2) common ROs within half-duplex uplink slots, as well as a PUSCH configuration that includes both (1) SBFD-dedicated POs within SBFD slots, and (2) common POs within half-duplex uplink slots.
Referring to diagram 705-a in FIG. 7, the third implementation 405-c of a random access configuration may allocate resources within a set of slots 710 or TTIs that are usable for exchanging signaling associated with a two-step RACH procedure, such as a first slot 710-a, a second slot 710-b, a third slot 710-c, a fourth slot 710-d, and a fifth slot 710-e. In this example, the first slot 710-a and the fifth slot 710-e may include half-duplex uplink slots (e.g., TDD UL slots) that include only uplink resources. Comparatively, the second slot 710-b, the third slot 710-c, and the fourth slot 710-d may include full-duplex slots (e.g., FDD UL/DL slots) that include both uplink and downlink resources (e.g., SBFD slots) . For example, as shown in FIG. 5, the slots 710-b, 710-c, and 710-d may include downlink resources that are split by an uplink sub-band that includes uplink resources (e.g., uplink sub-band 330 illustrated in FIG. 3) .
Continuing with reference to the diagram 705-a in FIG. 7, a random access configuration in accordance with the third implementation 405-c may include a first RACH configuration (e.g., legacy/TDD RACH configuration) that includes resources for common ROs 715 within the half-duplex uplink slot 710-a, and a second RACH configuration (e.g., SBFD RACH configuration) that includes resources for full-duplex ROs 735 within the SBFD slot 710-b. In accordance with the third implementation 405-c, the random access configuration may further include a first PUSCH configuration (e.g., legacy/TDD PUSCH configuration) that includes common POs 720 within the half-duplex uplink slot 710-e, and a second PUSCH configuration (e.g., SBFD PUSCH configuration) that includes resources for full-duplex POs (e.g., SBFD POs 725) within the full duplex slot 710-c. The set of common POs 720 may be mapped to the preambles of the set of common ROs 715. Similarly, the set of full-duplex POs 725 may be mapped to the preambles of the set of full-duplex ROs 735. In some aspects, a separate mapping (with respect to legacy/TDD two-step RACH procedures) between one or multiple PRACH preambles and a PO 720, 725 associated with a DMRS resource may be implemented for each PUSCH configuration.
In some aspects, the PUSCH slot 710-c including the set of SBFD POs 725 may be associated with a first time domain offset 730-a relative to the PRACH slot 710-b including the SBFD ROs 735. Similarly, the PUSCH slot 710-e including the common POs 720 may be associated with a second time domain offset 730-b relative to the PRACH slot 710-a including the set of common ROs 715.
In some aspects, an SBFD-aware UE 115 may be configured with an SBFD-dedicated MsgA configuration (e.g., SBFD RACH configuration, SBFD PUSCH configuration) for two-step RACH random access procedures (Type-2 Random access) . The SBFD-dedicated MsgA configuration may include (1) an SBFD-dedicated MsgA-RACH configuration, and (2) an SBFD-dedicated MsgA-PUSCH configuration. In some aspects, the SBFD-dedicated MsgA-PUSCH configuration may include or be associated with two sub-configurations for respective preamble groups. In other words, the SBFD-dedicated MsgA-PUSCH configuration may include up to two MsgA PUSCH resource configurations (e.g., up to two sub-configuration) associated with the SBFD dedicated MsgA preamble Group A (e.g., first sub-configuration for preamble Group A) and MsgA-preamble Group B (e.g., second sub-configuration for preamble Group B) .
In some aspects, the RACH configuration (s) and the PUSCH configuration (s) for the third implementation 405-c may be signaled or otherwise configured at a UE 115 in a number of ways. For example, the respective configurations for the third implementation may be configured as part of a common random access configuration for MsgA, as shown below:
MsgA-ConfigCommon-SBFD: : = SEQUENCE {
· rach-ConfigCommonTwoStepRA-SBFD---RACH-ConfigCommonTwoStepRA,
· msgA-PUSCH-Config-SBFD ---MsgA-PUSCH-Config ---OPTIONAL --Cond InitialBWPConfig}
In some cases, preambles of SBFD-dedicated ROs 735 may additionally or alternatively be mapped to the common (e.g., TDD/legacy) POs 720, as shown in the second diagram 705-b. Using this configuration shown in the second diagram 705-b, a SBFD-aware UE 115 may be able to send PRACH (e.g., MsgA preamble) in the SBFD-dedicated ROs 715, and then send the MsgA-PUSCH (e.g., MsgA payload) in either SBFD-dedicated POs 725 or common POs 720 (e.g., the UE 115 may select the earliest PO 720, 725 to transmit the MsgA payload) . In this regard, preambles of the SBFD-dedicated ROs 735 may be mapped to (1) SBFD-dedicated POs 725 (diagram 705-a) , (2) common POs 720 (diagram 705-b) , or both.
Similarly, in additional or alternative cases, preambles of common ROs 715 (e.g., legacy/TDD ROs) can be mapped to SBFD-dedicated POs 725, as shown in diagram 705-c. In such cases, SBFD-aware UEs 115 may be able to send PRACH (e.g., MsgA preambles) via the common ROs 715 (e.g., if common ROs 715 are earlier than SBFD ROs 735) , and transmit Msg-A PUSCH (e.g., MsgA payload) via the SBFD POs 725. In this regard, preambles of the common ROs 715 may be mapped to (1) common POs 720 (diagram 705-a) , (2) SBFD POs 725 (diagram 705-c) , or both.
In this regard, in accordance with the third implementation 405-c, the UE 115 may be configured to use any combination of a common RACH configuration (e.g., legacy/TDD RACH configuration) , an SBFD-dedicated RACH configuration, common PUSCH configuration (e.g., legacy/TDD PUSCH configuration) , and an SBFD-dedicated PUSCH configuration. As such, a UE 115 configured according to the third implementation 405-c may have four separate combinations for performing a two-step RACH procedure: (Option 1 –Legacy) : TDD-MsgA-PRACH configuration + TDD-MsgA-PUSCH configuration (shown in diagram 705-a) , (Option 2 –SBFD) : SBFD-MsgA-PRACH configuration + SBFD-MsgA-PUSCH configuration (shown in diagram 705-a) , (Option 3 -Mixed #1) : SBFD-MsgA-PRACH configuration + TDD-MsgA-PUSCH configuration (shown in diagram 705-b) , and (Option 4-Mixed #2) : TDD-MsgA-PRACH configuration + SBFD-MsgA-PUSCH configuration (shown in diagram 705-c) .
In some implementations, an SBFD-dedicated MsgA configuration may not include both an SBFD-dedicated RACH configuration and an SBFD-dedicated PUSCH configuration. In such cases, the UE 115 may be configured to “fall back” to common (e.g., TDD/legacy) configurations for the RACH or PUSCH configuration. For example, in cases where the SBFD-dedicated MsgA configuration contains only an SBFD MsgA-PUSCH configuration (and is missing a SBFD RACH configuration) then the SBFD-aware UE 115 may be configured to share the same MsgA-RACH configuration of the common RACH configuration. In other words, the UE 115 may be configured to “read in” the common (e.g., legacy/TDD) MsgA RACH configuration into the SBFD-dedicated MsgA configuration.
By way of another example, in cases where the SBFD-dedicated MsgA configuration contains only an SBFD MsgA-RACH configuration (and is missing an SBFD MsgA PUSCH configuration) , then the SBFD-aware UE 115 may be configured to share the same MsgA-PUSCH configuration of common PUSCH configuration. In other words, the UE 115 may be configured to “read in” the common (e.g., legacy/TDD) MsgA PUSCH configuration into the SBFD-dedicated MsgA configuration.
In some aspects, the respective configurations (e.g., RACH configurations, PUSCH configurations) may be UE-specific (e.g., UE-dedicated) such that each UE 115 utilizes dedicated configurations, or cell-specific (e.g., cell-dedicated) such that all UEs 115 within the given cell utilize the same cell-specific configurations. In some cases, the network may indicate whether indicated configurations (e.g., RACH configurations, PUSCH configurations) are UE-specific or cell-specific.
Further, in addition to the cell-specific two-steps random access configurations (e.g., the RACH configurations and PUSCH configurations described herein for two-step RACH procedures) , SBFD-aware UEs 115 may additionally be configured with UE-dedicated two-step RACH procedures in SBFD symbols for the additional operations or use-cases, such as SI requests, PDCCH orders (e.g., CFRA or CBRA) , beam failure recovery (BFR) , mobility, and the like. In other words, the UE 115 may be configured with different random access configurations that are usable for different operations, procedures, or use cases.
Moreover, a UE 115 may be configured to apply or extend indicated random access configurations to other operations, procedures, or use cases. For example, if an SBFD-aware UE 115 is configured with only a TDD dedicated two-step RA configuration for BFR, SI, mobility, etc., then the SBFD-aware UE 115 may be configured to use only the TDD msgA-RACH/msgA-PUSCH configuration (e.g., TDD msgA random access configuration) for performing BFR, SI, mobility, etc. In other cases, if the SBFD-aware UE 115 is configured with only a TDD dedicated two-step RA configuration for BFR, SI, mobility, etc., the SBFD-aware UE 115 may be able to use the cell-specific SBFD msgARACH configuration for performing BFR, SI, mobility, etc.
By way of another example, if an SBFD-aware UE 115 is not configured with any dedicated two-step RA configuration for BFR, SI, mobility, handover, etc., then the SBFD-aware UE 115 may be configured to use only the cell-specific TDD RACH configuration for performing BFR, SI, mobility, etc. In other cases, if an SBFD-aware UE 115 is not configured with any dedicated two-step RA configuration for BFR, SI, mobility, etc., then the SBFD-aware can UE 115 may be able to either the cell-specific SBFD RACH configuration or the cell-specific TDD RACH configuration for performing BFR, SI, mobility, etc.
FIG. 8 shows an example of a process flow 800 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure. In some examples, aspects of the process flow 800 may implement, or be implemented by, aspects of the wireless communications system 100, the two-step RACH procedure configuration 200, the wireless communications systems 300, the resource configurations 400-700, or any combination thereof. For example, the process flow 800 illustrates signaling and configurations for two-step RACH procedures that utilize dedicated SBFD resources, as described previously herein.
The process flow 800 includes a UE 115-c and a network entity 105-c, which may be examples of wireless devices as described herein. For example, the UE 115-c and the network entity 105-c illustrated in FIG. 8 may include examples of the UEs 115-a, 115-b and the network entities 105-a, 105-b, respectively, as illustrated in FIGs. 2 and 3. In this regard, the UE 115-c may be an example of an SBFD-aware UE 115 (e.g., a UE 115 capable of performing full-duplex communications, or otherwise capable of communicating within full-duplex slots) .
In some examples, the operations illustrated in process flow 800 may be performed by hardware (e.g., including circuitry, processing blocks, logic components, and other components) , code (e.g., software or firmware) executed by a processor, or any combination thereof. Alternative examples of the following may be implemented, where some steps are performed in a different order than described or are not performed at all. In some cases, steps may include additional features not mentioned below, or further steps may be added.
At 810, the UE 115-c may receive control signaling (e.g., RRC, SI) from the network entity 105-c, where the control signaling includes a random access configuration for performing a two-step RACH procedure with the network entity 105-c. For example, the control signaling may indicate one or more RACH configurations and one or more PUSCH configurations for performing a two-step RACH procedure.
As described previously herein, the RACH configuration (s) indicated via the control signaling at 805 may be associated with common ROs (e.g., legacy/TDD ROs) used to transmit MsgA preambles, as shown and described in FIGs. 4–7. Moreover, the PUSCH configuration (s) indicated via the control signaling at 805 may be associated with common POs (e.g., legacy/TDD ROs) used to transmit MsgA payloads, as shown and described in FIGs. 4–7. As described previously herein, the network may utilize various implementations that include different combinations of common ROs/POs and full-duplex ROs/POs.
For instance, the control signaling at 805 may configure the UE 115 according to the first implementation 405-a shown in FIG. 5, where the UE 115 receives a common RACH configuration, a common PUSCH configuration, and an SBFD PUSCH configuration. In other cases, the control signaling at 805 may configure the UE 115 according to the second implementation 405-b shown in FIG. 6, where the UE 115 receives a common RACH configuration, an SBFD RACH configuration, and a common PUSCH configuration. In other cases, the control signaling at 805 may configure the UE 115 according to the third implementation 405-c shown in FIG. 7, where the UE 115 receives a common RACH configuration, an SBFD RACH configuration, a common PUSCH configuration, and an SBFD PUSCH configuration.
At 810, the UE 115-c may monitor a set of SSBs associated with the configured ROs/POs. That is, the UE 115-c may perform measurements to evaluate channel quality metrics associated with the respective SSBs. As such, the UE 115-c may monitor the SSBs at 810 based on receiving the control signaling at 805.
At 815, the UE 115-c may select an SSB/preamble that will be used for a two-step RACH procedure. The UE 115-c may select the SSB/preamble at 815 based on receiving the control signaling at 805, monitoring the SSB at 815, or both. For example, referring to FIG. 5, the UE 115-c may determine that SSB #1 has the highest channel quality, and may therefore select the preambles corresponding to SSB #1 to perform the two-step RACH procedure.
At 820, in cases where the UE 115-c is configured with both common ROs and SBFD ROs, or with both common POs and SBFD POs, the UE 115-c (and/or network entity 105-c) may select/identify whether to use the common ROs/POs, or the SBFD ROs/POs. In some cases, the UE 115-c may select whether to use common or SBFD resources based on receiving the control signaling at 805, monitoring the SSB at 815, selecting the SSB/preamble at 815, or any combination thereof.
As described previously herein, the UE 115-a may select whether to use common or SBFD ROs/POs based on a number of criteria, including a relative timing of the common ROs 615-a and SBFD ROs 635-a in the time domain, based on measured/predicted channel quality metrics of the slots 610 including the respective ROs, based on RRC configuration (e.g., pre-configuration by the network) , based on a type of UE 115 (e.g., full-duplex UE 115, half-duplex UE 115) , PUSCH Tx power relative to a threshold PUSCH Tx power, or any combination thereof. For example, continuing with the same example in FIG. 5, the UE 115-c may select to use one of the SBFD POs 525 corresponding to SSB #1 (instead of common PO2 520 corresponding to SSB #1) based on the SBFD POs 525 occurring earlier in time.
At 825, the UE 115-c may transmit a preamble of a first message (e.g., MsgA) of the two-step RACH procedure. The UE 115-c may transmit the MsgA preamble at 825 based on receiving the control signaling at 805, monitoring the SSB at  815, selecting the SSB/preamble at 815, selecting/identifying whether to use common or SBFD resources at 820, or any combination thereof. For example, the UE 115-c may transmit the preamble via an RO associated with a RACH configuration indicated via the control signaling at 805. For instance, continuing with the same example above, upon identifying that SSB #1 has the highest channel quality, the UE 115-c may transmit the MsgA preamble using the common RO2 515 corresponding to SSB #1.
At 830, the UE 115-a may transmit a payload of the first message (e.g., MsgA) of the two-step RACH procedure. The UE 115-c may transmit the MsgA payload at 830 based on receiving the control signaling at 805, monitoring the SSB at 815, selecting the SSB/preamble at 815, selecting/identifying whether to use common or SBFD resources at 820, transmitting the MsgA preamble at 825, or any combination thereof.
In particular, the UE 115-c may transmit the MsgA payload via a PO associated with a PUSCH configuration indicated via the control signaling at 805, and using a PO that maps to the preamble/SSB of the RO used to transmit the MsgA preamble at 825. For example, continuing with the same example above, after transmitting the MsgA preamble via the common RO2 515, the UE 115-c may transmit the MsgA payload via the SBFD POs 3–4 that maps to the preamble of common RO2 515, or via the common PO2 520 that maps to the preamble of common RO2 515.
At 835, the network entity 105-c may decode the MsgA payload. In particular, the network entity 105-c may receive the MsgA preamble at 825, and may monitor the PO (s) corresponding to the RO in which the MsgA preamble was received in order to decode the MsgA payload.
At 840, the network entity 105-c may transmit a MsgB PDCCH portion to the UE 115-c. The MsgB PDCCH portion may include C-RNTI, MsgB-RNTI, or both.
At 845, the network entity 105-c may transmit a MsgB PDSCH portion to the UE 115-c. MsgB of the two-step RACH procedure (shown at 225 and 230) may include the information that is included within Msg2 and Msg4 of a four-step RACH procedure. The MsgB PDSCH may indicate a success random access response (RAR) . In other words, at 845, the MsgB PDSCH may indicate a successful completion of the two-step RACH procedure.
At 850, the UE 115-c may identify a valid TA and PUCCH resource/timing based on the successful completion of the two-step RACH procedure. That is, the UE 115-c may identify a valid TA and/or PUCCH resources/timing based on the MsgB PDCCH and/or MsgB PDSCH received at 840 and/or 845.
At 855, the UE 115-c may transmit a HARQ message to the network entity 105-c, where the HARQ message includes an ACK/NACK responsive to the MsgB received at 840 and 845. Subsequently, the UE 115-c and the network entity 105-c may communicate with one another based on the successful completion of the two-step RACH procedure.
FIG. 9 shows a block diagram 900 of a device 905 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure. The device 905 may be an example of aspects of a UE 115 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communications manager 920. The device 905, or one or more components of the device 905 (e.g., the receiver 910, the transmitter 915, the communications manager 920) , may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
The receiver 910 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for two-step random access procedures using dedicated SBFD resources) . Information may be passed on to other components of the device 905. The receiver 910 may utilize a single antenna or a set of multiple antennas.
The transmitter 915 may provide a means for transmitting signals generated by other components of the device 905. For example, the transmitter 915 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for two-step random access procedures using dedicated SBFD resources) . In some examples, the transmitter 915 may be co-located with a receiver 910 in a transceiver module. The transmitter 915 may utilize a single antenna or a set of multiple antennas.
The communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be examples of means for performing various aspects of techniques for two-step random access procedures using dedicated SBFD resources as described herein. For example, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be capable of performing one or more of the functions described herein.
In some examples, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include at least one of a processor, a digital signal processor (DSP) , a central processing unit (CPU) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .
Additionally, or alternatively, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code) . If implemented in code executed by at least one processor, the functions of the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure) .
In some examples, the communications manager 920 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 915, or both. For example, the communications manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.
For example, the communications manager 920 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a RACH configuration including a set of multiple common ROs within a first half-duplex uplink slot. The communications manager 920 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or more full-duplex slots. The communications manager 920 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity via a common RO of the set of multiple common ROs. The communications manager 920 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that is associated with the common RO, or via a full-duplex PO from the set of full-duplex POs that is associated with the common RO used to transmit the preamble. The communications manager 920 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
For example, the communications manager 920 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots. The communications manager 920 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, an PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple POs associated with the set of common ROs and the set of full-duplex ROs, the set of multiple POs including a set of common POs within one or more additional half-duplex uplink slots. The communications manager 920 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO of the set of full-duplex ROs. The communications manager 920 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity via a common PO of the set of common POs that maps to the common RO or the full-duplex RO that was used to transmit the preamble. The communications manager 920 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
For example, the communications manager 920 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots. The communications manager 920 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or additional more full-duplex slots, where the set of common ROs are mapped to the set of common POs, and where the set of full-duplex ROs mapped to the set of full-duplex POs. The communications manager 920 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO from the set of full-duplex ROs. The communications manager 920 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that maps to the common RO based on transmitting the preamble via the common RO, or via a full-duplex PO from the set of full-duplex POs that maps to the common RO used to transmit the preamble based on transmitting the preamble via the full-duplex RO. The communications manager 920 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
By including or configuring the communications manager 920 in accordance with examples as described herein, the device 905 (e.g., at least one processor controlling or otherwise coupled with the receiver 910, the transmitter 915, the communications manager 920, or a combination thereof) may support signaling and configurations that facilitate faster and more efficient RACH procedures (e.g., two-step RACH procedures) . In particular, by enabling UEs 115 to transmit RACH procedure signaling within full-duplex slots, techniques described herein may reduce a latency of two-step RACH procedures, and alleviate congestion/collisions within conventional RACH procedure resources within half-duplex slots.
FIG. 10 shows a block diagram 1000 of a device 1005 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure. The device 1005 may be an example of aspects of a device 905 or a UE 115 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communications manager 1020. The device 1005, or one or more components of the device 1005 (e.g., the receiver 1010, the transmitter 1015, the communications manager 1020) , may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
The receiver 1010 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for two-step random access procedures using dedicated SBFD resources) . Information may be passed on to other components of the device 1005. The receiver 1010 may utilize a single antenna or a set of multiple antennas.
The transmitter 1015 may provide a means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for two-step random access procedures using dedicated SBFD resources) . In some examples, the transmitter 1015 may be co-located with a receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or a set of multiple antennas.
The device 1005, or various components thereof, may be an example of means for performing various aspects of techniques for two-step random access procedures using dedicated SBFD resources as described herein. For example, the communications manager 1020 may include a control signaling receiving manager 1025, a preamble transmitting manager 1030, a payload transmitting manager 1035, a RACH procedure manager 1040, or any combination thereof. The communications manager 1020 may be an example of aspects of a communications manager 920 as described herein. In some examples, the communications manager 1020, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both. For example, the communications manager 1020 may receive information from the receiver 1010, send information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.
The control signaling receiving manager 1025 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a RACH configuration including a set of multiple common ROs within a first half-duplex uplink slot. The control signaling receiving manager 1025 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or more full-duplex slots. The preamble transmitting manager 1030 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity via a common RO of the set of multiple common ROs. The payload transmitting manager 1035 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that is associated with the common RO, or via a full-duplex PO from the set of full-duplex POs that is associated with the common RO used to transmit the preamble. The RACH procedure manager 1040 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
The control signaling receiving manager 1025 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of  common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots. The control signaling receiving manager 1025 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, an PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple POs associated with the set of common ROs and the set of full-duplex ROs, the set of multiple POs including a set of common POs within one or more additional half-duplex uplink slots. The preamble transmitting manager 1030 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO of the set of full-duplex ROs. The payload transmitting manager 1035 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity via a common PO of the set of common POs that maps to the common RO or the full-duplex RO that was used to transmit the preamble. The RACH procedure manager 1040 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
The control signaling receiving manager 1025 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots. The control signaling receiving manager 1025 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more additional half-duplex uplink slots, and the second  PUSCH configuration including a set of full-duplex POs within one or additional more full-duplex slots, where the set of common ROs are mapped to the set of common POs, and where the set of full-duplex ROs mapped to the set of full-duplex POs. The preamble transmitting manager 1030 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO from the set of full-duplex ROs. The payload transmitting manager 1035 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that maps to the common RO based on transmitting the preamble via the common RO, or via a full-duplex PO from the set of full-duplex POs that maps to the common RO used to transmit the preamble based on transmitting the preamble via the full-duplex RO. The RACH procedure manager 1040 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
FIG. 11 shows a block diagram 1100 of a communications manager 1120 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure. The communications manager 1120 may be an example of aspects of a communications manager 920, a communications manager 1020, or both, as described herein. The communications manager 1120, or various components thereof, may be an example of means for performing various aspects of techniques for two-step random access procedures using dedicated SBFD resources as described herein. For example, the communications manager 1120 may include a control signaling receiving manager 1125, a preamble transmitting manager 1130, a payload transmitting manager 1135, a RACH procedure manager 1140, a PO selection manager 1145, a validity manager 1150, an SSB monitoring manager 1155, a RO selection manager 1160, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories) , may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
The control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a RACH configuration including a set of multiple common ROs within a first half-duplex uplink slot. In some examples, the control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or more full-duplex slots. The preamble transmitting manager 1130 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity via a common RO of the set of multiple common ROs. The payload transmitting manager 1135 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that is associated with the common RO, or via a full-duplex PO from the set of full-duplex POs that is associated with the common RO used to transmit the preamble. The RACH procedure manager 1140 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
In some examples, the control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of multiple common ROs and the set of common POs, and a second mapping configuration between the set of multiple preambles of the set of multiple common ROs and the set of full-duplex POs. In some examples, the PO selection manager 1145 is capable of, configured to, or operable to support a means for selecting one of the common PO or the full-duplex PO that maps to the common RO used to transmit the preamble in accordance with the first mapping configuration or the second mapping configuration, where the payload of the first message is transmitted via the selected one of the common PO or the full-duplex PO.
In some examples, each common RO from the set of multiple common ROs is mapped to a set of multiple full-duplex POs from the set of full-duplex POs.
In some examples, the second PUSCH configuration includes a first sub-configuration associated with a first preamble group including the set of full-duplex POs, and a second sub-configuration associated with a second preamble group including an additional set of full-duplex POs.
In some examples, the PO selection manager 1145 is capable of, configured to, or operable to support a means for selecting one of the common PO or the full-duplex PO that maps to the common RO based on a relative timing of the common PO and the full-duplex PO in a time domain, one or more measured or predicted downlink signal quality metrics associated with slots that include the common PO and the full-duplex PO, an RRC configuration, a PUSCH Tx power relative to a Tx power threshold associated with the one or more full-duplex slots, a type of UE, or any combination thereof, where the payload of the first message of the two-step random access procedure is transmitted via the selected one of the common PO or the full-duplex PO.
In some examples, the validity manager 1150 is capable of, configured to, or operable to support a means for determining a validity of each full-duplex PO within the set of full-duplex POs based on a type of slot corresponding to each of the set of full-duplex POs, the type of slot including a full-duplex slot type or a half-duplex slot type.
In some examples, to support determining the validity of each full-duplex PO, the validity manager 1150 is capable of, configured to, or operable to support a means for determining that each full-duplex PO of the set of full-duplex POs is valid regardless of the type of slot in accordance with a first validity rule. In some examples, to support determining the validity of each full-duplex PO, the validity manager 1150 is capable of, configured to, or operable to support a means for determining that a subset of POs from the set of full-duplex POs are invalid based on the subset of POs being positioned within non-full-duplex slots and in accordance with a second validity rule.
In some examples, the set of full-duplex POs include a first subset of full-duplex POs within the one or more full-duplex slots, and a second subset of full-duplex POs that overlap in a time domain with the set of common POs within the one or more second half-duplex uplink slots. In some examples, the set of multiple common ROs are associated with a set of multiple preambles . In some examples, the set of multiple preambles are mapped to the set of common POs and the set of full-duplex POs such that temporally overlapping pairs of POs are associated with one or more common preambles of the set of multiple preambles. In some examples, each temporally overlapping pair of POs include one of the second subset of full-duplex POs and one of the set of common POs.
In some examples, the SSB monitoring manager 1155 is capable of, configured to, or operable to support a means for monitoring a set of multiple synchronization signal blocks, the set of multiple synchronization signal blocks corresponding with the set of multiple common ROs. In some examples, the RO selection manager 1160 is capable of, configured to, or operable to support a means for selecting the common RO from the set of multiple common ROs based on the monitoring.
In some examples, the set of full-duplex POs include SBFD POs. In some examples, the one or more full-duplex slots include one or more SBFD slots.
In some examples, the first PUSCH configuration indicates a first starting resource block frequency configuration associated with the set of common POs. In some examples, the second PUSCH configuration indicates a second starting resource block frequency configuration associated with the set of full-duplex POs.
In some examples, the first PUSCH configuration indicates a first quantity of frequency-division multiplexed POs associated with the set of common POs within the one or more second half-duplex uplink slots. In some examples, the second PUSCH configuration indicates a second quantity of frequency-division multiplexed POs associated with the set of full-duplex POs within the one or more full-duplex slots.
In some examples, the set of multiple common ROs and the set of common POs are usable by full-duplex-aware UEs and non-full-duplex-aware UEs. In some examples, the set of full-duplex POs are usable by full-duplex-aware UEs but unusable by non-full-duplex-aware UEs.
In some examples, the control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots. In some examples, the control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, an PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple POs associated with the set of common ROs and the set of full-duplex ROs, the set of multiple POs including a set of common POs within one or more additional half-duplex uplink slots. In some examples, the preamble transmitting manager 1130 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO of the set of full-duplex ROs. In some examples, the payload transmitting manager 1135 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity via a common PO of the set of common POs that maps to the common RO or the full-duplex RO that was used to transmit the preamble. In some examples, the RACH procedure manager 1140 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
In some examples, the first half-duplex uplink slot including the set of common ROs includes a PRACH slot. In some examples, the PUSCH configuration includes a first time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common POs, and a second time  domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common POs.
In some examples, the control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of common ROs and the set of common POs, and a second mapping configuration between the set of multiple preambles of the set of full-duplex ROs and the set of common POs.
In some examples, each common PO from the set of common POs is mapped to at least one common RO from the set of common ROs and at least one full-duplex RO from the set of full-duplex ROs.
In some examples, the RO selection manager 1160 is capable of, configured to, or operable to support a means for selecting one of the common RO or the full-duplex RO based on a relative timing of the common RO and the full-duplex RO in a time domain, one or more measured or predicted signal quality metrics associated with slots that include the common RO and the full-duplex RO, a PUSCH Tx power relative to a Tx power threshold associated with the one or more full-duplex slots, an RRC configuration, a type of UE, or any combination thereof, where the preamble of the first message of the two-step random access procedure is transmitted via the selected one of the common RO or the full-duplex RO.
In some examples, the validity manager 1150 is capable of, configured to, or operable to support a means for determining a validity of each full-duplex RO within the set of full-duplex ROs based on a type of slot corresponding to each of the set of full-duplex ROs, the type of slot including a full-duplex slot type or a half-duplex slot type.
In some examples, to support determining the validity of each full-duplex RO, the validity manager 1150 is capable of, configured to, or operable to support a means for determining that each full-duplex RO of the set of full-duplex ROs is valid regardless of the type of slot in accordance with a first validity rule. In some examples, to support determining the validity of each full-duplex RO, the validity manager 1150 is capable of, configured to, or operable to support a means for determining that a subset of ROs from the set of full-duplex ROs are invalid based on the subset of ROs being positioned within non-full-duplex slots and in accordance with a second validity rule.
In some examples, the set of full-duplex ROs include a first subset of full-duplex ROs within the one or more full-duplex slots, and a second subset of full-duplex ROs that overlap in a time domain with the set of common ROs within the first half-duplex uplink slot. In some examples, the set of common ROs and the set of full-duplex ROs are associated with a set of multiple preambles such that temporally overlapping pairs of ROs map to one or more common preambles of the set of multiple preambles. In some examples, each temporally overlapping pair of ROs include one of the second subset of full-duplex ROs and one of the set of common ROs.
In some examples, the set of full-duplex ROs include SBFD ROs. In some examples, the one or more full-duplex slots include one or more SBFD slots.
In some examples, the control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots. In some examples, the control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or additional more full-duplex slots, where the set of common ROs are mapped to the set of common POs, and where the set of full-duplex ROs mapped to the set of full-duplex POs. In some examples, the preamble transmitting manager 1130 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO from the set of full-duplex ROs. In some examples, the payload transmitting  manager 1135 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that maps to the common RO based on transmitting the preamble via the common RO, or via a full-duplex PO from the set of full-duplex POs that maps to the common RO used to transmit the preamble based on transmitting the preamble via the full-duplex RO. In some examples, the RACH procedure manager 1140 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
In some examples, the control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of common ROs and the set of common POs, and a second mapping configuration between the set of multiple preambles of the set of full-duplex ROs and the set of full-duplex POs.
In some examples, the control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, the second control signaling, or both, a third mapping configuration between the set of multiple preambles of set of common ROs and the set of full-duplex POs, a fourth mapping configuration between the set of multiple preambles of the set of full-duplex ROs and the set of common POs, or both.
In some examples, the set of full-duplex ROs include SBFD ROs. In some examples, the set of full-duplex POs include SBFD POs. In some examples, the one or more full-duplex slots, the one or more additional full-duplex slots, or both, include one or more SBFD slots.
In some examples, the control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, the second control signaling, or both, an indication that the first RACH configuration, second RACH configuration, the first PUSCH configuration, the second PUSCH configuration, or any combination thereof, are usable for performing random access procedures associated with SI requests, physical downlink control channel ordering, BFR, mobility, or any combination thereof.
In some examples, the control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, the second control signaling, or both, an indication that the second RACH configuration, the second PUSCH configuration, or both, include UE-specific configurations or cell-specific configurations.
In some examples, the control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, the second control signaling, third control signaling, or any combination thereof, a common random access configuration associated with one or more operations different from the two-step random access procedure. In some examples, the control signaling receiving manager 1125 is capable of, configured to, or operable to support a means for performing the one or more operations in accordance with either the common random access configuration, or in accordance with the second RACH configuration and the second PUSCH configuration.
In some examples, the RACH procedure manager 1140 is capable of, configured to, or operable to support a means for determining that the UE has not been configured with a common random access configuration associated with one or more operations different from the two-step random access procedure. In some examples, the RACH procedure manager 1140 is capable of, configured to, or operable to support a means for performing the one or more operations in accordance with the first RACH configuration and the first PUSCH configuration, or in accordance with the second RACH configuration and the second PUSCH configuration.
FIG. 12 shows a diagram of a system 1200 including a device 1205 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure. The device 1205 may be an example of or include components of a device 905, a device 1005, or a UE 115 as described herein. The device 1205 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entities 105, UEs 115, or a combination thereof) . The device 1205 may include components for bi-directional voice and data  communications including components for transmitting and receiving communications, such as a communications manager 1220, an input/output (I/O) controller, such as an I/O controller 1210, a transceiver 1215, one or more antennas 1225, at least one memory 1230, code 1235, and at least one processor 1240. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1245) .
The I/O controller 1210 may manage input and output signals for the device 1205. The I/O controller 1210 may also manage peripherals not integrated into the device 1205. In some cases, the I/O controller 1210 may represent a physical connection or port to an external peripheral. In some cases, the I/O controller 1210 may utilize an operating system such as or another known operating system. Additionally, or alternatively, the I/O controller 1210 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller 1210 may be implemented as part of one or more processors, such as the at least one processor 1240. In some cases, a user may interact with the device 1205 via the I/O controller 1210 or via hardware components controlled by the I/O controller 1210.
In some cases, the device 1205 may include a single antenna. However, in some other cases, the device 1205 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1215 may communicate bi-directionally via the one or more antennas 1225 using wired or wireless links as described herein. For example, the transceiver 1215 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1215 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1225 for transmission, and to demodulate packets received from the one or more antennas 1225. The transceiver 1215, or the transceiver 1215 and one or more antennas 1225, may be an example of a transmitter 915, a transmitter 1015, a receiver 910, a receiver 1010, or any combination thereof or component thereof, as described herein.
The at least one memory 1230 may include random access memory (RAM) and read-only memory (ROM) . The at least one memory 1230 may store computer-readable, computer-executable, or processor-executable code, such as the code 1235. The code 1235 may include instructions that, when executed by the at least one processor 1240, cause the device 1205 to perform various functions described herein. The code 1235 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1235 may not be directly executable by the at least one processor 1240 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1230 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
The at least one processor 1240 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs) , one or more graphics processing units (GPUs) , one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs) ) , one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof) . In some cases, the at least one processor 1240 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 1240. The at least one processor 1240 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 1230) to cause the device 1205 to perform various functions (e.g., functions or tasks supporting techniques for two-step random access procedures using dedicated SBFD resources) . For example, the device 1205 or a component of the device 1205 may include at least one processor 1240 and at least one memory 1230 coupled with or to the at least one processor 1240, the at least one processor 1240 and the at least one memory 1230 configured to perform various functions described herein. In some examples, the at least one processor 1240 may include multiple processors and the at least one memory 1230 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions described herein. In some examples, the at least one processor 1240 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1240) and memory circuitry (which may include the at least one memory 1230) ) , or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1240 or a processing system including the at least one processor 1240 may be configured to, configurable to, or operable to cause the device 1205 to perform one or more of the functions described herein. Further, as described herein, being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code 1235 (e.g., processor-executable code) stored in the at least one memory 1230 or otherwise, to perform one or more of the functions described herein.
For example, the communications manager 1220 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a RACH configuration including a set of multiple common ROs within a first half-duplex uplink slot. The communications manager 1220 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or more full-duplex slots. The communications manager 1220 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity via a common RO of the set of multiple common ROs. The communications manager 1220 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that is associated with the common RO, or via a full-duplex PO from the set of full-duplex POs that is associated with the common RO used to transmit the preamble. The communications manager 1220 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
For example, the communications manager 1220 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots. The communications manager 1220 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, an PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple POs associated with the set of common ROs and the set of full-duplex ROs, the set of multiple POs including a set of common POs within one or more additional half-duplex uplink slots. The communications manager 1220 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO of the set of full-duplex ROs. The communications manager 1220 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity via a common PO of the set of common POs that maps to the common RO or the full-duplex RO that was used to transmit the preamble. The communications manager 1220 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
For example, the communications manager 1220 is capable of, configured to, or operable to support a means for receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots. The communications manager 1220 is capable of, configured to, or operable to support a means for receiving, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or additional more full-duplex slots, where the set of common ROs are mapped to the set of common POs, and where the set of full-duplex ROs mapped to the set of full-duplex POs. The communications manager 1220 is capable of, configured to, or operable to support a means for transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO from the set of full-duplex ROs. The communications manager 1220 is capable of, configured to, or operable to support a means for transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that maps to the common RO based on transmitting the preamble via the common RO, or via a full-duplex PO from the set of full-duplex POs that maps to the common RO used to transmit the preamble based on transmitting the preamble via the full-duplex RO. The communications manager 1220 is capable of, configured to, or operable to support a means for receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure.
By including or configuring the communications manager 1220 in accordance with examples as described herein, the device 1205 may support signaling and configurations that facilitate faster and more efficient RACH procedures (e.g., two-step RACH procedures) . In particular, by enabling UEs 115 to transmit RACH procedure signaling within full-duplex slots, techniques described herein may reduce a latency of two-step RACH procedures, and alleviate congestion/collisions within conventional RACH procedure resources within half-duplex slots.
In some examples, the communications manager 1220 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 1215, the one or more antennas 1225, or any combination thereof. Although the communications manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1220 may be supported by or performed by the at least one processor 1240, the at least one memory 1230, the code 1235, or any combination thereof. For example, the code 1235 may include instructions executable by the at least one processor 1240 to cause the device 1205 to perform various aspects of techniques for two-step random access procedures using dedicated SBFD resources as described herein, or the at least one processor 1240 and the at least one memory 1230 may be otherwise configured to, individually or collectively, perform or support such operations.
FIG. 13 shows a block diagram 1300 of a device 1305 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure. The device 1305 may be an example of aspects of a network entity 105 as described herein. The device 1305 may include a receiver 1310, a transmitter 1315, and a communications manager 1320. The device 1305, or one or more components of the device 1305 (e.g., the receiver 1310, the transmitter 1315, the communications manager 1320) , may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
The receiver 1310 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) . Information may be passed on to other components of the device 1305. In some examples, the receiver 1310 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1310 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
The transmitter 1315 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1305. For example, the transmitter 1315 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) . In some examples, the transmitter 1315 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1315 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1315 and the receiver 1310 may be co-located in a transceiver, which may include or be coupled with a modem.
The communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be examples of means for performing various aspects of techniques for two-step random access procedures using dedicated SBFD resources as described herein. For example, the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be capable of performing one or more of the functions described herein.
In some examples, the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .
Additionally, or alternatively, the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code) . If implemented in code executed by at least one processor, the functions of the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure) .
In some examples, the communications manager 1320 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1310, the transmitter 1315, or both. For example, the communications manager 1320 may receive information from the receiver 1310, send information to the transmitter 1315, or be integrated in combination with the receiver 1310, the transmitter 1315, or both to obtain information, output information, or perform various other operations as described herein.
For example, the communications manager 1320 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a RACH configuration including a set of multiple common ROs within a first half-duplex uplink slot. The communications manager 1320 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or more full-duplex slots. The communications manager 1320 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity via a common RO of the set of multiple common ROs. The communications manager 1320 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that is associated with the common RO, or via a full-duplex PO from the set of full-duplex POs that is associated with the common RO used to receive the preamble. The communications manager 1320 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
For example, the communications manager 1320 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots. The communications manager 1320 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, an PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple POs associated with the set of common ROs and the set of full-duplex ROs, the set of multiple POs including a set of common POs within one or more additional half-duplex uplink slots. The communications manager 1320 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO of the set of full-duplex ROs. The communications manager 1320 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity via a common PO of the set of common POs that maps to the common RO or the full-duplex RO that was used to receive the preamble. The communications manager 1320 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
For example, the communications manager 1320 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots. The communications manager 1320 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or additional more full-duplex slots, where the set of common ROs are mapped to the set of common POs, and where the set of full-duplex ROs mapped to the set of full-duplex POs. The communications manager 1320 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO from the set of full-duplex ROs. The communications manager 1320 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that maps to the common RO based on transmitting the preamble via the common RO, or via a full-duplex PO from the set of full-duplex POs that maps to the common RO used to receive the preamble based on receiving the preamble via the full-duplex RO. The communications manager 1320 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
By including or configuring the communications manager 1320 in accordance with examples as described herein, the device 1305 (e.g., at least one processor controlling or otherwise coupled with the receiver 1310, the transmitter 1315, the communications manager 1320, or a combination thereof) may support signaling and configurations that facilitate faster and more efficient RACH procedures (e.g., two-step RACH procedures) . In particular, by enabling UEs 115 to transmit RACH procedure signaling within full-duplex slots, techniques described herein may reduce a latency of two-step RACH procedures, and alleviate congestion/collisions within conventional RACH procedure resources within half-duplex slots.
FIG. 14 shows a block diagram 1400 of a device 1405 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure. The device 1405 may be an example of aspects of a device 1305 or a network entity 105 as described herein. The device 1405 may include a receiver 1410, a transmitter 1415, and a communications manager 1420. The device 1405, or one or more components of the device 1405 (e.g., the receiver 1410, the transmitter 1415, the communications manager 1420) , may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
The receiver 1410 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) . Information may be passed on to other components of the device 1405. In some examples, the receiver 1410 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1410 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
The transmitter 1415 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1405. For example, the transmitter 1415 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) . In some examples, the transmitter 1415 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1415 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1415 and the receiver 1410 may be co-located in a transceiver, which may include or be coupled with a modem.
The device 1405, or various components thereof, may be an example of means for performing various aspects of techniques for two-step random access procedures using dedicated SBFD resources as described herein. For example, the communications manager 1420 may include a control signaling transmitting manager 1425, a preamble receiving manager 1430, a payload receiving manager 1435, a RACH procedure manager 1440, or any combination thereof. The communications manager 1420 may be an example of aspects of a communications manager 1320 as described herein. In some examples, the communications manager 1420, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1410, the transmitter 1415, or both. For example, the communications manager 1420 may receive information from the receiver 1410, send information to the transmitter 1415, or be integrated in combination with the receiver 1410, the transmitter 1415, or both to obtain information, output information, or perform various other operations as described herein.
The control signaling transmitting manager 1425 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a RACH configuration including a set of multiple common ROs within a first half-duplex uplink slot. The control signaling transmitting manager 1425 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or more full-duplex slots. The preamble receiving manager 1430 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity via a common RO of the set of multiple common ROs. The payload receiving manager 1435 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that is associated with the common RO, or via a full-duplex PO from the set of full-duplex POs that is associated with the common RO used to receive the preamble. The RACH procedure manager 1440 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
The control signaling transmitting manager 1425 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots. The control signaling transmitting manager 1425 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, an PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple POs associated with the set of common ROs and the set of full-duplex ROs, the set of multiple POs including a set of common POs within one or more additional half-duplex uplink slots.  The preamble receiving manager 1430 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO of the set of full-duplex ROs. The payload receiving manager 1435 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity via a common PO of the set of common POs that maps to the common RO or the full-duplex RO that was used to receive the preamble. The RACH procedure manager 1440 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
The control signaling transmitting manager 1425 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots. The control signaling transmitting manager 1425 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or additional more full-duplex slots, where the set of common ROs are mapped to the set of common POs, and where the set of full-duplex ROs mapped to the set of full-duplex POs. The preamble receiving manager 1430 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO from the set of full-duplex ROs. The payload receiving manager 1435 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that maps to the common RO based on transmitting the preamble via the common RO, or via a full-duplex PO from the set of full-duplex POs that maps to the common RO used to receive the preamble based on receiving the preamble via the full-duplex RO. The RACH procedure manager 1440 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
FIG. 15 shows a block diagram 1500 of a communications manager 1520 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure. The communications manager 1520 may be an example of aspects of a communications manager 1320, a communications manager 1420, or both, as described herein. The communications manager 1520, or various components thereof, may be an example of means for performing various aspects of techniques for two-step random access procedures using dedicated SBFD resources as described herein. For example, the communications manager 1520 may include a control signaling transmitting manager 1525, a preamble receiving manager 1530, a payload receiving manager 1535, a RACH procedure manager 1540, a PO identification manager 1545, a validity manager 1550, a RO identification manager 1555, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories) , may communicate, directly or indirectly, with one another (e.g., via one or more buses) . The communications may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105) , or any combination thereof.
The control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a RACH configuration including a set of multiple common ROs within a first half-duplex uplink slot. In some examples, the control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or more full-duplex slots. The preamble receiving manager 1530 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity via a common RO of the set of multiple common ROs. The payload receiving manager 1535 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that is associated with the common RO, or via a full-duplex PO from the set of full-duplex POs that is associated with the common RO used to receive the preamble. The RACH procedure manager 1540 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
In some examples, the control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of multiple common ROs and the set of common POs, and a second mapping configuration between the set of multiple preambles of the set of multiple common ROs and the set of full-duplex POs. In some examples, the PO identification manager 1545 is capable of, configured to, or operable to support a means for identifying one of the common PO or the full-duplex PO that maps to the common RO used to transmit the preamble in accordance with the first mapping configuration or the second mapping configuration, where the payload of the first message is received via the identified one of the common PO or the full-duplex PO.
In some examples, each common RO from the set of multiple common ROs is mapped to a set of multiple full-duplex POs from the set of full-duplex POs.
In some examples, the second PUSCH configuration includes a first sub-configuration associated with a first preamble group including the set of full-duplex POs, and a second sub-configuration associated with a second preamble group including an additional set of full-duplex POs.
In some examples, the PO identification manager 1545 is capable of, configured to, or operable to support a means for identifying one of the common PO or the full-duplex PO that maps to the common RO based on a relative timing of the common PO and the full-duplex PO in a time domain, one or more measured or predicted downlink signal quality metrics associated with slots that include the common PO and the full-duplex PO, an RRC configuration, a PUSCH Tx power relative to a Tx power threshold associated with the one or more full-duplex slots, a type of UE, or any combination thereof, where the payload of the first message of the two-step random access procedure is received via the identified one of the common PO or the full-duplex PO.
In some examples, the validity manager 1550 is capable of, configured to, or operable to support a means for determining a validity of each full-duplex PO within the set of full-duplex POs based on a type of slot corresponding to each of the set of full-duplex POs, the type of slot including a full-duplex slot type or a half-duplex slot type.
In some examples, to support determining the validity of each full-duplex PO, the validity manager 1550 is capable of, configured to, or operable to support a means for determining that each full-duplex PO of the set of full-duplex POs is valid regardless of the type of slot in accordance with a first validity rule. In some examples, to support determining the validity of each full-duplex PO, the validity manager 1550 is capable of, configured to, or operable to support a means for determining that a subset of POs from the set of full-duplex POs are invalid based on the subset of POs being positioned within non-full-duplex slots and in accordance with a second validity rule.
In some examples, the set of full-duplex POs include a first subset of full-duplex POs within the one or more full-duplex slots, and a second subset of full-duplex POs that overlap in a time domain with the set of common POs within the one or more second half-duplex uplink slots. In some examples, the set of multiple common ROs are associated with a set of multiple preambles . In some examples, the set of multiple preambles are mapped to the set of common POs and the set of full-duplex POs such that temporally overlapping pairs of POs are associated with one or more common preambles of the set of multiple preambles. In some examples, each temporally overlapping pair of POs include one of the second subset of full-duplex POs and one of the set of common POs.
In some examples, the set of full-duplex POs include SBFD POs. In some examples, the one or more full-duplex slots include one or more SBFD slots.
In some examples, the first PUSCH configuration indicates a first starting resource block frequency configuration associated with the set of common POs. In some examples, the second PUSCH configuration indicates a second starting resource block frequency configuration associated with the set of full-duplex POs.
In some examples, the first PUSCH configuration indicates a first quantity of frequency-division multiplexed POs associated with the set of common POs within the one or more second half-duplex uplink slots. In some examples, the second PUSCH configuration indicates a second quantity of frequency-division multiplexed POs associated with the set of full-duplex POs within the one or more full-duplex slots.
In some examples, the set of multiple common ROs and the set of common POs are usable by full-duplex-aware UEs and non-full-duplex-aware UEs. In some examples, the set of full-duplex POs are usable by full-duplex-aware UEs but unusable by non-full-duplex-aware UEs.
In some examples, the control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots. In some examples, the control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, an PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple POs associated with the set of common ROs and the set of full-duplex ROs, the set of multiple POs including a set of common POs within one or more additional half-duplex uplink slots. In some examples, the preamble receiving manager 1530 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO of the set of full-duplex ROs. In some examples, the payload receiving manager 1535 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity via a common PO of the set of common POs that maps to the common RO or the full-duplex RO that was used to receive the preamble. In some examples, the RACH procedure manager 1540 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
In some examples, the first half-duplex uplink slot including the set of common ROs includes a PRACH slot. In some examples, the PUSCH configuration includes a first time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common POs, and a second time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common POs.
In some examples, the control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of common ROs and the set of common POs, and a second mapping configuration between the set of multiple preambles of the set of full-duplex ROs and the set of common POs.
In some examples, each common PO from the set of common POs is mapped to at least one common RO from the set of common ROs and at least one full-duplex RO from the set of full-duplex ROs.
In some examples, the RO identification manager 1555 is capable of, configured to, or operable to support a means for identifying one of the common RO or the full-duplex RO based on a relative timing of the common RO and the full-duplex RO in a time domain, one or more measured or predicted signal quality metrics associated with slots that include the common RO and the full-duplex RO, a PUSCH Tx power relative to a Tx power threshold associated with the one or more full-duplex slots, an RRC configuration, a type of UE, or any combination thereof, where the preamble of the first message of the two-step random access procedure is received via the identified one of the common RO or the full-duplex RO.
In some examples, the validity manager 1550 is capable of, configured to, or operable to support a means for determining a validity of each full-duplex RO within the set of full-duplex ROs based on a type of slot corresponding to each of the set of full-duplex ROs, the type of slot including a full-duplex slot type or a half-duplex slot type.
In some examples, to support determining the validity of each full-duplex
RO, the validity manager 1550 is capable of, configured to, or operable to support a means for determining that each full-duplex RO of the set of full-duplex ROs is valid regardless of the type of slot in accordance with a first validity rule. In some examples, to support determining the validity of each full-duplex RO, the validity manager 1550 is capable of, configured to, or operable to support a means for determining that a subset of ROs from the set of full-duplex ROs are invalid based on the subset of ROs being positioned within non-full-duplex slots and in accordance with a second validity rule.
In some examples, the set of full-duplex ROs include a first subset of full-duplex ROs within the one or more full-duplex slots, and a second subset of full-duplex ROs that overlap in a time domain with the set of common ROs within the first half-duplex uplink slot. In some examples, the set of common ROs and the set of full-duplex ROs are associated with a set of multiple preambles such that temporally overlapping pairs of ROs map to one or more common preambles of the set of multiple preambles. In some examples, each temporally overlapping pair of ROs include one of the second subset of full-duplex ROs and one of the set of common ROs.
In some examples, the set of full-duplex ROs include SBFD ROs. In some examples, the one or more full-duplex slots include one or more SBFD slots.
In some examples, the control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots. In some examples, the control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or additional more full-duplex slots, where the set of common ROs are mapped to the set of common POs, and where the set of full-duplex ROs mapped to the set of full-duplex POs. In some examples, the preamble receiving manager 1530 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO from the set of full-duplex ROs. In some examples, the payload receiving manager 1535 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that maps to the common RO based on transmitting the preamble via the common RO, or via a full-duplex PO from the set of full-duplex POs that maps to the common RO used to receive the preamble based on receiving the preamble via the full-duplex RO. In some examples, the RACH procedure manager 1540 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
In some examples, the control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, the second control signaling, or both, a first mapping configuration between the set of multiple preambles of the set of common ROs and the set of common POs, and a second mapping configuration between the set of multiple preambles of the set of full-duplex ROs and the set of full-duplex POs.
In some examples, the control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, the second control signaling, or both, a third mapping configuration between the set of multiple preambles of set of common ROs and the set of full-duplex POs, a fourth mapping configuration between the set of multiple preambles of the set of full-duplex ROs and the set of common POs, or both.
In some examples, the set of full-duplex ROs include SBFD ROs. In some examples, the set of full-duplex POs include SBFD POs. In some examples, the one or more full-duplex slots, the one or more additional full-duplex slots, or both, include one or more SBFD slots.
In some examples, the control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, the second control signaling, or both, an indication that the first RACH configuration, second RACH configuration, the first PUSCH configuration, the second PUSCH configuration, or any combination thereof, are usable for performing random access procedures associated with SI requests, physical downlink control channel ordering, BFR, mobility, or any combination thereof.
In some examples, the control signaling transmitting manager 1525 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, the second control signaling, or both, an indication that the second RACH configuration, the second PUSCH configuration, or both, include UE-specific configurations or cell-specific configurations.
FIG. 16 shows a diagram of a system 1600 including a device 1605 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure. The device 1605 may be an example of or include components of a device 1305, a device 1405, or a network entity 105 as described herein. The device 1605 may communicate with other network devices or network equipment such as one or more of the network entities 105, UEs 115, or any combination thereof. The communications may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof. The device 1605 may include components that support outputting and obtaining communications, such as a communications manager 1620, a transceiver 1610, one or more antennas 1615, at least one memory 1625, code 1630, and at least one processor 1635. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1640) .
The transceiver 1610 may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver 1610 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1610 may include a wireless transceiver and may communicate bi-directionally with another wireless transceiver. In some examples, the device 1605 may include one or more antennas 1615, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently) . The transceiver 1610 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1615, by a wired transmitter) , to receive modulated signals (e.g., from one or more antennas 1615, from a wired receiver) , and to demodulate signals. In some implementations, the transceiver 1610 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1615 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1615 that are configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1610 may include or be configured for coupling with one or more processors or one or more memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof. In some implementations, the transceiver 1610, or the transceiver 1610 and the one or more  antennas 1615, or the transceiver 1610 and the one or more antennas 1615 and one or more processors or one or more memory components (e.g., the at least one processor 1635, the at least one memory 1625, or both) , may be included in a chip or chip assembly that is installed in the device 1605. In some examples, the transceiver 1610 may be operable to support communications via one or more communications links (e.g., communication link (s) 125, backhaul communication link (s) 120, a midhaul communication link 162, a fronthaul communication link 168) .
The at least one memory 1625 may include RAM, ROM, or any combination thereof. The at least one memory 1625 may store computer-readable, computer-executable, or processor-executable code, such as the code 1630. The code 1630 may include instructions that, when executed by one or more of the at least one processor 1635, cause the device 1605 to perform various functions described herein. The code 1630 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1630 may not be directly executable by a processor of the at least one processor 1635 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1625 may include, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices. In some examples, the at least one processor 1635 may include multiple processors and the at least one memory 1625 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories which may, individually or collectively, be configured to perform various functions herein (for example, as part of a processing system) .
The at least one processor 1635 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs) , one or more graphics processing units (GPUs) , one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs) ) , one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof) . In some cases, the at least one processor 1635 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller  may be integrated into one or more of the at least one processor 1635. The at least one processor 1635 may be configured to execute computer-readable instructions stored in a memory (e.g., one or more of the at least one memory 1625) to cause the device 1605 to perform various functions (e.g., functions or tasks supporting techniques for two-step random access procedures using dedicated SBFD resources) . For example, the device 1605 or a component of the device 1605 may include at least one processor 1635 and at least one memory 1625 coupled with one or more of the at least one processor 1635, the at least one processor 1635 and the at least one memory 1625 configured to perform various functions described herein. The at least one processor 1635 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1630) to perform the functions of the device 1605. The at least one processor 1635 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1605 (such as within one or more of the at least one memory 1625) . In some examples, the at least one processor 1635 may include multiple processors and the at least one memory 1625 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 1635 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1635) and memory circuitry (which may include the at least one memory 1625) ) , or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1635 or a processing system including the at least one processor 1635 may be configured to, configurable to, or operable to cause the device 1605 to perform one or more of the functions described herein. Further, as described herein, being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 1625 or otherwise, to perform one or more of the functions described herein.
In some examples, a bus 1640 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1640 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack) , which may include communications performed within a component of the device 1605, or between different components of the device 1605 that may be co-located or located in different locations (e.g., where the device 1605 may refer to a system in which one or more of the communications manager 1620, the transceiver 1610, the at least one memory 1625, the code 1630, and the at least one processor 1635 may be located in one of the different components or divided between different components) .
In some examples, the communications manager 1620 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links) . For example, the communications manager 1620 may manage the transfer of data communications for client devices, such as one or more UEs 115. In some examples, the communications manager 1620 may manage communications with one or more other network devices, and may include a controller or scheduler for controlling communications with UEs 115 (e.g., in cooperation with the one or more other network devices) . In some examples, the communications manager 1620 may support an X2 interface within an LTE/LTE-A wireless communications network technology to provide communication between network entities 105.
For example, the communications manager 1620 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a RACH configuration including a set of multiple common ROs within a first half-duplex uplink slot. The communications manager 1620 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or more full-duplex slots. The communications manager 1620 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity via a common RO of the set of multiple common ROs. The communications manager 1620 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that is associated with the common RO, or via a full-duplex PO from the set of full-duplex POs that is associated with the common RO used to receive the preamble. The communications manager 1620 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
For example, the communications manager 1620 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots. The communications manager 1620 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, an PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple POs associated with the set of common ROs and the set of full-duplex ROs, the set of multiple POs including a set of common POs within one or more additional half-duplex uplink slots. The communications manager 1620 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO of the set of full-duplex ROs. The communications manager 1620 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity via a common PO of the set of common POs that maps to the common RO or the full-duplex RO that was used to receive the preamble. The communications manager 1620 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
For example, the communications manager 1620 is capable of, configured to, or operable to support a means for transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots. The communications manager 1620 is capable of, configured to, or operable to support a means for transmitting, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or additional more full-duplex slots, where the set of common ROs are mapped to the set of common POs, and where the set of full-duplex ROs mapped to the set of full-duplex POs. The communications manager 1620 is capable of, configured to, or operable to support a means for receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO from the set of full-duplex ROs. The communications manager 1620 is capable of, configured to, or operable to support a means for receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that maps to the common RO based on transmitting the preamble via the common RO, or via a full-duplex PO from the set of full-duplex POs that maps to the common RO used to receive the preamble based on receiving the preamble via the full-duplex RO. The communications manager 1620 is capable of, configured to, or operable to support a means for transmitting, to the UE, a second message of the two-step random access procedure based on receiving the preamble and the payload of the first message of the two-step random access procedure.
By including or configuring the communications manager 1620 in accordance with examples as described herein, the device 1605 may support signaling and configurations that facilitate faster and more efficient RACH procedures (e.g., two-step RACH procedures) . In particular, by enabling UEs 115 to transmit RACH procedure signaling within full-duplex slots, techniques described herein may reduce a latency of two-step RACH procedures, and alleviate congestion/collisions within conventional RACH procedure resources within half-duplex slots. In some examples, the communications manager 1620 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1610, the one or more antennas 1615 (e.g., where applicable) , or any combination thereof. Although the communications manager 1620 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1620 may be supported by or performed by the transceiver 1610, one or more of the at least one processor 1635, one or more of the at least one memory 1625, the code 1630, or any combination thereof (for example, by a processing system including at least a portion of the at least one processor 1635, the at least one memory 1625, the code 1630, or any combination thereof) . For example, the code 1630 may include instructions executable by one or more of the at least one processor 1635 to cause the device 1605 to perform various aspects of techniques for two-step random access procedures using dedicated SBFD resources as described herein, or the at least one processor 1635 and the at least one memory 1625 may be otherwise configured to, individually or collectively, perform or support such operations.
FIG. 17 shows a flowchart illustrating a method 1700 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure. The operations of the method 1700 may be implemented by a UE or its components as described herein. For example, the operations of the method 1700 may be performed by a UE 115 as described with reference to FIGs. 1 through 12. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
At 1705, the method may include receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a RACH configuration including a set of multiple common ROs within a first half-duplex uplink slot. The operations of 1705 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed by a control signaling receiving manager 1125 as described with reference to FIG. 11.
At 1710, the method may include receiving, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more second half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or more full-duplex slots. The operations of 1710 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed by a control signaling receiving manager 1125 as described with reference to FIG. 11.
At 1715, the method may include transmitting a preamble of a first message of the two-step random access procedure to the network entity via a common RO of the set of multiple common ROs. The operations of 1715 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed by a preamble transmitting manager 1130 as described with reference to FIG. 11.
At 1720, the method may include transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that is associated with the common RO, or via a full-duplex PO from the set of full-duplex POs that is associated with the common RO used to transmit the preamble. The operations of 1720 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed by a payload transmitting manager 1135 as described with reference to FIG. 11.
At 1725, the method may include receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure. The operations of 1725 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1725 may be performed by a RACH procedure manager 1140 as described with reference to FIG. 11.
FIG. 18 shows a flowchart illustrating a method 1800 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure. The operations of the method 1800 may be implemented by a UE or its components as described herein. For example, the operations of the method 1800 may be performed by a UE 115 as described with reference to FIGs. 1 through 12. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
At 1805, the method may include receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots. The operations of 1805 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed by a control signaling receiving manager 1125 as described with reference to FIG. 11.
At 1810, the method may include receiving, via the first control signaling, second control signaling, or both, an PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration including a set of multiple POs associated with the set of common ROs and the set of full-duplex ROs, the set of multiple POs including a set of common POs within one or more additional half-duplex uplink slots. The operations of 1810 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed by a control signaling receiving manager 1125 as described with reference to FIG. 11.
At 1815, the method may include transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO of the set of full-duplex ROs. The operations of 1815 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed by a preamble transmitting manager 1130 as described with reference to FIG. 11.
At 1820, the method may include transmitting a payload of the first message of the two-step random access procedure to the network entity via a common PO of the set of common POs that maps to the common RO or the full-duplex RO that was used to transmit the preamble. The operations of 1820 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed by a payload transmitting manager 1135 as described with reference to FIG. 11.
At 1825, the method may include receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure. The operations of 1825 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1825 may be performed by a RACH procedure manager 1140 as described with reference to FIG. 11.
FIG. 19 shows a flowchart illustrating a method 1900 that supports techniques for two-step random access procedures using dedicated SBFD resources in accordance with one or more aspects of the present disclosure. The operations of the method 1900 may be implemented by a UE or its components as described herein. For example, the operations of the method 1900 may be performed by a UE 115 as described with reference to FIGs. 1 through 12. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
At 1905, the method may include receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, where the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration including a set of common ROs within a first half-duplex uplink slot, and the second RACH configuration including a set of full-duplex ROs within one or more full-duplex slots. The operations of 1905 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed by a control signaling receiving manager 1125 as described with reference to FIG. 11.
At 1910, the method may include receiving, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration including a set of common POs within one or more additional half-duplex uplink slots, and the second PUSCH configuration including a set of full-duplex POs within one or additional more full-duplex slots, where the set of common ROs are mapped to the set of common POs, and where the set of full-duplex ROs mapped to the set of full-duplex POs. The operations of 1910 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed by a control signaling receiving manager 1125 as described with reference to FIG. 11.
At 1915, the method may include transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RO from the set of common ROs, or via a full-duplex RO from the set of full-duplex ROs. The operations of 1915 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed by a preamble transmitting manager 1130 as described with reference to FIG. 11.
At 1920, the method may include transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PO from the set of common POs that maps to the common RO based on transmitting the preamble via the common RO, or via a full-duplex PO from the set of full-duplex POs that maps to the common RO used to transmit the preamble based on transmitting the preamble via the full-duplex RO. The operations of 1920 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1920 may be performed by a payload transmitting manager 1135 as described with reference to FIG. 11.
At 1925, the method may include receiving, from the network entity, a second message of the two-step random access procedure based on transmitting the preamble and the payload of the first message of the two-step random access procedure. The operations of 1925 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1925 may be performed by a RACH procedure manager 1140 as described with reference to FIG. 11.
The following provides an overview of aspects of the present disclosure:
Aspect 1: A method for wireless communications at a UE, comprising: receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, wherein the random access configuration is associated with a RACH configuration comprising a plurality of common RACH occasions within a first half-duplex uplink slot; receiving, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration comprising a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration comprising a set of full-duplex PUSCH occasions within one or more full-duplex slots; transmitting a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the plurality of common RACH occasions; transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that is associated with the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that is associated with the common RACH occasion used to transmit the preamble; and receiving, from the network entity, a second message of the two-step random access procedure based at least in part on transmitting the preamble and the payload of the first message of the two-step random access procedure.
Aspect 2: The method of aspect 1, wherein the plurality of common RACH occasions are associated with a plurality of preambles, the method further comprising: receiving, via the first control signaling, the second control signaling, or both, a first mapping configuration between the plurality of preambles of the plurality of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the plurality of preambles of the plurality of common RACH occasions and the set of full-duplex PUSCH occasions; and selecting one of the common PUSCH occasion or the full-duplex PUSCH occasion that maps to the common RACH occasion used to transmit the preamble in accordance with the first mapping configuration or the second mapping configuration, wherein the payload of the first message is transmitted via the selected one of the common PUSCH occasion or the full-duplex PUSCH occasion.
Aspect 3: The method of any of aspects 1 through 2, wherein each common RACH occasion from the plurality of common RACH occasions is mapped to a plurality of full-duplex PUSCH occasions from the set of full-duplex PUSCH occasions.
Aspect 4: The method of any of aspects 1 through 3, wherein the second PUSCH configuration comprises a first sub-configuration associated with a first preamble group comprising the set of full-duplex PUSCH occasions, and a second sub-configuration associated with a second preamble group comprising an additional set of full-duplex PUSCH occasions.
Aspect 5: The method of any of aspects 1 through 4, further comprising: selecting one of the common PUSCH occasion or the full-duplex PUSCH occasion that maps to the common RACH occasion based at least in part on a relative timing of the common PUSCH occasion and the full-duplex PUSCH occasion in a time domain, one or more measured or predicted downlink signal quality metrics associated with slots that include the common PUSCH occasion and the full-duplex PUSCH occasion, a radio resource control configuration, a PUSCH transmission power relative to a transmission power threshold associated with the one or more full-duplex slots, a type of UE, or any combination thereof, wherein the payload of the first message of the two-step random access procedure is transmitted via the selected one of the common PUSCH occasion or the full-duplex PUSCH occasion.
Aspect 6: The method of any of aspects 1 through 5, further comprising: determining a validity of each full-duplex PUSCH occasion within the set of full-duplex PUSCH occasions based at least in part on a type of slot corresponding to each of the set of full-duplex PUSCH occasions, the type of slot comprising a full-duplex slot type or a half-duplex slot type.
Aspect 7: The method of aspect 6, wherein determining the validity of each full-duplex PUSCH occasion comprises: determining that each full-duplex PUSCH occasion of the set of full-duplex PUSCH occasions is valid regardless of the type of slot in accordance with a first validity rule; or determining that a subset of PUSCH occasions from the set of full-duplex PUSCH occasions are invalid based at least in part on the subset of PUSCH occasions being positioned within non-full-duplex slots and in accordance with a second validity rule.
Aspect 8: The method of any of aspects 1 through 7, wherein the set of full-duplex PUSCH occasions comprise a first subset of full-duplex PUSCH occasions within the one or more full-duplex slots, and a second subset of full-duplex PUSCH occasions that overlap in a time domain with the set of common PUSCH occasions within the one or more second half-duplex uplink slots, and the plurality of common RACH occasions are associated with a plurality of preambles , the plurality of preambles are mapped to the set of common PUSCH occasions and the set of full-duplex PUSCH occasions such that temporally overlapping pairs of PUSCH occasions are associated with one or more common preambles of the plurality of preambles, each temporally overlapping pair of PUSCH occasions comprise one of the second subset of full-duplex PUSCH occasions and one of the set of common PUSCH occasions.
Aspect 9: The method of any of aspects 1 through 8, further comprising: monitoring a plurality of synchronization signal blocks, the plurality of synchronization signal blocks corresponding with the plurality of common RACH occasions; and selecting the common RACH occasion from the plurality of common RACH occasions based at least in part on the monitoring.
Aspect 10: The method of any of aspects 1 through 9, wherein the set of full-duplex PUSCH occasions comprise SBFD PUSCH occasions, and the one or more full-duplex slots comprise one or more SBFD slots.
Aspect 11: The method of any of aspects 1 through 10, wherein the first PUSCH configuration indicates a first starting resource block frequency configuration associated with the set of common PUSCH occasions, and the second PUSCH configuration indicates a second starting resource block frequency configuration associated with the set of full-duplex PUSCH occasions.
Aspect 12: The method of any of aspects 1 through 11, wherein the first PUSCH configuration indicates a first quantity of frequency-division multiplexed PUSCH occasions associated with the set of common PUSCH occasions within the one or more second half-duplex uplink slots, and the second PUSCH configuration indicates a second quantity of frequency-division multiplexed PUSCH occasions associated with the set of full-duplex PUSCH occasions within the one or more full-duplex slots.
Aspect 13: The method of any of aspects 1 through 12, wherein the plurality of common RACH occasions and the set of common PUSCH occasions are usable by full-duplex-aware UEs and non-full-duplex-aware UEs, and the set of full-duplex PUSCH occasions are usable by full-duplex-aware UEs but unusable by non-full-duplex-aware UEs.
Aspect 14: A method for wireless communications at a UE, comprising: receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, wherein the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration comprising a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration comprising a set of full-duplex RACH occasions within one or more full-duplex slots; receiving, via the first control signaling, second control signaling, or both, a PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration comprising a plurality of PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the plurality of PUSCH occasions comprising a set of common PUSCH occasions within one or more additional half-duplex uplink slots; transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion of the set of full-duplex RACH occasions; transmitting a payload of the first message of the two-step random access procedure to the network entity via a common PUSCH occasion of the set of common PUSCH occasions that maps to the common RACH occasion or the full-duplex RACH occasion that was used to transmit the preamble; and receiving, from the network entity, a second message of the two-step random access procedure based at least in part on transmitting the preamble and the payload of the first message of the two-step random access procedure.
Aspect 15: The method of aspect 14, wherein the first half-duplex uplink slot including the set of common RACH occasions comprises a PRACH slot, the PUSCH configuration comprises a first time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common PUSCH occasions, and a second time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common PUSCH occasions.
Aspect 16: The method of any of aspects 14 through 15, wherein the set of common RACH occasions and the set of full-duplex RACH occasions are associated with a plurality of preambles, the method further comprising: receiving, via the first control signaling, the second control signaling, or both, a first mapping configuration between the plurality of preambles of the set of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the plurality of preambles of the set of full-duplex RACH occasions and the set of common PUSCH occasions.
Aspect 17: The method of any of aspects 14 through 16, wherein each common PUSCH occasion from the set of common PUSCH occasions is mapped to at least one common RACH occasion from the set of common RACH occasions and at least one full-duplex RACH occasion from the set of full-duplex RACH occasions.
Aspect 18: The method of any of aspects 14 through 17, further comprising: selecting one of the common RACH occasion or the full-duplex RACH occasion based at least in part on a relative timing of the common RACH occasion and the full-duplex RACH occasion in a time domain, one or more measured or predicted signal quality metrics associated with slots that include the common RACH occasion and the full-duplex RACH occasion, a PUSCH transmission power relative to a transmission power threshold associated with the one or more full-duplex slots, a radio resource control configuration, a type of UE, or any combination thereof, wherein the preamble of the first message of the two-step random access procedure is transmitted via the selected one of the common RACH occasion or the full-duplex RACH occasion.
Aspect 19: The method of any of aspects 14 through 18, further comprising: determining a validity of each full-duplex RACH occasion within the set of full-duplex RACH occasions based at least in part on a type of slot corresponding to each of the set of full-duplex RACH occasions, the type of slot comprising a full-duplex slot type or a half-duplex slot type.
Aspect 20: The method of aspect 19, wherein determining the validity of each full-duplex RACH occasion comprises: determining that each full-duplex RACH occasion of the set of full-duplex RACH occasions is valid regardless of the type of slot in accordance with a first validity rule; or determining that a subset of RACH occasions from the set of full-duplex RACH occasions are invalid based at least in part on the subset of RACH occasions being positioned within non-full-duplex slots and in accordance with a second validity rule.
Aspect 21: The method of any of aspects 14 through 20, wherein the set of full-duplex RACH occasions comprise a first subset of full-duplex RACH occasions within the one or more full-duplex slots, and a second subset of full-duplex RACH occasions that overlap in a time domain with the set of common RACH occasions within the first half-duplex uplink slot, and the set of common RACH occasions and the set of full-duplex RACH occasions are associated with a plurality of preambles such that temporally overlapping pairs of RACH occasions map to one or more common preambles of the plurality of preambles, each temporally overlapping pair of RACH occasions comprise one of the second subset of full-duplex RACH occasions and one of the set of common RACH occasions.
Aspect 22: The method of any of aspects 14 through 21, wherein the set of full-duplex RACH occasions comprise SBFD RACH occasions, and the one or more full-duplex slots comprise one or more SBFD slots.
Aspect 23: A method for wireless communications at a UE, comprising: receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, wherein the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration comprising a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration comprising a set of full-duplex RACH occasions within one or more full-duplex slots; receiving, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration comprising a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration comprising a set of full-duplex PUSCH occasions within one or additional more full-duplex slots, wherein the set of common RACH occasions are mapped to the set of common PUSCH occasions, and wherein the set of full-duplex RACH occasions mapped to the set of full-duplex PUSCH occasions; transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion from the set of full-duplex RACH occasions; transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that maps to the common RACH occasion based at least in part on transmitting the preamble via the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that maps to the common RACH occasion used to transmit the preamble based at least in part on transmitting the preamble via the full-duplex RACH occasion; and receiving, from the network entity, a second message of the two-step random access procedure based at least in part on transmitting the preamble and the payload of the first message of the two-step random access procedure.
Aspect 24: The method of aspect 23, , wherein the set of common RACH occasions and the set of full-duplex RACH occasions are associated with a plurality of preambles, the method further comprising: receiving, via the first control signaling, the second control signaling, or both, a first mapping configuration between the plurality of preambles of the set of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the plurality of preambles of the set of full-duplex RACH occasions and the set of full-duplex PUSCH occasions.
Aspect 25: The method of aspect 24, further comprising: receiving, via the first control signaling, the second control signaling, or both, a third mapping configuration between the plurality of preambles of set of common RACH occasions and the set of full-duplex PUSCH occasions, a fourth mapping configuration between the plurality of preambles of the set of full-duplex RACH occasions and the set of common PUSCH occasions, or both.
Aspect 26: The method of any of aspects 23 through 25, wherein the set of full-duplex RACH occasions comprise SBFD RACH occasions, and the set of full-duplex PUSCH occasions comprise SBFD PUSCH occasions, the one or more full-duplex slots, the one or more additional full-duplex slots, or both, comprise one or more SBFD slots.
Aspect 27: The method of any of aspects 23 through 26, further comprising: receiving, via the first control signaling, the second control signaling, or both, an indication that the first RACH configuration, second RACH configuration, the first PUSCH configuration, the second PUSCH configuration, or any combination thereof, are usable for performing random access procedures associated with system information requests, physical downlink control channel ordering, beam failure recovery, mobility, or any combination thereof.
Aspect 28: The method of any of aspects 23 through 27, further comprising: receiving, via the first control signaling, the second control signaling, or both, an indication that the second RACH configuration, the second PUSCH configuration, or both, comprise UE-specific configurations or cell-specific configurations.
Aspect 29: The method of any of aspects 23 through 28, further comprising: receiving, via the first control signaling, the second control signaling, third control signaling, or any combination thereof, a common random access configuration associated with one or more operations different from the two-step random access procedure; and performing the one or more operations in accordance with either the common random access configuration, or in accordance with the second RACH configuration and the second PUSCH configuration.
Aspect 30: The method of any of aspects 23 through 29, further comprising: determining that the UE has not been configured with a common random access configuration associated with one or more operations different from the two-step random access procedure; and performing the one or more operations in accordance with the first RACH configuration and the first PUSCH configuration, or in accordance with the second RACH configuration and the second PUSCH configuration.
Aspect 31: A method for wireless communications at a network entity, comprising: transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, wherein the random access configuration is associated with a RACH configuration comprising a plurality of common RACH occasions within a first half-duplex uplink slot; transmitting, via the first control signaling, second control signaling, or both, a first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration comprising a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration comprising a set of full-duplex PUSCH occasions within one or more full-duplex slots; receiving a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the plurality of common RACH occasions; receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that is associated with the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that is associated with the common RACH occasion used to receive the preamble; and transmitting, to the UE, a second message of the two-step random access procedure based at least in part on receiving the preamble and the payload of the first message of the two-step random access procedure.
Aspect 32: The method of aspect 31, wherein the plurality of common RACH occasions are associated with a plurality of preambles, the method further comprising: transmitting, via the first control signaling, the second control signaling, or both, a first mapping configuration between the plurality of preambles of the plurality of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the plurality of preambles of the plurality of common RACH occasions and the set of full-duplex PUSCH occasions; and identifying one of the common PUSCH occasion or the full-duplex PUSCH occasion that maps to the common RACH occasion used to transmit the preamble in accordance with the first mapping configuration or the second mapping configuration, wherein the payload of the first message is received via the identified one of the common PUSCH occasion or the full-duplex PUSCH occasion.
Aspect 33: The method of any of aspects 31 through 32, wherein each common RACH occasion from the plurality of common RACH occasions is mapped to a plurality of full-duplex PUSCH occasions from the set of full-duplex PUSCH occasions.
Aspect 34: The method of any of aspects 31 through 33, wherein the second PUSCH configuration comprises a first sub-configuration associated with a first preamble group comprising the set of full-duplex PUSCH occasions, and a second sub-configuration associated with a second preamble group comprising an additional set of full-duplex PUSCH occasions.
Aspect 35: The method of any of aspects 31 through 34, further comprising: identifying one of the common PUSCH occasion or the full-duplex PUSCH occasion that maps to the common RACH occasion based at least in part on a relative timing of the common PUSCH occasion and the full-duplex PUSCH occasion in a time domain, one or more measured or predicted downlink signal quality metrics associated with slots that include the common PUSCH occasion and the full-duplex PUSCH occasion, a radio resource control configuration, a PUSCH transmission power relative to a transmission power threshold associated with the one or more full-duplex slots, a type of UE, or any combination thereof, wherein the payload of the first message of the two-step random access procedure is received via the identified one of the common PUSCH occasion or the full-duplex PUSCH occasion.
Aspect 36: The method of any of aspects 31 through 35, further comprising: determining a validity of each full-duplex PUSCH occasion within the set of full-duplex PUSCH occasions based at least in part on a type of slot corresponding to each of the set of full-duplex PUSCH occasions, the type of slot comprising a full-duplex slot type or a half-duplex slot type.
Aspect 37: The method of aspect 36, wherein determining the validity of each full-duplex PUSCH occasion comprises: determining that each full-duplex PUSCH occasion of the set of full-duplex PUSCH occasions is valid regardless of the type of slot in accordance with a first validity rule; or determining that a subset of PUSCH occasions from the set of full-duplex PUSCH occasions are invalid based at least in part on the subset of PUSCH occasions being positioned within non-full-duplex slots and in accordance with a second validity rule.
Aspect 38: The method of any of aspects 31 through 37, wherein the set of full-duplex PUSCH occasions comprise a first subset of full-duplex PUSCH occasions within the one or more full-duplex slots, and a second subset of full-duplex PUSCH occasions that overlap in a time domain with the set of common PUSCH occasions within the one or more second half-duplex uplink slots, and the plurality of common RACH occasions are associated with a plurality of preambles , the plurality of preambles are mapped to the set of common PUSCH occasions and the set of full-duplex PUSCH occasions such that temporally overlapping pairs of PUSCH occasions are associated with one or more common preambles of the plurality of preambles, each temporally overlapping pair of PUSCH occasions comprise one of the second subset of full-duplex PUSCH occasions and one of the set of common PUSCH occasions,
Aspect 39: The method of any of aspects 31 through 38, wherein the set of full-duplex PUSCH occasions comprise SBFD PUSCH occasions, and the one or more full-duplex slots comprise one or more SBFD slots.
Aspect 40: The method of any of aspects 31 through 39, wherein the first PUSCH configuration indicates a first starting resource block frequency configuration associated with the set of common PUSCH occasions, and the second PUSCH configuration indicates a second starting resource block frequency configuration associated with the set of full-duplex PUSCH occasions.
Aspect 41: The method of any of aspects 31 through 40, wherein the first PUSCH configuration indicates a first quantity of frequency-division multiplexed PUSCH occasions associated with the set of common PUSCH occasions within the one or more second half-duplex uplink slots, and the second PUSCH configuration indicates a second quantity of frequency-division multiplexed PUSCH occasions associated with the set of full-duplex PUSCH occasions within the one or more full-duplex slots.
Aspect 42: The method of any of aspects 31 through 41, wherein the plurality of common RACH occasions and the set of common PUSCH occasions are usable by full-duplex-aware UEs and non-full-duplex-aware UEs, and the set of full-duplex PUSCH occasions are usable by full-duplex-aware UEs but unusable by non-full-duplex-aware UEs.
Aspect 43: A method for wireless communications at a network entity, comprising: transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, wherein the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration comprising a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration comprising a set of full-duplex RACH occasions within one or more full-duplex slots; transmitting, via the first control signaling, second control signaling, or both, a PUSCH configuration for performing the two-step random access procedure, the PUSCH configuration comprising a plurality of PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the plurality of PUSCH occasions comprising a set of common PUSCH occasions within one or more additional half-duplex uplink slots; receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion of the set of full-duplex RACH occasions; receiving a payload of the first message of the two-step random access procedure to the network entity via a common PUSCH occasion of the set of common PUSCH occasions that maps to the common RACH occasion or the full-duplex RACH occasion that was used to receive the preamble; and transmitting, to the UE, a second message of the two-step random access procedure based at least in part on receiving the preamble and the payload of the first message of the two-step random access procedure.
Aspect 44: The method of aspect 43, wherein the first half-duplex uplink slot including the set of common RACH occasions comprises a PRACH slot, the PUSCH configuration comprises a first time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common PUSCH occasions, and a second time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common PUSCH occasions.
Aspect 45: The method of any of aspects 43 through 44, wherein the set of common RACH occasions and the set of full-duplex RACH occasions are associated with a plurality of preambles, the method further comprising: transmitting, via the first control signaling, the second control signaling, or both, a first mapping configuration between the plurality of preambles of the set of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the plurality of preambles of the set of full-duplex RACH occasions and the set of common PUSCH occasions.
Aspect 46: The method of any of aspects 43 through 45, wherein each common PUSCH occasion from the set of common PUSCH occasions is mapped to at least one common RACH occasion from the set of common RACH occasions and at least one full-duplex RACH occasion from the set of full-duplex RACH occasions.
Aspect 47: The method of any of aspects 43 through 46, further comprising: identifying one of the common RACH occasion or the full-duplex RACH occasion based at least in part on a relative timing of the common RACH occasion and the full-duplex RACH occasion in a time domain, one or more measured or predicted signal quality metrics associated with slots that include the common RACH occasion and the full-duplex RACH occasion, a PUSCH transmission power relative to a transmission power threshold associated with the one or more full-duplex slots, a radio resource control configuration, a type of UE, or any combination thereof, wherein the preamble of the first message of the two-step random access procedure is received via the identified one of the common RACH occasion or the full-duplex RACH occasion.
Aspect 48: The method of any of aspects 43 through 47, further comprising: determining a validity of each full-duplex RACH occasion within the set of full-duplex RACH occasions based at least in part on a type of slot corresponding to each of the set of full-duplex RACH occasions, the type of slot comprising a full-duplex slot type or a half-duplex slot type.
Aspect 49: The method of aspect 48, wherein determining the validity of each full-duplex RACH occasion comprises: determining that each full-duplex RACH occasion of the set of full-duplex RACH occasions is valid regardless of the type of slot in accordance with a first validity rule; or determining that a subset of RACH occasions from the set of full-duplex RACH occasions are invalid based at least in part on the subset of RACH occasions being positioned within non-full-duplex slots and in accordance with a second validity rule.
Aspect 50: The method of any of aspects 43 through 49, wherein the set of full-duplex RACH occasions comprise a first subset of full-duplex RACH occasions within the one or more full-duplex slots, and a second subset of full-duplex RACH occasions that overlap in a time domain with the set of common RACH occasions within the first half-duplex uplink slot, and the set of common RACH occasions and the set of full-duplex RACH occasions are associated with a plurality of preambles such that temporally overlapping pairs of RACH occasions map to one or more common preambles of the plurality of preambles, each temporally overlapping pair of RACH occasions comprise one of the second subset of full-duplex RACH occasions and one of the set of common RACH occasions.
Aspect 51: The method of any of aspects 43 through 50, wherein the set of full-duplex RACH occasions comprise SBFD RACH occasions, and the one or more full-duplex slots comprise one or more SBFD slots.
Aspect 52: A method for wireless communications at a network entity, comprising: transmitting, to a UE via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, wherein the random access configuration is associated with a first RACH configuration and a second RACH configuration, the first RACH configuration comprising a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration comprising a set of full-duplex RACH occasions within one or more full-duplex slots; transmitting, via the first control signaling, second control signaling, or both, first PUSCH configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration comprising a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration comprising a set of full-duplex PUSCH occasions  within one or additional more full-duplex slots, wherein the set of common RACH occasions are mapped to the set of common PUSCH occasions, and wherein the set of full-duplex RACH occasions mapped to the set of full-duplex PUSCH occasions; receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion from the set of full-duplex RACH occasions; receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that maps to the common RACH occasion based at least in part on transmitting the preamble via the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that maps to the common RACH occasion used to receive the preamble based at least in part on receiving the preamble via the full-duplex RACH occasion; and transmitting, to the UE, a second message of the two-step random access procedure based at least in part on receiving the preamble and the payload of the first message of the two-step random access procedure.
Aspect 53: The method of aspect 52, wherein the set of common RACH occasions and the set of full-duplex RACH occasions are associated with a plurality of preambles, the method further comprising: transmitting, via the first control signaling, the second control signaling, or both, a first mapping configuration between the plurality of preambles of the set of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the plurality of preambles of the set of full-duplex RACH occasions and the set of full-duplex PUSCH occasions.
Aspect 54: The method of any of aspects 52 through 53, further comprising: transmitting, via the first control signaling, the second control signaling, or both, a third mapping configuration between the plurality of preambles of set of common RACH occasions and the set of full-duplex PUSCH occasions, a fourth mapping configuration between the plurality of preambles of the set of full-duplex RACH occasions and the set of common PUSCH occasions, or both.
Aspect 55: The method of any of aspects 52 through 54, wherein the set of full-duplex RACH occasions comprise SBFD RACH occasions, and the set of full-duplex PUSCH occasions comprise SBFD PUSCH occasions, the one or more full-duplex slots, the one or more additional full-duplex slots, or both, comprise one or more SBFD slots.
Aspect 56: The method of any of aspects 52 through 55, further comprising: transmitting, via the first control signaling, the second control signaling, or both, an indication that the first RACH configuration, second RACH configuration, the first PUSCH configuration, the second PUSCH configuration, or any combination thereof, are usable for performing random access procedures associated with system information requests, physical downlink control channel ordering, beam failure recovery, mobility, or any combination thereof.
Aspect 57: The method of any of aspects 52 through 56, further comprising: transmitting, via the first control signaling, the second control signaling, or both, an indication that the second RACH configuration, the second PUSCH configuration, or both, comprise UE-specific configurations or cell-specific configurations.
Aspect 58: A UE comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 1 through 13.
Aspect 59: A UE comprising at least one means for performing a method of any of aspects 1 through 13.
Aspect 60: A non-transitory computer-readable medium storing code the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 13.
Aspect 61: A UE comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 14 through 22.
Aspect 62: A UE comprising at least one means for performing a method of any of aspects 14 through 22.
Aspect 63: A non-transitory computer-readable medium storing code the code comprising instructions executable by one or more processors to perform a method of any of aspects 14 through 22.
Aspect 64: A UE comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 23 through 30.
Aspect 65: A UE comprising at least one means for performing a method of any of aspects 23 through 30.
Aspect 66: A non-transitory computer-readable medium storing code the code comprising instructions executable by one or more processors to perform a method of any of aspects 23 through 30.
Aspect 67: A network entity comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method of any of aspects 31 through 42.
Aspect 68: A network entity comprising at least one means for performing a method of any of aspects 31 through 42.
Aspect 69: A non-transitory computer-readable medium storing code the code comprising instructions executable by one or more processors to perform a method of any of aspects 31 through 42.
Aspect 70: A network entity comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method of any of aspects 43 through 51.
Aspect 71: A network entity comprising at least one means for performing a method of any of aspects 43 through 51.
Aspect 72: A non-transitory computer-readable medium storing code the code comprising instructions executable by one or more processors to perform a method of any of aspects 43 through 51.
Aspect 73: A network entity comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method of any of aspects 52 through 57.
Aspect 74: A network entity comprising at least one means for performing a method of any of aspects 52 through 57.
Aspect 75: A non-transitory computer-readable medium storing code the code comprising instructions executable by one or more processors to perform a method of any of aspects 52 through 57.
It should be noted that the methods described herein describe possible implementations. The operations and the steps may be rearranged or otherwise modified and other implementations are possible. Further, aspects from two or more of the methods may be combined.
Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.
Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, a graphics processing unit (GPU) , a neural processing unit (NPU) , an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor but, in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration) . Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.
The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.
As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. ”
As used herein, including in the claims, the article “a” before a noun is open-ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns. Thus, the terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. For example, if a claim recites “a component” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “a component” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular  function. Subsequent reference to a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components, ” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ” Similarly, subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components. For example, referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ”
The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database, or another data structure) , ascertaining, and the like. Also, “determining” can include receiving (e.g., receiving information) , accessing (e.g., accessing data stored in memory) , and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.
In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label or other subsequent reference label.
The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration” and not “preferred” or “advantageous over other examples. ” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some figures, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.
The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims (62)

  1. A user equipment (UE) , comprising:
    one or more memories storing processor-executable code; and
    one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to:
    receive, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, wherein the random access configuration is associated with a random access channel (RACH) configuration comprising a plurality of common RACH occasions within a first half-duplex uplink slot;
    receive, via the first control signaling, second control signaling, or both, a first physical uplink shared channel (PUSCH) configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration comprising a set of common POs within one or more second half-duplex uplink slots, and the second PUSCH configuration comprising a set of full-duplex PUSCH occasions within one or more full-duplex slots;
    transmit a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the plurality of common RACH occasions;
    transmit a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that is associated with the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that is associated with the common RACH occasion used to transmit the preamble; and
    receive, from the network entity, a second message of the two-step random access procedure based at least in part on transmitting the preamble and the payload of the first message of the two-step random access procedure.
  2. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    receive, via the first control signaling, the second control signaling, or both, a first mapping configuration between a plurality of preambles of the plurality of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the plurality of preambles of the plurality of common RACH occasions and the set of full-duplex PUSCH occasions; and
    select one of the common PUSCH occasion or the full-duplex PUSCH occasion that maps to the common RACH occasion used to transmit the preamble in accordance with the first mapping configuration or the second mapping configuration, wherein the payload of the first message is transmitted via the selected one of the common PUSCH occasion or the full-duplex PUSCH occasion.
  3. The UE of claim 1, wherein each common RACH occasion from the plurality of common RACH occasions is mapped to a plurality of full-duplex PUSCH occasions from the set of full-duplex PUSCH occasions.
  4. The UE of claim 1, wherein the second PUSCH configuration comprises a first sub-configuration associated with a first preamble group comprising the set of full-duplex PUSCH occasions, and a second sub-configuration associated with a second preamble group comprising an additional set of full-duplex PUSCH occasions.
  5. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    select one of the common PUSCH occasion or the full-duplex PUSCH occasion that maps to the common RACH occasion based at least in part on a relative timing of the common PUSCH occasion and the full-duplex PUSCH occasion in a time domain, one or more measured or predicted downlink signal quality metrics associated with slots that include the common PUSCH occasion and the full-duplex PUSCH occasion, a radio resource control configuration, a PUSCH transmission power relative to a transmission power threshold associated with the one or more full-duplex slots, a type of UE, or any combination thereof, wherein the payload of the first message of the two-step random access procedure is transmitted via the selected one of the common PUSCH occasion or the full-duplex PUSCH occasion.
  6. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    determine a validity of each full-duplex PUSCH occasion within the set of full-duplex PUSCH occasions based at least in part on a type of slot corresponding to each of the set of full-duplex PUSCH occasions, the type of slot comprising a full-duplex slot type or a half-duplex slot type.
  7. The UE of claim 6, wherein, to determine the validity of each full-duplex PUSCH occasion, the one or more processors are individually or collectively operable to execute the code to cause the UE to:
    determine that each full-duplex PUSCH occasion of the set of full-duplex PUSCH occasions is valid regardless of the type of slot in accordance with a first validity rule; or
    determine that a subset of PUSCH occasions from the set of full-duplex PUSCH occasions are invalid based at least in part on the subset of PUSCH occasions being positioned within non-full-duplex slots and in accordance with a second validity rule.
  8. The UE of claim 1,
    wherein the set of full-duplex PUSCH occasions comprise a first subset of full-duplex PUSCH occasions within the one or more full-duplex slots, and a second subset of full-duplex PUSCH occasions that overlap in a time domain with the set of common PUSCH occasions within the one or more second half-duplex uplink slots, and
    wherein the plurality of common RACH occasions are associated with a plurality of preambles, wherein the plurality of preambles are mapped to the set of common PUSCH occasions and the set of full-duplex PUSCH occasions such that temporally overlapping pairs of PUSCH occasions are associated with one or more common preambles of the plurality of preambles, wherein each temporally overlapping pair of PUSCH occasions comprise one of the second subset of full-duplex PUSCH occasions and one of the set of common PUSCH occasions.
  9. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    monitor a plurality of synchronization signal blocks, the plurality of synchronization signal blocks corresponding with the plurality of common RACH occasions; and
    select the common RACH occasion from the plurality of common RACH occasions based at least in part on the monitoring.
  10. The UE of claim 1, wherein the set of full-duplex PUSCH occasions comprise sub-band full-duplex (SBFD) PUSCH occasions, and wherein the one or more full-duplex slots comprise one or more SBFD slots.
  11. The UE of claim 1, wherein the first PUSCH configuration indicates a first starting resource block frequency configuration associated with the set of common PUSCH occasions, and wherein the second PUSCH configuration indicates a second starting resource block frequency configuration associated with the set of full-duplex PUSCH occasions.
  12. The UE of claim 1, wherein the first PUSCH configuration indicates a first quantity of frequency-division multiplexed PUSCH occasions associated with the set of common PUSCH occasions within the one or more second half-duplex uplink slots, and wherein the second PUSCH configuration indicates a second quantity of frequency-division multiplexed PUSCH occasions associated with the set of full-duplex PUSCH occasions within the one or more full-duplex slots.
  13. The UE of claim 1, wherein the plurality of common RACH occasions and the set of common PUSCH occasions are usable by full-duplex-aware UEs and non-full-duplex-aware UEs, and wherein the set of full-duplex PUSCH occasions are usable by full-duplex-aware UEs but unusable by non-full-duplex-aware UEs.
  14. A user equipment (UE) , comprising:
    one or more memories storing processor-executable code; and
    one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to:
    receive, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity,  wherein the random access configuration is associated with a first random access channel (RACH) configuration and a second RACH configuration, the first RACH configuration comprising a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration comprising a set of full-duplex RACH occasions within one or more full-duplex slots;
    receive, via the first control signaling, second control signaling, or both, a physical uplink shared channel (PUSCH) configuration for performing the two-step random access procedure, the PUSCH configuration comprising a plurality of PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the plurality of PUSCH occasions comprising a set of common PUSCH occasions within one or more additional half-duplex uplink slots;
    transmit a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion of the set of full-duplex RACH occasions;
    transmit a payload of the first message of the two-step random access procedure to the network entity via a common PUSCH occasion of the set of common PUSCH occasions that maps to the common RACH occasion or the full-duplex RACH occasion that was used to transmit the preamble; and
    receive, from the network entity, a second message of the two-step random access procedure based at least in part on transmitting the preamble and the payload of the first message of the two-step random access procedure.
  15. The UE of claim 14, wherein the first half-duplex uplink slot including the set of common RACH occasions comprises a physical RACH (PRACH) slot, wherein the PUSCH configuration comprises a first time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common PUSCH occasions, and a second time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common PUSCH occasions.
  16. The UE of claim 14, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    receive, via the first control signaling, the second control signaling, or both, a first mapping configuration between the plurality of preambles of the set of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the plurality of preambles of the set of full-duplex RACH occasions and the set of common PUSCH occasions.
  17. The UE of claim 14, wherein each common PUSCH occasion from the set of common PUSCH occasions is mapped to at least one common RACH occasion from the set of common RACH occasions and at least one full-duplex RACH occasion from the set of full-duplex RACH occasions.
  18. The UE of claim 14, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    select one of the common RACH occasion or the full-duplex RACH occasion based at least in part on a relative timing of the common RACH occasion and the full-duplex RACH occasion in a time domain, one or more measured or predicted signal quality metrics associated with slots that include the common RACH occasion and the full-duplex RACH occasion, a PUSCH transmission power relative to a transmission power threshold associated with the one or more full-duplex slots, a radio resource control configuration, a type of UE, or any combination thereof, wherein the preamble of the first message of the two-step random access procedure is transmitted via the selected one of the common RACH occasion or the full-duplex RACH occasion.
  19. The UE of claim 14, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    determine a validity of each full-duplex RACH occasion within the set of full-duplex RACH occasions based at least in part on a type of slot corresponding to each of the set of full-duplex RACH occasions, the type of slot comprising a full-duplex slot type or a half-duplex slot type.
  20. The UE of claim 19, wherein, to determine the validity of each full-duplex RACH occasion, the one or more processors are individually or collectively operable to execute the code to cause the UE to:
    determine that each full-duplex RACH occasion of the set of full-duplex RACH occasions is valid regardless of the type of slot in accordance with a first validity rule; or
    determine that a subset of RACH occasions from the set of full-duplex RACH occasions are invalid based at least in part on the subset of RACH occasions being positioned within non-full-duplex slots and in accordance with a second validity rule.
  21. The UE of claim 14,
    wherein the set of full-duplex RACH occasions comprise a first subset of full-duplex RACH occasions within the one or more full-duplex slots, and a second subset of full-duplex RACH occasions that overlap in a time domain with the set of common RACH occasions within the first half-duplex uplink slot, and
    wherein the set of common RACH occasions and the set of full-duplex RACH occasions are associated with a plurality of preambles such that temporally overlapping pairs of RACH occasions map to one or more common preambles of the plurality of preambles, wherein each temporally overlapping pair of RACH occasions comprise one of the second subset of full-duplex RACH occasions and one of the set of common RACH occasions.
  22. The UE of claim 14, wherein the set of full-duplex RACH occasions comprise sub-band full-duplex (SBFD) RACH occasions, and wherein the one or more full-duplex slots comprise one or more SBFD slots.
  23. A user equipment (UE) , comprising:
    one or more memories storing processor-executable code; and
    one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to:
    receive, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, wherein the random access configuration is associated with a first random access channel (RACH) configuration and a second RACH configuration, the first RACH configuration comprising a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration comprising a set of full-duplex RACH occasions within one or more full-duplex slots;
    receive, via the first control signaling, second control signaling, or both, first physical uplink shared channel (PUSCH) configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration comprising a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration comprising a set of full-duplex PUSCH occasions within one or additional more full-duplex slots, wherein the set of common RACH occasions are mapped to the set of common PUSCH occasions, and wherein the set of full-duplex RACH occasions mapped to the set of full-duplex PUSCH occasions;
    transmit a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion from the set of full-duplex RACH occasions;
    transmit a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that maps to the common RACH occasion based at least in part on transmitting the preamble via the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that maps to the common RACH occasion used to transmit the preamble based at least in part on transmitting the preamble via the full-duplex RACH occasion; and
    receive, from the network entity, a second message of the two-step random access procedure based at least in part on transmitting the preamble and the payload of the first message of the two-step random access procedure.
  24. The UE of claim 23, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    receive, via the first control signaling, the second control signaling, or both, a first mapping configuration between a plurality of preambles of the set of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the plurality of preambles of the set of full-duplex RACH occasions and the set of full-duplex PUSCH occasions.
  25. The UE of claim 24, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    receive, via the first control signaling, the second control signaling, or both, a third mapping configuration between the plurality of preambles of set of common RACH occasions and the set of full-duplex PUSCH occasions, a fourth mapping configuration between the plurality of preambles of the set of full-duplex RACH occasions and the set of common PUSCH occasions, or both.
  26. The UE of claim 23, wherein the set of full-duplex RACH occasions comprise sub-band full-duplex (SBFD) RACH occasions, and wherein the set of full-duplex PUSCH occasions comprise SBFD PUSCH occasions, wherein the one or more full-duplex slots, the one or more additional full-duplex slots, or both, comprise one or more SBFD slots.
  27. The UE of claim 23, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    receive, via the first control signaling, the second control signaling, or both, an indication that the first RACH configuration, second RACH configuration, the first PUSCH configuration, the second PUSCH configuration, or any combination thereof, are usable for performing random access procedures associated with system information requests, physical downlink control channel ordering, beam failure recovery, mobility, or any combination thereof.
  28. The UE of claim 23, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    receive, via the first control signaling, the second control signaling, or both, an indication that the second RACH configuration, the second PUSCH configuration, or both, comprise UE-specific configurations or cell-specific configurations.
  29. The UE of claim 23, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    receive, via the first control signaling, the second control signaling, third control signaling, or any combination thereof, a common random access configuration associated with one or more operations different from the two-step random access procedure; and
    perform the one or more operations in accordance with either the common random access configuration, or in accordance with the second RACH configuration and the second PUSCH configuration.
  30. The UE of claim 23, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:
    determine that the UE has not been configured with a common random access configuration associated with one or more operations different from the two-step random access procedure; and
    perform the one or more operations in accordance with the first RACH configuration and the first PUSCH configuration, or in accordance with the second RACH configuration and the second PUSCH configuration.
  31. A network entity, comprising:
    one or more memories storing processor-executable code; and
    one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to:
    transmit, to a user equipment (UE) via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, wherein the random access configuration is associated with a random access channel (RACH) configuration comprising a plurality of common RACH occasions within a first half-duplex uplink slot;
    transmit, via the first control signaling, second control signaling, or both, a first physical uplink shared channel (PUSCH) configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration comprising a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration comprising a set of full-duplex PUSCH occasions within one or more full-duplex slots;
    receive a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the plurality of common RACH occasions;
    receive a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that is associated with the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that is associated with the common RACH occasion used to receive the preamble; and
    transmit, to the UE, a second message of the two-step random access procedure based at least in part on receiving the preamble and the payload of the first message of the two-step random access procedure.
  32. The network entity of claim 31, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:
    transmit, via the first control signaling, the second control signaling, or both, a first mapping configuration between the plurality of preambles of the plurality of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the plurality of preambles of the plurality of common RACH occasions and the set of full-duplex PUSCH occasions; and
    identify one of the common PUSCH occasion or the full-duplex PUSCH occasion that maps to the common RACH occasion used to transmit the preamble in accordance with the first mapping configuration or the second mapping configuration, wherein the payload of the first message is received via the identified one of the common PUSCH occasion or the full-duplex PUSCH occasion.
  33. The network entity of claim 31, wherein each common RACH occasion from the plurality of common RACH occasions is mapped to a plurality of full-duplex PUSCH occasions from the set of full-duplex PUSCH occasions.
  34. The network entity of claim 31, wherein the second PUSCH configuration comprises a first sub-configuration associated with a first preamble group comprising the set of full-duplex PUSCH occasions, and a second sub-configuration associated with a second preamble group comprising an additional set of full-duplex PUSCH occasions.
  35. The network entity of claim 31, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:
    identify one of the common PUSCH occasion or the full-duplex PUSCH occasion that maps to the common RACH occasion based at least in part on a relative timing of the common PUSCH occasion and the full-duplex PUSCH occasion in a time domain, one or more measured or predicted downlink signal quality metrics associated with slots that include the common PUSCH occasion and the full-duplex PUSCH occasion, a radio resource control configuration, a PUSCH transmission power relative to a transmission power threshold associated with the one or more full-duplex slots, a type of UE, or any combination thereof, wherein the payload of the first message of the two-step random access procedure is received via the identified one of the common PUSCH occasion or the full-duplex PUSCH occasion.
  36. The network entity of claim 31, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:
    determine a validity of each full-duplex PUSCH occasion within the set of full-duplex PUSCH occasions based at least in part on a type of slot corresponding to each of the set of full-duplex PUSCH occasions, the type of slot comprising a full-duplex slot type or a half-duplex slot type.
  37. The network entity of claim 36, wherein, to determine the validity of each full-duplex PUSCH occasion, the one or more processors are individually or collectively operable to execute the code to cause the network entity to:
    determine that each full-duplex PUSCH occasion of the set of full-duplex PUSCH occasions is valid regardless of the type of slot in accordance with a first validity rule; or
    determine that a subset of PUSCH occasions from the set of full-duplex PUSCH occasions are invalid based at least in part on the subset of PUSCH occasions being positioned within non-full-duplex slots and in accordance with a second validity rule.
  38. The network entity of claim 31,
    wherein the set of full-duplex PUSCH occasions comprise a first subset of full-duplex PUSCH occasions within the one or more full-duplex slots, and a second subset of full-duplex PUSCH occasions that overlap in a time domain with the set of common PUSCH occasions within the one or more second half-duplex uplink slots, and
    wherein the plurality of common RACH occasions are associated with a plurality of preambles, wherein the plurality of preambles are mapped to the set of common PUSCH occasions and the set of full-duplex PUSCH occasions such that temporally overlapping pairs of PUSCH occasions are associated with one or more common preambles of the plurality of preambles, wherein each temporally overlapping pair of PUSCH occasions comprise one of the second subset of full-duplex PUSCH occasions and one of the set of common PUSCH occasions,
  39. The network entity of claim 31, wherein the set of full-duplex PUSCH occasions comprise sub-band full-duplex (SBFD) PUSCH occasions, and wherein the one or more full-duplex slots comprise one or more SBFD slots.
  40. The network entity of claim 31, wherein the first PUSCH configuration indicates a first starting resource block frequency configuration associated with the set of common PUSCH occasions, and wherein the second PUSCH configuration indicates a second starting resource block frequency configuration associated with the set of full-duplex PUSCH occasions.
  41. The network entity of claim 31, wherein the first PUSCH configuration indicates a first quantity of frequency-division multiplexed PUSCH occasions associated with the set of common PUSCH occasions within the one or more second half-duplex uplink slots, and wherein the second PUSCH configuration indicates a second quantity of frequency-division multiplexed PUSCH occasions associated with the set of full-duplex PUSCH occasions within the one or more full-duplex slots.
  42. The network entity of claim 31, wherein the plurality of common RACH occasions and the set of common PUSCH occasions are usable by full-duplex-aware UEs and non-full-duplex-aware UEs, and wherein the set of full-duplex PUSCH occasions are usable by full-duplex-aware UEs but unusable by non-full-duplex-aware UEs.
  43. A network entity, comprising:
    one or more memories storing processor-executable code; and
    one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to:
    transmit, to a user equipment (UE) via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, wherein the random access configuration is associated with a first random access channel (RACH) configuration and a second RACH configuration, the first RACH configuration comprising a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration comprising a set of full-duplex RACH occasions within one or more full-duplex slots;
    transmit, via the first control signaling, second control signaling, or both, a physical uplink shared channel (PUSCH) configuration for performing the two-step random access procedure, the PUSCH configuration comprising a plurality of PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the plurality of PUSCH occasions comprising a set of common PUSCH occasions within one or more additional half-duplex uplink slots;
    receive a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion of the set of full-duplex RACH occasions;
    receive a payload of the first message of the two-step random access procedure to the network entity via a common PUSCH occasion of the set of common PUSCH occasions that maps to the common RACH occasion or the full-duplex RACH occasion that was used to receive the preamble; and
    transmit, to the UE, a second message of the two-step random access procedure based at least in part on receiving the preamble and the payload of the first message of the two-step random access procedure.
  44. The network entity of claim 43, wherein the first half-duplex uplink slot including the set of common RACH occasions comprises a physical RACH (PRACH) slot, wherein the PUSCH configuration comprises a first time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common PUSCH occasions, and a second time domain offset between the PRACH slot and the one or more additional half-duplex uplink slots including the set of common PUSCH occasions.
  45. The network entity of claim 43, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:
    transmit, via the first control signaling, the second control signaling, or both, a first mapping configuration between the plurality of preambles of the set of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the plurality of preambles of the set of full-duplex RACH occasions and the set of common PUSCH occasions.
  46. The network entity of claim 43, wherein each common PUSCH occasion from the set of common PUSCH occasions is mapped to at least one common RACH occasion from the set of common RACH occasions and at least one full-duplex RACH occasion from the set of full-duplex RACH occasions.
  47. The network entity of claim 43, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:
    identify one of the common RACH occasion or the full-duplex RACH occasion based at least in part on a relative timing of the common RACH occasion and the full-duplex RACH occasion in a time domain, one or more measured or predicted signal quality metrics associated with slots that include the common RACH occasion and the full-duplex RACH occasion, a PUSCH transmission power relative to a transmission power threshold associated with the one or more full-duplex slots, a radio resource control configuration, a type of UE, or any combination thereof, wherein the preamble of the first message of the two-step random access procedure is received via the identified one of the common RACH occasion or the full-duplex RACH occasion.
  48. The network entity of claim 43, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:
    determine a validity of each full-duplex RACH occasion within the set of full-duplex RACH occasions based at least in part on a type of slot corresponding to each of the set of full-duplex RACH occasions, the type of slot comprising a full-duplex slot type or a half-duplex slot type.
  49. The network entity of claim 48, wherein, to determine the validity of each full-duplex RACH occasion, the one or more processors are individually or collectively operable to execute the code to cause the network entity to:
    determine that each full-duplex RACH occasion of the set of full-duplex RACH occasions is valid regardless of the type of slot in accordance with a first validity rule; or
    determine that a subset of RACH occasions from the set of full-duplex RACH occasions are invalid based at least in part on the subset of RACH occasions being positioned within non-full-duplex slots and in accordance with a second validity rule.
  50. The network entity of claim 43,
    wherein the set of full-duplex RACH occasions comprise a first subset of full-duplex RACH occasions within the one or more full-duplex slots, and a second subset of full-duplex RACH occasions that overlap in a time domain with the set of common RACH occasions within the first half-duplex uplink slot, and
    wherein the set of common RACH occasions and the set of full-duplex RACH occasions are associated with a plurality of preambles such that temporally overlapping pairs of RACH occasions map to one or more common preambles of the plurality of preambles, wherein each temporally overlapping pair of RACH occasions comprise one of the second subset of full-duplex RACH occasions and one of the set of common RACH occasions.
  51. The network entity of claim 43, wherein the set of full-duplex RACH occasions comprise sub-band full-duplex (SBFD) RACH occasions, and wherein the one or more full-duplex slots comprise one or more SBFD slots.
  52. A network entity, comprising:
    one or more memories storing processor-executable code; and
    one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to:
    transmit, to a user equipment (UE) via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, wherein the random access configuration is associated with a first random access channel (RACH) configuration and a second RACH configuration, the first RACH configuration comprising a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration comprising a set of full-duplex RACH occasions within one or more full-duplex slots;
    transmit, via the first control signaling, second control signaling, or both, first physical uplink shared channel (PUSCH) configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration comprising a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration comprising a set of full-duplex PUSCH occasions within one or additional more full-duplex slots, wherein the set of common RACH occasions are mapped to the set of common PUSCH occasions, and wherein the set of full-duplex RACH occasions mapped to the set of full-duplex PUSCH occasions;
    receive a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion from the set of full-duplex RACH occasions;
    receive a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that maps to the common RACH occasion based at least in part on transmitting the preamble via the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that maps to the common RACH occasion used to receive the preamble based at least in part on receiving the preamble via the full-duplex RACH occasion; and
    transmit, to the UE, a second message of the two-step random access procedure based at least in part on receiving the preamble and the payload of the first message of the two-step random access procedure.
  53. The network entity of claim 52, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:
    transmit, via the first control signaling, the second control signaling, or both, a first mapping configuration between a plurality of preambles of the set of common RACH occasions and the set of common PUSCH occasions, and a second mapping configuration between the plurality of preambles of the set of full-duplex RACH occasions and the set of full-duplex PUSCH occasions.
  54. The network entity of claim 52, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:
    transmit, via the first control signaling, the second control signaling, or both, a third mapping configuration between a plurality of preambles of set of common RACH occasions and the set of full-duplex PUSCH occasions, a fourth mapping configuration between the plurality of preambles of the set of full-duplex RACH occasions and the set of common PUSCH occasions, or both.
  55. The network entity of claim 52, wherein the set of full-duplex RACH occasions comprise sub-band full-duplex (SBFD) RACH occasions, and wherein the set of full-duplex PUSCH occasions comprise SBFD PUSCH occasions, wherein the one or more full-duplex slots, the one or more additional full-duplex slots, or both, comprise one or more SBFD slots.
  56. The network entity of claim 52, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:
    transmit, via the first control signaling, the second control signaling, or both, an indication that the first RACH configuration, second RACH configuration, the first PUSCH configuration, the second PUSCH configuration, or any combination thereof, are usable for performing random access procedures associated with system information requests, physical downlink control channel ordering, beam failure recovery, mobility, or any combination thereof.
  57. The network entity of claim 52, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:
    transmit, via the first control signaling, the second control signaling, or both, an indication that the second RACH configuration, the second PUSCH configuration, or both, comprise UE-specific configurations or cell-specific configurations;
    receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, wherein the random access configuration is associated with a random access channel (RACH) configuration comprising a plurality of common RACH occasions within a first half-duplex uplink slot;
    receiving, via the first control signaling, second control signaling, or both, a first physical uplink shared channel (PUSCH) configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration comprising a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration comprising a set of full-duplex PUSCH occasions within one or more full-duplex slots;
    transmitting a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the plurality of common RACH occasions;
    transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that is associated with the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that is associated with the common RACH occasion used to transmit the preamble; and
    receiving, from the network entity, a second message of the two-step random access procedure based at least in part on transmitting the preamble and the payload of the first message of the two-step random access procedure.
  58. A method for wireless communications at a user equipment (UE) , comprising:
    receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, wherein the random access configuration is associated with a first random access channel (RACH) configuration and a second RACH configuration, the first RACH configuration comprising a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration comprising a set of full-duplex RACH occasions within one or more full-duplex slots;
    receiving, via the first control signaling, second control signaling, or both, a physical uplink shared channel (PUSCH) configuration for performing the two-step random access procedure, the PUSCH configuration comprising a plurality of PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the plurality of PUSCH occasions comprising a set of common PUSCH occasions within one or more additional half-duplex uplink slots;
    transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion of the set of full-duplex RACH occasions;
    transmitting a payload of the first message of the two-step random access procedure to the network entity via a common PUSCH occasion of the set of common PUSCH occasions that maps to the common RACH occasion or the full-duplex RACH occasion that was used to transmit the preamble; and
    receiving, from the network entity, a second message of the two-step random access procedure based at least in part on transmitting the preamble and the payload of the first message of the two-step random access procedure.
  59. A method for wireless communications at a user equipment (UE) , comprising:
    receiving, via first control signaling, a random access configuration for performing a two-step random access procedure with a network entity, wherein the random access configuration is associated with a first random access channel (RACH) configuration and a second RACH configuration, the first RACH configuration comprising a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration comprising a set of full-duplex RACH occasions within one or more full-duplex slots;
    receiving, via the first control signaling, second control signaling, or both, first physical uplink shared channel (PUSCH) configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration comprising a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration comprising a set of full-duplex PUSCH occasions within one or additional more full-duplex slots, wherein the set of common RACH occasions are mapped to the set of common PUSCH occasions, and wherein the set of full-duplex RACH occasions mapped to the set of full-duplex PUSCH occasions;
    transmitting a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion from the set of full-duplex RACH occasions;
    transmitting a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that maps to the common RACH occasion based at least in part on transmitting the preamble via the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that maps to the common RACH occasion used to transmit the preamble based at least in part on transmitting the preamble via the full-duplex RACH occasion; and
    receiving, from the network entity, a second message of the two-step random access procedure based at least in part on transmitting the preamble and the payload of the first message of the two-step random access procedure.
  60. A method for wireless communications at a network entity, comprising:
    transmitting, to a user equipment (UE) via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, wherein the random access configuration is associated with a random access channel (RACH) configuration comprising a plurality of common RACH occasions within a first half-duplex uplink slot;
    transmitting, via the first control signaling, second control signaling, or both, a first physical uplink shared channel (PUSCH) configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration comprising a set of common PUSCH occasions within one or more second half-duplex uplink slots, and the second PUSCH configuration comprising a set of full-duplex PUSCH occasions within one or more full-duplex slots;
    receiving a preamble of a first message of the two-step random access procedure to the network entity via a common RACH occasion of the plurality of common RACH occasions;
    receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that is associated with the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that is associated with the common RACH occasion used to receive the preamble; and
    transmitting, to the UE, a second message of the two-step random access procedure based at least in part on receiving the preamble and the payload of the first message of the two-step random access procedure.
  61. A method for wireless communications at a network entity, comprising:
    transmitting, to a user equipment (UE) via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, wherein the random access configuration is associated with a first random access channel (RACH) configuration and a second RACH configuration, the first RACH configuration comprising a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration comprising a set of full-duplex RACH occasions within one or more full-duplex slots;
    transmitting, via the first control signaling, second control signaling, or both, a physical uplink shared channel (PUSCH) configuration for performing the two-step random access procedure, the PUSCH configuration comprising a plurality of PUSCH occasions associated with the set of common RACH occasions and the set of full-duplex RACH occasions, the plurality of PUSCH occasions comprising a set of common PUSCH occasions within one or more additional half-duplex uplink slots;
    receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion of the set of full-duplex RACH occasions;
    receiving a payload of the first message of the two-step random access procedure to the network entity via a common PUSCH occasion of the set of common PUSCH occasions that maps to the common RACH occasion or the full-duplex RACH occasion that was used to receive the preamble; and
    transmitting, to the UE, a second message of the two-step random access procedure based at least in part on receiving the preamble and the payload of the first message of the two-step random access procedure.
  62. A method for wireless communications at a network entity, comprising:
    transmitting, to a user equipment (UE) via first control signaling, a random access configuration for performing a two-step random access procedure with the UE, wherein the random access configuration is associated with a first random access channel (RACH) configuration and a second RACH configuration, the first RACH configuration comprising a set of common RACH occasions within a first half-duplex uplink slot, and the second RACH configuration comprising a set of full-duplex RACH occasions within one or more full-duplex slots;
    transmitting, via the first control signaling, second control signaling, or both, first physical uplink shared channel (PUSCH) configuration and a second PUSCH configuration for performing the two-step random access procedure, the first PUSCH configuration comprising a set of common PUSCH occasions within one or more additional half-duplex uplink slots, and the second PUSCH configuration comprising a set of full-duplex PUSCH occasions within one or additional more full-duplex slots, wherein the set of common RACH occasions are mapped to the set of common PUSCH occasions, and wherein the set of full-duplex RACH occasions mapped to the set of full-duplex PUSCH occasions;
    receiving a preamble of a first message of the two-step random access procedure to the network entity either via a common RACH occasion from the set of common RACH occasions, or via a full-duplex RACH occasion from the set of full-duplex RACH occasions;
    receiving a payload of the first message of the two-step random access procedure to the network entity either via a common PUSCH occasion from the set of common PUSCH occasions that maps to the common RACH occasion based at least in part on transmitting the preamble via the common RACH occasion, or via a full-duplex PUSCH occasion from the set of full-duplex PUSCH occasions that maps to the common RACH occasion used to receive the preamble based at least in part on receiving the preamble via the full-duplex RACH occasion; and
    transmitting, to the UE, a second message of the two-step random access procedure based at least in part on receiving the preamble and the payload of the first message of the two-step random access procedure.
PCT/CN2024/077262 2024-02-16 2024-02-16 Techniques for two-step random access procedures using dedicated sub-band full duplex resources Pending WO2025171575A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/077262 WO2025171575A1 (en) 2024-02-16 2024-02-16 Techniques for two-step random access procedures using dedicated sub-band full duplex resources

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/077262 WO2025171575A1 (en) 2024-02-16 2024-02-16 Techniques for two-step random access procedures using dedicated sub-band full duplex resources

Publications (1)

Publication Number Publication Date
WO2025171575A1 true WO2025171575A1 (en) 2025-08-21

Family

ID=96772449

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/077262 Pending WO2025171575A1 (en) 2024-02-16 2024-02-16 Techniques for two-step random access procedures using dedicated sub-band full duplex resources

Country Status (1)

Country Link
WO (1) WO2025171575A1 (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210084688A1 (en) * 2019-09-18 2021-03-18 Qualcomm Incorporated Techniques for performing random access in full duplex wireless communications
US20210100038A1 (en) * 2019-09-30 2021-04-01 Qualcomm Incorporated Apparatus and methods for synchronization signal and random access communications in full duplex
US20210243812A1 (en) * 2020-02-03 2021-08-05 Samsung Electronics Co., Ltd. Method and apparatus for performing communication in wireless communication system
WO2023014089A1 (en) * 2021-08-04 2023-02-09 Samsung Electronics Co., Ltd. Method and apparatus for performing random access based on full-duplex system in wireless communication system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210084688A1 (en) * 2019-09-18 2021-03-18 Qualcomm Incorporated Techniques for performing random access in full duplex wireless communications
US20210100038A1 (en) * 2019-09-30 2021-04-01 Qualcomm Incorporated Apparatus and methods for synchronization signal and random access communications in full duplex
US20210243812A1 (en) * 2020-02-03 2021-08-05 Samsung Electronics Co., Ltd. Method and apparatus for performing communication in wireless communication system
WO2023014089A1 (en) * 2021-08-04 2023-02-09 Samsung Electronics Co., Ltd. Method and apparatus for performing random access based on full-duplex system in wireless communication system

Similar Documents

Publication Publication Date Title
US12452907B2 (en) Physical random access channel for uplink-subband in subband full duplex
WO2023184474A1 (en) Techniques for handling overlapping uplink transmissions associated with different timing advance groups
US12381689B2 (en) Interlaced feedback for sidelink communications via unlicensed channels
US12155607B2 (en) Techniques for cyclic frequency hopping in sub-band full duplex slots
US12213148B2 (en) Grant-based feedback bit determination for feedback occasions
US12341727B2 (en) Flexible channel structure for paired radio frequency spectrum bands
US12464388B2 (en) Beam failure detection reference signal set update
US20240306139A1 (en) Transmission of deferred feedback via uplink shared channel
EP4162745B1 (en) Techniques for control reduction in sidelink network
EP4552274A1 (en) Frequency division multiplexing for uplink shared channel transmissions with interlaced resource block allocation
WO2023205580A1 (en) Techniques for sending a collision indication via a physical sidelink feedback channel
WO2022216523A1 (en) Grant-based feedback bit determination for feedback occasions
WO2025171575A1 (en) Techniques for two-step random access procedures using dedicated sub-band full duplex resources
WO2025081399A1 (en) Techniques for skipping one or more transmission occasions using uplink control information
US12356466B2 (en) Resource mapping for random access repetitions using a same spatial filter
WO2025065710A1 (en) Timing advance timer expiration handling in multi transmission and reception point operation with multiple timing advance groups
WO2025129549A1 (en) Techniques for communicating assistance information in physical broadcast channel
WO2024239306A1 (en) Transmit power prioritization
WO2025152102A1 (en) Aggregated capability signaling for carrier aggregation and dual connectivity modes
WO2025209014A1 (en) Physical downlink control channel (pdcch) -ordered physical random access channel (prach) for an uplink-only transmission and reception point (trp)
WO2025118233A1 (en) Multiple timing advance values for uplink dense deployments
WO2025129439A1 (en) Techniques for quasi co-location multiplexing and prioritization
WO2025035244A1 (en) Sidelink channel occupancy time maintenance
WO2025184891A1 (en) Control signal design for uplink dense deployment
US20250261236A1 (en) Selecting random access channel occasions for subband full-duplex

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: 24924351

Country of ref document: EP

Kind code of ref document: A1