Requests for physical uplink shared channel repetition associated with a radio resource control connection request message in a random access channel procedure

Abstract

The various formats described in this case generally relate to wireless communications. In some formats, a user equipment (UE) may send a request to a base station for a repeat of the Entity Uplink Shared Channel (PUSCH) associated with a Radio Resource Control (RRC) Connection Request message in a Random Access Channel (RACH) procedure. The UE may send at least one PUSCH repeat associated with the RRC Connection Request message, at least in part, based on the request. Many other formats are described.

Description

[Technical Field]

[0001] The contents of this case generally relate to wireless communications, and to techniques and apparatus for requesting repeated requests for an entity uplink shared channel in connection with a radio resource control connection request message in a random access channel procedure. [Previous Technology]

[0002] Wireless communication systems are widely deployed to provide various telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiplexing access technologies that support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiplexing access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile service standard released by the 3rd Generation Partnership Project (3GPP).

[0003] A wireless network may include multiple base stations (BSs) capable of supporting communications for multiple user equipments (UEs). UEs may communicate with the BS via downlinks and uplinks. A "downlink" (or "forward link") refers to the communication link from the BS to the UE, and an "uplink" (or "backlink") refers to the communication link from the UE to the BS. As will be detailed herein, a BS may be referred to as a Node B, gNB, Access Point (AP), Radio Headend, Transmit / Receive Point (TRP), New Radio (NR) BS, 5G Node B, etc.

[0004] These multiplexing access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different user equipment to communicate at the municipal, national, regional, and even global levels. NR (also known as 5G) is a set of enhancements to the LTE mobile service standard released by 3GPP. NR is designed to better support mobile broadband internet access by: improving spectrum efficiency; reducing costs; improving service; utilizing new spectrum; and better integrating with other open standards by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (DL) and CP-OFDM or SC-FDM (e.g., also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink (UL); it also supports beamforming, multiple-input multiple-output (MIMO) antenna technologies, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements to LTE, NR, and other radio access technologies remain useful. [Summary of the Invention]

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

[0006] In some embodiments, a base station for wireless communication includes: a memory; and one or more processors coupled to the memory, the one or more processors being configured to: receive from the UE a request for a PUSCH repeat associated with an RRC connection request message for a RACH procedure; and receive at least one PUSCH repeat associated with the RRC connection request message based at least in part on the request.

[0007] In some embodiments, a method of wireless communication performed by a UE includes: sending a request to a base station for a PUSCH repeat associated with an RRC connection request message related to a RACH procedure; and sending at least one PUSCH repeat associated with the RRC connection request message based at least in part on the request.

[0008] In some embodiments, a method of wireless communication performed by a base station includes: receiving from a UE a request for a PUSCH repeat associated with an RRC connection request message for a RACH procedure; and receiving at least one PUSCH repeat associated with the RRC connection request message based at least in part on the request.

[0009] In some forms, 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 the UE, cause the UE to: send a request to a base station for a PUSCH repeat associated with an RRC connection request message of the RACH procedure; and, at least in part based on the request, send at least one PUSCH repeat associated with the RRC connection request message.

[0010] In some embodiments, 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 base station, cause the base station to: receive from the UE a request for a PUSCH repeat associated with an RRC connection request message for a RACH procedure; and, at least in part based on the request, receive at least one PUSCH repeat associated with the RRC connection request message.

[0011] In some embodiments, an apparatus for wireless communication includes: a unit for sending to a base station a request for a PUSCH repeat associated with an RRC connection request message of a RACH procedure; and a unit for sending at least one PUSCH repeat associated with the RRC connection request message based at least in part on the request.

[0012] In some embodiments, an apparatus for wireless communication includes: a unit for receiving from a UE a request for a PUSCH repeat associated with an RRC connection request message related to a RACH procedure; and a unit for receiving at least one PUSCH repeat associated with the RRC connection request message based at least in part on the request.

[0013] Some of the embodiments described herein relate to a UE for wireless communication. The user equipment may include memory and one or more processors coupled to the memory. The one or more processors may be configured to send a PRACH message to a base station and at least in part based on a decision regarding the satisfaction of one or more triggering criteria, the PRACH message including a request for a PUSCH repetition associated with an RRC connection request message of a RACH procedure, wherein the one or more triggering criteria include a reference signal received power threshold. The one or more processors may be configured to send at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.

[0014] Some of the embodiments described herein relate to a UE for wireless communication. The user equipment may include memory and one or more processors coupled to the memory. The one or more processors may be configured to send a PRACH message to a base station and at least in part based on a decision regarding the satisfaction of one or more triggering criteria, the PRACH message including a request for PUSCH repetition associated with an RRC connection request message of a RACH procedure, wherein the one or more triggering criteria include a reference signal received power threshold. The one or more processors may be configured to receive from the base station an indication of permission to grant a PUSCH repetition request, wherein the permission corresponds to at least a portion of the PUSCH repetition request. The one or more processors may be configured to send at least one PUSCH repetition associated with the RRC connection request message based at least in part on the request.

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

[0016] Some of the states described herein relate to a method of wireless communication performed by a UE. The method may include determining one or more backup frequency resources for PRACH transmission, wherein the use of the one or more backup frequency resources transmits PUSCH repetition information. The method may include sending a PRACH message to a base station using the one or more backup frequency resources used to transmit PUSCH repetition information.

[0017] Some of the methods described herein relate to a method of wireless communication performed by a base station. The method may include receiving a PRACH message from a UE using one or more backup frequency resources for PRACH transmission. The method may include determining PUSCH repetition information based on the one or more backup frequency resources used to receive the PRACH message, wherein the use of the one or more backup frequency resources transmits the PUSCH repetition information.

[0018] Some of the embodiments described herein relate to a UE for wireless communication. The user equipment may include memory and one or more processors coupled to the memory. The one or more processors may be configured to determine one or more alternative frequency resources for PRACH transmission, wherein the use of the one or more alternative frequency resources transmits PUSCH repetition information. The one or more processors may be configured to use the one or more alternative frequency resources used to transmit the PUSCH repetition information to send a PRACH message to a base station.

[0019] Some of the embodiments described herein relate to a base station for wireless communication. The base station may include memory and one or more processors coupled to the memory. The one or more processors may be configured to receive PRACH messages from a UE using one or more alternative frequency resources for PRACH transmission. The one or more processors may be configured to determine PUSCH repetition information based on the one or more alternative frequency resources used to receive the PRACH messages, wherein the use of the one or more alternative frequency resources transmits the PUSCH repetition information.

[0020] Some of the embodiments described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication performed by a UE. When executed by one or more processors of the UE, the set of instructions can cause the UE to determine one or more alternative frequency resources for PRACH transmission, wherein the use of the one or more alternative frequency resources transmits PUSCH repeat information. When executed by one or more processors of the UE, the set of instructions can cause the UE to use the one or more alternative frequency resources for transmitting the PUSCH repeat information to send a PRACH message to a base station.

[0021] Some of the embodiments described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication performed by a base station. When executed by one or more processors of the base station, the set of instructions enables the base station to use one or more spare frequency resources for PRACH transmission to receive PRACH messages from a UE. When executed by one or more processors of the base station, the set of instructions enables the base station to determine PUSCH repetition information based on the one or more spare frequency resources used to receive the PRACH messages, wherein the use of the one or more spare frequency resources transmits the PUSCH repetition information.

[0022] Some of the embodiments described herein relate to an apparatus for wireless communication. The apparatus may include units for determining one or more backup frequency resources for PRACH transmission, wherein the use of the one or more backup frequency resources transmits PUSCH repeat information. The apparatus may include units for using the one or more backup frequency resources used to transmit the PUSCH repeat information to send a PRACH message to a base station.

[0023] Some of the embodiments described herein relate to an apparatus for wireless communication. The apparatus may include units for receiving PRACH messages from a UE using one or more backup frequency resources used for PRACH transmission. The apparatus may include units for determining PUSCH repetition information based on the one or more backup frequency resources used to receive the PRACH messages, wherein the use of the one or more backup frequency resources transmits the PUSCH repetition information.

[0024] As substantially described with reference to the accompanying drawings and description and as shown in the drawings and description, various types generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication equipment and / or processing systems.

[0025] The features and technical advantages of the examples based on the content of this case have been outlined quite extensively above to facilitate a better understanding of the following detailed description. Other features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose as the content of this case. Such equivalent structures do not depart from the scope of the appended patent applications. The features (organization and operation) of the concepts disclosed herein, as well as the associated advantages, will be better understood from the following description when considered in conjunction with the accompanying drawings. Each drawing is provided for illustrative and descriptive purposes and not as a definition of limitation on the scope of the patent applications.

[0026] While various forms and embodiments have been described herein through the illustration of some examples, those skilled in the art will understand that other implementations and use cases can be implemented in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, the various embodiments and / or uses can be implemented by integrating chip-level embodiments with other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a particular use case or application, a wide variety of applicability to the described innovations is possible. The various implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and can be aggregated, distributed, or OEM devices or systems that include one or more forms of the described innovations. In some practical settings, devices that include the described forms and features may also include additional components and features for implementing and practicing the claimed and described embodiments. For example, the transmission and reception of wireless signals must include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be implemented in a variety of devices, chip-level components, systems, distributed deployments, end-user devices, etc., with different sizes, shapes, and constructions.

Implementation Method

[0034] Various embodiments of the present invention are described more fully below with reference to the accompanying drawings. However, the present invention may be implemented in many different forms and should not be construed as limited to any particular structure or function provided throughout the present invention. Rather, these embodiments are provided to make the present invention thorough and complete, and to fully convey the scope of the present invention to those skilled in the art to which it pertains. Based on the teachings herein, one skilled in the art to which the present invention pertains should understand that the scope of the present invention is intended to cover any embodiment of the present invention disclosed herein, whether implemented independently or in combination with any other embodiment of the present invention. For example, any number of embodiments set forth herein may be used to implement an apparatus or practice. In addition, the scope of the present invention is intended to cover such an apparatus or method practiced using structures, functions, or structures and functions other than those set forth herein or not set forth herein. It should be understood that any embodiment of the present invention disclosed herein may be embodied by one or more elements of the claim.

[0035] Several aspects of a telecommunications system will now be presented with reference to various devices and techniques. These devices and methods will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, programs, algorithms, etc. (collectively, "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0036] It should be noted that although the various forms may be described herein using terms commonly associated with 5G or NR Radio Access Technology (RAT), the various forms of the present invention may be applied to other RATs, such as 3G RAT, 4G RAT and / or RATs after 5G (e.g., 6G).

[0037] Figure 1 is a diagram illustrating an example of a wireless network 100 according to the present invention. The wireless network 100 may be or may include elements of a 5G (NR) network and / or an LTE network, etc. The wireless network 100 may include multiple base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with a user equipment (UE) and may also be referred to as an NR BS, Node B, gNB, 5G Node B (NB), Access Point, Transmit / Receive Point (TRP), etc. Each BS can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may represent the coverage area of ​​a BS and / or the BS subsystem serving that coverage area, depending on the context in which the term is used.

[0038] A BS can provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UEs with service subscriptions. A picocell can cover a relatively small geographic area and can allow unrestricted access by UEs with service subscriptions. A femtocell can cover a relatively small geographic area (e.g., a home) and can allow restricted access by UEs associated with that femtocell (e.g., UEs in a closed user group (CSG)). A BS for macrocells can be referred to as a macro BS. A BS for picocells can be referred to as a pico BS. A BS for femtocells can be referred to as a femto BS or a home BS. In the example shown in Figure 1, BS 110a can be a macro BS for macrocell 102a, BS 110b can be a pico BS for picocell 102b, and BS 110c can be a femto BS for femtocell 102c. A BS can support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "node B", "5G NB" and "cell" are used interchangeably in this document.

[0039] In some states, the cell may not be stationary, and the geographic area of ​​the cell may move depending on the location of the active BS. In some states, BSs may be interconnected with each other and / or interconnected with one or more other BSs or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces (e.g., direct physical connections using any suitable transport network, or virtual networks).

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

[0041] Wireless network 100 may be a heterogeneous network comprising different types of BSs (e.g., macro BS, pico BS, femto BS, repeater BS, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs may have high transmit power levels (e.g., 5 to 40 watts), while pico BSs, femto BSs, and repeater BSs may have lower transmit power levels (e.g., 0.1 to 2 watts).

[0042] The network controller 130 can be coupled to a group of BSs and can provide coordination and control for these BSs. The network controller 130 can communicate with the BSs via backhaul. The BSs can also communicate with each other directly or indirectly via wireless or wired backhaul.

[0043] UE 120 (e.g., 120a, 120b, 120c) may be distributed throughout the wireless network 100, and each UE may be stationary or mobile. UE may also be referred to as an access terminal, terminal, mobile station, user unit, station, etc. UE may be a cellular telephone (e.g., a smartphone), personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop, wireless telephone, wireless loop (WLL) station, tablet device, camera, gaming device, laptop, smart computer, ultrabook, medical device or apparatus, biometric sensor / device, wearable device (smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.)), entertainment device (e.g., music or video device, or satellite radio unit, etc.), vehicle component or sensor, smart instrument / sensor, industrial manufacturing equipment, GPS device, or any other suitable device configured to communicate via wireless or wired media.

[0044] Some UEs can be considered Machine-Type Communication (MTC) UEs or Evolved or Enhanced Machine-Type Communication (eMTC) UEs. MTC UEs and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which can communicate with a base station, another device (e.g., a remote device), or some other entity. Wireless nodes can provide connectivity to or to a network (e.g., a wide area network such as the Internet or cellular networks) via wired or wireless communication links, for example. Some UEs can be considered Internet of Things (IoT) devices and / or can be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs can be considered Customer Premises Equipment (CPE). UE 120 can be included within a housing that houses the components of UE 120, such as processor components and / or memory components. In some cases, the processor components and memory components can be coupled together. For example, processor components (e.g., one or more processors) and memory components (e.g., memory) can be operatively coupled, communicatively coupled, electronically coupled, electrically coupled, etc.

[0045] Typically, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

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

[0047] Devices of the wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices of the wireless network 100 can communicate using an operating band with a first frequency range (FR1), which spans from 410 MHz to 7.125 GHz, and / or can communicate using an operating band with a second frequency range (FR2), which spans from 24.25 GHz to 52.6 GHz. The frequencies between FR1 and FR2 are sometimes referred to as intermediate frequencies (IFs). 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, but it is different from the ultra-high frequency (EHF) band (30 GHz–300 GHz) which is designated as a "millimeter wave" band by the International Telecommunication Union (ITU). Therefore, unless otherwise explicitly stated, it should be understood that the terms "sub-6 GHz," if used herein, can broadly refer to frequencies less than 6 GHz, frequencies within FR1, and / or intermediate frequency frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise explicitly stated, it should be understood that the terms "millimeter wave," if used herein, can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or intermediate frequency frequencies (e.g., less than 24.25 GHz). It is conceivable that the frequencies included in FR1 and FR2 can be modified, and the techniques described herein are applicable to those modified frequency ranges.

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

[0049] Figure 2 is a diagram illustrating an example 200 of communication between base station 110 and UE 120 in wireless network 100, according to the present invention. Base station 110 may be equipped with T antennas 234a to 234t, and UE 120 may be equipped with R antennas 252a to 252r, wherein generally, T ≥ 1 and R ≥ 1.

[0050] At base station 110, transmitting processor 220 can receive data for one or more UEs from data source 212, select one or more modulation and coding schemes (MCS) for that UE based at least in part on the Channel Quality Indicator (CQI) received from each UE, process (e.g., encode and modulate) the data for that UE based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. Transmitting processor 220 can also process system information (e.g., semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, permission, and / or upper-layer signaling), and provide management burden symbols and control symbols. Transmitting processor 220 can also generate reference symbols for reference signals (e.g., cell-specific reference signal (CRS) or demodulated reference signal (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding, if applicable) on data symbols, control symbols, management burden symbols, and / or reference symbols, and can provide T output symbol streams to T modulators (MODs) 232a to 232t. Each modulator 232 can (e.g., for OFDM) process its corresponding output symbol stream to obtain an output sample stream. Each modulator 232 can 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 to 232t can be transmitted via T antennas 234a to 234t respectively.

[0051] At UE 120, antennas 252a to 252r can receive downlink signals from base station 110 and / or other base stations, and can respectively provide the received signals to demodulators (DEMODs) 254a to 254r. Each demodulator 254 can adjust (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain an input sample. Each demodulator 254 can (e.g., for OFDM) further process the input sample to obtain a received symbol. MIMO detector 256 can obtain the received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols (if applicable), and provide the detected symbols. Receiver processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to data slot 260, and provide decoded control information and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine parameters such as the Reference Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Received Quality (RSRQ), and / or CQI. In some configurations, one or more components of the UE 120 may be included in the housing 284.

[0052] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include one or more devices, such as those in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0053] Among other examples, antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, antenna groups, antenna element sets, and / or antenna arrays. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include one or more antenna elements. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include coplanar antenna element sets and / or non-coplanar antenna element sets. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include antenna elements within a single housing and / or antenna elements within multiple housings. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include one or more antenna elements coupled to one or more transmitting elements and / or receiving elements (e.g., one or more elements of FIG. 2).

[0054] On the uplink, at UE 120, the transmitting processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmitting processor 264 can also generate reference symbols for one or more reference signals. Symbols from the transmitting processor 264 can be pre-encoded (if applicable) by TX MIMO processor 266, further processed by modulators 254a to 254r (e.g., for DFT-s-OFDM, and / or CP-OFDM), and transmitted to base station 110. In some embodiments, the modem of UE 120 may include modulators and demodulators of UE 120 (e.g., MOD / DEMOD 254). In some embodiments, UE 120 includes a transceiver. The transceiver may include any combination of antenna 252, modulator and / or demodulator 254, MIMO detector 256, receiver processor 258, transmitter processor 264 and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform any of the methods described herein (e.g., as shown in Figures 4-12).

[0055] At base station 110, uplink signals from UE 120 and other UEs can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 (if applicable), and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 can provide decoded data to data slot 239 and decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and communicate with network controller 130 via communication unit 244. Base station 110 may include scheduler 246 for scheduling UE 120 for downlink and / or uplink communication. In some embodiments, the modem of base station 110 may include modulator and demodulator (e.g., MOD / DEMOD 232). In some embodiments, base station 110 includes transceiver. The transceiver may include any combination of antenna 234, modulator and / or demodulator 232, MIMO detector 236, receiver processor 238, transmitter processor 220 and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform any of the methods described herein (e.g., as shown in Figures 4-12).

[0056] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or any other component of FIG. 2 may execute one or more techniques associated with a request for repetition of the Entity Uplink Shared Channel (PUSCH) in connection with a Radio Resource Control (RRC) Connection Request message in a RACH procedure, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or any other component of FIG. 2 may execute or direct the operation of, for example, procedure 500 of FIG. 5, procedure 600 of FIG. 6, procedure 700 of FIG. 7, procedure 800 of FIG. 8, and / or other procedures described herein. Memory 242 and 282 may store data and code of base station 110 and UE 120, respectively. In some embodiments, memory 242 and / or memory 282 may include non-transitory computer-readable media storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly executed, or executed after compilation, translation, and / or interpretation), may cause one or more processors, UE 120, and / or base station 110 to perform or direct operations such as those described herein: program 500 of FIG. 5, program 600 of FIG. 6, program 700 of FIG. 7, program 800 of FIG. 8, and / or other programs described herein. In some embodiments, the execution instructions may include run instructions, translation instructions, compilation instructions, and / or interpretation instructions, etc.

[0057] In some configurations, the UE includes a unit for sending a request to the base station for a PUSCH repeat associated with an RRC connection request message of a Random Access Channel (RACH) procedure; or a unit for sending at least one PUSCH repeat associated with an RRC connection request message based at least partially on the request. In some configurations, the UE includes a unit for selecting one or more physical random access channel (PRACH) parameters based at least partially on the relationship between one or more physical random access channel (PRACH) parameters and one or more request parameters corresponding to the request for PUSCH repeat. In some configurations, the UE includes a unit for receiving a parameter configuration indicating the relationship from the base station. In some configurations, the UE includes a unit for determining whether one or more triggering criteria are met, wherein sending the request for PUSCH repeat includes sending the request for PUSCH repeat based at least partially on the determination that one or more triggering criteria are met. In some configurations, the UE includes a unit for receiving a trigger configuration indicating one or more triggering criteria from the base station.

[0058] In some configurations, the UE includes a unit for determining the RSRP based on a first synchronization signal block (SSB), wherein determining that one or more triggering criteria are met includes determining that the RSRP based on the first SSB meets a first RSRP threshold. In some configurations, the UE includes a unit for determining the RSRP based on a second SSB, wherein determining that one or more triggering criteria are met includes determining that the RSRP based on the second SSB meets a second RSRP threshold. In some configurations, the UE includes a unit for receiving a Random Access Response (RAR) message from a base station, wherein the RAR message indicates at least one of the following: a unit for determining at least one of a PUSCH repeat parameter or a PUSCH repeat resource based at least partially on the RAR message. In some configurations, the UE includes a unit for receiving an indication of PUSCH repeat request permission from a base station, wherein PUSCH repeat request permission corresponds to at least a portion of a PUSCH repeat request.

[0059] In some configurations, the UE includes a unit for determining one or more backup frequency resources for PRACH transmission, wherein the use of the one or more backup frequency resources transmits PUSCH repeat information; and / or a unit for using one or more backup frequency resources for transmitting PUSCH repeat information to send PRACH messages to the base station.

[0060] The unit for the UE to perform the operations described herein may include, for example, one or more of the following: antenna 252, demodulator 254, MIMO detector 256, receiver processor 258, transmitter processor 264, TX MIMO processor 266, modulator 254, controller / processor 280 or memory 282.

[0061] In some configurations, the base station includes a unit for receiving from the UE a request for PUSCH repetition associated with an RRC connection request message related to a RACH procedure; or a unit for receiving at least one PUSCH repetition associated with an RRC connection request message based at least partially on the request. In some configurations, the base station includes a unit for sending parameter configuration indicating a relationship to the UE. In some configurations, the base station includes a unit for sending to the UE a trigger configuration indicating one or more trigger criteria. In some configurations, the base station includes a unit for sending a RAR message to the UE. In some configurations, the base station includes a unit for sending to the UE an indication of PUSCH repetition request permission, wherein the PUSCH repetition request permission corresponds to at least a portion of the PUSCH repetition request.

[0062] In some configurations, the base station includes: a unit for receiving PRACH messages from the UE using one or more backup frequency resources for PRACH transmission; and / or a unit for determining PUSCH duplication information based on one or more backup frequency resources used for receiving PRACH messages, wherein the PUSCH duplication information is transmitted by the use of the one or more backup frequency resources.

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

[0064] Although the blocks in Figure 2 are shown as different components, the functions described above regarding these blocks can be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described regarding the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 can be executed by the controller / processor 280 or executed under the control of the controller / processor 280.

[0065] As mentioned above, Figure 2 is provided as an example. Other examples may differ from the examples described with respect to Figure 2.

[0066] Figure 3 is a schematic diagram of a four-step RACH operation example according to the contents of this case. As shown in Figure 3, base station 110 and UE 120 can communicate with each other to execute the four-step random access procedure.

[0067] As shown in component symbol 305, base station 110 can transmit and UE 120 can receive one or more SSBs and random access configuration information. In some cases, the random access configuration information may be transmitted and / or indicated by system information (e.g., in one or more system information blocks (SIBs)) and / or SSBs, for example, for contention-based random access. Alternatively, the random access configuration information may be transmitted in RRC messages and / or entity downlink control channel (PDCCH) command messages that trigger RACH procedures, for example, 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 random access messages (RAM) and / or one or more parameters for receiving RARs, etc.

[0068] As shown in component symbol 310, UE 120 can transmit RAM with a RACH request via PRACH. RAM may include preamble signals (sometimes referred to as random access preamble signals, PRACH preamble signals, and / or RAM preamble signals, etc.). In a four-step random access procedure, the message including the preamble signals may be referred to as message 1, msg1, MSG1, first message, and / or initial message, etc. The random access message may include a random access preamble signal identifier.

[0069] As indicated by component symbol 315, base station 110 may send a RAR as a response to a preamble signal. In the four-step random access procedure, the message including the RAR may be referred to as message 2, msg2, MSG 2, or a second message. In some cases, the RAR may indicate the detected random access preamble signal identifier (e.g., received from UE 120 in msg1). Alternatively, the RAR may indicate the resource configuration to be used by UE 120 to send message 3 (msg3) (see below).

[0070] In some configurations, as part of the second step of the four-step random access procedure, base station 110 may send PDCCH communications for the RAR. The PDCCH communications may schedule Entity Downlink Shared Channel (PDSCH) communications that include the RAR. For example, the PDCCH communications may indicate resource configurations used for the PDSCH communications. Furthermore, as part of the second step of the four-step random access procedure, base station 110 may send PDSCH communications for the RAR according to the PDCCH communication schedule. The RAR may be included in the MAC Protocol Data Unit (PDU) of the PDSCH communications.

[0071] As shown in component symbol 320, UE 120 can send an RRC connection request message. The RRC connection request message may be referred to as message 3 of the four-step random access procedure, msg3, MSG3, UE identification message, or third message. In some versions, the RRC connection request may include the UE identifier, uplink control information (UCI), and / or PUSCH communication (e.g., RRC connection request), etc.

[0072] As shown in component symbol 325, base station 110 can send an RRC connection setup message. The RRC connection setup message may be referred to as message 4, msg4, MSG4, or the fourth message in a four-step random access procedure. In some configurations, the RRC connection establishment message may include the detected UE identifier, timing advance value, and / or contention resolution information. As shown in component symbol 330, if UE 120 successfully receives the RRC connection establishment message, UE 120 can send a Hybrid Automatic Repeat Request (HARQ) acknowledgment (ACK).

[0073] RACH procedures may have coverage limitations, which can negatively impact network performance. In some cases, RACH messages with a frequency range greater than or equal to approximately 24 GHz may be missed by the UE or inaccurately decoded by the UE. Therefore, RRC connection setup messages may not be effectively transmitted, affecting network connectivity. Repetition of PUSCH associated with RRC connection setup messages can contribute to more effective coverage. To perform PUSCH repetition, the UE can transmit PUSCH repetition information to the base station to schedule PUSCH repetition. PUSCH repetition information may include a request for PUSCH repetition and / or an indication of the UE's capabilities for PUSCH repetition. However, scheduling PUSCH repetition for coverage of UEs for whom it is not an issue can lead to inefficiency, resulting in wasted resources. Furthermore, transmitting PUSCH repetition information as part of the data sent to the base station may not be an efficient use of resources.

[0074] The various forms of the techniques described herein can facilitate effective PUSCH repetition associated with the RRC connection setup request message during the RACH procedure. For example, the forms can enable the UE to request PUSCH repetition and / or parameters for PUSCH repetition. Therefore, the forms can enable PUSCH repetition only if and to a certain extent that PUSCH repetition is beneficial to the UE, which can lead to effective coverage enhancement for RRC connections, which can positively impact network performance and thus save resources (e.g., computing resources, storage resources, communication resources, and network resources) that would be wasted when scheduling PUSCH repetition for UEs for whom coverage is not an issue.

[0075] According to some embodiments of the present invention, the UE may use specific frequency resources to transmit PUSCH repetition information to the base station, wherein the use of specific frequency resources transmits PUSCH repetition information. For example, the UE may use general frequency resources for PRACH transmissions associated with a single PUSCH transmission without any PUSCH repetition. In another embodiment, the UE may use spare frequency resources used for PRACH transmissions to transmit PUSCH repetition information, wherein the use of spare frequency resources can transmit PUSCH repetition information. Thus, for example, the use of specific spare frequency resources can transmit PUSCH repetition to the base station, allowing the base station to determine PUSCH repetition information based on the use of spare frequency resources for PRACH transmissions, rather than transmitting PUSCH repetition information via a data signal. In some embodiments, the spare frequency resources may be at least partially different from the general frequency resources used for PRACH transmissions associated with a single PUSCH transmission.

[0076] In some states, the UE can determine the spare frequency resources for PRACH transmission and can use the spare frequency resources to send PRACH messages to transmit PUSCH repetition information. Based on the PUSCH repetition information, the UE can send PUSCH messages and at least one repetition of the PUSCH messages, thereby performing PUSCH repetition.

[0077] As mentioned above, the base station can determine the PUSCH repetition information based on the use of spare frequency resources for PRACH transmission. In some configurations, when the base station determines the PUSCH repetition information, the base station can send an indication of PUSCH resources and / or PUSCH parameters based on the PUSCH repetition information, enabling the UE to use the PUSCH resources and / or PUSCH parameters to send PUSCH messages and at least one repetition of the PUSCH messages. In some configurations, the indication of PUSCH resources and / or PUSCH parameters can be sent via RAR messages.

[0078] In some configurations, the base station may indicate a spare frequency resource to the UE. The base station may allocate the spare frequency resource, for example, by selecting an available frequency resource that differs from the general frequency resource. For example, the spare frequency resource may be allocated within a resource block. In one instance, the spare frequency resource may reside in a component carrier that is different from the general frequency resource used for a PRACH transmission associated with a single PUSCH transmission without PUSCH repetition. In some configurations, the base station may send resource parameters indicating the spare frequency resource to the UE, allowing the UE to determine the spare frequency resource based on the received resource parameters. In some configurations, the UE may receive the resource parameters from the base station via system information. In some configurations, the UE may receive the resource parameters via system information (e.g., Remainder Minimum System Information (RMSI)) sent from the base station.

[0079] In some configurations, resource parameters may specifically indicate standby frequency resources. In some configurations, resource parameters may include frequency offsets, whereby the UE can determine standby frequency resources by applying the frequency offsets to the general frequency resources of PRACH transmissions associated with a single PUSCH transmission without PUSCH repetition. In some configurations, frequency offsets may be provided across several resource blocks.

[0080] In some formats, PUSCH repetition information may indicate one or more parameters corresponding to a request for PUSCH repetition and / or an indication of UE capabilities used for PUSCH repetition. In some formats, one or more parameters may include one or more of the following: a request for PUSCH repetition, an indication of UE capabilities, and the number of PUSCH repetitions. In some formats, one or more parameters may include an indication that at least one of the request for PUSCH repetition or the indication of UE capabilities is associated with PUSCH repetition using DMRS aggregation for cross-time slot channel estimation. For example, when using DMRS aggregation / attachment, DMRS on different repetitions in different time slots can be used together for channel estimation as cross-time slot channel estimation. In some formats, one or more parameters may include an indication that PUSCH repetition is associated with one or more Transport Configuration Indicators (TCIs). For example, multiple TCIs may be associated with multiple beams of the UE. In some cases, one or more parameters may include indications that at least one of a request for PUSCH repetition or an indication of UE capability is associated with PUSCH repetition utilizing frequency hopping. For example, frequency hopping can occur when there is a frequency shift between PUSCH repetitions and therefore different frequencies are used for different repetitions.

[0081] By utilizing different sets of spare frequency resources, different parameters of PUSCH repeat information can be transmitted to the base station. For example, using one set of spare frequency resources can transmit one parameter, while using another set of spare frequency resources can transmit another parameter. In some cases, the spare frequency resources are different for each of the one or more parameters. In some cases, one set of spare frequency resources can be used to transmit multiple parameters, while different sets of spare frequency resources can be used to transmit a single parameter. For example, one set of spare frequency resources can be used to transmit a request for PUSCH repeat and the number of PUSCH repeats, while another set of spare frequency resources can be used to transmit an indication that the PUSCH repeat is associated with one or more TCIs. In one instance, one set of spare frequency resources can be used to transmit a request for PUSCH repeat and the number of PUSCH repeats is 2, while another set of spare frequency resources can be used to transmit a request for PUSCH repeat and the number of PUSCH repeats is 4.

[0082] The transmit power used for PUSCH repetition may differ from the transmit power used for a single PUSCH transmission without any PUSCH repetition. In some states, the UE can determine the transmit power parameter associated with the transmit power used for PUSCH repetition, and the UE configures the transmit power used for PUSCH repetition based on the transmit parameter. Reserved frequency resources can be associated with one transmit power parameter, and general frequency resources used for PRACH transmissions associated with a single PUSCH transmission without PUSCH repetition can be associated with different transmit parameters. Therefore, in some states, when the UE decides to use reserve frequency resources for PRACH transmission, the UE can determine the transmit power parameter used for PUSCH transmission as the transmit power parameter associated with the transmit power used for PUSCH repetition. In another state, when the UE decides to use general frequency resources for PRACH transmission, the UE can determine the transmit power parameter used for PUSCH transmission as the transmit power parameter associated with the transmit power used for a single PUSCH transmission without any PUSCH repetition. Therefore, deciding to use spare frequency resources for PRACH transmissions can indicate the transmit power parameters that will be used for PUSCH transmissions and / or PUSCH repetitions.

[0083] In some configurations, the base station may determine a transmit power parameter associated with the transmit power from the base station for PUSCH repetition, and may further determine a transmit power parameter associated with the transmit power for a single PUSCH transmission without any PUSCH repetition. The UE may receive from the base station the transmit power parameter associated with the transmit power from the base station for PUSCH repetition. The UE may also receive from the base station different transmit power parameters associated with the transmit power associated with the 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 configurations, the transmit power parameter associated with the transmit power for PUSCH repetition may include a power offset value between the transmit power for PUSCH repetition and a second transmit power for PRACH transmission. Furthermore, the transmit power associated with the transmit power for a single PUSCH transmission may include different power offset values ​​between the transmit power for a single PUSCH transmission and a second transmit power for PRACH transmission. For example, the second transmit power for PRACH transmission may remain unchanged. In one instance, to determine the transmit power used for PUSCH repetition, a power offset value between the transmit power used for PUSCH repetition and the second transmit power used for PRACH transmission can be applied to the second transmit power. In one instance, the power offset value can be based on the power parameter "msg3-DeltaPreamble" included in the PUSCH-ConfigCommon field transmitted from the base station. In another instance, the power parameter can 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.

[0084] In some cases, the transmit power parameters associated with the transmit power from the base station for PUSCH repetition and / or the transmit power associated with the transmit power for a single PUSCH transmission without any PUSCH repetition may be pre-loaded in the UE.

[0085] In some cases, the transmit power parameter includes a power offset between the transmit power used for PUSCH repetition and the second transmit power used for PRACH transmission.

[0086] As shown above, Figure 3 is provided as an example. Other examples may differ from the examples described with respect to Figure 3.

[0087] Figure 4 is a diagram illustrating an instance 400 associated with a PUSCH duplicate request related to an RRC connection request message in a RACH procedure, according to the content of this case. As shown in Figure 4, UE 405 and base station 410 can communicate with each other.

[0088] As indicated by component symbol 415, base station 410 can transmit and UE 405 can receive system information (SI), which may include parameter configuration indicating the relationship between one or more PRACH parameters and a request for a PUSCH repeat associated with the same RRC connection request message. In some cases, the parameter configuration may indicate the relationship between one or more PRACH parameters and one or more requested parameters corresponding to the requested PUSCH repeat. SI may include, for example, RMSI. In some cases, the above relationship or its pattern may be indicated by a radio communication standard.

[0089] As used herein, “repeated” means a communication transmitted multiple times, and refers to the initial transmission of the communication or any subsequent retransmission of the communication. PUSCH repetition (e.g., it may be referred to as slot repetition, slot aggregation, and / or multi-slot PUSCH) can be used to increase the signal-to-noise ratio (SNR) to improve transmission reliability.

[0090] As indicated by component symbol 420, UE 405 may decide to utilize spare frequency resources for PRACH transmission, wherein the use of spare frequency resources transmits PUSCH repeat information. Therefore, by utilizing spare frequency resources for PRACH transmission, UE 405 may indicate PUSCH repeat information to base station 410. The spare frequency resources may differ from the general frequency resources used for PRACH transmissions associated with a single PUSCH transmission without PUSCH repeat. The spare frequency resources may be determined based on resource parameters indicating the spare frequency resources, wherein the resource parameters may be pre-configured / pre-loaded at UE 405 or may be provided by base station 410 (e.g., via SI).

[0091] As shown in component symbol 425, UE 405 can transmit and base station 410 can receive a PRACH message, which includes a request for PUSCH repetition associated with an RRC connection request message related to the RACH procedure. In some configurations, using spare frequency resources for transmitting PUSCH repetition information, UE 405 can transmit and base station 410 can receive the PRACH message. The request for PUSCH repetition can indicate one or more suggested parameters corresponding to the PUSCH repetition. For example, one or more suggested parameters can indicate the number of PUSCH repetitions. In some configurations, the request for PUSCH repetition can indicate a request for an aggregated demodulation reference signal used for cross-time slot channel estimation. The request for PUSCH repetition can include requests for PUSCH repetition associated with one or more transport configuration indicators and / or requests for PUSCH repetition utilizing frequency hopping, etc. As mentioned above, PUSCH repeat information can indicate one or more parameters corresponding to a request for PUSCH repeat and / or an indication of the UE's capability for PUSCH repeat. Therefore, UE 405 can implicitly transmit PUSCH repeat information by using spare frequency resources used for transmitting PRACH messages.

[0092] In some configurations, UE 405 may repeat the PRACH message on multiple RACH occasions (ROs). In some configurations, the request for PUSCH repetition may be implicit. For example, UE 405 may send a PRACH preamble signal selected from a subset of PRACH preamble signals in the PRACH preamble signal set. The subset may indicate a request for PUSCH repetition. In some configurations, UE 405 may use a subset of ROs in the RO set to send the PRACH message, where the RO subset indicates a request for PUSCH repetition. In some configurations, UE 405 may use a PRACH format indicating a request for PUSCH repetition to send the PRACH message.

[0093] In some configurations, UE 405 may transmit PRACH messages based at least in part on one or more PRACH parameters. In some configurations, PRACH messages may be transmitted based at least in part on parameter configurations received from base station 410. UE 405 may select one or more PRACH parameters based at least in part on the relationship between one or more PRACH parameters and one or more request parameters corresponding to a request for PUSCH repetition. As shown above, this relationship may be indicated by the base station and / or specified in the radio communication standard.

[0094] UE 405 can be configured to determine that one or more trigger criteria are met, and to send a request for PUSCH repetition based at least in part on the determination that one or more trigger criteria are met. In some cases, base station 410 can send a trigger configuration indicating one or more trigger criteria, and UE 405 can receive the trigger configuration. The trigger configuration can be carried in an SI (e.g., RMSI).

[0095] In some configurations, for example, one or more triggering criteria may include one or more thresholds. For example, one or more triggering criteria may include a first RSRP threshold. UE 405 may determine the RSRP based on the first SSB and may determine that the RSRP based on the first SSB satisfies the first RSRP threshold. UE 405 may request PUSCH repetition at least in part based on the determination that the RSRP based on the first SSB satisfies the first RSRP threshold.

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

[0097] As shown in component symbol 430, when base station 410 decides that the spare frequency resources will be used to receive PRACH messages, base station 410 can determine the PUSCH repeat information based on the spare frequency resources.

[0098] As shown in component symbol 435, base station 410 can transmit and UE 405 can receive RAR messages. Based on PUSCH duplication information, RAR messages can be transmitted by base station 410 and received by UE 405. RAR messages can indicate at least one of the PUSCH resources used for RRC connection request messages or PUSCH parameters associated with RRC connection request messages. For example, UE 405 can determine at least one of PUSCH duplication parameters or PUSCH duplication resources, at least in part, based on the RAR message.

[0099] In some configurations, base station 410 can send and UE 405 can receive an indication of permission to request a repeat of PUSCH. The permission to request a repeat of PUSCH may correspond to at least a portion of a repeat of PUSCH. In some configurations, the indication of permission to request a repeat of PUSCH may be carried in a RAR message. For example, the indication of permission to request a repeat of PUSCH may be carried in the PDCCH portion of the RAR message.

[0100] As shown in component symbol 440, UE 405 can determine the transmit power parameters associated with the transmit power used for PUSCH repetition, and configure the transmit power used for PUSCH repetition based on the transmit parameters. The transmit power parameters can be determined based on spare frequency resources. The transmit power parameters can be pre-configured / pre-loaded at UE 405, or can be provided by base station 410 (e.g., via SI).

[0101] As shown in component symbol 445, UE 405 can send and base station 410 can receive RRC connection request PUSCH repeats. RRC connection request PUSCH repeats can be sent at least in part based on resources and / or parameters indicated in the RAR, and the RAR can be at least in part based on a request for PUSCH repeats. In some states, the resources and / or parameters indicated in the RAR can be at least in part based on PUSCH repeat information. In some states, any number of additional RRC connection request PUSCH repeats can be sent. As shown in component symbol 450, base station 410 can send and UE 405 can receive RRC connection establishment messages. Base station 410 can send an RRC connection establishment message in response to receiving one or more PUSCH repeats.

[0102] As shown above, Figure 4 is provided as an example. Other examples may differ from the examples described with respect to Figure 4.

[0103] Figure 5 is a diagram illustrating, for example, an example procedure 500 executed by a UE according to the content of this case. Example procedure 500 is an example in which a UE (e.g., UE 405) performs an operation associated with a request for a PUSCH repeating request related to an RRC connection request message also in the RACH procedure.

[0104] As shown in FIG5, in some configurations, procedure 500 may include receiving parameter configuration from a base station, which indicates the relationship between one or more PRACH parameters and one or more request parameters corresponding to a request for PUSCH repetition (block 510). For example, the UE (e.g., using the receiving unit 902 illustrated in FIG9) may receive parameter configuration from a base station, which indicates the relationship between one or more PRACH parameters and one or more request parameters corresponding to a request for PUSCH repetition. In some configurations, the parameter configuration is carried in the SI. In some configurations, the SI includes RMSI. In some configurations, the relationship is indicated by a radio communication standard.

[0105] As shown in FIG5, in some configurations, procedure 500 may include determining the RSRP (block 520). For example, the UE (e.g., using the determining component 908 illustrated in FIG9) may determine the RSRP. In some configurations, the RSRP may be an SSB-based RSRP. As shown in FIG5, in some configurations, procedure 500 may include determining that one or more triggering criteria are met (block 530). For example, the UE (e.g., using the determining component 908 illustrated in FIG9) may determine that one or more triggering criteria are met. In some configurations, procedure 500 includes receiving a trigger configuration indicating one or more triggering criteria from a base station. In some configurations, one or more triggering criteria are indicated in a radio communication standard.

[0106] In some states, the trigger configuration is carried in the SI. In some states, the SI includes RMSI. In some states, one or more trigger criteria include a first RSRP threshold. In some states, procedure 500 includes determining an RSRP based on a first SSB, wherein determining that one or more trigger criteria are met includes determining that the RSRP based on the first SSB meets the first RSRP threshold. In some states, one or more trigger criteria include a second RSRP threshold. In some states, procedure 500 includes determining an RSRP based on a second SSB, wherein determining that one or more trigger criteria are met includes determining that the RSRP based on the second SSB meets the second RSRP threshold.

[0107] As shown in FIG5, in some versions, procedure 500 may include selecting one or more PRACH parameters (block 540) based at least in part on the relationship between one or more PRACH parameters and one or more request parameters corresponding to a request for PUSCH repetition. For example, a UE (e.g., using the decision unit 908 illustrated in FIG9) may select one or more PRACH parameters based at least in part on the relationship between one or more PRACH parameters and one or more request parameters corresponding to a request for PUSCH repetition.

[0108] As shown in FIG5, in some configurations, procedure 500 may include sending a request to the base station for PUSCH repetition associated with the RRC connection request message of the RACH procedure (block 550). For example, as described above, the UE (e.g., using the transmitting component 904 illustrated in FIG9) may send a request to the base station for PUSCH repetition associated with the RRC connection request message of the RACH procedure. In some configurations, sending the request for PUSCH repetition includes sending the request for PUSCH repetition at least in part based on a determination that one or more triggering criteria are met. For example, in some configurations, the request for PUSCH repetition indicates at least in part a first number of requested PUSCH repetitions based on a determination that the RSRP of the first SSB meets a first RSRP threshold, and the request for PUSCH repetition indicates at least in part a second number of requested PUSCH repetitions based on a determination that the RSRP of the second SSB meets a second RSRP threshold.

[0109] In some states, the request for PUSCH repetition indicates one or more suggested parameters corresponding to the PUSCH repetition. In some states, one or more suggested parameters indicate the number of PUSCH repetitions. In some states, the request for PUSCH repetition indicates a request for an aggregated demodulation reference signal used for cross-time slot channel estimation. In some states, the request for PUSCH repetition includes a request for PUSCH repetition associated with one or more transport configuration indicators. In some states, the request for PUSCH repetition includes a request for PUSCH repetition utilizing frequency hopping.

[0110] In some states, sending a request for PUSCH repetition includes sending a PRACH message indicating a request for PUSCH repetition. In some states, sending a request for PUSCH repetition includes repeating the PRACH message in a plurality of RACH instances. In some states, sending a request for PUSCH repetition includes sending a PRACH preamble signal selected from a subset of PRACH preamble signals in a set of PRACH preamble signals, wherein the subset indicates a request for PUSCH repetition. In some states, sending a request for PUSCH repetition includes sending a PRACH message using a subset of ROs in a set of ROs, wherein the subset of ROs indicates a request for PUSCH repetition. In some states, sending a request for PUSCH repetition includes sending a PRACH message using a PRACH format indicating a request for PUSCH repetition. In some states, sending a PRACH message includes sending a PRACH message at least partially based on one or more PRACH parameters.

[0111] As shown in FIG5, in some configurations, procedure 500 may include receiving an indication of permission to grant a PUSCH repeat request from a base station, wherein the permission to grant a PUSCH repeat request corresponds to at least a portion of a PUSCH repeat request (block 560). For example, the UE (e.g., using the receiving component 902 illustrated in FIG9) may receive the indication of permission to grant a PUSCH repeat request from a base station, wherein the permission to grant a PUSCH repeat request corresponds to at least a portion of a PUSCH repeat request. In some configurations, the indication of permission to grant a PUSCH repeat request is carried in a RAR message. In some configurations, the indication of permission to grant a PUSCH repeat request is carried in the downlink control channel portion of the RAR message entity.

[0112] In some embodiments, procedure 500 includes receiving a RAR message from a base station, wherein the RAR message indicates 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 the PUSCH repeat parameters or PUSCH repeat resources based at least in part on the RAR message. In some embodiments, determining at least one of the PUSCH repeat parameters or PUSCH repeat resources includes determining at least one of the PUSCH repeat parameters or PUSCH repeat resources based at least in part on one or more rules indicated by a wireless communication standard.

[0113] As further shown in FIG5, in some configurations, procedure 500 may include sending at least one PUSCH repeat associated with the RRC connection request message (block 570) at least partially based on a request. For example, as described above, the UE (e.g., using the transmission component 904 illustrated in FIG9) may send at least one PUSCH repeat associated with the RRC connection request message at least partially based on a request. In some configurations, sending at least one PUSCH repeat includes sending at least one PUSCH repeat at least partially based on sending a request for a PUSCH repeat.

[0114] Program 500 may include additional patterns, such as any single pattern or any combination of patterns of one or more other programs described below and / or elsewhere herein. Although FIG5 illustrates an example block of program 500, in some patterns, program 500 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to the blocks shown in FIG5. Alternatively or concurrently, two or more blocks of program 500 may be executed simultaneously.

[0115] Figure 6 is a diagram illustrating, for example, an example procedure 600 executed by a UE according to the content of this case. Example procedure 600 is an example in which a UE (e.g., UE 405) performs an operation associated with a request for a PUSCH repetition related to an RRC connection request message in a RACH procedure.

[0116] As shown in FIG6, in some configurations, procedure 600 may include receiving resource parameters (block 610) indicating one or more backup frequency resources from a base station. For example, as described above, the UE (e.g., using the receiving unit 902 illustrated in FIG9) may receive resource parameters indicating one or more backup frequency resources from a base station. In some configurations, the resource parameters are received via SI. In some configurations, SI includes RMSI. In some configurations, the resource parameters include frequency offset.

[0117] As shown in FIG6, in some configurations, procedure 600 may include determining one or more backup frequency resources for PRACH transmission, wherein the use of one or more backup frequency resources transmits PUSCH repeat information (block 620). For example, the UE (e.g., using the determination component 908 illustrated in FIG9) may determine one or more backup frequency resources for PRACH transmission, wherein the use of one or more backup frequency resources transmits PUSCH repeat information, as described above.

[0118] In some states, one or more spare frequency resources are different from one or more frequency resources used for PRACH transmissions associated with a single PUSCH transmission without PUSCH repetition. In some states, one or more spare frequency resources are determined based on resource parameters. In some states, determining one or more spare frequency resources includes determining one or more spare frequency resources by applying a frequency offset to one or more frequency resources used for PRACH transmissions associated with a single PUSCH transmission without PUSCH repetition.

[0119] As further shown in FIG6, in some configurations, procedure 600 may include using one or more spare frequency resources for transmitting PUSCH repeat information to send a PRACH message to the base station (block 630). For example, as described above, the UE (e.g., using the transmission component 904 illustrated in FIG9) may use one or more spare frequency resources for transmitting PUSCH repeat information to send a PRACH message to the base station.

[0120] In some configurations, 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 configurations, the one or more parameters include at least one of the following: a request for PUSCH repetition, an 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 PUSCH repetition using DMRS aggregation for cross-time slot channel estimation, an indication that 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 PUSCH repetition using frequency hopping. In some configurations, the one or more spare frequency resources are different for each of the one or more parameters.

[0121] As further shown in FIG6, in some versions, procedure 600 may include receiving an indication of one or more PUSCH resources or at least one PUSCH parameter based on PUSCH repeat information (block 640). For example, as described above, the UE (e.g., using the receiving unit 902 illustrated in FIG9) may receive an indication of one or more PUSCH resources or at least one PUSCH parameter based on PUSCH repeat information.

[0122] As further shown in FIG6, in some embodiments, procedure 600 may include determining at least one transmit power parameter associated with the transmit power used for PUSCH repetition (block 650). For example, as described above, the UE (e.g., using the determining component 908 illustrated in FIG9) may determine at least one transmit power parameter associated with the transmit power used for PUSCH repetition. As further shown in FIG6, in some embodiments, procedure 600 may include configuring the transmit power used for PUSCH repetition based on at least one transmit power parameter (block 660). For example, as described above, the UE (e.g., using the transmitting component 904 illustrated in FIG9) may configure the transmit power used for PUSCH repetition based on at least one transmit power parameter.

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

[0124] As further shown in FIG6, in some configurations, procedure 600 may include transmitting a PUSCH message and at least one repetition of the PUSCH message based on PUSCH repetition information (block 670). For example, as described above, the UE (e.g., using the transmitting unit 904 illustrated in FIG9) may transmit a PUSCH message and at least one repetition of the PUSCH message based on PUSCH repetition information. In some configurations, at least one of one or more PUSCH resources or PUSCH parameters is used to transmit the PUSCH message and at least one repetition of the PUSCH message.

[0125] Program 600 may include additional patterns, such as any single pattern or any combination of patterns of one or more other programs described below and / or elsewhere herein. Although FIG6 illustrates an example block of program 600, in some patterns, program 600 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to the blocks shown in FIG6. Alternatively or concurrently, two or more blocks of program 600 may be executed simultaneously.

[0126] Figure 7 is a diagram illustrating, for example, an instance program 700 executed by a base station according to the contents of this case. Instance program 700 is an example in which a base station (e.g., base station 410) performs an operation associated with a request for a PUSCH repeating the request associated with an RRC connection request message in the RACH procedure.

[0127] As shown in FIG7, in some embodiments, procedure 700 may include sending parameter configuration to the UE, the parameter configuration indicating the relationship between one or more PRACH parameters and one or more request parameters corresponding to a request for PUSCH repetition (block 710). For example, as described above, a base station (e.g., using the transmitting unit 1104 illustrated in FIG11) may transmit parameter configuration to the UE, the parameter configuration indicating the relationship between one or more PRACH parameters and one or more request parameters corresponding to a request for PUSCH repetition. In some embodiments, the parameter configuration is carried in an SI. In some embodiments, the SI includes an RMSI. In some embodiments, the relationship is indicated by a radio communication standard.

[0128] As shown in FIG7, in some configurations, procedure 700 may include sending a trigger configuration indicating one or more trigger standards to the UE (block 720). For example, as described above, a base station (e.g., using the transmitting component 1104 described in FIG11) may send a trigger configuration indicating one or more trigger standards to the UE. In some configurations, the trigger configuration is carried in the SI. In some configurations, the SI includes the RMSI. In some configurations, one or more trigger standards include a first RSRP threshold. In some configurations, one or more trigger standards are indicated in the radio communication standard.

[0129] As shown in FIG7, in some configurations, procedure 700 may include receiving from the UE a request for PUSCH repetition associated with the RRC connection request message for the RACH procedure (block 730). For example, as described above, a base station (e.g., using the receiving component 1102 described in FIG11) may receive from the UE a request for PUSCH repetition associated with the RRC connection request message for the RACH procedure.

[0130] In some states, the request for PUSCH repetition indicates one or more suggested parameters corresponding to the PUSCH repetition. In some states, the one or more suggested parameters indicate the number of PUSCH repetitions. In some states, the request for PUSCH repetition indicates a request for an aggregated demodulation reference signal used for cross-time slot channel estimation. In some states, the request for PUSCH repetition includes a request for PUSCH repetition associated with one or more transport configuration indicators. In some states, the request for PUSCH repetition includes a request for PUSCH repetition utilizing frequency hopping.

[0131] In some states, receiving a request for PUSCH repetition includes receiving a PRACH message indicating a request for PUSCH repetition. In some states, receiving a request for PUSCH repetition includes receiving repeated PRACH messages in a plurality of RACH instances. In some states, receiving a request for PUSCH repetition includes receiving a PRACH preamble selected from a subset of PRACH preamble signals in a set of PRACH preamble signals, wherein the subset indicates a request for PUSCH repetition. In some states, receiving a request for PUSCH repetition includes receiving a PRACH message using a subset of ROs in a set of ROs, wherein the subset of ROs indicates a request for PUSCH repetition.

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

[0133] As shown in FIG7, in some configurations, procedure 700 may include sending an indication to the UE to grant a PUSCH repeat request, wherein 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 illustrated in FIG11) may send an indication to the UE to grant a PUSCH repeat request, wherein the PUSCH repeat request grant corresponds to at least a portion of the PUSCH repeat request, as described above. In some configurations, the indication to grant a PUSCH repeat request is carried in a RAR message. In some configurations, the indication to grant a PUSCH repeat request is carried in the PDCCH portion of the RAR message.

[0134] In some embodiments, procedure 800 includes sending a RAR message to the UE, wherein the RAR message indicates 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 embodiments, determining at least one of the PUSCH repeat parameters or PUSCH repeat resources includes determining at least one of the PUSCH repeat parameters or PUSCH repeat resources based at least in part on one or more rules indicated by a radio communication standard.

[0135] As further shown in FIG7, in some configurations, procedure 700 may include receiving at least one PUSCH repeat associated with an RRC connection request message (block 750) at least partially based on a request. For example, as described above, a base station (e.g., using the receiving component 1102 illustrated in FIG11) may receive at least one PUSCH repeat associated with an RRC connection request message at least partially based on a request. In some configurations, receiving at least one PUSCH repeat includes receiving at least one PUSCH repeat at least partially based on a request for the PUSCH repeat.

[0136] In some states, receiving a request for PUSCH repetition includes receiving the request for PUSCH repetition at least in part based on a decision regarding the satisfaction of one or more triggering criteria. In some states, the decision regarding the satisfaction of one or more triggering criteria includes a decision regarding the RSRP based on a first SSB satisfying a first RSRP threshold. In some states, the one or more triggering criteria include a second RSRP threshold. In some states, the decision regarding the satisfaction of one or more triggering criteria includes a decision regarding the RSRP based on a second SSB satisfying a second RSRP threshold. In some states, the request for PUSCH repetition indicates a first number of requested PUSCH repetitions at least in part based on a decision regarding the RSRP based on the first SSB satisfying the first RSRP threshold, and the request for PUSCH repetition indicates a second number of requested PUSCH repetitions at least in part based on a decision regarding the RSRP based on the second SSB satisfying the second RSRP threshold.

[0137] Program 700 may include additional patterns, such as any single pattern or any combination of patterns of one or more other programs described below and / or elsewhere herein. Although FIG7 illustrates an example block of program 700, in some patterns, program 700 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to the blocks shown in FIG7. Alternatively or concurrently, two or more blocks of program 700 may be executed simultaneously.

[0138] Figure 8 is a diagram illustrating, for example, an instance program 800 executed by a base station according to the contents of this case. Instance program 800 is an example in which a base station (e.g., base station 410) performs an operation associated with a request for a PUSCH repeating with an RRC connection request message in a RACH procedure.

[0139] As shown in FIG8, in some configurations, program 800 may include transmitting resource parameters (block 810) from a base station indicating one or more backup frequency resources. For example, as described above, a base station (e.g., using the transmitting unit 1104 described in FIG11) may transmit resource parameters indicating one or more backup frequency resources from the base station. In some configurations, the resource parameters are transmitted via SI. In some configurations, SI includes RMSI. In some configurations, the resource parameters include frequency offset.

[0140] As shown in FIG8, in some embodiments, procedure 800 may include using one or more backup frequency resources for PRACH transmission to receive PRACH messages from the UE (block 820). For example, as described above, a base station (e.g., using the receiving component 1102 described in FIG11) may use one or more backup frequency resources for PRACH transmission to receive PRACH messages from the UE. In some embodiments, one or more backup frequency resources are determined based on resource parameters. In some embodiments, one or more backup frequency resources are different from one or more frequency resources used for PRACH transmissions associated with a single PUSCH transmission without PUSCH repetition. In some embodiments, one or more backup frequency resources are determined by applying a frequency offset to one or more frequency resources used for PRACH transmissions associated with a single PUSCH transmission without PUSCH repetition.

[0141] As further shown in FIG8, in some embodiments, program 800 may include determining PUSCH repeat information based on one or more backup frequency resources used for receiving PRACH messages, wherein the use of one or more backup frequency resources transmits PUSCH repeat information (block 830). For example, a base station (e.g., using the determining component 1108 described in FIG11) may determine PUSCH repeat information based on one or more backup frequency resources used for receiving PRACH messages, wherein the use of one or more backup frequency resources transmits PUSCH repeat information, as described above.

[0142] In some configurations, 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 configurations, the one or more parameters include at least one of the following: a request for PUSCH repetition, an 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 PUSCH repetition using DMRS aggregation for cross-time slot channel estimation, an indication that 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 PUSCH repetition using frequency hopping. In some configurations, the one or more spare frequency resources are different for each of the one or more parameters.

[0143] As further shown in FIG8, in some configurations, program 800 may include sending an indication of one or more PUSCH resources or at least one of PUSCH parameters based on PUSCH repeat information (block 840). For example, as described above, a base station (e.g., using the transmitting unit 1104 illustrated in FIG11) may send an indication of one or more PUSCH resources or at least one of PUSCH parameters based on PUSCH repeat information.

[0144] As further shown in FIG8, in some versions, program 800 may include sending at least one transmit power parameter associated with the transmit power used for PUSCH repetition to the UE (block 850). For example, as described above, a base station (e.g., using the transmitting unit 1104 illustrated in FIG11) may send at least one transmit power parameter associated with the transmit power used for PUSCH repetition to the UE.

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

[0146] As further shown in FIG8, in some configurations, procedure 800 may include receiving a PUSCH message and at least one repeat of the PUSCH message from the UE based on PUSCH repeat information (block 860). For example, as described above, a base station (e.g., using the receiving component 1102 illustrated in FIG11) may receive a PUSCH message and at least one repeat of the PUSCH message from the UE based on PUSCH repeat information. In some configurations, at least one of one or more PUSCH resources or PUSCH parameters is used to receive the PUSCH message and at least one repeat of the PUSCH message.

[0147] Program 800 may include additional patterns, such as any single pattern or any combination of patterns of one or more other programs described below and / or elsewhere herein. Although FIG8 illustrates an example block of program 800, in some patterns, program 800 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently compared to the blocks shown in FIG8. Alternatively or concurrently, two or more blocks of program 800 may be executed.

[0148] FIG9 is a block diagram of an example device 900 for wireless communication. Device 900 may be a UE, or a UE may include device 900. In some embodiments, device 900 includes a receiving component 902 and a transmitting component 904, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 900 may use the receiving component 902 and the transmitting component 904 to communicate with another device 906 (e.g., a UE, a base station, or another wireless communication device). As further shown, device 900 may include a determining component 908.

[0149] In some embodiments, device 900 may be configured to perform one or more operations described herein in conjunction with FIG. 4. Alternatively or additionally, device 900 may be configured to perform one or more programs described herein, such as program 500 of FIG. 5, program 600 of FIG. 6, or a combination thereof. In some embodiments, device 900 and / or one or more components shown in FIG. 9 may include one or more components of the UE described above in conjunction with FIG. 2. Alternatively or additionally, one or more components shown in FIG. 9 may be implemented within one or more components described above in conjunction with FIG. 2. Alternatively or additionally, one or more components in the set of components may be implemented at least partially as software stored in 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.

[0150] The receiving unit 902 may receive communications from the device 906, such as reference signals, control information, data communications, or combinations thereof. The receiving unit 902 may provide the received communications to one or more other components of the device 900. In some embodiments, the receiving unit 902 may perform signal processing on the received communications (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of the device 906. In some embodiments, the receiving unit 902 may include one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof of the UE described above in conjunction with FIG. 2.

[0151] The transmitting component 904 can transmit communications to the device 906, such as reference signals, control information, data communications, or combinations thereof. In some embodiments, one or more other components of the device 906 can generate communications and provide the generated communications to the transmitting component 904 for transmission to the device 906. In some embodiments, the transmitting component 904 can perform signal processing on the generated communications (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) and can transmit the processed signals to the device 906. In some embodiments, the transmitting component 904 may include one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof, as described above in conjunction with FIG. 2. In some embodiments, the transmitting component 904 may be co-located with the receiving component 902 in the transceiver.

[0152] The decision-making component 908 can determine one or more spare frequency resources for PRACH transmission, wherein the use of one or more spare frequency resources transmits PUSCH repetition information. In some configurations, the decision-making component 908 may include one or more antennas, modulators, transmit MIMO processors, transmit processors, demodulators, MIMO detectors, receive processors, controllers / processors, memory, or combinations thereof of the UE described above in conjunction with FIG2. In some configurations, the decision-making component 908 may include a receive component 902 and / or a transmit component 904.

[0153] The transmitting unit 904 can use one or more spare frequency resources for transmitting PUSCH repeat information to send PRACH messages to the base station. The receiving unit 902 can receive resource parameters indicating one or more spare frequency resources from the base station, wherein the one or more spare frequency resources are determined based on the resource parameters.

[0154] The determining component 908 can be configured to determine that one or more triggering criteria are met, which triggers a PUSCH repetition request. The determining component 908 can determine at least one transmit power parameter associated with the transmit power used for PUSCH repetition. The transmitting component 904 can configure the transmit power used for PUSCH repetition based on at least one transmit power parameter. The receiving component 902 can receive at least one indication of one or more PUSCH resources or PUSCH parameters based on PUSCH repetition information, wherein a PUSCH message and at least one repetition of the PUSCH message are transmitted using one or more PUSCH resources or at least one PUSCH parameter.

[0155] The transmitting component 904 can send a request to the base station for a PUSCH repeat associated with the RRC connection request message of the RACH procedure. The transmitting component 904 can send at least one PUSCH repeat associated with the RRC connection request message based at least in part on the request. The transmitting component 904 can send a PUSCH message and at least one repeat of the PUSCH message based on the PUSCH repeat information.

[0156] The number and arrangement of components shown in Figure 9 are provided as examples. In practice, there may be additional components, fewer components, different components, or components with different arrangements compared to those shown in Figure 9. Furthermore, two or more components shown in Figure 9 may be implemented in a single component, or a single component shown in Figure 9 may be implemented as multiple distributed components. Alternatively or supplementarily, a set of components (one or more components) shown in Figure 9 may perform one or more functions, which are described as being performed by another set of components shown in Figure 9.

[0157] FIG10 is a block diagram illustrating an example of the hardware implementation of a UE 1000 employing a processing system 1014. For example, UE 1000 may be any one or more of the UEs shown in FIG1-4. In some cases, UE 1000 may be the device 900 illustrated in FIG9.

[0158] UE 1000 can be implemented using a processing system 1014 including one or more processors 1004. Examples of processors 1004 include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate control logic, individual hardware circuitry, and other suitable hardware configured to perform the various functions described herein. In various instances, UE 1000 can be configured to perform any one or more of the functions described herein. That is, the processor 1004 used in UE 1000 can be used to implement any one or more of the processes and programs described below and shown in Figures 5-6.

[0159] In this example, the processing system 1014 can be implemented using a bus architecture, typically represented by bus 1002. Bus 1002 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system 1014. Bus 1002 communicatively couples together various circuits including one or more processors (typically represented by processor 1004), memory 1005, and computer-readable media (typically represented by computer-readable media 1006). Bus 1002 may also connect various other circuits, such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art to which this invention pertains and will therefore not be described further. Bus interface 1008 provides an interface between bus 1002 and transceiver 1010. Transceiver 1010 provides a communication interface or a unit for communicating with various other devices via a transmission medium. Depending on the nature of the device, a user interface 1012 may also be provided (e.g., keyboard, display, speaker, microphone, joystick).

[0160] In some embodiments of the present invention, 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 embodiments, resource management circuitry 1040 may include or be included in determination component 908 illustrated in FIG. 9. In some embodiments of the present invention, processor 1004 may include communication management circuitry 1042 configured for various functions, including, for example, transmitting and receiving communications. For example, in some embodiments, communication management circuitry 1042 may include or be included in receiving component 902 and / or transmitting component 904 illustrated in FIG. 9. In some embodiments of the present invention, processor 1004 may include transmit power management circuitry 1044 configured for various functions, including, for example, determining and configuring transmit power for transmission. For example, in some embodiments, transmit power management circuitry 1044 may include or be included in determination component 908 and / or transmitting component 904 illustrated in FIG. 9.

[0161] The processor 1004 is responsible for managing the bus 1002 and general processing, including executing software stored on the computer-readable medium 1006. When executed by the processor 1004, the software causes the processing system 1014 to perform the various functions described below for any particular device. The computer-readable medium 1006 and memory 1005 can also be used to store data manipulated by the processor 1004 during software execution.

[0162] One or more processors 1004 in the processing system can execute software. Software should be interpreted broadly as instructions, instruction sets, code, code fragments, program code, program, subprogram, software component, application, software application, software suite, convention, sub-convention, object, executable program, running thread, program, function, etc., regardless of whether it is called software, firmware, middleware, microcode, hardware description language, or otherwise. Software may reside on computer-readable media 1006. Computer-readable media 1006 may be non-transitory computer-readable media. As examples, non-transitory computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic stripes), optical discs (e.g., compact discs (CDs) or digital versatile discs (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key floppy disk drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electronically erasable PROM (EEPROM), temporary storage, removable disks, and any other suitable media for storing software and / or instructions that can be accessed and read by a computer. Computer-readable media 1006 may reside in, be outside of, or be distributed across multiple entities including processing system 1014. Computer-readable media 1006 may be implemented in a computer program product. For example, a computer program product may include computer-readable media within packaging material. Those skilled in the art to which this invention pertains will recognize how best to achieve the functionality presented throughout this document, depending on the specific application and the overall design constraints imposed on the system.

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

[0164] The number and arrangement of components shown in Figure 10 are provided as examples. In practice, there may be additional components, fewer components, different components, or components with different arrangements compared to those shown in Figure 10. Furthermore, two or more components shown in Figure 10 may be implemented in a single component, or a single component shown in Figure 10 may be implemented as multiple distributed components. Alternatively or supplementarily, a set of components (one or more components) shown in Figure 10 may perform one or more functions, which are described as being performed by another set of components shown in Figure 10.

[0165] FIG11 is a block diagram of an example device 1100 for wireless communication. Device 1100 may be a base station, or a base station may include device 1100. In some embodiments, device 1100 includes a receiving component 1102 and a transmitting component 1104, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1100 can use the receiving component 1102 and the transmitting component 1104 to communicate with another device 1106 (e.g., a UE, a base station, or another wireless communication device). As further shown, device 1100 may include a determining component 1108.

[0166] In some embodiments, device 1100 may be configured to perform one or more operations described herein in conjunction with FIG. 4. Alternatively or additionally, device 1100 may be configured to perform one or more programs described herein, such as program 700 of FIG. 7, program 800 of FIG. 8, or a combination thereof. In some embodiments, device 1100 and / or one or more components shown in FIG. 11 may include one or more components of the UE described above in conjunction with FIG. 2. Alternatively or additionally, one or more components shown in FIG. 11 may be implemented within one or more components described above in conjunction with FIG. 2. Alternatively or additionally, one or more components in the set of components may be implemented at least partially as software stored in 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.

[0167] The receiving unit 1102 may receive communications from the device 1106, such as reference signals, control information, data communications, or combinations thereof. The receiving unit 1102 may provide the received communications to one or more other components of the device 1100. In some embodiments, the receiving unit 1102 may perform signal processing on the received communications (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of the device 1106. In some embodiments, the receiving unit 1102 may include one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof from the base station described above in conjunction with FIG2.

[0168] The transmitting component 1104 can transmit communications to the device 1106, such as reference signals, control information, data communications, or combinations thereof. In some embodiments, one or more other components of the device 1106 can generate communications and provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some embodiments, the transmitting component 1104 can perform signal processing on the generated communications (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) and can transmit the processed signals to the device 1106. In some embodiments, the transmitting component 1104 may include one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof from the base station described above in conjunction with FIG2. In some embodiments, the transmitting component 1104 may be co-located with the receiving component 1102 in the transceiver.

[0169] The receiving unit 1102 can receive from the UE a request for PUSCH repetition associated with the RRC connection request message for the RACH procedure. The receiving unit 1102 can use one or more spare frequency resources for PRACH transmission to receive PRACH messages from the UE.

[0170] The determining component 1108 may determine PUSCH repetition information based on one or more spare frequency resources used for receiving PRACH messages, wherein the use of one or more spare frequency resources transmits PUSCH repetition information. In some embodiments, the determining component 1108 may include one or more antennas, modulators, transmit MIMO processors, transmit processors, demodulators, MIMO detectors, receive processors, controllers / processors, memory, or combinations thereof of the base station described above in conjunction with FIG2. In some embodiments, the determining component 1108 may include receive component 1102 and / or transmit component 1104.

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

[0172] The transmitting unit 1104 can transmit at least one indication of one or more PUSCH resources or PUSCH parameters based on PUSCH duplication information, wherein at least one of one or more PUSCH resources or PUSCH parameters is used to receive PUSCH messages and at least one duplication of PUSCH messages. The transmitting unit 1104 can transmit resource parameters indicating one or more spare frequency resources from the base station, wherein the one or more spare frequency resources are determined based on the resource parameters. The transmitting unit 1104 can transmit at least one transmit power parameter to the UE.

[0173] The number and arrangement of components shown in Figure 11 are provided as examples. In practice, there may be additional components, fewer components, different components, or components with different arrangements compared to those shown in Figure 11. Furthermore, two or more components shown in Figure 11 may be implemented in a single component, or a single component shown in Figure 11 may be implemented as multiple distributed components. Alternatively or supplementarily, a set of components (one or more components) shown in Figure 11 may perform one or more functions, which are described as being performed by another set of components shown in Figure 11.

[0174] FIG12 is a conceptual diagram illustrating an example of a hardware implementation of an exemplary base station 1200 employing a processing system 1214. Depending on various aspects of this invention, any part or combination of elements, components, or elements can be implemented using a processing system 1214 including one or more processors 1204. For example, base station 1200 can be any one or more of the base stations shown in FIG1-4. In some aspects, base station 1200 can be the device 1100 illustrated in FIG11.

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

[0176] In some embodiments of this application, processor 1204 may include communication management circuitry 1240 configured for various functions, including, for example, transmitting and receiving communications. For example, communication management circuitry 1240 may include or be included in receiving component 1102 and / or transmitting component 1104 as illustrated in FIG. 11. In some embodiments of this application, processor 1204 may include resource management circuitry 1242 configured for various functions, including, for example, determining communication resources to be used. For example, resource management circuitry 1242 may include or be included in determining component 1108 as illustrated in FIG. 11. In some embodiments of this application, processor 1204 may include transmit power management circuitry 1244 configured for various functions, including, for example, determining and configuring transmit power for transmission. For example, transmit power management circuitry 1244 may include or be included in determining component 1108 and / or transmitting component 1104 as illustrated in FIG. 11.

[0177] In one or more instances, the computer-readable storage medium 1206 may include communication management software / instructions 1260 configured for various functions, including, for example, sending and receiving communications. For example, the communication management software / instructions 1260 may include or be included in the receiving component 1102 and / or the transmitting component 1104 illustrated in FIG. 11. In one or more instances, the computer-readable storage medium 1206 may include resource management software / instructions 1262 configured for various functions, including, for example, determining communication resources to be used. For example, the resource management software / instructions 1262 may include or be included in the determining component 1108 illustrated in FIG. 11. In one or more instances, 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 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 illustrated in FIG. 11.

[0178] The following provides an overview of some aspects of the content of this case:

[0179] State 1: A method of wireless communication performed by a user equipment (UE), comprising: sending to a base station a request for an entity uplink shared channel (PUSCH) repeat associated with a radio resource control (RRC) connection request message of a random access channel (RACH) procedure; and sending at least one PUSCH repeat associated with the RRC connection request message based at least in part on the request.

[0180] State 2: According to the method of State 1, wherein the request indication for PUSCH repetition corresponds to one or more suggested parameters for PUSCH repetition.

[0181] State 3: According to the method of State 2, one or more of the recommended parameters indicate the number of PUSCH repetitions.

[0182] State 4: The method according to any of the states 1-3, wherein the request for PUSCH repetition indicates a request for the aggregated demodulated reference signal used for cross-time slot channel estimation.

[0183] State 5: The method according to any of the states 1-4, wherein the request for PUSCH repeat includes the request for PUSCH repeat associated with one or more transport configuration indicators.

[0184] State 6: The method according to any of the states 1-5, wherein the request for PUSCH repetition includes the request for PUSCH repetition utilizing frequency hopping.

[0185] State 7: The method according to any of the states 1-6, wherein sending a request for PUSCH repetition includes sending a physical RACH (PRACH) message indicating a request for PUSCH repetition.

[0186] State 8: According to the method of State 7, wherein sending a request for PUSCH repetition includes repeating the PRACH message in multiple RACH instances.

[0187] State 9: The method according to any of the states 7 or 8, wherein sending a request for PUSCH repetition includes transmitting a PRACH preamble signal selected from a subset of PRACH preamble signals in the PRACH preamble signal set, wherein the subset indicates a request for PUSCH repetition.

[0188] State 10: The method according to any of the states 7-9, wherein sending a request for PUSCH repetition includes sending a PRACH message using a subset of ROs in the RACH occasion (RO) set, wherein the subset of ROs indicates a request for PUSCH repetition.

[0189] State 11: The method according to any of the states 7-10, wherein sending a request for PUSCH repetition includes sending a PRACH message using a PRACH format indicating a request for PUSCH repetition.

[0190] State 12: The method according to any of the states 7-11, wherein sending a PRACH message includes sending a PRACH message based at least in part on one or more PRACH parameters.

[0191] State 13: The method according to State 12 further includes selecting one or more PRACH parameters based at least in part on the relationship between one or more PRACH parameters and one or more request parameters corresponding to a request for repeating PUSCH.

[0192] State 14: According to the method of state 13, it also includes the parameter configuration of receiving the indication relationship from the base station.

[0193] State 15: According to the method of State 14, the parameter configuration is carried in the system information.

[0194] State 16: According to the method of State 15, the system information includes the remaining minimum system information.

[0195] State 17: The method described according to any of the states 13-16, wherein the relationship is indicated by the wireless communication standard.

[0196] State 18: The method according to any of the states 1-17 further includes determining that one or more triggering criteria are met, wherein sending a request for PUSCH repetition includes sending the request for PUSCH repetition at least in part based on the determination that one or more triggering criteria are met.

[0197] State 19: According to the method of State 18, it also includes receiving a trigger configuration indicating one or more trigger standards from the base station.

[0198] State 20: According to the method of State 19, the trigger configuration is carried in the system information.

[0199] State 21: According to the method of State 20, the system information includes the remaining minimum system information.

[0200] State 22: The method according to any of the states 18-21, wherein one or more triggering criteria include a first reference signal received power (RSRP) threshold.

[0201] State 23: The method according to state 22 further includes determining the RSRP based on the first synchronization signal block (SSB), wherein determining that one or more triggering criteria are satisfied includes determining that the RSRP based on the first SSB satisfies the first RSRP threshold.

[0202] State 24: According to the method of State 23, one or more triggering criteria include a second RSRP threshold.

[0203] State 25: The method according to State 24 further includes determining the RSRP based on the second SSB, wherein determining that one or more triggering criteria are satisfied includes determining that the RSRP based on the second SSB satisfies the second RSRP threshold.

[0204] State 26: According to the method of State 25, wherein the request instruction for PUSCH repetition is at least partially based on determining a first number of requested PUSCH repetitions that satisfy a first RSRP threshold based on a first SSB, and wherein the request instruction for PUSCH repetition is at least partially based on determining a second number of requested PUSCH repetitions that satisfy a second RSRP threshold based on a second SSB.

[0205] State 27: The method described according to any of the states 18-27, wherein one or more triggering criteria are indicated in the wireless communication standard.

[0206] State 28: The method according to any of the states 1-27, wherein sending at least one PUSCH repeat comprises sending at least one PUSCH repeat based at least in part on sending a request for a PUSCH repeat.

[0207] State 29: The method according to any of the states 1-28 further includes: receiving a Random Access Response (RAR) message from a base station, wherein the RAR message indicates at least one of the following: a PUSCH resource for an RRC connection request message, or a PUSCH parameter associated with an RRC connection request message; and determining at least one of a PUSCH repeat parameter or a PUSCH repeat resource based at least in part on the RAR message.

[0208] State 30: The method according to State 29, wherein determining at least one of the PUSCH repeat parameters or PUSCH repeat resources includes determining at least one of the PUSCH repeat parameters or PUSCH repeat resources based at least in part on one or more rules indicated by the wireless communication standard.

[0209] State 31: The method according to any of the states 1-30 further includes receiving an indication from the base station to grant permission for a PUSCH repeat request, wherein the permission for a PUSCH repeat request corresponds to at least a portion of a PUSCH repeat request.

[0210] State 32: According to the method of State 31, wherein an instruction to allow repeated PUSCH requests is carried in the Random Access Response (RAR) message.

[0211] State 33: According to the method of State 32, wherein an indication of permission to repeatedly request PUSCH is carried in the entity downlink control channel portion of the RAR message.

[0212] Sample 34: A method of wireless communication performed by a base station, comprising: receiving from a user equipment (UE) a request for an entity uplink shared channel (PUSCH) repeat associated with a radio resource control (RRC) connection request message in connection with a random access channel (RACH) procedure; and receiving at least one PUSCH repeat associated with the RRC connection request message based at least in part on the request.

[0213] State 35: According to the method of State 34, wherein the request indication for PUSCH repetition corresponds to one or more suggested parameters for PUSCH repetition.

[0214] State 36: According to the method of State 35, one or more of the recommended parameters indicate the number of PUSCH repetitions.

[0215] State 37: The method according to any of the states 34-36, wherein the request for PUSCH repetition indicates a request for the aggregated demodulated reference signal for cross-time slot channel estimation.

[0216] State 38: The method according to any of the states 34-37, wherein the request for PUSCH repeat includes the request for PUSCH repeat associated with one or more transport configuration indicators.

[0217] State 39: The method according to any of the states 34-38, wherein the request for PUSCH repetition includes the request for PUSCH repetition utilizing frequency hopping.

[0218] State 40: The method according to any of the states 34-39, wherein receiving a request for PUSCH repetition includes receiving a physical RACH (PRACH) message indicating a request for PUSCH repetition.

[0219] State 41: The method according to State 40, wherein receiving a request for PUSCH repetition includes receiving repeated PRACH messages in a plurality of RACH instances.

[0220] State 42: The method according to one of states 40 or 41, wherein receiving a request for PUSCH repetition includes receiving a PRACH preamble signal selected from a subset of PRACH preamble signals in a set of PRACH preamble signals, wherein the subset indicates a request for PUSCH repetition.

[0221] State 43: The method according to any of the states 40-42, wherein receiving a request for PUSCH repetition includes receiving a PRACH message using a subset of ROs in the RACH occasion (RO) set, wherein the subset of ROs indicates a request for PUSCH repetition.

[0222] State 44: The method according to any of the states 40-43, wherein receiving a request for PUSCH repetition includes receiving a PRACH message using a PRACH format indicating a request for PUSCH repetition.

[0223] State 45: The method according to any of the states 40-44, wherein receiving a PRACH message includes receiving a PRACH message at least in part based on one or more PRACH parameters.

[0224] State 46: According to the method of State 45, the selection of one or more PRACH parameters is based at least in part on the relationship between one or more PRACH parameters and one or more request parameters corresponding to a request for repeating PUSCH.

[0225] State 47: According to the method of state 46, it also includes sending parameter configuration of indication relationship to UE.

[0226] State 48: According to the method of State 46 or 47, the parameter configuration is carried in the system information.

[0227] State 49: According to the method of State 48, the system information includes the remaining minimum system information.

[0228] State 50: The method described according to any of the states 46-49, wherein the relationship is indicated by a wireless communication standard.

[0229] State 51: The method according to any of the states 34-50, wherein receiving a request for PUSCH repetition includes receiving the request for PUSCH repetition based at least in part on a decision regarding the satisfaction of one or more triggering criteria.

[0230] State 52: The method according to state 51 further includes sending a trigger configuration indicating one or more trigger criteria to the UE.

[0231] State 53: According to the method of state 52, the trigger configuration is carried in the system information.

[0232] State 54: According to the method of state 53, the system information includes the remaining minimum system information.

[0233] State 55: The method according to any of the states 51-54, wherein one or more triggering criteria include a first reference signal received power (RSRP) threshold.

[0234] State 56: According to the method of State 55, the decision regarding the satisfaction of one or more triggering criteria includes the decision regarding the RSRP based on the first synchronization signal block (SSB) satisfying the first RSRP threshold.

[0235] State 57: According to the method of State 56, one or more triggering criteria include a second RSRP threshold.

[0236] State 58: According to the method of State 57, the decision regarding the satisfaction of one or more triggering criteria includes the decision regarding the satisfaction of the second RSRP threshold based on the second SSB.

[0237] State 59: According to the method of State 58, wherein the request instruction for PUSCH repetition is at least partially based on a first number of requested PUSCH repetitions based on a decision that the RSRP based on the first SSB satisfies a first RSRP threshold, and wherein the request instruction for PUSCH repetition is at least partially based on a second number of requested PUSCH repetitions based on a decision that the RSRP based on the second SSB satisfies a second RSRP threshold.

[0238] State 60: The method according to any of the states 51-60, wherein one or more triggering criteria are indicated in a wireless communication standard.

[0239] State 61: The method according to any of the states 34-60, wherein receiving at least one PUSCH repeat comprises receiving at least one PUSCH repeat based at least in part on a request for a PUSCH repeat.

[0240] State 62: The method according to any of the states 34-61 further includes: sending a Random Access Response (RAR) message to the UE, wherein the RAR message indicates at least one of the following: a PUSCH resource for an RRC connection request message, or a PUSCH parameter associated with an RRC connection request message.

[0241] State 63: The method according to State 62, wherein the determination of at least one of the PUSCH repeat parameters or PUSCH repeat resources includes at least in part based on the determination of at least one of the PUSCH repeat parameters or PUSCH repeat resources based on one or more rules indicated by the wireless communication standard.

[0242] State 64: The method according to any of the states 34-63 further includes sending an indication to the UE to allow a PUSCH repeat request, wherein the PUSCH repeat request permission corresponds to at least a portion of the PUSCH repeat request.

[0243] State 65: According to the method of State 64, wherein an instruction to allow repeated PUSCH requests is carried in the Random Access Response (RAR) message.

[0244] State 66: The method according to one of State 64 or 65, wherein an indication for permission to repeatedly request PUSCH is carried in the entity downlink control channel portion of the RAR message.

[0245] Sample 67: A method for wireless communication by a user equipment (UE) includes: determining one or more backup frequency resources for physical random access channel (PRACH) transmission, wherein the use of one or more backup frequency resources transmits physical uplink shared channel (PUSCH) repeat information; and using one or more backup frequency resources for transmitting PUSCH repeat information to send a PRACH message to a base station.

[0246] State 68: According to the method of State 67, one or more spare frequency resources are different from one or more frequency resources used for PRACH transmissions associated with a single PUSCH transmission without PUSCH repetition.

[0247] State 69: The method according to one of state 67 or 68 further includes: sending a PUSCH message based on PUSCH repeat information and at least one repeat of the PUSCH message.

[0248] State 70: The method according to any of the states 67-69 further includes: receiving an indication of one or more PUSCH resources or at least one of PUSCH parameters based on PUSCH repeat information, wherein one or more PUSCH resources or at least one of PUSCH parameters are used to send a PUSCH message and at least one repeat of the PUSCH message.

[0249] State 71: The method according to any of the states 67-70 further includes: receiving from the base station resource parameters indicating one or more backup frequency resources, wherein the one or more backup frequency resources are determined based on the resource parameters.

[0250] State 72: According to the method of State 71, resource parameters are received via system information.

[0251] State 73: According to the method of state 72, the system information includes the remaining minimum system information (RMSI).

[0252] State 74: The method according to any of the states 71-73, wherein the resource parameters include a frequency offset, and wherein determining one or more spare frequency resources comprises: determining one or more spare frequency resources by applying the frequency offset to one or more frequency resources for a PRACH transmission associated with a single PUSCH transmission without PUSCH repetition.

[0253] State 75: The method according to any of the states 67-74 further includes: determining at least one transmit power parameter associated with the transmit power used for PUSCH repetition; and configuring the transmit power used for PUSCH repetition based on the at least one transmit power parameter.

[0254] State 76: According to the method of State 75, at least one transmit power parameter is determined based on one or more spare frequency resources determined for PRACH transmission.

[0255] State 77: The method according to one of state 75 or 76, wherein determining at least one transmit power parameter includes: receiving at least one transmit power parameter from the base station.

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

[0257] State 79: The method according to any of the states 67-78, wherein the PUSCH repeat information indicates one or more parameters corresponding to at least one of a request for PUSCH repeat or an indication of UE capability for PUSCH repeat.

[0258] State 80: The method according to State 79, wherein one or more parameters include at least one of the following: a request for PUSCH repetition, an 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 PUSCH repetition using demodulation reference signal (DMRS) aggregation for cross-time slot channel estimation, an indication that PUSCH repetition is associated with one or more transport configuration indicators (TCIs), or an indication that at least one of the request for PUSCH repetition or the indication of UE capability is associated with PUSCH repetition using frequency hopping.

[0259] State 81: The method according to one of states 79 or 80, wherein one or more spare frequency resources are different for each of one or more parameters.

[0260] Sample 82: A method for wireless communication by a base station, comprising: using one or more spare frequency resources for PRACH transmission to receive entity random access channel (PRACH) messages from a user equipment (UE); and determining entity uplink shared channel (PUSCH) duplication information based on one or more spare frequency resources used to receive the PRACH messages, wherein the use of one or more spare frequency resources transmits the PUSCH duplication information.

[0261] State 83: According to the method of State 82, one or more spare frequency resources are different from one or more frequency resources used for PRACH transmissions associated with a single PUSCH transmission without PUSCH repetition.

[0262] State 84: The method according to one of State 82 or 83 further includes: receiving a PUSCH message from the UE based on PUSCH repetition information and at least one repetition of the PUSCH message.

[0263] State 85: The method according to any of the states 82-84 further includes: sending an indication of one or more PUSCH resources or at least one of PUSCH parameters based on PUSCH repeat information, wherein one or more PUSCH resources or at least one of PUSCH parameters are used to receive PUSCH messages and at least one repeat of the PUSCH messages.

[0264] State 86: The method according to any of the states 82-85 further includes: sending resource parameters indicating one or more backup frequency resources, wherein the one or more backup frequency resources are determined based on the resource parameters.

[0265] State 87: According to the method of State 86, the resource parameters are sent via system information.

[0266] State 88: According to the method of state 87, the system information includes the remaining minimum system information (RMSI).

[0267] State 89: The method according to any of the states 86-88, wherein the resource parameters include a frequency offset, and wherein one or more spare frequency resources are determined by applying the frequency offset to one or more frequency resources for a PRACH transmission associated with a single PUSCH transmission without PUSCH repetition.

[0268] State 90: The method according to any of the states 82-87, wherein the transmit power for PUSCH repetition is configured based on at least one transmit power parameter associated with the transmit power.

[0269] State 91: According to the method of State 90, at least one transmit power parameter is determined based on one or more spare frequency resources determined for PRACH transmission.

[0270] State 92: The method according to one of state 90 or 91 further includes: sending at least one transmit power parameter to the UE.

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

[0272] State 94: The method according to any of the states 82-93, wherein the PUSCH repeat information indicates one or more parameters corresponding to at least one of a request for PUSCH repeat or an indication of UE capability for PUSCH repeat.

[0273] State 95: According to the method of State 94, one or more parameters include at least one of the following: a request for PUSCH repetition, an 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 PUSCH repetition using demodulation reference signal (DMRS) aggregation for cross-time slot channel estimation, an indication that PUSCH repetition is associated with one or more Transmission Configuration Indicators (TCIs), or an indication that at least one of the request for PUSCH repetition or the indication of UE capability is associated with PUSCH repetition using frequency hopping.

[0274] State 96: The method according to one of state 94 or 95, wherein one or more spare frequency resources are different for each of one or more parameters.

[0275] Sample 97: A method for wireless communication by a user equipment (UE) includes: sending an entity random access channel procedure (PRACH) message to a base station, which includes a request for an entity uplink shared channel (PUSCH) repeat associated with a radio resource control (RRC) connection request message of the random access channel (RACH) procedure; and sending at least one PUSCH repeat associated with the RRC connection request message based at least in part on the request.

[0276] State 98: According to the method of State 97, sending a request for PUSCH repetition includes repeating the PRACH message in multiple RACH instances.

[0277] State 99: The method according to any one of states 97 or 98, wherein sending a request for PUSCH repetition includes sending a PRACH preamble signal selected from a subset of PRACH preamble signals in the PRACH preamble signal set, wherein the subset indicates a request for PUSCH repetition.

[0278] State 100: The method according to any of the states 97-99, wherein sending a request for PUSCH repetition includes sending a PRACH message using a subset of ROs in the RACH occasion (RO) set, wherein the subset of ROs indicates a request for PUSCH repetition.

[0279] State 101: The method according to any of the states 97-100, wherein sending a PRACH message includes sending a PRACH message based at least in part on one or more PRACH parameters.

[0280] Sample 102: A method of wireless communication by a user equipment (UE) includes: sending an Entity Random Access Channel Procedure (PRACH) message to a base station and at least in part based on a decision regarding the satisfaction of one or more triggering criteria, the message including a request for an Entity Uplink Shared Channel (PUSCH) repetition associated with a Radio Resource Control (RRC) Connection Request message of the Random Access Channel (RACH) procedure, wherein the one or more triggering criteria include a reference signal received power threshold; and sending at least one PUSCH repetition associated with the RRC Connection Request message, at least in part based on the request.

[0281] State 103: According to the method of state 102, sending a request for PUSCH repetition includes sending a physical RACH (PRACH) message indicating a request for PUSCH repetition.

[0282] State 104: The method according to one of state 102 or 103 further includes determining RSRP based on a first synchronization signal block (SSB), wherein determining that one or more triggering criteria are satisfied includes determining that RSRP based on the first SSB satisfies a first RSRP threshold.

[0283] Sample 105: A method for wireless communication by a user equipment (UE) comprising: sending an Entity Random Access Channel Procedure (PRACH) message to a base station and at least in part based on a decision regarding the satisfaction of one or more triggering criteria, the message including a request for repetition of an Entity Uplink Shared Channel (PUSCH) associated with a Radio Resource Control (RRC) Connection Request message of the Random Access Channel (RACH) procedure, wherein the one or more triggering criteria include a reference signal received power threshold; receiving from the base station an indication of permission to grant a PUSCH repetition request, wherein the permission to grant a PUSCH repetition request corresponds to at least a portion of the PUSCH repetition request; and sending at least one PUSCH repetition associated with the RRC Connection Request message, at least in part based on the request.

[0284] State 106: According to the method of State 105, wherein an instruction to allow repeated PUSCH requests is carried in the Random Access Response (RAR) message.

[0285] State 107: An apparatus for wireless communication at 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 the method according to one or more of the states 1-33.

[0286] State 108: A device for wireless communication, comprising: a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the method according to one or more states 1-33.

[0287] State 109: An apparatus for wireless communication, comprising at least one unit for performing the method according to one or more states 1-33.

[0288] Format 110: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method described according to one or more of formats 1-33.

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

[0290] State 112: An apparatus for wireless communication at 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 the method according to one or more of states 34-66.

[0291] State 113: A device for wireless communication, comprising: a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the method according to one or more states 34-66.

[0292] State 114: An apparatus for wireless communication, comprising at least one unit for performing the method according to one or more states 34-66.

[0293] Format 115: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method described according to one or more formats 34-66.

[0294] State 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 the method according to one or more of the states 34-66.

[0295] State 117: An apparatus for wireless communication at 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 the method according to one or more of the states 67-81.

[0296] State 118: A device for wireless communication, comprising: a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the method according to one or more states 67-81.

[0297] State 119: An apparatus for wireless communication, comprising at least one unit for performing the method according to one or more states 67-81.

[0298] Sample 120: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method described in accordance with one or more of the samples 67-81.

[0299] State 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 the method according to one or more states 67-81.

[0300] Speech 122: An apparatus for wireless communication at 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 the method according to one or more of the specifications 82-96.

[0301] State 123: A device for wireless communication, comprising: a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the method according to one or more states 82-96.

[0302] State 124: An apparatus for wireless communication, comprising at least one unit for performing the method according to one or more states 82-96.

[0303] Sample 125: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method described in accordance with one or more of the samples 82-96.

[0304] Speech 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 the method according to one or more of the specifications 82-96.

[0305] State 127: An apparatus for wireless communication at 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 the method according to one or more of the states 97-101.

[0306] State 128: A device for wireless communication, comprising: a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the method according to one or more states 97-101.

[0307] State 129: An apparatus for wireless communication, comprising at least one unit for performing the method according to one or more states 97-101.

[0308] Sample 130: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method described in one or more of the samples 97-101.

[0309] State 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 the method according to one or more states 97-101.

[0310] State 132: An apparatus for wireless communication at 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 the method according to one or more of the states 102-104.

[0311] Speech 133: A device for wireless communication, comprising: a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the method according to one or more of the specifications 102-104.

[0312] State 134: An apparatus for wireless communication, comprising at least one unit for performing the method according to one or more states 102-104.

[0313] Format 135: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method described according to one or more formats 102-104.

[0314] Format 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 the method according to one or more formats 102-104.

[0315] State 137: An apparatus for wireless communication at 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 the method according to one or more of the states 105-106.

[0316] State 138: A device for wireless communication, comprising: a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the method according to one or more states 105-106.

[0317] State 139: An apparatus for wireless communication, comprising at least one unit for performing the method according to one or more states 105-106.

[0318] Format 140: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method described according to one or more formats 105-106.

[0319] Speech 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 the method according to one or more of the specifications 105-106.

[0320] The foregoing disclosure provides explanation and description, but is not intended to be exhaustive or to limit the forms to the precise forms disclosed. In view of the foregoing disclosure, modifications and variations are possible, or modifications and variations may be obtained from the implementation of these forms.

[0321] As used herein, the term "component" is intended to be interpreted broadly as hardware, and / or a combination of hardware and software. "Software" should be interpreted broadly as instructions, instruction sets, code, code fragments, code, programs, subprograms, software modules, applications, software applications, software packages, conventions, sub-conventions, objects, executable files, threads in execution, programs, and / or functions, regardless of whether it refers to software, firmware, middleware, microcode, hardware description languages, etc. As used herein, a processor is implemented in hardware, and / or a combination of hardware and software. It is evident that the systems and / or methods described herein can be implemented in various forms of hardware, and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limited to these forms. Therefore, this document describes the operation and behavior of the system and / or method without referencing any specific software code—it should be understood that software and hardware can be designed to implement the system and / or method, at least in part, based on the description herein.

[0322] As used herein, depending on the context, satisfying a threshold can mean a value 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.

[0323] Although specific combinations of features are stated in the request and / or disclosed in the specification, these combinations are not intended to limit the disclosure of each specimen. In fact, many of these features can be combined in ways not specifically stated in the request and / or disclosed in the specification. Although each dependent request listed below may directly depend on only one request, the disclosure of each specimen includes combinations of each dependent request with each of the other requests in the set of requests. As used herein, the phrase "at least one" in the list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to cover 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 ordering of a, b, and c).

[0324] Unless explicitly stated otherwise, no element, action, or instruction used herein should be construed as critical or necessary. Furthermore, as used herein, the articles “a” and “one” are intended to include one or more items and may be used interchangeably with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and may be used interchangeably with “one or more.” The term “only one” or similar language is used when only one item is desired. Furthermore, as used herein, the terms “having,” “possessing,” “containing,” etc., are intended to be open-ended terms. Furthermore, unless explicitly stated otherwise, the phrase “based on” is intended to mean “at least partially based on.” Furthermore, as used herein, the term "or" is intended to be inclusive when used in a series and may be used interchangeably with "and / or" unless otherwise expressly stated (e.g., if used in combination with "each" or "only one"). [Simplified Explanation of the Diagram]

[0027] To gain a more detailed understanding of the aforementioned features of this case, a more specific description summarized above can be obtained by referring to various embodiments, some of which are shown in the accompanying drawings. However, it should be noted that the drawings only illustrate specific typical embodiments of this case and are therefore not intended to limit its scope, as the description may allow for other equivalent embodiments. The same element symbols in different drawings may identify the same or similar elements.

[0028] Figure 1 is a diagram illustrating an example of a wireless network according to the contents of this case.

[0029] Figure 2 is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network, according to the contents of this case.

[0030] Figure 3 is an example of a four-step random access channel (RACH) operation according to the contents of this case.

[0031] Figure 4 is a diagram illustrating an example of a request associated with a repeated request for an entity uplink shared channel (PUSCH) in the RACH procedure for a Radio Resource Control (RRC) Connection Request message, according to the content of this case.

[0032] Figure 5-8 is a diagram illustrating an example procedure associated with a request for a repeating PUSCH message in the RACH procedure in accordance with the contents of this case, which is related to the RRC connection request message.

[0033] Figure 9-12 is a block diagram of an example device for wireless communication according to the contents of this case.

Claims

1. A user equipment (UE) for wireless communication, comprising: One memory; and one or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: send to a base station a request for an entity uplink shared channel (PUSCH) repeat associated with a radio resource control (RRC) connection request message of a random access channel (RACH) procedure, wherein the request includes a PRACH preamble selected from a subset of PRACH preambles in an entity RACH (PRACH) preamble set, and the subset of PRACH preambles indicates the request for PUSCH repeat; and send at least one PUSCH repeat associated with the RRC connection request message, at least in part based on the request.

2. According to Request Item 1, the request indication for PUSCH repetition corresponds to one or more suggested parameters for the PUSCH repetition.

3. According to request item 1, the memory and the one or more processors are configured to send an entity PRACH message indicating the request for PUSCH repetition when the request for PUSCH repetition is sent.

4. According to request item 3, the memory and the one or more processors are configured to repeat the PRACH message in a plurality of RACH instances when the request for PUSCH repetition is sent.

5. According to request item 3, when the request for PUSCH repetition is sent, the memory and the one or more processors are configured to use a subset of ROs in a RACH occasion (RO) set to send the PRACH message.

6. The UE according to request item 3, wherein when the PRACH message is sent, the memory and the one or more processors are configured to send the PRACH message at least in part based on one or more PRACH parameters.

7. The UE according to request item 6, wherein the memory and the one or more processors are further configured to select the one or more PRACH parameters at least in part based on a relationship between the one or more PRACH parameters and the one or more request parameters corresponding to the request for repeating for PUSCH.

8. The UE according to request item 7, wherein the memory and the one or more processors are further configured to receive a parameter configuration indicating the relationship from the base station.

9. According to request item 8 of the UE, where the parameter configuration is carried in the system information.

10. According to request item 9, the UE, wherein the system information includes the remaining minimum system information.

11. The UE according to request item 7, wherein the relationship is indicated by a wireless communication standard.

12. The UE according to request item 1, wherein the memory and the one or more processors are further configured to determine that one or more triggering criteria are met, wherein when the request for PUSCH repetition is sent, the memory and the one or more processors are configured to send the request for PUSCH repetition at least in part based on the determination that one or more triggering criteria are met.

13. The UE according to request item 12, wherein the memory and the one or more processors are further configured to receive a trigger configuration indicating the one or more trigger standards from the base station.

14. According to request item 13, the UE, wherein the trigger configuration is carried in the system information.

15. The UE according to request item 14, wherein the system information includes the remaining minimum system information.

16. The UE according to request item 12, wherein the one or more triggering criteria include a first reference signal received power (RSRP) threshold.

17. The UE according to request item 16, wherein the memory and the one or more processors are further configured to determine an RSRP based on a first synchronization signal block (SSB), wherein when it is determined that the one or more triggering criteria are met, the memory and the one or more processors are configured to determine that the RSRP based on the first SSB meets the first RSRP threshold.

18. The UE according to request item 17, wherein the one or more triggering criteria include a second RSRP threshold.

19. The UE according to request item 18, wherein the memory and the one or more processors are further configured to determine an RSRP based on a second SSB, wherein when it is determined that the one or more triggering criteria are met, the memory and the one or more processors are configured to determine that the RSRP based on the second SSB meets the second RSRP threshold.

20. The UE according to request item 19, wherein the request for PUSCH repetition indicates a first number of requested PUSCH repetitions based at least in part on determining that the RSRP based on the first SSB satisfies the first RSRP threshold, and wherein the request for PUSCH repetition indicates a second number of requested PUSCH repetitions based at least in part on determining that the RSRP based on the second SSB satisfies the second RSRP threshold.

21. The UE according to request item 12, wherein the one or more triggering criteria are indicated in a wireless communication standard.

22. The UE according to request item 1, wherein when the at least one PUSCH repeat is sent, the memory and the one or more processors are configured to send the at least one PUSCH repeat at least in part based on sending the request for the PUSCH repeat.

23. The UE according to request item 1, wherein the memory and the one or more processors are further configured to: receive a Random Access Response (RAR) message from the base station, wherein the RAR message indicates at least one of the following: a PUSCH resource for the RRC connection request message, or a PUSCH parameter associated with the RRC connection request message; and determine at least one of a PUSCH repeat parameter or a PUSCH repeat resource based at least in part on the RAR message.

24. The UE according to request item 23, wherein when determining the PUSCH repeat parameter or the at least one of the PUSCH repeat resources, the memory and the one or more processors are configured to determine the PUSCH repeat parameter or the at least one of the PUSCH repeat resources based at least in part on one or more rules indicated by a radio communication standard.

25. The UE according to request item 1, wherein the memory and the one or more processors are further configured to receive from the base station an indication of permission to grant a PUSCH repeat request, wherein the permission to grant a PUSCH repeat request corresponds to at least a portion of the PUSCH repeat request.

26. The UE according to request item 25, wherein the instruction to grant permission for repeated requests for the PUSCH is carried in a Random Access Response (RAR) message.

27. The UE according to request item 26, wherein the instruction to grant permission for repeated requests for the PUSCH is carried in an entity downlink control channel portion of the RAR message.

28. A user equipment (UE) for wireless communication, comprising: One memory; and one or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: send an Entity Random Access Channel Procedure (PRACH) message to a base station, the message including a request for an Entity Uplink Shared Channel (PUSCH) repeat associated with a Radio Resource Control (RRC) Connection Request message of a Random Access Channel (RACH) procedure, wherein the request includes a PRACH preamble selected from a subset of PRACH preamble signals in a set of PRACH preamble signals, and the subset of PRACH preamble signals indicates the request for the PUSCH repeat; and send at least one PUSCH repeat associated with the RRC Connection Request message, at least in part based on the request.

29. The UE according to request item 28, wherein when the request for repeating PUSCH is sent, the memory and the one or more processors are configured to repeat the PRACH message in a plurality of RACH instances.

30. The UE according to request item 28, wherein when the request for PUSCH repetition is sent, the memory and the one or more processors are configured to use a subset of ROs in a RACH occasion (RO) set to send the PRACH message.

31. The UE according to request item 28, wherein when the PRACH message is sent, the memory and the one or more processors are configured to send the PRACH message at least in part based on one or more PRACH parameters.

32. A user equipment (UE) for wireless communication, comprising: One memory; and one or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: send an Physical Random Access Channel Procedure (PRACH) message to a base station and at least in part based on a decision regarding the satisfaction of one or more triggering criteria, the message including 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, wherein the request includes a PRACH preamble selected from a subset of PRACH preamble signals in a set of PRACH preamble signals, and the subset of PRACH preamble signals indicates the request for PUSCH repetition, and the one or more triggering criteria include a reference signal received power threshold; and send at least one PUSCH repetition associated with the RRC Connection Request message, at least in part based on the request.

33. The UE according to request item 32, wherein when the request for PUSCH repetition is sent, the memory and the one or more processors are configured to send an entity PRACH message indicating the request for PUSCH repetition.

34. The UE according to request item 32, wherein the memory and the one or more processors are further configured to determine a reference signal received power (RSRP) based on a first synchronization signal block (SSB), wherein when it is determined that the one or more triggering criteria are met, the memory and the one or more processors are configured to determine that the RSRP based on the first SSB meets the RSRP threshold.

35. A user equipment (UE) for wireless communication, comprising: One memory; and one or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: transmit an Entity Random Access Channel Procedure (PRACH) message to a base station and at least in part based on a decision regarding the satisfaction of one or more triggering criteria, the message including a request for repetition of an Entity Uplink Shared Channel (PUSCH) associated with a Radio Resource Control (RRC) Connection Request message of a Random Access Channel (RACH) procedure, wherein the request includes a PRACH preamble selected from a subset of PRACH preamble signals in a set of PRACH preamble signals, and the subset of PRACH preamble signals indicates the request for PUSCH repetition, and the one or more triggering criteria include a reference signal received power threshold; receive from the base station an indication of permission to grant the PUSCH repetition request, wherein the permission to grant the PUSCH repetition request corresponds to at least a portion of the PUSCH repetition request; and transmit at least one PUSCH repetition associated with the RRC Connection Request message, at least in part based on the request.

36. The UE according to request item 35, wherein the instruction to grant permission for repeated requests for the PUSCH is carried in a Random Access Response (RAR) message.

37. A base station for wireless communication, comprising: One memory; and one or more processors operatively coupled to the memory, the memory and the one or more processors being configured to: receive from a user equipment (UE) a request for a physical uplink shared channel (PUSCH) repeat associated with a radio resource control (RRC) connection request message of a random access channel (RACH) procedure, wherein the request includes a PRACH preamble selected from a subset of PRACH preambles in a set of physical RACH (PRACH) preambles, and the subset of PRACH preambles indicates the request for PUSCH repeat; and receive at least one PUSCH repeat associated with the RRC connection request message, at least in part based on the request.

38. The base station according to request 37, wherein when the request for PUSCH repetition is received, the memory and the one or more processors are configured to receive an entity PRACH message indicating the request for PUSCH repetition.

39. The base station according to request 38, wherein when the PRACH message is received, the memory and the one or more processors are configured to receive the PRACH message at least in part based on one or more PRACH parameters, and wherein a selection of the one or more PRACH parameters is at least in part based on a relationship between the one or more PRACH parameters and one or more request parameters corresponding to the request for PUSCH repetition.

40. The base station according to request item 39, wherein the memory and the one or more processors are further configured to send a parameter configuration indicating the relationship to the UE.

41. The base station according to request item 37, wherein when receiving the request for PUSCH repetition, the memory and the one or more processors are configured to receive the request for PUSCH repetition at least in part based on a decision regarding the satisfaction of one or more trigger criteria, and wherein the memory and the one or more processors are further configured to send a trigger configuration indicating the one or more trigger criteria to the UE.

42. The base station according to request item 37, wherein the memory and the one or more processors are further configured to: send a Random Access Response (RAR) message to the UE, wherein the RAR message indicates at least one of the following: a PUSCH resource for the RRC connection request message, or a PUSCH parameter associated with the RRC connection request message.

43. The base station according to request item 37, wherein the memory and the one or more processors are further configured to send an indication to the UE to allow a PUSCH repeat request, wherein the PUSCH repeat request permission corresponds to at least a portion of the PUSCH repeat request.

44. The base station according to request 43, wherein the instruction to repeatedly request permission for the PUSCH is carried in a Random Access Response (RAR) message.

45. A method of wireless communication performed by a user equipment (UE), comprising the steps of: sending to a base station a request for a physical uplink shared channel (PUSCH) repeat associated with a radio resource control (RRC) connection request message of a random access channel (RACH) procedure, wherein the request includes a PRACH preamble selected from a subset of PRACH preambles in a set of physical RACH preambles, and the subset of PRACH preambles indicates the request for PUSCH repeat; and sending at least one PUSCH repeat associated with the RRC connection request message, at least in part based on the request.

46. ​​The method according to request item 45, wherein sending the request for PUSCH repetition includes the following steps: sending an entity PRACH message indicating the request for PUSCH repetition.

47. According to the method of request item 46, sending the request for PUSCH repetition includes the following steps: using a subset of ROs in a RACH occasion (RO) set to send the PRACH message.

48. The method according to request item 45 further includes determining that one or more triggering criteria are met, wherein sending the request for PUSCH repetition includes the step of: sending the request for PUSCH repetition at least in part based on the determination that one or more triggering criteria are met.

49. The method according to request item 48, wherein the one or more triggering criteria include a first reference signal received power (RSRP) threshold.

50. The method according to claim 45 further includes the step of: receiving from the base station an instruction to allow a PUSCH repeat request, wherein the PUSCH repeat request permission corresponds to at least a portion of the PUSCH repeat request.

Images