Frequency domain multiplexing of demodulation reference signals

Abstract

Methods, systems, and apparatus for wireless communication are described. The techniques described herein relate to Frequency Division Multiplexing (FDM) of a Demodulation Reference Signal (DMRS). A User Equipment (UE) receives control signaling including configuration for uplink control messages. The UE generates uplink control messages based on the configuration and a first uplink control message format from multiple formats. The uplink control message includes a DMRS in FDM with uplink control information (UCI). The first uplink control message format is associated with a Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveform and the number of four or more OFDM symbols. The UE uses the DFT-s-OFDM waveform to transmit the uplink control messages.

Description

Cross-references

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 542,345, filed December 15, 2023, entitled “FREQUENCYDOMAIN MULTIPLEXING OF DEMODULATION REFERENCE SIGNAL”, which is assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety. Technical Field

[0002] The following discussion pertains to wireless communication, including frequency domain multiplexing of demodulation reference signals. Background Technology

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can 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, LTE-A Advanced (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 technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE).

[0004] Some wireless communication systems support multiple formats for Physical Uplink Control Channel (PUCCH) messages from User Equipment (UE). These formats can be classified based on physical resource allocation, including the length of Orthogonal Frequency Division Multiplexing (OFDM) symbols or the number of bits carried in the PUCCH message. Formats associated with fewer than four OFDM symbols (such as one to two OFDM symbols) can be referred to as “short” format PUCCH messages, and formats associated with at least four OFDM symbols (such as four to fourteen OFDM symbols) can be referred to as “long” format PUCCH messages. Long format PUCCH messages (such as large format PUCCH messages with Time Division Multiplexing (TDM) DMRS) can be associated with high overhead. Summary of the Invention

[0005] The described technology relates to improved methods, systems, devices, and apparatuses for frequency division multiplexing (FDM) supporting demodulation reference signals (DMRS). For a PUCCH message associated with at least four orthogonal frequency division multiplexing (OFDM) symbols (“long” format PUCCH message), DMRS and uplink control information (UCI) can be multiplexed in the frequency domain. The long format PUCCH message may have a Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveform. FDM DMRS and UCI can reduce DMRS overhead while maintaining the peak-to-average power ratio (PAPR) of the long format PUCCH message's DFT-s-OFDM (e.g., below a threshold PAPR). For a long format PUCCH message with a DFT-s-OFDM waveform, the DMRS multiplexing mode can be switched from time division multiplexing (TDM) to FDM. The signaling indicating the switch from TDM to FDM can be dynamic, semi-static, or static. The signaling can be based on attributes such as: the DMRS density in the frequency domain, the number of configured FDM DMRS symbols (e.g., symbols where UCI performs FDM with DMRS), or the type of DMRS demodulation sequence.

[0006] A method for wireless communication by a UE is described. The method may include: receiving control signaling including a configuration for an uplink control message; generating the uplink control message according to the configuration and a first uplink control message format from a set of multiple uplink control message formats, wherein the uplink control message includes a DMRS for FDM with UCI, and wherein the first uplink control message format is associated with a DFT-s-OFDM waveform and a number of four or more OFDM symbols; and transmitting the uplink control message using the DFT-s-OFDM waveform.

[0007] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code so that the UE: receives control signaling including a configuration for uplink control messages; generates the uplink control message according to the configuration and a first uplink control message format from a set of multiple uplink control message formats, wherein the uplink control message includes a DMRS with UCI FDM, and wherein the first uplink control message format is associated with a DFT-s-OFDM waveform and a number of four or more OFDM symbols; and transmits the uplink control message using the DFT-s-OFDM waveform.

[0008] Another UE for wireless communication is described. The UE may include: components for receiving control signaling including a configuration for an uplink control message; components for generating the uplink control message according to the configuration and a first uplink control message format from a set of multiple uplink control message formats, wherein the uplink control message includes a DMRS with FDM with UCI, and wherein the first uplink control message format is associated with a DFT-s-OFDM waveform and a number of four or more OFDM symbols; and components for transmitting the uplink control message using the DFT-s-OFDM waveform.

[0009] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive control signaling including a configuration for an uplink control message; generate the uplink control message according to the configuration and a first uplink control message format from a set of multiple uplink control message formats, wherein the uplink control message includes a DMRS for FDM with UCI, and wherein the first uplink control message format is associated with a DFT-s-OFDM waveform and a number of four or more OFDM symbols; and transmit the uplink control message using the DFT-s-OFDM waveform.

[0010] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the control signaling includes an indication of switching from TDM to FDM based on the first uplink control message format.

[0011] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the indication for handover includes dynamic indication, semi-static indication, or static indication.

[0012] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, the control signaling includes radio resource control signaling.

[0013] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, frequency division multiplexing of the DMRS with the UCI may be based on the type of demodulation sequence associated with the DMRS.

[0014] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, this type of demodulation sequence may be associated with the root index associated with the DMRS.

[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, frequency division multiplexing of the DMRS with the UCI can be based on the DMRS density in the frequency domain.

[0016] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, frequency division multiplexing of the DMRS with the UCI can be based on the number of DMRS symbols that can be FDMed with the UCI in a time slot.

[0017] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for generating a sidelink message that includes FDM with sidelink control information in a DMRS; and sending the sidelink message to a second UE.

[0018] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, a second uplink control message format in this set of multiple uplink control message formats may be associated with a CP-OFDM waveform and the number of two or fewer OFDM symbols.

[0019] A method for wireless communication by a network entity is described. The method may include: outputting control signaling including a configuration for an uplink control message; obtaining the uplink control message based on the configuration and a first uplink control message format from a set of multiple uplink control message formats, wherein the uplink control message includes a DMRS with UCI for FDM, and wherein the first uplink control message format is associated with a DFT-s-OFDM waveform and a number of four or more OFDM symbols; and decoding the uplink control message based on the configuration.

[0020] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code so that the network entity: outputs control signaling including a configuration for uplink control messages; obtains the uplink control messages according to the configuration and a first uplink control message format from a set of multiple uplink control message formats, wherein the uplink control messages include DMRS with UCI FDM, and wherein the first uplink control message format is associated with a DFT-s-OFDM waveform and a number of four or more OFDM symbols; and decodes the uplink control messages based on the configuration.

[0021] Another network entity for wireless communication is described. This network entity may include: components for outputting control signaling including a configuration for uplink control messages; components for obtaining the uplink control message based on the configuration and a first uplink control message format from a set of multiple uplink control message formats, wherein the uplink control message includes DMRS with UCI FDM, and wherein the first uplink control message format is associated with a DFT-s-OFDM waveform and a number of four or more OFDM symbols; and components for decoding the uplink control message based on the configuration.

[0022] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: output control signaling including a configuration for an uplink control message; obtain the uplink control message according to the configuration and a first uplink control message format from a set of multiple uplink control message formats, wherein the uplink control message includes a DMRS for FDM with UCI, and wherein the first uplink control message format is associated with a DFT-s-OFDM waveform and a number of four or more OFDM symbols; and decode the uplink control message based on the configuration.

[0023] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting downlink control messages, which include DMRS with downlink control information in FDM, wherein the downlink control messages utilize DFT-s-OFDM waveforms.

[0024] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the control signaling includes an indication to switch from TDM to FDM based on the first uplink control message format.

[0025] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the indication for switching includes dynamic, semi-static, or static indications.

[0026] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the control signaling includes radio resource control signaling.

[0027] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, frequency division multiplexing of the DMRS with the UCI may be based on the type of demodulation sequence associated with the DMRS.

[0028] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, this type of demodulation sequence may be associated with the root index associated with the DMRS.

[0029] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, frequency division multiplexing of the DMRS with the UCI can be based on the DMRS density in the frequency domain.

[0030] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, frequency division multiplexing of the DMRS with the UCI can be based on the number of DMRS symbols that can be FDMed with the UCI in a time slot.

[0031] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a second uplink control message format in this set of multiple uplink control message formats may be associated with a CP-OFDM waveform and the number of two or fewer OFDM symbols. Attached Figure Description

[0032] Figure 1 An example of a wireless communication system supporting frequency domain multiplexing of a demodulated reference signal according to one or more aspects of this disclosure is shown.

[0033] Figure 2 An example of a wireless communication system supporting frequency domain multiplexing of a demodulated reference signal according to one or more aspects of this disclosure is shown.

[0034] Figure 3 An example of a process flow for frequency domain multiplexing of a demodulated reference signal according to one or more aspects of this disclosure is shown.

[0035] Figure 4 and Figure 5 A block diagram of an apparatus for frequency domain multiplexing of a demodulated reference signal according to one or more aspects of this disclosure is shown.

[0036] Figure 6 A block diagram of a communication manager supporting frequency domain multiplexing of a demodulated reference signal according to one or more aspects of this disclosure is shown.

[0037] Figure 7 A diagram of a system including a device for frequency domain multiplexing supporting demodulation reference signals, according to one or more aspects of this disclosure, is shown.

[0038] Figure 8 and Figure 9 A block diagram of an apparatus for frequency domain multiplexing of a demodulated reference signal according to one or more aspects of this disclosure is shown.

[0039] Figure 10 A block diagram of a communication manager supporting frequency domain multiplexing of a demodulated reference signal according to one or more aspects of this disclosure is shown.

[0040] Figure 11 A diagram of a system including a device for frequency domain multiplexing supporting demodulation reference signals, according to one or more aspects of this disclosure, is shown.

[0041] Figures 12 to 15 A flowchart illustrating a method for frequency domain multiplexing of a demodulated reference signal according to one or more aspects of this disclosure is shown. Detailed Implementation

[0042] Some wireless communication systems support multiple formats for Physical Uplink Control Channel (PUCCH) messages from User Equipment (UE). These formats can be categorized based on physical resource allocation, including the length of Orthogonal Frequency Division Multiplexing (OFDM) symbols or the number of bits carried in the PUCCH message. As described herein, a PUCCH message format associated with fewer than four OFDM symbols (such as one to two OFDM symbols) can be referred to as a “short” format PUCCH message. A format associated with four or more OFDM symbols (such as four to fourteen OFDM symbols) can be referred to as a “long” format PUCCH message. A long format PUCCH message may include a demodulation reference signal (DMRS) multiplexed with uplink control information (UCI) in the time domain (e.g., time division multiplexing (TDM)), while a short format PUCCH message may include a DMRS multiplexed with UCI in the frequency domain (e.g., frequency division multiplexing (FDM)). However, long-format PUCCH messages (such as large-format PUCCH messages with TDM DMRS) can be associated with high overhead. High overhead can lead to a reduction in the number of UCIs that can be included in long-format PUCCH messages.

[0043] For long-format PUCCHs with Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveforms, DMRS and UCI can be multiplexed in the frequency domain (e.g., FDM). FDMing of DMRS and UCI reduces DMRS overhead while maintaining the peak-to-average power ratio (PAPR) of the long-format PUCCH's DFT-s-OFDM waveform (e.g., below a threshold PAPR). For long PUCCH formats with DFT-s-OFDM waveforms, the DMRS multiplexing mode can switch from TDM to FDM. The signaling indicating the switch from TDM to FDM can be dynamic, semi-static, or static. This signaling can be based on attributes such as: the DMRS density in the frequency domain, the number of configured FDM DMRS symbols (e.g., symbols where UCI and DMRS are FDMed), or the type of DMRS demodulation sequence.

[0044] The aspects of this disclosure are first described in the context of wireless communication systems. These aspects are further illustrated by apparatus diagrams, system diagrams, and flowcharts relating to FDM in relation to DMRS, and are further described with reference to these diagrams.

[0045] Figure 1 An example of an FDM wireless communication system 100 supporting DMRS according to one or more aspects of this disclosure is shown. 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 under other systems and radio technologies including future systems and radio technologies not explicitly mentioned herein.

[0046] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0047] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0048] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or 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, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. As another example, a node may be 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 UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

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

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

[0051] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across 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, 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, a non-real-time RIC), a service management and orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0052] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can 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 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can 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 each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed 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 can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0053] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can 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 node 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 DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with 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 node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, 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 IAB node 104) may be configured to operate according to the techniques described herein.

[0054] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support FDM as described herein for DMRS. 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).

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

[0056] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0057] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating 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 coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured using multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0058] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0059] The communication link 125 shown in the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0060] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a particular radio access technology (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one of the carrier bandwidths in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0061] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and 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 decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal 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.

[0062] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0063] 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 (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a 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 number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

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

[0065] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can 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 set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0066] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to 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 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0067] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timings, and transmissions from different network entities 105 can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timings, and in some examples, transmissions from different network entities 105 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0068] Some UE 115s (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115s may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0069] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115s include entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0070] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private 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 prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

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

[0072] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or a combination of these. Vehicles may signal information related to traffic conditions, signal control, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0073] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can 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), 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), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be transferred through user plane entities, which provide IP address allocation and other functions. User plane entities can connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0074] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately 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 are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0075] The wireless communication system 100 can also operate in the Ultra High Frequency (SHF) band (also known as the centimeter band) in the range of 3 GHz to 30 GHz or in the Extremely High Frequency (EHF) band (e.g., 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmissions, EHF transmissions may experience even greater attenuation and shorter range. The techniques disclosed herein can be adopted across transmissions using one or more different frequency bands, and the frequency band usage specified across these frequency bands may vary by country or regulatory authority.

[0076] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed bands may be combined with component carriers operating with licensed bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0077] 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 techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation 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, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0078] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0079] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0080] The wireless communication system 100 may be a 5G NR system supporting multiple formats for PUCCH messages from UE 115, wherein the format of the PUCCH message may be based on the UCI payload (e.g., the number of bits carried by the PUCCH message), physical resource allocation including the length of OFDM symbols, the number of physical resource blocks (PRBs), or any combination thereof. For example, the format may include the following:

[0081] For example, formats associated with fewer than four OFDM symbols (such as one to two OFDM symbols) can be referred to as “short” format PUCCH messages, and formats associated with at least four OFDM symbols (such as four to fourteen OFDM symbols) can be referred to as “long” format PUCCH messages. Therefore, formats 0 and 2 can be referred to as short format PUCCH messages, and formats 1, 3, and 4 can be referred to as long format PUCCH messages. Short format PUCCH messages can be based on a cyclic prefix (CP) OFDM (CP-OFDM) waveform with FDM DMRS and UCI. Short format PUCCH messages can have less than 50% DMRS density in an OFDM symbol. Long format PUCCH messages can be based on a DFT-s-OFDM waveform with TDM DMRS (e.g., for coverage enhancement) and UCI with more than 50% DMRS in a time slot. UCI can be based on binary phase shift keying (BPSK) modulation (e.g., π / 2 BPSK) or quadrature phase shift keying (QPSK) modulation.

[0082] As discussed herein, long-format PUCCH messages with DFT-s-OFDM can include FDM DMRS and UCI. DFT-s-OFDM waveforms enable multiplexing in the frequency domain, but can also be associated with PAPR loss (e.g., PAPR cost). In some examples, such as long-format PUCCH messages with high DMRS overhead, reducing DMRS overhead can allow the PUCCH message to carry more UCI. For example, the TDM DMRS overhead for PUCCH message format 3 can be less than 50%. To reduce DMRS overhead on long-format PUCCH messages (such as format 3), DMRS can be FDMed with UCI without reducing PAPR below a PAPR threshold, so that channel estimation may not be affected below the performance threshold. In some examples, such as high-Doppler scenarios, DMRS overhead can be reduced. In such examples, dedicated DMRS symbols (i.e., TDM DMRS and data) can be configured. However, DMRS overhead can be further reduced by FDMing DMRS and UCI for long-format PUCCH messages. Furthermore, FDM of DMRS and UCI can lead to better rate matching (i.e., more decoding gain) and can reduce block error rate (BLER) performance (e.g., end-to-end BLER performance).

[0083] Figure 2 An example of a DMRS-enabled FDM wireless communication system 200 according to one or more aspects of this disclosure is shown. The wireless communication system 200 may implement, or be implemented by, aspects of the wireless communication system 100. For example, the wireless communication system 200 includes a UE 115-a and a network entity 105-a, which may be related to... Figure 1 Examples of UE 115 and network entity 105 described.

[0084] In some examples, UE 115-a can perform various processes to provide FDM / DMRS with UCI in DFT-s-OFDM. For example, the processing blockchain for FDM with DMRS and UCI in UE 115-a may include the following.

[0085] Blockchain can involve multiple inputs, outputs, and functions (e.g., the number of subcarriers). N ), data subcarrier ( N d ), pilot tone ( N p ) and the number of available OFDM symbols or sequences ( M It includes UCI data, serial-to-parallel (S / P) function, DFT function, DMRS data, frequency mapping between data and reference signal (RS), subcarrier mapping, N-point inverse fast Fourier transform (IFFT) function, parallel-to-serial (P / S) function, and cyclic prefix function (CP+).

[0086] In some examples, FDM may not affect the PAPR of the DFT, resulting in a PAPR below a threshold PAPR. For instance, the normalized squared amplitude of an FDM signal may be affected by the root index of the Zadoff-Chu (ZC) sequence and the density of the DMRS in the frequency domain. In such examples, when a QPSK-modulated UCI is FDMed with ZC DMRS having a specific root index, the PAPR performance may be... The complementary cumulative distribution function (CCDF) points are the same. When the QPSK modulated UCI is subjected to FDM with a frequency domain ZCDMRS having 50% density in the frequency domain, the PAPR loss can be Average decibels (dB). For example, the loss of PAPR compared to TDM can be compensated by the better decoding gain provided by FDM. In some examples, a power-boosted TDM DMRS tone can have similar results to an unpower-boosted FDM DMRS tone, thus indicating that the PAPR loss is still below the threshold PAPR.

[0087] In the wireless communication system 200, UE 115-a can transmit FDM DMRS with UCI to network entity 105-a. For example, network entity 105-a can communicate with UE 115-a using communication link 125. In some examples, communication link 125 may include a first channel 225-a for transmitting data from UE 115-a to network entity 105-a and a second channel 225-b for transmitting data from network entity 105-a to UE 115-a. Communication link 125 may be an example of an NR or LTE link between UE 115-a and network entity 105-a. Communication link 125 may include a bidirectional link, which, for example, enables both uplink and downlink communication via channel 225.

[0088] UE 115-a may use (e.g., communication link 125) a first channel 225-a to send uplink messages 245 (e.g., uplink transmissions), such as uplink control signals or uplink data signals, to network entity 105-a, and network entity 105-a may use (e.g., communication link 125) a second channel 225-b to send downlink messages 250 (e.g., downlink transmissions), such as downlink control signals or downlink data signals, to UE 115-a. In some examples, downlink message 250 may be part of control signaling sent from network entity 105-a.

[0089] Network entity 105-a may send downlink message 250, which may include configuration for uplink message 245. This configuration may instruct UE 115-a to switch from TDM to FDM based on the uplink message format. For example, if uplink message 245 is a long-format PUCCH message, UE 115-a may use FDM to switch or continue. Long-format PUCCH messages may include formats 1, 3, and 4. In some examples, downlink message 250 may be an RRC signal. The indication of switching via downlink message 250 may be dynamic, semi-static, or static.

[0090] UE 115-a can send uplink message 245 to network entity 105-a using a DFT-s-OFDM waveform. Uplink message 245 can be generated by UE 115-a according to the configuration provided in downlink message 250. Uplink message 245 can be associated with four or more OFDM symbols and can have formats from multiple uplink message formats (e.g., format 1, 3, or 4). Uplink message 245 can include a DMRS signal for FDM with UCI. In some examples, FDM with UCI using DMRS can be based on the number of DMRS symbols for FDM with UCI in a time slot.

[0091] Figure 3 An example of a process flow 300 for an FDM supporting DMRS according to one or more aspects of this disclosure is shown. Process flow 300 may implement, or be implemented by, aspects of wireless communication system 100 or wireless communication system 200. For example, process flow 300 may include UE 115-b, UE 115-c, and network entity 105-b, which may be examples of UE 115 and network entity 105 as described herein. In the following description of process flow 300, operations performed by UE 115-b, UE 115-c, and network entity 105-b may be performed in a different order than the exemplary order shown or at different times. Some operations in process flow 300 may also be omitted, or other operations may be added to process flow 300. Furthermore, although the operations in process flow 300 are illustrated as being performed by UE 115-b, UE 115-c, and network entity 105-b, the examples herein should not be construed as limiting, as the described features may be associated with any number of different devices.

[0092] At 305, UE 115-b can receive control signaling including configuration for uplink control messages. The control signaling may include an indication of a handover from TDM to FDM based on a first uplink control message format. The handover indication may include a dynamic indication, a semi-static indication, or a static indication. The control signaling may include RRC signaling.

[0093] At 310, UE 115-b can generate uplink control messages based on configuration and a first uplink control message format from multiple uplink control message formats. The uplink control message may include DMRS with UCI for FDM. The first uplink control message format may be associated with a DFT-s-OFDM waveform and the number of four or more OFDM symbols. In some examples, the FDM DMRS with UCI may be based on the type of demodulation sequence associated with the DMRS. The type of demodulation sequence may be associated with a root index associated with the demodulation reference signal. In some examples, the FDM DMRS with UCI may be based on the DMRS density in the frequency domain. Furthermore, FDM with UCI using DMRS may be based on the number of DMRS symbols for FDM with UCI in the time slot.

[0094] At 315, UE 115-b can use a DFT-s-OFDM waveform to send uplink control messages. In some examples, at 320, UE 115-b can generate a sidelink message that includes DMRS with FDM sidelink control information. In some examples, at 325, UE 115-b can send this sidelink message to a second UE 115.

[0095] Figure 4 A block diagram 400 of an FDM device 405 supporting DMRS according to one or more aspects of this disclosure is shown. Device 405 may be an example of various aspects of UE 115 as described herein. Device 405 may include a receiver 410, a transmitter 415, and a communication manager 420. Device 405, or one or more components of device 405 (e.g., receiver 410, transmitter 415, and communication manager 420), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0096] Receiver 410 may provide components for receiving information such as packets, user data, control information, or any combination thereof, associated with various information channels (e.g., control channels, data channels, FDM-related information channels of DMRS). The information may be passed to other components of device 405. Receiver 410 may utilize a single antenna or a collection of antennas.

[0097] Transmitter 415 may provide components for transmitting signals generated by other components of device 405. For example, transmitter 415 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, FDM-related information channels of DMRS), user data, control information, or any combination thereof. In some examples, transmitter 415 may be co-located with receiver 410 in a transceiver module. Transmitter 415 may utilize a single antenna or a collection of multiple antennas.

[0098] The communication manager 420, receiver 410, transmitter 415, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of the FDM as described herein in the DMRS. For example, the communication manager 420, receiver 410, transmitter 415, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0099] In some examples, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0100] Additionally or alternatively, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0101] In some examples, the communication manager 420 may be configured to use a receiver 410, a transmitter 415, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 420 may receive information from the receiver 410, transmit information to the transmitter 415, or integrate with the receiver 410, the transmitter 415, or both to acquire information, output information, or perform various other operations as described herein.

[0102] Communication manager 420 can support wireless communication according to examples disclosed herein. For example, communication manager 420 is capable of, configured to, or operable to support components for receiving control signaling including configuration for uplink control messages. Communication manager 420 is capable of, configured to, or operable to support components for generating uplink control messages based on configuration and a first uplink control message format from a set of multiple uplink control message formats, wherein the uplink control message includes a demodulation reference signal frequency-division multiplexed with uplink control information, and wherein the first uplink control message format is associated with a Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT) waveform and a number of four or more orthogonal frequency division multiplexing symbols. Communication manager 420 is capable of, configured to, or operable to support components for transmitting uplink control messages using a DFT waveform.

[0103] By including or configuring a communication manager 420 according to an example as described herein, device 405 (e.g., at least one processor that controls or otherwise couples to receiver 410, transmitter 415, communication manager 420, or a combination thereof) can support techniques for reducing overhead in PUCCH messages and increasing the number of UCIs that can be included in the message while maintaining PAPR above a PAPR threshold.

[0104] Figure 5 A block diagram 500 of an FDM device 505 supporting DMRS according to one or more aspects of this disclosure is shown. Device 505 may be an example of aspects of device 405 or UE 115 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Device 505, or one or more components of device 505 (e.g., receiver 510, transmitter 515, and communication manager 520), may include at least one processor that may be coupled to at least one memory to support the described technology. Each of these components may communicate with each other (e.g., via one or more buses).

[0105] Receiver 510 may provide components for receiving information such as packets, user data, control information, or any combination thereof, associated with various information channels (e.g., control channels, data channels, FDM-related information channels of DMRS). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

[0106] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, FDM-related information channels of DMRS), user data, control information, or any combination thereof. In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0107] Device 505 or its various components may be examples of various aspects of an FDM used to perform DMRS as described herein. For example, communication manager 520 may include control signaling receive manager 525, uplink message generation manager 530, uplink message sending manager 535, or any combination thereof. Communication manager 520 may be examples of various aspects of communication manager 420 as described herein. In some examples, communication manager 520 or its various components may be configured to use receiver 510, transmitter 515, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or be integrated in combination with receiver 510, transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0108] Communication manager 520 can support wireless communication according to examples disclosed herein. Control signaling receiving manager 525 is capable of, configured to, or operable to support components for receiving control signaling including configuration for uplink control messages. Uplink message generation manager 530 is capable of, configured to, or operable to support components for generating uplink control messages based on configuration and a first uplink control message format from a set of multiple uplink control message formats, wherein the uplink control message includes a demodulation reference signal frequency-division multiplexed with uplink control information, and wherein the first uplink control message format is associated with a Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT) waveform and a number of four or more orthogonal frequency division multiplexing symbols. Uplink message sending manager 535 is capable of, configured to, or operable to support components for sending uplink control messages using a DFT waveform.

[0109] Figure 6A block diagram 600 of a communication manager 620 for an FDM supporting DMRS according to one or more aspects of this disclosure is shown. The communication manager 620 may be an example of a communication manager 420, a communication manager 520, or aspects thereof as described herein. The communication manager 620 or its various components may be examples of components for performing various aspects of an FDM for DMRS as described herein. For example, the communication manager 620 may include a control signaling receive manager 625, an uplink message generation manager 630, an uplink message sending manager 635, a sidelink message generation manager 640, a sidelink message sending manager 645, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0110] Communication manager 620 can support wireless communication according to examples disclosed herein. Control signaling receive manager 625 is capable of, configured to, or operable to support components for receiving control signaling including configuration for uplink control messages. Uplink message generation manager 630 is capable of, configured to, or operable to support components for generating uplink control messages based on configuration and a first uplink control message format from a set of multiple uplink control message formats, wherein the uplink control message includes a demodulation reference signal frequency-division multiplexed with uplink control information, and wherein the first uplink control message format is associated with a Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT) waveform and a number of four or more orthogonal frequency division multiplexing symbols. Uplink message transmission manager 635 is capable of, configured to, or operable to support components for transmitting uplink control messages using a DFT waveform.

[0111] In some examples, control signaling includes an indication to switch from time-division multiplexing to frequency-division multiplexing based on a first uplink control message format.

[0112] In some examples, the indications for switching include dynamic indications, semi-static indications, or static indications.

[0113] In some examples, control signaling includes radio resource control signaling.

[0114] In some examples, the demodulation reference signal and uplink control information are frequency-division multiplexed based on the type of demodulation sequence associated with the demodulation reference signal.

[0115] In some examples, the type of demodulated sequence is associated with the root index of the demodulated reference signal.

[0116] In some examples, the demodulation reference signal and uplink control information are frequency-division multiplexed based on the demodulation reference signal density in the frequency domain.

[0117] In some examples, the demodulation reference signal is frequency-division multiplexed with the uplink control information based on the number of demodulation reference signal symbols that are frequency-division multiplexed with the uplink control information in the time slot.

[0118] In some examples, the sidelink message generation manager 640 is capable of, configured to, or operable to support components for generating sidelink messages, which include demodulation reference signals frequency-division multiplexed with sidelink control information. In some examples, the sidelink message transmission manager 645 is capable of, configured to, or operable to support components for transmitting sidelink messages to a second UE.

[0119] In some examples, the second uplink control message format in a set of multiple uplink control message formats is associated with the number of cyclic prefix orthogonal frequency division multiplexing waveforms and two or fewer orthogonal frequency division multiplexing symbols.

[0120] Figure 7 A diagram of a system 700 including an FDM device 705 supporting DMRS, according to one or more aspects of this disclosure, is shown. Device 705 may be an example of device 405, device 505, or UE 115 as described herein, or may include components thereof. Device 705 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 705 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 720, an input / output (I / O) controller 710, a transceiver 715, an antenna 725, at least one memory 730, code 735, and at least one processor 740. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 745).

[0121] I / O controller 710 manages the input and output signals of device 705. I / O controller 710 can also manage peripheral devices not integrated into device 705. In some cases, I / O controller 710 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 710 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ®LINUX ® Alternatively, the I / O controller 710 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 710 may be implemented as part of one or more processors, such as at least one processor 740. In some cases, a user may interact with the device 705 via the I / O controller 710 or via hardware components controlled by the I / O controller 710.

[0122] In some cases, device 705 may include a single antenna 725. However, in other cases, device 705 may have more than one antenna 725, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 715 may communicate bidirectionally via one or more antennas 725, a wired link, or a wireless link as described herein. For example, transceiver 715 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 715 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 725 for transmission; and demodulating packets received from one or more antennas 725. Transceiver 715, or transceiver 715 and one or more antennas 725, may be an example of transmitter 415, transmitter 515, receiver 410, receiver 510, or any combination thereof or components thereof as described herein.

[0123] At least one memory 730 may include random access memory (RAM) and read-only memory (ROM). At least one memory 730 may store computer-readable, computer-executable code 735, including instructions that, when executed by at least one processor 740, cause device 705 to perform the various functions described herein. Code 735 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 735 may not be directly executable by at least one processor 740, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 730 may contain a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0124] At least one processor 740 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 740 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 740. At least one processor 740 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 730) to cause device 705 to perform various functions (e.g., functions or tasks of an FDM supporting DMRS). For example, device 705 or components of device 705 may include at least one processor 740 and at least one memory 730 coupled to or coupled to at least one processor 740, wherein at least one processor 740 and at least one memory 730 are configured to perform the various functions described herein. In some examples, at least one processor 740 may include multiple processors, and at least one memory 730 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 740 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 740) and memory circuitry (which may include at least one memory 730)) or components that receive or receive input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Thus, at least one processor 740 or a processing system including at least one processor 740 may be configured, capable of being configured, or operable to cause device 705 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 730 or otherwise.

[0125] The communication manager 720 can support wireless communication according to examples disclosed herein. For example, the communication manager 720 is capable of, configured to, or operable to support components for receiving control signaling including configuration for uplink control messages. The communication manager 720 is capable of, configured to, or operable to support components for generating uplink control messages based on configuration and a first uplink control message format from a set of multiple uplink control message formats, wherein the uplink control message includes a demodulation reference signal frequency-division multiplexed with uplink control information, and wherein the first uplink control message format is associated with a Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT) waveform and a number of four or more orthogonal frequency division multiplexing symbols. The communication manager 720 is capable of, configured to, or operable to support components for transmitting uplink control messages using a DFT waveform.

[0126] By including or configuring a communication manager 720 according to an example as described herein, device 705 can support techniques for reducing overhead in PUCCH messages and increasing the number of UCIs that can be included in the message, while maintaining PAPR above a PAPR threshold.

[0127] In some examples, the communication manager 720 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 715, one or more antennas 725, or any combination thereof, or otherwise cooperating with them. Although the communication manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 720 may be supported or executed by at least one processor 740, at least one memory 730, code 735, or any combination thereof. For example, code 735 may include instructions that can be executed by at least one processor 740 to cause device 705 to perform various aspects of FDM of DMRS as described herein, or at least one processor 740 and at least one memory 730 may be otherwise configured to perform or support such operations individually or jointly.

[0128] Figure 8 A block diagram 800 of an FDM device 805 supporting DMRS according to one or more aspects of this disclosure is shown. Device 805 may be an example of aspects of network entity 105 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805, or one or more components of device 805 (e.g., receiver 810, transmitter 815, and communication manager 820), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

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

[0130] Transmitter 815 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 805. For example, transmitter 815 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, transmitter 815 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 815 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 815 and receiver 810 may be co-located in a transceiver, which may include or be coupled to a modem.

[0131] The communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of an FDM as described herein in the DMRS. For example, the communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0132] In some examples, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0133] Additionally or alternatively, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0134] In some examples, the communication manager 820 may be configured to use a receiver 810, a transmitter 815, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or be integrated in combination with the receiver 810, the transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0135] The communication manager 820 can support wireless communication according to examples disclosed herein. For example, the communication manager 820 is capable of, configured to, or operable to support components for outputting control signaling including configuration for uplink control messages. The communication manager 820 is capable of, configured to, or operable to support components for obtaining uplink control messages based on configuration and a first uplink control message format from a set of multiple uplink control message formats, wherein the uplink control message includes a demodulated reference signal frequency-division multiplexed with uplink control information, and wherein the first uplink control message format is associated with a discrete Fourier transform extended orthogonal frequency division multiplexing waveform and a number of four or more orthogonal frequency division multiplexing symbols. The communication manager 820 is capable of, configured to, or operable to support components for decoding uplink control messages based on configuration.

[0136] By including or configuring a communication manager 820 according to an example as described herein, device 805 (e.g., at least one processor that controls or otherwise couples to receiver 810, transmitter 815, communication manager 820, or a combination thereof) can support techniques for reducing overhead in PUCCH messages and increasing the number of UCIs that can be included in the message while maintaining PAPR above a PAPR threshold.

[0137] Figure 9 A block diagram 900 of an FDM device 905 supporting DMRS according to one or more aspects of this disclosure is shown. Device 905 may be an example of aspects of device 805 or network entity 105 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905, or one or more components of device 905 (e.g., receiver 910, transmitter 915, and communication manager 920), may include at least one processor that may be coupled to at least one memory to support the described technology. Each of these components may communicate with each other (e.g., via one or more buses).

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

[0139] Transmitter 915 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 905. For example, transmitter 915 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, transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 915 and receiver 910 may be co-located in a transceiver, which may include or be coupled to a modem.

[0140] Device 905 or its various components may be examples of various aspects of an FDM used to perform DMRS as described herein. For example, communication manager 920 may include control signaling output manager 925, uplink message receiving manager 930, decoding manager 935, or any combination thereof. Communication manager 920 may be examples of aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to use receiver 910, transmitter 915, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 920 may receive information from receiver 910, transmit information to transmitter 915, or be integrated in combination with receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0141] Communication manager 920 can support wireless communication according to examples disclosed herein. Control signaling output manager 925 is capable of, configured to, or operable to support components for outputting control signaling including configuration for uplink control messages. Uplink message receiving manager 930 is capable of, configured to, or operable to support components for obtaining uplink control messages based on configuration and a first uplink control message format from a set of multiple uplink control message formats, wherein the uplink control message includes a demodulated reference signal frequency-division multiplexed with uplink control information, and wherein the first uplink control message format is associated with a discrete Fourier transform extended orthogonal frequency division multiplexing waveform and a number of four or more orthogonal frequency division multiplexing symbols. Decoding manager 935 is capable of, configured to, or operable to support components for decoding uplink control messages based on configuration.

[0142] Figure 10 A block diagram 1000 of a communication manager 1020 for an FDM supporting DMRS according to one or more aspects of this disclosure is shown. The communication manager 1020 may be an example of a communication manager 820, a communication manager 920, or aspects thereof as described herein. The communication manager 1020 or its various components may be examples of components for performing various aspects of an FDM for DMRS as described herein. For example, the communication manager 1020 may include a control signaling output manager 1025, an uplink message receiving manager 1030, a decoding manager 1035, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and this communication may include communication within protocol layers of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0143] Communication manager 1020 can support wireless communication according to examples disclosed herein. Control signaling output manager 1025 is capable of, configured to, or operable to support components for outputting control signaling including configurations for uplink control messages. Uplink message receiving manager 1030 is capable of, configured to, or operable to support components for obtaining uplink control messages based on configuration and a first uplink control message format from a set of multiple uplink control message formats, wherein the uplink control message includes a demodulated reference signal frequency-division multiplexed with uplink control information, and wherein the first uplink control message format is associated with a discrete Fourier transform extended orthogonal frequency division multiplexing waveform and a number of four or more orthogonal frequency division multiplexing symbols. Decoding manager 1035 is capable of, configured to, or operable to support components for decoding uplink control messages based on configuration.

[0144] In some examples, the downlink message output manager 1040 is capable of, configured to, or operable to support components for outputting downlink control messages, which include a demodulated reference signal frequency-division multiplexed with downlink control information, wherein the downlink control message utilizes a discrete Fourier transform to extend the orthogonal frequency division multiplexed waveform.

[0145] In some examples, control signaling includes an indication to switch from time-division multiplexing to frequency-division multiplexing based on a first uplink control message format.

[0146] In some examples, the indications for switching include dynamic indications, semi-static indications, or static indications.

[0147] In some examples, control signaling includes radio resource control signaling.

[0148] In some examples, the demodulation reference signal and uplink control information are frequency-division multiplexed based on the type of demodulation sequence associated with the demodulation reference signal.

[0149] In some examples, the type of demodulated sequence is associated with the root index of the demodulated reference signal.

[0150] In some examples, the demodulation reference signal and uplink control information are frequency-division multiplexed based on the demodulation reference signal density in the frequency domain.

[0151] In some examples, the demodulation reference signal is frequency-division multiplexed with the uplink control information based on the number of demodulation reference signal symbols that are frequency-division multiplexed with the uplink control information in the time slot.

[0152] In some examples, the second uplink control message format in a set of multiple uplink control message formats is associated with the number of cyclic prefix orthogonal frequency division multiplexing waveforms and two or fewer orthogonal frequency division multiplexing symbols.

[0153] Figure 11 A diagram of a system 1100 including a device 1105 supporting DMRS for an FDM, according to one or more aspects of this disclosure, is shown. Device 1105 may be an example of device 805, device 905, or network entity 105 as described herein, or a component including such devices or network entities. Device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and this communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1105 may include components supporting output and enabling communication, such as a communication manager 1120, a transceiver 1110, an antenna 1115, at least one memory 1125, code 1130, and at least one processor 1135. These components may communicate electronically or otherwise (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1140).

[0154] Transceiver 1110 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1110 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1110 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1105 may include one or more antennas 1115 that are capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1110 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1115, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1115, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1110 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1115 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1115 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1110 may include one or more processors or one or more memory components, or be configured to couple to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1110, or transceiver 1110 and one or more antennas 1115, or transceiver 1110 and one or more antennas 1115 and one or more processors or one or more memory components (e.g., at least one processor 1135, at least one memory 1125, or both), may be included in a chip or chip assembly mounted in device 1105. In some examples, transceiver 1110 may be able to operate 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).

[0155] At least one memory 1125 may include RAM, ROM, or any combination thereof. At least one memory 1125 may store computer-readable, computer-executable code 1130 including instructions that, when executed by one or more of at least one processor 1135, cause device 1105 to perform the various functions described herein. Code 1130 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1130 may not be directly executable by a processor in at least one processor 1135, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1125 may also include a BIOS, among other things, that controls basic hardware or software operations, such as interaction with peripheral components or devices. In some examples, at least one processor 1135 may include multiple processors, and at least one memory 1125 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0156] At least one processor 1135 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, at least one processor 1135 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1135. At least one processor 1135 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1125) to cause device 1105 to perform various functions (e.g., functions or tasks of FDM supporting DMRS). For example, device 1105 or components of device 1105 may include at least one processor 1135 and at least one memory 1125 coupled to one or more of the at least one processor 1135, wherein at least one processor 1135 and at least one memory 1125 are configured to perform the various functions described herein. At least one processor 1135 may 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 (e.g., by executing code 1130) host functions for performing the functions of device 1105. At least one processor 1135 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1105 (such as within one or more memories of at least one memory 1125). In some examples, at least one processor 1135 may include multiple processors, and at least one memory 1125 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1135 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1135) and memory circuitry (which may include at least one memory 1125)) or components that receive or acquire input and process the input to produce, generate, or acquire a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Therefore, at least one processor 1135 or a processing system including at least one processor 1135 may be configured, configured to, or operated to cause the device 1105 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1125 or otherwise.

[0157] In some examples, bus 1140 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1140 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1105, or communication performed between different components of device 1105 that are co-addressable or may be located in different locations (e.g., where device 1105 may refer to a system in which one or more of communication manager 1120, transceiver 1110, at least one memory 1125, code 1130 and at least one processor 1135 may be located in one component of different components or partitioned between different components).

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

[0159] Communication manager 1120 can support wireless communication according to examples disclosed herein. For example, communication manager 1120 is capable of, configured to, or operable to support components for outputting control signaling including configuration for uplink control messages. Communication manager 1120 is capable of, configured to, or operable to support components for obtaining uplink control messages based on configuration and a first uplink control message format from a set of multiple uplink control message formats, wherein the uplink control message includes a demodulated reference signal frequency-division multiplexed with uplink control information, and wherein the first uplink control message format is associated with a discrete Fourier transform extended orthogonal frequency division multiplexing waveform and a number of four or more orthogonal frequency division multiplexing symbols. Communication manager 1120 is capable of, configured to, or operable to support components for decoding uplink control messages based on configuration.

[0160] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 can support techniques for reducing overhead in PUCCH messages and increasing the number of UCIs that can be included in the message, while maintaining PAPR above a PAPR threshold.

[0161] In some examples, the communication manager 1120 may be configured to use or otherwise coordinate with the transceiver 1110, one or more antennas 1115 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by the transceiver 1110, one or more processors in at least one processor 1135, one or more memories in at least one memory 1125, code 1130, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1135, at least one memory 1125, code 1130, or any combination thereof). For example, code 1130 may include instructions that can be executed by one or more processors in at least one processor 1135 to cause the device 1105 to perform various aspects of the FDM of the DMRS as described herein, or at least one processor 1135 and at least one memory 1125 may be otherwise configured to perform or support such operations individually or jointly.

[0162] Figure 12 A flowchart illustrating a method 1200 of an FDM supporting DMRS according to various aspects of this disclosure is shown. Operation of method 1200 may be implemented by a UE or its components as described herein. For example, operation of method 1200 may be performed by, as referenced... Figures 1 to 7 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0163] At 1205, the method may include receiving control signaling including configuration for uplink control messages. The operation of block 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1205 may be provided by reference to [reference needed]. Figure 6 The control signaling receiver 625 described herein is used to perform this action.

[0164] At 1210, the method may include generating the uplink control message according to the configuration and a first uplink control message format from a set of multiple uplink control message formats, wherein the uplink control message includes a demodulated reference signal frequency-division multiplexed with uplink control information, and wherein the first uplink control message format is associated with a discrete Fourier transform extended orthogonal frequency division multiplexing waveform and a number of four or more orthogonal frequency division multiplexing symbols. The operation of block 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1210 may be derived from references... Figure 6 The described uplink message generation manager 630 is used to execute this.

[0165] At 1215, the method may include using a discrete Fourier transform to extend the orthogonal frequency division multiplexing waveform to transmit uplink control messages. The operation of block 1215 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1215 may be derived from references... Figure 6 The described uplink message sending manager 635 is used to perform this.

[0166] Figure 13 A flowchart illustrating a method 1300 of an FDM supporting DMRS according to various aspects of this disclosure is shown. Operation of method 1300 may be implemented by a UE or its components as described herein. For example, operation of method 1300 may be performed by, as referenced... Figures 1 to 7 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0167] At 1305, the method may include receiving control signaling including configuration for uplink control messages. Operation of block 1305 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1305 may be provided by reference to [reference needed]. Figure 6 The control signaling receiver 625 described herein is used to perform this action.

[0168] At 1310, the method may include generating the uplink control message according to the configuration and a first uplink control message format from a set of multiple uplink control message formats, wherein the uplink control message includes a demodulated reference signal frequency-division multiplexed with uplink control information, and wherein the first uplink control message format is associated with a discrete Fourier transform extended orthogonal frequency division multiplexing waveform and a number of four or more orthogonal frequency division multiplexing symbols. The operation of block 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1310 may be derived from references... Figure 6 The described uplink message generation manager 630 is used to execute this.

[0169] At 1315, the method may include using a discrete Fourier transform to extend the orthogonal frequency division multiplexing waveform to transmit uplink control messages. The operation of block 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1315 may be derived from references... Figure 6 The described uplink message sending manager 635 is used to perform this.

[0170] At 1320, the method may include generating a sidelink message that includes a demodulated reference signal frequency-division multiplexed with sidelink control information. The operation of block 1320 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1320 may be derived from references... Figure 6 The described sidelink message generation manager 640 is used to perform this.

[0171] At 1325, the method may include sending a sidelink message to a second UE. The operation of block 1325 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1325 may be derived from references... Figure 6 The described sidelink message sending manager 645 is used to perform this.

[0172] Figure 14 A flowchart illustrating a method 1400 of an FDM supporting DMRS according to various aspects of this disclosure is shown. The operation of method 1400 may be implemented by a network entity or its components as described herein. For example, the operation of method 1400 may be implemented by, as referenced... Figures 1 to 3 as well as Figures 8 to 11 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0173] At 1405, the method may include outputting control signaling including configuration for uplink control messages. Operation of block 1405 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1405 may be provided by reference to [reference needed]. Figure 10 The control signaling output manager 1025 described is executed.

[0174] At 1410, the method may include obtaining the uplink control message according to the configuration and a first uplink control message format from a set of multiple uplink control message formats, wherein the uplink control message includes a demodulated reference signal frequency-division multiplexed with uplink control information, and wherein the first uplink control message format is associated with a discrete Fourier transform extended orthogonal frequency division multiplexing waveform and a number of four or more orthogonal frequency division multiplexing symbols. The operation of block 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1410 may be derived from references... Figure 10 The described uplink message receiving manager 1030 is used to perform this.

[0175] At 1415, the method may include decoding uplink control messages based on configuration. The operation of block 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1415 may be derived from references... Figure 10 The described decoding manager 1035 is executed.

[0176] Figure 15 A flowchart illustrating a method 1500 of an FDM supporting DMRS according to various aspects of this disclosure is shown. The operation of method 1500 may be implemented by a network entity or its components as described herein. For example, the operation of method 1500 may be implemented by, as referenced... Figures 1 to 3 as well as Figures 8 to 11 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0177] At 1505, the method may include outputting a downlink control message, the downlink control message including a demodulated reference signal frequency-division multiplexed with downlink control information, wherein the downlink control message utilizes a discrete Fourier transform to extend the orthogonal frequency division multiplexed waveform. The operation of block 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1505 may be derived from a reference... Figure 10 The downlink message output manager 1040 described herein is used to perform this action.

[0178] At 1510, the method may include outputting control signaling including configuration for uplink control messages. Operation of block 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be derived from references... Figure 10 The control signaling output manager 1025 described is executed.

[0179] At 1515, the method may include obtaining the uplink control message according to the configuration and a first uplink control message format from a set of multiple uplink control message formats, wherein the uplink control message includes a demodulated reference signal frequency-division multiplexed with uplink control information, and wherein the first uplink control message format is associated with a discrete Fourier transform extended orthogonal frequency division multiplexing waveform and a number of four or more orthogonal frequency division multiplexing symbols. The operation of block 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1515 may be derived from references... Figure 10 The described uplink message receiving manager 1030 is used to perform this.

[0180] At 1520, the method may include decoding uplink control messages based on configuration. The operation of block 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1520 may be derived from references... Figure 10 The described decoding manager 1035 is executed.

[0181] The following provides an overview of the various aspects of this disclosure.

[0182] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving control signaling including a configuration for an uplink control message; generating the uplink control message according to the configuration and a first uplink control message format from a plurality of uplink control message formats, wherein the uplink control message includes a DMRS for FDM with UCI, and wherein the first uplink control message format is associated with a DFT-s-OFDM waveform and a number of four or more OFDM symbols; and transmitting the uplink control message using the DFT-s-OFDM waveform.

[0183] Aspect 2: According to the method of aspect 1, the control signaling includes an indication to switch from TDM to FDM at least in part based on the first uplink control message format.

[0184] Aspect 3: According to the method of aspect 2, the indication for switching includes a dynamic indication, a semi-static indication, or a static indication.

[0185] Aspect 4: The method according to any one of Aspects 2 to 3, wherein the control signaling includes radio resource control signaling.

[0186] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the DMRS is subjected to FDM with the UCI based at least in part on the type of demodulation sequence associated with the DMRS.

[0187] Aspect 6: According to the method of aspect 5, wherein the type of the demodulated sequence is associated with a root index associated with the DMRS.

[0188] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the DMRS and the UCI are subjected to FDM at least in part based on the DMRS density in the frequency domain.

[0189] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the DMRS is performed FDM with the UCI based at least in part on the number of DMRS symbols that are performed FDM with the UCI in a time slot.

[0190] Aspect 9: The method according to any one of Aspects 1 to 8, the method further comprising: generating a sidelink message, the sidelink message including DMRS with sidelink control information FDM; and sending the sidelink message to a second UE.

[0191] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the second uplink control message format in the plurality of uplink control message formats is associated with the CP-OFDM waveform and the number of two or fewer OFDM symbols.

[0192] Aspect 11: A method for wireless communication at a network entity, the method comprising: outputting control signaling including a configuration for uplink control messages; obtaining the uplink control messages according to the configuration and a first uplink control message format from a plurality of uplink control message formats, wherein the uplink control messages include DMRS with UCI FDM, and wherein the first uplink control message format is associated with a DFT-s-OFDM waveform and a number of four or more OFDM symbols; and decoding the uplink control messages at least in part based on the configuration.

[0193] Aspect 12: According to the method of aspect 11, the method further includes: outputting a downlink control message, the downlink control message including a DMRS with downlink control information in FDM, wherein the downlink control message utilizes a DFT-s-OFDM waveform.

[0194] Aspect 13: The method according to any one of Aspects 11 to 12, wherein the control signaling includes an indication to switch from TDM to FDM based at least in part on the first uplink control message format.

[0195] Aspect 14: The method according to aspect 13, wherein the indication for switching includes a dynamic indication, a semi-static indication, or a static indication.

[0196] Aspect 15: The method according to any one of Aspects 13 to 14, wherein the control signaling includes radio resource control signaling.

[0197] Aspect 16: The method according to any one of aspects 11 to 15, wherein the DMRS is subjected to FDM with the UCI based at least in part on the type of demodulation sequence associated with the DMRS.

[0198] Aspect 17: The method according to aspect 16, wherein the type of the demodulated sequence is associated with a root index associated with the DMRS.

[0199] Aspect 18: The method according to any one of Aspects 11 to 17, wherein the DMRS and the UCI are subjected to FDM at least in part based on the DMRS density in the frequency domain.

[0200] Aspect 19: The method according to any one of aspects 11 to 18, wherein the DMRS is performed FDM with the UCI based at least in part on the number of DMRS symbols that are performed FDM with the UCI in a time slot.

[0201] Aspect 20: The method according to any one of Aspects 11 to 19, wherein the second uplink control message format of the plurality of uplink control message formats is associated with the CP-OFDM waveform and the number of two or fewer OFDM symbols.

[0202] Aspect 21: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of Aspects 1 to 10.

[0203] Aspect 22: A UE for wireless communication, the UE comprising at least one component for performing the method according to any one of aspects 1 to 10.

[0204] Aspect 23: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 1 to 10.

[0205] Aspect 24: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, so that the network entity performs a method according to any one of aspects 11 to 20.

[0206] Aspect 25: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 11 to 20.

[0207] Aspect 26: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 11 to 20.

[0208] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0209] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

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

[0211] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0212] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including portions distributed such that the functions are implemented in different physical locations.

[0213] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0214] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, 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). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0215] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0216] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, acquiring, selecting, choosing, creating, and other similar actions.

[0217] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate between similar components. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second reference numeral or other subsequent reference numerals.

[0218] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0219] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this 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 user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Receive control signaling, including configuration for uplink control messages; The uplink control message is generated according to the configuration and a first uplink control message format from multiple uplink control message formats, wherein the uplink control message includes a demodulation reference signal frequency-division multiplexed with uplink control information, and wherein the first uplink control message format is associated with a discrete Fourier transform extended orthogonal frequency division multiplexed waveform and the number of four or more orthogonal frequency division multiplexed symbols; as well as The uplink control message is transmitted using the Discrete Fourier Transform extended orthogonal frequency division multiplexing waveform.

2. The UE of claim 1, wherein the control signaling includes an indication of switching from time division multiplexing to frequency division multiplexing based at least in part on the first uplink control message format.

3. The UE according to claim 2, wherein the indication for handover includes a dynamic indication, a semi-static indication, or a static indication.

4. The UE according to claim 2, wherein the control signaling includes radio resource control signaling.

5. The UE of claim 1, wherein the frequency division multiplexing of the demodulation reference signal with the uplink control information is based at least in part on the type of demodulation sequence associated with the demodulation reference signal.

6. The UE of claim 5, wherein the type of the demodulation sequence is associated with a root index associated with the demodulation reference signal.

7. The UE of claim 1, wherein the frequency division multiplexing of the demodulation reference signal and the uplink control information is based at least in part on the demodulation reference signal density in the frequency domain.

8. The UE of claim 1, wherein the frequency division multiplexing of the demodulation reference signal with the uplink control information is based at least in part on the number of demodulation reference signal symbols that are frequency divided multiplexed with the uplink control information in the time slot.

9. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Generate a sidelink message, the sidelink message including a demodulation reference signal frequency-division multiplexed with sidelink control information; and The side link message is sent to the second UE.

10. The UE of claim 1, wherein the second uplink control message format in the plurality of uplink control message formats is associated with a cyclic prefix orthogonal frequency division multiplexing waveform and the number of two or fewer orthogonal frequency division multiplexing symbols.

11. A network entity, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the network entity: The output includes control signaling for configuring uplink control messages; The uplink control message is obtained according to the configuration and a first uplink control message format from multiple uplink control message formats, wherein the uplink control message includes a demodulation reference signal frequency-division multiplexed with uplink control information, and wherein the first uplink control message format is associated with a discrete Fourier transform extended orthogonal frequency division multiplexing waveform and the number of four or more orthogonal frequency division multiplexing symbols; and The uplink control messages are decoded based at least in part on the configuration.

12. The network entity of claim 11, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to: Output downlink control messages, which include demodulation reference signals frequency-division multiplexed with downlink control information, wherein the downlink control messages utilize discrete Fourier transform to extend orthogonal frequency division multiplexed waveforms.

13. The network entity of claim 11, wherein the control signaling includes an indication to switch from time division multiplexing to frequency division multiplexing at least in part based on the first uplink control message format.

14. The network entity of claim 13, wherein the indication for switching includes a dynamic indication, a semi-static indication, or a static indication.

15. The network entity of claim 13, wherein the control signaling includes radio resource control signaling.

16. The network entity of claim 11, wherein the frequency division multiplexing of the demodulation reference signal with the uplink control information is based at least in part on the type of demodulation sequence associated with the demodulation reference signal.

17. The network entity of claim 16, wherein the type of the demodulated sequence is associated with a root index associated with the demodulated reference signal.

18. The network entity of claim 11, wherein the frequency division multiplexing of the demodulation reference signal with the uplink control information is based at least in part on the demodulation reference signal density in the frequency domain.

19. The network entity of claim 11, wherein the frequency division multiplexing of the demodulation reference signal with the uplink control information is based at least in part on the number of demodulation reference signal symbols frequency division multiplexed with the uplink control information in the time slot.

20. The network entity of claim 11, wherein the second uplink control message format of the plurality of uplink control message formats is associated with a cyclic prefix orthogonal frequency division multiplexing waveform and the number of two or fewer orthogonal frequency division multiplexing symbols.

21. A method for conducting wireless communication at a user equipment (UE), the method comprising: Receive control signaling, including configuration for uplink control messages; The uplink control message is generated according to the configuration and a first uplink control message format from multiple uplink control message formats, wherein the uplink control message includes a demodulation reference signal frequency-division multiplexed with uplink control information, and wherein the first uplink control message format is associated with a discrete Fourier transform extended orthogonal frequency division multiplexed waveform and the number of four or more orthogonal frequency division multiplexed symbols; as well as The uplink control message is transmitted using the Discrete Fourier Transform extended orthogonal frequency division multiplexing waveform.

22. The method of claim 21, wherein the control signaling includes an indication of switching from time division multiplexing to frequency division multiplexing based at least in part on the first uplink control message format.

23. The method of claim 22, wherein the indication for switching includes a dynamic indication, a semi-static indication, or a static indication.

24. The method of claim 22, wherein the control signaling includes radio resource control signaling.

25. The method of claim 21, wherein the frequency division multiplexing of the demodulation reference signal with the uplink control information is based at least in part on the type of demodulation sequence associated with the demodulation reference signal.

26. The method of claim 25, wherein the type of the demodulated sequence is associated with a root index associated with the demodulated reference signal.

27. The method of claim 21, wherein the frequency division multiplexing of the demodulation reference signal with the uplink control information is based at least in part on the demodulation reference signal density in the frequency domain.

28. A method for conducting wireless communication at a network entity, the method comprising: The output includes control signaling for configuring uplink control messages; The uplink control message is obtained according to the configuration and a first uplink control message format from multiple uplink control message formats, wherein the uplink control message includes a demodulation reference signal frequency-division multiplexed with uplink control information, and wherein the first uplink control message format is associated with a discrete Fourier transform extended orthogonal frequency division multiplexing waveform and the number of four or more orthogonal frequency division multiplexing symbols; and The uplink control messages are decoded based at least in part on the configuration.

29. The method of claim 28, wherein the frequency division multiplexing of the demodulation reference signal with the uplink control information is based at least in part on the number of demodulation reference signal symbols frequency division multiplexed with the uplink control information in the time slot.

30. The method of claim 28, wherein the second uplink control message format of the plurality of uplink control message formats is associated with a cyclic prefix orthogonal frequency division multiplexing waveform and the number of two or fewer orthogonal frequency division multiplexing symbols.

Images