Demodulation reference signal configuration for uplink messages

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive control signaling indicating a demodulation reference signal (DMRS) configuration for an uplink message, the control signaling may instruct the UE to avoid including a DMRS in at least a first portion of the uplink message based on the DMRS configuration. The UE may encode the uplink message that does not have the DMRS in at least the first portion of the uplink message according to the DMRS configuration. The UE may transmit the uplink message based on encoding the uplink message, and a network entity may receive and decode the uplink message. In some examples, the network entity may receive signaling including a set of uplink messages from different UEs. In this way, the network entity may decode each uplink message using a respective Reed-Muller (RM) code according to a multi-user decoding algorithm.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application No. 17 / 844,554, entitled “DEMODULATION REFERENCE SIGNAL CONFIGURATION FOR UPLINK MESSAGES,” filed by Sen et al. on June 20, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including demodulation reference signal (DMRS) configuration for uplink messages. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0005] The described technology relates to improved methods, systems, devices and apparatuses that support demodulation reference signal (DMRS) configuration for uplink messages. For example, the described technology provides that network entities and user equipment (UE) reduce DMRS port leakage by operating according to the technology for DMRS configuration relative to uplink messages. In some specific implementations, the network entity may configure the UE to perform non-coherent physical uplink shared channel (PUSCH) transmission using Reed-Muller (RM) decoding technology. In this way, the UE can encode the signal according to the configured RM code and send the encoded signal to the network entity. On the decoding side at the network, the network entity can use non-coherent decoding for one or more encoded signals from multiple UEs according to a multi-user decoding algorithm.

[0006] Additionally or alternatively, the network entity may use the associated physical random access channel (PRACH) portion of the uplink message to perform channel estimation for the PUSCH. For example, the network entity may configure the UE to use a full DMRS, a partial DMRS, or no DMRS, such as when sending a first message (e.g., Msg-A) in a PRACH process. In an example where the UE is configured not to send DMRS, the network entity may perform channel estimation based on the PRACH preamble and extrapolate channel coefficients for resource elements to be used for the associated PUSCH. In some examples, the network entity may configure the UE to apply a comb structure when sending the PRACH preamble. In some examples, the network entity may configure the UE to send a partial DMRS in a frequency range not covered by the PRACH. In some examples, the network entity may configure the UE to send a full DMRS at the end of a timeslot and in a symbol after the transmission of the PUSCH.

[0007] A method for wireless communication at a UE is described. The method may include: receiving control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates to the UE based on the DMRS configuration to avoid including DMRS in at least a first portion of the uplink message; encoding the uplink message without the DMRS in at least the first portion of the uplink message according to the DMRS configuration; and sending the uplink message based on encoding the uplink message.

[0008] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: receive control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates to the UE based on the DMRS configuration to avoid including DMRS in at least a first portion of the uplink message; encode the uplink message without the DMRS in at least the first portion of the uplink message according to the DMRS configuration; and send the uplink message based on encoding the uplink message.

[0009] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates to the UE based on the DMRS configuration to avoid including DMRS in at least a first portion of the uplink message; means for encoding the uplink message without the DMRS in at least the first portion of the uplink message according to the DMRS configuration; and means for sending the uplink message based on encoding the uplink message.

[0010] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates to the UE based on the DMRS configuration to avoid including DMRS in at least a first portion of the uplink message; encode the uplink message without the DMRS in at least the first portion of the uplink message according to the DMRS configuration; and send the uplink message based on encoding the uplink message.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, encoding the uplink message may include operations, features, components, or instructions for encoding the uplink message that does not include the DMRSs in the first part using an RM code according to the DMRS configuration.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the DMRS configuration includes a field indicating that the UE may want to avoid including the DMRSs in the first part of the uplink message.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the DMRS configuration includes a field indicating a low-density parity-check code and an RM code used by the UE to encode the uplink message, and the field may be included in an uplink channel resource information element.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for selecting a PRACH preamble to include in the uplink message, and generating the scrambling identifier based on the PRACH preamble, or based on radio resource control signaling (RRC) indicating a scrambling identifier associated with the UE, or both, wherein encoding the uplink message may be based on the scrambling identifier.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the DMRS configuration may include operations, features, components, or instructions for receiving an indication of whether the UE may include these DMRSs in a second part of the uplink message over a frequency bandwidth that may be covered by a random access channel of the uplink message, wherein the random access channel may be included in the first part of the uplink message.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the indication may include operations, features, components, or instructions for the following actions: receiving a first configuration indicating that the UE includes one or more demodulation reference signals in each frequency resource of the frequency bandwidth covered by the random access channel; receiving a second configuration indicating that the UE includes the one or more demodulation reference signals in a subset of the frequency resources of the frequency bandwidth covered by the random access channel; and receiving a third configuration indicating that the UE avoids including the demodulation reference signal in the second part of the uplink message.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the DMRS configuration may include operations, features, components, or instructions for receiving an indication of a PRACH comb pattern to be applied to the first portion of the uplink message.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, encoding the uplink message may include operations, features, components, or instructions for encoding the uplink message without the DMRSs in any portion of the uplink message according to the DMRS configuration.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, encoding the uplink message may include operations, features, components, or instructions for encoding the first portion of the uplink message according to a PRACH comb pattern based on the DMRS configuration.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, encoding the uplink message may include operations, features, components, or instructions for encoding the uplink message to include one or more DMRSs in a second portion of the uplink message according to the DMRS configuration.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, encoding the uplink message may include operations, features, components, or instructions for encoding the second portion of the uplink message to include the one or more DMRSs at the beginning or end of the second portion based on the DMRS configuration.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, encoding the uplink message may include operations, features, components, or instructions for encoding the second portion of the uplink message to include the one or more DMRSs in a set of frequency resources without a random access channel signal according to the DMRS configuration.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, encoding the uplink message may include operations, features, components, or instructions for encoding the second portion of the uplink message based on the DMRS configuration to include the one or more DMRSs in a frequency resource set that includes a random access channel signal in the first portion.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the DMRS configuration may be based on an amount of Doppler spread at the UE.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the uplink message may include operations, features, components, or instructions for the following actions: sending PRACH in a first set of frequency resources in the first part of the uplink message according to the DMRS configuration; and sending an uplink shared channel in a second set of frequency resources in the second part of the uplink message according to the DMRS configuration, wherein the first set of frequency resources and the second set of frequency resources include the same set of frequency resources or a subset of the same frequency resources.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the DMRS configuration may include the second set of frequency resources based on the first set of frequency resources.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the DMRS configuration may include the first set of frequency resources based on the second set of frequency resources.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control signaling may include operations, features, components, or instructions for receiving an RRC message including the DMRS configuration for the uplink message.

[0029] A method of wireless communication at a network entity is described. The method may include: sending control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates to a UE based on the DMRS configuration to avoid including DMRS in at least a first portion of the uplink message; receiving the uplink message without the DMRS in at least the first portion of the uplink message according to the DMRS configuration; and decoding the uplink message based on the DMRS configuration.

[0030] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: send control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates to a UE based on the DMRS configuration to avoid including DMRS in at least a first portion of the uplink message; receive the uplink message without the DMRS in at least the first portion of the uplink message according to the DMRS configuration; and decode the uplink message based on the DMRS configuration.

[0031] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for sending control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates to a UE based on the DMRS configuration to avoid including DMRS in at least a first portion of the uplink message; means for receiving the uplink message without the DMRS in at least the first portion of the uplink message according to the DMRS configuration; and means for decoding the uplink message based on the DMRS configuration.

[0032] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to: send control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates to a UE based on the DMRS configuration to avoid including DMRS in at least a first portion of the uplink message; receive the uplink message without the DMRS in at least the first portion of the uplink message according to the DMRS configuration; and decode the uplink message based on the DMRS configuration.

[0033] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a signal including a set of uplink messages from different UEs, wherein each uplink message in the set of uplink messages may be associated with an RM code.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, decoding the uplink message may include operations, features, components, or instructions for: decoding the uplink message using a corresponding RM code according to the DMRS configuration, wherein the uplink message may not include these DMRSs in the first part of the uplink message; and eliminating the decoded uplink message from the signal including the uplink message set according to a multi-user decoding algorithm.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the DMRS configuration includes a field indicating a low-density parity-check code and an RM code used by the UE to encode the uplink message, and the field may be included in an uplink channel resource information element. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 An example of a wireless communication system supporting a demodulation reference signal (DMRS) configuration for uplink messages according to one or more aspects of the present disclosure is illustrated.

[0037] Figure 2 An example of a wireless communication system supporting DMRS configuration for uplink messages according to one or more aspects of the present disclosure is illustrated.

[0038] Figure 3 An example of a multi-user decoding algorithm supporting DMRS configuration for uplink messages according to one or more aspects of the present disclosure is illustrated.

[0039] Figures 4 to 8 An example of uplink message configuration supporting DMRS configuration for uplink messages according to one or more aspects of the present disclosure is illustrated.

[0040] Fig. 9 An example of a process flow to support DMRS configuration for uplink messages in accordance with one or more aspects of the present disclosure is illustrated.

[0041] Fig.10 and Fig.11 A block diagram of a device supporting DMRS configuration for uplink messages according to one or more aspects of the present disclosure is shown.

[0042] Fig.12A block diagram of a communications manager supporting DMRS configuration for uplink messages is shown in accordance with one or more aspects of the present disclosure.

[0043] Fig.13 A diagram of a system including a device supporting DMRS configuration for uplink messages in accordance with one or more aspects of the present disclosure is shown.

[0044] Fig.14 and Fig.15 A block diagram of a device supporting DMRS configuration for uplink messages according to one or more aspects of the present disclosure is shown.

[0045] Fig.16 A block diagram of a communications manager supporting DMRS configuration for uplink messages is shown in accordance with one or more aspects of the present disclosure.

[0046] Fig.17 A diagram of a system including a device supporting DMRS configuration for uplink messages in accordance with one or more aspects of the present disclosure is shown.

[0047] Figures 18 to 21 A flow chart illustrating a method of supporting DMRS configuration for uplink messages according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0048] In some examples of wireless communication, one or more wireless devices (e.g., user equipment (UE)) may contend with a network entity for access to a channel. Thus, each of the one or more UEs may operate according to a random access channel (RACH) procedure (e.g., a 2-step or 4-step RACH procedure). For example, a first UE may send a first message (e.g., Msg-A) to a network entity, the first message including a physical RACH (PRACH) preamble for identifying the UE and uplink data sent on a physical uplink shared channel (PUSCH) opportunity. In some examples, the PRACH preamble may be mapped to a set of time and frequency resources and a set of demodulation reference signal (DMRS) ports, wherein the DMRS ports may be used by the network entity for channel estimation of an associated PUSCH. However, in some cases, multiplexing of multiple UEs competing for channel access may result in leakage of DMRS ports, resulting in asynchronous transmission. Thus, it may be advantageous for the network entity to perform channel estimation for the PUSCH with reduced DMRS or without using DMRS.

[0049] The network entity and the UE can reduce DMRS port leakage by operating according to the technology of DMRS configuration for uplink messages as described herein. In some specific implementations, the network entity can configure the UE to use Reed-Muller (RM) decoding technology to perform non-coherent PUSCH transmission. In this way, the UE can generate a coded signal according to the configured RM code and send the coded signal to the network entity. In some cases, the coded signal may not include DMRS. On the decoding side at the network, the network entity can use non-coherent decoding for coded signals from one or more UEs according to a multi-user decoding algorithm, wherein the network entity can decode data based on the RM code and perform channel estimation for each UE. The network entity can repeat the iteration until each UE is correctly decoded or the decoding does not improve.

[0050] Additionally or alternatively, the network entity may use the associated PRACH portion of the PUSCH to perform channel estimation for the PUSCH. In some specific implementations, the network entity may configure the UE with a DMRS configuration, such as relative to the bandwidth spanned by the PRACH. For example, the UE may be configured to use a full DMRS (e.g., a DMRS spanning the full PRACH bandwidth), a partial DMRS (e.g., a DMRS included across a subset of the PRACH bandwidth), or no DMRS (e.g., a DMRS not included in any PRACH bandwidth), such as when sending a first message (e.g., Msg-A) in a PRACH process. In an example where the UE is configured not to send DMRS, the network entity may perform channel estimation based on the PRACH preamble and extrapolate channel coefficients for resource elements to be used for the associated PUSCH. In some examples, the network entity may configure the UE to apply a comb structure when sending the PRACH preamble (without DMRS). In some examples, the network entity may configure the UE to send DMRS in a frequency range not covered by the PRACH. In some examples, the network entity may configure the UE to send DMRS in a symbol after the end of a timeslot and the transmission of PUSCH. Thus, based on this configuration, the network entity may receive an uplink message (e.g., Msg-A) and derive a channel estimate for PUSCH using PRACH or a combination of PRACH and DMRS.

[0051] Various aspects of the present disclosure are first described in the context of a wireless communication system. Various aspects of the present disclosure are further illustrated and described by and with reference to multi-user decoding algorithms and uplink message configurations. Various aspects of the present disclosure are further illustrated and described by and with reference to apparatus diagrams, system diagrams, and flow charts related to DMRS configurations for uplink messages.

[0052] Figure 1An example of a wireless communication system 100 supporting DMRS configuration for uplink messages according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0053] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0054] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be able to communicate with various types of devices such as Figure 1 Other UEs 115 or network entities 105 are shown communicating.

[0055] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0056] In some examples, the network entities 105 may communicate with the core network 130, or communicate with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3 or other interface protocols). In some examples, the network entities 105 may communicate with each other through the backhaul communication link 120 (e.g., according to X2, Xn or other interface protocols) directly (e.g., directly between each network entity 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication link 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication link 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0057] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a home Node B, a home evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0058] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0059] The functional split between CU 160, DU 165, and RU 175 is flexible and may support different functionalities, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 175. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 can be within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 can be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 that communicate over those communication links.

[0060] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0061] In the context of the application of the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support DMRS configuration for uplink messages as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0062] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0063] The UE 115 described herein may be capable of communicating with various types of devices such as other UEs 115 which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0064] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) on one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of a network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0065] The signal waveform transmitted by the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a resource of a subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0066] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0067] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into multiple micro-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0068] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmit time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0069] Physical channels may be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels may be multiplexed on a downlink carrier using, for example, one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0070] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0071] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0072] In some examples, a UE 115 may be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .

[0073] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0074] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0075] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band, such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations in an unlicensed band may be based on a carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating in a licensed band. Operations in an unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0076] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may have an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0077] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0078] The wireless communication system 100 can be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication at the bearer or PDCP layer can be IP-based. The RLC layer can perform packet segmentation and reorganization to communicate through logical channels. The MAC layer can perform priority processing and multiplexing of logical channels into transport channels. The MAC layer can also use error detection technology, error correction technology, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer can provide the establishment, configuration, and maintenance of the RRC connection that supports the radio bearer of user plane data between the UE 115 and the network entity 105 or the core network 130. At the PHY layer, the transport channel can be mapped to the physical channel.

[0079] In some examples of the wireless communication system 100, one or more wireless devices (e.g., UE 115) may contend with the network entity 105 for access to a channel. Thus, each of the one or more UEs 115 may operate according to a RACH procedure. For example, a first UE 115 may send a first message to the network entity 105, the first message including a PRACH preamble for identifying the UE 115 and uplink data sent on a PUSCH opportunity. In some examples, the PRACH preamble may be mapped to a set of time and frequency resources and a set of DMRS ports, where the DMRS ports may be used by the network entity 105 for channel estimation of an associated PUSCH.

[0080] Techniques for performing channel estimation may be improved. For example, the channel estimation techniques described herein may allow a device (e.g., UE 115, network entity 105) to perform channel estimation based on parameters other than DRMS ​​(e.g., RM code, PRACH). In some cases, the techniques described herein may allow channel estimation without DMRS. In some implementations, the network entity 105 may configure the UE 115 to perform non-coherent PUSCH transmission using RM decoding techniques. For example, the UE 115 may generate a coded signal according to the configured RM code and send the coded signal to the network entity 105. On the decoding side at the network, the network entity 105 may use non-coherent decoding for one or more coded signals from multiple UEs 115 according to a multi-user decoding algorithm, wherein the network entity 105 may decode the data based on the RM code associated with the transmission and perform channel estimation for each UE 115. The network entity 105 may repeat the iteration until each UE 115 is correctly decoded or the decoding does not improve.

[0081] Additionally or alternatively, the network entity 105 may use the associated PRACH portion of the PUSCH to perform channel estimation for the PUSCH. For example, the network entity 105 may configure the UE 115 to include a full DMRS, a partial DMRS, or no DMRS in an uplink message (e.g., Msg-A). In an example where the UE 115 is configured not to send a DMRS, the network entity 105 may perform channel estimation based on the PRACH preamble and extrapolate channel coefficients for resource elements to be used for the associated PUSCH. In some examples, the network entity 105 may configure the UE 115 to apply a comb structure (such as reference 1) when sending the PRACH preamble. Figure 5 In some examples, network entity 105 may configure UE 115 to send DMRS in a frequency range not covered by PRACH (see Figure 6 In some examples, network entity 105 may configure UE 115 to transmit DMRS in symbols after the end of a time slot and the transmission of a PUSCH (see reference Figure 8 Thus, based on this configuration, the network entity 105 may receive uplink messages and derive a channel estimate for the PUSCH using the PRACH or a combination of the PRACH and the DMRS.

[0082] Figure 2 An example of a wireless communication system 200 that supports DMRS configuration for uplink messages according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 200 may implement one or more aspects of the wireless communication system 100. For example, the UE 115-a and the network entity 105-a may be reference Figure 1 1 and corresponding examples of a UE 115 and a network entity 105. Although examples are discussed herein, any number of devices and device types may be used to implement the specific implementations described in the present disclosure. The wireless communication system 200 may support control signaling between the UE 115-a and the network entity 105-a, which instructs the UE 115-a to avoid including DMRS in at least a first portion of the uplink message 215 based on receiving the DMRS configuration message 205.

[0083] In some examples of the wireless communication system 200, the UE 115-a may compete with the network entity 105-a for access to the channel. In this way, the UE 115-a may operate according to a RACH process (e.g., a 2-step RACH process, a 4-step RACH, etc.). In the example of a 2-step RACH process, the UE 115-a may send a first message (e.g., Msg-A) of the RACH process to the network entity 105-a, which may include a PRACH preamble for identifying the UE 115-a and uplink data sent on a PUSCH opportunity. In some examples, the UE 115-a may select a PRACH preamble from a set of PRACH preambles configured by the network and send the PRACH preamble during the RACH opportunity. The UE 115-a may randomly select a PRACH preamble, such as from a set of 64 preambles. Additionally or alternatively, the PRACH preamble may be mapped to a set of time and frequency resources and a set of DMRS ports. In some examples, the DMRS port may be used by the network entity 105 - a for channel estimation for the associated PUSCH transmission.

[0084] However, in some cases, the multiplexing of multiple UEs 115 competing for channel access may result in increased complexity of channel estimation at the network entity 105-a. For example, the network may support multiple orthogonal DMRS ports (e.g., 12 orthogonal DMRS ports), where the limited number of DMRS ports may result in a bottleneck as the number of multiplexed UEs 115 increases. In some examples, a bottleneck associated with a DMRS port may result in a DMRS port shift, where the DMRS ports are no longer orthogonal (e.g., leakage between DMRS ports). In some instances, DMRS port leakage may result in asynchronous transmission for each UE 115, which may result in the loss of timing advance (TA) information for each corresponding PUSCH transmission. Additionally or alternatively, the use of DMRS may increase the signaling overhead of the wireless communication system 200. Thus, it may be advantageous for the network entity 105-a to perform channel estimation for PUSCH with reduced DMRS opportunities.

[0085] The network entity 105-a may perform channel estimation without using DMRS or using reduced DMRS according to the techniques described herein. For example, the network entity 105-a may send a DMRS configuration message 205 to the UE 115-a, which may instruct the UE 115-a to encode the uplink message 215 so that at least a first portion (e.g., a time range, a frequency range, or a combination thereof) of the uplink message 215 may not include DMRS. For example, the UE 115-a may configure the channel estimation based on the following example: Figure 2The illustrated uplink message configuration 220 is used to generate the uplink message 215. In such an example, the uplink message configuration 220 may include a set of PRACH resources 225 during a first set of time and frequency resources, a set of PUSCH resources 235 during a second set of time and frequency resources, and a set of blank resources 230 between the PRACH resources 225 and the PUSCH resources 235. In this way, the uplink message configuration 220 can avoid including DMRS resources during at least a first portion of the uplink message 215. Figures 4 to 8 ) describes further examples of various uplink message configurations 220.

[0086] In some implementations, the DMRS configuration message 205 may indicate to the UE 115-a that non-coherent PUSCH transmission is to be performed according to the RM decoding technique to allow the network entity 105-a to perform channel estimation without DMRS or using reduced DMRS opportunities. In such implementations, the DMRS configuration message 205 may include one or more fields that indicate to the UE 115-a to avoid including DMRS in the uplink message 215. For example, the DMRS configuration message 205 may be an example of a control message (e.g., an RRC message, a medium access control-control element (MAC-CE) message, a downlink control information (DCI) message) that configures DMRS for use by the UE 115-a in a RACH process (e.g., MsgA-DMRS-Config-r16), which may include a field indicating the length of the associated DMRS (e.g., msgA-MaxLength-r16). In this way, the network entity 105-a may set the length of the associated DMRS to a value of "0" to indicate that the UE 115-a does not use DMRS.

[0087] Additionally or alternatively, the DMRS configuration message 205 may be an example of a control message that configures resources for a PUSCH at a UE 115-a (e.g., MsgA-PUSCH-Resource-r16), the control message including a field indicating a number of DMRSs to be used in the PUSCH (e.g., nrofDMRS-Sequences-r16). In this way, the network entity 105-a may set the number of DMRSs to a value of “0” to indicate that the UE 115-a is not using DMRSs in the uplink message 215. In some examples, the DMRS configuration message 205 may also include a field indicating a low-density parity check (LDPC) code and / or RM code used by the UE 115-a to encode the uplink message 215 (e.g., msgA-code-r16 ENUMERATED{LDPC, RM}). In this way, the UE 115-a may perform uplink message encoding 210 according to the LDPC code and / or RM code indicated in the DMRS configuration message 205.

[0088] In some examples, the UE 115-a may select a PRACH preamble to include in the uplink message 215 based on the DMRS configuration message 205. The UE 115-a may also generate a scrambling ID associated with the UE 115-a based on the PRACH preamble, based on control signaling (e.g., RRC signaling) indicating the scrambling ID, or based on both. In some examples, the UE 115-a may perform uplink message encoding 210 based on the scrambling ID and send the encoded uplink message 215 to the network entity 105-a. In this way, the network entity 105-a may receive the encoded uplink message 215 and use non-coherent decoding on the scrambled signals from multiple UEs 115 according to a multi-user decoding algorithm, wherein the network entity 105-a concurrently decodes the data and performs channel estimation for a single UE 115 at a time based on the RM code associated with the transmission. The network entity 105-a may repeat the iteration of the multi-user decoding algorithm until all UEs 115 are correctly decoded or the decoding does not improve. Further discussion of the multi-user decoding algorithm at the network entity 105-a based on non-coherent PUSCH is described herein, including reference to Figure 3 .

[0089] In some cases, the wireless communication system 200 may use non-coherent PUSCH for uplink messages 215 with smaller data payloads (e.g., less than 200 bits of data). In some examples, non-coherent PUSCH may be applied to PUSCH types other than RACH PUSCH (e.g., configured grant PUSCH or grant-based PUSCH). In the example of non-coherent PUSCH, PUSCH resources 235 may be independent of PRACH resources 225.

[0090] In some examples, the UE 115-a may select a PRACH preamble to include in the uplink message 215 based on the DMRS configuration message 205. The UE 115-a may also generate a scrambling ID associated with the UE 115-a based on the PRACH preamble, based on control signaling (e.g., RRC signaling) indicating the scrambling ID, or based on both. In some examples, the UE 115-a may perform uplink message encoding 210 based on the scrambling ID and send the encoded uplink message 215 to the network entity 105-a. In this way, the network entity 105-a may receive the encoded uplink message 215 and use non-coherent decoding on the scrambled signals from multiple UEs 115 according to a multi-user decoding algorithm, wherein the network entity 105-a concurrently decodes the data and performs channel estimation for a single UE 115 at a time based on the RM code associated with the transmission. The network entity 105-a may repeat the iteration of the multi-user decoding algorithm until all UEs 115 are correctly decoded or the decoding does not improve. Further discussion of the multi-user decoding algorithm at the network entity 105-a based on non-coherent PUSCH is described herein, including reference to Figure 3 .

[0091] In some cases, the wireless communication system 200 may use non-coherent PUSCH for uplink messages 215 with smaller data payloads (e.g., less than 200 bits of data). In some examples, non-coherent PUSCH may be applied to PUSCH types other than RACH PUSCH (e.g., configured grant PUSCH or grant-based PUSCH). In the example of non-coherent PUSCH, PUSCH resources 235 may be independent of PRACH resources 225.

[0092] In addition or alternatively to implementing non-coherent PUSCH transmission, the network entity 105-a may use the corresponding PRACH resources 225 to perform channel estimation for the PUSCH resources 235 so as to perform channel estimation without using DMRS or using reduced DMRS opportunities. In this way, the DMRS configuration message 205 may instruct the UE 115-a to use full DMRS, partial DMRS, or no DMRS when sending the uplink message 215. In such a specific implementation, the DMRS configuration message 205 may be an example of a control message (e.g., an RRC message) that configures DMRS for use by the UE 115-a in a RACH process (e.g., MsgA-DMRS-Config-r16), which may include a field indicating an associated DMRS version (e.g., MsgA-PUSCH-DMRS-version ENUMERATED {full, partial, none}). For example, the DMRS configuration message 205 may indicate whether the UE 115-a is to send DMRS on the bandwidth covered by the PRACH, where the UE 115-a may be configured to send DMRS on continuous frequency resources containing PUSCH, on a portion of frequency resources containing PUSCH, or avoid sending DMRS.

[0093] In an example where the UE 115-a is configured not to transmit DMRS, the network entity 105-a may perform channel estimation based on the PRACH preamble (e.g., the PRACH resource 225) and extrapolate channel coefficients to be used for the PUSCH resource 235. Further discussion of the UE 115-a being configured not to transmit DMRS is described herein, including reference to Figure 4 .

[0094] In some examples, the network entity 105-a may configure the UE 115-a to apply a comb structure to the uplink message configuration 220 for the PRACH resource 225. Further discussion of uplink message 215 transmission using a comb structure is described herein, including reference to Figure 5 .

[0095] In some examples, the network entity 105-a may configure the UE 115-a to transmit partial DMRS in frequency resources not covered by the PRACH resources 225. Further discussion of partial DMRS configuration is described herein, including reference to Figure 6 .

[0096] In some examples, the network entity 105-a may configure the first UE 115 and the second UE 115 to use different DMRS configurations (e.g., sending a respective DMRS configuration message 205 to each UE 115). Further discussion of indicating different DMRS configurations to respective UEs 115 is described herein, including reference to Figure 7 .

[0097] In some examples, the network entity 105-a may configure the UE 115-a to transmit a full DMRS at the end of a time slot and after the transmission of the PUSCH resources 235. Further discussion of full DMRS configuration is described herein, including reference to Figure 8 .

[0098] The wireless communication system 200 may utilize PRACH-based channel estimation for low-mobility Internet of Things (IoT) applications, for situations where the PUSCH bandwidth is included in the PRACH bandwidth, for situations where the time gap between the PRACH resources 225 and the PUSCH resources 235 is below a configured threshold, or a combination thereof.

[0099] Figure 3 An example of a multi-user decoding algorithm 300 that supports DMRS configuration for uplink messages according to one or more aspects of the present disclosure is illustrated. In some examples, the multi-user decoding algorithm 300 can implement one or more aspects of the wireless communication system 100 and the wireless communication system 200. For example, referring to Figure 1 , the multi-user decoding algorithm 300 may be implemented by the network entity 105. Additionally or alternatively, reference Figure 2 , the multi-user decoding algorithm 300 may be an example of a multi-user decoding algorithm used by the network entity 105-a. The multi-user decoding algorithm 300 may support decoding multiplexed signaling from multiple UEs 115 competing for access to a channel associated with the network entity 105, wherein the multiplexed signaling includes non-coherent PUSCH transmissions.

[0100] In some cases, the wireless device may perform coherent communication, where the transmitting device may include pilot symbols (e.g., DMRS symbols) in the data transmission. The receiving device may use the pilot symbols to perform channel estimation and extrapolate the channel estimate for the data symbols. The receiving device may then demodulate and decode the data symbols based on the extrapolated channel estimate. In some other cases, the wireless device may perform non-coherent communication, where the transmitting device does not include pilot symbols in the data transmission. Therefore, every symbol in the data transmission can be used for data, which can improve throughput. However, the receiving device will infer (e.g., demodulate and decode) the data information directly from the received signal without performing channel estimation.

[0101] In order to successfully infer data information without performing channel estimation, channel coherence can be utilized. That is, non-coherent communication schemes can utilize the following fact: the channel realizations of adjacent decoded symbols (e.g., in adjacent time or frequency resources) can be identical or strongly correlated. For example, in differential modulation, information can be modulated on the phase difference between adjacent decoded symbols, while in a sequence-based scheme, information can be jointly modulated on a symbol sequence. In order to have high performance at low SNR, non-coherent communication schemes will utilize as much channel coherence as possible. However, longer channel coherence leads to longer memory and thus increases receiver complexity. The complexity of optimal decoding may be exponential in terms of channel coherence and payload size. Therefore, the technology described herein utilizes channel coherence, but the complexity is greatly reduced by using the RM decoding technology that utilizes the differential structure of the code.

[0102] RM codes are algebraic codes, and RM codewords can be considered as binary polynomials, so mathematically, decoding can include polynomial reconstruction. Specifically, the goal of decoding is to recover the coefficients of the polynomial representing the RM codeword. Coefficients of different polynomial orders can be reconstructed at different steps of the decoding process, where the main property of the RM code that can be used for non-coherent communication is the differential property of the RM code. The differential of an RM code of order r is an RM code of order r-1. For example, the decoding process can start with a code of order r and a differential can be applied along the direction α, which can produce an RM code of order r-1. The differential property is beneficial because it is assumed that the channel is the same and the channel coefficients can be removed in order to perform non-coherent decoding using r-1.

[0103] For example, the network entity 105 may receive a multiplexed uplink message including a set of uplink messages (e.g., packets) from a set of different UEs 115. In some examples, each uplink message in the set of uplink messages may be associated with a corresponding RM code. In some examples, each RM code may be a unique RM code associated with the corresponding UE 115. For example, as described in reference Figure 2As described, the network entity 105 may send a DMRS configuration message 205 to each UE 115, the DMRS configuration message indicating the corresponding LDPC code and RM code unique to the receiving UE 115. Additionally or alternatively, each UE 115 may uniquely determine the corresponding RM code. In some cases, each UE 115 may signal the RM code to the network entity 105, and / or the network entity 105 is able to identify each RM code associated with each UE 115. Additionally or alternatively, the network entity 105 and the set of UEs 115 may determine which wireless communications may use RM decoding technology. For example, the network entity 105 may send a corresponding control signal to each UE in the set of UEs 115, indicating a set of one or more transmissions in which RM decoding is to be used. Therefore, each UE in the set of UEs 115 may send a confirmation message indicating that RM decoding is used for one or more transmissions.

[0104] In this way, the network entity 105 may decode each uplink message in the uplink message set using the corresponding RM code according to the multi-user decoding algorithm 300 and perform channel estimation of the corresponding non-coherent PUSCH transmission. For example, the network entity 105 may have an associated non-coherent decoder 305, and the network entity 105 may use the non-coherent decoder to decode multiple non-coherent PUSCH transmissions in the uplink message set. In some examples, the network entity 105 may decode each uplink message in the uplink message set separately. For example, the network entity 105 may decode the multiplexed uplink message using the first corresponding RM code associated with the first UE 115 and the first uplink message. By using the first corresponding RM code, the network entity 105 may attempt to decode (e.g., descramble) the content of the first uplink message according to the multiplexed uplink message. In this way, the network entity 105 may perform channel estimation 310 on the PUSCH transmission of the first uplink message according to the first corresponding RM code. In some examples, the network entity 105 may decode the uplink message and concurrently perform channel estimation 310. Based on decoding and performing channel estimation 310, the network entity 105 may perform signal construction 315 to construct a first uplink message independent of the multiplexed uplink message.

[0105] In this way, the network entity 105 may decode each uplink message in the uplink message set using the corresponding RM code according to the multi-user decoding algorithm 300 and perform channel estimation of the corresponding non-coherent PUSCH transmission. For example, the network entity 105 may have an associated non-coherent decoder 305, and the network entity 105 may use the non-coherent decoder to decode multiple non-coherent PUSCH transmissions in the uplink message set. In some examples, the network entity 105 may decode each uplink message in the uplink message set separately. For example, the network entity 105 may decode the multiplexed uplink message using the first corresponding RM code and the first uplink message associated with the first UE 115.

[0106] By using the first corresponding RM code, the network entity 105 may attempt to decode (e.g., descramble) the content of the first uplink message according to the multiplexed uplink message. In this way, the network entity 105 may perform channel estimation 310 on the PUSCH transmission of the first uplink message according to the first corresponding RM code. In some examples, the network entity 105 may decode the uplink message and perform channel estimation 310 concurrently. Based on decoding and performing channel estimation 310, the network entity 105 may perform signal construction 315 to construct the first uplink message independently of the multiplexed uplink message.

[0107] In some examples, and as described herein, each RM codeword may be a binary polynomial. In this way, the network entity may decode the data associated with the RM codeword based on performing polynomial reconstruction. For example, the network entity 105 may recover the coefficients of the polynomial representing a given RM codeword. The network entity may recover the coefficients of the polynomial by utilizing the differential property of RM decoding, where the differential of an RM code of order r may have an order r-1. In this way, the network entity 105 may receive a multiplexed uplink message across a set of receive antennas, and may calculate the differential of the multiplexed signal based on how the multiplexed signal is received at each receive antenna in the set of receive antennas. In some examples, the network entity 105 may combine each of these differentials across the set of receive antennas to construct an r-1 projection of a tensor (e.g., an algebraic object describing a multilinear relationship between a set of algebraic objects related to a vector space) associated with the rth order binary polynomial of the RM codeword.

[0108] Based on constructing the r-1 projection, the network entity may reconstruct a square tensor from the projection and eliminate the contribution of the square tensor from the set of receive antennas. In this way, the network entity 105 may calculate another set of differences as another channel output after eliminating the contribution of the square tensor. In some examples, the network entity may recursively reconstruct the set of square tensors to obtain the RM codeword and associated data for a given UE 115 at the network entity 105.

[0109] Based on successfully decoding the first uplink message, performing channel estimation 310, and performing signal construction 315, the network entity 105 may remove (e.g., eliminate) the first uplink message from the multiplexed uplink message. That is, the network entity 105 may remove the contribution of the first UE 115 to the overall signal. For example, the network entity 105 may perform interference cancellation 320, in which the network entity 105 eliminates the content of the first uplink message from the received multiplexed uplink message.

[0110] After or concurrently with applying the multi-user decoding algorithm 300 to the first UE 115, the network entity 105 may perform the multi-user decoding algorithm 300 using the second corresponding RM code to decode a second uplink message associated with the second corresponding RM code, perform channel estimation 310, and perform signal construction 315. In some examples, the network entity 105 may repeat iterations of the multi-user decoding algorithm 300 until each UE 115 associated with the multiplexed uplink message is correctly decoded and / or until the algorithm results in no additional improvement for each decoded uplink message from the multiplexed uplink message.

[0111] In some implementations, the network entity 105 may use the multi-user decoding algorithm 300 to decode each of the respective uplink messages simultaneously from the multiplexed uplink messages. In such cases, the network entity 105 may utilize each of the respective decoded uplink messages individually or collectively to determine whether any improvements may be made to one or more of the decoded uplink messages. If improvements may be made, the network entity 105 may apply all or a portion of the multi-user decoding algorithm 300 to one or more specific uplink messages that may be improved, or to a complete set of uplink messages associated with the multiplexed uplink messages.

[0112] In some examples, if the network entity 105 identifies no improvement in decoding the multi-user decoding algorithm 300, the network entity 105 may avoid repeating the multi-user decoding algorithm 300. For example, one or more parameters associated with decoding the multiplexed uplink message (e.g., time to decode the message, power used to decode the message, etc.) may satisfy one or more configured thresholds, thereby instructing the network entity 105 to end the multi-user decoding algorithm 300.

[0113] Figure 4An example of an uplink message configuration 400 supporting DMRS configuration for an uplink message according to one or more aspects of the present disclosure is illustrated. In some examples, the uplink message configuration 400 can implement one or more aspects of the wireless communication system 100 and the wireless communication system 200. For example, referring to Figure 2 , the uplink message configuration 400 may be an example of the uplink message configuration 220. Additionally or alternatively, reference Figure 2 , PRACH resources 405, blank resources 410, and PUSCH resources 415 may be respective examples of PRACH resources 225, blank resources 230, and PUSCH resources 235. Uplink message configuration 400 may support uplink message transmission from UE 115 to network entity 105 without DMRS in at least a first portion of the uplink message.

[0114] In some examples, UE 115 may generate uplink message configuration 400 based on control signaling (e.g., RRC signaling) received from network entity 105. For example, referring to Figure 2 , the uplink message configuration 400 may be an example of a configuration generated based on receiving the DMRS configuration message 205, which includes a field (e.g., parameter) indicating that the UE 115 does not include DMRS (e.g., MsgA-PUSCH-DMRS-version ENUMERATED {None}). Additionally or alternatively, the uplink message may include a field indicating whether the UE 115 is to send DMRS on the frequency range (e.g., bandwidth) covered by the PRACH resources 405. Therefore, the UE 115 may generate the uplink message configuration 400 without DMRS.

[0115] like Figure 4 As shown, the uplink message configuration 400 includes a set of PRACH resources 405 during a first time range spanning a first frequency range, and may include a set of PUSCH resources 415 during a second time range spanning a second frequency range. In some examples of the uplink message configuration 400, the second frequency range associated with the PUSCH resources 415 may be included in the first frequency range associated with the PRACH resources 405 (e.g., the PUSCH bandwidth PRACH bandwidth). For example, Figure 4As shown, the PRACH resources 405 may span 12 resource blocks of the frequency, and the PUSCH resources may span 6 resource blocks of the frequency, wherein the 6 resource blocks may be a subset of the 12 resource blocks. In some implementations, the UE 115 may be configured to generate an uplink message configuration 400 without DMRS based on the second frequency range being included in the first frequency range (e.g., when the PRACH BW includes the PUSCH BW). In some cases, the UE 115 may be configured to generate an uplink message configuration 400 without DMRS based on the format of the PRACH resources 405, the PUSCH resources 415, or both. For example, the UE 115 may be configured to generate an uplink message configuration 400 without DMRS based on being configured to send the PRACH resources 405 according to a short format (e.g., 12 resource blocks based on a 15kHz SCS) and / or send the PUSCH resources 415 according to a long format (e.g., 6 resource blocks based on a 15kHz SCS).

[0116] Additionally or alternatively, the uplink message configuration 400 may include a small time gap between the PRACH resources 405 and the PUSCH resources 415 (eg, the number of blank resources 410 between the end of the PRACH resources 405 and the beginning of the PUSCH resources 415 may be below a configured threshold).

[0117] In this way, the UE 115 may send an uplink message to the network entity 105 according to the uplink message configuration 400. In some examples, the network entity 105 may perform channel estimation on the PUSCH resources 415 based on performing channel estimation on the PRACH resources 405. For example, the network entity 105 may perform a direct Fourier transform (DFT)-based channel estimation (e.g., a sounding reference signal (SRS)-based channel estimation) for the set of PRACH resources 405. In some examples, the network entity 105 may perform channel estimation for the PRACH resources 405 via a Zadoff-Chu sequence. Based on performing channel estimation on the PRACH preamble, the network entity 105 may extrapolate channel coefficients for the PUSCH resources 415 without using a DMRS (e.g., adjusting the channel coefficients based on changes in frequency and time between the PUSCH resources 415 and the PRACH resources 405).

[0118] Based on UE 115 not including DMRS in the uplink message, UE 115 and network entity 105 may benefit from a lower coding rate associated with the uplink message.

[0119] Figure 5An example of an uplink message configuration 500 supporting DMRS configuration for an uplink message according to one or more aspects of the present disclosure is illustrated. In some examples, the uplink message configuration 500 can implement one or more aspects of the wireless communication system 100, the wireless communication system 200, and the uplink message configuration 400. For example, referring to Figure 2 , the uplink message configuration 500 may be an example of the uplink message configuration 220. Additionally or alternatively, reference Figure 2 , PRACH resources 505, blank resources 510, and PUSCH resources 515 may be respective examples of PRACH resources 225, blank resources 230, and PUSCH resources 235. Uplink message configuration 500 may support uplink message transmission from UE 115 to network entity 105 without DMRS in at least a first portion of the uplink message.

[0120] In some examples, UE 115 may generate uplink message configuration 500 based on control signaling received from network entity 105. For example, referring to Figure 2 , uplink message configuration 500 may be an example of a configuration generated based on receiving DMRS configuration message 205, which includes a field (e.g., MsgA-PUSCH-DMRS-version ENUMERATED {None}) indicating that UE 115 does not include DMRS. Therefore, UE 115 may generate uplink message configuration 500 without DMRS.

[0121] like Figure 5As shown, the uplink message configuration 500 includes a set of PRACH resources 505 during a first time range spanning a first frequency range, and may include a set of PUSCH resources 515 during a second time range spanning a second frequency range. In some examples, the UE 115 may configure the PRACH resources 505 of the uplink message configuration 500 according to a comb structure. In some examples, the UE 115 may use a comb structure for the PRACH resources 505 based on receiving an RRC message or some other control message indicating the use of a comb (e.g., comb-1 / 2 / 3 / 4). In some cases, the control message may indicate that the UE 115 is to implement a comb structure, and the UE 115 may select which comb structure to use. In such cases, the UE 115 may send an indication of the comb structure that the UE 115 applies or will apply to the PRACH resources 505 to the network entity 105. In some cases, the control message may indicate a specific comb structure that the UE 115 is to apply to the PRACH resources 405. In some implementations, the UE 115 may be configured to apply a comb structure such that the PRACH resources 505 span a frequency range that includes the frequency range covered by the PUSCH resources 515 (e.g., Figure 5 as depicted in ).

[0122] By adding a comb structure to the PRACH resources 505, the PRACH transmission can cover a larger frequency band. For example, for a subcarrier spacing (SCS) of 15 kHz, a PRACH transmission that fills a total of 12 frequency resource blocks will span a total of 18 frequency resource blocks (e.g., including the blank resources 510 between the PRACH resources 505). In another example, for a 30 kHz SCS, a PRACH transmission that fills a total of 6 frequency resource blocks will span a total of 12 frequency resource blocks (e.g., as shown in FIG. Figure 5 In one example, every 32 PRACH preambles may be mapped to half of the PUSCH. Thus, the PUSCH bandwidth may be divided into four, and the 32 preambles may be mapped to one quarter. In some examples, using a comb structure for PRACH transmissions may increase the number of UEs 115 multiplexed for a given uplink transmission to the network entity 105.

[0123] As reference Figure 4As described, UE 115 may send an uplink message to network entity 105 according to uplink message configuration 500. In some examples, network entity 105 may perform channel estimation on PUSCH resources 515 based on performing channel estimation on PRACH resources 505. Based on performing channel estimation on the PRACH preamble, network entity 105 may extrapolate channel coefficients for PUSCH resources 515 without using DMRS (e.g., adjust channel coefficients based on changes in frequency and time between PUSCH resources 515 and PRACH resources 505).

[0124] Figure 6 An example of an uplink message configuration 600 supporting DMRS configuration for an uplink message according to one or more aspects of the present disclosure is illustrated. In some examples, the uplink message configuration 600 can implement one or more aspects of the wireless communication system 100, the wireless communication system 200, and the uplink message configuration 400. For example, referring to Figure 2 , the uplink message configuration 600 may be an example of the uplink message configuration 220. Additionally or alternatively, reference Figure 2 , PRACH resources 605, blank resources 610, and PUSCH resources 615 may be respective examples of PRACH resources 225, blank resources 230, and PUSCH resources 235. The uplink message configuration 600 may support uplink message transmission from the UE 115 to the network entity 105 without a DMRS in at least a first portion of the uplink message.

[0125] In some examples, UE 115 may generate uplink message configuration 600 based on control signaling received from network entity 105. For example, referring to Figure 2 , the uplink message configuration 600 may be an example of a configuration generated based on receiving the DMRS configuration message 205, the DMRS configuration message including a field (e.g., MsgA-PUSCH-DMRS-versionENUMERATED{part}) indicating that the UE 115 does not include a DMRS in the first part of the uplink message but may be configured to include a DMRS in the second part. Thus, the UE 115 may generate the uplink message configuration 600 with a partial DMRS (e.g., a DMRS included in a subset of frequency resources of the uplink message, a subset of time resources of the uplink message, or a combination thereof).

[0126] like Figure 6As shown, the uplink message configuration 600 includes a set of PRACH resources 605 during a first time range spanning a first frequency range, and may include a set of PUSCH resources 615 during a second time range spanning a second frequency range. In some examples, according to the DMRS configuration message 205 indicating a partial DMRS configuration, the second time range including the set of PUSCH resources 615 may also include a set of DMRS resources 620. In some examples, the DMRS resources 620 of the partial DMRS configuration may span resources on frequency resources not covered by the PRACH resources 605 (e.g., such as Figure 6 In some examples, UE 115 may Figure 4 and Figure 5 The uplink message configuration 600 may be generated using the techniques described herein. For example, the UE 115 may receive an RRC message from the network entity 105 indicating the use of a comb structure for the PRACH resources 605, and insert DMRS resources 620 in the blank frequency resources of the comb structure, wherein the blank frequency resources may be in a time range associated with the PRACH resources 405, a time range associated with the PUSCH resources 415, or a combination thereof. For example, the UE 115 may be configured to include DMRS in all or a subset of frequency resources not covered by the PRACH, and may include DMRS with the PRACH or the PUSCH. Additionally or alternatively, the UE 115 may generate the uplink message configuration 600 such that the PUSCH bandwidth is PRACH bandwidth.

[0127] Thus, UE 115 may send an uplink message to network entity 105 according to uplink message configuration 600. In some examples, network entity 105 may perform channel estimation on PUSCH resources 615 based on performing channel estimation on PRACH resources 605 in conjunction with channel estimation of DMRS resources 620. For example, as shown in FIG. Figure 4 As discussed, the network entity 105 may perform channel estimation for the PRACH resources 605 via a Zadoff-Chu sequence and further perform channel estimation for the DMRS resources 620. In this way, the network entity 105 may combine the PRACH and DMRS channel estimates and extrapolate channel coefficients for the PUSCH resources 615. By combining channel estimates from portions of the DMRS and PRACH, the network entity 105 may benefit from increased reliability for performing PUSCH channel estimation.

[0128] Figure 7Examples of uplink message configurations 700 according to one or more aspects of the present disclosure are illustrated, which may include uplink message configurations 700-a and 700-b that support DMRS configurations for uplink messages. In some examples, the uplink message configuration 700 may implement one or more aspects of the wireless communication system 100, the wireless communication system 200, and the uplink message configuration 400. For example, referring to Figure 1 and Figure 2 , uplink message configurations 700-a and 700-b may be respective examples of uplink message configurations 220 for the first UE 115 and the second UE 115. Additionally or alternatively, reference Figure 2 , PRACH resources 705, blank resources 710, and PUSCH resources 715 may be respective examples of PRACH resources 225, blank resources 230, and PUSCH resources 235. Uplink message configuration 700 may support sending respective uplink messages from first UE 115 and second UE 115 to network entity 105 using different DMRS configurations.

[0129] In some examples, the first UE 115 and the second UE 115 may generate uplink message configurations 700-a and 700-b according to corresponding control signaling received from the network entity 105. For example, referring to Figure 2 , the uplink message configuration 700-a can be an example of a configuration generated based on receiving a DMRS configuration message 205, which includes a field indicating that the first UE 115 includes a complete DMRS (e.g., MsgA-PUSCH-DMRS-version ENUMERATED{complete}). Additionally or alternatively, the uplink message configuration 700-b can be an example of a configuration generated based on receiving a DMRS configuration message 205, which includes a field indicating that the second UE 115 does not include a DMRS (e.g., MsgA-PUSCH-DMRS-version ENUMERATED{none}). Although Figure 7 Two different DMRS configurations for two UEs 115 are illustrated, but it should be understood that the network entity 105 may configure any number of UEs 115 using any of the different DMRS configurations described herein.

[0130] like Figure 7As illustrated, the uplink message configuration 700-b may not include a set of PRACH resources 705, but instead include a full DMRS and PUSCH transmission over a second time range, where the DMRS resources 720 span the same frequency resources as the PUSCH resources 715. Additionally or alternatively, the uplink message configuration 700-b includes a set of PRACH resources 705 during a first time range spanning a first frequency range, and may include a set of PUSCH resources 715 during a second time range spanning a second frequency range. In some examples of the uplink message configuration 700-b, the second frequency range associated with the PUSCH resources 715 may be included in the first frequency range associated with the PRACH resources 705 (e.g., the PUSCH bandwidth PRACH bandwidth).

[0131] In this way, the first UE 115 and the second UE 115 can send corresponding uplink messages to the network entity 105 according to the uplink message configurations 700-a and 700-b. In some examples, the network entity 105 can use the received DMRS resources 720 to perform channel estimation on the PUSCH from the first UE 115. Additionally or alternatively, the network entity 105 can perform channel estimation on the PRACH resources 705 based on using the reference Figure 4 The described techniques are used to extrapolate channel coefficients to perform channel estimation for PUSCH resources 715 from the second UE 115. By using different DMRS configurations for different UEs 115, the network entity 105 can benefit from being able to use the various PUSCH channel estimation techniques described herein while reducing the total number of DMRS resources 720 used.

[0132] Figure 8 An example of an uplink message configuration 800 supporting DMRS configuration for an uplink message according to one or more aspects of the present disclosure is illustrated. In some examples, the uplink message configuration 800 can implement one or more aspects of the wireless communication system 100, the wireless communication system 200, and the uplink message configuration 400. For example, referring to Figure 2 , the uplink message configuration 800 may be an example of the uplink message configuration 220. Additionally or alternatively, reference Figure 2 , PRACH resources 805, blank resources 810, and PUSCH resources 815 may be respective examples of PRACH resources 225, blank resources 230, and PUSCH resources 235. The uplink message configuration 800 may support uplink message transmission from the UE 115 to the network entity 105 without a DMRS in at least a first portion of the uplink message.

[0133] In some examples, UE 115 may generate uplink message configuration 800 based on control signaling received from network entity 105. For example, referring to Figure 2 , the uplink message configuration 800 can be an example of a configuration generated based on receiving the DMRS configuration message 205, which includes a field indicating that the UE 115 includes a DMRS as part of the uplink message (e.g., MsgA-PUSCH-DMRS-version ENUMERATED {complete}). In this way, the UE 115 can generate an uplink message configuration 800 with a complete DMRS (e.g., a DMRS spanning a set of frequency resources including a PUSCH frequency resource). In some examples, the DMRS configuration message 205 may also include a field indicating that the UE 115 includes a DMRS resource 820 for a complete DMRS at the end of a time slot associated with the PUSCH transmission of the uplink message configuration 800. Additionally or alternatively, the UE 115 may determine or be preconfigured to include a DMRS at the end of a time slot. For example, the UE 115 may receive an indication or be configured to avoid including DMRS with the PRACH, and thus the UE 115 may determine to include DRMS ​​after the PUSCH when the UE 115 is configured to include the full DMRS with the uplink message.

[0134] In some examples, in the event that the Doppler of one or more channels between the UE 115 and the network entity 105 is above a configured threshold, the network entity 105 may instruct the UE 115 to use a combined DMRS. In some cases, the UE 115 may be configured to combine the DMRS at the end of the uplink message in a high Doppler scenario. For example, if the UE 115 is operating in a high mobility environment (e.g., on a high-speed train), the UE 115 may experience a frequency Doppler shift for the set of time-frequency resources as the UE 115 moves relative to the network entity 105. For example, due to the high Doppler, the channel estimate based on the PRACH resource 805 may no longer be completely accurate before the time of the PUSCH resource 815. By interpolating channel coefficients from PRACH resources 805 before PUSCH transmission and interpolating channel coefficients of DMRS resources 820 after PUSCH transmission, the network entity 105 can identify and mitigate time and frequency resource shifts caused by Doppler to increase channel estimates for PUSCH resources 815.

[0135] like Figure 8As shown, uplink message configuration 800 includes a set of PRACH resources 805 during a first time range spanning a first frequency range, and may include a set of PUSCH resources 815 and DMRS resources 820 during a second time range spanning a second frequency range.

[0136] Thus, UE 115 may send an uplink message to network entity 105 according to uplink message configuration 800. In some examples, network entity 105 may perform channel estimation on PUSCH resources 815 based on performing channel estimation on PRACH resources 805 in conjunction with channel estimation on DMRS resources 820. For example, as shown in FIG. Figure 4 As discussed, the network entity 105 may perform channel estimation for the PRACH resources 805 via a Zadoff-Chu sequence and further perform channel estimation for the DMRS resources 820. In this way, the network entity 105 may combine the PRACH and DMRS channel estimates and interpolate channel coefficients for the PUSCH resources 815. By interpolating channel estimates from portions of the DMRS and PRACH, the network entity 105 may benefit from increased reliability for performing PUSCH channel estimation.

[0137] Fig. 9 An example of a process flow 900 for supporting DMRS configuration for uplink messages according to one or more aspects of the present disclosure is illustrated. In some examples, the process flow 900 can implement aspects of the wireless communication system 100, the wireless communication system 200, the multi-user decoding algorithm 300, the uplink message configuration 400 to 800, or a combination thereof. The process flow 900 includes a UE 115-b and a network entity 105-b, which can be as described in reference Figure 1 and Figure 2 105 and the corresponding examples of the described UE 115 and network entity 105. The following alternative examples may be implemented, in which some of the steps may be performed in a different order than described or not performed at all. In some cases, the steps may include additional features not mentioned below, or other steps may be added. In addition, although the process flow 900 shows the process between a single UE 115 and a single network entity 105, it should be understood that these processes may occur between any number of wireless devices, network devices, and / or network device types.

[0138] At 905, UE 115-b may receive control signaling from network entity 105-b indicating a DMRS configuration for an uplink message. In some examples, the control signaling may indicate that UE 115-b may avoid including DMRS in at least a first portion of the uplink message based on the DMRS configuration. In some examples, UE 115-b may receive an RRC message (or some other control message) including the DMRS configuration for the uplink message. In some examples, the DMRS configuration may be based on a Doppler spread amount at UE 115-b.

[0139] In some examples, the DMRS configuration may include a field indicating that UE 115-b may avoid including DMRS in the first part of the uplink message. Additionally or alternatively, the DMRS configuration includes a field indicating the LDPC code and RM code used by UE 115-b to encode the uplink message. In some cases, this field may be included in an uplink channel resource information element.

[0140] In some examples, UE 115-b may receive an indication of whether UE 115-b may include DMRS in the second part of the uplink message on a frequency bandwidth that may be covered by RACH of the uplink message. In some cases, RACH may be included in the first part of the uplink message. For example, UE 115-b may receive a first configuration indicating that UE 115-b includes one or more DMRS in each frequency resource of the frequency bandwidth covered by RACH. Additionally or alternatively, UE 115-b may receive a second configuration indicating that one or more DMRS are included in a subset of frequency resources of the frequency bandwidth covered by RACH. Additionally or alternatively, UE 115-b may receive a third configuration indicating that UE 115-b avoids including DMRS in the second part of the uplink message.

[0141] In some examples, UE 115-b may receive an indication of a PRACH comb pattern to be applied to a first portion of an uplink message.

[0142] In some examples, at 910, UE 115-b may select a PRACH preamble to include in the uplink message. Additionally or alternatively, UE 115-b may generate a scrambling ID associated with UE 115-b based on the PRACH preamble, based on RRC signaling (e.g., from network entity 105-b) indicating the scrambling ID, or both. In such examples, encoding the uplink message may be based on the scrambling identity.

[0143] At 915, UE 115-b may encode an uplink message that does not have a DMRS in at least a first portion of the uplink message according to the DMRS configuration. In some examples, UE 115-b may encode an uplink message that does not include a DMRS in the first portion using an RM code according to the DMRS configuration. In some examples, UE 115-b may encode an uplink message that does not have a DMRS in any portion of the uplink message according to the DMRS configuration. In some examples, UE 115-b may encode the first portion of the uplink message according to a PRACH comb pattern based on the DMRS configuration. In some examples, UE 115-b may encode the uplink message according to the DMRS configuration to include one or more DMRS in the second portion of the uplink message. In some examples, UE 115-b may encode the second portion of the uplink message according to the DMRS configuration to include one or more DMRS at the beginning or end of the second portion. In some examples, UE 115-b may encode the second portion of the uplink message based on the DMRS configuration to include one or more DMRS in a frequency resource set without a RACH signal. In some examples, UE 115-b may encode the second portion of the uplink message based on the DMRS configuration to include one or more DMRS in a frequency resource set that includes a RACH signal in the first portion.

[0144] At 920, UE 115-b may send an uplink message based on encoding the uplink message. In some examples, UE 115-b may send a PRACH in a first frequency resource set in a first part of the uplink message according to a DMRS configuration, and send an uplink shared channel (e.g., PUSCH) in a second frequency resource set in a second part of the uplink message according to the DMRS configuration. In some examples, the first frequency resource set and the second frequency resource set include the same frequency resource set or a subset of the same frequency resources. In some cases, the DMRS configuration may include the second frequency resource set based on the first frequency resource set. In some cases, the DMRS configuration may include the first frequency resource set based on the second frequency resource set.

[0145] In some examples, network entity 105-b may receive data from multiple UEs 115 ( Fig. 9 ) receives a signal including an uplink message set, wherein each uplink message in the uplink message set may be associated with an RM code.

[0146] At 925, the network entity 105-b may decode the uplink message based on the DMRS configuration. In an example where the network entity 105-b receives a signal including a set of uplink messages from different UEs 115, the network entity 105-b may decode the uplink message using a corresponding RM code according to the DMRS configuration, wherein the uplink message may not include a DMRS in a first portion of the uplink message. In this way, the network entity 105-b may eliminate the decoded uplink message from the signal including the set of uplink messages according to a multi-user decoding algorithm.

[0147] Fig.10 A block diagram 1000 of a device 1005 supporting DMRS configuration for uplink messages according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of a UE 115 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0148] The receiver 1010 may provide means for receiving information associated with various information channels (e.g., a control channel related to a DMRS configuration for an uplink message, a data channel, an information channel) such as packets, user data, control information, or any combination thereof. The information may be communicated to other components of the device 1005. The receiver 1010 may utilize a single antenna or a collection of multiple antennas.

[0149] The transmitter 1015 may provide means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to DMRS configurations for uplink messages, data channels, information channels). In some examples, the transmitter 1015 may be co-located with the receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or a collection of multiple antennas.

[0150] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of DMRS configuration for uplink messages as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0151] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured to or otherwise supports components for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0152] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0153] In some examples, communication manager 1020 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in conjunction with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0154] According to the examples disclosed herein, the communication manager 1020 can support wireless communication at the UE. For example, the communication manager 1020 can be configured to or otherwise support a component for receiving control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates that the UE is to avoid including DMRS in at least a first portion of the uplink message based on the DMRS configuration. The communication manager 1020 can be configured to or otherwise support a component for encoding an uplink message without DMRS in at least a first portion of the uplink message according to the DMRS configuration. The communication manager 1020 can be configured to or otherwise support a component for sending an uplink message based on encoding the uplink message.

[0155] By including or configuring a communication manager 1020 according to the examples described herein, the device 1005 (e.g., a processor controlling or otherwise coupled to the receiver 1010, the transmitter 1015, the communication manager 1020, or a combination thereof) may support techniques for reducing bottlenecks at DMRS ports by reducing DMRS in uplink messages, which may be understood as reducing signaling overhead, reducing power consumption, and more efficiently utilizing communication resources.

[0156] Fig.11 A block diagram 1100 of a device 1105 supporting DMRS configuration for uplink messages according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the device 1005 or UE 115 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0157] The receiver 1110 may provide means for receiving information associated with various information channels (e.g., a control channel related to a DMRS configuration for an uplink message, a data channel, an information channel) such as packets, user data, control information, or any combination thereof. The information may be communicated to other components of the device 1105. The receiver 1110 may utilize a single antenna or a collection of multiple antennas.

[0158] The transmitter 1115 may provide means for transmitting signals generated by other components of the device 1105. For example, the transmitter 1115 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to DMRS configurations for uplink messages, data channels, information channels). In some examples, the transmitter 1115 may be co-located with the receiver 1110 in a transceiver module. The transmitter 1115 may utilize a single antenna or a collection of multiple antennas.

[0159] The device 1105 or its various components may be examples of components for performing various aspects of DMRS configuration for uplink messages as described herein. For example, the communication manager 1120 may include a control signaling receiving component 1125, an encoding component 1130, an uplink message sending component 1135, or any combination thereof. The communication manager 1120 may be an example of various aspects of the communication manager 1020 as described herein. In some examples, the communication manager 1120 or its various components may be configured to use or otherwise cooperate with the receiver 1110, the transmitter 1115, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 1120 may receive information from the receiver 1110, transmit information to the transmitter 1115, or integrate with the receiver 1110, the transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0160] According to the examples disclosed herein, the communication manager 1120 may support wireless communication at the UE. The control signaling receiving component 1125 may be configured to or otherwise support a means for receiving control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates to the UE based on the DMRS configuration to avoid including DMRS in at least a first portion of the uplink message. The encoding component 1130 may be configured to or otherwise support a means for encoding an uplink message without DMRS in at least a first portion of the uplink message according to the DMRS configuration. The uplink message sending component 1135 may be configured to or otherwise support a means for sending an uplink message based on encoding the uplink message.

[0161] Fig.12A block diagram 1200 of a communication manager 1220 supporting DMRS configuration for uplink messages according to one or more aspects of the present disclosure is shown. The communication manager 1220 can be an example of aspects of the communication manager 1020, the communication manager 1120, or both as described herein. The communication manager 1220 or its various components can be examples of components for performing various aspects of DMRS configuration for uplink messages as described herein. For example, the communication manager 1220 may include a control signaling receiving component 1225, an encoding component 1230, an uplink message sending component 1235, a PRACH preamble code selection component 1240, a scrambling ID generation component 1245, or any combination thereof. Each of these components can communicate with each other directly or indirectly (e.g., via one or more buses).

[0162] According to the examples disclosed herein, the communication manager 1220 may support wireless communication at the UE. The control signaling receiving component 1225 may be configured to or otherwise support a means for receiving control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates to the UE based on the DMRS configuration to avoid including DMRS in at least a first portion of the uplink message. The encoding component 1230 may be configured to or otherwise support a means for encoding an uplink message without DMRS in at least a first portion of the uplink message according to the DMRS configuration. The uplink message sending component 1235 may be configured to or otherwise support a means for sending an uplink message based on encoding the uplink message.

[0163] In some examples, to support encoding of an uplink message, encoding component 1230 may be configured as or otherwise support means for encoding an uplink message that does not include a DMRS in the first portion using an RM code according to a DMRS configuration.

[0164] In some examples, the DMRS configuration includes a field indicating that the UE is to avoid including the DMRS in the first part of the uplink message.

[0165] In some examples, the DMRS configuration includes a field indicating an LDPC code and an RM code used by the UE to encode an uplink message. In some examples, the field is included in an uplink channel resource information element.

[0166] In some examples, the PRACH preamble selection component 1240 may be configured to or otherwise support a component for selecting a PRACH preamble to include in an uplink message. In some examples, the scrambling ID generation component 1245 may be configured to or otherwise support a component for generating a scrambling identity based on the PRACH preamble, or based on RRC signaling indicating a scrambling identity associated with the UE, or based on both, wherein encoding the uplink message is based on the scrambling identity.

[0167] In some examples, to support receiving a DMRS configuration, the control signaling receiving component 1225 may be configured to or otherwise support a component for receiving an indication of whether the UE is to include a DMRS in the second part of the uplink message on a frequency bandwidth covered by a RACH of the uplink message, wherein the RACH is included in the first part of the uplink message.

[0168] In some examples, to support receiving the indication, the control signaling receiving component 1225 may be configured to or otherwise support a component for receiving a first configuration, the first configuration indicating that the UE includes one or more demodulation reference signals in each frequency resource of the frequency bandwidth covered by the RACH. In some examples, to support receiving the indication, the control signaling receiving component 1225 may be configured to or otherwise support a component for receiving a second configuration, the second configuration indicating that the UE includes one or more demodulation reference signals in a subset of frequency resources of the frequency bandwidth covered by the RACH. In some examples, to support receiving the indication, the control signaling receiving component 1225 may be configured to or otherwise support a component for receiving a third configuration, the third configuration indicating that the UE avoids including demodulation reference signals in the second part of the uplink message.

[0169] In some examples, to support receiving a DMRS configuration, control signaling receiving component 1225 may be configured or otherwise support means for receiving an indication of a PRACH comb pattern to be applied to a first portion of an uplink message.

[0170] In some examples, to support encoding of an uplink message, encoding component 1230 may be configured or otherwise support means for encoding an uplink message without a DMRS in any portion of the uplink message according to a DMRS configuration.

[0171] In some examples, to support encoding of the uplink message, encoding component 1230 may be configured as or otherwise support means for encoding a first portion of the uplink message according to a PRACH comb pattern based on a DMRS configuration.

[0172] In some examples, to support encoding of the uplink message, encoding component 1230 may be configured to or otherwise support means for encoding the uplink message according to the DMRS configuration to include one or more DMRS in the second portion of the uplink message.

[0173] In some examples, to support encoding of the uplink message, encoding component 1230 may be configured to or otherwise support means for encoding the second portion of the uplink message according to the DMRS configuration to include one or more DMRS at the beginning or end of the second portion.

[0174] In some examples, to support encoding of the uplink message, encoding component 1230 may be configured to or otherwise support means for encoding a second portion of the uplink message according to a DMRS configuration to include one or more DMRS in a frequency resource set without a RACH signal.

[0175] In some examples, to support encoding of an uplink message, encoding component 1230 may be configured as or otherwise support a component for encoding a second portion of the uplink message based on a DMRS configuration to include one or more DMRSs in a frequency resource set that includes a RACH signal in the first portion.

[0176] In some examples, the DMRS configuration is based on the amount of Doppler spread at the UE.

[0177] In some examples, to support sending an uplink message, the uplink message sending component 1235 may be configured to or otherwise support means for sending a PRACH in a first set of frequency resources in a first portion of the uplink message according to a DMRS configuration. In some examples, to support sending an uplink message, the uplink message sending component 1235 may be configured to or otherwise support means for sending an uplink shared channel in a second set of frequency resources in a second portion of the uplink message according to a DMRS configuration, wherein the first set of frequency resources and the second set of frequency resources include the same set of frequency resources or a subset of the same frequency resources.

[0178] In some examples, the DMRS configuration includes a second set of frequency resources based on the first set of frequency resources.

[0179] In some examples, the DMRS configuration includes a first set of frequency resources based on a second set of frequency resources.

[0180] In some examples, to support receiving control signaling, control signaling receiving component 1225 may be configured or otherwise support means for receiving an RRC message including a DMRS configuration for an uplink message.

[0181] Fig.13 A diagram of a system 1300 including a device 1305 supporting DMRS configuration for uplink messages according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of a device 1005, a device 1105, or a UE 115 as described herein, or include components thereof. The device 1305 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1305 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1320, an input / output (I / O) controller 1310, a transceiver 1315, an antenna 1325, a memory 1330, a code 1335, and a processor 1340. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1345).

[0182] I / O controller 1310 can manage input signals and output signals of device 1305. I / O controller 1310 can also manage peripheral devices that are not integrated into device 1305. In some cases, I / O controller 1310 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1310 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 1310 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1310 may be implemented as part of a processor, such as processor 1340. In some cases, a user may interact with device 1305 via I / O controller 1310 or via hardware components controlled by I / O controller 1310.

[0183] In some cases, the device 1305 may include a single antenna 1325. However, in some other cases, the device 1305 may have more than one antenna 1325, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1315 may communicate bidirectionally via one or more antennas 1325, a wired or wireless link, as described herein. For example, the transceiver 1315 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1315 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1325 for transmission; and demodulating packets received from one or more antennas 1325. The transceiver 1315 or the transceiver 1315 and one or more antennas 1325 may be examples of transmitters 1015, transmitters 1115, receivers 1010, receivers 1110, or any combination thereof or components thereof as described herein.

[0184] Memory 1330 may include random access memory (RAM) and read-only memory (ROM). Memory 1330 may store computer-readable, computer-executable code 1335 including instructions that, when executed by processor 1340, cause device 1305 to perform various functions described herein. Code 1335 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1335 may not be directly executable by processor 1340, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1330 may also include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0185] Processor 1340 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1340 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1340. Processor 1340 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1330) to enable device 1305 to perform various functions (e.g., various functions or tasks supporting DMRS configuration for uplink messages). For example, device 1305 or a component of device 1305 may include processor 1340 and memory 1330 coupled to or coupled to processor 1340, and processor 1340 and memory 1330 are configured to perform various functions described herein.

[0186] According to the examples disclosed herein, the communication manager 1320 may support wireless communication at the UE. For example, the communication manager 1320 may be configured to or otherwise support a means for receiving control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates to the UE based on the DMRS configuration to avoid including DMRS in at least a first portion of the uplink message. The communication manager 1320 may be configured to or otherwise support a means for encoding an uplink message without DMRS in at least a first portion of the uplink message according to the DMRS configuration. The communication manager 1320 may be configured to or otherwise support a means for sending an uplink message based on encoding the uplink message.

[0187] By including or configuring a communication manager 1320 according to the examples described herein, the device 1305 may support techniques for reducing bottlenecks at DMRS ports by reducing DMRS in uplink messages, which may be understood as reducing signaling overhead, reducing power consumption, improving coordination between devices, extending battery life, improving utilization of processing power, and more efficiently utilizing communication resources.

[0188] In some examples, the communication manager 1320 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1315, one or more antennas 1325, or any combination thereof. Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the processor 1340, the memory 1330, the code 1335, or any combination thereof. For example, the code 1335 may include instructions that are executable by the processor 1340 to cause the device 1305 to perform various aspects of DMRS configuration for uplink messages as described herein, or the processor 1340 and the memory 1330 may be otherwise configured to perform or support such operations.

[0189] Fig.14 A block diagram 1400 of a device 1405 supporting DMRS configuration for uplink messages according to one or more aspects of the present disclosure is shown. The device 1405 may be an example of aspects of the network entity 105 as described herein. The device 1405 may include a receiver 1410, a transmitter 1415, and a communication manager 1420. The device 1405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0190] Receiver 1410 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 1405. In some examples, receiver 1410 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1410 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0191] The transmitter 1415 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1405. For example, the transmitter 1415 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1415 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1415 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1415 and the receiver 1410 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0192] The communication manager 1420, the receiver 1410, the transmitter 1415, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of DMRS configuration for uplink messages as described herein. For example, the communication manager 1420, the receiver 1410, the transmitter 1415, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0193] In some examples, the communication manager 1420, the receiver 1410, the transmitter 1415, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports means for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0194] Additionally or alternatively, in some examples, the communication manager 1420, the receiver 1410, the transmitter 1415, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1420, the receiver 1410, the transmitter 1415, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0195] In some examples, communication manager 1420 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1410, transmitter 1415, or both. For example, communication manager 1420 may receive information from receiver 1410, transmit information to transmitter 1415, or be integrated in conjunction with receiver 1410, transmitter 1415, or both to obtain information, output information, or perform various other operations as described herein.

[0196] According to examples as disclosed herein, the communication manager 1420 may support wireless communications at a network entity. For example, the communication manager 1420 may be configured to or otherwise support a means for sending control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates to the UE based on the DMRS configuration to avoid including the DMRS in at least a first portion of the uplink message. The communication manager 1420 may be configured to or otherwise support a means for receiving an uplink message without a DMRS in at least a first portion of the uplink message according to the DMRS configuration. The communication manager 1420 may be configured to or otherwise support a means for decoding an uplink message based on the DMRS configuration.

[0197] By including or configuring a communication manager 1420 according to the examples described herein, the device 1405 (e.g., a processor controlling or otherwise coupled to the receiver 1410, the transmitter 1415, the communication manager 1420, or a combination thereof) may support techniques for reducing bottlenecks at DMRS ports by reducing DMRS in uplink messages, which may be understood as reducing signaling overhead, reducing power consumption, and more efficiently utilizing communication resources.

[0198] Fig.15 A block diagram 1500 of a device 1505 supporting DMRS configuration for uplink messages according to one or more aspects of the present disclosure is shown. The device 1505 may be an example of aspects of the device 1405 or the network entity 105 as described herein. The device 1505 may include a receiver 1510, a transmitter 1515, and a communication manager 1520. The device 1505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0199] Receiver 1510 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 1505. In some examples, receiver 1510 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1510 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0200] The transmitter 1515 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1505. For example, the transmitter 1515 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1515 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1515 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1515 and the receiver 1510 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0201] Device 1505 or its various components may be examples of components for performing various aspects of DMRS configuration for uplink messages as described herein. For example, communication manager 1520 may include control signaling sending component 1525, uplink message receiving component 1530, decoding component 1535, or any combination thereof. Communication manager 1520 may be an example of various aspects of communication manager 1420 as described herein. In some examples, communication manager 1520 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1510, transmitter 1515, or both. For example, communication manager 1520 may receive information from receiver 1510, transmit information to transmitter 1515, or integrate with receiver 1510, transmitter 1515, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0202] According to examples as disclosed herein, the communication manager 1520 may support wireless communications at a network entity. The control signaling sending component 1525 may be configured to or otherwise support means for sending control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates to the UE based on the DMRS configuration to avoid including DMRS in at least a first portion of the uplink message. The uplink message receiving component 1530 may be configured to or otherwise support means for receiving an uplink message without DMRS in at least a first portion of the uplink message according to the DMRS configuration. The decoding component 1535 may be configured to or otherwise support means for decoding an uplink message based on the DMRS configuration.

[0203] Fig.16A block diagram 1600 of a communication manager 1620 supporting DMRS configuration for uplink messages according to one or more aspects of the present disclosure is shown. The communication manager 1620 may be an example of aspects of the communication manager 1420, the communication manager 1520, or both as described herein. The communication manager 1620 or its various components may be examples of components for performing various aspects of DMRS configuration for uplink messages as described herein. For example, the communication manager 1620 may include a control signaling transmission component 1625, an uplink message receiving component 1630, a decoding component 1635, an uplink message elimination component 1640, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), and the communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105), or any combination thereof.

[0204] According to examples as disclosed herein, the communication manager 1620 may support wireless communications at a network entity. The control signaling sending component 1625 may be configured to or otherwise support means for sending control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates to the UE based on the DMRS configuration to avoid including DMRS in at least a first portion of the uplink message. The uplink message receiving component 1630 may be configured to or otherwise support means for receiving an uplink message without DMRS in at least a first portion of the uplink message according to the DMRS configuration. The decoding component 1635 may be configured to or otherwise support means for decoding an uplink message based on the DMRS configuration.

[0205] In some examples, uplink message receiving component 1630 may be configured or otherwise support components for receiving a signal including a set of uplink messages from different UEs, wherein each uplink message in the set of uplink messages is associated with a RM code.

[0206] In some examples, to support decoding of an uplink message, decoding component 1635 may be configured to or otherwise support a means for decoding an uplink message using a corresponding RM code according to a DMRS configuration, wherein the uplink message does not include a DMRS in a first portion of the uplink message. In some examples, to support decoding of an uplink message, uplink message elimination component 1640 may be configured to or otherwise support a means for eliminating a decoded uplink message from a signal including an uplink message set according to a multi-user decoding algorithm.

[0207] In some examples, the DMRS configuration includes a field indicating an LDPC code and an RM code used by the UE to encode an uplink message. In some examples, the field is included in an uplink channel resource information element.

[0208] Fig.17 A diagram of a system 1700 including a device 1705 supporting DMRS configuration for uplink messages according to one or more aspects of the present disclosure is shown. The device 1705 may be an example of a device 1405, a device 1505, or a network entity 105 as described herein, or include components thereof. The device 1705 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communication may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1705 may include components that support output and acquisition of communications, such as a communication manager 1720, a transceiver 1710, an antenna 1715, a memory 1725, a code 1730, and a processor 1735. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1740).

[0209] The transceiver 1710 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1710 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1710 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1705 may include one or more antennas 1715, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1710 may also include a modem for: modulating a signal, providing the modulated signal for transmission (e.g., via one or more antennas 1715, via a wired transmitter), receiving the modulated signal (e.g., from one or more antennas 1715, from a wired receiver), and demodulating the signal. The transceiver 1710 or transceiver 1710 and one or more antennas 1715 or wired interfaces (where applicable) may be examples of transmitter 1415, transmitter 1515, receiver 1410, receiver 1510, or any combination thereof or components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0210] Memory 1725 may include RAM and ROM. Memory 1725 may store computer-readable, computer-executable code 1730 including instructions that, when executed by processor 1735, cause device 1705 to perform various functions described herein. Code 1730 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1730 may not be directly executable by processor 1735, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1725 may also include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0211] Processor 1735 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, processor 1735 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1735. Processor 1735 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1725) to enable device 1705 to perform various functions (e.g., various functions or tasks supporting DMRS configuration for uplink messages). For example, device 1705 or a component of device 1705 may include processor 1735 and memory 1725 coupled to processor 1735, and processor 1735 and memory 1725 are configured to perform various functions described herein. Processor 1735 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functionality for performing functions of device 1705 (e.g., by executing code 1730).

[0212] In some examples, bus 1740 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1740 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1705, or communications performed between different components of device 1705 that may be co-located or may be located in different locations (e.g., where device 1705 may refer to a system in which one or more of communication manager 1720, transceiver 1710, memory 1725, code 1730, and processor 1735 may be located in one of the different components or divided between the different components).

[0213] In some examples, communication manager 1720 may manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1720 may manage delivery of data communications for client devices such as one or more UEs 115. In some examples, communication manager 1720 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with UE 115 in collaboration with other network entities 105. In some examples, communication manager 1720 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0214] According to examples as disclosed herein, the communication manager 1720 may support wireless communications at a network entity. For example, the communication manager 1720 may be configured to or otherwise support a means for sending control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates to the UE based on the DMRS configuration to avoid including DMRS in at least a first portion of the uplink message. The communication manager 1720 may be configured to or otherwise support a means for receiving an uplink message without DMRS in at least a first portion of the uplink message according to the DMRS configuration. The communication manager 1720 may be configured to or otherwise support a means for decoding an uplink message based on the DMRS configuration.

[0215] By including or configuring a communication manager 1720 according to the examples described herein, the device 1705 can support technology for reducing bottlenecks at DMRS ports by reducing DMRS in uplink messages, which can be understood as reducing signaling overhead, reducing power consumption, improving coordination between devices, extending battery life, improving utilization of processing power, and more efficient utilization of communication resources.

[0216] In some examples, the communication manager 1720 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1710, one or more antennas 1715 (e.g., where applicable), or any combination thereof. Although the communication manager 1720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1720 may be supported or performed by the processor 1735, the memory 1725, the code 1730, the transceiver 1710, or any combination thereof. For example, the code 1730 may include instructions that are executable by the processor 1735 to cause the device 1705 to perform various aspects of DMRS configuration for uplink messages as described herein, or the processor 1735 and the memory 1725 may be otherwise configured to perform or support such operations.

[0217] Fig.18 A flowchart illustrating a method 1800 for supporting DMRS configuration for uplink messages according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 13 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0218] At 1805, the method may include: receiving control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates to the UE based on the DMRS configuration to avoid including DMRS in at least a first portion of the uplink message. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.12 The control signaling receiving component 1225 described is executed.

[0219] At 1810, the method may include encoding an uplink message without a DMRS in at least a first portion of the uplink message according to the DMRS configuration. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Fig.12 The described encoding component 1230 is performed.

[0220] At 1815, the method may include sending the uplink message based on encoding the uplink message. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Fig.12 The described uplink message sending component 1235 is performed.

[0221] Fig.19 A flowchart illustrating a method 1900 for supporting DMRS configuration for uplink messages according to one or more aspects of the present disclosure is shown. The operations of the method 1900 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1900 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 13 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0222] At 1905, the method may include: receiving control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates to the UE based on the DMRS configuration to avoid including DMRS in at least a first portion of the uplink message. The operations of 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed as described in reference to Fig.12 The control signaling receiving component 1225 described is executed.

[0223] At 1910, the method may include: receiving a means for indicating whether the UE is to include a DMRS in a second part of the uplink message on a frequency bandwidth covered by a RACH of the uplink message, wherein the RACH is included in a first part of the uplink message. The operations of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed as described in reference to Fig.12 The control signaling receiving component 1225 described is executed.

[0224] At 1915, the method may include encoding an uplink message without a DMRS in at least a first portion of the uplink message according to the DMRS configuration. The operations of 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed as described in reference to Fig.12 The described encoding component 1230 is performed.

[0225] At 1920, the method may include sending an uplink message based on encoding the uplink message. The operations of 1920 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1920 may be performed as described in reference to Fig.12 The described uplink message sending component 1235 is performed.

[0226] Fig. 20 A flowchart illustrating a method 2000 for supporting DMRS configuration for uplink messages according to one or more aspects of the present disclosure is shown. The operations of the method 2000 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2000 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 9 as well as Figures 14 to 17 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0227] At 2005, the method may include: sending control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates to the UE based on the DMRS configuration to avoid including DMRS in at least a first portion of the uplink message. The operations of 2005 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2005 may be performed as described in reference to Fig.16 The described control signaling sending component 1625 executes.

[0228] At 2010, the method may include: receiving an uplink message without a DMRS in at least a first portion of the uplink message according to the DMRS configuration. The operations of 2010 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed as described in reference to Fig.16 The described uplink message receiving component 1630 is performed.

[0229] At 2015, the method may include: decoding an uplink message based on the DMRS configuration. The operations of 2015 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2015 may be performed as described in reference to Fig.16 The described decoding component 1635 is performed.

[0230] Fig.21 A flowchart illustrating a method 2100 for supporting DMRS configuration for uplink messages according to one or more aspects of the present disclosure is shown. The operations of the method 2100 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2100 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 9 as well as Figures 14 to 17 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0231] At 2105, the method may include: sending control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates to the UE based on the DMRS configuration to avoid including DMRS in at least a first portion of the uplink message. The operations of 2105 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2105 may be performed as described in reference to Fig.16 The described control signaling sending component 1625 executes.

[0232] At 2110, the method may include receiving an uplink message without a DMRS in at least a first portion of the uplink message according to the DMRS configuration. The operations of 2110 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2110 may be performed as described in reference to Fig.16 The described uplink message receiving component 1630 is performed.

[0233] At 2115, the method may include: receiving a signal including an uplink message set from a different UE, wherein each uplink message in the uplink message set is associated with an RM code. The operations of 2115 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 2115 may be performed as described in reference to Fig.16 The described uplink message receiving component 1630 is performed.

[0234] At 2120, the method may include decoding an uplink message based on the DMRS configuration. The operations of 2120 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2120 may be performed as described in reference to Fig.16 The described decoding component 1635 is performed.

[0235] The following provides an overview of various aspects of the disclosure:

[0236] Aspect 1: A method for performing wireless communications at a UE, the method comprising: receiving control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates to the UE to avoid including the DMRS in at least a first part of the uplink message based at least in part on the DMRS configuration; encoding the uplink message without the DMRS in at least the first part of the uplink message according to the DMRS configuration; and sending the uplink message based at least in part on encoding the uplink message.

[0237] Aspect 2: The method according to aspect 1, wherein encoding the uplink message further comprises: encoding the uplink message not including the DMRS in the first part using an RM code according to the DMRS configuration.

[0238] Aspect 3: The method according to any one of aspects 1 to 2, wherein the DMRS configuration includes a field indicating that the UE is to avoid including the DMRS in the first part of the uplink message.

[0239] Aspect 4: A method according to any one of Aspects 1 to 3, wherein the DMRS configuration includes a field indicating a low-density parity-check code and an RM code used by the UE to encode the uplink message, and the field is included in an uplink channel resource information element.

[0240] Aspect 5: According to the method described in any one of Aspects 1 to 4, the method further includes: selecting a PRACH preamble code to be included in the uplink message; and generating the scrambling identifier based at least in part on the PRACH preamble code, or based on RRC signaling indicating a scrambling identifier associated with the UE, or based on both, wherein encoding the uplink message is at least in part based on the scrambling identifier.

[0241] Aspect 6: A method according to any one of Aspects 1 to 5, wherein receiving the DMRS configuration further includes: receiving an indication of whether the UE is to include the DMRS in the second part of the uplink message on the frequency bandwidth covered by the random access channel of the uplink message, wherein the random access channel is included in the first part of the uplink message.

[0242] Aspect 7: A method according to Aspect 6, wherein receiving the indication further includes: receiving a first configuration, wherein the first configuration indicates that the UE includes one or more demodulation reference signals in each frequency resource of the frequency bandwidth covered by the random access channel; receiving a second configuration, wherein the second configuration indicates that the UE includes the one or more demodulation reference signals in a subset of the frequency resources of the frequency bandwidth covered by the random access channel; or receiving a third configuration, wherein the third configuration indicates that the UE avoids including the demodulation reference signal in the second part of the uplink message.

[0243] Aspect 8: The method according to any one of aspects 1 to 7, wherein receiving the DMRS configuration includes: receiving an indication of a PRACH comb pattern to be applied to the first part of the uplink message.

[0244] Aspect 9: The method according to any one of Aspects 1 to 8, wherein encoding the uplink message further comprises: encoding the uplink message without the DMRS in any part of the uplink message according to the DMRS configuration.

[0245] Aspect 10: The method according to any one of aspects 1 to 9, wherein encoding the uplink message further comprises: encoding the first part of the uplink message according to a PRACH comb pattern based at least in part on the DMRS configuration.

[0246] Aspect 11: The method according to any one of Aspects 1 to 10, wherein encoding the uplink message further comprises: encoding the uplink message according to the DMRS configuration to include one or more DMRSs in the second part of the uplink message.

[0247] Aspect 12: The method according to Aspect 11, wherein encoding the uplink message further comprises: encoding the second part of the uplink message according to the DMRS configuration to include the one or more DMRSs at the beginning or end of the second part.

[0248] Aspect 13: A method according to any one of Aspects 11 to 12, wherein encoding the uplink message further comprises: encoding the second part of the uplink message according to the DMRS configuration to include the one or more DMRSs in a frequency resource set that does not have a random access channel signal.

[0249] Aspect 14: A method according to any one of Aspects 11 to 13, wherein encoding the uplink message further comprises: encoding the second part of the uplink message at least partially based on the DMRS configuration to include the one or more DMRSs in a frequency resource set, and the frequency resource set includes a random access channel signal in the first part.

[0250] Aspect 15: The method according to any one of aspects 1 to 14, wherein the DMRS configuration is based at least in part on an amount of Doppler spread at the UE.

[0251] Aspect 16: A method according to any one of Aspects 1 to 15, wherein sending the uplink message further comprises: sending PRACH in a first frequency resource set in the first part of the uplink message according to the DMRS configuration; and sending an uplink shared channel in a second frequency resource set in the second part of the uplink message according to the DMRS configuration, wherein the first frequency resource set and the second frequency resource set include the same frequency resource set or a subset of the same frequency resources.

[0252] Aspect 17: The method according to aspect 16, wherein the DMRS configuration includes the second set of frequency resources based at least in part on the first set of frequency resources.

[0253] Aspect 18: The method according to any one of aspects 16 to 17, wherein the DMRS configuration is based at least in part on the second set of frequency resources including the first set of frequency resources.

[0254] Aspect 19: The method according to any one of aspects 1 to 18, wherein receiving the control signaling further comprises: receiving an RRC message including the DMRS configuration for the uplink message.

[0255] Aspect 20: A method for performing wireless communications at a network entity, the method comprising: sending control signaling indicating a DMRS configuration for an uplink message, wherein the control signaling further indicates to a UE at least in part based on the DMRS configuration to avoid including the DMRS in at least a first part of the uplink message; receiving the uplink message without the DMRS in at least the first part of the uplink message according to the DMRS configuration; and decoding the uplink message at least in part based on the DMRS configuration.

[0256] Aspect 21: The method according to aspect 20, the method further comprising: receiving a signal including an uplink message set from different UEs, wherein each uplink message in the uplink message set is associated with an RM code.

[0257] Aspect 22: A method according to Aspect 21, wherein decoding the uplink message further comprises: decoding the uplink message using a corresponding RM code according to the DMRS configuration, wherein the uplink message does not include the DMRS in the first part of the uplink message; and eliminating the decoded uplink message from the signal including the uplink message set according to a multi-user decoding algorithm.

[0258] Aspect 23: A method according to any one of Aspects 20 to 22, wherein the DMRS configuration includes a field indicating a low-density parity-check code and an RM code for the UE to encode the uplink message, and the field is included in an uplink channel resource information element.

[0259] Aspect 24: An apparatus for performing wireless communications at a UE, the apparatus 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 according to any one of Aspects 1 to 19.

[0260] Aspect 25: An apparatus for wireless communication at a UE, the apparatus comprising: at least one component for performing the method according to any one of aspects 1 to 19.

[0261] Aspect 26: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 19.

[0262] Aspect 27: An apparatus for wireless communication at a network entity, the apparatus 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 according to any one of Aspects 20 to 23.

[0263] Aspect 28: An apparatus for wireless communication at a network entity, the apparatus comprising at least one means for performing the method according to any one of aspects 20 to 23.

[0264] Aspect 29: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 20 to 23.

[0265] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and other implementations are possible. In addition, aspects from two or more methods may be combined.

[0266] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0267] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0268] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0269] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium, or sent via a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0270] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to be transmitted from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code components and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0271] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0272] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), etc. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0273] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second or other subsequent reference labels.

[0274] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The specific implementation includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0275] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), the method comprising: receiving control signaling indicating a demodulation reference signal configuration for an uplink message, wherein the control signaling further indicates, based at least in part on the demodulation reference signal configuration, that the UE is to avoid including a demodulation reference signal in at least a first portion of the uplink message; encoding the uplink message without the demodulation reference signal in at least the first part of the uplink message according to the demodulation reference signal configuration; as well as The uplink message is sent based at least in part on encoding the uplink message.

2. The method of claim 1 , wherein encoding the uplink message further comprises: The uplink message not including the demodulation reference signal in the first part is encoded using a Reed-Muller code according to the demodulation reference signal configuration.

3. The method of claim 1, wherein the demodulation reference signal configuration comprises a field indicating that the UE is to avoid including the demodulation reference signal in the first part of the uplink message.

4. The method of claim 1, wherein the demodulation reference signal configuration comprises a field indicating a low density parity check code and a Reed-Muller code used by the UE to encode the uplink message, wherein the field is included in an uplink channel resource information element.

5. The method according to claim 1, further comprising: selecting a physical random access channel preamble to include in the uplink message; as well as The scrambling identity is generated based at least in part on the physical random access channel preamble, based on radio resource control signaling indicating a scrambling identity associated with the UE, or based on both, wherein encoding the uplink message is based at least in part on the scrambling identity.

6. The method of claim 1 , wherein receiving the demodulation reference signal configuration further comprises: An indication of whether the UE is to include the demodulation reference signal in a second part of the uplink message is received over a frequency bandwidth covered by a random access channel of the uplink message, wherein the random access channel is included in the first part of the uplink message.

7. The method of claim 6, wherein receiving the indication further comprises: receiving a first configuration, the first configuration instructing the UE to include one or more demodulation reference signals in each frequency resource of the frequency bandwidth covered by the random access channel; receiving a second configuration, the second configuration instructing the UE to include the one or more demodulation reference signals in a subset of frequency resources of the frequency bandwidth covered by the random access channel; or A third configuration is received, the third configuration instructing the UE to avoid including a demodulation reference signal in the second part of the uplink message.

8. The method of claim 1 , wherein receiving the demodulation reference signal configuration comprises: An indication of a physical random access channel comb pattern to be applied to the first portion of the uplink message is received.

9. The method of claim 1, wherein encoding the uplink message further comprises: The uplink message is encoded according to the demodulation reference signal configuration without the demodulation reference signal in any part of the uplink message.

10. The method of claim 1, wherein encoding the uplink message further comprises: Based at least in part on the demodulation reference signal configuration, the first portion of the uplink message is encoded according to a physical random access channel comb pattern.

11. The method of claim 1 , wherein encoding the uplink message further comprises: The uplink message is encoded according to the demodulation reference signal configuration to include one or more demodulation reference signals in a second portion of the uplink message.

12. The method of claim 11, wherein encoding the uplink message further comprises: The second portion of the uplink message is encoded according to the demodulation reference signal configuration to include the one or more demodulation reference signals at the beginning or the end of the second portion.

13. The method of claim 11, wherein encoding the uplink message further comprises: The second portion of the uplink message is encoded according to the demodulation reference signal configuration to include the one or more demodulation reference signals in a set of frequency resources without random access channel signals.

14. The method of claim 11, wherein encoding the uplink message further comprises: The second portion of the uplink message is encoded based at least in part on the demodulation reference signal configuration to include the one or more demodulation reference signals in a set of frequency resources that include a random access channel signal in the first portion.

15. The method of claim 1, wherein the demodulation reference signal configuration is based at least in part on an amount of Doppler spread at the UE.

16. The method of claim 1, wherein sending the uplink message further comprises: sending a physical random access channel in a first set of frequency resources in the first part of the uplink message according to the demodulation reference signal configuration; as well as An uplink shared channel is sent in a second set of frequency resources in a second part of the uplink message according to the demodulation reference signal configuration, wherein the first set of frequency resources and the second set of frequency resources comprise the same set of frequency resources or a subset of the same frequency resources.

17. The method of claim 16, wherein the demodulation reference signal configuration includes the second set of frequency resources based at least in part on the first set of frequency resources.

18. The method of claim 16, wherein the demodulation reference signal configuration is based at least in part on the second set of frequency resources including the first set of frequency resources.

19. The method of claim 1, wherein receiving the control signaling further comprises: A radio resource control message is received that includes the demodulation reference signal configuration for the uplink message.

20. A method for wireless communication at a network entity, the method comprising: transmitting control signaling indicating a demodulation reference signal configuration for an uplink message, wherein the control signaling further indicates to a user equipment (UE) to avoid including a demodulation reference signal in at least a first portion of the uplink message based at least in part on the demodulation reference signal configuration; receiving the uplink message without the demodulation reference signal in at least the first part of the uplink message according to the demodulation reference signal configuration; as well as The uplink message is decoded based at least in part on the demodulation reference signal configuration.

21. The method according to claim 20, further comprising: A signal including a set of uplink messages is received from different UEs, wherein each uplink message in the set of uplink messages is associated with a Reed-Muller code.

22. The method of claim 21, wherein decoding the uplink message further comprises: decoding the uplink message using a corresponding Reed-Muller code according to the demodulation reference signal configuration, wherein the uplink message does not include the demodulation reference signal in the first part of the uplink message; as well as The decoded uplink message is eliminated from the signal including the set of uplink messages according to a multi-user decoding algorithm.

23. The method of claim 20, wherein the demodulation reference signal configuration comprises a field indicating a low density parity check code and a Reed-Muller code used by the UE to encode the uplink message, wherein the field is included in an uplink channel resource information element.

24. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving control signaling indicating a demodulation reference signal configuration for an uplink message, wherein the control signaling further indicates, based at least in part on the demodulation reference signal configuration, that the UE is to avoid including a demodulation reference signal in at least a first portion of the uplink message; encoding the uplink message without the demodulation reference signal in at least the first part of the uplink message according to the demodulation reference signal configuration; as well as The uplink message is sent based at least in part on encoding the uplink message.

25. The apparatus of claim 24, wherein the instructions for encoding the uplink message are further executable by the processor to cause the apparatus to: The uplink message not including the demodulation reference signal in the first part is encoded using a Reed-Muller code according to the demodulation reference signal configuration.

26. The apparatus of claim 24, wherein the demodulation reference signal configuration comprises a field indicating that the UE is to avoid including the demodulation reference signal in the first part of the uplink message.

27. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: transmitting control signaling indicating a demodulation reference signal configuration for an uplink message, wherein the control signaling further indicates to a user equipment (UE) to avoid including a demodulation reference signal in at least a first portion of the uplink message based at least in part on the demodulation reference signal configuration; receiving the uplink message without the demodulation reference signal in at least the first part of the uplink message according to the demodulation reference signal configuration; as well as The uplink message is decoded based at least in part on the demodulation reference signal configuration.

28. The apparatus of claim 27, wherein the instructions are further executable by the processor to cause the apparatus to: A signal including a set of uplink messages is received from different UEs, wherein each uplink message in the set of uplink messages is associated with a Reed-Muller code.

29. The apparatus of claim 28, wherein the instructions for decoding the uplink message are further executable by the processor to cause the apparatus to: decoding the uplink message using a corresponding Reed-Muller code according to the demodulation reference signal configuration, wherein the uplink message does not include the demodulation reference signal in the first part of the uplink message; and The decoded uplink message is eliminated from the signal including the set of uplink messages according to a multi-user decoding algorithm.

30. The apparatus of claim 27, wherein the demodulation reference signal configuration comprises a field indicating a low density parity check code and a Reed-Muller code used by the UE to encode the uplink message, wherein the field is included in an uplink channel resource information element.

Images