Request for physical uplink shared channel reuse associated with a radio resource control connection request message during a random access channel procedure - Patents.com

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may transmit a request for a physical uplink shared channel (PUSCH) repetition associated with a radio resource control (RRC) connection request message of a random access channel (RACH) procedure to a base station. The UE may transmit at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request. Numerous other aspects are described.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This patent application is a continuation of U.S. Provisional Patent Application No. 63 / 138,210, filed January 15, 2021, entitled "REQUESTS FOR PHYSICAL UPLINK SHARED CHANNEL REPETITION ASSOCIATED WITH A RADIO RESOURCE CONTROL CONNECTION REQUEST MESSAGE IN A RANDOM ACCESS CHANNEL PROCEDURE," and U.S. Provisional Patent Application No. 63 / 141,299, filed January 25, 2021, entitled "COMMUNICATION OF PHYSICAL UPLINK SHARED CHANNEL REPETITION INFORMATION USING SPECIFIC FREQUENCY RESOURCES FOR A PHYSICAL RANDOM ACCESS CHANNEL MESSAGE," all of which are expressly incorporated herein by reference. This application claims priority to U.S. Nonprovisional Patent Application No. 17 / 646,393, filed December 29, 2021, entitled "REQUEST MESSAGE IN A RANDOM ACCESS CHANNEL PROCEDURE."

[0002] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for requesting physical uplink shared channel repetition associated with a radio resource control connection request message during a random access channel procedure. [Background technology]

[0003] Wireless communication systems have been widely deployed to provide various telecommunication services, such as telephone, video, data, messaging, and broadcast. A typical wireless communication system may utilize multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such 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 extensions to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the 3rd Generation Partnership Project (3GPP®).

[0004] A wireless network may include a number of base stations (BSs) that can support communication for a number of user equipments (UEs). The UEs may communicate with the BSs via a downlink and an uplink. The "downlink" (or "forward link") refers to the communication link from the BS to the UE, and the "uplink" (or "reverse link") refers to the communication link from the UE to the BS. As described in more detail herein, a BS may be referred to as a Node B, gNB, access point (AP), radio head, transmit receive point (TRP), new radio (NR) BS, 5G Node B, etc.

[0005] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that allows various user equipment to communicate at city, national, regional, and even global levels. NR, sometimes referred to as 5G, is a set of extensions to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, reducing costs, improving services, utilizing new spectrum, and using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink (DL) and CP-OFDM and / or SC-FDM (also known as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM) on the uplink (UL) to better integrate with other open standards, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to grow, further improvements in LTE, NR, and other radio access technologies remain useful. Summary of the Invention [Means for solving the problem]

[0006] In some aspects, a user equipment (UE) for wireless communication includes a memory and one or more processors coupled to the memory, where the one or more processors are configured to: send a request for physical uplink shared channel repetition (PUSCH repetition) associated with a radio resource control (RRC) connection request message of a random access channel (RACH) procedure to a base station; and transmit at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.

[0007] In some aspects, a base station for wireless communication includes a memory and one or more processors coupled to the memory, where the one or more processors are configured to receive, from a UE, a request for PUSCH repetitions associated with an RRC connection request message of a RACH procedure, and receive at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.

[0008] In some aspects, a method of wireless communication implemented by a UE includes transmitting a request for PUSCH repetitions associated with an RRC connection request message of a RACH procedure to a base station and transmitting at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.

[0009] In some aspects, a method of wireless communication implemented by a base station includes receiving, from a UE, a request for PUSCH repetitions associated with an RRC connection request message of a RACH procedure, and receiving at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.

[0010] In certain aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to send a request to a base station for PUSCH repetitions associated with an RRC connection request message of a RACH procedure, and to transmit at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.

[0011] In certain aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communications includes one or more instructions that, when executed by one or more processors of a base station, cause the base station to receive a request from a UE for PUSCH repetitions associated with an RRC connection request message of a RACH procedure and receive at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.

[0012] In some aspects, an apparatus for wireless communication includes means for transmitting a request for PUSCH repetitions associated with an RRC connection request message of a RACH procedure to a base station and means for transmitting at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.

[0013] In certain aspects, an apparatus for wireless communication includes means for receiving, from a UE, a request for PUSCH repetitions associated with an RRC connection request message of a RACH procedure, and means for receiving at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.

[0014] Some aspects described herein relate to a UE for wireless communication. The user equipment may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit a PRACH message including a request for PUSCH repetitions associated with an RRC connection request message of a RACH procedure to a base station and based at least in part on a determination that one or more trigger criteria are satisfied, the one or more trigger criteria including a reference signal received power threshold. The one or more processors may be configured to transmit at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.

[0015] Some aspects described herein relate to a UE for wireless communication. The user equipment may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit a PRACH message including a request for PUSCH repetitions associated with an RRC connection request message of a RACH procedure to a base station and based at least in part on a determination that one or more trigger criteria are satisfied, the one or more trigger criteria including a reference signal received power threshold. The one or more processors may be configured to receive an indication of a PUSCH repetition request grant from the base station, the PUSCH repetition request grant corresponding to at least a portion of the PUSCH repetition request. The one or more processors may be configured to transmit at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.

[0016] Some aspects described herein relate to a base station for wireless communication. The base station may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a request from a UE for PUSCH repetitions associated with an RRC connection request message of a RACH procedure. The one or more processors may be configured to receive at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.

[0017] Certain aspects described herein relate to a method of wireless communication by a UE. The method may include determining one or more alternating frequency resources for PRACH transmission, where the one or more alternating frequency resources are used to communicate PUSCH repetition information. The method may include transmitting a PRACH message to a base station using the one or more alternating frequency resources for communicating the PUSCH repetition information.

[0018] Certain aspects described herein relate to a method of wireless communication by a base station that may include receiving a PRACH message from a UE using one or more alternating frequency resources for a PRACH transmission. The method may include determining PUSCH repetition information based on the one or more alternating frequency resources used to receive the PRACH message, where the PUSCH repetition information is communicated using the one or more alternating frequency resources.

[0019] Certain aspects described herein relate to a UE for wireless communication. The user equipment may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to determine one or more alternating frequency resources for PRACH transmission, where the one or more alternating frequency resources are used to communicate PUSCH repetition information. The one or more processors may be configured to transmit a PRACH message to a base station using the one or more alternating frequency resources for communicating the PUSCH repetition information.

[0020] Some aspects described herein relate to a base station for wireless communication. The base station may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a PRACH message from a UE using one or more alternating frequency resources for PRACH transmission. The one or more processors may be configured to determine PUSCH repetition information based on the one or more alternating frequency resources used to receive the PRACH message, where the PUSCH repetition information is communicated using the one or more alternating frequency resources.

[0021] Certain aspects described herein relate to a non-transitory computer-readable medium storing 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 determine one or more alternating frequency resources for PRACH transmission, where the one or more alternating frequency resources are used to communicate PUSCH repetition information. The set of instructions, when executed by the one or more processors of the UE, may cause the UE to transmit a PRACH message to a base station using the one or more alternating frequency resources for communicating the PUSCH repetition information.

[0022] Certain aspects described herein relate to a non-transitory computer-readable medium storing 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 receive a PRACH message from a UE using one or more alternating frequency resources for PRACH transmission. The set of instructions, when executed by the one or more processors of the base station, may cause the base station to determine PUSCH repetition information based on the one or more alternating frequency resources used to receive the PRACH message, where the PUSCH repetition information is communicated using the one or more alternating frequency resources.

[0023] Certain aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for determining one or more alternating frequency resources for PRACH transmission, where the one or more alternating frequency resources are used to communicate PUSCH repetition information. The apparatus may include means for transmitting a PRACH message to a base station using the one or more alternating frequency resources for communicating the PUSCH repetition information.

[0024] Certain aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a PRACH message from a UE using one or more alternating frequency resources for PRACH transmission. The apparatus may include means for determining PUSCH repetition information based on the one or more alternating frequency resources used to receive the PRACH message, where the PUSCH repetition information is communicated using the one or more alternating frequency resources.

[0025] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as fully described herein with reference to and as illustrated in the drawings and this specification.

[0026] The foregoing has outlined rather broadly the features and technical advantages of the embodiments according to the present disclosure so that the detailed description that follows may be better understood. Additional features and advantages are described below. The concepts and examples disclosed may be readily used as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent structures do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both their organization and methods of operation, together with associated advantages, will be better understood from the following description when considered in conjunction with the accompanying drawings. Each of the figures is provided for the purpose of illustration and explanation, and not as a definition of the limits of the claims.

[0027] Although aspects are described in this disclosure by illustrating some examples, those skilled in the art will understand that such aspects may be implemented in many different configurations and scenarios. The techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging configurations. For example, some aspects may be implemented by integrated chip embodiments or other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, or artificial intelligence-enabled devices). Aspects may be implemented with chip-level components, modular components, non-modular components, non-chip-level components, device-level components, or system-level components. Devices incorporating the described aspects and features may include additional components and features for the implementation and practice of the claims and described aspects. For example, the transmission and reception of wireless signals may include several components (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, or summers) for analog and digital purposes. It is contemplated that aspects described herein may be practiced in a wide variety of devices, components, systems, distributed configurations, or end-user devices of various sizes, shapes, and configurations.

[0028] So that the above-mentioned features of the present disclosure may be understood in detail, the contents briefly summarized above may be more particularly described by referring to the embodiments, some of which are shown in the attached drawings. However, since the present description may admit of other equally effective embodiments, it should be noted that the attached drawings show only some typical embodiments of the present disclosure and therefore should not be considered as limiting its scope. The same reference numbers in different drawings may identify the same or similar elements. [Brief description of the drawings]

[0029] [Figure 1] FIG. 1 illustrates an example of a wireless network in accordance with the present disclosure. [Diagram 2] FIG. 1 illustrates an example of a base station communicating with a user equipment (UE) in a wireless network in accordance with the present disclosure. [Diagram 3] FIG. 1 illustrates an example of a four-stage random access channel (RACH) operation in accordance with the present disclosure. [Figure 4] FIG. 1 illustrates an example related to a request for Physical Uplink Shared Channel (PUSCH) repetition associated with a Radio Resource Control (RRC) Connection Request message during a RACH procedure, in accordance with the present disclosure. [Diagram 5] FIG. 1 illustrates an example process associated with a request for PUSCH repetition associated with an RRC connection request message during a RACH procedure, in accordance with the present disclosure. [Figure 6] FIG. 1 illustrates an example process associated with a request for PUSCH repetition associated with an RRC connection request message during a RACH procedure, in accordance with the present disclosure. [Figure 7] FIG. 1 illustrates an example process associated with a request for PUSCH repetition associated with an RRC connection request message during a RACH procedure, in accordance with the present disclosure. [Figure 8] FIG. 1 illustrates an example process associated with a request for PUSCH repetition associated with an RRC connection request message during a RACH procedure, in accordance with the present disclosure. [Figure 9] 1 is a block diagram of an example apparatus for wireless communication according to the present disclosure. [Figure 10] 1 is a block diagram of an example apparatus for wireless communication according to the present disclosure. [Figure 11] 1 is a block diagram of an example apparatus for wireless communication according to the present disclosure. [Figure 12] 1 is a block diagram of an example apparatus for wireless communication according to the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0030] Various aspects of the present disclosure will be described more fully below with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout the present disclosure. Rather, these aspects are designed so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art should appreciate that the scope of the present disclosure is intended to encompass any aspect of the present disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the present disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects described herein. In addition, the scope of the present disclosure is intended to encompass such an apparatus or method that is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure described herein. It should be understood that any aspect of the present disclosure disclosed herein may be embodied by one or more elements of a claim.

[0031] Several aspects of a telecommunications system are now presented with reference to various apparatus and techniques. These apparatus and techniques are described in the detailed description that follows and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0032] Although aspects may be described herein using terminology commonly associated with 5G or NR radio access technologies (RATs), it should be noted that aspects of the disclosure may apply to other RATs, such as 3G RATs, 4G RATs, and / or post-5G (e.g., 6G) RATs.

[0033] FIG. 1 illustrates an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be or include elements of a 5G (NR) network and / or an LTE network, among other examples. The wireless network 100 may include several base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) as well as other network entities. A base station (BS) is an entity that communicates with user equipment (UE) and may also be referred to as an NR BS, Node B, gNB, 5G Node B (NB), access point, transmit reception point (TRP), etc. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a BS and / or a BS subsystem serving this coverage area, depending on the context in which the term is used.

[0034] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs with an association with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In the example shown in FIG. 1, BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. A BS may support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” may be used interchangeably herein.

[0035] In some aspects, the cells may not necessarily be stationary and the geographic area of ​​the cells may move according to the location of the mobile BS. In some aspects, the BSs may be interconnected to each other and / or to one or more other BSs or network nodes (not shown) in wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

[0036] The wireless network 100 may also include relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a BS or a UE) and send the transmission of the data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. In the example shown in FIG. 1, a relay BS 110d may communicate with the BS 110a and the UE 120d to facilitate communication between the macro BS 110a and the UE 120d. A relay BS may also be referred to as a relay station, a relay base station, a relay, etc.

[0037] The wireless network 100 may be a heterogeneous network including different types of BSs, such as macro BSs, pico BSs, femto BSs, relay BSs, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5-40 watts), while a pico BS, femto BS, and relay BS may have a lower transmit power level (e.g., 0.1-2 watts).

[0038] A network controller 130 may couple to a set of BSs and provide coordination and control for these BSs. The network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with each other directly or indirectly via wireless or wireline backhaul.

[0039] The UEs 120 (e.g., 120a, 120b, 120c) may be dispersed throughout the wireless network 100, and each UE may be fixed or mobile. A UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. A UE may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or satellite radio), a vehicle part or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate over a wireless or wired medium.

[0040] Some UEs may be considered as machine type communication (MTC) UEs or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and eMTC UEs 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. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered as customer premises equipment (CPE). The UE 120 may be included within a housing that houses components of the UE 120, such as a processor component and / or a memory component. In some aspects, the processor component and the memory component may be coupled to each other. For example, a processor component (e.g., one or more processors) and a memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0041] In general, any number of wireless networks may be deployed within a given geographic area. Each wireless network may support a particular RAT and may operate on one or more frequencies. The RAT may also be referred to as a radio technology, an air interface, etc. The frequencies may also be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic region to avoid interference between wireless networks of different RATs. In some cases, NR networks or 5G RAT networks may be deployed.

[0042] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using the base station 110 as an intermediary for communicating with each other) using one or more sidelink channels. For example, the UEs 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (which may include, e.g., vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, etc.), and / or mesh networks. In this case, the UEs 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the base station 110.

[0043] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be sub-divided into various classes, bands, channels, etc. based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using an operating band having a first frequency range (FR1), which may range from 410 MHz to 7.125 GHz, and / or may communicate using an operating band having a second frequency range (FR2), which may range from 24.25 GHz to 52.6 GHz. Frequencies between FR1 and FR2 may be referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as the "sub-6 GHz" band. Similarly, FR2 is often referred to as the "millimeter wave" band, even though it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunications Union (ITU). Thus, unless otherwise specified, it should be understood that terms such as "sub-6 GHz," as used herein, may broadly refer to frequencies below 6 GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise specified, it should be understood that terms such as "millimeter wave," as used herein, may broadly refer to frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25 GHz). The frequencies included in FR1 and FR2 may be modified, and it is contemplated that the techniques described herein are applicable to those modified frequency ranges.

[0044] As noted above, Figure 1 is provided as an example. Other examples may differ from those described with respect to Figure 1.

[0045] 2 is a diagram illustrating an example base station 110 200 in communication with a UE 120 in wireless network 100 in accordance with the present disclosure. The base station 110 may be equipped with T antennas 234a through 234t, and the UE 120 may be equipped with R antennas 252a through 252r, where in general T≧1 and R≧1.

[0046] At the base station 110, the transmit processor 220 may receive data for one or more UEs from a data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for the UE, and provide data symbols to all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or higher layer signaling) and provide overhead and control symbols. The transmit processor 220 may also 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)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.

[0047] At the UE 120, the antennas 252a-252r may receive downlink signals from the base station 110 and / or other base stations, respectively, and may provide received signals to demodulators (DEMODs) 254a-254r. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254a-254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 260, and provide decoded control and system information to the controller / processor 280. The term "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. In some aspects, one or more components of the UE 120 may be included within the housing 284.

[0048] 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.

[0049] An antenna (e.g., antennas 234a-t and / or antennas 252a-r) may include or be contained within one or more antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays, among other examples. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include one or more antenna elements. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include a set of coplanar antenna elements and / or a set of non-coplanar antenna elements. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include antenna elements in a single housing and / or antenna elements in multiple housings. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include one or more antenna elements coupled to one or more transmitting and / or receiving components, such as one or more components of FIG. 2.

[0050] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI) from the controller / processor 280. The transmit processor 264 may also 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 modulators 254a-254r (e.g., for DFT-s-OFDM, or CP-OFDM), and transmitted to the base station 110. In some aspects, the modulators and demodulators (e.g., MOD / DEMOD 254) of the UE 120 may be included within a modem of the UE 120. In some aspects, the UE 120 includes a transceiver. The transceiver may include any combination of antennas 252, modulators and / or demodulators 254, MIMO detectors 256, receive processors 258, transmit processors 264, and / or TX MIMO processors 266. The transceiver may be used to implement aspects of any of the methods described herein, for example, as described with respect to FIGS.

[0051] At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by the demodulator 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 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 the UE 120 for downlink and / or uplink communication. In some aspects, a modulator and demodulator (e.g., MOD / DEMOD 232) of the base station 110 may be included within a modem of the base station 110. In some aspects, the base station 110 includes a transceiver. The transceiver may include any combination of antennas 234, modulators and / or demodulators 232, MIMO detectors 236, receive processors 238, transmit processors 220, and / or TX MIMO processors 230. The transceiver may be used to implement aspects of any of the methods described herein, for example, as described with respect to FIGS.

[0052] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other components of FIG. 2 may implement one or more techniques associated with a request for a physical uplink shared channel (PUSCH) repetition associated with a radio resource control (RRC) connection request message during a RACH procedure, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other components of FIG. 2 may implement or direct the operation 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 described herein. The memories 242 and 282 may store data and program codes for the base station 110 and the UE 120, respectively. In some aspects, the memory 242 and / or the memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., immediately or after being compiled, converted, and / or interpreted) 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, such as, 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. In some aspects, executing the instructions may include executing the instructions, converting the instructions, compiling the instructions, and / or interpreting the instructions, among other examples.

[0053] In some aspects, the UE includes means for transmitting a request for PUSCH repetitions associated with an RRC connection request message of a random access channel (RACH) procedure to a base station, or means for transmitting at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request. In some aspects, the UE includes means for selecting one or more physical random access channel (PRACH) parameters based at least in part on a relationship between one or more PRACH parameters and one or more request parameters corresponding to the request for PUSCH repetitions. In some aspects, the UE includes means for receiving a parameter configuration from the base station indicative of the relationship. In some aspects, the UE includes means for determining that one or more trigger criteria are satisfied, and transmitting the request for PUSCH repetitions includes transmitting the request for PUSCH repetitions based at least in part on determining that the one or more trigger criteria are satisfied. In some aspects, the UE includes means for receiving a trigger configuration indicative of the one or more trigger criteria from the base station.

[0054] In some aspects, the UE includes means for determining a first synchronization signal block (SSB) based RSRP, where determining that the one or more trigger criteria are satisfied includes determining that the first SSB based RSRP satisfies a first RSRP threshold. In some aspects, the UE includes means for determining a second SSB based RSRP, where determining that the one or more trigger criteria are satisfied includes determining that the second SSB based RSRP satisfies a second RSRP threshold. In some aspects, the UE includes means for receiving a random access response (RAR) message from the base station, where the RAR message indicates at least one of a PUSCH repetition parameter or a PUSCH repetition resource. In some aspects, the UE includes means for receiving an indication of a PUSCH repetition request grant from the base station, where the PUSCH repetition request grant corresponds to at least a portion of the PUSCH repetition request.

[0055] In some aspects, the UE includes means for determining one or more alternating frequency resources for PRACH transmission, where the one or more alternating frequency resources are used to communicate PUSCH repetition information, and / or means for transmitting a PRACH message to the base station using the one or more alternating frequency resources for communicating the PUSCH repetition information.

[0056] Means for a UE to perform the operations described herein may include, for example, one or more of the antenna 252, the demodulator 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the modulator 254, the controller / processor 280, or the memory 282.

[0057] In some aspects, the base station includes means for receiving from the UE a request for PUSCH repetitions associated with an RRC connection request message of the RACH procedure or means for receiving at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request. In some aspects, the base station includes means for transmitting a parameter configuration indicative of the relationship to the UE. In some aspects, the base station includes means for transmitting a trigger configuration indicative of one or more trigger criteria to the UE. In some aspects, the base station includes means for transmitting a RAR message to the UE. In some aspects, the base station includes means for transmitting an indication of a PUSCH repetition request grant to the UE, the PUSCH repetition request grant corresponding to at least a portion of the PUSCH repetition request.

[0058] In some aspects, the base station includes means for receiving a PRACH message from the UE using one or more alternating frequency resources for the PRACH transmission, and / or means for determining PUSCH repetition information based on the one or more alternating frequency resources used to receive the PRACH message, where the PUSCH repetition information is communicated using the one or more alternating frequency resources.

[0059] Means for a base station to perform the operations described herein may include, for example, one or more of the transmit processor 220, the TX MIMO processor 230, the modulator 232, the antennas 234, the demodulator 232, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0060] 2 are illustrated as distinct components, the functionality described above with respect to the blocks may be implemented with a single hardware component, software component, or combination of components, or with various combinations of components. For example, functionality described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0061] As noted above, Figure 2 is provided as an example. Other examples may differ from those described with respect to Figure 2.

[0062] 3 is a diagram illustrating an example of a four-stage RACH operation according to the present disclosure. As shown in FIG. 3, the base station 110 and the UE 120 may communicate with each other to perform a four-stage RACH procedure.

[0063] As indicated by reference numeral 305, the base station 110 may transmit, and the UE 120 may receive, one or more SSBs and random access configuration information. In some aspects, the random access configuration information may be transmitted and / or indicated by system information (e.g., in one or more system information blocks (SIBs), among other examples) and / or SSBs, such as for contention-based random access. Additionally or alternatively, the random access configuration information may be transmitted in an RRC message and / or a physical downlink control channel (PDCCH) order message that triggers a RACH procedure, such as for contention-free random access. 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 RAR, among other examples.

[0064] As indicated by reference numeral 310, UE 120 may transmit a RAM with a RACH request over the PRACH. The RAM may include a preamble (sometimes referred to as a random access preamble, a PRACH preamble, and / or a RAM preamble, among other examples). The message including the preamble may be referred to as a message 1, msg1, MSG1, a first message, and / or an initial message, among other examples in a four-stage random access procedure. The random access message may include a random access preamble identifier.

[0065] As indicated by reference numeral 315, the base station 110 may transmit an RAR in response to the preamble. The message containing the RAR may be referred to as message 2, msg2, MSG2, or the second message in the four-stage random access procedure. In some aspects, the RAR may indicate a 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) (see below).

[0066] In some aspects, as part of a second stage of the four-stage random access procedure, 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. For example, the PDCCH communication may indicate a resource allocation for the PDSCH communication. Also, as part of the second stage of the four-stage random access procedure, the base station 110 may transmit a PDSCH communication for the RAR as scheduled by the PDCCH communication. The RAR may be included in a MAC protocol data unit (PDU) of the PDSCH communication.

[0067] As indicated by reference numeral 320, the UE 120 may transmit an RRC connection request message. The RRC connection request message may be referred to as message 3, msg3, MSG3, a UE identification message, or a third message of the four-stage random access procedure. In some aspects, the RRC connection request may include a UE identifier, uplink control information (UCI), and / or a PUSCH communication (e.g., an RRC connection request), among other examples.

[0068] As indicated by reference numeral 325, 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 the fourth message of the four-stage random access procedure. In some aspects, the RRC connection setup message may include a detected UE identifier, a timing advance value, and / or contention resolution information, among other examples. As indicated by reference numeral 330, if the UE 120 successfully receives the RRC connection setup message, the UE 120 may transmit a hybrid automatic repeat request (HARQ) acknowledgement (ACK).

[0069] The RACH procedure may have coverage limitations, which may cause adverse effects on network performance. In some cases, RACH messages in a frequency range of about 24 GHz or higher may not be received by the UE or may be decoded incorrectly by the UE. As a result, the RRC connection setup message may not be transmitted effectively, and network connectivity is impaired. Repetition of the PUSCH associated with the RRC connection setup message may promote more effective coverage. To implement PUSCH repetition, the UE may communicate PUSCH repetition information to the base station to schedule PUSCH repetition. The PUSCH repetition information may include a request for PUSCH repetition and / or an indication of the UE capability for PUSCH repetition. However, scheduling PUSCH repetition for UEs for which coverage is not an issue may result in inefficiencies that waste resources. Furthermore, transmitting PUSCH repetition information as part of the data transmitted to the base station may not be an efficient use of resources.

[0070] Aspects of the techniques described herein may facilitate efficient PUSCH repetition associated with an RRC connection setup request message during a RACH procedure. For example, aspects may enable a UE to request PUSCH repetition and / or parameters of PUSCH repetition. Thus, aspects may enable PUSCH repetition only when and to the extent that it can benefit the UE, resulting in efficient coverage enhancement for the RRC connection, which can positively impact network performance, thereby saving resources (e.g., computational, memory, communication, and network resources) that would be wasted in connection with scheduling PUSCH repetition for UEs for which coverage is not an issue.

[0071] According to some aspects of the present disclosure, the UE may use a specific frequency resource to communicate the PUSCH repetition information to the base station, and the PUSCH repetition information is communicated by using the specific frequency resource. For example, the UE may use a regular frequency resource for the PRACH transmission associated with a single PUSCH transmission without any PUSCH repetition. Meanwhile, the UE may use an alternate frequency resource for the PRACH transmission to communicate the PUSCH repetition information, and the PUSCH repetition information may be communicated by using the alternate frequency resource. Thus, for example, instead of conveying the PUSCH repetition information by specific data signaling, the PUSCH repetition may be communicated to the base station by using the specific alternate frequency resource such that the base station may determine the PUSCH repetition information based on the use of the alternate frequency resource for the PRACH transmission. In some aspects, the alternate frequency resource may be at least partially different from the regular frequency resource for the PRACH transmission associated with the single PUSCH transmission.

[0072] In some aspects, the UE may determine an alternating frequency resource for PRACH transmission and may transmit the PRACH message using the alternating frequency resource to communicate PUSCH repetition information. Based on the PUSCH repetition information, the UE may transmit the PUSCH message and at least one repetition of the PUSCH message, thereby implementing PUSCH repetition.

[0073] As mentioned above, the base station may determine the PUSCH repetition information based on the use of alternating frequency resources for the PRACH transmission. In some aspects, once the base station determines the PUSCH repetition information, the base station may transmit an indication of PUSCH resources and / or PUSCH parameters based on the PUSCH repetition information such that the UE can use the PUSCH resources and / or PUSCH parameters to transmit the PUSCH message and at least one repetition of the PUSCH message. In some aspects, the indication of the PUSCH resources and / or PUSCH parameters may be transmitted via a RAR message.

[0074] In some aspects, the base station may indicate the alternate frequency resource to the UE. The base station may allocate the alternate frequency resource, for example, by selecting an available frequency resource different from the regular frequency resource. For example, the alternate frequency resource may be allocated among resource blocks. In an example, the alternate frequency resource may be in a different component carrier than the regular frequency resource for a PRACH transmission associated with a single PUSCH transmission without PUSCH repetition. In some aspects, the base station may transmit resource parameters indicating the alternate frequency resource to the UE, such that the UE can determine the alternate frequency resource based on the received resource parameters. In some aspects, the UE may receive the resource parameters via system information from the base station. In some aspects, the UE may receive the resource parameters via system information (e.g., Minimum Remaining System Information (RMSI)) transmitted from the base station.

[0075] In some aspects, the resource parameters may specifically indicate the alternating frequency resource. In some aspects, the resource parameters may include a frequency offset, in which case the UE may determine the alternating frequency resource by applying a frequency offset to a regular frequency resource for a PRACH transmission associated with a single PUSCH transmission without PUSCH repetition. In some aspects, the frequency offset may be given in number of resource blocks.

[0076] In some aspects, the PUSCH repetition information may indicate one or more parameters corresponding to a request for PUSCH repetition and / or an indication of UE capability for PUSCH repetition. In some aspects, the one or more parameters may include one or more of a request for PUSCH repetition, an indication of UE capability, and a number of PUSCH repetitions. In some aspects, the one or more parameters may include an indication that at least one of the request for PUSCH repetition or the indication of UE capability is associated with a PUSCH repetition with DMRS aggregation for cross-slot channel estimation. For example, when DMRS aggregation / bundling is used, DMRS in different repetitions in different slots may be used together as a cross-slot channel estimation for channel estimation. In some aspects, the one or more parameters may include an indication that the PUSCH repetition is associated with one or more transmission configuration indicators (TCIs). For example, multiple TCIs may be associated with multiple beams of the UE. In some aspects, the one or more parameters may include an indication that at least one of the request for a PUSCH repetition or the indication of UE capability is associated with a PUSCH repetition with frequency hopping. For example, frequency hopping may occur when there is a frequency shift between PUSCH repetitions, such that different frequencies are used for different repetitions.

[0077] By using different sets of alternating frequency resources, different parameters of the PUSCH repetition information may be communicated to the base station. For example, one parameter may be communicated by using one set of alternating frequency resources and another parameter may be communicated by using another set of alternating frequency resources. In some aspects, one or more alternating frequency resources are different for each of the one or more parameters. In some aspects, a set of alternating frequency resources may be used to communicate multiple parameters and a different set of alternating frequency resources may be used to communicate a single parameter. For example, a set of alternating frequency resources may be used to communicate a request for PUSCH repetitions and the number of PUSCH repetitions and another set of alternating frequency resources may be used to communicate an indication that the PUSCH repetitions are associated with one or more TCIs. In one example, a set of alternating frequency resources may be used to communicate a request for PUSCH repetitions and the number of PUSCH repetitions being two, and another set of alternating frequency resources may be used to communicate a request for PUSCH repetitions and the number of PUSCH repetitions being four.

[0078] The transmit power for the PUSCH repetitions may be different from the transmit power for a single PUSCH transmission without any PUSCH repetitions. In some aspects, the UE may determine a transmit power parameter associated with the transmit power for the PUSCH repetitions, and the UE configures the transmit power for the PUSCH repetitions based on the transmit parameter. The alternate frequency resource may be associated with one transmit power parameter, and the regular frequency resource for the PRACH transmission associated with the single PUSCH transmission without PUSCH repetitions may be associated with a different transmit parameter. Thus, in some aspects, when the UE determines to use the alternate frequency resource for the PRACH transmission, the UE may determine the transmit power parameter for the PUSCH transmission to be the transmit power parameter associated with the transmit power for the PUSCH repetitions. On the other hand, when the UE determines to use the regular frequency resource for the PRACH transmission, the UE may determine the transmit power parameter for the PUSCH transmission to be the transmit power parameter associated with the transmit power for the single PUSCH transmission without any PUSCH repetitions. Thus, deciding to use alternating frequency resources for PRACH transmission may indicate which transmit power parameters to use for PUSCH transmission and / or PUSCH repetition.

[0079] In some aspects, the base station may determine a transmit power parameter associated with a transmit power for a PUSCH repetition from the base station and may further determine a transmit power parameter associated with a transmit power for a single PUSCH transmission without any PUSCH repetition. The UE may receive from the base station a transmit power parameter associated with a transmit power for a PUSCH repetition from the base station. The UE may also receive from the base station a different transmit power parameter associated with a transmit power for a single PUSCH transmission without any PUSCH repetition. The transmit power parameter may be received from the base station via system information (e.g., RMSI) from the base station. In some aspects, the transmit power parameter associated with a transmit power for a PUSCH repetition may include a power offset value between the transmit power for the PUSCH repetition and a second transmit power for the PRACH transmission. Furthermore, the transmit power parameter associated with a transmit power for the single PUSCH transmission may include a different power offset value between the transmit power for the single PUSCH transmission and the second transmit power for the PRACH transmission. For example, the second transmit power for the PRACH transmission may remain the same. In one example, to determine the transmit power for the PUSCH repetition, a power offset value between the transmit power for the PUSCH repetition and the second transmit power for the PRACH transmission may be applied to the second transmit power. In one example, the power offset value may be based on the power parameter "msg3-DeltaPreamble" included in the PUSCH-ConfigCommon field communicated from the base station. In another example, the power parameter may include one or more of the parameters "msg3-Alpha", "p0-NominalWithoutGrant" and "p0-PUSCH-Alpha" in the PUSCH-PowerControl field transmitted from the base station.

[0080] In some aspects, a transmit power parameter associated with a transmit power for PUSCH repetitions from a base station and / or a transmit power for a single PUSCH transmission without any PUSCH repetitions may be preloaded at the UE.

[0081] In some aspects, the transmit power parameter includes a power offset value between a transmit power for the PUSCH repetition and a second transmit power for the PRACH transmission.

[0082] As noted above, Figure 3 is provided as an example. Other examples may differ from those described with respect to Figure 3.

[0083] 4 is a diagram illustrating an example 400 associated with a request for PUSCH repetition associated with an RRC connection request message during a RACH procedure in accordance with the present disclosure. As shown in FIG. 4, a UE 405 and a base station 410 may communicate with each other.

[0084] As indicated by reference numeral 415, the base station 410 may transmit, and the UE 405 may receive, system information (SI), which may include a parameter configuration indicating a relationship between one or more PRACH parameters and a request for PUSCH repetitions associated with the RRC connection request message. In some aspects, the parameter configuration may indicate a relationship between one or more PRACH parameters and one or more requested parameters corresponding to the requested PUSCH repetitions. The SI may include, for example, an RMSI. In some aspects, the above-mentioned relationships, or aspects thereof, may be indicated by a wireless communication standard.

[0085] As used herein, "repetition" refers to a communication that is transmitted multiple times, either the initial transmission of that communication or any subsequent retransmissions of that communication. PUSCH repetition (which may be referred to as slot repetition, slot aggregation, and / or multi-slot PUSCH, for example) may be used to increase the signal-to-noise ratio (SNR) to improve transmission reliability.

[0086] As indicated by reference numeral 420, the UE 405 may determine to use an alternate frequency resource for PRACH transmission, where the alternate frequency resource is used to communicate PUSCH repetition information. Thus, by using the alternate frequency resource for PRACH transmission, the UE 405 may indicate PUSCH repetition information to the base station 410. The alternate frequency resource may be different from a regular frequency resource for PRACH transmission associated with a single PUSCH transmission without PUSCH repetition. The alternate frequency resource may be determined based on a resource parameter indicating the alternate frequency resource, where the resource parameter may be pre-configured / pre-loaded in the UE 405 or provided by the base station 410 (e.g., by SI).

[0087] As indicated by reference numeral 425, the UE 405 may transmit, and the base station 410 may receive, a PRACH message including a request for PUSCH repetitions associated with an RRC connection request message of a RACH procedure. In some aspects, the UE 405 may transmit, and the base station 410 may receive, a PRACH message using alternating frequency resources for communicating the PUSCH repetition information. The request for PUSCH repetitions may indicate one or more proposed parameters corresponding to the PUSCH repetitions. For example, the one or more proposed parameters may indicate a number of PUSCH repetitions. In some aspects, the request for PUSCH repetitions may indicate a request for aggregated demodulation reference signals for cross-slot channel estimation. The request for PUSCH repetitions may include, among other examples, a request for PUSCH repetitions associated with one or more transmission configuration indicators and / or a request for PUSCH repetitions with frequency hopping. As discussed above, the PUSCH repetition information may indicate one or more parameters corresponding to a request for PUSCH repetitions and / or an indication of the UE capability for PUSCH repetitions. Thus, the UE 405 may implicitly communicate PUSCH repetition information by using alternating frequency resources for transmitting the PRACH message.

[0088] In some aspects, the UE 405 may repeat a PRACH message over multiple RACH opportunities (ROs). In some aspects, the request for PUSCH repetition may be implicit. For example, the UE 405 may transmit a PRACH preamble selected from a subset of PRACH preambles of a set of PRACH preambles. The subset may indicate a request for PUSCH repetition. In some aspects, the UE 405 may transmit a PRACH message using a subset of ROs of a set of ROs, the subset of ROs indicating a request for PUSCH repetition. In some aspects, the UE 405 may transmit a PRACH message using a PRACH format indicating a request for PUSCH repetition.

[0089] In some aspects, the UE 405 may transmit a PRACH message based at least in part on one or more PRACH parameters. In some aspects, the PRACH message may be transmitted based at least in part on a parameter configuration received from the base station 410. The UE 405 may select one or more PRACH parameters based at least in part on a relationship between the one or more PRACH parameters and one or more request parameters corresponding to a request for PUSCH repetitions. As mentioned above, the relationship may be indicated by the base station and / or specified in a wireless communication standard.

[0090] The UE 405 may be configured to determine that one or more trigger criteria are satisfied and to transmit a request for PUSCH repetition based at least in part on determining that the one or more trigger criteria are satisfied. In some aspects, the base station 410 may transmit, and the UE 405 may receive, a trigger configuration indicating the one or more trigger criteria. The trigger configuration may be conveyed in the SI (e.g., RMSI).

[0091] In some aspects, for example, the one or more trigger criteria may include one or more thresholds. For example, the one or more trigger criteria may include a first RSRP threshold. The UE 405 may determine a first SSB-based RSRP and may determine that the first SSB-based RSRP satisfies the first RSRP threshold. The UE 405 may request PUSCH repetition based at least in part on determining that the first SSB-based RSRP satisfies the first RSRP threshold.

[0092] In some aspects, the one or more trigger criteria may include a second RSRP threshold. The UE 405 may determine a second SSB-based RSRP and may determine that the second SSB-based RSRP satisfies the second RSRP threshold. In some aspects, for example, the request for PUSCH repetitions may indicate a first number of PUSCH repetitions requested based at least in part on determining that the first SSB-based RSRP satisfies the first RSRP threshold and may indicate a second number of PUSCH repetitions requested based at least in part on determining that the second SSB-based RSRP satisfies the second RSRP threshold. In some aspects, the one or more trigger criteria may be indicated in a wireless communication standard.

[0093] As indicated by reference numeral 430, if the base station 410 determines that an alternating frequency resource is to be used to receive the PRACH message, the base station 410 may determine PUSCH repetition information based on the alternating frequency resource.

[0094] As indicated by reference numeral 435, the base station 410 may transmit, and the UE 405 may receive, an RAR message. The RAR message may be transmitted by the base station 410 and received by the UE 405 based on the PUSCH repetition information. The RAR message may indicate at least one of a PUSCH resource for an RRC connection request message or a PUSCH parameter associated with the RRC connection request message. The UE 405 may, for example, determine at least one of a PUSCH repetition parameter or a PUSCH repetition resource based at least in part on the RAR message.

[0095] In some aspects, the base station 410 may transmit, and the UE 405 may receive, an indication of a PUSCH repetition request grant. The PUSCH repetition request grant may correspond to at least a portion of a PUSCH repetition request. In some aspects, the indication of the PUSCH repetition request grant may be carried in a RAR message. For example, the indication of the PUSCH repetition request grant may be carried in a PDCCH portion of the RAR message.

[0096] As indicated by reference numeral 440, the UE 405 may determine a transmit power parameter associated with a transmit power for the PUSCH repetition and configure the transmit power for the PUSCH repetition based on the transmit parameter. The transmit power parameter may be determined based on the alternating frequency resource. The transmit power parameter may be pre-configured / pre-loaded at the UE 405 or may be provided by the base station 410 (e.g., by an SI).

[0097] The UE 405 may transmit, and the base station 410 may receive, an RRC connection request PUSCH repetition, as indicated by reference numeral 445. The RRC connection request PUSCH repetition may be transmitted based at least in part on resources and / or parameters indicated in the RAR, which may be based at least in part on a request for PUSCH repetition. In some aspects, the resources and / or parameters indicated in the RAR may be based at least in part on PUSCH repetition information. In some aspects, any number of additional RRC connection request PUSCH repetitions may be transmitted. The base station 410 may transmit, and the UE 405 may receive, an RRC connection setup message, as indicated by reference numeral 450. The base station 410 may transmit the RRC connection setup message in response to receiving one or more of the PUSCH repetitions.

[0098] As noted above, Figure 4 is provided as an example. Other examples may differ from what is described with respect to Figure 4.

[0099] 5 illustrates an example process 500, performed, for example, by a UE, in accordance with the present disclosure. The example process 500 is an example in which a UE (e.g., UE 405) performs operations associated with a request for PUSCH repetition associated with an RRC connection request message during a RACH procedure.

[0100] As shown in FIG. 5, in some aspects, process 500 may include receiving a parameter configuration from a base station indicating a relationship between one or more PRACH parameters and one or more request parameters corresponding to a request for PUSCH repetitions (block 510). For example, a UE (e.g., using the receiving component 902 shown in FIG. 9) may receive a parameter configuration from a base station indicating a relationship between one or more PRACH parameters and one or more request parameters corresponding to a request for PUSCH repetitions. In some aspects, the parameter configuration is conveyed in an SI. In some aspects, the SI includes an RMSI. In some aspects, the relationship is indicated by a wireless communication standard.

[0101] As shown in FIG. 5, in some aspects, the process 500 may include determining an RSRP (block 520). For example, the UE (e.g., using the determining component 908 shown in FIG. 9) may determine the RSRP. In some aspects, the RSRP may be an SSB-based RSRP. As shown in FIG. 5, in some aspects, the process 500 may include determining that one or more trigger criteria are satisfied (block 530). For example, the UE (e.g., using the determining component 908 shown in FIG. 9) may determine that one or more trigger criteria are satisfied. In some aspects, the process 500 includes receiving a trigger configuration from a base station indicating the one or more trigger criteria. In some aspects, the one or more trigger criteria are indicated in a wireless communication standard.

[0102] In some aspects, the trigger configuration is conveyed in an SI. In some aspects, the SI includes an RMSI. In some aspects, the one or more trigger criteria include a first RSRP threshold. In some aspects, the process 500 includes determining a first SSB-based RSRP, and determining that the one or more trigger criteria are satisfied includes determining that the first SSB-based RSRP satisfies the first RSRP threshold. In some aspects, the one or more trigger criteria include a second RSRP threshold. In some aspects, the process 500 includes determining a second SSB-based RSRP, and determining that the one or more trigger criteria are satisfied includes determining that the second SSB-based RSRP satisfies the second RSRP threshold.

[0103] 5, in some aspects, process 500 may include selecting one or more PRACH parameters based at least in part on a relationship between the one or more PRACH parameters and one or more request parameters corresponding to a request for PUSCH repetitions (block 540). For example, a UE (e.g., using the determining component 908 shown in FIG. 9) may select one or more PRACH parameters based at least in part on a relationship between the one or more PRACH parameters and one or more request parameters corresponding to a request for PUSCH repetitions.

[0104] As shown in FIG. 5, in some aspects, the process 500 may include transmitting a request for PUSCH repetitions associated with an RRC connection request message of the RACH procedure to a base station (block 550). For example, a UE (e.g., using the transmitting component 904 shown in FIG. 9) may transmit a request for PUSCH repetitions associated with an RRC connection request message of the RACH procedure to a base station as described above. In some aspects, transmitting the request for PUSCH repetitions includes transmitting the request for PUSCH repetitions based at least in part on determining that one or more trigger criteria are satisfied. For example, in some aspects, the request for PUSCH repetitions indicates a first number of requested PUSCH repetitions based at least in part on determining that a first SSB-based RSRP satisfies a first RSRP threshold, and the request for PUSCH repetitions indicates a second number of requested PUSCH repetitions based at least in part on determining that a second SSB-based RSRP satisfies a second RSRP threshold.

[0105] In some aspects, the request for PUSCH repetitions indicates one or more proposed parameters corresponding to PUSCH repetitions. In some aspects, the one or more proposed parameters indicate a number of PUSCH repetitions. In some aspects, the request for PUSCH repetitions indicates a request for an aggregated demodulation reference signal for cross-slot channel estimation. In some aspects, the request for PUSCH repetitions includes a request for PUSCH repetitions associated with one or more transmission configuration indicators. In some aspects, the request for PUSCH repetitions includes a request for PUSCH repetitions with frequency hopping.

[0106] In some aspects, transmitting the request for PUSCH repetitions includes transmitting a PRACH message indicating the request for PUSCH repetitions. In some aspects, transmitting the request for PUSCH repetitions includes repeating the PRACH message over multiple RACH opportunities. In some aspects, transmitting the request for PUSCH repetitions includes transmitting a PRACH preamble selected from a subset of PRACH preambles of the set of PRACH preambles, the subset indicating the request for PUSCH repetitions. In some aspects, transmitting the request for PUSCH repetitions includes transmitting the PRACH message using a subset of ROs of the set of ROs, the subset of ROs indicating the request for PUSCH repetitions. In some aspects, transmitting the request for PUSCH repetitions includes transmitting the PRACH message using a PRACH format indicating the request for PUSCH repetitions. In some aspects, transmitting the PRACH message includes transmitting the PRACH message based at least in part on one or more PRACH parameters.

[0107] As shown in FIG. 5, in some aspects, the process 500 may include receiving an indication of a PUSCH repeat request grant from a base station, the PUSCH repeat request grant corresponding to at least a portion of the PUSCH repeat request (block 560). For example, a UE (e.g., using the receiving component 902 shown in FIG. 9) may receive an indication of a PUSCH repeat request grant from a base station, the PUSCH repeat request grant corresponding to at least a portion of the PUSCH repeat request. In some aspects, the indication of the PUSCH repeat request grant is carried in a RAR message. In some aspects, the indication of the PUSCH repeat request grant is carried in a physical downlink control channel portion of the RAR message.

[0108] In some aspects, the process 500 includes receiving an RAR message from a base station, the RAR message indicating at least one of a PUSCH resource for an RRC connection request message or a PUSCH parameter associated with the RRC connection request message, and determining at least one of a PUSCH repetition parameter or a PUSCH repetition resource based at least in part on the RAR message. In some aspects, determining at least one of a PUSCH repetition parameter or a PUSCH repetition resource includes determining at least one of a PUSCH repetition parameter or a PUSCH repetition resource based at least in part on one or more rules indicated by a wireless communications standard.

[0109] 5, in some aspects, the process 500 may include transmitting at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request (block 570). For example, the UE (e.g., using the transmitting component 904 shown in FIG. 9) may transmit at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request, as described above. In some aspects, transmitting the at least one PUSCH repetition includes transmitting the at least one PUSCH repetition based at least in part on transmitting a request for the PUSCH repetition.

[0110] Process 500 may include additional aspects, such as any single aspect or any combination of aspects described above and / or with respect to one or more other processes described elsewhere herein. Although Figure 5 illustrates example blocks of process 500, in some aspects process 500 may include additional blocks, fewer blocks, different blocks, or blocks ordered differently than those illustrated in Figure 5. Additionally or alternatively, two or more of the blocks of process 500 may be performed in parallel.

[0111] 6 illustrates an example process 600, performed, for example, by a UE, in accordance with the present disclosure. The example process 600 is an example in which a UE (e.g., UE 405) performs operations associated with a request for PUSCH repetition associated with an RRC connection request message during a RACH procedure.

[0112] As shown in FIG. 6, in some aspects, process 600 may include receiving resource parameters from a base station indicating one or more alternating frequency resources (block 610). For example, a UE (e.g., using receiving component 902 shown in FIG. 9) may receive resource parameters from a base station indicating one or more alternating frequency resources as described above. In some aspects, the resource parameters are received via SI. In some aspects, the SI includes RMSI. In some aspects, the resource parameters include a frequency offset.

[0113] 6, in some aspects, process 600 may include determining one or more alternating frequency resources for PRACH transmission, where the one or more alternating frequency resources are used to communicate PUSCH repetition information (block 620). For example, a UE (e.g., using determining component 908 shown in FIG. 9) may determine one or more alternating frequency resources for PRACH transmission, where the one or more alternating frequency resources are used to communicate PUSCH repetition information, as described above.

[0114] In some aspects, the one or more alternate frequency resources are different from the one or more frequency resources for the PRACH transmission associated with the single PUSCH transmission without PUSCH repetition. In some aspects, the one or more alternative frequency resources are determined based on a resource parameter. In some aspects, determining the one or more alternate frequency resources includes determining the one or more alternate frequency resources by applying a frequency offset to the one or more frequency resources for the PRACH transmission associated with the single PUSCH transmission without PUSCH repetition.

[0115] 6, in some aspects, the process 600 may include transmitting a PRACH message to the base station using one or more alternating frequency resources for communicating the PUSCH repetition information (block 630). For example, a UE (e.g., using the transmitting component 904 shown in FIG. 9) may transmit a PRACH message to the base station using one or more alternating frequency resources for communicating the PUSCH repetition information, as described above.

[0116] In some aspects, the PUSCH repetition information indicates one or more parameters corresponding to at least one of a request for PUSCH repetition or an indication of UE capability for PUSCH repetition. In some aspects, the one or more parameters include at least one of the request for PUSCH repetition, the indication of UE capability, the number of PUSCH repetitions, an indication that at least one of the request for PUSCH repetition or the indication of UE capability is associated with a PUSCH repetition with DMRS aggregation for cross-slot channel estimation, an indication that the PUSCH repetition is associated with one or more TCIs, or an indication that at least one of the request for PUSCH repetition or the indication of UE capability is associated with a PUSCH repetition with frequency hopping. In some aspects, the one or more alternating frequency resources are different for each of the one or more parameters.

[0117] 6, in some aspects, the process 600 may include receiving at least one of an indication of one or more PUSCH resources or PUSCH parameters based on the PUSCH repetition information (block 640). For example, a UE (e.g., using the receiving component 902 shown in FIG. 9) may receive at least one of an indication of one or more PUSCH resources or PUSCH parameters based on the PUSCH repetition information, as described above.

[0118] As further shown in FIG. 6, in some aspects, the process 600 may include determining at least one transmit power parameter associated with a transmit power for the PUSCH repetition (block 650). For example, the UE (e.g., using the determining component 908 shown in FIG. 9) may determine the at least one transmit power parameter associated with a transmit power for the PUSCH repetition as described above. As further shown in FIG. 6, in some aspects, the process 600 may include configuring a transmit power for the PUSCH repetition based on the at least one transmit power parameter (block 660). For example, the UE (e.g., using the transmitting component 904 shown in FIG. 9) may configure a transmit power for the PUSCH repetition based on the at least one transmit power parameter as described above.

[0119] In some aspects, the at least one transmit power parameter is determined based on the one or more alternating frequency resources determined for the PRACH transmission. In some aspects, determining the at least one transmit power parameter includes receiving the at least one transmit power parameter from a base station. In some aspects, the at least one transmit power parameter includes a power offset value between a transmit power for the PUSCH repetition and a second transmit power for the PRACH transmission.

[0120] As further shown in FIG. 6, in some aspects, the process 600 may include transmitting the PUSCH message and at least one repetition of the PUSCH message based on the PUSCH repetition information (block 670). For example, a UE (e.g., using the transmitting component 904 shown in FIG. 9) may transmit the PUSCH message and at least one repetition of the PUSCH message based on the PUSCH repetition information, as described above. In some aspects, the PUSCH message and at least one repetition of the PUSCH message are transmitted using at least one of one or more PUSCH resources or PUSCH parameters.

[0121] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or with respect to one or more other processes described elsewhere herein. Although Figure 6 illustrates example blocks of process 600, in some aspects process 600 may include additional, fewer, different, or differently ordered blocks compared to the blocks illustrated in Figure 6. Additionally or alternatively, two or more of the blocks of process 600 may be performed in parallel.

[0122] 7 illustrates an example process 700 implemented, for example, by a base station, in accordance with the present disclosure. The example process 700 is an example in which a base station (e.g., base station 410) performs operations associated with a request for PUSCH repetitions associated with an RRC connection request message during a RACH procedure.

[0123] As shown in FIG. 7, in some aspects, process 700 may include transmitting (block 710) a parameter configuration to the UE indicating a relationship between one or more PRACH parameters and one or more request parameters corresponding to a request for PUSCH repetitions. For example, a base station (e.g., using the transmitting component 1104 shown in FIG. 11) may transmit to the UE a parameter configuration indicating a relationship between one or more PRACH parameters and one or more request parameters corresponding to a request for PUSCH repetitions, as described above. In some aspects, the parameter configuration is carried in SI. In some aspects, the SI includes RMSI. In some aspects, the relationship is indicated by a wireless communication standard.

[0124] As shown in FIG. 7, in some aspects, process 700 may include transmitting a trigger configuration to the UE indicating the one or more trigger criteria (block 720). For example, a base station (e.g., using transmitting component 1104 shown in FIG. 11) may transmit the trigger configuration to the UE indicating the one or more trigger criteria as described above. In some aspects, the trigger configuration is carried in SI. In some aspects, the SI includes RMSI. In some aspects, the one or more trigger criteria include a first RSRP threshold. In some aspects, the one or more trigger criteria are indicated in a wireless communication standard.

[0125] 7, in some aspects, process 700 may include receiving a request from the UE for PUSCH repetitions associated with an RRC connection request message of the RACH procedure (block 730). For example, a base station (e.g., using the receiving component 1102 shown in FIG. 11) may receive a request from the UE for PUSCH repetitions associated with an RRC connection request message of the RACH procedure, as described above.

[0126] In some aspects, the request for PUSCH repetitions indicates one or more proposed parameters corresponding to PUSCH repetitions. In some aspects, the one or more proposed parameters indicate a number of PUSCH repetitions. In some aspects, the request for PUSCH repetitions indicates a request for an aggregated demodulation reference signal for cross-slot channel estimation. In some aspects, the request for PUSCH repetitions includes a request for PUSCH repetitions associated with one or more transmission configuration indicators. In some aspects, the request for PUSCH repetitions includes a request for PUSCH repetitions with frequency hopping.

[0127] In some aspects, receiving the request for PUSCH repetition includes receiving a PRACH message indicating a request for PUSCH repetition. In some aspects, receiving the request for PUSCH repetition includes receiving a repeated PRACH message over multiple RACH opportunities. In some aspects, receiving the request for PUSCH repetition includes receiving a PRACH preamble selected from a subset of PRACH preambles of a set of PRACH preambles, the subset indicating a request for PUSCH repetition. In some aspects, receiving the request for PUSCH repetition includes receiving a PRACH message using a subset of ROs of a set of ROs, the subset of ROs indicating a request for PUSCH repetition.

[0128] In some aspects, receiving the request for PUSCH repetitions includes receiving a PRACH message with a PRACH format indicating the request for PUSCH repetitions. In some aspects, receiving the PRACH message includes receiving a PRACH message based at least in part on one or more PRACH parameters. In some aspects, the selection of the one or more PRACH parameters is based at least in part on a relationship between the one or more PRACH parameters and one or more request parameters corresponding to the request for PUSCH repetitions.

[0129] As shown in FIG. 7, in some aspects, the process 700 may include transmitting an indication of a PUSCH repeat request grant to the UE, where the PUSCH repeat request grant corresponds to at least a portion of the PUSCH repeat request (block 740). For example, a base station (e.g., using the transmitting component 1104 shown in FIG. 11) may transmit an indication of a PUSCH repeat request grant to the UE, where the PUSCH repeat request grant corresponds to at least a portion of the PUSCH repeat request, as described above. In some aspects, the indication of the PUSCH repeat request grant is carried in a RAR message. In some aspects, the indication of the PUSCH repeat request grant is carried in a PDCCH portion of the RAR message.

[0130] In some aspects, the process 700 includes transmitting an RAR message to the UE, the RAR message indicating at least one of a PUSCH resource for an RRC connection request message or a PUSCH parameter associated with the RRC connection request message. In some aspects, determining the at least one of the PUSCH repetition parameter or the PUSCH repetition resource includes determining the at least one of the PUSCH repetition parameter or the PUSCH repetition resource based at least in part on one or more rules set forth by a wireless communications standard.

[0131] 7, in some aspects, the process 700 may include receiving at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request (block 750). For example, a base station (e.g., using the receiving component 1102 shown in FIG. 11) may receive at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request, as described above. In some aspects, receiving the at least one PUSCH repetition includes receiving at least one PUSCH repetition based at least in part on the request for the PUSCH repetition.

[0132] In some aspects, receiving a request for PUSCH repetitions includes receiving a request for PUSCH repetitions based at least in part on a determination that one or more trigger criteria are satisfied. In some aspects, the determination that the one or more trigger criteria are satisfied includes a determination that a first SSB-based RSRP satisfies a first RSRP threshold. In some aspects, the one or more trigger criteria include a second RSRP threshold. In some aspects, the determination that the one or more trigger criteria are satisfied includes a determination that a second SSB-based RSRP satisfies a second RSRP threshold. In some aspects, the request for PUSCH repetitions indicates a first number of PUSCH repetitions requested based at least in part on a determination that the first SSB-based RSRP satisfies the first RSRP threshold, and the request for PUSCH repetitions indicates a second number of PUSCH repetitions requested based at least in part on a determination that the second SSB-based RSRP satisfies the second RSRP threshold.

[0133] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or with respect to one or more other processes described elsewhere herein. Although Figure 7 illustrates example blocks of process 700, in some aspects process 700 may include additional blocks, fewer blocks, different blocks, or blocks ordered differently than the blocks illustrated in Figure 7. Additionally or alternatively, two or more of the blocks of process 700 may be performed in parallel.

[0134] 8 illustrates an example process 800, implemented, for example, by a base station, in accordance with the present disclosure. The example process 800 is an example in which a base station (e.g., base station 410) performs operations associated with a request for PUSCH repetition associated with an RRC connection request message during a RACH procedure.

[0135] As shown in FIG. 8, in some aspects, process 800 may include transmitting resource parameters from a base station indicating one or more alternating frequency resources (block 810). For example, a base station (e.g., using transmitting component 1104 shown in FIG. 11) may transmit resource parameters from the base station indicating one or more alternating frequency resources as described above. In some aspects, the resource parameters are transmitted via SI. In some aspects, the SI includes RMSI. In some aspects, the resource parameters include a frequency offset.

[0136] As shown in FIG. 8, in some aspects, the process 800 may include receiving a PRACH message from the UE using one or more alternate frequency resources for the PRACH transmission (block 820). For example, a base station (e.g., using the receiving component 1102 shown in FIG. 11) may receive a PRACH message from the UE using one or more alternate frequency resources for the PRACH transmission as described above. In some aspects, the one or more alternate frequency resources are determined based on a resource parameter. In some aspects, the one or more alternate frequency resources are different from the one or more frequency resources for the PRACH transmission associated with the single PUSCH transmission without PUSCH repetition. In some aspects, the one or more alternate frequency resources are determined by applying a frequency offset to the one or more frequency resources for the PRACH transmission associated with the single PUSCH transmission without PUSCH repetition.

[0137] 8, in some aspects, the process 800 may include determining PUSCH repetition information based on one or more alternating frequency resources used to receive the PRACH message, where the PUSCH repetition information is communicated using the one or more alternating frequency resources (block 830). For example, the base station (e.g., using the determining component 1108 shown in FIG. 11) may determine PUSCH repetition information based on one or more alternating frequency resources used to receive the PRACH message, as described above, where the PUSCH repetition information is communicated using the one or more alternating frequency resources.

[0138] In some aspects, the PUSCH repetition information indicates one or more parameters corresponding to at least one of a request for PUSCH repetition or an indication of UE capability for PUSCH repetition. In some aspects, the one or more parameters include at least one of the request for PUSCH repetition, the indication of UE capability, the number of PUSCH repetitions, an indication that at least one of the request for PUSCH repetition or the indication of UE capability is associated with a PUSCH repetition with DMRS aggregation for cross-slot channel estimation, an indication that the PUSCH repetition is associated with one or more TCIs, or an indication that at least one of the request for PUSCH repetition or the indication of UE capability is associated with a PUSCH repetition with frequency hopping. In some aspects, the one or more alternating frequency resources are different for each of the one or more parameters.

[0139] 8, in some aspects, the process 800 may include transmitting at least one of an indication of one or more PUSCH resources or PUSCH parameters based on the PUSCH repetition information (block 840). For example, a base station (e.g., using the transmitting component 1104 shown in FIG. 11) may transmit at least one of an indication of one or more PUSCH resources or PUSCH parameters based on the PUSCH repetition information, as described above.

[0140] 8, in some aspects, the process 800 may include transmitting at least one transmit power parameter associated with a transmit power for the PUSCH repetition to the UE (block 850). For example, the base station (e.g., using the transmitting component 1104 shown in FIG. 11) may transmit at least one transmit power parameter associated with a transmit power for the PUSCH repetition to the UE, as described above.

[0141] In some aspects, the at least one transmit power parameter includes a power offset value between a transmit power for the PUSCH repetition and a second transmit power for the PRACH transmission. In some aspects, the transmit power for the PUSCH repetition is configured based on the at least one transmit power parameter associated with the transmit power. In some aspects, the at least one transmit power parameter is determined based on one or more alternating frequency resources determined for the PRACH transmission.

[0142] 8, in some aspects, the process 800 may include receiving the PUSCH message and at least one repetition of the PUSCH message from the UE based on the PUSCH repetition information (block 860). For example, a base station (e.g., using the receiving component 1102 shown in FIG. 11) may receive the PUSCH message and at least one repetition of the PUSCH message from the UE based on the PUSCH repetition information, as described above. In some aspects, the PUSCH message and at least one repetition of the PUSCH message are received using at least one of one or more PUSCH resources or PUSCH parameters.

[0143] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or with respect to one or more other processes described elsewhere herein. Although Figure 8 illustrates example blocks of process 800, in some aspects process 800 may include additional blocks, fewer blocks, different blocks, or blocks ordered differently than the blocks illustrated in Figure 8. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.

[0144] 9 is a block diagram of an example apparatus 900 for wireless communication. The apparatus 900 may be a UE, or a UE may include the apparatus 900. In some aspects, the apparatus 900 includes a receiving component 902 and a transmitting component 904, which may be in communication with one another (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using the receiving component 902 and the transmitting component 904. As further shown, the apparatus 900 may include a determining component 908.

[0145] In some aspects, the apparatus 900 may be configured to perform one or more operations described herein with respect to FIG. 4. Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as process 500 of FIG. 5, process 600 of FIG. 6, or some combination thereof. In some aspects, the apparatus 900 and / or one or more components illustrated in FIG. 9 may include one or more components of a UE described above with respect to FIG. 2. Additionally or alternatively, one or more components illustrated in FIG. 9 may be implemented within one or more components described above with respect to 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 processor to perform the function or operation of the component.

[0146] The receiving component 902 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 906. The receiving component 902 may provide the received communications to one or more other components of the apparatus 900. In some aspects, the receiving component 902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) and provide the processed signals to one or more other components of the apparatus 906. In some aspects, the receiving component 902 may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of a UE as described above with respect to FIG.

[0147] The transmitting component 904 may transmit a communication to the device 906, such as a reference signal, control information, a data communication, or a combination thereof. In some aspects, one or more other components of the device 906 may generate a communication and provide the generated communication to the transmitting component 904 for transmission to the device 906. In some aspects, the transmitting component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communication and may transmit the processed signal to the device 906. In some aspects, the transmitting component 904 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of a UE as described above in connection with FIG. 2. In some aspects, the transmitting component 904 may be co-located with the receiving component 902 in a transceiver.

[0148] The determining component 908 may determine one or more alternating frequency resources for PRACH transmission, where the one or more alternating frequency resources are used to communicate the PUSCH repetition information. In some aspects, the determining component 908 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of the UE described above in connection with FIG. 2. In some aspects, the determining component 908 may include the receiving component 902 and / or the transmitting component 904.

[0149] The transmitting component 904 may transmit the PRACH message to the base station using one or more alternate frequency resources for communicating the PUSCH repetition information. The receiving component 902 may receive a resource parameter from the base station indicating the one or more alternate frequency resources, where the one or more alternate frequency resources are determined based on the resource parameter.

[0150] The determining component 908 may be configured to determine that one or more trigger criteria are satisfied and trigger a PUSCH repetition request. The determining component 908 may determine at least one transmit power parameter associated with a transmit power for the PUSCH repetition. The transmitting component 904 may configure a transmit power for the PUSCH repetition based on the at least one transmit power parameter. The receiving component 902 may receive an indication of one or more PUSCH resources or at least one of the PUSCH parameters based on the PUSCH repetition information, and the PUSCH message and at least one repetition of the PUSCH message are transmitted using the one or more PUSCH resources or at least one of the PUSCH parameters.

[0151] The transmitting component 904 may transmit a request for PUSCH repetitions associated with an RRC connection request message of the RACH procedure to the base station. The transmitting component 904 may transmit at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request. The transmitting component 904 may transmit a PUSCH message and at least one repetition of the PUSCH message based on the PUSCH repetition information.

[0152] The number and arrangement of components shown in Figure 9 are given as an example. In practice, there may be additional components, fewer components, different components, or components arranged differently than those shown in Figure 9. Furthermore, two or more components shown in Figure 9 may be implemented within a single component, or a single component shown in Figure 9 may be implemented as multiple distributed components. Additionally or alternatively, a set of components (or components) shown in Figure 9 may perform one or more functions described as being performed by another set of components shown in Figure 9.

[0153] 10 is a block diagram illustrating an example of a hardware implementation for a UE 1000 utilizing a processing system 1014. For example, the UE 1000 may be a UE such as that shown in any one or more of Figures 1-4. In some aspects, the UE 1000 may be an apparatus 900 shown in Figure 9.

[0154] The UE 1000 may be implemented using a processing system 1014 including one or more processors 1004. Examples of the processor 1004 include a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, gate logic, discrete hardware circuitry, and other suitable hardware configured to perform various functions described throughout this disclosure. In various examples, the UE 1000 may be configured to perform any one or more of the functions described herein. That is, the processor 1004 as used within the UE 1000 may be used to implement any one or more of the processes and procedures described below and illustrated in Figures 5-6.

[0155] In this example, the processing system 1014 may be implemented with a bus architecture, generally represented by bus 1002. The bus 1002 may include any number of interconnecting buses and bridges, depending on the particular application and overall design constraints of the processing system 1014. The bus 1002 communicatively couples various circuits, including one or more processors (schematically represented by processor 1004), memory 1005, and computer-readable media (schematically represented by computer-readable storage media 1006), to one another. The bus 1002 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. The bus interface 1008 provides an interface between the bus 1002 and the transceiver 1010. The transceiver 1010 provides a communication interface or means for communicating with various other devices over a transmission medium. Depending on the nature of the device, a user interface 1012 (eg, keypad, display, speaker, microphone, joystick) may also be provided.

[0156] In some aspects of the disclosure, the processor 1004 may include resource management circuitry 1040 configured for various functions including, for example, determining communication resources to be used. For example, in some aspects, the resource management circuitry 1040 may include or be included in the determining component 908 shown in FIG. 9. In some aspects of the disclosure, the processor 1004 may include communication management circuitry 1042 configured for various functions including, for example, transmitting and receiving communications. For example, in some aspects, the communication management circuitry 1042 may include or be included in the receiving component 902 and / or the transmitting component 904 shown in FIG. 9. In some aspects of the disclosure, the processor 1004 may include transmit power management circuitry 1044 configured for various functions including, for example, determining and configuring transmit power for a transmission. For example, in some aspects, the transmit power management circuitry 1044 may include or be included in the determining component 908 and / or the transmitting component 904 shown in FIG. 9.

[0157] The processor 1004 is responsible for managing the bus 1002 and for general processing, including the execution of software stored on the computer-readable storage medium 1006. The software, when executed by the processor 1004, causes the processing system 1014 to perform various functions, described below for any particular apparatus. The computer-readable storage medium 1006 and memory 1005 may also be used for storing data that is manipulated by the processor 1004 when executing software.

[0158] The one or more processors 1004 in the processing system may execute software. Software should be interpreted broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on a computer-readable storage medium 1006. The computer-readable storage medium 1006 may be a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media include, by way of example, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disks (CDs) or digital versatile disks (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. The computer-readable storage medium 1006 may reside within the processing system 1014, external to the processing system 1014, or distributed across multiple entities including the processing system 1014. The computer-readable storage medium 1006 may be embodied in a computer program product. By way of example, the computer program product may include the computer-readable storage medium in packaging materials. Depending on the particular application and the overall design constraints imposed on the overall system, one skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure.

[0159] In one or more examples, the computer-readable storage medium 1006 may include resource management software / instructions 1060 configured for various functions including, for example, determining a communications resource to be used. For example, the resource management software / instructions 1060 may include or be included in the determining component 908 shown in FIG. 9. In one or more examples, the computer-readable storage medium 1006 may include communications management software / instructions 1062 configured for various functions including, for example, transmitting and receiving communications. For example, the communications management software / instructions 1062 may include or be included in the receiving component 902 and / or the transmitting component 904 shown in FIG. 9. In one or more examples, the computer-readable storage medium 1006 may include transmit power management software / instructions 1064 configured for various functions including, for example, determining and configuring a transmit power for a transmission. For example, the transmit power management software / instructions 1064 may include or be included in the determining component 908 and / or the transmitting component 904 shown in FIG. 9.

[0160] The number and arrangement of components shown in Figure 10 are given as an example. In practice, there may be additional components, fewer components, different components, or components arranged differently compared to those shown in Figure 10. Furthermore, two or more components shown in Figure 10 may be implemented within a single component, or a single component shown in Figure 10 may be implemented as multiple distributed components. Additionally or alternatively, a set of components (or components) shown in Figure 10 may perform one or more functions described as being performed by another set of components shown in Figure 10.

[0161] 11 is a block 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. In some aspects, the apparatus 1100 includes a receiving component 1102 and a transmitting component 1104, which may be in communication with one another (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using the receiving component 1102 and the transmitting component 1104. As further shown, the apparatus 1100 may include a determining component 1108.

[0162] In some aspects, the apparatus 1100 may be configured to perform one or more operations described herein with respect to FIG. 4. Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as process 700 of FIG. 7, process 800 of FIG. 8, or a combination thereof. In some aspects, the apparatus 1100 and / or one or more components illustrated in FIG. 11 may include one or more components of a base station described above with respect to FIG. 2. Additionally or alternatively, one or more components illustrated in FIG. 11 may be implemented within one or more components described above with respect to 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 processor to perform the function or operation of the component.

[0163] The receiving component 1102 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 1106. The receiving component 1102 may provide the received communications to one or more other components of the apparatus 1100. In some aspects, the receiving component 1102 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) and provide the processed signals to one or more other components of the apparatus 1106. In some aspects, the receiving component 1102 may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of a base station as described above with respect to FIG.

[0164] The transmitting component 1104 may transmit a communication, such as a reference signal, control information, a data communication, or a combination thereof, to the device 1106. In some aspects, one or more other components of the device 1106 may generate a communication and provide the generated communication to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplifying, modulating, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communication and may transmit the processed signal to the device 1106. In some aspects, the transmitting component 1104 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the base station described above in connection with FIG. 2. In some aspects, the transmitting component 1104 may be co-located with the receiving component 1102 in a transceiver.

[0165] The receiving component 1102 may receive a request for PUSCH repetition from the UE associated with an RRC connection request message of the RACH procedure. The receiving component 1102 may receive a PRACH message from the UE using one or more alternating frequency resources for PRACH transmission.

[0166] The determining component 1108 may determine the PUSCH repetition information based on one or more alternating frequency resources used to receive the PRACH message, where the PUSCH repetition information is communicated using the one or more alternating frequency resources. In some aspects, the determining component 1108 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof of the base station described above with respect to FIG. 2. In some aspects, the determining component 1108 may include the receiving component 1102 and / or the transmitting component 1104.

[0167] The receiving component 1102 may receive a PUSCH message and at least one repetition of the PUSCH message from the UE based on the PUSCH repetition information. The receiving component 1102 may receive at least one PUSCH repetition associated with an RRC connection request message based at least in part on the request. The determining component 1108 may determine that the PRACH message indicates a PUSCH repetition request.

[0168] The transmitting component 1104 may transmit at least one of an indication of one or more PUSCH resources or PUSCH parameters based on the PUSCH repetition information, where the PUSCH message and at least one repetition of the PUSCH message are received using at least one of the one or more PUSCH resources or PUSCH parameters. The transmitting component 1104 may transmit a resource parameter indicating one or more alternate frequency resources from the base station, where the one or more alternate frequency resources are determined based on the resource parameter. The transmitting component 1104 may transmit at least one transmit power parameter to the UE.

[0169] The number and arrangement of components shown in Figure 11 are given as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components compared to those shown in Figure 11. Furthermore, two or more components shown in Figure 11 may be implemented within a single component, or a single component shown in Figure 11 may be implemented as multiple distributed components. Additionally or alternatively, a set of components (or components) shown in Figure 11 may perform one or more functions described as being performed by another set of components shown in Figure 11.

[0170] 12 is a conceptual diagram illustrating an example of a hardware implementation for an exemplary base station 1200 utilizing a processing system 1214. According to various aspects of the disclosure, the elements, or any portion of the elements, or any combination of the elements, may be implemented using a processing system 1214 including one or more processors 1204. For example, the base station 1200 may be a base station as shown in any one or more of FIGS. 1-4. In some aspects, the base station 1200 may be the apparatus 1100 shown in FIG. 11.

[0171] The processing system 1214 may be substantially similar to the processing system 1014 shown in Figure 10, including a bus interface 1208, a bus 1202, a memory 1205, a processor 1204, and a computer-readable storage medium 1206. Additionally, the base station 1200 may include a user interface 1212 and a transceiver 1210 substantially similar to those described above in Figure 10. That is, the processor 1204 as used within the base station 1200 may be used to implement any one or more of the processes described below and illustrated in Figures 7-8.

[0172] In some aspects of the disclosure, the processor 1204 may include a communication management circuitry 1240 configured for various functions including, for example, transmitting and receiving communications. For example, the communication management circuitry 1240 may include or be included in the receiving component 1102 and / or the transmitting component 1104 shown in FIG. 11. In some aspects of the disclosure, the processor 1204 may include a resource management circuitry 1242 configured for various functions including, for example, determining a communication resource to be used. For example, the resource management circuitry 1242 may include or be included in the determining component 1108 shown in FIG. 11. In some aspects of the disclosure, the processor 1204 may include a transmit power management circuitry 1244 configured for various functions including, for example, determining and configuring a transmit power for a transmission. For example, the transmit power management circuitry 1244 may include or be included in the determining component 1108 and / or the transmitting component 1104 shown in FIG. 11.

[0173] In one or more examples, the computer-readable storage medium 1206 may include communications management software / instructions 1260 configured for various functions including, for example, transmitting and receiving communications. For example, the communications management software / instructions 1260 may include or be included in the receiving component 1102 and / or the transmitting component 1104 shown in FIG. 11 . In one or more examples, the computer-readable storage medium 1206 may include resource management software / instructions 1262 configured for various functions including, for example, determining communications resources to be used. For example, the resource management software / instructions 1262 may include or be included in the determining component 1108 shown in FIG. 11 . In one or more examples, the computer-readable storage medium 1206 may include transmit power management software / instructions 1264 configured for various functions including, for example, determining and configuring transmit power for a transmission. For example, the transmit power management software / instructions 1264 may include or be included in the determining component 1108 and / or the transmitting component 1104 shown in FIG. 11 .

[0174] The following provides a summary of several aspects of the disclosure.

[0175] Aspect 1: A method of wireless communications implemented by a user equipment (UE), comprising: transmitting, to a base station, a request for physical uplink shared channel (PUSCH) repetitions associated with a radio resource control (RRC) connection request message of a random access channel (RACH) procedure; and transmitting at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.

[0176] Example 2: The method of example 1, wherein the request for a PUSCH repetition indicates one or more proposed parameters corresponding to the PUSCH repetition.

[0177] Example 3: The method of example 2, wherein the one or more proposed parameters indicate a number of PUSCH repetitions.

[0178] Example 4: The method of any of Examples 1-3, wherein the request for PUSCH repetition indicates a request for aggregated demodulation reference signals for cross-slot channel estimation.

[0179] Example 5: The method of any of Examples 1-4, wherein the request for PUSCH repetition includes a request for PUSCH repetition associated with one or more transmission configuration indicators.

[0180] Example 6: The method of any of Examples 1 to 5, wherein the request for PUSCH repetition includes a request for PUSCH repetition with frequency hopping.

[0181] Aspect 7: The method of any of aspects 1-6, wherein transmitting the request for PUSCH repetition includes transmitting a Physical RACH (PRACH) message indicating the request for PUSCH repetition.

[0182] Aspect 8: The method of aspect 7, wherein the step of transmitting the request for PUSCH repetition includes repeating the PRACH message over multiple RACH opportunities.

[0183] Aspect 9: The method of any of aspects 7 or 8, wherein the step of transmitting a request for PUSCH repetition includes transmitting a PRACH preamble selected from a subset of PRACH preambles of the set of PRACH preambles, the subset indicating a request for PUSCH repetition.

[0184] Aspect 10: The method of any of aspects 7 to 9, wherein the step of transmitting a request for PUSCH repetition includes a step of transmitting a PRACH message using a subset of RACH opportunities (ROs) from a set of ROs, the subset of ROs indicating a request for PUSCH repetition.

[0185] Aspect 11: The method of any of aspects 7-10, wherein the step of transmitting the request for PUSCH repetition includes the step of transmitting a PRACH message using a PRACH format indicating the request for PUSCH repetition.

[0186] Aspect 12: The method of any of aspects 7-11, wherein transmitting the PRACH message includes transmitting the PRACH message based at least in part on one or more PRACH parameters.

[0187] Aspect 13: The method of aspect 12, further comprising selecting one or more PRACH parameters based at least in part on a relationship between the one or more PRACH parameters and one or more request parameters corresponding to a request for PUSCH repetitions.

[0188] Aspect 14: The method of aspect 13, further comprising receiving a parameter configuration from a base station indicative of the relationship.

[0189] Aspect 15: The method of aspect 14, wherein the parameter configuration is conveyed in system information.

[0190] Aspect 16: The method of aspect 15, wherein the system information includes remaining minimum system information.

[0191] Aspect 17: The method of any of aspects 13-16, wherein the relationship is indicated by a wireless communication standard.

[0192] Aspect 18: The method of any of aspects 1-17, further comprising determining that one or more trigger criteria are satisfied, and wherein transmitting the request for PUSCH repetition comprises transmitting the request for PUSCH repetition based at least in part on determining that the one or more trigger criteria are satisfied.

[0193] Aspect 19: The method of aspect 18, further comprising receiving a trigger configuration from a base station indicating one or more trigger criteria.

[0194] Aspect 20: The method of aspect 19, wherein the trigger configuration is conveyed in system information.

[0195] Aspect 21: The method of aspect 20, wherein the system information includes remaining minimum system information.

[0196] Example 22: The method of any of examples 18-21, wherein the one or more trigger criteria includes a first reference signal received power (RSRP) threshold.

[0197] Aspect 23: The method of aspect 22, further comprising determining a first synchronization signal block (SSB) based RSRP, wherein determining that one or more trigger criteria are satisfied comprises determining that the first SSB based RSRP satisfies a first RSRP threshold.

[0198] Example 24: The method of example 23, wherein the one or more trigger criteria includes a second RSRP threshold.

[0199] Aspect 25: The method of aspect 24, further comprising determining a second SSB-based RSRP, wherein determining that the one or more trigger criteria are satisfied comprises determining that the second SSB-based RSRP satisfies a second RSRP threshold.

[0200] Aspect 26: The method of aspect 25, wherein the request for PUSCH repetitions indicates a first number of requested PUSCH repetitions based at least in part on determining that the first SSB-based RSRP satisfies a first RSRP threshold, and the request for PUSCH repetitions indicates a second number of requested PUSCH repetitions based at least in part on determining that the second SSB-based RSRP satisfies a second RSRP threshold.

[0201] Example 27: The method of any of examples 18 to 27, wherein the one or more trigger criteria are specified in a wireless communication standard.

[0202] Aspect 28: The method of any of aspects 1-27, wherein the step of transmitting the at least one PUSCH repetition includes the step of transmitting the at least one PUSCH repetition based at least in part on transmitting a request for the PUSCH repetition.

[0203] Aspect 29: The method of any of aspects 1-28, further comprising: receiving a random access response (RAR) message from the base station, the RAR message indicating at least one of a PUSCH resource for an RRC connection request message or a PUSCH parameter associated with the RRC connection request message; and determining at least one of a PUSCH repetition parameter or a PUSCH repetition resource based at least in part on the RAR message.

[0204] Aspect 30: The method of aspect 29, wherein determining at least one of a PUSCH repetition parameter or a PUSCH repetition resource includes determining at least one of a PUSCH repetition parameter or a PUSCH repetition resource based at least in part on one or more rules set forth by a wireless communication standard.

[0205] Aspect 31: The method of any of aspects 1-30, further comprising receiving an indication of a PUSCH repetition request grant from the base station, the PUSCH repetition request grant corresponding to at least a portion of the PUSCH repetition request.

[0206] Example 32: The method of example 31, wherein the indication of the PUSCH repetition request grant is carried in a random access response (RAR) message.

[0207] Aspect 33: The method of aspect 32, wherein the indication of the PUSCH repetition request grant is carried within a physical downlink control channel portion of the RAR message.

[0208] Aspect 34: A method of wireless communication implemented by a base station, the method including: receiving, from a user equipment (UE), a request for physical uplink shared channel (PUSCH) repetitions associated with a radio resource control (RRC) connection request message of a random access channel (RACH) procedure; and receiving, based at least in part on the request, at least one PUSCH repetition associated with the RRC connection request message.

[0209] Example 35: The method of example 34, wherein the request for the PUSCH repetition indicates one or more proposed parameters corresponding to the PUSCH repetition.

[0210] Example 36: The method of example 35, wherein the one or more proposed parameters indicate a number of PUSCH repetitions.

[0211] Example 37: The method of any of Examples 34-36, wherein the request for PUSCH repetition indicates a request for aggregated demodulation reference signals for cross-slot channel estimation.

[0212] Example 38: The method of any of examples 34-37, wherein the request for PUSCH repetitions includes a request for PUSCH repetitions associated with one or more transmission configuration indicators.

[0213] Example 39: The method of any of Examples 34 to 38, wherein the request for PUSCH repetitions includes a request for PUSCH repetitions with frequency hopping.

[0214] Example 40: The method of any of Examples 34-39, wherein receiving the request for PUSCH repetition includes receiving a Physical RACH (PRACH) message indicating the request for PUSCH repetition.

[0215] Aspect 41: The method of aspect 40, wherein receiving a request for PUSCH repetition includes receiving a repeated PRACH message over multiple RACH opportunities.

[0216] Aspect 42: The method of any of aspects 40 or 41, wherein the step of receiving a request for PUSCH repetition includes the step of receiving a PRACH preamble selected from a subset of PRACH preambles of the set of PRACH preambles, the subset indicating a request for PUSCH repetition.

[0217] Aspect 43: The method of any of aspects 40 to 42, wherein the step of receiving a request for PUSCH repetition includes a step of receiving a PRACH message using a subset of RACH opportunities (ROs) out of a set of ROs, the subset of ROs indicating a request for PUSCH repetition.

[0218] Aspect 44: The method of any of aspects 40 to 43, wherein receiving the request for PUSCH repetition includes receiving a PRACH message using a PRACH format indicating the request for PUSCH repetition.

[0219] Aspect 45: The method of any of aspects 40-44, wherein receiving the PRACH message includes receiving the PRACH message based at least in part on one or more PRACH parameters.

[0220] Aspect 46: The method of aspect 45, wherein the selection of the one or more PRACH parameters is based at least in part on a relationship between the one or more PRACH parameters and one or more request parameters corresponding to a request for PUSCH repetitions.

[0221] Aspect 47: The method of aspect 46, further comprising transmitting a parameter configuration to the UE indicating the relationship.

[0222] Aspect 48: The method of any of aspects 46 or 47, wherein the parameter configuration is conveyed in system information.

[0223] Aspect 49: The method of aspect 48, wherein the system information includes remaining minimum system information.

[0224] Aspect 50: The method of any of aspects 46-49, wherein the relationship is indicated by a wireless communication standard.

[0225] Aspect 51: The method of any of aspects 34 to 50, wherein receiving a request for PUSCH repetition includes receiving a request for PUSCH repetition based at least in part on a determination that one or more trigger criteria are satisfied.

[0226] Aspect 52: The method of aspect 51, further comprising the step of transmitting a trigger configuration to the UE indicating one or more trigger criteria.

[0227] Aspect 53: The method of aspect 52, wherein the trigger configuration is conveyed within system information.

[0228] Aspect 54: The method of aspect 53, wherein the system information includes remaining minimum system information.

[0229] Example 55: The method of any of examples 51-54, wherein the one or more trigger criteria includes a first reference signal received power (RSRP) threshold.

[0230] Aspect 56: The method of aspect 55, wherein the determination that the one or more trigger criteria are satisfied includes a determination that a first synchronization signal block (SSB)-based RSRP satisfies a first RSRP threshold.

[0231] Embodiment 57: The method of embodiment 56, wherein the one or more trigger criteria includes a second RSRP threshold.

[0232] Aspect 58: The method of aspect 57, wherein the determination that the one or more trigger criteria are satisfied includes a determination that the second SSB-based RSRP satisfies a second RSRP threshold.

[0233] Aspect 59: The method of aspect 58, wherein the request for PUSCH repetitions indicates a first number of requested PUSCH repetitions based at least in part on a determination that the first SSB-based RSRP satisfies a first RSRP threshold, and the request for PUSCH repetitions indicates a second number of requested PUSCH repetitions based at least in part on a determination that the second SSB-based RSRP satisfies a second RSRP threshold.

[0234] Aspect 60: The method of any of aspects 51 to 60, wherein the one or more trigger criteria are specified in a wireless communication standard.

[0235] Example 61: The method of any of Examples 34-60, wherein receiving the at least one PUSCH repetition includes receiving the at least one PUSCH repetition based at least in part on a request for the PUSCH repetition.

[0236] Aspect 62: The method of any of aspects 34 to 61, further comprising the step of transmitting a random access response (RAR) message to the UE, the RAR message indicating at least one of a PUSCH resource for the RRC connection request message or a PUSCH parameter associated with the RRC connection request message.

[0237] Aspect 63: The method of aspect 62, wherein determining at least one of a PUSCH repetition parameter or a PUSCH repetition resource includes determining at least one of a PUSCH repetition parameter or a PUSCH repetition resource based at least in part on one or more rules set forth by a wireless communication standard.

[0238] Example 64: The method of any of Examples 34 to 63, further comprising: sending an indication of a PUSCH repetition request grant to the UE, the PUSCH repetition request grant corresponding to at least a portion of the PUSCH repetition request.

[0239] Aspect 65: The method of aspect 64, wherein the indication of the PUSCH repetition request grant is carried in a random access response (RAR) message.

[0240] Aspect 66: The method of any of aspects 64 or 65, wherein the indication of the PUSCH repetition request grant is carried within a physical downlink control channel portion of the RAR message.

[0241] Aspect 67: A method of wireless communication by a user equipment (UE), comprising: determining one or more alternating frequency resources for physical random access channel (PRACH) transmission, wherein physical uplink shared channel (PUSCH) repetition information is communicated using the one or more alternating frequency resources; and transmitting a PRACH message to a base station using the one or more alternating frequency resources for communicating the PUSCH repetition information.

[0242] Aspect 68: The method of aspect 67, wherein the one or more alternating frequency resources are different from the one or more frequency resources for a PRACH transmission associated with a single PUSCH transmission without PUSCH repetition.

[0243]

[0081] Aspect 69: The method of any of aspects 67 or 68, further comprising transmitting the PUSCH message and at least one repetition of the PUSCH message based on the PUSCH repetition information.

[0244] Example 70: The method of any of Examples 67 to 69, further comprising receiving an indication of one or more PUSCH resources or at least one of PUSCH parameters based on the PUSCH repetition information, wherein the PUSCH message and at least one repetition of the PUSCH message are transmitted using the one or more PUSCH resources or at least one of the PUSCH parameters.

[0245] Aspect 71: The method of any of aspects 67-70, further comprising receiving a resource parameter from the base station indicating one or more alternate frequency resources, wherein the one or more alternate frequency resources are determined based on the resource parameter.

[0246] Aspect 72: The method of aspect 71, wherein the resource parameters are received via system information.

[0247] Aspect 73: The method of aspect 72, wherein the system information includes Minimum Residual System Information (RMSI).

[0248] Aspect 74: The method of any of aspects 71 to 73, wherein the resource parameter includes a frequency offset, and determining the one or more alternate frequency resources includes determining the one or more alternate frequency resources by applying a frequency offset to one or more frequency resources for a PRACH transmission associated with a single PUSCH transmission without PUSCH repetition.

[0249] Example 75: The method of any of Examples 67 to 74, further comprising: determining at least one transmit power parameter associated with a transmit power for the PUSCH repetition; and configuring a transmit power for the PUSCH repetition based on the at least one transmit power parameter.

[0250] Aspect 76: The method of aspect 75, wherein the at least one transmit power parameter is determined based on one or more alternating frequency resources determined for the PRACH transmission.

[0251] Aspect 77: The method of any of aspects 75 or 76, wherein the step of determining the at least one transmit power parameter includes the step of receiving the at least one transmit power parameter from a base station.

[0252] Example 78: The method of any of examples 75-77, wherein the at least one transmit power parameter includes a power offset value between a transmit power for the PUSCH repetition and a second transmit power for the PRACH transmission.

[0253] Example 79: The method of any of Examples 67-78, wherein the PUSCH repetition information indicates one or more parameters corresponding to at least one of a request for PUSCH repetition or an indication of UE capability for PUSCH repetition.

[0254] Aspect 80: The method of aspect 79, wherein the one or more parameters include at least one of a request for PUSCH repetitions, an indication of UE capability, a number of PUSCH repetitions, an indication that at least one of the request for PUSCH repetitions or the indication of UE capability is associated with a PUSCH repetition with demodulation reference signal (DMRS) aggregation for cross-slot channel estimation, an indication that the PUSCH repetition is associated with one or more transmission configuration indicators (TCIs), or an indication that at least one of the request for PUSCH repetitions or the indication of UE capability is associated with a PUSCH repetition with frequency hopping.

[0255] Aspect 81: The method of any of aspects 79 or 80, wherein the one or more alternating frequency resources are different with respect to each of the one or more parameters.

[0256] Aspect 82: A method of wireless communication by a base station, comprising: receiving a physical random access channel (PRACH) message from a user equipment (UE) using one or more alternating frequency resources for PRACH transmission; and determining physical uplink shared channel (PUSCH) repetition information based on the one or more alternating frequency resources used to receive the PRACH message, wherein the PUSCH repetition information is communicated using the one or more alternating frequency resources.

[0257] Aspect 83: The method of aspect 82, wherein the one or more alternating frequency resources are different from the one or more frequency resources for a PRACH transmission associated with a single PUSCH transmission without PUSCH repetition.

[0258] Aspect 84: The method of any of aspects 82 or 83, further comprising receiving, from the UE, a PUSCH message and at least one repetition of the PUSCH message based on the PUSCH repetition information.

[0259] Example 85: The method of any of Examples 82 to 84, further comprising transmitting an indication of one or more PUSCH resources or at least one of the PUSCH parameters based on the PUSCH repetition information, wherein the PUSCH message and the at least one repetition of the PUSCH message are received using the one or more PUSCH resources or at least one of the PUSCH parameters.

[0260] Aspect 86: The method of any of aspects 82-85, further comprising transmitting a resource parameter indicating one or more alternate frequency resources, wherein the one or more alternate frequency resources are determined based on the resource parameter.

[0261] Aspect 87: The method of aspect 86, wherein the resource parameters are transmitted via system information.

[0262] Aspect 88: The method of aspect 87, wherein the system information includes Minimum Residual System Information (RMSI).

[0263] Aspect 89: The method of any of aspects 86-88, wherein the resource parameter includes a frequency offset, and the one or more alternative frequency resources are determined by applying a frequency offset to one or more frequency resources for a PRACH transmission associated with a single PUSCH transmission without PUSCH repetition.

[0264] Example 90: The method of any of Examples 82-87, wherein the transmit power for the PUSCH repetition is configured based on at least one transmit power parameter associated with the transmit power.

[0265] Aspect 91: The method of aspect 90, wherein the at least one transmit power parameter is determined based on one or more alternating frequency resources determined for the PRACH transmission.

[0266] Aspect 92: The method of any of aspects 90 or 91, further comprising transmitting at least one transmit power parameter to the UE.

[0267] Example 93: The method of any of examples 90-92, wherein the at least one transmit power parameter includes a power offset value between a transmit power for the PUSCH repetition and a second transmit power for the PRACH transmission.

[0268] Example 94: The method of any of examples 82-93, wherein the PUSCH repetition information indicates one or more parameters corresponding to at least one of a request for PUSCH repetition or an indication of UE capability for PUSCH repetition.

[0269] Aspect 95: The method of aspect 94, wherein the one or more parameters include at least one of a request for PUSCH repetitions, an indication of UE capability, a number of PUSCH repetitions, an indication that at least one of the request for PUSCH repetitions or the indication of UE capability is associated with a PUSCH repetition with demodulation reference signal (DMRS) aggregation for cross-slot channel estimation, an indication that the PUSCH repetition is associated with one or more transmission configuration indicators (TCIs), or an indication that at least one of the request for PUSCH repetitions or the indication of UE capability is associated with a PUSCH repetition with frequency hopping.

[0270] Aspect 96: The method of any of aspects 94 or 95, wherein the one or more alternating frequency resources are different with respect to each of the one or more parameters.

[0271] Aspect 97: A method for wireless communication by a user equipment (UE), comprising: transmitting a physical random access channel procedure (PRACH) message to a base station including a request for physical uplink shared channel (PUSCH) repetitions associated with a radio resource control (RRC) connection request message of a random access channel (RACH) procedure; and transmitting at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.

[0272] Aspect 98: The method of aspect 97, wherein the step of transmitting the request for PUSCH repetition includes the step of repeating the PRACH message over multiple RACH opportunities.

[0273] Aspect 99: The method of any of aspects 97 or 98, wherein the step of transmitting a request for PUSCH repetition includes the step of transmitting a PRACH preamble selected from a subset of PRACH preambles of the set of PRACH preambles, the subset indicating a request for PUSCH repetition.

[0274] Aspect 100: The method of any of aspects 97-99, wherein the step of transmitting a request for PUSCH repetition includes a step of transmitting a PRACH message using a subset of RACH opportunities (ROs) out of a set of ROs, the subset of ROs indicating a request for PUSCH repetition.

[0275] Aspect 101: The method of any of aspects 97-100, wherein transmitting the PRACH message includes transmitting the PRACH message based at least in part on one or more PRACH parameters.

[0276] Aspect 102: A method for wireless communication by a user equipment (UE), comprising: transmitting, to a base station and based at least in part on a determination that one or more trigger criteria are satisfied, a physical random access channel procedure (PRACH) message including a request for physical uplink shared channel (PUSCH) repetitions associated with a radio resource control (RRC) connection request message of a random access channel (RACH) procedure, the physical random access channel procedure (PRACH) including a request for PUSCH repetitions associated with the RRC connection request message, the PRACH message ...

[0277] Aspect 103: The method of aspect 102, wherein the step of transmitting the request for PUSCH repetition includes the step of transmitting a Physical RACH (PRACH) message indicating the request for PUSCH repetition.

[0278] Aspect 104: The method of any of aspects 102 or 103, further comprising determining a first synchronization signal block (SSB) based RSRP, wherein determining that one or more trigger criteria are satisfied comprises determining that the first SSB based RSRP satisfies a first RSRP threshold.

[0279] Aspect 105: A method for wireless communication by a user equipment (UE), comprising: transmitting, to a base station and based at least in part on a determination that one or more trigger criteria are satisfied, a physical random access channel procedure (PRACH) message including a request for physical uplink shared channel (PUSCH) repetitions associated with a radio resource control (RRC) connection request message of a random access channel (RACH) procedure, the PRACH ...

[0280] Aspect 106: The method of aspect 105, wherein the indication of the PUSCH repetition request grant is carried in a random access response (RAR) message.

[0281] Aspect 107: An apparatus for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of one or more of aspects 1 to 33.

[0282] Aspect 108: A device for wireless communication comprising a memory and one or more processors coupled to the memory, wherein the memory and the one or more processors are configured to implement a method of one or more of aspects 1 to 33.

[0283] Example 109: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Examples 1 to 33.

[0284] Aspect 110: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform a method of one or more of aspects 1-33.

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

[0286] Aspect 112: An apparatus for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of one or more of aspects 34 to 66.

[0287] Aspect 113: A device for wireless communication comprising a memory and one or more processors coupled to the memory, wherein the memory and the one or more processors are configured to implement a method of one or more of aspects 34 to 66.

[0288] Example 114: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Examples 34 to 66.

[0289] Aspect 115: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform a method of one or more of aspects 34-66.

[0290] Aspect 116: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method of one or more of aspects 34-66.

[0291] Aspect 117: An apparatus for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of one or more of aspects 67 to 81.

[0292] Aspect 118: A device for wireless communication comprising a memory and one or more processors coupled to the memory, wherein the memory and the one or more processors are configured to implement a method of one or more of aspects 67 to 81.

[0293] Example 119: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Examples 67 to 81.

[0294] Aspect 120: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform a method of one or more of aspects 67 to 81.

[0295] Aspect 121: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method of one or more of aspects 67-81.

[0296] Aspect 122: An apparatus for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of one or more of aspects 82 to 96.

[0297] Aspect 123: A device for wireless communication comprising a memory and one or more processors coupled to the memory, wherein the memory and the one or more processors are configured to implement a method of one or more of aspects 82 to 96.

[0298] Example 124: An apparatus for wireless communication, comprising at least one means for implementing the method of one or more of Examples 82 to 96.

[0299] Aspect 125: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform a method of one or more of aspects 82-96.

[0300] Aspect 126: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method of one or more of aspects 82-96.

[0301] Aspect 127: An apparatus for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of one or more of aspects 97 to 101.

[0302] Aspect 128: A device for wireless communication comprising a memory and one or more processors coupled to the memory, wherein the memory and the one or more processors are configured to implement a method of one or more of aspects 97 to 101.

[0303] Example 129: An apparatus for wireless communication, comprising at least one means for implementing the method of one or more of examples 97 to 101.

[0304] Aspect 130: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform a method of one or more of aspects 97 to 101.

[0305] Aspect 131: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method of one or more of aspects 97-101.

[0306] Aspect 132: An apparatus for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of one or more of aspects 102 to 104.

[0307] Aspect 133: A device for wireless communication comprising a memory and one or more processors coupled to the memory, wherein the memory and the one or more processors are configured to implement a method of one or more of aspects 102 to 104.

[0308] Aspect 134: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of aspects 102 to 104.

[0309] Aspect 135: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform a method of one or more of aspects 102-104.

[0310] Aspect 136: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method of one or more of aspects 102-104.

[0311] Aspect 137: An apparatus for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of one or more of aspects 105-106.

[0312] Aspect 138: A device for wireless communication comprising a memory and one or more processors coupled to the memory, wherein the memory and the one or more processors are configured to implement the method of one or more of aspects 105 to 106.

[0313] Aspect 139: An apparatus for wireless communication, comprising at least one means for implementing the method of one or more of aspects 105 to 106.

[0314] Aspect 140: 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 105-106.

[0315] Aspect 141: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method of one or more of aspects 105-106.

[0316] The above disclosure provides illustration and description, but is not intended to be exhaustive or to limit the embodiments to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the embodiments.

[0317] The term "component" as used herein shall be broadly construed as hardware and / or a combination of hardware and software. "Software" shall be broadly construed to mean, among other examples, instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. A processor as used herein is implemented in hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein may be implemented in different forms of hardware and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not intended to limit the aspects. Thus, the operation and behavior of the systems and / or methods have been described herein without reference to any specific software code. It will be understood that software and hardware may be designed to implement the systems and / or methods based at least in part on the description herein.

[0318] As used herein, "meeting a threshold" can 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, etc., depending on the context.

[0319] Although certain combinations of features are recited in the claims and / or disclosed herein, these combinations do not limit the disclosure of the various aspects. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed herein. Although each dependent claim listed below may depend directly on only one claim, the disclosure of the various aspects includes each dependent claim in combination with every other claim in the claim set. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. By way of example, "at least one of a, b, or c" is intended to include a, b, c, ab, ac, bc, and abc, as well as any combination having multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other order of a, b, and c).

[0320] No element, act, or instruction used herein should be construed as critical or essential unless expressly described as such. Additionally, the articles "a" and "an" as used herein are intended to include one or more items and may be used interchangeably with "one or more." Additionally, the article "the" as used herein is intended to include one or more items referred to with the article "the" and may be used interchangeably with "one or more." Additionally, the terms "set" and "group" as used herein are intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items) and may be used interchangeably with "one or more." When only one item is intended, the phrase "only one" or similar language is used. Additionally, terms such as "has," "have," "having," and the like as used herein are intended to be open-ended terms. Additionally, the phrase "based on" is intended to mean "based at least in part on," unless otherwise specified. Additionally, as used herein, the term "or" is intended to be inclusive when used in a consecutive manner, and may be used interchangeably with "and / or" unless otherwise noted (e.g., when used in combination with "either" or "only one of"). [Explanation of symbols]

[0321] 100 Wireless Network 102a Macro Cell 102b Picocell 102c Femtocell 110 base station 110a BS, Macro BS 110b BS 110c BS 110d BS, live BS 120UE 120a UE 120b UE 120c UE 120d UE 120e UE 130 Network Controller 212 Data Source 220 Transmit Processor 230 Transmit (TX) Multiple Input Multiple Output (MIMO) Processor 232 Modulator (MOD), Demodulator, MOD / DEMOD 234 Antenna 236 MIMO Detector 238 Receive Processor 239 Data Sink 240 Controllers / Processors 242 Memory 244 Communication Unit 246 Scheduler 252 Antenna 254 Demodulator (DEMOD), Modulator, MOD / DEMOD 256 MIMO Detector 258 Receive Processor 260 Data Sink 262 Data Sources 264 Transmit Processor 266 TX MIMO Processor 280 Controller / Processor 282 Memory 284 Housing 405 UE 410 base station 900 equipment 902 Receiving Component 904 Transmission Component 906 Equipment 908 Judgment Component 1000UE 1002 Bus 1004 Processor 1005 Memory 1006 Computer-readable storage medium 1010 Transceiver 1012 User Interface 1014 Processing System 1040 Resource Management Circuit Configuration 1042 Communication management circuit configuration 1044 Transmission power management circuit configuration 1060 Resource Management Software / Instructions 1062 Communications Management Software / Instructions 1064 Transmit Power Management Software / Instructions 1100 equipment 1102 Receiving Component 1104 Transmission components 1106 Equipment 1108 Judgment Component 1200 base stations 1202 Bus 1204 Processor 1205 Memory 1206 Computer-readable storage medium 1208 Bus Interface 1210 Transceiver 1212 User Interface 1214 Processing System 1240 Communication management circuit configuration 1242 Resource Management Circuit Configuration 1244 Transmission power management circuit configuration 1260 Communications Management Software / Instructions 1262 Resource Management Software / Instructions 1264 Transmit Power Management Software / Instructions

Claims

1. A user equipment (UE) for wireless communications, comprising: Memory, and one or more processors operably coupled to the memory, the memory and the one or more processors comprising: transmitting a request for physical uplink shared channel (PUSCH) repetitions associated with a radio resource control (RRC) connection request message of a random access channel (RACH) procedure to a base station, the transmitting the request for PUSCH repetitions including transmitting a PRACH preamble selected from a subset of PRACH preambles of a set of PRACH preambles, the subset indicating the request for PUSCH repetitions; and transmitting at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.

2. The UE of claim 1, wherein the request for a PUSCH repetition indicates one or more proposed parameters corresponding to the PUSCH repetition.

3. 10. The UE of claim 1, wherein the memory and the one or more processors are configured to, when transmitting the request for PUSCH repetition, transmit a Physical RACH (PRACH) message indicating the request for PUSCH repetition.

4. the memory and the one or more processors are configured to repeat the PRACH message over multiple RACH opportunities when sending the request for PUSCH repetition; or 4. The UE of claim 3, wherein the memory and the one or more processors are configured to transmit the PRACH message using a subset of RACH opportunities (ROs) of a set of ROs when transmitting the request for PUSCH repetition, the subset of ROs indicating the request for PUSCH repetition.

5. the memory and the one or more processors are configured, when transmitting the PRACH message, to transmit the PRACH message based at least in part on one or more PRACH parameters; The memory and the one or more processors are further configured to select the one or more PRACH parameters based at least in part on a relationship between the one or more PRACH parameters and one or more request parameters corresponding to the request for PUSCH repetitions; the memory and the one or more processors are further configured to receive from the base station a parameter configuration indicative of the relationship; The UE of claim 3 , wherein the parameter configuration is conveyed in system information, and the system information includes remaining minimum system information.

6. 13. The UE of claim 1, wherein the memory and the one or more processors are further configured to determine that one or more trigger criteria are satisfied, and wherein the memory and the one or more processors are configured to transmit the request for PUSCH repetition when transmitting the request for PUSCH repetition based at least in part on determining that the one or more trigger criteria are satisfied.

7. the memory and the one or more processors are further configured to receive a trigger configuration from the base station indicating the one or more trigger criteria; The trigger configuration is carried in system information; The UE of claim 6, wherein the system information includes remaining minimum system information.

8. the one or more trigger criteria include a first reference signal received power (RSRP) threshold; 7. The UE of claim 6, wherein the memory and the one or more processors are further configured to determine a first synchronization signal block (SSB) based RSRP, and wherein the memory and the one or more processors are configured to determine that the first SSB based RSRP satisfies the first RSRP threshold when determining that the one or more trigger criteria are satisfied.

9. the one or more trigger criteria include a second RSRP threshold; The memory and the one or more processors are further configured to determine a second SSB-based RSRP, and the memory and the one or more processors are configured to determine that the second SSB-based RSRP satisfies the second RSRP threshold when determining that the one or more trigger criteria are satisfied; 10. The UE of claim 8, wherein the request for PUSCH repetitions indicates a first number of requested PUSCH repetitions based at least in part on determining that the first SSB-based RSRP satisfies the first RSRP threshold, and wherein the request for PUSCH repetitions indicates a second number of requested PUSCH repetitions based at least in part on determining that the second SSB-based RSRP satisfies the second RSRP threshold.

10. the memory and the one or more processors are configured, when transmitting the at least one PUSCH repetition, to transmit the at least one PUSCH repetition based at least in part on transmitting the request for a PUSCH repetition. or The memory and the one or more processors receiving a random access response (RAR) message from the base station, the RAR message comprising: a PUSCH resource for the RRC connection request message; or indicating at least one PUSCH parameter associated with the RRC connection request message; and determining at least one of a PUSCH repetition parameter or a PUSCH repetition resource based at least in part on the RAR message. The memory and the one or more processors are configured, when determining the at least one of the PUSCH repetition parameters or the PUSCH repetition resources, to determine the at least one of the PUSCH repetition parameters or the PUSCH repetition resources based at least in part on one or more rules set forth by a wireless communication standard. or The memory and the one or more processors are further configured to receive an indication of a PUSCH repeat request grant from the base station, the PUSCH repeat request grant corresponding to at least a portion of the PUSCH repeat request; The indication of the PUSCH repetition request grant is carried in a Random Access Response (RAR) message; The UE of claim 1 , wherein the indication of the PUSCH repetition request grant is carried in a physical downlink control channel portion of the RAR message.

11. 1. A base station for wireless communications, comprising: Memory, and one or more processors operably coupled to the memory, the memory and the one or more processors comprising: receiving, from a user equipment (UE), a request for physical uplink shared channel (PUSCH) repetition associated with a radio resource control (RRC) connection request message of a random access channel (RACH) procedure, wherein receiving the request for PUSCH repetition includes receiving a PRACH preamble selected from a subset of PRACH preambles of a set of PRACH preambles, the subset indicating the request for PUSCH repetition; and receiving at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.

12. the memory and the one or more processors are configured, when receiving the request for PUSCH repetition, to receive a Physical RACH (PRACH) message indicating the request for PUSCH repetition; The memory and the one or more processors are configured, when receiving the PRACH message, to receive the PRACH message based at least in part on one or more PRACH parameters, selection of the one or more PRACH parameters being based at least in part on a relationship between the one or more PRACH parameters and one or more request parameters corresponding to the request for PUSCH repetitions; the memory and the one or more processors are further configured to transmit to the UE a parameter configuration indicative of the relationship. or The memory and the one or more processors are configured to receive the request for PUSCH repetition based at least in part on a determination that one or more trigger criteria are satisfied when receiving the request for PUSCH repetition, and the memory and the one or more processors are further configured to transmit a trigger configuration to the UE indicating the one or more trigger criteria. or The memory and the one or more processors and transmitting a random access response (RAR) message to the UE, the RAR message comprising: a PUSCH resource for the RRC connection request message; or indicating at least one of the PUSCH parameters associated with the RRC connection request message; or The memory and the one or more processors are further configured to send an indication of a PUSCH repeat request grant to the UE, the PUSCH repeat request grant corresponding to at least a portion of the PUSCH repeat request; 12. The base station of claim 11, wherein the indication of the PUSCH repetition request grant is carried in a random access response (RAR) message.

13. 1. A method of wireless communication implemented by a user equipment (UE), comprising: transmitting a request for Physical Uplink Shared Channel (PUSCH) repetitions associated with a Radio Resource Control (RRC) Connection Request message of a Random Access Channel (RACH) procedure to a base station, the transmitting the request for PUSCH repetitions comprising transmitting a PRACH preamble selected from a subset of PRACH preambles of a set of PRACH preambles, the subset indicating the request for PUSCH repetitions; and transmitting at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.

14. A method of wireless communications implemented by a base station, comprising: receiving, from a user equipment (UE), a request for physical uplink shared channel (PUSCH) repetition associated with a radio resource control (RRC) connection request message of a random access channel (RACH) procedure, wherein receiving the request for PUSCH repetition comprises receiving a PRACH preamble selected from a subset of PRACH preambles of a set of PRACH preambles, the subset indicating the request for PUSCH repetition; and receiving at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.

15. A computer program comprising instructions which, when executed by a computer, cause the computer to carry out the method according to claim 13 or 14.

Images