CN117178513A - Phase tracking reference signal transmission in radio resource control connection request message - Google Patents

Abstract

Various aspects of the present disclosure relate generally to wireless communications. In some aspects, a User Equipment (UE) may receive a Phase Tracking Reference Signal (PTRS) indication from a network node prior to transmission of a Radio Resource Control (RRC) connection request message, the PTRS indication to indicate presence of PTRS. The UE may transmit an RRC connection request message including the PTRS based at least in part on the PTRS indication. Numerous other aspects are described.

Description

Phase tracking reference signal transmission in radio resource control connection request message

Cross Reference to Related Applications

This patent application claims priority from U.S. provisional patent application No.63/175,921 entitled "PHASE TRACKING REFERENCE SIGNAL TRANSMISSION IN A RADIO RESOURCE CONTROL CONNECTION REQUEST MESSAGE (phase tracking reference signal transmission in radio resource control connection request message)" filed on month 16 of 2021, and U.S. non-provisional patent application No.17/652,141 entitled "PHASE TRACKING REFERENCE SIGNAL TRANSMISSION IN A RADIO RESOURCE CONTROL CONNECTION REQUEST MESSAGE (phase tracking reference signal transmission in radio resource control connection request message)" filed on month 23 of 2022, which are hereby expressly incorporated herein by reference.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for phase tracking reference signal transmission in a radio resource control connection request message.

Background

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple-access techniques capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access techniques 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 an enhancement set to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the third generation partnership project (3 GPP).

A wireless network may include several Base Stations (BSs) capable of supporting several User Equipment (UE) communications. The UE may communicate with the BS via the downlink and uplink. "downlink" (or "forward link") refers to the communication link from the BS to the UE, and "uplink" (or "reverse link") refers to the communication link from the UE to the BS. As will be described in more detail herein, a BS may be referred to as a node B, a gNB, an Access Point (AP), a radio head, a transmission-reception point (TRP), a New Radio (NR) BS, a 5G B node, and so on.

The above multiple access techniques have been adopted in various telecommunication standards to provide a common protocol that enables different user equipment to communicate at the urban, national, regional, and even global level. NR (which may also be referred to as 5G) is an enhanced set of LTE mobile standards promulgated by 3 GPP. NR is designed to better support mobile broadband internet access by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the Downlink (DL) (CP-OFDM), CP-OFDM and/or SC-FDM on the Uplink (UL) (e.g., also known as discrete fourier transform spread OFDM (DFT-s-OFDM)), and supporting beamforming, multiple Input Multiple Output (MIMO) antenna technology and carrier aggregation to improve spectral efficiency, reduce cost, improve service, utilize new spectrum, and integrate better with other open standards. As the demand for mobile broadband access continues to grow, further improvements to LTE, NR and other radio access technologies remain useful.

SUMMARY

In some aspects, a method of wireless communication performed by a User Equipment (UE) includes: receiving a Phase Tracking Reference Signal (PTRS) indication from a network node prior to transmission of a Radio Resource Control (RRC) connection request message, the PTRS indication being for indicating presence of PTRS; and transmitting an RRC connection request message including the PTRS based at least in part on the PTRS indication.

In some aspects, a method of wireless communication performed by a network node comprises: transmitting a PTRS indication indicating the presence of PTRS to the UE prior to transmission of the RRC connection request message; and receiving an RRC connection request message including the PTRS based at least in part on the PTRS indication.

In some aspects, a UE for wireless communication, comprises: a memory; and one or more processors coupled to the memory, the one or more processors configured to: receiving a PTRS indication indicating the presence of PTRS from the network node prior to transmission of the RRC connection request message; and transmitting an RRC connection request message including the PTRS based at least in part on the PTRS indication.

In some aspects, a network node for wireless communication comprises: a memory and one or more processors coupled to the memory configured to: transmitting a PTRS indication indicating the presence of PTRS to the UE prior to transmission of the RRC connection request message; and receiving an RRC connection request message including the PTRS based at least in part on the PTRS indication.

In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: receiving a PTRS indication indicating the presence of PTRS from the network node prior to transmission of the RRC connection request message; and transmitting an RRC connection request message including the PTRS based at least in part on the PTRS indication.

In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a network node, cause the network node to: transmitting a PTRS indication indicating the presence of PTRS to the UE prior to transmission of the RRC connection request message; and receiving an RRC connection request message including the PTRS based at least in part on the PTRS indication.

In some aspects, an apparatus for wireless communication comprises: means for receiving a PTRS indication indicating the presence of PTRS from the network node prior to transmission of the RRC connection request message; and means for transmitting an RRC connection request message including the PTRS based at least in part on the PTRS indication.

In some aspects, an apparatus for wireless communication comprises: means for transmitting a PTRS indication indicating the presence of PTRS to the UE prior to transmission of the RRC connection request message; and means for receiving an RRC connection request message including the PTRS based at least in part on the PTRS indication.

Aspects generally include a method, apparatus (device), system, computer program product, non-transitory computer readable medium, user equipment, network node, wireless communication device, and/or processing system substantially as described herein with reference to and as illustrated in the accompanying drawings and description.

The foregoing has outlined rather broadly the features and technical advantages of examples in accordance with the present disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The features of the concepts disclosed herein, both as to their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in connection with the accompanying drawings. Each of the figures is provided for the purpose of illustration and description, and is not intended to be limiting of the claims.

While aspects are described in this disclosure by way of illustration of some examples, those skilled in the art will appreciate that such aspects may be implemented in many different arrangements and scenarios. The techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and/or packaging arrangements. For example, some aspects may be implemented via an integrated chip embodiment or other non-module component based device (e.g., an end user device, a vehicle, a communication device, a computing device, industrial equipment, retail/shopping devices, medical devices, or artificial intelligence enabled devices). Aspects may be implemented in a chip-level component, a module component, a non-chip-level component, a device-level component, or a system-level component. Devices incorporating the described aspects and features may include additional components and features for achieving and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include several components (e.g., hardware components including antennas, radio Frequency (RF) chains, power amplifiers, modulators, buffers, processor(s), interleavers, adders, or summers) for analog and digital purposes. The aspects described herein are intended to be practical in a wide variety of devices, components, systems, distributed arrangements, or end user devices of various sizes, shapes, and configurations.

Brief Description of Drawings

So that the manner in which the above recited features of the present disclosure can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.

Fig. 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

Fig. 2 is a diagram illustrating an example in which a base station is in communication with a User Equipment (UE) in a wireless network according to the present disclosure.

Fig. 3 is a diagram illustrating an example of a Phase Tracking Reference Signal (PTRS) according to the present disclosure.

Fig. 4 is a diagram illustrating an example associated with PTRS transmission in a Radio Resource Control (RRC) connection request message in a Random Access Channel (RACH) procedure according to the present disclosure.

Fig. 5 and 6 are diagrams illustrating example processes associated with PTRS transmission in an RRC connection request message in a RACH procedure according to the present disclosure.

Fig. 7 and 8 are block diagrams illustrating example apparatuses for wireless communication according to this disclosure.

Detailed Description

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

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

It should be noted that although aspects may be described herein using terms commonly associated with 5G or NR Radio Access Technologies (RATs), aspects of the present disclosure may be applied to other RATs, such as 3G RATs, 4G RATs, and/or RATs after 5G (e.g., 6G).

Fig. 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (NR) network and/or an LTE network, etc. or may include elements thereof. Wireless network 100 may include several base stations 110 (shown as BS110a, BS110b, BS110c, and BS110 d) and other network entities. A Base Station (BS) is an entity that communicates with User Equipment (UE) and may also be referred to as an NR BS, node B, gNB, 5G B Node (NB), access point, transmission-reception point (TRP), and so forth. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to a coverage area of a BS and/or a BS subsystem serving the coverage area, depending on the context in which the term is used.

The BS may provide communication coverage for a macrocell, a picocell, a femtocell, and/or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG)). The BS for a macro cell may be referred to as a macro BS. The BS for a pico cell may be referred to as a pico BS. The BS for a femto cell may be referred to as a femto BS or a home BS. In the example shown in fig. 1, BS110a may be a macro BS for macro cell 102a, BS110b may be a pico BS for pico cell 102b, and BS110c may be a femto BS for femto cell 102 c. The BS may support one or more (e.g., three) cells. The terms "eNB," "base station," "NR BS," "gNB," "TRP," "AP," "node B," "5G NB," and "cell" may be used interchangeably herein.

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

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

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

The network controller 130 may be coupled to a set of BSs and may provide coordination and control of the BSs. The network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with each other directly or indirectly via a wireless or wired backhaul.

UEs 120 (e.g., 120a, 120b, 120 c) may be dispersed throughout wireless network 100, and each UE may be stationary or mobile. A UE may also be called an access terminal, mobile station, subscriber unit, station, etc. The UE may be a cellular telephone (e.g., a smart phone), a Personal Digital Assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a Wireless Local Loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, a super book, a medical device or equipment, a biometric sensor/device, a wearable device (smart watch, smart garment, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., music or video device, or satellite radio), a vehicle component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

Some UEs may be considered Machine Type Communication (MTC) UEs, or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, and/or location tags, which may communicate with a base station, another device (e.g., a remote device), or some other entity. The wireless node may provide connectivity to or to a network (e.g., a wide area network such as the internet or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered internet of things (IoT) devices and/or may be implemented as NB-IoT (narrowband internet of things) devices. Some UEs may be considered Customer Premise Equipment (CPE). UE 120 may be included within a housing that houses components of UE 120, such as processor components and/or memory components. In some aspects, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.

In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular RAT and may operate on one or more frequencies. RATs may also be referred to as radio technologies, air interfaces, etc. Frequencies may also be referred to as carriers, frequency channels, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

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

Devices of the wireless network 100 may communicate using electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices of the wireless network 100 may communicate using an operating frequency band having a first frequency range (FR 1) and/or may communicate using an operating frequency band having a second frequency range (FR 2), the first frequency range (FR 1) may span 410MHz to 7.125GHz, and the second frequency range (FR 2) may span 24.25GHz to 52.6GHz. The frequency between FR1 and FR2 is sometimes referred to as the mid-band frequency. Although a portion of FR1 is greater than 6GHz, FR1 is commonly referred to as the "sub-6 GHz" band. Similarly, FR2 is commonly referred to as the "millimeter wave" frequency band, although it is different from the Extremely High Frequency (EHF) frequency band (30 GHz-300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" frequency band. Thus, unless specifically stated otherwise, it should be understood that, if used herein, the term sub-6 GHz and the like may broadly represent frequencies less than 6GHz, frequencies within FR1, and/or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless specifically stated otherwise, it should be understood that, if used herein, the term "millimeter wave" or the like may broadly refer to frequencies within the EHF band, frequencies within FR2, and/or mid-band frequencies (e.g., less than 24.25 GHz). It is contemplated that the frequencies included in FR1 and FR2 may be modified, and that the techniques described herein are applicable to those modified frequency ranges.

As described herein, a node, which may be referred to as a "node," "network node," or "wireless node," may be a base station (e.g., base station 110), a UE (e.g., UE 120), a relay device, a network controller, an apparatus, a device, a computing system, one or more components of any of these, and/or another processing entity configured to perform one or more aspects of the techniques described herein. For example, the network node may be a UE. As another example, the network node may be a base station. The network node may be one or more components of an aggregated base station and/or a disaggregated base station. As an example, the first network node may be configured to communicate with the second network node or the third network node. The adjectives "first", "second", "third", etc., are used in connection with a discussion to make a contextual distinction between two or more modified nouns, and are not intended to be absolute modifiers that are applicable only to a corresponding node throughout the full document. For example, a network node may be referred to as a "first network node" in connection with one discussion and a "second network node" in connection with another discussion, or vice versa. Referring to a UE, a base station, apparatus, device, computing system, etc. may include disclosure of the UE, base station, apparatus, device, computing system, etc. as a network node. For example, the disclosure that the UE is configured to receive information from the base station also discloses that the first network node is configured to receive information from the second network node. Consistent with the present disclosure, once a particular example is extended in accordance with the present disclosure (e.g., a UE configured to receive information from a base station also discloses a first network node configured to receive information from a second network node), a wider example of a narrower example may be interpreted in the opposite manner, but in a wider open manner. In the above examples where the UE is configured to receive information from the base station also discloses that the first network node is configured to receive information from the second network node, "first network node" may refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, a first one or more components, a first processing entity, etc. configured to receive information from the second network; and "second network node" may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a first one or more components, a first processing entity, etc.

In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, communication manager 140 may receive a Phase Tracking Reference Signal (PTRS) indication from a network node prior to transmission of a Radio Resource Control (RRC) connection request message, the PTRS indication to indicate the presence of PTRS; and transmitting an RRC connection request message including the PTRS based at least in part on the PTRS indication. Additionally or alternatively, communication manager 140 may perform one or more other operations described herein.

In some aspects, network node 110 may include a communication manager 150. As described in more detail elsewhere herein, communication manager 150 may transmit a PTRS indication indicating the presence of PTRS to the UE prior to transmission of the RRC connection request message; and receiving an RRC connection request message including the PTRS based at least in part on the PTRS indication. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

As indicated above, fig. 1 is provided as an example. Other examples may differ from the example described with respect to fig. 1.

Fig. 2 is a diagram illustrating an example 200 in which a base station 110 is in communication with a UE 120 in a wireless network 100 according to the present disclosure. Base station 110 may be equipped with T antennas 234a through 234T, and UE 120 may be equipped with R antennas 252a through 252R, where in general T is 1 and R is 1.

At base station 110, transmit processor 220 may receive data for one or more UEs from data source 212, select one or more Modulation and Coding Schemes (MCSs) for each UE based at least in part on a Channel Quality Indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS(s) selected for the UE, and provide data symbols for all UEs. Transmit processor 220 may also process system information (e.g., for semi-Static Resource Partitioning Information (SRPI)) and control information (e.g., CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary Synchronization Signals (PSS) or Secondary Synchronization Signals (SSS)). A Transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide T output symbol streams to T Modulators (MODs) 232a through 232T. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. T downlink signals from modulators 232a through 232T may be transmitted via T antennas 234a through 234T, respectively.

In some aspects, the term "base station" (e.g., base station 110) may refer to an aggregated base station, a decomposed base station, and/or one or more components of a decomposed base station. For example, in some aspects, a "base station" may refer to a control unit, a distributed unit, a plurality of control units, a plurality of distributed units, and/or a combination thereof. In some aspects, the term "base station" or "network entity" may refer to a device configured to perform one or more functions, such as those described above in connection with base station 110. In some aspects, a "base station" may refer to a plurality of devices configured to perform the one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographic location or different geographic locations) may be configured to perform, or repeat the performance of, at least a portion of the functionality, and the term "base station" may refer to any one or more of these different devices. In some aspects, a "base station" may refer to one or more virtual base stations, one or more virtual base station functions, and/or a combination thereof. For example, in some cases, two or more base station functions may be instantiated on a single device. In some aspects, a "base station" may refer to one of the base station functions, but not another. In this way, a single device may include more than one base station.

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

The network controller 130 may include a communication unit 294, a controller/processor 290, and a memory 292. The network controller 130 may comprise, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via a communication unit 294.

Antennas (e.g., antennas 234a through 234t and/or antennas 252a through 252 r) may include or be included in one or more antenna panels, antenna groups, sets of antenna elements, and/or antenna arrays, etc. The antenna panel, antenna group, antenna element set, and/or antenna array may include one or more antenna elements. The antenna panel, antenna group, antenna element set, and/or antenna array may include a coplanar antenna element set and/or a non-coplanar antenna element set. The antenna panel, antenna group, antenna element set, and/or antenna array may include antenna elements within a single housing and/or antenna elements within multiple housings. The antenna panel, antenna group, antenna element set, and/or antenna array may include one or more antenna elements coupled to one or more transmission and/or reception components, such as one or more components of fig. 2.

On the uplink, at UE 120, transmit processor 264 may 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). Transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some aspects, a modulator and demodulator (e.g., MOD/DEMOD 254) of UE 120 may be included in the modem of UE 120. In some aspects, UE 120 includes a transceiver. The transceiver may include any combination of antenna(s) 252, modulator and/or demodulator 254, MIMO detector 256, receive processor 258, transmit 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 aspects of any of the methods described herein (e.g., as described with reference to fig. 4-8).

At base station 110, uplink signals from UE 120 as well as other UEs may be received by antennas 234, processed by demodulators 232, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller/processor 240. The base station 110 may include a communication unit 244 and communicate with the network controller 130 via the communication unit 244. Base station 110 may include a scheduler 246 to schedule UEs 120 for downlink and/or uplink communications. In some aspects, a modulator and demodulator (e.g., MOD/DEMOD 232) of base station 110 may be included in a modem of base station 110. In some aspects, the base station 110 comprises a transceiver. The transceiver may include any combination of antenna(s) 234, modulator and/or demodulator 232, MIMO detector 236, receive processor 238, transmit 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 aspects of any of the methods described herein (e.g., as described with reference to fig. 4-8).

The controller/processor 240 of the base station 110, the controller/processor 280 of the UE 120, and/or any other component(s) of fig. 2 may perform one or more techniques associated with PTRS transmission in an RRC connection request message of a Random Access Channel (RACH) procedure, as described in more detail elsewhere herein. In some aspects, a network node described herein may be a base station (e.g., base station 110), similar to a base station (e.g., base station 110), or included in a base station (e.g., base station 110). For example, controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component(s) of fig. 2 may perform or direct operations such as process 500 of fig. 5, process 600 of fig. 6, and/or other processes as described herein. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and/or memory 282 may include: a non-transitory computer readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of base station 110 and/or UE 120 (e.g., directly, or after compilation, conversion, and/or interpretation), may cause the one or more processors, UE 120, and/or base station 110 to perform or direct operations such as process 500 of fig. 5, process 600 of fig. 6, and/or other processes described herein. In some aspects, executing instructions may include executing instructions, converting instructions, compiling instructions, and/or interpreting instructions, among others.

In some aspects, the UE includes: means for receiving a PTRS indication indicating the presence of PTRS from the network node prior to transmission of the RRC connection request message; or means for transmitting an RRC connection request message including the PTRS based at least in part on the PTRS indication. Means for a UE to perform the operations described herein may include, for example, one or more of the antennas 252, the demodulator 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the modulator 254, the controller/processor 280, or the memory 282.

In some aspects, a network node comprises: means for transmitting a PTRS indication indicating the presence of PTRS to the UE prior to transmission of the RRC connection request message; or means for receiving an RRC connection request message including the PTRS based at least in part on the PTRS indication. Means for a network node to perform the operations described herein may include, for example, one or more of transmit processor 220, TX MIMO processor 230, modulator 232, antenna 234, demodulator 232, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.

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

As indicated above, fig. 2 is provided as an example. Other examples may differ from the example described with respect to fig. 2.

Fig. 3 is a diagram illustrating an example 300 of assigning PTRS and other signals and channels to resource elements according to the present disclosure.

Fig. 3 illustrates PTRS pilot signals (also referred to as PTRS pilot tones, PTRS signals, and/or PTRS) for an orthogonal frequency division multiplexing (CP-OFDM) communication system having a cyclic prefix. PTRS may be contiguous (as illustrated) or non-contiguous in the time domain. For UE 120, the PTRS may occupy one tone or several tones based at least in part on the scheduled bandwidth, MCS, signal-to-noise ratio (SNR), interference level, port mapping, and/or another attribute that may affect the received signal quality of the communication signal. The tones may be referred to as subcarriers.

PTRS may be used by UE 120 and/or base station 110 to perform phase tracking, phase estimation, and/or correction of oscillator phase noise, particularly for millimeter wave communications. PTRS may be embedded in a Physical Downlink Shared Channel (PDSCH) resource allocation or a Physical Uplink Shared Channel (PUSCH) allocation. In some cases, one PTRS port may be configured for downlink communication (e.g., within PDSCH resource allocation), and at most two PTRS ports may be configured for uplink communication (e.g., within PUSCH resource allocation). For CP-OFDM communications, PTRS may use the same sequence as the corresponding DMRS, which may be a Gold sequence (e.g., a Quadrature Phase Shift Keying (QPSK) modulated Gold sequence). In some aspects, the correspondence between PTRS ports and DMRS ports may be indicated by the base station to the UE (e.g., via DMRS-PTRS association indicated in the downlink control information). In some cases, for uplink communications, a greater number of DMRS ports (e.g., up to 4 DMRS ports) may be configured for the UE than the number of PTRS ports configured for the UE (e.g., up to 2 PTRS ports).

Higher SNR in PTRS may provide more accurate phase error estimation. Accordingly, in some aspects, PTRS may be located in tones with good channel conditions, high SNR, and/or high signal to interference plus noise ratio (SINR), which may result in more accurate phase tracking at UE 120. Increasing the number of PTRS may provide a more accurate phase error estimate. For example, an increased number of PTRSs may allow thermal noise to be averaged over a greater number of PTRSs. Furthermore, an increased number of PTRSs may allow for frequency diversity to be utilized.

However, using a large number of PTRSs may increase overhead. Furthermore, for a given number of PTRS in the scheduled bandwidth, the gain from increasing the number of PTRS may saturate. Accordingly, UEs 120 with large scheduled bandwidths may use a sparser PTRS frequency domain pattern. In contrast, UEs 120 with small scheduled bandwidths may use denser PTRS frequency domain patterns. In contrast to DMRS, PTRS may be relatively sparse in frequency. For example, one PTRS Resource Element (RE) may be used in every 2 or 4 Resource Blocks (RBs), and 4 or 6 DMRS REs may be used in each RB. As shown in fig. 3, PTRS may be relatively dense in time compared to DMRS.

The number of PTRSs required to achieve a certain performance requirement (e.g., bit error rate less than 0.5%, 1%, 2%, or other threshold) for a given scheduled bandwidth may depend on several factors, such as channel conditions, UE speed, UE capability, UE processing power, UE battery charge, mobility, and other factors that may affect communication system performance. A communication system with too few PTRSs may result in more retransmissions due to channel errors, which reduces throughput. Systems with too many PTRS can utilize valuable system bandwidth to minimize degradation of the channel error rate.

Some communication systems may use a fixed PTRS pattern (e.g., in the time and/or frequency domain), such as the PTRS pattern shown in fig. 3. In this case, the density of PTRS may be fixed both in terms of the number of PTRS and the resource elements carrying PTRS. Alternatively, some communication systems may use flexible PTRS configurations, where resource elements carrying PTRS may be flexibly configured. In some cases, PTRS is configured using RRC messages.

In some cases, PTRS may be used to facilitate joint channel estimation, such as, for example, when a UE cannot use DMRS bundling to maintain sufficient phase continuity for joint channel estimation. The DMRS may include a reference signal generated from a base sequence (such as a Zadoff-Chu sequence or Gold sequence). The DMRS may carry information for estimating a radio channel for demodulating an associated physical channel, e.g., a Physical Downlink Control Channel (PDCCH), PDSCH, physical Uplink Control Channel (PUCCH), or PUSCH. The design and mapping of DMRS may be specific to the physical channel that the DMRS uses for estimation. DMRS is UE-specific, may be beamformed, may be limited to scheduled resources (e.g., rather than transmitted on wideband), and may be transmitted only when necessary. DMRS is used for both downlink and uplink communications.

In some cases, a UE may associate or cluster multiple time domain resources (which may be referred to as uplink DMRS clusters and/or DMRS clusters) for purposes of joint channel estimation, in which case a base station may assume that the same precoder is used across the multiple time domain resources, and may coherently filter DMRS transmissions across the multiple time domain resources to improve the accuracy of the channel estimation.

However, in some cases, whether the UE supports PUSCH DMRS bundling and/or PUCCH DMRS bundling may depend on one or more UE capabilities for phase continuity maintenance. In some cases, the UE may not be able to perform phase continuity maintenance applicable to DMRS bundling. In some cases, indicating this capability to the base station prior to the RRC connection request message in the RACH procedure may result in excessive overhead of the Physical RACH (PRACH) request, even though the UE is able to maintain phase continuity. In some cases PTRS may be used to facilitate joint channel estimation for RRC connection request messages, which has been found to improve network performance in some cases. However, RRC signaling that may be used to configure PTRS is not available during initial access and/or RACH procedures. As a result, using PTRS to facilitate joint channel estimation may result in excessive overhead and computational resource consumption.

Some aspects of the techniques and apparatus described herein may facilitate joint channel estimation associated with RRC connection request messages using PTRS. For example, in some aspects, a network node may transmit and a UE may receive a PTRS indication indicating the presence of PTRS and/or PTRS transmission parameters. The UE may transmit an RRC connection request message including the PTRS based at least in part on the PTRS indication. In this way, some aspects may facilitate reducing excessive overhead and computing resource consumption and positively impacting network performance.

As indicated above, fig. 3 is provided as an example. Other examples may differ from the example described with respect to fig. 3.

Fig. 4 is a diagram illustrating an example 400 associated with PTRS transmission in an RRC connection request message in a four-step RACH procedure according to the present disclosure. As shown in fig. 4, the network node 402 and the UE 404 may communicate with each other to perform a four-step RACH procedure.

As shown by reference numeral 405, the network node 402 may transmit and the UE 404 may receive one or more Synchronization Signal Blocks (SSBs), as well as random access configuration information. In some aspects, the random access configuration information may be transmitted in and/or indicated by system information (e.g., one or more System Information Blocks (SIBs)) and/or SSBs, such as for contention-based random access. Additionally or alternatively, the random access configuration information may be transmitted in an RRC message and/or PDCCH order message triggering the RACH procedure, such as for contention-free random access. The random access configuration information may include one or more parameters to be used in a random access procedure, such as one or more parameters for transmitting RAM, and/or one or more parameters for receiving a Random Access Response (RAR).

As indicated by reference numeral 410, the UE 404 may transmit RAM, which may include a preamble (sometimes referred to as a random access preamble, PRACH preamble, or RAM preamble). The message including the preamble may be referred to as message 1, MSG1, first message, or initial message in the four-step RACH procedure. The random access message may include a random access preamble identifier.

As indicated by reference numeral 415, the network node 402 may transmit the RAR as a reply to the preamble. The message including the RAR may be referred to as message 2, MSG2, or a second message in the four-step random access procedure. In some aspects, the RAR may indicate a detected random access preamble identifier (e.g., received from the UE 404 in msg 1). Additionally or alternatively, the RAR may indicate a resource allocation to be used by the UE 404 to transmit message 3 (msg 3).

In some aspects, as shown, the RAR may include a PTRS indication. In some aspects, the PTRS indication may be separate from the RAR by the network node but still transmitted prior to transmission of the RRC connection request message. The PTRS indication may indicate the presence of PTRS. In some aspects, the PTRS indication may indicate one or more parameters associated with transmitting PTRS and/or PTRS repetition. As used herein, "duplicate" refers to a communication that is transmitted more than once and refers to an initial transmission of the communication or any subsequent retransmission of the communication.

For example, in some aspects, the UE 404 may obtain a PTRS repetition configuration. The PTRS repetition configuration may indicate at least one parameter associated with transmitting multiple repetitions of PTRS. The at least one parameter may be indicative of at least one of a transmission time or a repetition frequency density. In some aspects, the UE 404 may obtain the PTRS repetition configuration by receiving System Information (SI) indicating the PTRS repetition configuration. For example, PTRS repetition configuration may be indicated by SIB (e.g., SIB 1). In some aspects, the PTRS repetition configuration may be indicated by a wireless communication standard.

In some aspects, at least one parameter associated with transmitting the multiple repetitions of PTRS may be based at least in part on at least one parameter associated with transmission of the RRC connection request message. The at least one parameter associated with the transmission of the RRC connection request message may indicate at least one of a number of repetitions of the RRC connection request message, an MCS, or a bandwidth.

In some aspects, the network node 402 may transmit PDCCH communications for the RAR as part of the second step of the four-step random access procedure. The PDCCH communication may schedule PDSCH communication including RAR. For example, PDCCH communication may indicate resource allocation for PDSCH communication. In some aspects, PDCCH communication may indicate resource allocation for RRC connection request messages. The resource allocation may be indicated by one or more Downlink Control Information (DCI) transmissions associated with the PDCCH communication. In some aspects, the PDCCH communication may include a PTRS indication. Also, as part of the second step of the four-step random access procedure, the network node 402 may transmit PDSCH communications for the RAR as scheduled by PDCCH communications. The RAR may be included in a MAC Protocol Data Unit (PDU) of PDSCH communication.

In some aspects, the UE 404 may receive the PTRS indication by interpreting a bit field of the RAR to identify the PTRS indication. In some aspects, the PDCCH may schedule retransmission of the RRC connection request message, and receiving the PTRS indication may include interpreting a bit field of a downlink control information transmission corresponding to the PDCCH to identify the PTRS indication. In some aspects, receiving the PTRS indication may include receiving an indication of RRC connection request message repetition. In some aspects, the UE 404 may receive the PTRS indication by receiving an indication of a number of repetitions of the RRC connection request message.

In some aspects, the UE 404 may receive the PTRS indication by determining that an indication condition is met. For example, in some aspects, determining that the indication condition is met may include determining that a pair of consecutive RRC connection request message repetitions includes a first repetition associated with a first uplink time slot and a second repetition associated with a second uplink time slot, wherein at least one third uplink time slot is disposed between the first uplink time slot and the second uplink time slot. In some aspects, network node 402 may transmit and UE 404 may receive a PTRS indication configuration indicating one or more rules for implicitly indicating the existence of PTRS. In some aspects, receiving the PTRS indication configuration may include receiving Remaining Minimum System Information (RMSI). The SIB may indicate the RMSI.

As indicated by reference numeral 420, the UE 404 may transmit an RRC connection request message. The RRC connection request message may be referred to as message 3, MSG3, or a third message of the four-step random access procedure. In some aspects, the RRC connection request may include a UE identifier, uplink Control Information (UCI), and/or PUSCH communications (e.g., an RRC connection request).

As shown by reference numeral 425, the network node 402 may transmit an RRC connection setup message. The RRC connection setup message may be referred to as message 4, MSG4, or fourth message of the four-step random access procedure. In some aspects, the RRC connection setup message may include the detected UE identifier, timing advance value, and/or contention resolution information. As indicated by reference numeral 430, if the UE 404 successfully receives the RRC connection setup message, the UE 404 may transmit a hybrid automatic repeat request (HARQ) Acknowledgement (ACK).

As indicated above, fig. 4 is provided as an example. Other examples may differ from the example described with respect to fig. 4.

Fig. 5 is a diagram illustrating an example process 500 performed, for example, by a UE, in accordance with the present disclosure. The example process 500 is an example in which a UE (e.g., the UE 404) performs operations associated with phase tracking reference signal transmission in a radio resource control connection request message.

As shown in fig. 5, in some aspects, process 500 may include: a PTRS indication indicating the presence of PTRS is received from the network node prior to transmission of the RRC connection request message (block 510). For example, the UE (e.g., using the receiving component 702 depicted in fig. 7) may receive a PTRS indication from the network node indicating the existence of PTRS prior to transmission of the RRC connection request message, as described above.

As further shown in fig. 5, in some aspects, process 500 may include transmitting an RRC connection request message including a PTRS based at least in part on the PTRS indication (block 520). For example, the UE (e.g., using transmission component 704 depicted in fig. 7) may transmit an RRC connection request message including the PTRS based at least in part on the PTRS indication, as described above.

Process 500 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in conjunction with one or more other processes described elsewhere herein.

In a first aspect, receiving the PTRS indication includes receiving a RAR including the PTRS indication.

In a second aspect, alone or in combination with the first aspect, receiving the PTRS indication includes interpreting a bit field of the RAR to identify the PTRS indication.

In a third aspect, alone or in combination with one or more of the first and second aspects, receiving the PTRS indication comprises receiving a PDCCH transmission comprising the PTRS indication, wherein the PDCCH transmission schedules a random access response.

In a fourth aspect, alone or in combination with the third aspect, receiving the PTRS indication includes interpreting a bit field of a downlink control information transmission corresponding to the PDCCH to identify the PTRS indication.

In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, receiving the PTRS indication comprises receiving a PDCCH comprising the PTRS indication, wherein the PDCCH schedules retransmission of RRC connection request messages.

In a sixth aspect, alone or in combination with the fifth aspect, receiving the PTRS indication includes interpreting a bit field of a downlink control information transmission corresponding to the PDCCH to identify the PTRS indication.

In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, receiving the PTRS indication comprises receiving an indication of RRC connection request message repetition.

In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, receiving the PTRS indication comprises receiving an indication of a number of repetitions of the RRC connection request message.

In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, receiving the PTRS indication includes determining that an indication condition is met.

In a tenth aspect, alone or in combination with the ninth aspect, determining that the indication condition is met comprises determining that a pair of consecutive RRC connection request message repetitions includes a first repetition associated with a first uplink time slot and a second repetition associated with a second uplink time slot, wherein at least one third uplink time slot is arranged between the first uplink time slot and the second uplink time slot.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, process 500 includes receiving a PTRS indication configuration that indicates one or more rules for implicitly indicating the presence of PTRS.

In a twelfth aspect, alone or in combination with the eleventh aspect, receiving the PTRS indication configuration includes receiving RMSI.

In a thirteenth aspect, alone or in combination with the twelfth aspect, receiving the RMSI includes receiving a SIB indicative of the RMSI.

In a fourteenth aspect, alone or in combination with the thirteenth aspect, the process 500 includes obtaining a PTRS repetition configuration indicating at least one parameter associated with a plurality of repetitions of transmitting PTRS.

In a fifteenth aspect, alone or in combination with the fourteenth aspect, the at least one parameter is indicative of at least one of a transmission time or a repetition frequency density.

In a sixteenth aspect, alone or in combination with one or more of the fourteenth to fifteenth aspects, obtaining the PTRS repetition configuration includes receiving system information indicating the PTRS repetition configuration.

In a seventeenth aspect, alone or in combination with one or more of the fourteenth to sixteenth aspects, the PTRS repetition configuration is indicated by a wireless communication standard.

In an eighteenth aspect, alone or in combination with one or more of the fourteenth to seventeenth aspects, the at least one parameter associated with transmitting the multiple repetitions of PTRS is based at least in part on the at least one parameter associated with transmission of the RRC connection request message.

In a nineteenth aspect, alone or in combination with the eighteenth aspect, the at least one parameter associated with transmission of the RRC connection request message indicates at least one of a number of repetitions of the RRC connection request message, a modulation and coding scheme, or a bandwidth.

While fig. 5 shows example blocks of the process 500, in some aspects, the process 500 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than depicted in fig. 5. Additionally or alternatively, two or more blocks of process 500 may be performed in parallel.

Fig. 6 is a diagram illustrating an example process 600 performed, for example, by a network node, in accordance with the present disclosure. The example process 600 is an example in which a network node (e.g., the network node 402) performs operations associated with phase tracking reference signal transmission in a radio resource control connection request message.

As shown in fig. 6, in some aspects, process 600 may include: a PTRS indication indicating the presence of PTRS is transmitted to the UE prior to transmission of the RRC connection request message (block 610). For example, the network node (e.g., using transmission component 804 depicted in fig. 8) may transmit a PTRS indication indicating the existence of PTRS to the UE prior to transmission of the RRC connection request message, as described above.

As further shown in fig. 6, in some aspects, process 600 may include receiving an RRC connection request message including a PTRS based at least in part on the PTRS indication (block 620). For example, the network node (e.g., using the receiving component 802 depicted in fig. 8) may receive an RRC connection request message including a PTRS based at least in part on the PTRS indication, as described above.

Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in conjunction with one or more other processes described elsewhere herein.

In a first aspect, transmitting the PTRS indication includes transmitting a RAR including the PTRS indication.

In a second aspect, alone or in combination with the first aspect, the PTRS indication is based at least in part on an interpretation of a bit field of the RAR.

In a third aspect, alone or in combination with one or more of the first and second aspects, transmitting the PTRS indication comprises transmitting a PDCCH transmission comprising the PTRS indication, wherein the PDCCH transmission schedules a random access response.

In a fourth aspect, alone or in combination with the third aspect, the PTRS indication is based at least in part on an interpretation of a bit field of a DCI transmission corresponding to the PDCCH.

In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, transmitting the PTRS indication comprises transmitting a PDCCH transmission comprising the PTRS indication, wherein the PDCCH schedules retransmission of RRC connection request messages.

In a sixth aspect, alone or in combination with the fifth aspect, the PTRS indication is based at least in part on an interpretation of a bit field of a downlink control information transmission corresponding to the PDCCH.

In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, transmitting the PTRS indication comprises transmitting an indication of RRC connection request message repetition.

In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, transmitting the PTRS indication comprises transmitting an indication of a number of repetitions of the RRC connection request message.

In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the PTRS indication is based at least in part on a determination that an indication condition is met.

In a tenth aspect, alone or in combination with the ninth aspect, the determination that the indication condition is met is based at least in part on a determination that a pair of consecutive RRC connection request messages repeatedly includes a first repetition associated with a first uplink time slot and a second repetition associated with a second uplink time slot, wherein at least one third uplink time slot is arranged between the first uplink time slot and the second uplink time slot.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, process 600 includes transmitting a PTRS indication configuration that indicates one or more rules for implicitly indicating the presence of PTRS.

In a twelfth aspect, alone or in combination with the eleventh aspect, transmitting the PTRS indication configuration includes transmitting RMSI.

In a thirteenth aspect, alone or in combination with the twelfth aspect, transmitting the RMSI includes transmitting a SIB indicating the RMSI.

In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the PTRS repetition configuration indicates at least one parameter associated with transmitting multiple repetitions of PTRS.

In a fifteenth aspect, alone or in combination with the fourteenth aspect, the at least one parameter is indicative of at least one of a transmission time or a repetition frequency density.

In a sixteenth aspect, alone or in combination with one or more of the fourteenth to fifteenth aspects, the process 600 includes transmitting system information indicating a PTRS repetition configuration.

In a seventeenth aspect, alone or in combination with one or more of the fourteenth to sixteenth aspects, the PTRS repetition configuration is indicated by a wireless communication standard.

In an eighteenth aspect, alone or in combination with one or more of the fourteenth to seventeenth aspects, the at least one parameter associated with transmitting the multiple repetitions of PTRS is based at least in part on the at least one parameter associated with transmission of the RRC connection request message.

In a nineteenth aspect, alone or in combination with the eighteenth aspect, the at least one parameter associated with transmission of the RRC connection request message indicates at least one of a number of repetitions of the RRC connection request message, a modulation and coding scheme, or a bandwidth.

While fig. 6 shows example blocks of the process 600, in some aspects, the process 600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than depicted in fig. 6. Additionally or alternatively, two or more blocks of process 600 may be performed in parallel.

Fig. 7 is a block diagram of an example apparatus 700 for wireless communication. The apparatus 700 may be a UE, or the UE may include the apparatus 700. In some aspects, the apparatus 700 includes a receiving component 702 and a transmitting component 704 that can be in communication with each other (e.g., via one or more buses and/or one or more other components). As shown, apparatus 700 may use a receiving component 702 and a transmitting component 704 to communicate with another apparatus 706 (such as a UE, a network node, or another wireless communication device). As further shown, the apparatus 700 may include a communication manager 708. The communication manager 708 can include a determination component 710.

In some aspects, the apparatus 700 may be configured to perform one or more operations described herein in connection with fig. 4. Additionally or alternatively, the apparatus 700 may be configured to perform one or more processes described herein, such as the process 500 of fig. 5. In some aspects, the apparatus 700 and/or one or more components shown in fig. 7 may include one or more components of the UE described above in connection with fig. 2. Additionally or alternatively, one or more components shown in fig. 7 may be implemented within one or more components described above in connection with fig. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in 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 functions or operations of the component.

The receiving component 702 can receive a communication (such as a reference signal, control information, data communication, or a combination thereof) from the device 706. The receiving component 702 can provide the received communication to one or more other components of the apparatus 700. In some aspects, the receiving component 702 can perform signal processing (such as filtering, amplifying, demodulating, analog-to-digital converting, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation or decoding, etc.) on the received communication and can provide the processed signal to one or more other components of the apparatus 700. In some aspects, the receiving component 702 may include one or more antennas, demodulators, MIMO detectors, receive processors, controllers/processors, memories, or a combination thereof for the UE described above in connection with fig. 2.

The transmission component 704 can communicate a communication (such as a reference signal, control information, data communication, or a combination thereof) to the device 706. In some aspects, one or more other components of apparatus 700 may generate a communication and may provide the generated communication to transmission component 704 for transmission to apparatus 706. In some aspects, the transmission component 704 can perform signal processing (such as filtering, amplifying, modulating, digital-to-analog converting, multiplexing, interleaving, mapping, encoding, etc.) on the generated communication and can transmit the processed signal to the device 706. In some aspects, the transmission component 704 may include one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers/processors, memories, or combinations thereof of the UE described above in connection with fig. 2. In some aspects, the transmitting component 704 can be co-located with the receiving component 702 in a transceiver.

The receiving component 702 may receive a PTRS indication indicating the presence of PTRS from the network node prior to transmission of the RRC connection request message. The transmission component 704 can transmit an RRC connection request message including the PTRS based at least in part on the PTRS indication. The receiving component 702 may receive a PTRS indication configuration that indicates one or more rules for implicitly indicating the presence of PTRS.

Communication manager 708 may obtain a PTRS repetition configuration that indicates at least one parameter associated with transmitting multiple repetitions of PTRS. The communication manager 708 can also facilitate any other communication actions performed using the receiving component 702 and/or the transmitting component 704. In some aspects, the communication manager 708 may include one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers/processors, memories, or combinations thereof of the UEs described above in connection with fig. 2. In some aspects, the communication manager 708 can include a determination component 710, a reception component 702, and/or a transmission component 704.

Determination component 710 can determine PTRS repetition configuration and/or satisfaction of indication conditions, and the like. In some aspects, the determining component 710 may include one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers/processors, memories, or combinations thereof of the UE described above in connection with fig. 2. In some aspects, the determining component 710 may include the receiving component 702 and/or the transmitting component 704.

The number and arrangement of components shown in fig. 7 are provided as examples. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in fig. 7. Further, two or more components shown in fig. 7 may be implemented within a single component, or a single component shown in fig. 7 may be implemented as multiple distributed components. Additionally or alternatively, a set of components (e.g., one or more components) shown in fig. 7 may perform one or more functions described as being performed by another set of components shown in fig. 7.

Fig. 8 is a block diagram of an example apparatus 800 for wireless communication. The apparatus 800 may be a network node or the network node may comprise the apparatus 800. In some aspects, apparatus 800 includes a receiving component 802 and a transmitting component 804 that can be in communication with each other (e.g., via one or more buses and/or one or more other components). As shown, apparatus 800 can employ a receiving component 802 and a transmitting component 804 to communicate with another apparatus 806 (such as a UE, a network node, or another wireless communication device). As further shown, the apparatus 800 can include a communication manager 808. The communication manager 808 may include a determining component 810.

In some aspects, the apparatus 800 may be configured to perform one or more operations described herein in connection with fig. 4. Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as process 600 of fig. 6. In some aspects, apparatus 800 and/or one or more components shown in fig. 8 may comprise one or more components of a base station described above in connection with fig. 2. Additionally or alternatively, one or more components shown in fig. 8 may be implemented within one or more components described above in connection with fig. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in 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 functions or operations of the component.

The receiving component 802 can receive a communication (such as a reference signal, control information, data communication, or a combination thereof) from a device 806. The receiving component 802 can provide the received communication to one or more other components of the apparatus 800. In some aspects, the receiving component 802 can perform signal processing (such as filtering, amplifying, demodulating, analog-to-digital converting, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation or decoding, etc.) on the received communication and can provide the processed signal to one or more other components of the apparatus 800. In some aspects, the receive component 802 can include one or more antennas, demodulators, MIMO detectors, receive processors, controllers/processors, memory, or a combination thereof for a base station as described above in connection with fig. 2.

The transmission component 804 can transmit communications (such as reference signals, control information, data communications, or a combination thereof) to the device 806. In some aspects, one or more other components of the apparatus 800 may generate a communication and may provide the generated communication to the transmission component 804 for transmission to the apparatus 806. In some aspects, the transmission component 804 can perform signal processing (such as filtering, amplifying, modulating, digital-to-analog converting, multiplexing, interleaving, mapping, encoding, etc.) on the generated communications and can transmit the processed signals to the device 806. In some aspects, the transmission component 804 can include one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers/processors, memories, or combinations thereof of the base station described above in connection with fig. 2. In some aspects, the transmitting component 804 may be co-located with the receiving component 802 in a transceiver.

The transmission component 804 may transmit a PTRS indication indicating the presence of PTRS to the UE prior to transmission of the RRC connection request message. The receiving component 802 can receive an RRC connection request message including a PTRS based at least in part on the PTRS indication. The transmission component 804 may transmit a PTRS indication configuration that indicates one or more rules for implicitly indicating the presence of PTRS. The transmission component 804 may transmit system information indicating PTRS repetition configuration.

The determining component 810 can determine resources and/or parameters associated with one or more configurations (e.g., PTRS indication configuration) and/or resource allocations, and/or the like. In some aspects, the determining component 810 may include one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers/processors, memories, or combinations thereof of the base station described above in connection with fig. 2. In some aspects, the determining component 810 can include the receiving component 802 and/or the transmitting component 804.

The communication manager 808 can generate one or more configurations (e.g., PTRS indication configuration) and/or resource allocations, etc. In some aspects, the communication manager 808 may include one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers/processors, memories, or combinations thereof of the base station described above in connection with fig. 2. In some aspects, the communication manager 808 can include a determining component 810, a receiving component 802, and/or a transmitting component 804.

The number and arrangement of components shown in fig. 8 are provided as examples. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in fig. 8. Further, two or more components shown in fig. 8 may be implemented within a single component, or a single component shown in fig. 8 may be implemented as multiple distributed components. Additionally or alternatively, a set of components (e.g., one or more components) shown in fig. 8 may perform one or more functions described as being performed by another set of components shown in fig. 8.

The following provides an overview of some aspects of the disclosure:

aspect 1: a method of wireless communication performed by a User Equipment (UE), comprising: receiving a Phase Tracking Reference Signal (PTRS) indication from a network node prior to transmission of a Radio Resource Control (RRC) connection request message, the PTRS indication being for indicating presence of PTRS; and transmitting an RRC connection request message including the PTRS based at least in part on the PTRS indication.

Aspect 2: the method of aspect 1, wherein receiving the PTRS indication comprises receiving a Random Access Response (RAR) comprising the PTRS indication.

Aspect 3: the method of aspect 2, wherein receiving the PTRS indication comprises interpreting a bit field of the RAR to identify the PTRS indication.

Aspect 4: the method of any of aspects 1-3, wherein receiving the PTRS indication comprises receiving a Physical Downlink Control Channel (PDCCH) transmission comprising the PTRS indication, wherein the PDCCH transmission schedules a random access response.

Aspect 5: the method of aspect 4, wherein receiving the PTRS indication comprises interpreting a bit field of a downlink control information transmission corresponding to the PDCCH to identify the PTRS indication.

Aspect 6: the method of any of aspects 1-5, wherein receiving the PTRS indication comprises receiving a Physical Downlink Control Channel (PDCCH) comprising the PTRS indication, wherein the PDCCH schedules retransmission of RRC connection request messages.

Aspect 7: the method of aspect 6, wherein receiving the PTRS indication comprises interpreting a bit field of a downlink control information transmission corresponding to the PDCCH to identify the PTRS indication.

Aspect 8: the method of any of aspects 1-7, wherein receiving the PTRS indication comprises receiving an indication of RRC connection request message repetition.

Aspect 9: the method of any of aspects 1-8, wherein receiving the PTRS indication comprises receiving an indication of a number of repetitions of an RRC connection request message.

Aspect 10: the method of any of aspects 1-9, wherein receiving the PTRS indication comprises determining that an indication condition is met.

Aspect 11: the method of aspect 10, wherein determining that the indication condition is met comprises determining that a pair of consecutive RRC connection request message repetitions includes a first repetition associated with a first uplink time slot and a second repetition associated with a second uplink time slot, wherein at least one third uplink time slot is disposed between the first uplink time slot and the second uplink time slot.

Aspect 12: the method of any of aspects 1-11, further comprising receiving a PTRS indication configuration indicating one or more rules for implicitly indicating the presence of PTRS.

Aspect 13: the method of aspect 12, wherein receiving the PTRS indication configuration comprises receiving Remaining Minimum System Information (RMSI).

Aspect 14: the method of aspect 13, wherein receiving the RMSI includes receiving a System Information Block (SIB) indicating the RMSI.

Aspect 15: the method of any of aspects 1-14, further comprising obtaining a PTRS repetition configuration indicating at least one parameter associated with transmitting a plurality of repetitions of PTRS.

Aspect 16: the method of aspect 15, wherein the at least one parameter is indicative of at least one of a transmission time or a repetition frequency density.

Aspect 17: the method of any of aspects 15 or 16, wherein obtaining the PTRS repetition configuration comprises receiving system information indicating the PTRS repetition configuration.

Aspect 18: the method of any of aspects 15-17, wherein the PTRS repetition configuration is indicated by a wireless communication standard.

Aspect 19: the method of any of aspects 15-18, wherein at least one parameter associated with transmitting multiple repetitions of PTRS is based at least in part on at least one parameter associated with transmission of an RRC connection request message.

Aspect 20: the method of aspect 19, wherein the at least one parameter associated with transmission of the RRC connection request message indicates at least one of: the number of repetitions of the RRC connection request message, the modulation and coding scheme, or the bandwidth.

Aspect 21: a method of wireless communication performed by a network node, comprising: transmitting a Phase Tracking Reference Signal (PTRS) indication to a User Equipment (UE) prior to transmission of a Radio Resource Control (RRC) connection request message, the PTRS indication to indicate presence of PTRS; and receiving an RRC connection request message including the PTRS based at least in part on the PTRS indication.

Aspect 22: the method of aspect 21, wherein transmitting the PTRS indication comprises transmitting a Random Access Response (RAR) including the PTRS indication.

Aspect 23: the method of aspect 22, wherein the PTRS indication is based at least in part on an interpretation of a bit field of the RAR.

Aspect 24: the method of any of aspects 21-23, wherein transmitting the PTRS indication comprises transmitting a Physical Downlink Control Channel (PDCCH) transmission comprising the PTRS indication, wherein the PDCCH transmission schedules a random access response.

Aspect 25: the method of aspect 24, wherein the PTRS indication is based at least in part on an interpretation of a bit field of a downlink control information transmission corresponding to the PDCCH.

Aspect 26: the method of any of aspects 21-25, wherein transmitting the PTRS indication comprises transmitting a Physical Downlink Control Channel (PDCCH) comprising the PTRS indication, wherein the PDCCH schedules retransmission of RRC connection request messages.

Aspect 27: the method of aspect 26, wherein the PTRS indication is based at least in part on an interpretation of a bit field of a downlink control information transmission corresponding to the PDCCH.

Aspect 28: the method of any of aspects 21-27, wherein transmitting the PTRS indication comprises transmitting an indication of RRC connection request message repetition.

Aspect 29: the method of any of aspects 21-28, wherein transmitting the PTRS indication comprises transmitting an indication of a number of repetitions of the RRC connection request message.

Aspect 30: the method of any of aspects 21-29, wherein the PTRS indication is based at least in part on a determination that an indication condition is met.

Aspect 31: the method of aspect 30, wherein the determination that the indication condition is met is based at least in part on a determination that a pair of consecutive RRC connection request messages repeatedly includes a first repetition associated with a first uplink time slot and a second repetition associated with a second uplink time slot, wherein at least one third uplink time slot is disposed between the first uplink time slot and the second uplink time slot.

Aspect 32: the method of any of aspects 21-31, further comprising transmitting a PTRS indication configuration indicating one or more rules for implicitly indicating the presence of PTRS.

Aspect 33: the method of aspect 32, wherein transmitting the PTRS indication configuration comprises transmitting Remaining Minimum System Information (RMSI).

Aspect 34: the method of aspect 33, wherein transmitting the RMSI includes transmitting a System Information Block (SIB) indicating the RMSI.

Aspect 35: the method of any of aspects 21-34, wherein the PTRS repetition configuration indicates at least one parameter associated with transmitting multiple repetitions of PTRS.

Aspect 36: the method of aspect 35, wherein the at least one parameter is indicative of at least one of a transmission time or a repetition frequency density.

Aspect 37: the method of any one of aspects 35 or 36, further comprising: system information indicating PTRS repetition configuration is transmitted.

Aspect 38: the method of any of aspects 35-37, wherein the PTRS repetition configuration is indicated by a wireless communication standard.

Aspect 39: the method of any of aspects 35-38, wherein at least one parameter associated with transmitting multiple repetitions of PTRS is based at least in part on at least one parameter associated with transmission of an RRC connection request message.

Aspect 40: the method of aspect 39, wherein the at least one parameter associated with transmission of the RRC connection request message indicates at least one of: the number of repetitions of the RRC connection request message, the modulation and coding scheme, or the bandwidth.

Aspect 41: 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 as one or more of aspects 1-20.

Aspect 42: an apparatus for wireless communication, comprising a memory; and one or more processors coupled to the memory, the memory and the one or more processors configured to perform the method as in one or more of aspects 1-20.

Aspect 43: an apparatus for wireless communication, comprising at least one means for performing the method of one or more of aspects 1-20.

Aspect 44: a non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform a method as one or more of aspects 1-20.

Aspect 45: a non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method as in one or more of aspects 1-20.

Aspect 46: 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 a method as in one or more of aspects 21-40.

Aspect 47: an apparatus for wireless communication, comprising a memory; and one or more processors coupled to the memory, the memory and the one or more processors configured to perform the method as in one or more of aspects 21-40.

Aspect 48: an apparatus for wireless communication, comprising at least one means for performing a method as one or more of aspects 21-40.

Aspect 49: a non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform a method as one or more of aspects 21-40.

Aspect 50: a non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method as in one or more of aspects 21-40.

The foregoing disclosure provides insight and description, but is not intended to be exhaustive or to limit aspects to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the various aspects.

As used herein, the term "component" is intended to be broadly interpreted as hardware and/or a combination of hardware and software. "software" should be construed broadly to mean instructions, instruction sets, code segments, program code, programs, subroutines, software modules, applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and/or functions, etc., whether described in software, firmware, middleware, microcode, hardware description language, or other terminology. As used herein, a processor is implemented in hardware, and/or a combination of hardware and software. It will be apparent that the systems and/or methods described herein may be implemented in different forms of hardware, and/or combinations of hardware and software. The actual specialized control hardware or software code used to implement the systems and/or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and/or methods were described herein without reference to the specific software code-it being understood that software and hardware can be designed to implement the systems and/or methods based at least in part on the description herein.

As used herein, satisfying a threshold may refer to a value greater than a threshold, greater than or equal to a threshold, less than or equal to a threshold, not equal to a threshold, etc., depending on the context.

Although specific combinations of features are recited in the claims and/or disclosed in the specification, such combinations are not intended to limit the disclosure of the various aspects. Indeed, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each of the dependent claims listed below may depend directly on only one claim, disclosure of various aspects includes each dependent claim in combination with each other claim of the set of claims. As used herein, a phrase referring to a list of items "at least one of" refers to any combination of these items, including individual members. As an example, "at least one of a, b, or c" is intended to encompass: a. b, c, a-b, a-c, b-c, and a-b-c, as well as any combination having multiple identical elements (e.g., a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b-b, b-b-c, c-c, and c-c-c, or any other ordering of a, b, and c).

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Moreover, as used herein, the articles "a" and "an" 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 conjunction with the article "the" and may be used interchangeably with "one or more". Furthermore, as used herein, the terms "set (collection)" and "group" are intended to include one or more items (e.g., related items, non-related items, or a combination of related and non-related items), and may be used interchangeably with "one or more. Where only one item is intended, the phrase "only one" or similar language is used. Also, as used herein, the terms "having," "containing," "including," and the like are intended to be open ended terms. Furthermore, the phrase "based on" is intended to mean "based, at least in part, on" unless explicitly stated otherwise. Also, as used herein, the term "or" when used in a sequence is intended to be inclusive and may be used interchangeably with "and/or" unless otherwise specifically stated (e.g., where used in conjunction with "any one of" or "only one of").

Claims (30)

1. A method of wireless communication performed by a User Equipment (UE), comprising:

receiving a Phase Tracking Reference Signal (PTRS) indication from a network node prior to transmission of a Radio Resource Control (RRC) connection request message, the PTRS indication being for indicating presence of PTRS; and

the RRC connection request message including the PTRS is transmitted based at least in part on the PTRS indication.

2. The method of claim 1, wherein receiving the PTRS indication comprises receiving a Random Access Response (RAR) comprising the PTRS indication.

3. The method of claim 2, wherein receiving the PTRS indication comprises interpreting a bit field of the RAR to identify the PTRS indication.

4. The method of claim 1, wherein receiving the PTRS indication comprises receiving a Physical Downlink Control Channel (PDCCH) transmission comprising the PTRS indication, wherein the PDCCH transmission schedules a random access response.

5. The method of claim 4, wherein receiving the PTRS indication comprises interpreting a bit field of a downlink control information transmission corresponding to the PDCCH to identify the PTRS indication.

6. The method of claim 1, wherein receiving the PTRS indication comprises receiving a Physical Downlink Control Channel (PDCCH) comprising the PTRS indication, wherein the PDCCH schedules retransmission of the RRC connection request message.

7. The method of claim 6, wherein receiving the PTRS indication comprises interpreting a bit field of a downlink control information transmission corresponding to the PDCCH to identify the PTRS indication.

8. The method of claim 1, wherein receiving the PTRS indication comprises receiving an indication of RRC connection request message repetition.

9. The method of claim 1, wherein receiving the PTRS indication comprises receiving an indication of a number of repetitions of the RRC connection request message.

10. The method of claim 1, wherein receiving the PTRS indication comprises determining that an indication condition is met.

11. The method of claim 10, wherein determining that the indication condition is met comprises determining that a pair of consecutive RRC connection request message repetitions includes a first repetition associated with a first uplink time slot and a second repetition associated with a second uplink time slot, wherein at least one third uplink time slot is disposed between the first uplink time slot and the second uplink time slot.

12. The method of claim 1, further comprising: a PTRS indication configuration is received that indicates one or more rules for implicitly indicating the presence of the PTRS.

13. The method of claim 12, wherein receiving the PTRS indication configuration comprises receiving Remaining Minimum System Information (RMSI).

14. The method of claim 13, wherein receiving the RMSI comprises receiving a System Information Block (SIB) indicating the RMSI.

15. The method of claim 1, further comprising: a PTRS repetition configuration is obtained that indicates at least one parameter associated with transmitting multiple repetitions of the PTRS.

16. The method of claim 15, wherein the at least one parameter indicates at least one of a transmission time or a repetition frequency density.

17. The method of claim 15, wherein obtaining the PTRS repetition configuration comprises receiving system information indicating the PTRS repetition configuration.

18. The method of claim 15, wherein the PTRS repetition configuration is indicated by a wireless communication standard.

19. The method of claim 15, wherein the at least one parameter associated with transmitting the plurality of repetitions of the PTRS is based at least in part on at least one parameter associated with transmission of the RRC connection request message.

20. The method of claim 19, wherein the at least one parameter associated with transmission of the RRC connection request message indicates at least one of:

The number of repetitions of the RRC connection request message,

modulation and coding scheme, or

Bandwidth.

21. A method of wireless communication performed by a network node, comprising:

transmitting a Phase Tracking Reference Signal (PTRS) indication to a User Equipment (UE) prior to transmission of a Radio Resource Control (RRC) connection request message, the PTRS indication to indicate presence of PTRS; and

the RRC connection request message including the PTRS is received based at least in part on the PTRS indication.

22. The method of claim 21, wherein transmitting the PTRS indication comprises transmitting a Random Access Response (RAR) that includes the PTRS indication, and wherein the PTRS indication is based at least in part on an interpretation of a bit field of the RAR.

23. The method of claim 21, wherein transmitting the PTRS indication comprises transmitting a Physical Downlink Control Channel (PDCCH) transmission comprising the PTRS indication, wherein the PDCCH transmission schedules a random access response, and wherein the PTRS indication is based at least in part on an interpretation of a bit field of a downlink control information transmission corresponding to the PDCCH.

24. The method of claim 21, wherein transmitting the PTRS indication comprises transmitting a Physical Downlink Control Channel (PDCCH) comprising the PTRS indication, wherein the PDCCH schedules retransmission of the RRC connection request message, and wherein the PTRS indication is based at least in part on an interpretation of a bit field of a downlink control information transmission corresponding to the PDCCH.

25. The method of claim 21, wherein transmitting the PTRS indication comprises transmitting an indication of RRC connection request message repetition.

26. The method of claim 21, wherein transmitting the PTRS indication comprises transmitting an indication of a number of repetitions of the RRC connection request message.

27. The method of claim 21, wherein the PTRS indication is based at least in part on a determination that an indication condition is met, wherein the determination that the indication condition is met is based at least in part on a determination that a pair of consecutive RRC connection request message repetitions includes a first repetition associated with a first uplink time slot and a second repetition associated with a second uplink time slot, and wherein at least one third uplink time slot is disposed between the first uplink time slot and the second uplink time slot.

28. The method of claim 21, wherein a PTRS repetition configuration indicates at least one parameter associated with transmitting a plurality of repetitions of the PTRS, and wherein the at least one parameter indicates at least one of a transmission time or a repetition frequency density.

29. A User Equipment (UE) for wireless communication, comprising:

A memory; and

one or more processors coupled to the memory, the one or more processors configured to:

receiving a Phase Tracking Reference Signal (PTRS) indication from a network node prior to transmission of a Radio Resource Control (RRC) connection request message, the PTRS indication being for indicating presence of PTRS; and

the RRC connection request message including the PTRS is transmitted based at least in part on the PTRS indication.

30. A network node for wireless communication, comprising:

a memory; and

one or more processors coupled to the memory, the one or more processors configured to:

transmitting a Phase Tracking Reference Signal (PTRS) indication to a User Equipment (UE) prior to transmission of a Radio Resource Control (RRC) connection request message, the PTRS indication to indicate presence of PTRS; and

the RRC connection request message including the PTRS is received based at least in part on the PTRS indication.