WO2024031663A1 - Liaison de ressources de fréquence d'accès aléatoire - Google Patents

Liaison de ressources de fréquence d'accès aléatoire Download PDF

Info

Publication number
WO2024031663A1
WO2024031663A1 PCT/CN2022/112198 CN2022112198W WO2024031663A1 WO 2024031663 A1 WO2024031663 A1 WO 2024031663A1 CN 2022112198 W CN2022112198 W CN 2022112198W WO 2024031663 A1 WO2024031663 A1 WO 2024031663A1
Authority
WO
WIPO (PCT)
Prior art keywords
sub
band
random access
message
bandwidth part
Prior art date
Application number
PCT/CN2022/112198
Other languages
English (en)
Inventor
Hung Dinh LY
Yongjun Kwak
Kexin XIAO
Original Assignee
Qualcomm Incorporated
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 Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2022/112198 priority Critical patent/WO2024031663A1/fr
Publication of WO2024031663A1 publication Critical patent/WO2024031663A1/fr

Links

Images

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/0866—Non-scheduled access, e.g. ALOHA using a dedicated channel for access
    • H04W74/0891—Non-scheduled access, e.g. ALOHA using a dedicated channel for access for synchronized access
    • 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

Definitions

  • the following relates to wireless communications, including random access frequency resource linkage.
  • 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
  • a reduced capability wireless device may perform a random access procedure.
  • such approaches may be improved.
  • a user equipment may receive a synchronization signal block message that indicates an initial uplink bandwidth part and a plurality of random access occasions, where at least a subset of the plurality of random access occasions are frequency division multiplexed within the initial uplink bandwidth part.
  • the UE may receive, based on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part.
  • the UE may transmit a first random access message in a first random access occasion of the plurality of random access occasions.
  • the UE may monitor for a first control channel message in a first sub-band of the initial downlink bandwidth part, where an offset of the first sub-band within the initial downlink bandwidth part is based on the first random access occasion.
  • a method for wireless communication at a user equipment may include receiving a synchronization signal block message that indicates an initial uplink bandwidth part and a set of multiple random access occasions, where at least a subset of the set of multiple random access occasions are frequency division multiplexed within the initial uplink bandwidth part, receiving, based on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part, transmitting a first random access message in a first random access occasion of the set of multiple random access occasions, and monitoring for a first control channel message in a first sub-band of the initial downlink bandwidth part, where an offset of the first sub-band within the initial downlink bandwidth part is based on the first random access occasion.
  • the apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory.
  • the instructions may be executable by the processor to cause the apparatus to receive a synchronization signal block message that indicates an initial uplink bandwidth part and a set of multiple random access occasions, where at least a subset of the set of multiple random access occasions are frequency division multiplexed within the initial uplink bandwidth part, receive, based on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part, transmit a first random access message in a first random access occasion of the set of multiple random access occasions, and monitor for a first control channel message in a first sub-band of the initial downlink bandwidth part, where an offset of the first sub-band within the initial downlink bandwidth part is based on the first random access occasion.
  • the apparatus may include means for receiving a synchronization signal block message that indicates an initial uplink bandwidth part and a set of multiple random access occasions, where at least a subset of the set of multiple random access occasions are frequency division multiplexed within the initial uplink bandwidth part, means for receiving, based on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part, means for transmitting a first random access message in a first random access occasion of the set of multiple random access occasions, and means for monitoring for a first control channel message in a first sub-band of the initial downlink bandwidth part, where an offset of the first sub-band within the initial downlink bandwidth part is based on the first random access occasion.
  • a non-transitory computer-readable medium storing code for wireless communication at a UE is described.
  • the code may include instructions executable by a processor to receive a synchronization signal block message that indicates an initial uplink bandwidth part and a set of multiple random access occasions, where at least a subset of the set of multiple random access occasions are frequency division multiplexed within the initial uplink bandwidth part, receive, based on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part, transmit a first random access message in a first random access occasion of the set of multiple random access occasions, and monitor for a first control channel message in a first sub-band of the initial downlink bandwidth part, where an offset of the first sub-band within the initial downlink bandwidth part is based on the first random access occasion.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining the offset of the first sub-band relative to a first physical resource block of the initial downlink bandwidth part based on a subcarrier spacing of the initial downlink bandwidth part.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving system information indicating the offset of the first sub-band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining the offset of the first sub-band based on a maximum bandwidth capability of the UE.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving system information indicating a frequency domain resource allocation offset of the initial downlink bandwidth part that may be relative to a first physical resource block of the initial downlink bandwidth part.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for monitoring for the first control channel message in the first sub-band based on a bandwidth of the first sub-band fully overlapping with the first random access occasion.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for monitoring for the first control channel message in the first sub-band based on a mapping between the first random access occasion and the first sub-band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for monitoring for a first shared channel message in the first sub-band based on monitoring for the first control channel message in the first sub-band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for monitoring for a second control channel message, a second shared channel message, or both in the first sub-band based on monitoring for the first control channel message in the first sub-band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving the first control channel message in the first sub-band, the first control channel message including an indication of a second sub-band of the initial downlink bandwidth part.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for monitoring for a first shared channel message in the second sub-band based on the indication of the second sub-band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for monitoring for a second control channel message, a second shared channel message, or both in the second sub-band based on monitoring for the first shared channel message in the second sub-band or the indication of the second sub-band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for monitoring for a second shared channel message based on monitoring for a second control channel message in the first sub-band or the second sub-band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for monitoring for a second shared channel message in a sub-band in which the UE monitored for a control channel message associated with an uplink retransmission.
  • the second sub-band may be a same sub-band as the first sub-band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining an uplink sub-band for one or more uplink transmissions in the initial uplink bandwidth part based on a downlink sub-band used for one or more downlink transmission in the initial downlink bandwidth part.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving an indication of a mapping between the uplink sub-band and the downlink sub-band, where determining the uplink sub-band may be based on the indication of the mapping.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining a mapping between the uplink sub-band and the downlink sub-band based on a frequency domain overlap between the uplink sub-band and the downlink sub-band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining the uplink sub-band may be further based on the first random access occasion.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting a preamble of the first random access message in a first sub-band of the initial uplink bandwidth part and transmitting a payload of the first random access message in the first sub-band of the initial uplink bandwidth part based on transmitting the preamble in the first sub-band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting a preamble of the first random access message in a first sub-band of the initial uplink bandwidth part and transmitting a payload of the first random access message in a second sub-band of the initial uplink bandwidth part based on a mapping between the payload and the second sub-band.
  • a method for wireless communication at a network entity may include transmitting a synchronization signal block message that indicates an initial uplink bandwidth part and a set of multiple random access occasions, where at least a subset of the set of multiple random access occasions are frequency division multiplexed within the initial uplink bandwidth part, transmitting, based on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part, receiving a first random access message in a first random access occasion of the set of multiple random access occasions, and transmitting a first control channel message in a first sub-band of the initial downlink bandwidth part, where an offset of the first sub-band within the initial downlink bandwidth part is based on the first random access occasion.
  • the apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory.
  • the instructions may be executable by the processor to cause the apparatus to transmit a synchronization signal block message that indicates an initial uplink bandwidth part and a set of multiple random access occasions, where at least a subset of the set of multiple random access occasions are frequency division multiplexed within the initial uplink bandwidth part, transmit, based on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part, receive a first random access message in a first random access occasion of the set of multiple random access occasions, and transmit a first control channel message in a first sub-band of the initial downlink bandwidth part, where an offset of the first sub-band within the initial downlink bandwidth part is based on the first random access occasion.
  • the apparatus may include means for transmitting a synchronization signal block message that indicates an initial uplink bandwidth part and a set of multiple random access occasions, where at least a subset of the set of multiple random access occasions are frequency division multiplexed within the initial uplink bandwidth part, means for transmitting, based on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part, means for receiving a first random access message in a first random access occasion of the set of multiple random access occasions, and means for transmitting a first control channel message in a first sub-band of the initial downlink bandwidth part, where an offset of the first sub-band within the initial downlink bandwidth part is based on the first random access occasion.
  • a non-transitory computer-readable medium storing code for wireless communication at a network entity is described.
  • the code may include instructions executable by a processor to transmit a synchronization signal block message that indicates an initial uplink bandwidth part and a set of multiple random access occasions, where at least a subset of the set of multiple random access occasions are frequency division multiplexed within the initial uplink bandwidth part, transmit, based on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part, receive a first random access message in a first random access occasion of the set of multiple random access occasions, and transmit a first control channel message in a first sub-band of the initial downlink bandwidth part, where an offset of the first sub-band within the initial downlink bandwidth part is based on the first random access occasion.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining the offset of the first sub-band relative to a first physical resource block of the initial downlink bandwidth part based on a subcarrier spacing of the initial downlink bandwidth part.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting system information indicating the offset of the first sub-band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining the offset of the first sub-band based on a maximum bandwidth capability of a UE.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting system information indicating a frequency domain resource allocation offset of the initial downlink bandwidth part that may be relative to a first physical resource block of the initial downlink bandwidth part.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting the first control channel message in the first sub-band based on a bandwidth of the first sub-band fully overlapping with the first random access occasion.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting the first control channel message in the first sub-band based on a mapping between the first random access occasion and the first sub-band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting a first shared channel message in the first sub-band based on transmitting the first control channel message in the first sub-band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting a second control channel message, a second shared channel message, or both in the first sub-band based on transmitting the first control channel message in the first sub-band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting the first control channel message in the first sub-band, the first control channel message including an indication of a second sub-band of the initial downlink bandwidth part.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting a first shared channel message in the second sub-band based on the indication of the second sub-band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting a second control channel message, a second shared channel message, or both in the second sub-band based on transmitting the first shared channel message in the second sub-band or the indication of the second sub-band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting a second shared channel message based on transmitting a second control channel message in the first sub-band or the second sub-band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting a second shared channel message in a sub-band in which the network entity transmitted a control channel message associated with an uplink retransmission.
  • the second sub-band may be a same sub-band as the first sub-band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining an uplink sub-band for one or more uplink transmissions in the initial uplink bandwidth part based on a downlink sub-band used for one or more downlink transmission in the initial downlink bandwidth part.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting an indication of a mapping between the uplink sub-band and the downlink sub-band, where determining the uplink sub-band may be based on the indication of the mapping.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining a mapping between the uplink sub-band and the downlink sub-band based on a frequency domain overlap between the uplink sub-band and the downlink sub-band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining the uplink sub-band may be further based on the first random access occasion.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a preamble of the first random access message in a first sub-band of the initial uplink bandwidth part and receiving a payload of the first random access message in the first sub-band of the initial uplink bandwidth part based on receiving the preamble in the first sub-band.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a preamble of the first random access message in a first sub-band of the initial uplink bandwidth part and receiving a payload of the first random access message in a second sub-band of the initial uplink bandwidth part based on a mapping between the payload and the second sub-band.
  • FIG. 1 illustrates an example of a wireless communications system that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • FIG. 2 illustrates an example of a wireless communications system that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • FIG. 3 illustrates an example of a resource scheme that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • FIG. 4 illustrates an example of a resource scheme that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • FIG. 5 illustrates an example of a resource scheme that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • FIG. 6 illustrates an example of a resource scheme that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • FIG. 7 illustrates an example of a process flow that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • FIGs. 8 and 9 show block diagrams of devices that support random access frequency resource linkage in accordance with one or more examples as described herein.
  • FIG. 10 shows a block diagram of a communications manager that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • FIG. 11 shows a diagram of a system including a device that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • FIGs. 12 and 13 show block diagrams of devices that support random access frequency resource linkage in accordance with one or more examples as described herein.
  • FIG. 14 shows a block diagram of a communications manager that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • FIG. 15 shows a diagram of a system including a device that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • FIGs. 16 and 17 show flowcharts illustrating methods that support random access frequency resource linkage in accordance with one or more examples as described herein.
  • Some wireless communications systems may support user equipment (UEs) with different capabilities.
  • UEs user equipment
  • a wireless communications system may support higher capability UEs with low latency and high data throughput, such as UEs that support ultra-reliable low latency communications (URLLC) .
  • the wireless communications system may also support lower capability UEs, or reduced capability UEs, with reduced peak data throughput, latency, reliability, bandwidth, or other characteristics or capabilities.
  • some devices may operate within a limited radio frequency (RF) bandwidth.
  • RF radio frequency
  • frequency domain resource restrictions for various random access procedure messages may be introduced.
  • frequency resources for downlink messages of a random access procedure e.g., Msg2/Msg4 physical downlink control channel (PDCCH) /physical downlink shared channel (PDSCH)
  • PDCCH physical downlink control channel
  • PDSCH physical downlink shared channel
  • Sub-bands may be determined through explicit means (e.g., signaling) or implicit means (e.g., based on a subcarrier spacing (SCS) , a bandwidth capability of a UE, or other factors) . Further, determination of sub-bands for other messages or operations may be explicitly signaled (e.g., in Msg2/Msg4 PDCCH/PDSCH messaging) or implicitly determined (e.g., by using the same sub-band that was used for other messaging) . Such use of sub-bands and explicit or implicit linkage of frequency resources may be applied to both 2-step and 4-step random access procedures as well as other random access procedures.
  • SCS subcarrier spacing
  • aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are then described in the context of a wireless communications system, resources schemes, and a process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to random access frequency resource linkage.
  • FIG. 1 illustrates an example of a wireless communications system 100 that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • the wireless communications system 100 may include one or more 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 one or more communication links 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 one or more communication links 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, such as other 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 the core network 130, or with one another, or both.
  • network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., in accordance with an S1, N2, N3, or other interface protocol) .
  • network entities 105 may communicate with one another via a backhaul communication link 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 a core network 130) .
  • 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 links 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) , 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 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 a 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 a giga-NodeB (either of which may be
  • 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 a single network entity 105 (e.g., 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 two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) .
  • IAB integrated access backhaul
  • O-RAN open RAN
  • vRAN virtualized RAN
  • C-RAN cloud RAN
  • a network entity 105 may include one or more of a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) 180 system, or any combination thereof.
  • 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 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, and 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, and 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) ) .
  • the CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.
  • L1 e.g., physical (PHY) layer
  • L2 e.g., radio link control (RLC) layer, medium access control (MAC) layer
  • 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 more RUs 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 one or more DUs 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u) , and a DU 165 may be connected to one or more RUs 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 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 one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other.
  • One or more IAB nodes 104 may be referred to as a donor entity or an IAB donor.
  • One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140) .
  • the one or more donor network entities 105 may be in communication with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120) .
  • IAB nodes 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by DUs 165 of a coupled IAB donor.
  • IAB-MT IAB mobile termination
  • An IAB-MT may include 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 an IAB node 104 used for access via the DU 165 of the IAB node 104 (e.g., referred to as virtual IAB-MT (vIAB-MT) ) .
  • the IAB nodes 104 may include DUs 165 that support communication links with additional entities (e.g., IAB nodes 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., one or more IAB nodes 104 or components of IAB nodes 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 nodes 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 core network 130.
  • the IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170) , in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link) .
  • IAB donor and IAB nodes 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 via an interface, which may be an example of a portion of backhaul link, and may communicate with other CUs 160 (e.g., a CU 160 associated with an alternative IAB donor) via an Xn-C interface, which may be an example of a portion of a backhaul link.
  • An IAB node 104 may refer to a RAN node that provides 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 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with the IAB node 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 one or more other IAB nodes 104) .
  • an IAB node 104 may also be referred to as a parent node or a child node to other IAB nodes 104, depending on the relay chain or configuration of the AN. Therefore, the IAB-MT entity of IAB nodes 104 may provide a Uu interface for a child IAB node 104 to receive signaling from a parent IAB node 104, and the DU interface (e.g., DUs 165) may provide a Uu interface for a parent IAB node 104 to signal to a child IAB node 104 or UE 115.
  • the DU interface e.g., DUs 165
  • IAB node 104 may be referred to as a parent node that supports communications for a child IAB node, or referred to as a child IAB node associated with an IAB donor, or both.
  • the IAB donor may include a CU 160 with a wired or wireless connection (e.g., a backhaul communication link 120) to the core network 130 and may act as parent node to IAB nodes 104.
  • the DU 165 of IAB donor may relay transmissions to UEs 115 through IAB nodes 104, or may directly signal transmissions to a UE 115, or both.
  • the CU 160 of IAB donor may signal communication link establishment via an F1 interface to IAB nodes 104, and the IAB nodes 104 may schedule transmissions (e.g., transmissions to the UEs 115 relayed from the IAB donor) through the DUs 165. That is, data may be relayed to and from IAB nodes 104 via signaling via an NR Uu interface to MT of the IAB node 104. Communications with IAB node 104 may be scheduled by a DU 165 of IAB donor and communications with IAB node 104 may be scheduled by DU 165 of IAB node 104.
  • one or more components of the disaggregated RAN architecture may be configured to support random access frequency resource linkage 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., IAB nodes 104, DUs 165, CUs 160, RUs 170, RIC 175, SMO 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, or vehicles, 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 other UEs 115 that may sometimes act 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 other UEs 115 that may sometimes act 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 one or more communication links 125 (e.g., an access link) using resources associated with one or more carriers.
  • the term “carrier” may refer to a set of RF spectrum resources having a defined physical layer structure for supporting the communication links 125.
  • a carrier used for a communication link 125 may include a portion of a RF spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR) .
  • BWP bandwidth part
  • Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information) , 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.
  • 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 105) .
  • a network entity 105 e.g., a base station 140, a CU 160, a DU 165, a RU 170
  • a carrier may also 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 radio access technology) .
  • the communication links 125 shown in 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.
  • the carrier bandwidth may be one of a set of bandwidths for carriers of a particular radio access technology (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 multiple UEs 115 and UE-specific search space sets for sending control information to a specific UE 115.
  • 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) , or others) .
  • 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.
  • 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 lower-powered network entity 105 (e.g., a lower-powered base station 140) , as compared with 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 multiple 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 110.
  • different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105.
  • the overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105.
  • the wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.
  • the wireless communications system 100 may support synchronous or asynchronous operation.
  • network entities 105 e.g., base stations 140
  • network entities 105 may have different frame timings, and transmissions from different network entities 105 may, in some examples, not be aligned in time.
  • the techniques described herein may be used for either synchronous or asynchronous operations.
  • Some UEs 115 may be low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication) .
  • M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity 105 (e.g., a base station 140) without human intervention.
  • M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program.
  • Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.
  • Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently) .
  • half-duplex communications may be performed at a reduced peak rate.
  • Other power conservation techniques for the UEs 115 include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., according to narrowband communications) , or a combination of these techniques.
  • some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.
  • a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.
  • 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 115 via a device-to-device (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 each of the other 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 100 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 also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known as the centimeter band, or using an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) , also known as the millimeter band.
  • SHF super high frequency
  • EHF extremely high frequency
  • the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the network entities 105 (e.g., base stations 140, RUs 170) , and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas.
  • mmW millimeter wave
  • such techniques may facilitate using antenna arrays within a device.
  • EHF transmissions may be subject to even greater attenuation and shorter range than SHF or UHF transmissions.
  • the techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.
  • 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) radio access technology, 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
  • Some signals may be transmitted by transmitting device (e.g., a transmitting network entity 105, a transmitting UE 115) along a single beam direction (e.g., a direction associated with the receiving device, such as a receiving network entity 105 or a receiving UE 115) .
  • a single beam direction e.g., a direction associated with the receiving device, such as a receiving network entity 105 or a receiving UE 115
  • 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.
  • 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.
  • 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 receiving device (e.g., a network entity 105) , such as synchronization signals, reference signals, beam selection signals, or other control signals.
  • a receiving device e.g., a network entity 105
  • signals such as synchronization signals, reference signals, beam selection signals, or other control signals.
  • 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., a communication link 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 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 UE 115 (which may be a reduced capability UE) may operate with one or more frequency domain resource restrictions for random access procedure messages. For example, the UE 115 may engage in a random access procedure in which one or more messages (e.g., UL, DL, or both) may be transmitted over frequency resources that may be limited to one or more sub-bands of initial BWPs (e.g., UL, DL, or both) .
  • the UE 115, the network entity 105, or both may determine the sub-bands to be used through explicit means (e.g., signaling) or implicit means (e.g., based on a subcarrier spacing (SCS) , a bandwidth capability of the UE 115, or other factors) .
  • explicit means e.g., signaling
  • implicit means e.g., based on a subcarrier spacing (SCS) , a bandwidth capability of the UE 115, or other factors
  • the network entity 105 may explicitly signal one or more sub-bands to be used for other messaging (e.g., in Msg2/Msg4 PDCCH/PDSCH messaging) or the UE 115 and the network entity 105 may implicitly determine such sub-bands (e.g., by using the same sub-band that was used for other messaging) .
  • FIG. 2 illustrates an example of a wireless communications system 200 that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • the wireless communications system 200 may involve the network entity 105-a that may be an example of one or more network entities discussed in relation to other figures.
  • the wireless communications system 200 may involve the UE 115-b that may be an example of UEs discussed in relation to other figures.
  • the UE 115 a may be located in a geographic coverage area 110-a that may be associated with the network entity 105-a.
  • the network entity 105-a and UE 115-a may communicate via one or more downlink communication links 205-a and one or more uplink communication links 205-b.
  • the UE 115-a and the network entity 105-a may engage in a random access procedure.
  • the random access procedure may include one or more uplink transmissions and one or more downlink transmissions. These transmissions may be associated with control channels, shared channels, random access channels, other channels, or any combination thereof.
  • the UE 115-a and the network entity 105-a may engage in a four step random access procedure. In other examples, the UE 115-a and the network entity 105-a may engage in a two step random access procedure. Regardless of the particular details of the random access procedure, the techniques described herein for frequency resource determination or selection may be applied to the four step random access procedure, the two step random access procedure, other random access procedures, or any combination thereof.
  • an initial UL BWP may be configured, selected, defined, indicated, or determined for the UE 115-a (e.g., in a system information block (SIB) such as SIB1 or other signaling) .
  • SIB system information block
  • One or more random access channel (RACH) occasions (RO) , uplink message allocation (e.g., Msg3 PUSCH resource allocation) information, or both may be associated with frequency resources included within frequency resources covered by or assigned to the initial UL BWP.
  • the UE 115-a may receive an indication of a first RO frequency location, which may include an indication of an offset from a first physical resource block (PRB) (e.g., PRB0) of the initial UL BWP.
  • PRB physical resource block
  • An example parameter for such an offset may be, for example, msg1-FrequencyStart.
  • PUSCH resource mapping in frequency domain may begin or be determined relative to the first PRB (e.g., PRB0) of the initial uplink BWP.
  • a maximum size of the initial UL BWP for enhanced reduced capability (eRedcap) UEs may be 5 MHz, which may be smaller than reduced capability (Redcap) or other UE bandwidths (e.g., 20 MHz or higher) .
  • an initial UL BWP for an eRedcap UE may contain one or two ROs (e.g., depending on the SCS of a physical random access channel (PRACH) ) .
  • PRACH physical random access channel
  • an initial DL BWP by be determined or selected based on a location, a size, or both of a CORESET (e.g., CORESET 0) , which may be configured in a master information block (MIB) .
  • a maximum size of an initial DL BWP for eRedcap UEs may be a reduced frequency range compared to other UEs (e.g., 5 MHz instead of 20 MHz) .
  • the techniques described herein may include frequency domain resource restriction for downlink control channel messaging, downlink shared channel messaging, or both. Such techniques may facilitate concurrent operation of eRedcap UEs with Redcap UEs and other UEs in the same initial BWPs. Additionally, or alternatively, the techniques described herein may include a linkage or mapping between frequency resources (e.g., UL, DL, or both) to determine or select valid resources for transmission, reception, or both of UL messages, DL messages, or both during a random access procedure.
  • frequency resources e.g., UL, DL, or both
  • the UE 115-a may receive SSB 220 (e.g., from the network entity 105-a) .
  • the SSB 220 may include an indication of an initial UL BWP and a plurality of ROs that the UE 115-a may use for transmissions during a random access procedure.
  • the ROs may be multiplexed (e.g., in the frequency domain, within the initial UL BWP, or both) .
  • the UE 115-a may further receive the MIB 225 which may indicate an initial DL BWP to be used during the random access procedure.
  • the UE 115-a may (e.g., as part of the random access procedure) , transmit the first random access message 230 in a first RO of the ROs indicated in the SSB 220.
  • the first random access message 230 may be, for example, a Msg1 of a four step random access procedure or may be a MsgA of a two step random access procedure.
  • the UE 115-a may monitor for the first control channel message 235 in a sub-band of the initial DL BWP (e.g., instead of monitoring in the entire bandwidth of the initial DL BWP as may be done in other approaches) .
  • the sub-band may be associated with an offset (e.g., to locate or define a bandwidth of the sub-band relative to a reference point, such as a first PRB of the initial DL BWP) .
  • the offset may be based on the RO that was selected for transmitting the first random access message 230. For example, a frequency range of the sub-band may overlap with a frequency range of the RO.
  • the UE 115-a (which may be an example of an eRedcap UE) may communicate using frequency-restricted resources while still operating within a same initial BWP (e.g., UL, DL, or both) as other UEs that may not communicate using frequency-restricted resources.
  • a same initial BWP e.g., UL, DL, or both
  • FIG. 3 illustrates an example of a resource scheme 300 that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • the resource scheme 300 may include an initial BWP 320 that may be divided into sub-band 0 325, sub-band 1 330, sub-band 2 335, and sub-band 3 340.
  • the resource scheme 300 may further include offsets corresponding to the sub-bands, including frequency domain resource allocation (FDRA) offset 0 345, FDRA offset 1 350, FDRA offset 2 355, and FDRA offset 3 360.
  • FDRA frequency domain resource allocation
  • initial BWPs used for random access procedures may be divided or partitioned into sub-bands (e.g., so that eRedcap UEs may employ the use of reduced bandwidths for random access procedures alongside other UEs that may employ other bandwidths for random access procedures) .
  • starting points or reference points of the sub-bands 325, 330, 335, and 340 may be determined, defined, or selected with respect to a first PRB (e.g., PRB0) of the initial BWP. In some examples, such starting points may be based on an SCS of the initial BWP.
  • the FDRA offsets 345, 350, 355, and 360 may be indicated in system information (SI) or may be determined based on a maximum UE BW.
  • SI system information
  • an offset k may be given by k*N rb where N rb may be the quantity of resource blocks (RBs) contained in the maximum UE BW.
  • a sub-band may be valid if it contains a predefined number of RBs (e.g., N rb ) .
  • the start of FDRA for UL transmission (e.g., in case of an initial UL BWP) or for DL reception (e.g., in the case of an initial DL BWP) may be a first RB in a valid sub-band.
  • a sub-band size for an initial UL BWP and a sub-band size for an initial DL BWP can be different. In some examples, such a sub-band size may be 5 MHz.
  • FIG. 4 illustrates an example of a resource scheme 400 that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • the resource scheme 400 may be associated with control channel message transmission or control channel message reception (e.g., PDCCH transmission or PDCCH reception) .
  • the resource scheme 400 may include an initial UL BWP 420 and an initial DL BWP 425.
  • RO 1 430, RO 2 435, RO 3 440, and RO 4 445 may be associated with frequency domain resources that fall within frequency domain resources associated with the initial UL BWP 420.
  • the initial DL BWP 425 may include one or more sub-bands, such as sub-band 0 450, sub-band 1 455, sub-band 2 460, and sub-band 3 465.
  • the UE may determines or select a sub-band for monitoring for control channel signaling (e.g., Msg2 PDCCH signaling in a four step random access process) .
  • the sub-band that the UE selects may fully overlap (e.g., as depicted by frequency overlap 475) in the frequency domain with the RO that UE has chosen for a first random access transmission (e.g., a PRACH transmission) .
  • a first random access transmission e.g., a PRACH transmission
  • the UE may also monitor sub-band 2 460 for control channel signaling, such as the PDCCH message 470.
  • TDD time-domain duplexed
  • a network entity may can configure or indicate to the UE a mapping between an RO and sub-band.
  • the network entity may configure the mapping 480 that may map the RO 1 430 and the sub-band 0 450.
  • the UE may monitor (e.g., based on the mapping 480) sub-band 0 450 to receive the PDCCH message 470.
  • Such a mapping may be a 1-to-1 mapping (e.g., one RO to one sub-band) , a 1-to-many mapping (e.g., one RO to multiple sub-bands) , a many-to-1 mapping (e.g., multiple ROs to a single sub-band) , or a many-to-many mapping (e.g., multiple ROs to multiple sub-bands) .
  • the UE may determine or select a sub-band for monitoring (e.g., Msg2 PDCCH monitoring) based on the configured mapping and the RO used for PRACH transmission.
  • a sub-band for monitoring e.g., Msg2 PDCCH monitoring
  • such approaches may be employed in scenarios involving TDD carriers or FDD carriers (e.g., where the initial UL BWP 520 and the initial DL BWP 525 are in different carriers) .
  • FIG. 5 illustrates an example of a resource scheme 500 that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • the resource scheme 500 may be associated with shared channel message transmission or shared channel message reception (e.g., PDSCH transmission or PDSCH reception) .
  • the resource scheme 500 may include an initial UL BWP 520 and an initial DL BWP 525.
  • RO 1 530, RO 2 535, RO 3 540, and RO 4 545 may be associated with frequency domain resources that fall within frequency domain resources associated with the initial UL BWP 520.
  • the initial DL BWP 525 may include one or more sub-bands, such as sub-band 0 550, sub-band 1 555, sub-band 2 560, and sub-band 3 565.
  • a sub-band for shared channel reception may be the sub-band that UE monitors for control channel reception (e.g., Msg2 PDCCH) .
  • Msg2 PDCCH control channel reception
  • the UE may determine that the UE is to monitor sub-band 2 560 to receive the PDSCH message 575 (e.g., based on the frequency overlap 580) .
  • the sub-band for shared channel reception may be indicated to the UE in control channel signaling (e.g., Msg2 PDCCH) .
  • control channel signaling e.g., Msg2 PDCCH
  • the UE may determine that the UE is to monitor sub-band 0 550 to receive the PDSCH message 575 based on the indication 585 indicating the sub-band 0 550.
  • the UE may determine or select a sub-band for second control channel monitoring for another control message (e.g., Msg4 PDCCH monitoring) that may be the same as the sub-band used for the first control channel monitoring (e.g., Msg2 PDCCH monitoring) , the same as the sub-band used for the first shared channel monitoring (e.g., Msg2 PDSCH monitoring) , or may be configured (e.g., via an indication, such as indication 585) in the first control channel signaling (e.g., the PDCCH message 570, which may be an example of Msg2) .
  • Msg4 PDCCH monitoring another control message
  • the PDCCH message 570 may be an example of Msg2 .
  • the UE may determine or select a sub-band for second shared channel monitoring for another shared channel message (Msg4 PDSCH monitoring) may be the same as the same as the sub-band used for the first control channel monitoring (e.g., Msg2 PDCCH monitoring) , the same as the sub-band used for the first shared channel monitoring (e.g., Msg2 PDSCH monitoring) , the same as the control channel monitoring associated with retransmission (e.g., Msg3 PDCCH messaging or monitoring) , or may be configured (e.g., via an indication, such as indication 585) in the first control channel signaling (e.g., the PDCCH message 570, which may be an example of Msg2 or Msg4) or in random access response (RAR) signaling.
  • Msg4 PDSCH monitoring may be the same as the same as the sub-band used for the first control channel monitoring (e.g., Msg2 PDCCH monitoring) , the same as the sub-band used for
  • FIG. 6 illustrates an example of a resource scheme 600 that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • the resource scheme 600 may be associated with shared channel message transmission or shared channel message reception (e.g., PDSCH transmission or PDSCH reception) .
  • the resource scheme 600 may include an initial DL BWP 620 and an initial UL BWP 625.
  • the initial DL BWP 620 may include one or more sub-bands, such as DL sub-band 0 630, DL sub-band 1 635, DL sub-band 2 640, and DL sub-band 3 645.
  • the initial UL BWP 625 may include one or more sub-bands, such as UL sub-band 0 650, UL sub-band 1 655, UL sub-band 2 660, and UL sub-band 3 665.
  • the UE may determine an UL sub-band for UL transmission (e.g., PUCCH, PUSCH, or both) based on a DL sub-band used for DL reception (e.g., PDCCH, PDSCH, or both) .
  • an UL sub-band for UL transmission e.g., PUCCH, PUSCH, or both
  • a DL sub-band used for DL reception e.g., PDCCH, PDSCH, or both
  • the UE may use the UL sub-band 2 660 that corresponds to the DL sub-band 2 640 (e.g., the frequency resources of the UL sub-band 2 660 and the DL sub-band 2 640 completely overlap or are the same, as indicated by the frequency overlap 670) for monitoring form the PUCCH message 680, the PUSCH message 685, or both.
  • the UL sub-band 2 660 corresponds to the DL sub-band 2 640 (e.g., the frequency resources of the UL sub-band 2 660 and the DL sub-band 2 640 completely overlap or are the same, as indicated by the frequency overlap 670) for monitoring form the PUCCH message 680, the PUSCH message 685, or both.
  • a network entity may configure a mapping between an UL sub-band and a DL sub-band. For example, the network entity may configure (e.g., signal to the UE) the mapping 675 that may map the DL sub-band 1 635 and the UL sub-band 0 650. If the UE uses the SL sub-band 1 635 to monitor for a first PDSCH or PDCCH, the UE may use the UL sub-band 0 650 to transmit the PUCCH message 680, the PUSCH message 685, or both.
  • Such a mapping may be a 1-to-1 mapping (e.g., one RO to one sub-band) , a 1-to-many mapping (e.g., one RO to multiple sub-bands) , a many-to-1 mapping (e.g., multiple ROs to a single sub-band) , or a many-to-many mapping (e.g., multiple ROs to multiple sub-bands) .
  • the mapping may be implicit (e.g., based on the frequency domain overlapping between UL sub-band and DL sub-band) .
  • the frequency overlap 670 may be an example of such implicit mapping.
  • the UE may determine a sub-band for UL transmission based on the configured mapping and the RO used for transmission of a first random access message (e.g., PRACH transmission) . For example, suppose that the UE selected an RO corresponding to DL sub-band 1 635 for transmission of the first random access message and subsequently monitored the DL sub-band 1 635 as a result. The UE may then select and monitor the UL sub-band 0 650 based on the mapping 675, the RO (e.g., that corresponds to the DL sub-band 1 635, optionally using one or more techniques described herein) , or both.
  • a first random access message e.g., PRACH transmission
  • FIG. 7 illustrates an example of a process flow 700 that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • the process flow 700 may implement various aspects of the present disclosure described herein.
  • the elements described in the process flow 700 e.g., UE 115-b and network entity 105-b
  • the operations between the various entities or elements may be performed in different orders or at different times. Some operations may also be left out of the process flow 700, or other operations may be added. Although the various entities or elements are shown performing the operations of the process flow 700, some aspects of some operations may also be performed by other entities or elements of the process flow 700 or by entities or elements that are not depicted in the process flow, or any combination thereof.
  • the UE 115-b may receive a synchronization signal block message that may indicate an initial uplink bandwidth part and a plurality of random access occasions and at least a subset of the plurality of random access occasions may be frequency division multiplexed within the initial uplink bandwidth part.
  • the UE 115-b may receive, based on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part.
  • the UE 115-b may receive system information that may indicate a frequency domain resource allocation offset of the initial downlink bandwidth part that is relative to a first physical resource block of the initial downlink bandwidth part.
  • the UE 115-b may determine the offset of the first sub-band relative to a first physical resource block of the initial downlink bandwidth part based on a subcarrier spacing of the initial downlink bandwidth part. In some examples, the UE 115-b may receive system information indicating the offset of the first sub-band. In some examples, the UE 115-b may determine the offset of the first sub-band based on a maximum bandwidth capability of the UE.
  • the UE 115-b may transmit a first random access message in a first random access occasion of the plurality of random access occasions.
  • the UE 115-b may transmit a preamble of the first random access message in a first sub-band of the initial uplink bandwidth part and transmit a payload of the first random access message in the first sub-band of the initial uplink bandwidth part based on transmitting the preamble in the first sub-band.
  • the UE 115-b may transmit the payload of the first random access message in the second sub-band of the initial uplink bandwidth part based on a mapping between the payload and the second sub-band.
  • the UE 115-b may monitor for a first control channel message in a first sub-band of the initial downlink bandwidth part and an offset of the first sub-band within the initial downlink bandwidth part may be based on the first random access occasion.
  • the UE 115-b may monitor for the first control channel message in the first sub-band based on a bandwidth of the first sub-band fully overlapping with the first random access occasion. Additionally, or alternatively, the UE 115-b may monitor for the first control channel message in the first sub-band based on a mapping between the first random access occasion and the first sub-band.
  • the UE 115-b may receive the first control channel message in the first sub-band, the first control channel message that may include an indication of a second sub-band of the initial downlink bandwidth part.
  • the second sub-band may be a same sub-band as the first sub-band.
  • the UE 115-b may monitor for a first shared channel message in the first sub-band based on monitoring for the first control channel message in the first sub-band. In some examples, the UE 115-b may monitor for a first shared channel message in the second sub-band based on the indication of the second sub-band. In some examples, the second sub-band may be a same sub-band as the first sub-band.
  • the UE 115-b may determine an uplink sub-band for one or more uplink transmissions in the initial uplink bandwidth part based on a downlink sub-band used for one or more downlink transmission in the initial downlink bandwidth part.
  • the UE 115-b may receive an indication of a mapping between the uplink sub-band and the downlink sub-band and determining the uplink sub-band may be based on the indication of the mapping. Additionally, or alternatively, the UE 115-b may determine a mapping between the uplink sub-band and the downlink sub-band based on a frequency domain overlap between the uplink sub-band and the downlink sub-band. In some examples, the UE 115-b may determine the uplink sub-band based on the first random access occasion.
  • the UE 115-b may monitor for a second control channel message, a second shared channel message, or both in the first sub-band based on monitoring for the first control channel message in the first sub-band.
  • the UE 115-b may monitor for a second control channel message, a second shared channel message, or both in the second sub-band based on monitoring for the first shared channel message in the second sub-band or the indication of the second sub-band.
  • the second sub-band may be a same sub-band as the first sub-band.
  • the UE 115-b may monitor for a second control channel message, a second shared channel message, or both in the second sub-band based on monitoring for the first shared channel message in the second sub-band or the indication of the second sub-band. In some examples, the UE 115-b may monitor for a second shared channel message based on monitoring for a second control channel message in the first sub-band or the second sub-band. In some examples, the UE 115-b may monitor for a second shared channel message in a sub-band in which the UE monitored for a control channel message associated with an uplink retransmission. In some examples, the second sub-band may be a same sub-band as the first sub-band.
  • FIG. 8 shows a block diagram 800 of a device 805 that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • the device 805 may be an example of aspects of a UE 115 as described herein.
  • the device 805 may include a receiver 810, a transmitter 815, and a communications manager 820.
  • the device 805 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 810 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 random access frequency resource linkage) . Information may be passed on to other components of the device 805.
  • the receiver 810 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 815 may provide a means for transmitting signals generated by other components of the device 805.
  • the transmitter 815 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 random access frequency resource linkage) .
  • the transmitter 815 may be co-located with a receiver 810 in a transceiver module.
  • the transmitter 815 may utilize a single antenna or a set of multiple antennas.
  • the communications manager 820, the receiver 810, the transmitter 815, or various combinations thereof or various components thereof may be examples of means for performing various aspects of random access frequency resource linkage as described herein.
  • the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may support a method for performing one or more of the functions described herein.
  • the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a digital signal processor (DSP) , a central processing unit (CPU) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting 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
  • a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory) .
  • the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager 820, the receiver 810, the transmitter 815, 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 a means for performing the functions described in the present disclosure) .
  • code e.g., as communications management software or firmware
  • the functions of the communications manager 820, the receiver 810, the transmitter 815, 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 a
  • the communications manager 820 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 810, the transmitter 815, or both.
  • the communications manager 820 may receive information from the receiver 810, send information to the transmitter 815, or be integrated in combination with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 820 may support wireless communication at a UE in accordance with examples as disclosed herein.
  • the communications manager 820 may be configured as or otherwise support a means for receiving a synchronization signal block message that indicates an initial uplink bandwidth part and a set of multiple random access occasions, where at least a subset of the set of multiple random access occasions are frequency division multiplexed within the initial uplink bandwidth part.
  • the communications manager 820 may be configured as or otherwise support a means for receiving, based on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part.
  • the communications manager 820 may be configured as or otherwise support a means for transmitting a first random access message in a first random access occasion of the set of multiple random access occasions.
  • the communications manager 820 may be configured as or otherwise support a means for monitoring for a first control channel message in a first sub-band of the initial downlink bandwidth part, where an offset of the first sub-band within the initial downlink bandwidth part is based on the first random access occasion.
  • the device 805 e.g., a processor controlling or otherwise coupled with the receiver 810, the transmitter 815, the communications manager 820, or a combination thereof
  • the device 805 may support techniques for reduced processing, reduced power consumption, more efficient utilization of communication resources, or any combination thereof.
  • FIG. 9 shows a block diagram 900 of a device 905 that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • the device 905 may be an example of aspects of a device 805 or 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 may also include a processor. 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 random access frequency resource linkage) . 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 random access frequency resource linkage) .
  • 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 device 905, or various components thereof may be an example of means for performing various aspects of random access frequency resource linkage as described herein.
  • the communications manager 920 may include an SSB reception component 925, a MIB reception component 930, a random access component 935, a control channel component 940, or any combination thereof.
  • the communications manager 920 may be an example of aspects of a communications manager 820 as described herein.
  • the communications manager 920, 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 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 may support wireless communication at a UE in accordance with examples as disclosed herein.
  • the SSB reception component 925 may be configured as or otherwise support a means for receiving a synchronization signal block message that indicates an initial uplink bandwidth part and a set of multiple random access occasions, where at least a subset of the set of multiple random access occasions are frequency division multiplexed within the initial uplink bandwidth part.
  • the MIB reception component 930 may be configured as or otherwise support a means for receiving, based on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part.
  • the random access component 935 may be configured as or otherwise support a means for transmitting a first random access message in a first random access occasion of the set of multiple random access occasions.
  • the control channel component 940 may be configured as or otherwise support a means for monitoring for a first control channel message in a first sub-band of the initial downlink bandwidth part, where an offset of the first sub-band within the initial downlink bandwidth part is based on the first random access occasion.
  • FIG. 10 shows a block diagram 1000 of a communications manager 1020 that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • the communications manager 1020 may be an example of aspects of a communications manager 820, a communications manager 920, or both, as described herein.
  • the communications manager 1020, or various components thereof, may be an example of means for performing various aspects of random access frequency resource linkage as described herein.
  • the communications manager 1020 may include an SSB reception component 1025, a MIB reception component 1030, a random access component 1035, a control channel component 1040, a sub-band offset component 1045, a shared channel component 1050, an uplink sub-band component 1055, or any combination thereof.
  • Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
  • the communications manager 1020 may support wireless communication at a UE in accordance with examples as disclosed herein.
  • the SSB reception component 1025 may be configured as or otherwise support a means for receiving a synchronization signal block message that indicates an initial uplink bandwidth part and a set of multiple random access occasions, where at least a subset of the set of multiple random access occasions are frequency division multiplexed within the initial uplink bandwidth part.
  • the MIB reception component 1030 may be configured as or otherwise support a means for receiving, based on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part.
  • the random access component 1035 may be configured as or otherwise support a means for transmitting a first random access message in a first random access occasion of the set of multiple random access occasions.
  • the control channel component 1040 may be configured as or otherwise support a means for monitoring for a first control channel message in a first sub-band of the initial downlink bandwidth part, where an offset of the first sub-band within the initial downlink bandwidth part is based on the first random access occasion.
  • the sub-band offset component 1045 may be configured as or otherwise support a means for determining the offset of the first sub-band relative to a first physical resource block of the initial downlink bandwidth part based on a subcarrier spacing of the initial downlink bandwidth part.
  • the sub-band offset component 1045 may be configured as or otherwise support a means for receiving system information indicating the offset of the first sub-band.
  • the sub-band offset component 1045 may be configured as or otherwise support a means for determining the offset of the first sub-band based on a maximum bandwidth capability of the UE.
  • the sub-band offset component 1045 may be configured as or otherwise support a means for receiving system information indicating a frequency domain resource allocation offset of the initial downlink bandwidth part that is relative to a first physical resource block of the initial downlink bandwidth part.
  • control channel component 1040 may be configured as or otherwise support a means for monitoring for the first control channel message in the first sub-band based on a bandwidth of the first sub-band fully overlapping with the first random access occasion.
  • control channel component 1040 may be configured as or otherwise support a means for monitoring for the first control channel message in the first sub-band based on a mapping between the first random access occasion and the first sub-band.
  • the shared channel component 1050 may be configured as or otherwise support a means for monitoring for a first shared channel message in the first sub-band based on monitoring for the first control channel message in the first sub-band.
  • control channel component 1040 may be configured as or otherwise support a means for monitoring for a second control channel message, a second shared channel message, or both in the first sub-band based on monitoring for the first control channel message in the first sub-band.
  • control channel component 1040 may be configured as or otherwise support a means for receiving the first control channel message in the first sub-band, the first control channel message including an indication of a second sub-band of the initial downlink bandwidth part.
  • the shared channel component 1050 may be configured as or otherwise support a means for monitoring for a first shared channel message in the second sub-band based on the indication of the second sub-band.
  • the random access component 1035 may be configured as or otherwise support a means for monitoring for a second control channel message, a second shared channel message, or both in the second sub-band based on monitoring for the first shared channel message in the second sub-band or the indication of the second sub-band.
  • the shared channel component 1050 may be configured as or otherwise support a means for monitoring for a second shared channel message based on monitoring for a second control channel message in the first sub-band or the second sub-band.
  • the shared channel component 1050 may be configured as or otherwise support a means for monitoring for a second shared channel message in a sub-band in which the UE monitored for a control channel message associated with an uplink retransmission.
  • the second sub-band is a same sub-band as the first sub-band.
  • the uplink sub-band component 1055 may be configured as or otherwise support a means for determining an uplink sub-band for one or more uplink transmissions in the initial uplink bandwidth part based on a downlink sub-band used for one or more downlink transmission in the initial downlink bandwidth part.
  • the uplink sub-band component 1055 may be configured as or otherwise support a means for receiving an indication of a mapping between the uplink sub-band and the downlink sub-band, where determining the uplink sub-band is based on the indication of the mapping.
  • the uplink sub-band component 1055 may be configured as or otherwise support a means for determining a mapping between the uplink sub-band and the downlink sub-band based on a frequency domain overlap between the uplink sub-band and the downlink sub-band.
  • the uplink sub-band component 1055 may be configured as or otherwise support a means for determining the uplink sub-band based on the first random access occasion.
  • the random access component 1035 may be configured as or otherwise support a means for transmitting a preamble of the first random access message in a first sub-band of the initial uplink bandwidth part. In some examples, the random access component 1035 may be configured as or otherwise support a means for transmitting a payload of the first random access message in the first sub-band of the initial uplink bandwidth part based on transmitting the preamble in the first sub-band.
  • the random access component 1035 may be configured as or otherwise support a means for transmitting a preamble of the first random access message in a first sub-band of the initial uplink bandwidth part. In some examples, the random access component 1035 may be configured as or otherwise support a means for transmitting a payload of the first random access message in a second sub-band of the initial uplink bandwidth part based on a mapping between the payload and the second sub-band.
  • FIG. 11 shows a diagram of a system 1100 including a device 1105 that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • the device 1105 may be an example of or include the components of a device 805, a device 905, or a UE 115 as described herein.
  • the device 1105 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof.
  • the device 1105 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1120, an input/output (I/O) controller 1110, a transceiver 1115, an antenna 1125, a memory 1130, code 1135, and a processor 1140. 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 1145) .
  • buses
  • the I/O controller 1110 may manage input and output signals for the device 1105.
  • the I/O controller 1110 may also manage peripherals not integrated into the device 1105.
  • the I/O controller 1110 may represent a physical connection or port to an external peripheral.
  • the I/O controller 1110 may utilize an operating system such as or another known operating system.
  • the I/O controller 1110 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device.
  • the I/O controller 1110 may be implemented as part of a processor, such as the processor 1140.
  • a user may interact with the device 1105 via the I/O controller 1110 or via hardware components controlled by the I/O controller 1110.
  • the device 1105 may include a single antenna 1125. However, in some other cases, the device 1105 may have more than one antenna 1125, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 1115 may communicate bi-directionally, via the one or more antennas 1125, wired, or wireless links as described herein.
  • the transceiver 1115 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1115 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1125 for transmission, and to demodulate packets received from the one or more antennas 1125.
  • the transceiver 1115 may be an example of a transmitter 815, a transmitter 915, a receiver 810, a receiver 910, or any combination thereof or component thereof, as described herein.
  • the memory 1130 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 1130 may store computer-readable, computer-executable code 1135 including instructions that, when executed by the processor 1140, cause the device 1105 to perform various functions described herein.
  • the code 1135 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code 1135 may not be directly executable by the processor 1140 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 1130 may contain, 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 processor 1140 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 1140 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 1140.
  • the processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1130) to cause the device 1105 to perform various functions (e.g., functions or tasks supporting random access frequency resource linkage) .
  • the device 1105 or a component of the device 1105 may include a processor 1140 and memory 1130 coupled with or to the processor 1140, the processor 1140 and memory 1130 configured to perform various functions described herein.
  • the communications manager 1120 may support wireless communication at a UE in accordance with examples as disclosed herein.
  • the communications manager 1120 may be configured as or otherwise support a means for receiving a synchronization signal block message that indicates an initial uplink bandwidth part and a set of multiple random access occasions, where at least a subset of the set of multiple random access occasions are frequency division multiplexed within the initial uplink bandwidth part.
  • the communications manager 1120 may be configured as or otherwise support a means for receiving, based on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part.
  • the communications manager 1120 may be configured as or otherwise support a means for transmitting a first random access message in a first random access occasion of the set of multiple random access occasions.
  • the communications manager 1120 may be configured as or otherwise support a means for monitoring for a first control channel message in a first sub-band of the initial downlink bandwidth part, where an offset of the first sub-band within the initial downlink bandwidth part is based on the first random access occasion.
  • the device 1105 may support techniques for improved communication reliability, reduced latency, improved user experience related to reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, improved utilization of processing capability, or any combination thereof.
  • the communications manager 1120 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 1115, the one or more antennas 1125, or any combination thereof.
  • the communications manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1120 may be supported by or performed by the processor 1140, the memory 1130, the code 1135, or any combination thereof.
  • the code 1135 may include instructions executable by the processor 1140 to cause the device 1105 to perform various aspects of random access frequency resource linkage as described herein, or the processor 1140 and the memory 1130 may be otherwise configured to perform or support such operations.
  • FIG. 12 shows a block diagram 1200 of a device 1205 that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • the device 1205 may be an example of aspects of a network entity 105 as described herein.
  • the device 1205 may include a receiver 1210, a transmitter 1215, and a communications manager 1220.
  • the device 1205 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 1210 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 1205.
  • the receiver 1210 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1210 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 1215 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1205.
  • the transmitter 1215 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 1215 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1215 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 1215 and the receiver 1210 may be co-located in a transceiver, which may include or be coupled with a modem.
  • the communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof or various components thereof may be examples of means for performing various aspects of random access frequency resource linkage as described herein.
  • the communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may support a method for performing one or more of the functions described herein.
  • the communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include 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 a means for performing the functions described in the present disclosure.
  • a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory) .
  • the communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager 1220, the receiver 1210, the transmitter 1215, 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 a means for performing the functions described in the present disclosure) .
  • code e.g., as communications management software or firmware
  • the functions of the communications manager 1220, the receiver 1210, the transmitter 1215, 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 a
  • the communications manager 1220 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1210, the transmitter 1215, or both.
  • the communications manager 1220 may receive information from the receiver 1210, send information to the transmitter 1215, or be integrated in combination with the receiver 1210, the transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 1220 may support wireless communication at a network entity in accordance with examples as disclosed herein.
  • the communications manager 1220 may be configured as or otherwise support a means for transmitting a synchronization signal block message that indicates an initial uplink bandwidth part and a set of multiple random access occasions, where at least a subset of the set of multiple random access occasions are frequency division multiplexed within the initial uplink bandwidth part.
  • the communications manager 1220 may be configured as or otherwise support a means for transmitting, based on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part.
  • the communications manager 1220 may be configured as or otherwise support a means for receiving a first random access message in a first random access occasion of the set of multiple random access occasions.
  • the communications manager 1220 may be configured as or otherwise support a means for transmitting a first control channel message in a first sub-band of the initial downlink bandwidth part, where an offset of the first sub-band within the initial downlink bandwidth part is based on the first random access occasion.
  • the device 1205 e.g., a processor controlling or otherwise coupled with the receiver 1210, the transmitter 1215, the communications manager 1220, or a combination thereof
  • the device 1205 may support techniques for reduced processing, reduced power consumption, more efficient utilization of communication resources, or any combination thereof.
  • FIG. 13 shows a block diagram 1300 of a device 1305 that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • the device 1305 may be an example of aspects of a device 1205 or 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 may also include a processor. 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 device 1305, or various components thereof may be an example of means for performing various aspects of random access frequency resource linkage as described herein.
  • the communications manager 1320 may include an SSB transmission component 1325, a MIB transmission component 1330, a random access component 1335, a control channel component 1340, or any combination thereof.
  • the communications manager 1320 may be an example of aspects of a communications manager 1220 as described herein.
  • the communications manager 1320, 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 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 may support wireless communication at a network entity in accordance with examples as disclosed herein.
  • the SSB transmission component 1325 may be configured as or otherwise support a means for transmitting a synchronization signal block message that indicates an initial uplink bandwidth part and a set of multiple random access occasions, where at least a subset of the set of multiple random access occasions are frequency division multiplexed within the initial uplink bandwidth part.
  • the MIB transmission component 1330 may be configured as or otherwise support a means for transmitting, based on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part.
  • the random access component 1335 may be configured as or otherwise support a means for receiving a first random access message in a first random access occasion of the set of multiple random access occasions.
  • the control channel component 1340 may be configured as or otherwise support a means for transmitting a first control channel message in a first sub-band of the initial downlink bandwidth part, where an offset of the first sub-band within the initial downlink bandwidth part is based on the first random access occasion.
  • FIG. 14 shows a block diagram 1400 of a communications manager 1420 that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • the communications manager 1420 may be an example of aspects of a communications manager 1220, a communications manager 1320, or both, as described herein.
  • the communications manager 1420, or various components thereof, may be an example of means for performing various aspects of random access frequency resource linkage as described herein.
  • the communications manager 1420 may include an SSB transmission component 1425, a MIB transmission component 1430, a random access component 1435, a control channel component 1440, a sub-band offset component 1445, a shared channel component 1450, an uplink sub-band component 1455, or any combination thereof.
  • Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses) which 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 communications manager 1420 may support wireless communication at a network entity in accordance with examples as disclosed herein.
  • the SSB transmission component 1425 may be configured as or otherwise support a means for transmitting a synchronization signal block message that indicates an initial uplink bandwidth part and a set of multiple random access occasions, where at least a subset of the set of multiple random access occasions are frequency division multiplexed within the initial uplink bandwidth part.
  • the MIB transmission component 1430 may be configured as or otherwise support a means for transmitting, based on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part.
  • the random access component 1435 may be configured as or otherwise support a means for receiving a first random access message in a first random access occasion of the set of multiple random access occasions.
  • the control channel component 1440 may be configured as or otherwise support a means for transmitting a first control channel message in a first sub-band of the initial downlink bandwidth part, where an offset of the first sub-band within the initial downlink bandwidth part is based on the first random access occasion.
  • the sub-band offset component 1445 may be configured as or otherwise support a means for determining the offset of the first sub-band relative to a first physical resource block of the initial downlink bandwidth part based on a subcarrier spacing of the initial downlink bandwidth part.
  • the sub-band offset component 1445 may be configured as or otherwise support a means for transmitting system information indicating the offset of the first sub-band.
  • the sub-band offset component 1445 may be configured as or otherwise support a means for determining the offset of the first sub-band based on a maximum bandwidth capability of a UE.
  • the sub-band offset component 1445 may be configured as or otherwise support a means for transmitting system information indicating a frequency domain resource allocation offset of the initial downlink bandwidth part that is relative to a first physical resource block of the initial downlink bandwidth part.
  • control channel component 1440 may be configured as or otherwise support a means for transmitting the first control channel message in the first sub-band based on a bandwidth of the first sub-band fully overlapping with the first random access occasion.
  • control channel component 1440 may be configured as or otherwise support a means for transmitting the first control channel message in the first sub-band based on a mapping between the first random access occasion and the first sub-band.
  • the shared channel component 1450 may be configured as or otherwise support a means for transmitting a first shared channel message in the first sub-band based on transmitting the first control channel message in the first sub-band.
  • control channel component 1440 may be configured as or otherwise support a means for transmitting a second control channel message, a second shared channel message, or both in the first sub-band based on transmitting the first control channel message in the first sub-band.
  • control channel component 1440 may be configured as or otherwise support a means for transmitting the first control channel message in the first sub-band, the first control channel message including an indication of a second sub-band of the initial downlink bandwidth part.
  • the shared channel component 1450 may be configured as or otherwise support a means for transmitting a first shared channel message in the second sub-band based on the indication of the second sub-band.
  • the random access component 1435 may be configured as or otherwise support a means for transmitting a second control channel message, a second shared channel message, or both in the second sub-band based on transmitting the first shared channel message in the second sub-band or the indication of the second sub-band.
  • the shared channel component 1450 may be configured as or otherwise support a means for transmitting a second shared channel message based on transmitting a second control channel message in the first sub-band or the second sub-band.
  • the shared channel component 1450 may be configured as or otherwise support a means for transmitting a second shared channel message in a sub-band in which the network entity transmitted a control channel message associated with an uplink retransmission.
  • the second sub-band is a same sub-band as the first sub-band.
  • the uplink sub-band component 1455 may be configured as or otherwise support a means for determining an uplink sub-band for one or more uplink transmissions in the initial uplink bandwidth part based on a downlink sub-band used for one or more downlink transmission in the initial downlink bandwidth part.
  • the uplink sub-band component 1455 may be configured as or otherwise support a means for transmitting an indication of a mapping between the uplink sub-band and the downlink sub-band, where determining the uplink sub-band is based on the indication of the mapping.
  • the uplink sub-band component 1455 may be configured as or otherwise support a means for determining a mapping between the uplink sub- band and the downlink sub-band based on a frequency domain overlap between the uplink sub-band and the downlink sub-band.
  • the uplink sub-band component 1455 may be configured as or otherwise support a means for determining the uplink sub-band based on the first random access occasion.
  • the random access component 1435 may be configured as or otherwise support a means for receiving a preamble of the first random access message in a first sub-band of the initial uplink bandwidth part. In some examples, the random access component 1435 may be configured as or otherwise support a means for receiving a payload of the first random access message in the first sub-band of the initial uplink bandwidth part based on receiving the preamble in the first sub-band.
  • the random access component 1435 may be configured as or otherwise support a means for receiving a preamble of the first random access message in a first sub-band of the initial uplink bandwidth part. In some examples, the random access component 1435 may be configured as or otherwise support a means for receiving a payload of the first random access message in a second sub-band of the initial uplink bandwidth part based on a mapping between the payload and the second sub-band.
  • FIG. 15 shows a diagram of a system 1500 including a device 1505 that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • the device 1505 may be an example of or include the components of a device 1205, a device 1305, or a network entity 105 as described herein.
  • the device 1505 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof.
  • the device 1505 may include components that support outputting and obtaining communications, such as a communications manager 1520, a transceiver 1510, an antenna 1515, a memory 1525, code 1530, and a processor 1535. 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 1540) .
  • buses e.g.,
  • the transceiver 1510 may support bi-directional communications via wired links, wireless links, or both as described herein.
  • the transceiver 1510 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1510 may include a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the device 1505 may include one or more antennas 1515, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently) .
  • the transceiver 1510 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1515, by a wired transmitter) , to receive modulated signals (e.g., from one or more antennas 1515, from a wired receiver) , and to demodulate signals.
  • the transceiver 1510 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1515 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1515 that are configured to support various transmitting or outputting operations, or a combination thereof.
  • the transceiver 1510 may include or be configured for coupling with one or more processors or 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 1510, or the transceiver 1510 and the one or more antennas 1515, or the transceiver 1510 and the one or more antennas 1515 and one or more processors or memory components may be included in a chip or chip assembly that is installed in the device 1505.
  • the transceiver may be operable to support communications via one or more communications links (e.g., a communication link 125, a backhaul communication link 120, a midhaul communication link 162, a fronthaul communication link 168) .
  • one or more communications links e.g., a communication link 125, a backhaul communication link 120, a midhaul communication link 162, a fronthaul communication link 168 .
  • the memory 1525 may include RAM and ROM.
  • the memory 1525 may store computer-readable, computer-executable code 1530 including instructions that, when executed by the processor 1535, cause the device 1505 to perform various functions described herein.
  • the code 1530 may be stored in a non-transitory computer- readable medium such as system memory or another type of memory. In some cases, the code 1530 may not be directly executable by the processor 1535 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 1525 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • the processor 1535 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, a discrete hardware component, or any combination thereof) .
  • the processor 1535 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 1535.
  • the processor 1535 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1525) to cause the device 1505 to perform various functions (e.g., functions or tasks supporting random access frequency resource linkage) .
  • the device 1505 or a component of the device 1505 may include a processor 1535 and memory 1525 coupled with the processor 1535, the processor 1535 and memory 1525 configured to perform various functions described herein.
  • the processor 1535 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 1530) to perform the functions of the device 1505.
  • the processor 1535 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1505 (such as within the memory 1525) .
  • the processor 1535 may be a component of a processing system.
  • a processing system may generally refer to a system or series of machines or components that receives inputs and processes the inputs to produce a set of outputs (which may be passed to other systems or components of, for example, the device 1505) .
  • a processing system of the device 1505 may refer to a system including the various other components or subcomponents of the device 1505, such as the processor 1535, or the transceiver 1510, or the communications manager 1520, or other components or combinations of components of the device 1505.
  • the processing system of the device 1505 may interface with other components of the device 1505, and may process information received from other components (such as inputs or signals) or output information to other components.
  • a chip or modem of the device 1505 may include a processing system and one or more interfaces to output information, or to obtain information, or both.
  • the one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or a same interface configured to output information and to obtain information, among other implementations.
  • the one or more interfaces may refer to an interface between the processing system of the chip or modem and a transmitter, such that the device 1505 may transmit information output from the chip or modem.
  • the one or more interfaces may refer to an interface between the processing system of the chip or modem and a receiver, such that the device 1505 may obtain information or signal inputs, and the information may be passed to the processing system.
  • a first interface also may obtain information or signal inputs
  • a second interface also may output information or signal outputs.
  • a bus 1540 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1540 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 1505, or between different components of the device 1505 that may be co-located or located in different locations (e.g., where the device 1505 may refer to a system in which one or more of the communications manager 1520, the transceiver 1510, the memory 1525, the code 1530, and the processor 1535 may be located in one of the different components or divided between different components) .
  • a logical channel of a protocol stack e.g., between protocol layers of a protocol stack
  • the device 1505 may refer to a system in which one or more of the communications manager 1520, the transceiver 1510, the memory 1525, the code 1530, and the processor 1535 may be located in one of the different components
  • the communications manager 1520 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links) .
  • the communications manager 1520 may manage the transfer of data communications for client devices, such as one or more UEs 115.
  • the communications manager 1520 may manage communications with other network entities 105, and may include a controller or scheduler for controlling communications with UEs 115 in cooperation with other network entities 105.
  • the communications manager 1520 may support an X2 interface within an LTE/LTE-A wireless communications network technology to provide communication between network entities 105.
  • the communications manager 1520 may support wireless communication at a network entity in accordance with examples as disclosed herein.
  • the communications manager 1520 may be configured as or otherwise support a means for transmitting a synchronization signal block message that indicates an initial uplink bandwidth part and a set of multiple random access occasions, where at least a subset of the set of multiple random access occasions are frequency division multiplexed within the initial uplink bandwidth part.
  • the communications manager 1520 may be configured as or otherwise support a means for transmitting, based on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part.
  • the communications manager 1520 may be configured as or otherwise support a means for receiving a first random access message in a first random access occasion of the set of multiple random access occasions.
  • the communications manager 1520 may be configured as or otherwise support a means for transmitting a first control channel message in a first sub-band of the initial downlink bandwidth part, where an offset of the first sub-band within the initial downlink bandwidth part is based on the first random access occasion.
  • the device 1505 may support techniques for improved communication reliability, reduced latency, improved user experience related to reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, improved utilization of processing capability, or any combination thereof.
  • the communications manager 1520 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1510, the one or more antennas 1515 (e.g., where applicable) , or any combination thereof.
  • the communications manager 1520 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1520 may be supported by or performed by the transceiver 1510, the processor 1535, the memory 1525, the code 1530, or any combination thereof.
  • the code 1530 may include instructions executable by the processor 1535 to cause the device 1505 to perform various aspects of random access frequency resource linkage as described herein, or the processor 1535 and the memory 1525 may be otherwise configured to perform or support such operations.
  • FIG. 16 shows a flowchart illustrating a method 1600 that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • the operations of the method 1600 may be implemented by a UE or its components as described herein.
  • the operations of the method 1600 may be performed by a UE 115 as described with reference to FIGs. 1 through 11.
  • 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 a synchronization signal block message that indicates an initial uplink bandwidth part and a set of multiple random access occasions, where at least a subset of the set of multiple random access occasions are frequency division multiplexed within the initial uplink bandwidth part.
  • the operations of 1605 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed by an SSB reception component 1025 as described with reference to FIG. 10.
  • the method may include receiving, based on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part.
  • the operations of 1610 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed by a MIB reception component 1030 as described with reference to FIG. 10.
  • the method may include transmitting a first random access message in a first random access occasion of the set of multiple random access occasions.
  • the operations of 1615 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed by a random access component 1035 as described with reference to FIG. 10.
  • the method may include monitoring for a first control channel message in a first sub-band of the initial downlink bandwidth part, where an offset of the first sub-band within the initial downlink bandwidth part is based on the first random access occasion.
  • the operations of 1620 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed by a control channel component 1040 as described with reference to FIG. 10.
  • FIG. 17 shows a flowchart illustrating a method 1700 that supports random access frequency resource linkage in accordance with one or more examples as described herein.
  • the operations of the method 1700 may be implemented by a network entity or its components as described herein.
  • the operations of the method 1700 may be performed by a network entity as described with reference to FIGs. 1 through 7 and 12 through 15.
  • a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.
  • the method may include transmitting a synchronization signal block message that indicates an initial uplink bandwidth part and a set of multiple random access occasions, where at least a subset of the set of multiple random access occasions are frequency division multiplexed within the initial uplink bandwidth part.
  • 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 an SSB transmission component 1425 as described with reference to FIG. 14.
  • the method may include transmitting, based on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part.
  • 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 MIB transmission component 1430 as described with reference to FIG. 14.
  • the method may include receiving a first random access message in a first random access occasion of the set of multiple random access occasions.
  • 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 random access component 1435 as described with reference to FIG. 14.
  • the method may include transmitting a first control channel message in a first sub-band of the initial downlink bandwidth part, where an offset of the first sub-band within the initial downlink bandwidth part is based on the first random access occasion.
  • 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 control channel component 1440 as described with reference to FIG. 14.
  • a method for wireless communication at a UE comprising: receiving a synchronization signal block message that indicates an initial uplink bandwidth part and a plurality of random access occasions, wherein at least a subset of the plurality of random access occasions are frequency division multiplexed within the initial uplink bandwidth part; receiving, based at least in part on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part; transmitting a first random access message in a first random access occasion of the plurality of random access occasions; and monitoring for a first control channel message in a first sub-band of the initial downlink bandwidth part, wherein an offset of the first sub-band within the initial downlink bandwidth part is based at least in part on the first random access occasion.
  • Aspect 2 The method of aspect 1, further comprising: determining the offset of the first sub-band relative to a first physical resource block of the initial downlink bandwidth part based at least in part on a subcarrier spacing of the initial downlink bandwidth part.
  • Aspect 3 The method of aspect 2, further comprising: receiving system information indicating the offset of the first sub-band.
  • Aspect 4 The method of any of aspects 2 through 3, further comprising: determining the offset of the first sub-band based at least in part on a maximum bandwidth capability of the UE.
  • Aspect 5 The method of any of aspects 1 through 4, further comprising: receiving system information indicating a frequency domain resource allocation offset of the initial downlink bandwidth part that is relative to a first physical resource block of the initial downlink bandwidth part.
  • Aspect 6 The method of any of aspects 1 through 5, further comprising: monitoring for the first control channel message in the first sub-band based at least in part on a bandwidth of the first sub-band fully overlapping with the first random access occasion.
  • Aspect 7 The method of any of aspects 1 through 6, further comprising: monitoring for the first control channel message in the first sub-band based at least in part on a mapping between the first random access occasion and the first sub-band.
  • Aspect 8 The method of any of aspects 1 through 7, further comprising: monitoring for a first shared channel message in the first sub-band based at least in part on monitoring for the first control channel message in the first sub-band.
  • Aspect 9 The method of any of aspects 1 through 8, further comprising: monitoring for a second control channel message, a second shared channel message, or both in the first sub-band based at least in part on monitoring for the first control channel message in the first sub-band.
  • Aspect 10 The method of any of aspects 1 through 9, further comprising: receiving the first control channel message in the first sub-band, the first control channel message comprising an indication of a second sub-band of the initial downlink bandwidth part.
  • Aspect 11 The method of aspect 10, further comprising: monitoring for a first shared channel message in the second sub-band based at least in part on the indication of the second sub-band.
  • Aspect 12 The method of aspect 11, further comprising: monitoring for a second control channel message, a second shared channel message, or both in the second sub-band based at least in part on monitoring for the first shared channel message in the second sub-band or the indication of the second sub-band.
  • Aspect 13 The method of any of aspects 11 through 12, further comprising: monitoring for a second shared channel message based at least in part on monitoring for a second control channel message in the first sub-band or the second sub-band.
  • Aspect 14 The method of any of aspects 11 through 13, further comprising: monitoring for a second shared channel message in a sub-band in which the UE monitored for a control channel message associated with an uplink retransmission.
  • Aspect 15 The method of any of aspects 10 through 14, wherein the second sub-band is a same sub-band as the first sub-band.
  • Aspect 16 The method of any of aspects 1 through 15, further comprising: determining an uplink sub-band for one or more uplink transmissions in the initial uplink bandwidth part based at least in part on a downlink sub-band used for one or more downlink transmission in the initial downlink bandwidth part.
  • Aspect 17 The method of aspect 16, further comprising: receiving an indication of a mapping between the uplink sub-band and the downlink sub-band, wherein determining the uplink sub-band is based at least in part on the indication of the mapping.
  • Aspect 18 The method of any of aspects 16 through 17, further comprising: determining a mapping between the uplink sub-band and the downlink sub-band based at least in part on a frequency domain overlap between the uplink sub-band and the downlink sub-band.
  • Aspect 19 The method of aspect 18, further comprising: determining the uplink sub-band is further based at least in part on the first random access occasion.
  • Aspect 20 The method of any of aspects 1 through 19, further comprising: transmitting a preamble of the first random access message in a first sub-band of the initial uplink bandwidth part; and transmitting a payload of the first random access message in the first sub-band of the initial uplink bandwidth part based at least in part on transmitting the preamble in the first sub-band.
  • Aspect 21 The method of any of aspects 1 through 20, further comprising: transmitting a preamble of the first random access message in a first sub-band of the initial uplink bandwidth part; and transmitting a payload of the first random access message in a second sub-band of the initial uplink bandwidth part based at least in part on a mapping between the payload and the second sub-band.
  • a method for wireless communication at a network entity comprising: transmitting a synchronization signal block message that indicates an initial uplink bandwidth part and a plurality of random access occasions, wherein at least a subset of the plurality of random access occasions are frequency division multiplexed within the initial uplink bandwidth part; transmitting, based at least in part on receiving the synchronization signal block message, a master information block message that indicates an initial downlink bandwidth part; receiving a first random access message in a first random access occasion of the plurality of random access occasions; and transmitting a first control channel message in a first sub-band of the initial downlink bandwidth part, wherein an offset of the first sub-band within the initial downlink bandwidth part is based at least in part on the first random access occasion.
  • Aspect 23 The method of aspect 22, further comprising: determining the offset of the first sub-band relative to a first physical resource block of the initial downlink bandwidth part based at least in part on a subcarrier spacing of the initial downlink bandwidth part.
  • Aspect 24 The method of aspect 23, further comprising: transmitting system information indicating the offset of the first sub-band.
  • Aspect 25 The method of any of aspects 23 through 24, further comprising: determining the offset of the first sub-band based at least in part on a maximum bandwidth capability of a UE.
  • Aspect 26 The method of any of aspects 22 through 25, further comprising: transmitting system information indicating a frequency domain resource allocation offset of the initial downlink bandwidth part that is relative to a first physical resource block of the initial downlink bandwidth part.
  • Aspect 27 The method of any of aspects 22 through 26, further comprising: transmitting the first control channel message in the first sub-band based at least in part on a bandwidth of the first sub-band fully overlapping with the first random access occasion.
  • Aspect 28 The method of any of aspects 22 through 27, further comprising: transmitting the first control channel message in the first sub-band based at least in part on a mapping between the first random access occasion and the first sub-band.
  • Aspect 29 The method of any of aspects 22 through 28, further comprising: transmitting a first shared channel message in the first sub-band based at least in part on transmitting the first control channel message in the first sub-band.
  • Aspect 30 The method of any of aspects 22 through 29, further comprising: transmitting a second control channel message, a second shared channel message, or both in the first sub-band based at least in part on transmitting the first control channel message in the first sub-band.
  • Aspect 31 The method of any of aspects 22 through 30, further comprising: transmitting the first control channel message in the first sub-band, the first control channel message comprising an indication of a second sub-band of the initial downlink bandwidth part.
  • Aspect 32 The method of aspect 31, further comprising: transmitting a first shared channel message in the second sub-band based at least in part on the indication of the second sub-band.
  • Aspect 33 The method of aspect 32, further comprising: transmitting a second control channel message, a second shared channel message, or both in the second sub-band based at least in part on transmitting the first shared channel message in the second sub-band or the indication of the second sub-band.
  • Aspect 34 The method of any of aspects 32 through 33, further comprising: transmitting a second shared channel message based at least in part on transmitting a second control channel message in the first sub-band or the second sub-band.
  • Aspect 35 The method of any of aspects 32 through 34, further comprising: transmitting a second shared channel message in a sub-band in which the network entity transmitted a control channel message associated with an uplink retransmission.
  • Aspect 36 The method of any of aspects 31 through 35, wherein the second sub-band is a same sub-band as the first sub-band.
  • Aspect 37 The method of any of aspects 22 through 36, further comprising: determining an uplink sub-band for one or more uplink transmissions in the initial uplink bandwidth part based at least in part on a downlink sub-band used for one or more downlink transmission in the initial downlink bandwidth part.
  • Aspect 38 The method of aspect 37, further comprising: transmitting an indication of a mapping between the uplink sub-band and the downlink sub-band, wherein determining the uplink sub-band is based at least in part on the indication of the mapping.
  • Aspect 39 The method of any of aspects 37 through 38, further comprising: determining a mapping between the uplink sub-band and the downlink sub-band based at least in part on a frequency domain overlap between the uplink sub-band and the downlink sub-band.
  • Aspect 40 The method of aspect 39, further comprising: determining the uplink sub-band is further based at least in part on the first random access occasion.
  • Aspect 41 The method of any of aspects 22 through 40, further comprising: receiving a preamble of the first random access message in a first sub-band of the initial uplink bandwidth part; and receiving a payload of the first random access message in the first sub-band of the initial uplink bandwidth part based at least in part on receiving the preamble in the first sub-band.
  • Aspect 42 The method of any of aspects 22 through 41, further comprising: receiving a preamble of the first random access message in a first sub-band of the initial uplink bandwidth part; and receiving a payload of the first random access message in a second sub-band of the initial uplink bandwidth part based at least in part on a mapping between the payload and the second sub-band.
  • Aspect 43 An apparatus for wireless communication at a UE, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 1 through 21.
  • Aspect 44 An apparatus for wireless communication at a UE, comprising at least one means for performing a method of any of aspects 1 through 21.
  • Aspect 45 A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform a method of any of aspects 1 through 21.
  • Aspect 46 An apparatus for wireless communication at a network entity, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 22 through 42.
  • Aspect 47 An apparatus for wireless communication at a network entity, comprising at least one means for performing a method of any of aspects 22 through 42.
  • Aspect 48 A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform a method of any of aspects 22 through 42.
  • 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) .
  • 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.
  • 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)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des procédés, des systèmes et des dispositifs destinés aux communications sans fil sont décrits. Un équipement utilisateur (UE) peut recevoir un message de bloc de signal de synchronisation qui indique une partie de bande passante de liaison montante initiale et une pluralité d'occasions d'accès aléatoire, au moins un sous-ensemble de la pluralité d'occasions d'accès aléatoire étant multiplexé par répartition en fréquence dans la partie de bande passante de liaison montante initiale. L'UE peut recevoir, sur la base de la réception du message de bloc de signal de synchronisation, un message de bloc d'informations maître qui indique une partie de bande passante de liaison descendante initiale. L'UE peut transmettre un premier message d'accès aléatoire dans une première occasion d'accès aléatoire de la pluralité d'occasions d'accès aléatoire. L'UE peut surveiller un premier message de canal de commande dans une première sous-bande de la partie de bande passante de liaison descendante initiale, un décalage de la première sous-bande à l'intérieur de la partie de bande passante de liaison descendante initiale étant basé sur la première occasion d'accès aléatoire.
PCT/CN2022/112198 2022-08-12 2022-08-12 Liaison de ressources de fréquence d'accès aléatoire WO2024031663A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/112198 WO2024031663A1 (fr) 2022-08-12 2022-08-12 Liaison de ressources de fréquence d'accès aléatoire

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/112198 WO2024031663A1 (fr) 2022-08-12 2022-08-12 Liaison de ressources de fréquence d'accès aléatoire

Publications (1)

Publication Number Publication Date
WO2024031663A1 true WO2024031663A1 (fr) 2024-02-15

Family

ID=89850478

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/112198 WO2024031663A1 (fr) 2022-08-12 2022-08-12 Liaison de ressources de fréquence d'accès aléatoire

Country Status (1)

Country Link
WO (1) WO2024031663A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210289471A1 (en) * 2020-03-13 2021-09-16 Qualcomm Incorporated On-demand multicast control channel messages
WO2021190510A1 (fr) * 2020-03-23 2021-09-30 FG Innovation Company Limited Procédé d'accès initial et dispositif associé
US20210329718A1 (en) * 2020-04-21 2021-10-21 Samsung Electronics Co., Ltd. Cell search procedure and initial bwp configuration for reduced capability ue device
US20210352466A1 (en) * 2020-05-07 2021-11-11 Samsung Electronics Co., Ltd. System and method for providing early indication by reduced capability nr device
CN114642069A (zh) * 2019-11-15 2022-06-17 联想(北京)有限公司 通信方法及设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114642069A (zh) * 2019-11-15 2022-06-17 联想(北京)有限公司 通信方法及设备
US20210289471A1 (en) * 2020-03-13 2021-09-16 Qualcomm Incorporated On-demand multicast control channel messages
WO2021190510A1 (fr) * 2020-03-23 2021-09-30 FG Innovation Company Limited Procédé d'accès initial et dispositif associé
US20210329718A1 (en) * 2020-04-21 2021-10-21 Samsung Electronics Co., Ltd. Cell search procedure and initial bwp configuration for reduced capability ue device
US20210352466A1 (en) * 2020-05-07 2021-11-11 Samsung Electronics Co., Ltd. System and method for providing early indication by reduced capability nr device

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "BW Reduction for RedCap UE", 3GPP TSG-RAN WG1 MEETING #106, R1-2107351, 7 August 2021 (2021-08-07), XP052038299 *
SPREADTRUM COMMUNICATIONS: "Discussion on aspects related to reduced maximum UE bandwidth", 3GPP TSG RAN WG1 #106BIS-E, R1-2108913, 2 October 2021 (2021-10-02), XP052057925 *

Similar Documents

Publication Publication Date Title
WO2024031663A1 (fr) Liaison de ressources de fréquence d'accès aléatoire
WO2024092596A1 (fr) Indication implicite de répétition de prach
WO2024045001A1 (fr) Techniques d'attribution de ressources de fréquence dans un canal d'accès aléatoire
US20240098759A1 (en) Common time resources for multicasting
US20240072980A1 (en) Resource indicator values for guard band indications
US20240040561A1 (en) Frequency resource selection for multiple channels
US11576201B2 (en) Candidate uplink grants for channel access
US20240088985A1 (en) Techniques for beam failure recovery in multi-path communications
US20240098029A1 (en) Rules for dropping overlapping uplink shared channel messages
US20240064696A1 (en) Reduced beam for paging
US20240114366A1 (en) Beam failure detection reference signal set update
US20230345454A1 (en) Techniques for sending a collision indication via a physical sidelink feedback channel
WO2024059960A1 (fr) Rapport de faisceau de liaison montante et de liaison descendante
WO2024026617A1 (fr) Paramètres de puissance par défaut par point de transmission et de réception
US20240146354A1 (en) Frequency hopping across subbands within a bandwidth part
US20240114518A1 (en) System information transmission with coverage recovery
WO2023130421A1 (fr) Commutation de liaison montante pour transmissions simultanées
US20230318736A1 (en) Configuring a mixed-waveform modulation and coding scheme table
WO2023184062A1 (fr) Configurations de ressources d'informations d'état de canal pour prédiction de faisceau
US20230354309A1 (en) Uplink control channel resource selection for scheduling request transmission
WO2024092688A1 (fr) Techniques de gestion de temporisateur d'alignement temporel en liaison montante pour de multiples points d'émission-réception
WO2023178646A1 (fr) Techniques de configuration de multiples bandes de fréquences de liaison montante supplémentaires par cellule de desserte
US20240049242A1 (en) Cross-transmission and reception point (trp) indication of a transmission configuration indication state
US20240098760A1 (en) Multicast scheduling in a full duplex network
US20240056908A1 (en) Feedback codebook construction for control channel carrier switching

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

Country of ref document: EP

Kind code of ref document: A1