[go: up one dir, main page]

WO2023010584A1 - Occasions d'accès aléatoire pour la répétition d'un message de canal partagé de liaison montante physique - Google Patents

Occasions d'accès aléatoire pour la répétition d'un message de canal partagé de liaison montante physique Download PDF

Info

Publication number
WO2023010584A1
WO2023010584A1 PCT/CN2021/111360 CN2021111360W WO2023010584A1 WO 2023010584 A1 WO2023010584 A1 WO 2023010584A1 CN 2021111360 W CN2021111360 W CN 2021111360W WO 2023010584 A1 WO2023010584 A1 WO 2023010584A1
Authority
WO
WIPO (PCT)
Prior art keywords
random access
subset
occasions
repetition
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2021/111360
Other languages
English (en)
Inventor
Hung Dinh LY
Mahmoud Taherzadeh Boroujeni
Kexin XIAO
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Priority to PCT/CN2021/111360 priority Critical patent/WO2023010584A1/fr
Publication of WO2023010584A1 publication Critical patent/WO2023010584A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/189—Transmission or retransmission of more than one copy of a message
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H04W74/0836—Random access procedures, e.g. with 4-step access with 2-step access

Definitions

  • aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for configuring and using random access occasions for repetitions of a physical uplink shared channel message.
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts.
  • Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, or the like) .
  • multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE) .
  • LTE/LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP) .
  • UMTS Universal Mobile Telecommunications System
  • a wireless network may include one or more base stations that support communication for a user equipment (UE) or multiple UEs.
  • a UE may communicate with a base station via downlink communications and uplink communications.
  • Downlink (or “DL” ) refers to a communication link from the base station to the UE
  • uplink (or “UL” ) refers to a communication link from the UE to the base station.
  • New Radio which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the 3GPP.
  • NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and/or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM) ) on the uplink, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.
  • OFDM orthogonal frequency division multiplexing
  • SC-FDM single-carrier frequency division multiplexing
  • DFT-s-OFDM discrete Fourier transform spread OFDM
  • MIMO multiple-input multiple-output
  • the apparatus may include a memory and one or more processors, coupled to the memory.
  • the one or more processors may be configured to receive, from a base station, an indication of a set of random access occasions, wherein the set of random access occasions are shared with one or more legacy UEs, and wherein the set of random access occasions are associated with repetition of a physical uplink shared channel (PUSCH) message.
  • the one or more processors may be further configured to transmit a random access preamble within a random access occasion selected from the set.
  • PUSCH physical uplink shared channel
  • the apparatus may include a memory and one or more processors, coupled to the memory.
  • the one or more processors may be configured to transmit, to a UE, an indication of a set of random access occasions, wherein the set of random access occasions are shared with one or more legacy UEs, and wherein the set of random access occasions are associated with repetition of a PUSCH message.
  • the one or more processors may be further configured to receive a random access preamble within a random access occasion selected from the set.
  • the apparatus may include a memory and one or more processors, coupled to the memory.
  • the one or more processors may be configured to receive, from a base station, an indication of a set of random access occasions, wherein the set of random access occasions is distinct from an additional set of random access occasions associated with one or more legacy UEs, and wherein at least a first subset of the set of random access occasions are associated with repetition of a PUSCH message and a second subset of the set of random access occasions are associated with a reduced capacity (RedCap) identification message.
  • the one or more processors may be further configured to transmit a random access preamble within a random access occasion selected from the first subset or the second subset.
  • the apparatus may include a memory and one or more processors, coupled to the memory.
  • the one or more processors may be configured to transmit, to a UE, an indication of a set of random access occasions, wherein the set of random access occasions is distinct from an additional set of random access occasions associated with one or more legacy UEs, and wherein at least a first subset of the set of random access occasions are associated with repetition of a PUSCH message and a second subset of the set of random access occasions are associated with a RedCap identification message.
  • the one or more processors may be further configured to receive a random access preamble within a random access occasion selected from the first subset or the second subset.
  • the method may include receiving, from a base station, an indication of a set of random access occasions, wherein the set of random access occasions are shared with one or more legacy UEs, and wherein the set of random access occasions are associated with repetition of a PUSCH message.
  • the method may further include transmitting a random access preamble within a random access occasion selected from the set.
  • the method may include transmitting, to a UE, an indication of a set of random access occasions, wherein the set of random access occasions are shared with one or more legacy UEs, and wherein the set of random access occasions are associated with repetition of a PUSCH message.
  • the method may further include receiving a random access preamble within a random access occasion selected from the set.
  • the method may include receiving, from a base station, an indication of a set of random access occasions, wherein the set of random access occasions is distinct from an additional set of random access occasions associated with one or more legacy UEs, and wherein at least a first subset of the set of random access occasions are associated with repetition of a PUSCH message and a second subset of the set of random access occasions are associated with a RedCap identification message.
  • the method may further include transmitting a random access preamble within a random access occasion selected from the first subset or the second subset.
  • the method may include transmitting, to a UE, an indication of a set of random access occasions, wherein the set of random access occasions is distinct from an additional set of random access occasions associated with one or more legacy UEs, and wherein at least a first subset of the set of random access occasions are associated with repetition of a PUSCH message and a second subset of the set of random access occasions are associated with a RedCap identification message.
  • the method may further include receiving a random access preamble within a random access occasion selected from the first subset or the second subset.
  • Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE.
  • the set of instructions when executed by one or more processors of the UE, may cause the UE to receive, from a base station, an indication of a set of random access occasions, wherein the set of random access occasions are shared with one or more legacy UEs, and wherein the set of random access occasions are associated with repetition of a PUSCH message.
  • the set of instructions when executed by one or more processors of the UE, may further cause the UE to transmit a random access preamble within a random access occasion selected from the set.
  • Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a base station.
  • the set of instructions when executed by one or more processors of the base station, may cause the base station to transmit, to a UE, an indication of a set of random access occasions, wherein the set of random access occasions are shared with one or more legacy UEs, and wherein the set of random access occasions are associated with repetition of a PUSCH message.
  • the set of instructions when executed by one or more processors of the base station, may further cause the base station to receive a random access preamble within a random access occasion selected from the set.
  • Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE.
  • the set of instructions when executed by one or more processors of the UE, may cause the UE to receive, from a base station, an indication of a set of random access occasions, wherein the set of random access occasions is distinct from an additional set of random access occasions associated with one or more legacy UEs, and wherein at least a first subset of the set of random access occasions are associated with repetition of a PUSCH message and a second subset of the set of random access occasions are associated with a RedCap identification message.
  • the set of instructions when executed by one or more processors of the UE, may further cause the UE to transmit a random access preamble within a random access occasion selected from the first subset or the second subset.
  • Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a base station.
  • the set of instructions when executed by one or more processors of the base station, may cause the base station to transmit, to a UE, an indication of a set of random access occasions, wherein the set of random access occasions is distinct from an additional set of random access occasions associated with one or more legacy UEs, and wherein at least a first subset of the set of random access occasions are associated with repetition of a PUSCH message and a second subset of the set of random access occasions are associated with a RedCap identification message.
  • the set of instructions when executed by one or more processors of the base station, may further cause the base station to receive a random access preamble within a random access occasion selected from the first subset or the second subset.
  • the apparatus may include means for receiving, from a base station, an indication of a set of random access occasions, wherein the set of random access occasions are shared with one or more legacy UEs, and wherein the set of random access occasions are associated with repetition of a PUSCH message.
  • the apparatus may further include means for transmitting a random access preamble within a random access occasion selected from the set.
  • the apparatus may include means for transmitting, to a UE, an indication of a set of random access occasions, wherein the set of random access occasions are shared with one or more legacy UEs, and wherein the set of random access occasions are associated with repetition of a PUSCH message.
  • the apparatus may further include means for receiving a random access preamble within a random access occasion selected from the set.
  • the apparatus may include means for receiving, from a base station, an indication of a set of random access occasions, wherein the set of random access occasions is distinct from an additional set of random access occasions associated with one or more legacy UEs, and wherein at least a first subset of the set of random access occasions are associated with repetition of a PUSCH message and a second subset of the set of random access occasions are associated with a RedCap identification message.
  • the apparatus may further include means for transmitting a random access preamble within a random access occasion selected from the first subset or the second subset.
  • the apparatus may include means for transmitting, to a UE, an indication of a set of random access occasions, wherein the set of random access occasions is distinct from an additional set of random access occasions associated with one or more legacy UEs, and wherein at least a first subset of the set of random access occasions are associated with repetition of a PUSCH message and a second subset of the set of random access occasions are associated with a RedCap identification message.
  • the apparatus may further include means for receiving a random access preamble within a random access occasion selected from the first subset or the second subset.
  • aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and/or processing system as substantially described herein with reference to and as illustrated by the drawings and specification.
  • aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects may be implemented in many different arrangements and scenarios.
  • Techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and/or packaging arrangements.
  • some aspects may be implemented via integrated chip embodiments or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, and/or artificial intelligence devices) .
  • Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and/or system-level components.
  • Devices incorporating described aspects and features may include additional components and features for implementation and practice of claimed and described aspects.
  • transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and/or summers) .
  • RF radio frequency
  • aspects described herein may be practiced in a wide variety of devices, components, systems, distributed arrangements, and/or end-user devices of varying size, shape, and constitution.
  • Fig. 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.
  • Fig. 2 is a diagram illustrating an example of a base station in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.
  • UE user equipment
  • Fig. 3 is a diagram illustrating an example of a four-step random access procedure, in accordance with the present disclosure.
  • Fig. 4 is a diagram illustrating an example associated with configuring and using random access occasions for repetitions of a physical uplink shared channel (PUSCH) message, in accordance with the present disclosure.
  • PUSCH physical uplink shared channel
  • Figs. 5A and 5B are diagrams illustrating examples associated with random access occasions for repetitions of a PUSCH message, in accordance with the present disclosure.
  • Figs. 6, 7, 8, and 9 are diagrams illustrating example processes associated with configuring and using random access occasions for repetitions of a PUSCH message, in accordance with the present disclosure.
  • Figs. 10 and 11 are diagrams of example apparatuses for wireless communication, in accordance with the present disclosure.
  • NR New Radio
  • RAT radio access technology
  • Fig. 1 is a diagram illustrating an example of a wireless network 100, in accordance with the present disclosure.
  • the wireless network 100 may be or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g., Long Term Evolution (LTE) ) network, among other examples.
  • the wireless network 100 may include one or more base stations 110 (shown as a BS 110a, a BS 110b, a BS 110c, and a BS 110d) , auser equipment (UE) 120 or multiple UEs 120 (shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e) , and/or other network entities.
  • UE auser equipment
  • a base station 110 is an entity that communicates with UEs 120.
  • a base station 110 (sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G) , a gNB (e.g., in 5G) , an access point, and/or a transmission reception point (TRP) .
  • Each base station 110 may provide communication coverage for a particular geographic area.
  • the term “cell” can refer to a coverage area of a base station 110 and/or a base station subsystem serving this coverage area, depending on the context in which the term is used.
  • a base station 110 may provide communication coverage for a macro cell, apico cell, a femto cell, and/or another type of cell.
  • a macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions.
  • a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscription.
  • a femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 having association with the femto cell (e.g., UEs 120 in a closed subscriber group (CSG) ) .
  • CSG closed subscriber group
  • a base station 110 for a macro cell may be referred to as a macro base station.
  • a base station 110 for a pico cell may be referred to as a pico base station.
  • a base station 110 for a femto cell may be referred to as a femto base station or an in-home base station.
  • the BS 110a may be a macro base station for a macro cell 102a
  • the BS 110b may be a pico base station for a pico cell 102b
  • the BS 110c may be a femto base station for a femto cell 102c.
  • a base station may support one or multiple (e.g., three) cells.
  • a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a base station 110 that is mobile (e.g., a mobile base station) .
  • the base stations 110 may be interconnected to one another and/or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as a direct physical connection or a virtual network, using any suitable transport network.
  • the wireless network 100 may include one or more relay stations.
  • a relay station is an entity that can receive a transmission of data from an upstream station (e.g., a base station 110 or a UE 120) and send a transmission of the data to a downstream station (e.g., a UE 120 or a base station 110) .
  • a relay station may be a UE 120 that can relay transmissions for other UEs 120.
  • the BS 110d e.g., a relay base station
  • the BS 110a e.g., a macro base station
  • a base station 110 that relays communications may be referred to as a relay station, a relay base station, a relay, or the like.
  • the wireless network 100 may be a heterogeneous network that includes base stations 110 of different types, such as macro base stations, pico base stations, femto base stations, relay base stations, or the like. These different types of base stations 110 may have different transmit power levels, different coverage areas, and/or different impacts on interference in the wireless network 100.
  • macro base stations may have a high transmit power level (e.g., 5 to 40 watts) whereas pico base stations, femto base stations, and relay base stations may have lower transmit power levels (e.g., 0.1 to 2 watts) .
  • a network controller 130 may couple to or communicate with a set of base stations 110 and may provide coordination and control for these base stations 110.
  • the network controller 130 may communicate with the base stations 110 via a backhaul communication link.
  • the base stations 110 may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link.
  • the UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile.
  • a UE 120 may include, for example, an access terminal, a terminal, a mobile station, and/or a subscriber unit.
  • a UE 120 may be a cellular phone (e.g., a smart phone) , a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet) ) , an entertainment device (e.g., amusic device, a video device, and/or a satellite radio)
  • Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs.
  • An MTC UE and/or an eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, and/or a location tag, that may communicate with a base station, another device (e.g., a remote device) , or some other entity.
  • Some UEs 120 may be considered Internet-of-Things (IoT) devices, and/or may be implemented as NB-IoT (narrowband IoT) devices.
  • Some UEs 120 may be considered a Customer Premises Equipment.
  • a UE 120 may be included inside a housing that houses components of the UE 120, such as processor components and/or memory components.
  • the processor components and the memory components may be coupled together.
  • the processor components e.g., one or more processors
  • the memory components e.g., a memory
  • the processor components and the memory components may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.
  • any number of wireless networks 100 may be deployed in a given geographic area.
  • Each wireless network 100 may support a particular RAT and may operate on one or more frequencies.
  • a RAT may be referred to as a radio technology, an air interface, or the like.
  • a frequency may be referred to as a carrier, a frequency channel, or the like.
  • Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.
  • NR or 5G RAT networks may be deployed.
  • two or more UEs 120 may communicate directly using one or more sidelink channels (e.g., without using a base station 110 as an intermediary to communicate with one another) .
  • the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol) , and/or a mesh network.
  • V2X vehicle-to-everything
  • a UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the base station 110.
  • Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, or the like. For example, devices of the wireless network 100 may communicate using one or more operating bands.
  • devices of the wireless network 100 may communicate using one or more operating bands.
  • two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz) . It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles.
  • FR2 which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz–300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
  • EHF extremely high frequency
  • ITU International Telecommunications Union
  • FR3 7.125 GHz–24.25 GHz
  • FR3 7.125 GHz–24.25 GHz
  • FR3 7.125 GHz–24.25 GHz
  • Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies.
  • higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz.
  • FR4a or FR4-1 52.6 GHz–71 GHz
  • FR4 52.6 GHz–114.25 GHz
  • FR5 114.25 GHz–300 GHz
  • sub-6 GHz may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies.
  • millimeter wave may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band.
  • frequencies included in these operating bands may be modified, and techniques described herein are applicable to those modified frequency ranges.
  • the UE 120 may include a communication manager 140.
  • the communication manager 140 may receive, from the base station 110, an indication of a set of random access occasions that are shared with one or more legacy UEs and that are associated with repetition of a physical uplink shared channel (PUSCH) message. Additionally, the communication manager 140 may transmit a random access preamble within a random access occasion selected from the set. Accordingly, as shown in Fig. 1, the UE 120 may transmit repetitions of the PUSCH message to the base station 110.
  • PUSCH physical uplink shared channel
  • the communication manager 140 may receive, from the base station 110, an indication of a set of random access occasions that is distinct from an additional set of random access occasions associated with one or more legacy UEs, where at least a first subset of the set of random access occasions are associated with repetition of a PUSCH message and a second subset of the set of random access occasions are associated with a reduced capacity (RedCap) identification message. Additionally, the communication manager 140 may transmit a random access preamble within a random access occasion selected from the first subset or the second subset. Accordingly, as shown in Fig. 1, the UE 120 may transmit repetitions of the PUSCH message to the base station 110. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.
  • the base station 110 may include a communication manager 150.
  • the communication manager 150 may transmit, to the UE 120, an indication of a set of random access occasions that are shared with one or more legacy UEs and that are associated with repetition of a PUSCH message. Additionally, the communication manager 150 may receive a random access preamble within a random access occasion selected from the set. Accordingly, as shown in Fig. 1, the base station 110 may receive repetitions of the PUSCH message from the UE 120.
  • the communication manager 150 may transmit, to the UE 120, an indication of a set of random access occasions that is distinct from an additional set of random access occasions associated with one or more legacy UEs, where at least a first subset of the set of random access occasions are associated with repetition of a PUSCH message and a second subset of the set of random access occasions are associated with a RedCap identification message. Additionally, the communication manager 150 may receive a random access preamble within a random access occasion selected from the first subset or the second subset. Accordingly, as shown in Fig. 1, the base station 110 may receive repetitions of the PUSCH message from the UE 120. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.
  • Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.
  • Fig. 2 is a diagram illustrating an example 200 of a base station 110 in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure.
  • the base station 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ⁇ 1) .
  • the UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ⁇ 1) .
  • a transmit processor 220 may receive data, from a data source 212, intended for the UE 120 (or a set ofUEs 120) .
  • the transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120.
  • MCSs modulation and coding schemes
  • CQIs channel quality indicators
  • the base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS (s) selected for the UE 120 and may provide data symbols for the UE 120.
  • the transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI) ) and control information (e.g., CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and control symbols.
  • the transmit processor 220 may generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS) ) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS) ) .
  • reference signals e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)
  • synchronization signals e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)
  • a transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) , shown as modems 232a through 232t.
  • each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232.
  • Each modem 232 may use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream.
  • Each modem 232 may further use a respective modulator component to process (e.g., convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain a downlink signal.
  • the modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) , shown as antennas 234a through 234t.
  • a set of antennas 252 may receive the downlink signals from the base station 110 and/or other base stations 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) , shown as modems 254a through 254r.
  • R received signals e.g., R received signals
  • each received signal may be provided to a demodulator component (shown as DEMOD) of a modem 254.
  • DEMOD demodulator component
  • Each modem 254 may use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and/or digitize) a received signal to obtain input samples.
  • Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols.
  • a MIMO detector 256 may obtain received symbols from the modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols.
  • a receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller/processor 280.
  • controller/processor may refer to one or more controllers, one or more processors, or a combination thereof.
  • a channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and/or a CQI parameter, among other examples.
  • RSRP reference signal received power
  • RSSI received signal strength indicator
  • RSSRQ reference signal received quality
  • CQI CQI parameter
  • the network controller 130 may include a communication unit 294, a controller/processor 290, and a memory 292.
  • the network controller 130 may include, for example, one or more devices in a core network.
  • the network controller 130 may communicate with the base station 110 via the communication unit 294.
  • One or more antennas may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and/or one or more antenna arrays, among other examples.
  • An antenna panel, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements (within a single housing or multiple housings) , a set of coplanar antenna elements, a set of non-coplanar antenna elements, and/or one or more antenna elements coupled to one or more transmission and/or reception components, such as one or more components of Fig. 2.
  • a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports that include RSRP, RSSI, RSRQ, and/or CQI) from the controller/processor 280.
  • the transmit processor 264 may generate reference symbols for one or more reference signals.
  • the symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by the modems 254 (e.g., for DFT-s-OFDM or CP-OFDM) , and transmitted to the base station 110.
  • the modem 254 of the UE 120 may include a modulator and a demodulator.
  • the UE 120 includes a transceiver.
  • the transceiver may include any combination of the antenna (s) 252, the modem (s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and/or the TX MIMO processor 266.
  • the transceiver may be used by a processor (e.g., the controller/processor 280) and the memory 282 to perform aspects of any of the methods described herein (e.g., with reference to Figs. 4-10) .
  • the uplink signals from UE 120 and/or other UEs may be received by the antennas 234, processed by the modem 232 (e.g., a demodulator component, shown as DEMOD, of the modem 232) , detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120.
  • the receive processor 238 may provide the decoded data to a data sink 239 and provide the decoded control information to the controller/processor 240.
  • the base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244.
  • the base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and/or uplink communications.
  • the modem 232 of the base station 110 may include a modulator and a demodulator.
  • the base station 110 includes a transceiver.
  • the transceiver may include any combination of the antenna (s) 234, the modem (s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and/or the TX MIMO processor 230.
  • the transceiver may be used by a processor (e.g., the controller/processor 240) and the memory 242 to perform aspects of any of the methods described herein (e.g., with reference to Figs. 4-10) .
  • the controller/processor 240 of the base station 110, the controller/processor 280 of the UE 120, and/or any other component (s) of Fig. 2 may perform one or more techniques associated with configuring and using random access occasions for repetitions of a PUSCH message, as described in more detail elsewhere herein.
  • the controller/processor 240 of the base station 110, the controller/processor 280 of the UE 120, and/or any other component (s) of Fig. 2 may perform or direct operations of, for example, process 500 of Fig. 5, process 600 of Fig. 6, process 700 of Fig. 7, process 800 of Fig. 8, and/or other processes as described herein.
  • the memory 242 and the memory 282 may store data and program codes for the base station 110 and the UE 120, respectively.
  • the memory 242 and/or the memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication.
  • the one or more instructions when executed (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the base station 110 and/or the UE 120, may cause the one or more processors, the UE 120, and/or the base station 110 to perform or direct operations of, for example, process 500 of Fig. 5, process 600 of Fig. 6, process 700 of Fig. 7, process 800 of Fig. 8, and/or other processes as described herein.
  • executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.
  • a UE may include means for receiving, from a base station (e.g., the base station 110 and/or apparatus 1100 of Fig. 11) , an indication of a set of random access occasions, wherein the set of random access occasions are shared with one or more legacy UEs, and wherein the set of random access occasions are associated with repetition of a PUSCH message; and/or means for transmitting a random access preamble within a random access occasion selected from the set.
  • the means for the UE to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller/processor 280, or memory 282.
  • the UE may include means for receiving, from the base station, an indication of a set of random access occasions, wherein the set of random access occasions is distinct from an additional set of random access occasions associated with one or more legacy UEs, and wherein at least a first subset of the set of random access occasions are associated with repetition of a PUSCH message and a second subset of the set of random access occasions are associated with a RedCap identification message; and/or means for transmitting a random access preamble within a random access occasion selected from the first subset or the second subset.
  • the means for the UE to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller/processor 280, or memory 282.
  • a base station may include means for transmitting, to a UE (e.g., the UE 120 and/or apparatus 1000 of Fig. 10) , an indication of a set of random access occasions, wherein the set of random access occasions are shared with one or more legacy UEs, and wherein the set of random access occasions are associated with repetition of a PUSCH message; and/or means for receiving a random access preamble within a random access occasion selected from the set.
  • the means for the base station to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.
  • the base station may include means for transmitting, to the UE, an indication of a set of random access occasions, wherein the set of random access occasions is distinct from an additional set of random access occasions associated with one or more legacy UEs, and wherein at least a first subset of the set of random access occasions are associated with repetition of a PUSCH message and a second subset of the set of random access occasions are associated with a RedCap identification message; and/or means for receiving a random access preamble within a random access occasion selected from the first subset or the second subset.
  • the means for the base station to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.
  • While blocks in Fig. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components.
  • the functions described with respect to the transmit processor 264, the receive processor 258, and/or the TX MIMO processor 266 may be performed by or under the control of the controller/processor 280.
  • Fig. 2 is provided as an example. Other examples may differ from what is described with regard to Fig. 2.
  • Fig. 3 is a diagram illustrating an example of a four-step random access procedure, in accordance with the present disclosure. As shown in Fig. 3, a base station 110 and a UE 120 may communicate with one another to perform the four-step random access procedure.
  • the base station 110 may transmit, and the UE 120 may receive, one or more synchronization signal blocks (SSBs) and random access configuration information.
  • the random access configuration information may be transmitted in and/or indicated by system information (e.g., in one or more system information blocks (SIBs) ) and/or an SSB, such as for contention-based random access.
  • the random access configuration information may be transmitted in a radio resource control (RRC) message and/or a physical downlink control channel (PDCCH) order message that triggers a random access channel (RACH) procedure, such as for contention-free random access.
  • RRC radio resource control
  • PDCCH physical downlink control channel
  • RACH random access channel
  • the random access configuration information may include one or more parameters to be used in the random access procedure, such as one or more parameters for transmitting a random access message (RAM) and/or one or more parameters for receiving a random access response (RAR) .
  • the UE 120 may transmit a RAM, which may include a preamble (sometimes referred to as a random access preamble, a physical random access channel (PRACH) preamble, or a RAM preamble) .
  • a preamble sometimes referred to as a random access preamble, a physical random access channel (PRACH) preamble, or a RAM preamble
  • the message that includes the preamble may be referred to as a message 1, msg1, MSG1, a first message, or an initial message in a four-step random access procedure.
  • the random access message may include a random access preamble identifier.
  • the base station 110 may transmit an RAR as a reply to the preamble.
  • the message that includes the RAR may be referred to as message 2, msg2, MSG2, or a second message in a four-step random access procedure.
  • the RAR may indicate the detected random access preamble identifier (e.g., received from the UE 120 in msg1) . Additionally, or alternatively, the RAR may indicate a resource allocation to be used by the UE 120 to transmit message 3 (msg3) .
  • the base station 110 may transmit a PDCCH communication for the RAR.
  • the PDCCH communication may schedule a physical downlink shared channel (PDSCH) communication that includes the RAR.
  • the PDCCH communication may indicate a resource allocation for the PDSCH communication.
  • the base station 110 may transmit the PDSCH communication for the RAR, as scheduled by the PDCCH communication.
  • the RAR may be included in a medium access control (MAC) protocol data unit (PDU) of the PDSCH communication.
  • MAC medium access control
  • the UE 120 may transmit an RRC connection request message.
  • the RRC connection request message may be referred to as message 3, msg3, MSG3, or a third message of a four-step random access procedure.
  • the RRC connection request may include a UE identifier, uplink control information (UCI) , and/or a PUSCH communication (e.g., an RRC connection request) .
  • UCI uplink control information
  • PUSCH communication e.g., an RRC connection request
  • the base station 110 may transmit an RRC connection setup message.
  • the RRC connection setup message may be referred to as message 4, msg4, MSG4, or a fourth message of a four-step random access procedure.
  • the RRC connection setup message may include the detected UE identifier, a timing advance value, and/or contention resolution information.
  • the UE 120 may transmit a hybrid automatic repeat request (HARQ) acknowledgement (ACK) if the UE 120 successfully receives the RRC connection setup message.
  • HARQ hybrid automatic repeat request
  • ACK hybrid automatic repeat request acknowledgement
  • msg3 may cause a bottleneck in the RACH procedure.
  • DCI e.g., DCI format 1_0 scrambled using a random access radio network temporary identifier (RA-RNTI)
  • RA-RNTI random access radio network temporary identifier
  • a UE After decoding DCI (e.g., DCI format 1_0 scrambled using a random access radio network temporary identifier (RA-RNTI) ) and receiving the RAR based on the DCI, a UE transmits msg3 to a base station. If the base station does not receive msg3 from the UE, the base station will again transmit DCI (e.g., DCI format 0_0 scrambled using a temporary cell radio network temporary identifier (TC-RNTI) ) to allow the UE to retransmit msg3 to the base station.
  • TC-RNTI temporary cell radio network temporary identifier
  • Some techniques and apparatuses described herein enable a UE (e.g., UE 120) to select a random access occasion associated with repetition of a PUSCH message, such as msg3. Accordingly, the UE 120 can request to repeat the PUSCH message by using that random access occasion, and the base station 110 can approve the request in the RAR (or DCI associated with the RAR) . As a result, the base station 110 need not wait until the PUSCH message is not received and transmit additional DCI in order to allow the UE 120 to repeat the PUSCH message. Accordingly, the base station 110 and the UE 120 experience reduced latency and also conserve power and processing resources.
  • Fig. 3 is provided as an example. Other examples may differ from what is described with regard to Fig. 3.
  • Fig. 4 is a diagram illustrating an example 400 associated with configuring and using random access occasions for repetitions of a PUSCH message, in accordance with the present disclosure.
  • a base station 110 and a UE 120 may communicate with one another (e.g., on a wireless network, such as wireless network 100) .
  • a random access occasion (also referred to as an “RO” ) may include one or more time resources (e.g., a frame, a subframe, a slot, and/or one or more symbols) and one or more frequency resources (e.g., one or more resource blocks (RBs) ) for the UE 120 to use for initiating a RACH procedure with the base station 110 (e.g., by transmitting a random access preamble) .
  • RB may refer to one or more subcarriers (e.g., each subcarrier may include one or more frequencies) , which may be consecutive in a frequency domain.
  • an RB may include a plurality of resource elements (REs) , where each RE corresponds to a single subcarrier.
  • the random access occasion may additionally include one or more spatial resources (e.g., a beam or transmission configuration indicator (TCI) state for the UE 120 to use when transmitting in the random access occasion) .
  • TCI transmission configuration indicator
  • the base station 110 may transmit one or more RRC messages including a prach-ConfigurationIndex data structure and/or an ra-OccasionList data structure (e.g., indicating the set of random access occasions) , optionally with a prach-ConfigurationFrameOffset-IAB data structure and/or a prach-ConfigurationSOffset-IAB data structure (e.g., offsetting the set of random access occasions indicated by prach-ConfigurationIndex in time) .
  • a prach-ConfigurationIndex data structure and/or an ra-OccasionList data structure e.g., indicating the set of random access occasions
  • a prach-ConfigurationFrameOffset-IAB data structure e.g., offsetting the set of random access occasions indicated by prach-ConfigurationIndex in time
  • the base station 110 may transmit one or more RRC messages including parameters associated with relationships between SSBs and the set of random access occasions (e.g., an ssb-perRACH-OccasionAndCB-PreamblesPerSSB data structure indicating a quantity of SSBs mapped to each random access occasion) , random access preambles to use in the set of random access occasions (e.g., an ra-PreambleStartIndex data structure indicating a starting index for random access preambles to use, a preambleTransMax data structure indicating a maximum quantity of random access preamble transmissions, and/or an ssb-perRACH-OccasionAndCB-PreamblesPerSSB data structure indicating a quantity of random access preambles mapped to each SSB) , and/or transmission parameters to use when transmitting in the set of random access occasions (e.g., a powerRampingStep indicating a power ramping factor to use,
  • the set of random access occasions may be associated with repetition of a PUSCH message (e.g., msg3 as described in connection with Fig. 3) .
  • the UE 120 may request to repeat the PUSCH message by initiating a RACH procedure with the base station 110 (e.g., by transmitting a random access preamble as described in connection with reference number 415) within a random access occasion in the set of random access occasions.
  • the set of random access occasions may be shared with one or more legacy UEs.
  • legacy UE refers to a UE that supports an earlier version of one or more standards (e.g., an earlier version of 3GPP specifications and/or another standard) relative to the UE 120 and/or that uses older hardware and/or software relative to the UE 120.
  • the set of random access occasions may be shared with one or more legacy UEs for a 4-step RACH procedure (e.g., as described in connection with Fig. 3) .
  • the set of random access occasions is a subset of a larger set of random access occasions
  • the indication of the set of random access occasions includes an index associated with a mask used to determine the subset of the larger set of random access occasions.
  • the index may map to the mask through a table and/or another similar data structure.
  • Table 1 An example of such a table for when the set of random access occasions are shared with one or more legacy UEs for a 4-step RACH procedure is shown as Table 1 below:
  • an index value of 0 indicates that the UE 120 may use every 4-step random access occasion in the set of random access occasions to request PUSCH repetition.
  • An index value of 1 indicates that the UE 120 may use every 4-step random access occasion associated with PRACH index 1 (e.g., indicated using aprach-ConfigurationIndex data structure) to request PUSCH repetition.
  • An index value of 9 indicates that the UE 120 may use every 4-step random access occasion associated with an even SSB to request PUSCH repetition.
  • An index value of 11 indicates that the UE 120 may use the first two 4-step random access occasions after the start of an odd subframe to request PUSCH repetition.
  • An index value of 14 indicates that the UE 120 may use the third 4-step random access occasion after the start of an even subframe to request PUSCH repetition. Additionally, in some aspects and as shown in example Table 1, one or more index values may be reserved. Although Table 1 is shown with sixteen possible values for the index, other examples may include more values (e.g., seventeen values, eighteen values, and so on) or fewer values (e.g., fifteen values, fourteen values, and so on) .
  • the set of random access occasions may be shared with one or more legacy UEs for a 2-step RACH procedure.
  • the set of random access occasions may be a subset of a larger set of random access occasions, such that the indication of the set of random access occasions includes an index associated with a mask used to determine the subset of the larger set of random access occasions.
  • the index may map to the mask through a table and/or another similar data structure.
  • Table 2 An example of such a table for when the set of random access occasions are shared with one or more legacy UEs for a 2-step RACH procedure is shown as Table 2 below:
  • an index value of 0 indicates that the UE 120 may use every 2-step random access occasion in the set of random access occasions to request PUSCH repetition.
  • An index value of 1 indicates that the UE 120 may use every 2-step random access occasion associated with PRACH index 1 (e.g., indicated using aprach-ConfigurationIndex data structure) to request PUSCH repetition.
  • An index value of 9 indicates that the UE 120 may use every 2-step random access occasion associated with an even SSB to request PUSCH repetition.
  • An index value of 11 indicates that the UE 120 may use the first two 2-step random access occasions after the start of an odd subframe to request PUSCH repetition.
  • An index value of 14 indicates that the UE 120 may use the third 2-step random access occasion after the start of an even subframe to request PUSCH repetition. Additionally, in some aspects and as shown in example Table 2, one or more index values may be reserved. Although Table 2 is shown with sixteen possible values for the index, other examples may include more values (e.g., seventeen values, eighteen values, and so on) or fewer values (e.g., fifteen values, fourteen values, and so on) .
  • a common table may be used to map to the mask when the set of random access occasions are shared with one or more legacy UEs for a 2-step RACH procedure and when the set of random access occasions are shared with one or more legacy UEs for a 4-step RACH procedure.
  • An example of such a table is shown as Table 3 below:
  • an index value of 0 indicates that the UE 120 may use every random access occasion in the set of random access occasions to request PUSCH repetition.
  • An index value of 1 indicates that the UE 120 may use every random access occasion associated with PRACH index 1 (e.g., indicated using a prach-ConfigurationIndex data structure) to request PUSCH repetition.
  • An index value of 9 indicates that the UE 120 may use every random access occasion associated with an even SSB to request PUSCH repetition.
  • An index value of 11 indicates that the UE 120 may use every 2-step random access occasion in the set of random access occasions to request PUSCH repetition.
  • An index value of 12 indicates that the UE 120 may use every 2-step random access occasion associated with PRACH index 1 (e.g., indicated using aprach-ConfigurationIndex data structure) to request PUSCH repetition.
  • An index value of 14 indicates that the UE 120 may use every 2-step random access occasion associated with an even SSB to request PUSCH repetition. Additionally, in some aspects, one or more index values may be reserved.
  • Table 3 is shown with sixteen possible values for the index, other examples may include more values (e.g., seventeen values, eighteen values, and so on) or fewer values (e.g., fifteen values, fourteen values, and so on) .
  • the set of random access occasions may be shared with one or more legacy UEs for both a 4-step RACH procedure and a 2-step RACH procedure.
  • the set of random access occasions may be a subset of a larger set of random access occasions, such that the indication of the set of random access occasions includes an index associated with a mask used to determine the subset of the larger set of random access occasions.
  • the index may map to the mask through a table and/or another similar data structure.
  • Table 4 An example of such a table for when the set of random access occasions are shared with one or more legacy UEs for both a 4-step RACH procedure and a 2-step RACH procedure is shown as Table 4 below:
  • an index value of 0 indicates that the UE 120 may use every random access occasion in the set of random access occasions to request PUSCH repetition.
  • An index value of 1 indicates that the UE 120 may use every random access occasion associated with PRACH index 1 (e.g., indicated using a prach-ConfigurationIndex data structure) to request PUSCH repetition.
  • An index value of 9 indicates that the UE 120 may use every random access occasion associated with an even SSB to request PUSCH repetition.
  • An index value of 11 indicates that the UE 120 may use the first two random access occasions after the start of an odd subframe to request PUSCH repetition.
  • An index value of 14 indicates that the UE 120 may use the third random access occasion after the start of an even subframe to request PUSCH repetition.
  • one or more index values may be reserved.
  • Table 4 is shown with sixteen possible values for the index, other examples may include more values (e.g., seventeen values, eighteen values, and so on) or fewer values (e.g., fifteen values, fourteen values, and so on) .
  • a common table may be used to map to the mask when the set of random access occasions are shared with one or more legacy UEs for a 2-step RACH procedure, for a 4-step RACH procedure, or for both a 2-step RACH procedure and a 4-step RACH procedure.
  • An example of such a table is shown as Table 5 below:
  • an index value of 0 indicates that the UE 120 may use every 4-step random access occasion in the set of random access occasions to request PUSCH repetition.
  • an index value of 3 indicates that the UE 120 may use every 2-step random access occasion in the set of random access occasions to request PUSCH repetition, and an index value of 6 indicates that the UE 120 may use every random access occasion in the set of random access occasions to request PUSCH repetition.
  • An index value of 1 indicates that the UE 120 may use every 4-step random access occasion associated with an even SSB to request PUSCH repetition.
  • an index value of 4 indicates that the UE 120 may use every 2-step random access occasion associated with an even SSB to request PUSCH repetition
  • an index value of 7 indicates that the UE 120 may use every random access occasion associated with an even SSB to request PUSCH repetition.
  • one or more index values may be reserved.
  • Table 5 is shown with sixteen possible values for the index, other examples may include more values (e.g., seventeen values, eighteen values, and so on) or fewer values (e.g., fifteen values, fourteen values, and so on) .
  • the UE 120 and the base station 110 may use Table 7.4-1 from 3GPP Technical Specification (TS) 38.321 to map to the mask.
  • Table 7.4-1 may be modified as shown below in example Table 6:
  • an index value of 11 indicates that the UE 120 may use every 4-step random access occasion, in the set of random access occasions, both for a 2-step RACH procedure and to request PUSCH repetition.
  • an index value of 12 indicates that the UE 120 may use every 4-step random access occasion, associated with an even SSB, both for a 2-step RACH procedure and to request PUSCH repetition.
  • one or more index values may be reserved.
  • Table 6 is shown with sixteen possible values for the index, other examples may include more values (e.g., seventeen values, eighteen values, and so on) or fewer values (e.g., fifteen values, fourteen values, and so on) .
  • the tables described above may be programmed (and/or otherwise preconfigured) into the UE 120 and the base station 110 (e.g., according to 3GPP specifications and/or another standard) . Additionally, or alternatively, the base station 110 may transmit, and the UE 120 may receive, the table to use (e.g., in SIB and/or an RRC message) . In a combinatory example, the base station 110 may transmit, and the UE 120 may receive, an indication of which table to use from a plurality of tables that are programmed (and/or otherwise preconfigured) into the UE 120 and the base station 110(e.g., according to 3GPP specifications and/or another standard) .
  • the set of random access occasions is distinct from an additional set of random access occasions associated with one or more legacy UEs.
  • the base station 110 may transmit one or more different RRC messages (e.g., with different data structures, as described above) that indicate the set of random access occasions from the RRC messages transmitted to legacy UEs that indicate the additional set of random access occasions.
  • at least a first subset of the set of random access occasions are associated with repetition of a PUSCH message (e.g., msg3 as described in connection with Fig. 3) and a second subset of the set of random access occasions are associated with a RedCap identification message.
  • a PUSCH message e.g., msg3 as described in connection with Fig. 3
  • the first subset may include random access occasions 501a, 501b, 501c, 501d, and 501e
  • the second subset may include random access occasions 503a, 503b, 503c, 503d, and 503e.
  • the UE 120 may request to repeat the PUSCH message by initiating a RACH procedure with the base station 110 (e.g., by transmitting a random access preamble as described in connection with reference number 415) within a random access occasion in the first subset, and the UE 120 may identify itself as a RedCap UE by initiating a RACH procedure with the base station 110 (e.g., by transmitting a random access preamble as described in connection with reference number 415) within a random access occasion in the second subset.
  • a third subset of the set of random access occasions may be associated both with repetition of the PUSCH message and with the RedCap identification message. For example, as shown in Fig.
  • the first subset may include random access occasions 551a, 551b, and 551c
  • the second subset may include random access occasions 553a, 553b, and 553c
  • the third subset may include random access occasions 555a, 555b, and 555c.
  • RedCap UE may refer to a UE that operates using fewer antennas (e.g., fewer Rx antennas) and/or reduced bandwidth (e.g., operating in a 5-20 MHz range rather than a 100 MHz bandwidth) in order to conserve battery power.
  • Such UEs may include smart devices (such as smart watches and/or fitness trackers, among other examples) , industrial sensors, and/or video surveillance devices, among other examples.
  • the indication of the set of random access occasions may include one or more indices associated with one or more masks used to determine the first subset and the second subset.
  • a first index may map (e.g., using a table and/or another data structure, as described above) to a first mask that selects the first subset of random access occasions from the set of random access occasions.
  • the first subset of random access occasions may include remaining random access occasions that are not within the second subset.
  • a second index may map(e.g., using a table and/or another data structure, as described above) to a second mask that selects the second subset of random access occasions from the set of random access occasions.
  • the second subset of random access occasions may include remaining random access occasions that are not within the first subset.
  • the table and/or other data structure may provide a mask that indicates both the first subset and the second subset with only one index value.
  • a third index may map (e.g., using a table and/or another data structure, as described above) to a third mask that selects the third subset of random access occasions from the set of random access occasions.
  • the third subset of random access occasions may include remaining random access occasions that are not within the first subset or the second subset.
  • the table and/or other data structure may provide a mask that indicates the first subset, the second subset, and the third subset with only one index value.
  • the UE 120 may select a random access occasion to use. For example, the UE 120 may select a random access occasion from the first subset in order to indicate a request for repetition of the PUSCH message. As an alternative, the UE 120 may select a random access occasion from the second subset in order to identify itself as a RedCap UE. In aspects where the set of random access occasions are divided into the first subset, the second subset, and the third subset, the UE 120 may select a random access occasion from the third subset in order to indicate a request for repetition of the PUSCH message and to identify itself as a RedCap UE.
  • the UE 120 may additionally select a random access preamble to use.
  • the selected random access preamble may indicate when the UE 120 is requesting repetition of the PUSCH message and is identifying itself as a RedCap UE.
  • the UE 120 may transmit, in an occasion from the first subset of random access occasions, a random access preamble selected from a first set of random access preambles to indicate that the UE 120 is requesting repetition of the PUSCH message and is identifying itself as a RedCap UE; on the other hand, the UE 120 may transmit, in an occasion from the first subset of random access occasions, a random access preamble selected from a second set of random access preambles to indicate that the UE 120 is requesting repetition of the PUSCH message and is not identifying itself as a RedCap UE.
  • the UE 120 may transmit, in an occasion from the second subset of random access occasions, a random access preamble selected from a first set of random access preambles to indicate that the UE 120 is requesting repetition of the PUSCH message and is identifying itself as a RedCap UE; on the other hand, the UE 120 may transmit, in an occasion from the second subset of random access occasions, a random access preamble selected from a second set of random access preambles to indicate that the UE 120 is not requesting repetition of the PUSCH message and is identifying itself as a RedCap UE.
  • the UE 120 may select any random access preamble configured for the set of random access occasions.
  • the selected random access preamble may indicate when the UE 120 is requesting repetition of the PUSCH message.
  • the UE 120 may transmit, in an occasion from the set of random access occasions, a random access preamble selected from a first set of random access preambles to indicate that the UE 120 is requesting repetition of the PUSCH message; on the other hand, the UE 120 may transmit, in an occasion from the set of random access occasions, a random access preamble selected from a second set of random access preambles to indicate that the UE 120 is not requesting repetition of the PUSCH message.
  • the UE 120 may transmit, and the base station 110 may receive, a random access preamble within the selected random access occasion (e.g., selected as described in connection with reference number 410) .
  • the random access preamble may be selected as described in connection with reference number 410.
  • the base station 110 may transmit, and the UE 120 may receive, a random access response.
  • the random access response may include DCI and a corresponding PDSCH message.
  • the response may approve the request for repetition of the PUSCH message from the UE 120.
  • the random access response may indicate a plurality of uplink resources (e.g., in time, frequency, and/or space) in which the UE 120 may transmit repetitions of the PUSCH message (e.g., msg3 as described in connection with Fig. 3) .
  • the UE 120 may transmit, and the base station 110 may receive, a PUSCH message.
  • the UE 120 may transmit msg3 as described in connection with Fig. 3.
  • the UE 120 may transmit, and the base station 110 may receive, a repetition of the PUSCH message.
  • the UE 120 may transmit a repetition of msg3 as described in connection with Fig. 3.
  • the UE 120 may transmit two or more repetitions of the PUSCH message. Although two repetitions are depicted in Fig. 4, the description similarly applies to additional repetitions (e.g., three repetitions, four repetitions, and so on) .
  • the base station 110 may indicate a quantity of repetitions (e.g., in the RAR as described in connection with reference number 420) such that the UE 120 transmits the indicated quantity of repetitions of the PUSCH message.
  • the base station 110 may indicate a maximum quantity of repetitions (e.g., in the RAR as described in connection with reference number 420) such that the UE 120 transmits repetitions of the PUSCH message until the UE 120 receives an acknowledgement (e.g., a HARQ ACK) and/or an additional message (e.g., msg4 as described in connection with Fig. 3) from the base station 110 or until the UE 120 has transmitted the maximum quantity of repetitions of the PUSCH message.
  • an acknowledgement e.g., a HARQ ACK
  • an additional message e.g., msg4 as described in connection with Fig.
  • the UE 120 can select a random access occasion associated with repetition of the PUSCH message. Accordingly, the UE 120 can request to repeat the PUSCH message by using that random access occasion, and the base station 110 can approve the request in the RAR. As a result, the base station 110 need not wait until the PUSCH message is not received and transmit additional DCI in order to allow the UE 120 to repeat the PUSCH message. Accordingly, the base station 110 and the UE 120 experience reduced latency and also conserve power and processing resources.
  • Fig. 4 is provided as an example. Other examples may differ from what is described with respect to Fig. 4.
  • Fig. 5A is a diagram illustrating an example 500 associated with random access occasions for repetitions of a PUSCH message.
  • example 500 includes a first subset of a set of random access occasions that includes occasions 501a, 501b, 501c, 501d, and 501e and that is associated with repetition of a PUSCH message (e.g., msg3 as described in connection with Fig. 3) and a second subset of the set of random access occasions that includes occasions 503a, 503b, 503c, 503d, and 503e and that is associated with a RedCap identification message.
  • the set of random access occasions may repeat in time according to a periodicity 505. Accordingly, the first subset and the second subset may include additional random access occasions in time based on the periodicity 505.
  • a UE may select a random access occasion from the first subset in order to indicate a request for repetition of the PUSCH message, or may select a random access occasion from the second subset in order to identify itself as a RedCap UE.
  • the UE 120 may select a random access preamble to indicate the combination.
  • the UE 120 may transmit, in an occasion from the first subset, a random access preamble selected from a first set of random access preambles to indicate that the UE 120 is requesting repetition of the PUSCH message and is identifying itself as a RedCap UE; on the other hand, the UE 120 may transmit, in an occasion from the first subset, a random access preamble selected from a second set of random access preambles to indicate that the UE 120 is requesting repetition of the PUSCH message and is not identifying itself as a RedCap UE.
  • the UE 120 may transmit, in an occasion from the second subset, a random access preamble selected from a first set of random access preambles to indicate that the UE 120 is requesting repetition of the PUSCH message and is identifying itself as a RedCap UE; on the other hand, the UE 120 may transmit, in an occasion from the second subset, arandom access preamble selected from a second set of random access preambles to indicate that the UE 120 is not requesting repetition of the PUSCH message and is identifying itself as a RedCap UE.
  • Fig. 5B is a diagram illustrating an example 550 associated with random access occasions for repetitions of a PUSCH message.
  • example 550 includes a first subset of a set of random access occasions that includes occasions 551a, 551b, and 551c and that is associated with repetition of a PUSCH message (e.g., msg3 as described in connection with Fig.
  • the set of random access occasions may repeat in time according to a periodicity 557. Accordingly, the first subset, the second subset, and the third subset may include additional random access occasions in time based on the periodicity 557.
  • a UE may select a random access occasion from the first subset in order to indicate a request for repetition of the PUSCH message, may select a random access occasion from the second subset in order to identify itself as a RedCap UE, or may select a random access occasion from the third subset in order to request for repetition of the PUSCH message and also identify itself as a RedCap UE.
  • Figs. 5A and 5B are provided as examples. Other examples may differ from what is described with respect to Figs. 5A and 5B.
  • Fig. 6 is a diagram illustrating an example process 600 performed, for example, by a UE, in accordance with the present disclosure.
  • Example process 600 is an example where the UE (e.g., UE 120 and/or apparatus 1000 of Fig. 10) performs operations associated with using random access occasions for repetition of a PUSCH message.
  • the UE e.g., UE 120 and/or apparatus 1000 of Fig. 10.
  • process 600 may include receiving, from a base station (e.g., base station 110 and/or apparatus 1100 of Fig. 11) , an indication of a set of random access occasions (block 610) .
  • the UE e.g., using communication manager 140 and/or reception component 1002, depicted in Fig. 10) may receive, from a base station, an indication of a set of random access occasions, as described herein.
  • the set of random access occasions are shared with one or more legacy UEs, and the set of random access occasions are associated with repetition of a PUSCH message.
  • process 600 may include transmitting a random access preamble within a random access occasion selected from the set (block 620) .
  • the UE e.g., using communication manager 140 and/or transmission component 1004, depicted in Fig. 10
  • Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • the random access preamble indicates a request for repetition of the PUSCH message.
  • process 600 further includes receiving (e.g., using communication manager 140 and/or reception component 1002) a response that approves the request for repetition of the PUSCH message, and transmitting (e.g., using communication manager 140 and/or transmission component 1004) two or more repetitions of the PUSCH message.
  • the set of random access occasions are shared with one or more legacy UEs for a 4-step random access procedure, a 2-step random access procedure, or a combination thereof.
  • the set of random access occasions is a subset of a larger set of random access occasions
  • the indication of the set of random access occasions includes an index associated with a mask used to determine the subset of the larger set of random access occasions
  • the index is associated with a table stored on the UE.
  • process 600 further includes receiving (e.g., using communication manager 140 and/or reception component 1002) a table relating different indices to different masks, where the index is associated with the table.
  • the table is received in an SIB or an RRC message.
  • process 600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 6. Additionally, or alternatively, two or more of the blocks of process 600 may be performed in parallel.
  • Fig. 7 is a diagram illustrating an example process 700 performed, for example, by a base station, in accordance with the present disclosure.
  • Example process 700 is an example where the base station (e.g., base station 110 and/or apparatus 1100 of Fig. 11) performs operations associated with configuring random access occasions for repetition of a PUSCH message.
  • the base station e.g., base station 110 and/or apparatus 1100 of Fig. 11
  • process 700 may include transmitting, to a UE (e.g., UE 120 and/or apparatus 1000 of Fig. 10) , an indication of a set of random access occasions (block 710) .
  • the base station e.g., using communication manager 150 and/or transmission component 1104, depicted in Fig. 11
  • the set of random access occasions are shared with one or more legacy UEs, and the set of random access occasions are associated with repetition of a PUSCH message.
  • process 700 may include receiving a random access preamble within a random access occasion selected from the set(block 720) .
  • the base station e.g., using communication manager 150 and/or reception component 1102, depicted in Fig. 11
  • Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • the random access preamble indicates a request for repetition of the PUSCH message.
  • process 700 further includes transmitting (e.g., using communication manager 150 and/or transmission component 1104) a response that approves the request for repetition of the PUSCH message, and receiving (e.g., using communication manager 150 and/or reception component 1102) two or more repetitions of the PUSCH message.
  • the set of random access occasions are shared with one or more legacy UEs for a 4-step random access procedure, a 2-step random access procedure, or a combination thereof.
  • the set of random access occasions is a subset of a larger set of random access occasions
  • the indication of the set of random access occasions includes an index associated with a mask used to determine the subset of the larger set of random access occasions
  • the index is associated with a table stored on the base station.
  • process 700 further includes transmitting (e.g., using communication manager 150 and/or transmission component 1104) a table relating different indices to different masks, where the index is associated with the table.
  • the table is transmitted in an SIB or an RRC message.
  • process 700 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 7. Additionally, or alternatively, two or more of the blocks of process 700 may be performed in parallel.
  • Fig. 8 is a diagram illustrating an example process 800 performed, for example, by a UE, in accordance with the present disclosure.
  • Example process 800 is an example where the UE (e.g., UE 120 and/or apparatus 1000 of Fig. 10) performs operations associated with using random access occasions for repetition of a PUSCH message.
  • the UE e.g., UE 120 and/or apparatus 1000 of Fig. 10.
  • process 800 may include receiving, from a base station (e.g., base station 110 and/or apparatus 1100 of Fig. 11) , an indication of a set of random access occasions (block 810) .
  • a base station e.g., base station 110 and/or apparatus 1100 of Fig. 11
  • the UE e.g., using communication manager 140 and/or reception component 1002, depicted in Fig. 10) may receive, from a base station, an indication of a set of random access occasions, as described herein.
  • the set of random access occasions is distinct from an additional set of random access occasions associated with one or more legacy UEs, and at least a first subset of the set of random access occasions are associated with repetition of a PUSCH message and a second subset of the set of random access occasions are associated with a RedCap identification message.
  • process 800 may include transmitting a random access preamble within a random access occasion selected from the first subset or the second subset (block 820) .
  • the UE e.g., using communication manager 140 and/or transmission component 1004, depicted in Fig. 10
  • Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • the selected random access occasion indicates one of a request for repetition of the PUSCH message or a RedCap identification.
  • the random access preamble indicates the other of the request for repetition of the PUSCH message or the RedCap identification.
  • process 800 further includes receiving (e.g., using communication manager 140 and/or reception component 1002) a response that approves the request for repetition of the PUSCH message, and transmitting (e.g., using communication manager 140 and/or transmission component 1004) two or more repetitions of the PUSCH message.
  • a third subset of the set of random access occasions are associated with repetition of the PUSCH message and with the RedCap identification message.
  • the selected random access occasion indicates a request for repetition of the PUSCH message, a RedCap identification, or a combination thereof.
  • the indication of the set of random access occasions includes one or more indices associated with one or more masks used to determine the first subset and the second subset.
  • process 800 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 8. Additionally, or alternatively, two or more of the blocks of process 800 may be performed in parallel.
  • Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a base station, in accordance with the present disclosure.
  • Example process 900 is an example where the base station (e.g., base station 110 and/or apparatus 1100 of Fig. 11) performs operations associated with configuring random access occasions for repetition of a PUSCH message.
  • the base station e.g., base station 110 and/or apparatus 1100 of Fig. 11
  • process 900 may include transmitting, to a UE (e.g., UE 120 and/or apparatus 1000 of Fig. 10) , an indication of a set of random access occasions (block 910) .
  • a UE e.g., UE 120 and/or apparatus 1000 of Fig. 10.
  • the base station e.g., using communication manager 150 and/or transmission component 1104, depicted in Fig. 11
  • the set of random access occasions is distinct from an additional set of random access occasions associated with one or more legacy UEs, and at least a first subset of the set of random access occasions are associated with repetition of a PUSCH message and a second subset of the set of random access occasions are associated with a RedCap identification message.
  • process 900 may include receiving a random access preamble within a random access occasion selected from the first subset or the second subset (block 920) .
  • the base station e.g., using communication manager 150 and/or reception component 1102, depicted in Fig. 11
  • Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • the selected random access occasion indicates one of a request for repetition of the PUSCH message or a RedCap identification.
  • the random access preamble indicates the other of the request for repetition of the PUSCH message or the RedCap identification.
  • process 900 further includes transmitting (e.g., using communication manager 150 and/or transmission component 1104) a response that approves the request for repetition of the PUSCH message, and receiving (e.g., using communication manager 150 and/or reception component 1102) two or more repetitions of the PUSCH message.
  • a third subset of the set of random access occasions are associated with repetition of the PUSCH message and with the RedCap identification message.
  • the selected random access occasion indicates a request for repetition of the PUSCH message, a RedCap identification, or a combination thereof.
  • the indication of the set of random access occasions includes one or more indices associated with one or more masks used to determine the first subset and the second subset.
  • process 900 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 9. Additionally, or alternatively, two or more of the blocks of process 900 may be performed in parallel.
  • Fig. 10 is a diagram of an example apparatus 1000 for wireless communication.
  • the apparatus 1000 may be a UE, or a UE may include the apparatus 1000.
  • the apparatus 1000 includes a reception component 1002 and a transmission component 1004, which may be in communication with one another (for example, via one or more buses and/or one or more other components) .
  • the apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device) using the reception component 1002 and the transmission component 1004.
  • the apparatus 1000 may include the communication manager 140.
  • the communication manager 140 may include one or more of a selection component 1008 and/or a determination component 1010, among other examples.
  • the apparatus 1000 may be configured to perform one or more operations described herein in connection with Fig. 4. Additionally, or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as process 600 of Fig. 6, process 800 of Fig. 8, or a combination thereof.
  • the apparatus 1000 and/or one or more components shown in Fig. 10 may include one or more components of the UE described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 10 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.
  • the reception component 1002 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1006.
  • the reception component 1002 may provide received communications to one or more other components of the apparatus 1000.
  • the reception component 1002 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , and may provide the processed signals to the one or more other components of the apparatus 1006.
  • the reception component 1002 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2.
  • the transmission component 1004 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1006.
  • one or more other components of the apparatus 1006 may generate communications and may provide the generated communications to the transmission component 1004 for transmission to the apparatus 1006.
  • the transmission component 1004 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) , and may transmit the processed signals to the apparatus 1006.
  • the transmission component 1004 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, amemory, or a combination thereof, of the UE described in connection with Fig. 2. In some aspects, the transmission component 1004 may be co-located with the reception component 1002 in a transceiver.
  • the reception component 1002 may receive (e.g., from the apparatus 1006) an indication of a set of random access occasions.
  • the set of random access occasions may be shared with one or more legacy UEs associated with repetition of a PUSCH message.
  • the transmission component 1004 may transmit a random access preamble within a random access occasion selected from the set.
  • the selection component 1008 may select the random access occasion to use based at least in part on the apparatus 1000 requesting repetition of the PUSCH message. Additionally, or alternatively, the selection component 1008 may select a random access preamble to transmit based at least in part on the apparatus 1000 requesting repetition of the PUSCH message.
  • the selection component 1008 may include a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2.
  • the reception component 1002 may receive a response that approves the request for repetition of the PUSCH message. Accordingly, the transmission component 1004 may transmit two or more repetitions of the PUSCH message.
  • the reception component 1002 may receive a table relating different indices to different masks. Additionally, or alternatively, the apparatus 1000 may store a table relating different indices to different masks. Accordingly, the determination component 1010 may determine the set of random access occasions based at least in part on an index included in the indication.
  • the determination component 1010 may include a receive processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with Fig. 2.
  • the set of random access occasions may be distinct from an additional set of random access occasions associated with one or more legacy UEs. Accordingly, at least a first subset of the set of random access occasions may be associated with repetition of a PUSCH message, and a second subset of the set of random access occasions may be associated with a RedCap identification message.
  • the transmission component 1004 may transmit a random access preamble within a random access occasion selected from the first subset or the second subset.
  • the selection component 1008 may select the random access occasion to use based at least in part on the apparatus 1000 requesting repetition of the PUSCH message and/or identifying itself as a RedCap UE. Additionally, or alternatively, the selection component 1008 may select a random access preamble to transmit based at least in part on the apparatus 1000 requesting repetition of the PUSCH message and/or identifying itself as a RedCap UE.
  • the reception component 1002 may receive a response that approves the request for repetition of the PUSCH message. Accordingly, the transmission component 1004 may transmit two or more repetitions of the PUSCH message.
  • Fig. 10 The number and arrangement of components shown in Fig. 10 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 10. Furthermore, two or more components shown in Fig. 10 may be implemented within a single component, or a single component shown in Fig. 10 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 10 may perform one or more functions described as being performed by another set of components shown in Fig. 10.
  • Fig. 11 is a diagram of an example apparatus 1100 for wireless communication.
  • the apparatus 1100 may be a base station, or a base station may include the apparatus 1100.
  • the apparatus 1100 includes a reception component 1102 and a transmission component 1104, which may be in communication with one another (for example, via one or more buses and/or one or more other components) .
  • the apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using the reception component 1102 and the transmission component 1104.
  • the apparatus 1100 may include the communication manager 150.
  • the communication manager 150 may include an allocation component 1108, among other examples.
  • the apparatus 1100 may be configured to perform one or more operations described herein in connection with Fig. 4. Additionally, or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as process 600 of Fig. 6, process 800 of Fig. 8, or a combination thereof.
  • the apparatus 1100 and/or one or more components shown in Fig. 11 may include one or more components of the base station described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 11 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, acomponent (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.
  • the reception component 1102 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1106.
  • the reception component 1102 may provide received communications to one or more other components of the apparatus 1100.
  • the reception component 1102 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , and may provide the processed signals to the one or more other components of the apparatus 1106.
  • the reception component 1102 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the base station described in connection with Fig. 2.
  • the transmission component 1104 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1106.
  • one or more other components of the apparatus 1106 may generate communications and may provide the generated communications to the transmission component 1104 for transmission to the apparatus 1106.
  • the transmission component 1104 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) , and may transmit the processed signals to the apparatus 1106.
  • the transmission component 1104 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the base station described in connection with Fig. 2. In some aspects, the transmission component 1104 may be co-located with the reception component 1102 in a transceiver.
  • the transmission component 1104 may transmit (e.g., to the apparatus 1106) an indication of a set of random access occasions.
  • the set of random access occasions may be shared with one or more legacy UEs and associated with repetition of a PUSCH message.
  • the allocation component 1108 may determine to allocate the set of random access occasions to both the apparatus 1106 and the one or more legacy UEs.
  • the allocation component 1108 may include a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the base station described in connection with Fig. 2. Accordingly, the reception component 1102 may receive a random access preamble within a random access occasion selected from the set.
  • the transmission component 1104 may transmit a response that approves the request for repetition of the PUSCH message. Accordingly, the reception component 1102 may receive two or more repetitions of the PUSCH message.
  • the transmission component 1104 may transmit a table relating different indices to different masks. Additionally, or alternatively, the apparatus 1100 may store a table relating different indices to different masks. Accordingly, the indication may include an index corresponding to a mask for the set of random access occasions that are determined by the allocation component 1108.
  • the set of random access occasions may be distinct from an additional set of random access occasions associated with one or more legacy UEs. Accordingly, at least a first subset of the set of random access occasions may be associated with repetition of a PUSCH message and a second subset of the set of random access occasions may be associated with a RedCap identification message.
  • the allocation component 1108 may determine to allocate the set of random access occasions to the apparatus 1106 and the additional set of random access occasions to the one or more legacy UEs. Accordingly, the reception component 1102 may receive a random access preamble within a random access occasion selected from the first subset or the second subset.
  • the transmission component 1104 may transmit a response that approves the request for repetition of the PUSCH message. Accordingly, the reception component 1102 may receive two or more repetitions of the PUSCH message.
  • Fig. 11 The number and arrangement of components shown in Fig. 11 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 11. Furthermore, two or more components shown in Fig. 11 may be implemented within a single component, or a single component shown in Fig. 11 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 11 may perform one or more functions described as being performed by another set of components shown in Fig. 11.
  • a method of wireless communication performed by a user equipment (UE) comprising: receiving, from a base station, an indication of a set of random access occasions, wherein the set of random access occasions are shared with one or more legacy UEs, and wherein the set of random access occasions are associated with repetition of a physical uplink shared channel (PUSCH) message; and transmitting a random access preamble within a random access occasion selected from the set.
  • UE user equipment
  • Aspect 2 The method of Aspect 1, wherein the random access preamble indicates a request for repetition of the PUSCH message.
  • Aspect 3 The method of Aspect 2, further comprising: receiving a response that approves the request for repetition of the PUSCH message; and transmitting two or more repetitions of the PUSCH message.
  • Aspect 4 The method of any of Aspects 1 through 3, wherein the set of random access occasions are shared with one or more legacy UEs for a 4-step random access procedure, a 2-step random access procedure, or a combination thereof.
  • Aspect 5 The method of any of Aspects 1 through 4, wherein the set of random access occasions is a subset of a larger set of random access occasions, and the indication of the set of random access occasions includes an index associated with a mask used to determine the subset of the larger set of random access occasions.
  • Aspect 6 The method of Aspect 5, wherein the index is associated with a table stored on the UE.
  • Aspect 7 The method of any of Aspects 5 through 6, further comprising: receiving a table relating different indices to different masks, wherein the index is associated with the table.
  • Aspect 8 The method of Aspect 7, wherein the table is received in a system information block (SIB) or a radio resource control (RRC) message.
  • SIB system information block
  • RRC radio resource control
  • a method of wireless communication performed by a base station comprising: transmitting, to a user equipment (UE) , an indication of a set of random access occasions, wherein the set of random access occasions are shared with one or more legacy UEs, and wherein the set of random access occasions are associated with repetition of a physical uplink shared channel (PUSCH) message; and receiving a random access preamble within a random access occasion selected from the set.
  • UE user equipment
  • Aspect 10 The method of Aspect 9, wherein the random access preamble indicates a request for repetition of the PUSCH message.
  • Aspect 11 The method of Aspect 10, further comprising: transmitting a response that approves the request for repetition of the PUSCH message; and receiving two or more repetitions of the PUSCH message.
  • Aspect 12 The method of any of Aspects 9 through 11, wherein the set of random access occasions are shared with one or more legacy UEs for a 4-step random access procedure, a 2-step random access procedure, or a combination thereof.
  • Aspect 13 The method of any of Aspects 9 through 12, wherein the set of random access occasions is a subset of a larger set of random access occasions, and the indication of the set of random access occasions includes an index associated with a mask used to determine the subset of the larger set of random access occasions.
  • Aspect 14 The method of Aspect 13, wherein the index is associated with a table stored on the base station.
  • Aspect 15 The method of any of Aspects 13 through 14, further comprising: transmitting a table relating different indices to different masks, wherein the index is associated with the table.
  • Aspect 16 The method of Aspect 15, wherein the table is transmitted in a system information block (SIB) or a radio resource control (RRC) message.
  • SIB system information block
  • RRC radio resource control
  • a method of wireless communication performed by a user equipment (UE) comprising: receiving, from a base station, an indication of a set of random access occasions, wherein the set of random access occasions is distinct from an additional set of random access occasions associated with one or more legacy UEs, and wherein at least a first subset of the set of random access occasions are associated with repetition of a physical uplink shared channel (PUSCH) message and a second subset of the set of random access occasions are associated with a reduced capacity (RedCap) identification message; and transmitting a random access preamble within a random access occasion selected from the first subset or the second subset.
  • PUSCH physical uplink shared channel
  • RedCap reduced capacity
  • Aspect 18 The method of Aspect 17, wherein the selected random access occasion indicates one of a request for repetition of the PUSCH message or a RedCap identification.
  • Aspect 19 The method of Aspect 18, wherein the random access preamble indicates the other of the request for repetition of the PUSCH message or the RedCap identification.
  • Aspect 20 The method of any of Aspects 18 through 19, further comprising: receiving a response that approves the request for repetition of the PUSCH message; and transmitting two or more repetitions of the PUSCH message.
  • Aspect 21 The method of Aspect 17, wherein a third subset of the set of random access occasions are associated with repetition of the PUSCH message and with the RedCap identification message.
  • Aspect 22 The method of Aspect 21, wherein the selected random access occasion indicates a request for repetition of the PUSCH message, a RedCap identification, or a combination thereof.
  • Aspect 23 The method of any of Aspects 17 through 22, wherein the indication of the set of random access occasions includes one or more indices associated with one or more masks used to determine the first subset and the second subset.
  • a method of wireless communication performed by a base station comprising: transmitting, to a user equipment (UE) , an indication of a set of random access occasions, wherein the set of random access occasions is distinct from an additional set of random access occasions associated with one or more legacy UEs, and wherein at least a first subset of the set of random access occasions are associated with repetition of a physical uplink shared channel (PUSCH) message and a second subset of the set of random access occasions are associated with a reduced capacity (RedCap) identification message; and receiving a random access preamble within a random access occasion selected from the first subset or the second subset.
  • PUSCH physical uplink shared channel
  • RedCap reduced capacity
  • Aspect 25 The method of Aspect 24, wherein the selected random access occasion indicates one of a request for repetition of the PUSCH message or a RedCap identification.
  • Aspect 26 The method of Aspect 25, wherein the random access preamble indicates the other of the request for repetition of the PUSCH message or the RedCap identification.
  • Aspect 27 The method of any of Aspects 25 through 26, further comprising: transmitting a response that approves the request for repetition of the PUSCH message; and receiving two or more repetitions of the PUSCH message.
  • Aspect 28 The method of Aspect 24, wherein a third subset of the set of random access occasions are associated with repetition of the PUSCH message and with the RedCap identification message.
  • Aspect 29 The method of Aspect 28, wherein the selected random access occasion indicates a request for repetition of the PUSCH message, a RedCap identification, or a combination thereof.
  • Aspect 30 The method of any of Aspects 24 through 29, wherein the indication of the set of random access occasions includes one or more indices associated with one or more masks used to determine the first subset and the second subset.
  • Aspect 31 An apparatus for wireless communication at a device, 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 the method of one or more of Aspects 1-8.
  • Aspect 32 A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-8.
  • Aspect 33 An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-8.
  • Aspect 34 A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-8.
  • Aspect 35 A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-8.
  • Aspect 36 An apparatus for wireless communication at a device, 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 the method of one or more of Aspects 9-16.
  • Aspect 37 A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 9-16.
  • Aspect 38 An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 9-16.
  • Aspect 39 A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 9-16.
  • Aspect 40 A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 9-16.
  • Aspect 41 An apparatus for wireless communication at a device, 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 the method of one or more of Aspects 17-23.
  • Aspect 42 A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 17-23.
  • Aspect 43 An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 17-23.
  • Aspect 44 A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 17-23.
  • Aspect 45 A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 17-23.
  • Aspect 46 An apparatus for wireless communication at a device, 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 the method of one or more of Aspects 24-30.
  • Aspect 47 A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 24-30.
  • Aspect 48 An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 24-30.
  • Aspect 49 A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 24-30.
  • Aspect 50 A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 24-30.
  • the term “component” is intended to be broadly construed as hardware and/or a combination of hardware and software.
  • “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and/or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • a “processor” is implemented in hardware and/or a combination of hardware and software. It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware and/or a combination of hardware and software.
  • satisfying a threshold may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.
  • “at least one of: a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiples of the same element (e.g., a+a, a+a+a, a+a+b, a+ a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c) .
  • the terms “has, ” “have, ” “having, ” or the like are intended to be open-ended terms that do not limit an element that they modify (e.g., an element “having” A may also have B) .
  • the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.
  • the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or, ” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of” ) .

Landscapes

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

Abstract

Divers aspects de la présente divulgation portent d'une manière générale sur la communication sans fil. Selon certains aspects, un équipement utilisateur (UE) peut recevoir une indication d'un ensemble d'occasions d'accès aléatoire. L'ensemble d'occasions d'accès aléatoire peut être partagé avec des UE existants, et l'ensemble d'occasions d'accès aléatoire peut être associé à la répétition d'un message de canal partagé de liaison montante physique (PUSCH). En variante, l'ensemble d'occasions d'accès aléatoire peut être distinct d'un ensemble supplémentaire d'occasions d'accès aléatoire associées à des UE existants, et au moins un premier sous-ensemble de l'ensemble d'occasions d'accès aléatoire étant associé à la répétition d'un message PUSCH et un deuxième sous-ensemble de l'ensemble d'occasions d'accès aléatoire étant associés à un message d'identification de capacité réduite (RedCap) . En conséquence, l'UE peut transmettre un préambule d'accès aléatoire dans une occasion choisie dans l'ensemble. De nombreux autres aspects sont décrits.
PCT/CN2021/111360 2021-08-06 2021-08-06 Occasions d'accès aléatoire pour la répétition d'un message de canal partagé de liaison montante physique Ceased WO2023010584A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/111360 WO2023010584A1 (fr) 2021-08-06 2021-08-06 Occasions d'accès aléatoire pour la répétition d'un message de canal partagé de liaison montante physique

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/111360 WO2023010584A1 (fr) 2021-08-06 2021-08-06 Occasions d'accès aléatoire pour la répétition d'un message de canal partagé de liaison montante physique

Publications (1)

Publication Number Publication Date
WO2023010584A1 true WO2023010584A1 (fr) 2023-02-09

Family

ID=77626877

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/111360 Ceased WO2023010584A1 (fr) 2021-08-06 2021-08-06 Occasions d'accès aléatoire pour la répétition d'un message de canal partagé de liaison montante physique

Country Status (1)

Country Link
WO (1) WO2023010584A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4318974A1 (fr) * 2022-08-05 2024-02-07 Comcast Cable Communications, LLC Accès aléatoire dans un réseau non terrestre

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210058971A1 (en) * 2019-08-19 2021-02-25 Samsung Electronics Co., Ltd. Repetition of prach preamble transmission for ues
WO2021119978A1 (fr) * 2019-12-17 2021-06-24 Qualcomm Incorporated Configuration pour répétitions de liaison montante dans une procédure d'accès aléatoire
WO2021127962A1 (fr) * 2019-12-24 2021-07-01 Qualcomm Incorporated Répétition efficace de nouveau message de lumière radio dans une procédure de canal d'accès aléatoire en deux étapes

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210058971A1 (en) * 2019-08-19 2021-02-25 Samsung Electronics Co., Ltd. Repetition of prach preamble transmission for ues
WO2021119978A1 (fr) * 2019-12-17 2021-06-24 Qualcomm Incorporated Configuration pour répétitions de liaison montante dans une procédure d'accès aléatoire
WO2021127962A1 (fr) * 2019-12-24 2021-07-01 Qualcomm Incorporated Répétition efficace de nouveau message de lumière radio dans une procédure de canal d'accès aléatoire en deux étapes

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4318974A1 (fr) * 2022-08-05 2024-02-07 Comcast Cable Communications, LLC Accès aléatoire dans un réseau non terrestre

Similar Documents

Publication Publication Date Title
US11785644B2 (en) Random access channel transmissions using resources associated with synchronization signal blocks
US11864238B2 (en) Mapping aspects of random access channel procedure
US11844115B2 (en) Indicating user equipment capability using random access preambles
US11950297B2 (en) Repetition-based contention-free random access
US12389409B2 (en) Dynamic indication of a full duplex random access channel occasion
US11871457B2 (en) Transmitting random access messages using aerial user equipment specific parameters
US12192954B2 (en) Paging indication of channel state information reference signal resources for beam refinement for a random access channel procedure
WO2023010584A1 (fr) Occasions d'accès aléatoire pour la répétition d'un message de canal partagé de liaison montante physique
EP4381882B1 (fr) Répétition de canal d'accès aléatoire
WO2022237818A1 (fr) Occasions de canal physique à accès aléatoire pour transmettre des requêtes de répétition de canal physique partagé montant
US11818764B2 (en) Message repetitions during a random access procedure
US11665747B2 (en) Random access configurations using reference signals
US11818770B2 (en) Random access channel beam management
WO2023141924A1 (fr) Procédure de canal d'accès aléatoire en deux étapes
EP4238254A1 (fr) Techniques pour planifier des signaux de référence d'informations d'état de canal et une rétroaction pendant une opération de canal d'accès aléatoire
US11991757B2 (en) Random access channel coverage enhancement
WO2023082081A1 (fr) Indication de quantité de répétition de msg3
WO2023097593A1 (fr) Augmentation de puissance basée sur l'équipement utilisateur pour la retransmission du message 3 de la procédure de canal d'accès aléatoire
WO2022232984A1 (fr) Partitions à accès aléatoire pour différents cas d'utilisation

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21765550

Country of ref document: EP

Kind code of ref document: A1