Concurrent code division and frequency division signaling via uplink channels

Abstract

Methods, systems, and devices are described for wireless communication at a user equipment (UE). The UE may operate by asynchronously transmitting a code division multiple access (CDMA) uplink signal to a network entity. The UE may transmit the CDMA signal via an uplink channel that may be shared with Orthogonal Frequency Division Multiplexing (OFDM) signaling transmitted by one or more other UEs. The UE may indicate to the network entity the ability to communicate with the CDMA waveform, and may use the CDMA waveform based on sending the indication. The UE may also receive one or more parameters associated with using the CDMA waveform, and may use the CDMA waveform based on the one or more parameters. The uplink channel may be a random access channel (RACH) and may support RACH transmission, or may be a data channel and support data transmission.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This patent application claims priority to U.S. patent application No. 17 / 944,036, filed by Ma et al. on September 13, 2022, entitled “CONCURRENT CODEDIVISION AND FREQUENCY DIVISION SIGNALING VIA AN UPLINK CHANNEL,” which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0002] The following relates to wireless communications at a user equipment (UE), including concurrent code-division and frequency-division signaling via an uplink channel. Background Art

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

[0004] In some wireless communication systems, a user equipment (UE) may maintain an accurate position with a network entity so that the UE and the terrestrial network entity may communicate synchronously. However, in some cases, the UE may not support synchronous operation. Summary of the invention

[0005] The described techniques relate to improved methods, systems, devices, and apparatuses that support concurrent code division and frequency division signaling via an uplink channel. For example, the described techniques allow a user equipment (UE) to perform asynchronous communications using a waveform based on code division multiple access (CDMA), such that the UE can communicate with a network entity (e.g., a non-terrestrial or terrestrial network entity) using the CDMA waveform. The UE can indicate to the network entity the ability to communicate using the CDMA waveform, and can use the CDMA waveform based on sending the indication. The UE can also receive one or more parameters associated with using the CDMA waveform, and can use the CDMA waveform based on the one or more parameters. The CDMA waveform can be sent via an uplink channel, which can be shared with an orthogonal frequency division multiple access (OFDMA) waveform (e.g., sent by one or more other UEs). In some cases, an uplink channel for CDMA transmissions can be divided into CDMA subchannels for CDMA transmissions. The uplink channel can be a random access channel (RACH) and can support RACH transmissions, or can be a data channel and support data transmissions. In some cases, the UE may transition from CDMA to OFDMA transmissions after establishing timing adjustments with the network.

[0006] A method for wireless communication at a UE is described. The method may include: sending a first indication to a network entity and using an OFDMA signal that the UE supports CDMA transmission using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, and the CDMA transmissions in the one or more CDMA transmissions are at least partially concurrent with the OFDMA transmissions in the one or more OFDMA transmissions; receiving a second indication of one or more parameters for the CDMA transmission using the uplink channel; and sending a CDMA signal via the uplink channel using the one or more parameters based on sending the first indication that the UE supports CDMA transmission using the uplink channel.

[0007] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: send a first indication to a network entity and using an OFDMA signal that the UE supports CDMA transmission using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, and the CDMA transmissions in the one or more CDMA transmissions are at least partially concurrent with the OFDMA transmissions in the one or more OFDMA transmissions; receive a second indication of one or more parameters for the CDMA transmission using the uplink channel; and send a CDMA signal via the uplink channel using the one or more parameters based on sending the first indication that the UE supports CDMA transmission using the uplink channel.

[0008] Another apparatus for wireless communication at a UE is described. The apparatus may include: a component for sending a first indication to a network entity and using an OFDMA signal that the UE supports CDMA transmission using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, and a CDMA transmission in the one or more CDMA transmissions is at least partially concurrent with an OFDMA transmission in the one or more OFDMA transmissions; a component for receiving a second indication of one or more parameters for the CDMA transmission using the uplink channel; and a component for sending a CDMA signal via the uplink channel using the one or more parameters based on sending the first indication that the UE supports CDMA transmission using the uplink channel.

[0009] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions that can be executed by a processor to: send a first indication to a network entity and using an OFDMA signal that the UE supports CDMA transmission using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, and the CDMA transmissions in the one or more CDMA transmissions are at least partially concurrent with the OFDMA transmissions in the one or more OFDMA transmissions; receive a second indication of one or more parameters for the CDMA transmission using the uplink channel; and send a CDMA signal via the uplink channel using the one or more parameters based on sending the first indication that the UE supports CDMA transmission using the uplink channel.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a third indication from a network entity that the uplink channel supports CDMA transmission, wherein transmitting the CDMA signal may be based on receiving the third indication.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving a third indication from a network entity via an uplink channel to restrict CDMA transmission; and suppressing transmission of a second CDMA signal based on the third indication, wherein the transmission of the CDMA signal may be based on the transmission of the CDMA signal that occurred before receiving the third indication.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a CDMA signal may include operations, features, components, or instructions for: sending a random access preamble via a random access channel (RACH); and sending a capsule including data transmission associated with the random access preamble via the RACH, wherein the UE sends the capsule during a time period that may be based on a propagation delay of the transmission between the UE and a network entity.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, propagation delay may be based on a reference signal received power (RSRP) measurement.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a length of the random access preamble may be based on a propagation delay.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a CDMA signal may include operations, features, components, or instructions for sending data via a data channel at a time offset from a RACH transmission, where the time offset may be based on a propagation delay of the transmission between the UE and a network entity.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a preamble associated with data via a data channel and prior to sending the data, wherein the preamble may be used to resynchronize uplink transmissions from the UE to a network entity.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving a third indication of a timing adjustment from a network entity; and transitioning from sending a CDMA waveform via an uplink channel to sending an OFDM waveform via an uplink channel based on receiving the third indication.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: The uplink transmission from the UE to the network entity may be an asynchronous transmission.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, an uplink channel includes a set of multiple CDMA subchannels based on one or more parameters of a CDMA transmission.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a UE and a network entity communicate via a non-terrestrial network (NTN).

[0021] A method for wireless communication at a network entity is described. The method may include: receiving a first indication via an OFDMA signal that a UE supports CDMA transmission using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, a CDMA transmission in the one or more CDMA transmissions being at least partially concurrent with an OFDMA transmission in the one or more OFDMA transmissions; sending a second indication of one or more parameters for the CDMA transmission using the uplink channel; and receiving a CDMA signal via the uplink channel using the one or more parameters based on receiving the first indication that the UE supports CDMA transmission using the uplink channel.

[0022] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a first indication via an OFDMA signal that a UE supports CDMA transmission using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, and a CDMA transmission in the one or more CDMA transmissions is at least partially concurrent with an OFDMA transmission in the one or more OFDMA transmissions; send a second indication of one or more parameters for the CDMA transmission using the uplink channel; and receive a CDMA signal via the uplink channel using the one or more parameters based on receiving the first indication that the UE supports CDMA transmission using the uplink channel.

[0023] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for receiving, via an OFDMA signal, a first indication that a UE supports CDMA transmissions using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, a CDMA transmission in the one or more CDMA transmissions being at least partially concurrent with an OFDMA transmission in the one or more OFDMA transmissions; means for sending a second indication of one or more parameters for the CDMA transmissions using the uplink channel; and means for receiving, via the uplink channel, a CDMA signal using the one or more parameters based on receiving the first indication that the UE supports CDMA transmissions using the uplink channel.

[0024] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to: receive a first indication via an OFDMA signal that a UE supports CDMA transmission using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, a CDMA transmission in the one or more CDMA transmissions being at least partially concurrent with an OFDMA transmission in the one or more OFDMA transmissions; send a second indication of one or more parameters for the CDMA transmission using the uplink channel; and receive a CDMA signal via the uplink channel using the one or more parameters based on receiving the first indication that the UE supports CDMA transmission using the uplink channel.

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining whether a received power level of an uplink channel satisfies a threshold power level; and sending a third indication that the uplink channel supports CDMA transmission based on determining that the received power level fails to satisfy the threshold power level, wherein receiving a CDMA signal may be based on sending the third indication.

[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining whether a received power level of an uplink channel satisfies a threshold power level; and sending a third indication to the UE to restrict CDMA transmission via the uplink channel based on determining that the received power level of the uplink channel satisfies the threshold power level.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining whether a received power level of an uplink channel meets a threshold power level based on an ability of a network entity's receiver to detect and cancel interference, wherein the threshold power level may be based on the ability of the network entity's receiver.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a CDMA signal may include operations, features, components, or instructions for: receiving a random access preamble associated with a UE via a RACH; and receiving a capsule including a data transmission associated with the random access preamble via the RACH, wherein a network entity receives the capsule during a time period that may be based on a propagation delay of the transmission between the UE and the network entity.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the propagation delay may be based on RSRP measurements.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a length of the random access preamble may be based on a propagation delay.

[0031] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving data via a data channel at a time offset from a RACH transmission, wherein the time offset may be based on a propagation delay of transmissions between the UE and a network entity.

[0032] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a preamble associated with data via a data channel and prior to receipt of the data, wherein the preamble may be used to resynchronize uplink transmissions from the UE to a network entity.

[0033] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: sending a third indication of a timing adjustment to the UE; and receiving a signal associated with the UE via an uplink channel, the signal including an OFDM waveform based on the third indication of the timing adjustment.

[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving signaling including a CDMA signal and an OFDM signal via an uplink channel, wherein receiving the CDMA signal may be based on processing the signaling.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, an uplink channel includes a set of multiple CDMA subchannels based on one or more parameters of a CDMA transmission.

[0036] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: uplink transmission from the UE to the network entity may be asynchronous transmission, and downlink transmission from the network entity to the UE may be synchronous transmission.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a UE and a network entity communicate via an NTN. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 An example of a wireless communication system supporting concurrent code division and frequency division signaling via an uplink channel in accordance with one or more aspects of the present disclosure is illustrated.

[0039] Figure 2 An example of a wireless communication system supporting concurrent code division and frequency division signaling via an uplink channel in accordance with one or more aspects of the present disclosure is illustrated.

[0040] Figure 3A and Figure 3B An example of a channel configuration supporting concurrent code division and frequency division signaling via an uplink channel in accordance with one or more aspects of the present disclosure is illustrated.

[0041] Figure 4An example of a process flow supporting concurrent code division and frequency division signaling via an uplink channel in accordance with one or more aspects of the present disclosure is illustrated.

[0042] Figure 5 and Figure 6 A block diagram of an apparatus supporting concurrent code and frequency division signaling via an uplink channel in accordance with one or more aspects of the present disclosure is shown.

[0043] Figure 7 A block diagram of a communications manager supporting concurrent code and frequency division signaling via an uplink channel is shown in accordance with one or more aspects of the present disclosure.

[0044] Figure 8 A diagram of a system including a device supporting concurrent code and frequency division signaling via an uplink channel is shown in accordance with one or more aspects of the present disclosure.

[0045] Fig. 9 and Fig.10 A block diagram of an apparatus supporting concurrent code and frequency division signaling via an uplink channel in accordance with one or more aspects of the present disclosure is shown.

[0046] Fig.11 A block diagram of a communications manager supporting concurrent code and frequency division signaling via an uplink channel is shown in accordance with one or more aspects of the present disclosure.

[0047] Fig.12 A diagram of a system including a device supporting concurrent code and frequency division signaling via an uplink channel is shown in accordance with one or more aspects of the present disclosure.

[0048] Figures 13 to 16 A flow chart illustrating a method of supporting concurrent code division and frequency division signaling via an uplink channel according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0049] In some implementations or networks (e.g., in non-terrestrial networks), there may be a propagation delay between a user equipment (UE) and a network entity. The UE may communicate with the network entity using an orthogonal frequency division multiplexing (OFDM)-based waveform (e.g., orthogonal frequency division multiple access (OFDMA) signaling). The decoding of the OFDM waveform may use synchronization between the UE and the network entity in order to maintain the orthogonality of the waveform. Such synchronization may be supported by a global navigation satellite system (GNSS), because the GNSS may provide accurate positioning information that may be used to calculate a timing advance for performing uplink transmissions. Thus, UEs in a coverage area of ​​a network entity may remain synchronized with the network entity. For example, a UE positioned farther away from a network entity (e.g., on a cell edge) may determine a larger timing advance (e.g., in order to maintain synchronization or similar timing for signals received at the network entity) than a UE positioned closer to the network entity.

[0050] In some cases, the UE may not have the capability to use GNSS (e.g., may be a low-tier UE), may have GNSS turned off (e.g., to save power), may not be able to access GNSS services (e.g., due to the location of the UE), or may not be able to use GNSS. Without GNSS, the UE may not be able to achieve uplink synchronization at a receiver of a network entity (e.g., for a network entity that is located relatively far from the UE), thereby destroying the orthogonality of the OFDM waveform. In such cases, communication methods that use synchronization between devices (e.g., OFDM waveforms) may experience reduced reliability, reduced communication quality, increased interference between transmissions, or any combination thereof.

[0051] Techniques, methods, and apparatus described herein allow a UE to perform asynchronous communications using a waveform based on code division multiple access (CDMA), such that the UE can communicate with a network entity (e.g., a non-terrestrial or terrestrial network entity) without using GNSS. The UE can indicate to the network entity an ability to communicate using a CDMA waveform, and can use the CDMA waveform based on sending the indication. The UE can also receive one or more parameters associated with using the CDMA waveform, such as via system information, and can use the CDMA waveform based on the one or more parameters. The CDMA waveform can be sent via an uplink channel, which can be shared with an OFDM waveform (e.g., sent by one or more other UEs).

[0052] In some cases, an uplink channel used for CDMA transmission may be divided into CDMA sub-channels for CDMA transmission. In some cases, a UE communicating using a CDMA waveform may cause interference to other UEs in the network that do not communicate using CDMA (e.g., using an OFDM waveform). Therefore, a network entity may monitor the interference or load of the system and may instruct the UE to stop using the CDMA waveform when the load exceeds a threshold. The uplink channel may be a random access channel (RACH) and may support RACH transmissions, or may be a data channel and support data transmissions. In some cases, the UE may transition from CDMA to OFDMA transmissions after establishing a timing adjustment with the network.

[0053] Various aspects of the present disclosure are first described in the context of a wireless communication system. Additional wireless communication systems, channel configurations, and process flows are provided to describe various aspects of the present disclosure. Various aspects of the present disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flow charts related to concurrent code division and frequency division signaling via an uplink channel.

[0054] Figure 1 An example of a wireless communication system 100 that supports concurrent code division and frequency division signaling via an uplink channel in accordance with one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

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

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

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

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

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

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

[0061] The split of functionality between CU 160, DU 165, and RU 170 is flexible and may support different functionality 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 functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating via those communication links.

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

[0063] Where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support concurrent code division and frequency division signaling via uplink channels as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

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

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

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

[0067] The signal waveform transmitted via the carrier may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as OFDM or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where 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 coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0068] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period. Seconds, for this can represent the supported subcarrier spacing, and The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames, each radio frame having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0069] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended to the front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of 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 may depend on the subcarrier spacing or the operating frequency band.

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

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

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

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

[0074] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement 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 geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

[0075] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for UEs 115 include entering a power saving deep sleep mode when not engaged in active communications, operating using limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a subcarrier or resource block (RB) set) within a carrier, within a guard band of a carrier, or outside a carrier.

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

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

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

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

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

[0081] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas, which can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO 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, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a set of antenna ports of multiple rows and columns that the network entity 105 can use to support beamforming for communication with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

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

[0083] In some implementations, a non-terrestrial network entity (e.g., a satellite) may be an example of a network entity 105. There may be propagation delays (e.g., for non-terrestrial networks or other networks) between the UE 115 and the network entity 105. In some cases, the non-terrestrial network may be used for the delivery of small data services, such as text messaging (e.g., emergency messaging) for UE 115 outside of terrestrial network coverage, or IoT services.

[0084] In some examples, the propagation delay between the UE 115 and the non-terrestrial network entity 105 (e.g., or other network entities 105) may span several milliseconds, while the propagation delay between the UE 115 and the terrestrial network entity 105 may be one microsecond or more (e.g., on the order of microseconds). The UE 115 may communicate with the network entity using an OFDM-based waveform (e.g., OFDMA signaling), which may include pre-coding the waveform using DFT-S-OFDM. Such OFDM coding may use synchronization across UEs 115 (e.g., synchronization between the UE 115 and the network entity 105) within the coverage area 110 of the corresponding network entity 105 in order to maintain orthogonality of the waveform.

[0085] Such synchronization may be supported by GNSS, as GNSS may provide accurate positioning information that may be used to calculate a timing advance for performing uplink transmissions. Thus, UEs 115 in coverage area 110 may remain synchronized with respective network entities 105. For example, a UE 115 located further away from network entity 105 (e.g., on a cell edge) may determine a larger timing advance (e.g., in order to maintain synchronization with signals received at network entity 105, such as similar timing) than a UE 115 located closer to network entity 105.

[0086] In some cases, the UE 115 may not have the ability to use GNSS (e.g., may be a low-tier UE 115), may have GNSS turned off (e.g., to save power), may not have access to GNSS services (e.g., due to the location of the UE 115), may not be able to use GNSS, etc. In the absence of GNSS, the UE 115 may have difficulty achieving uplink synchronization at the receiver (e.g., for a network entity 105 that is located relatively far from the UE 115), thereby destroying the orthogonality of the waveform. In such cases, communication methods that use synchronization between devices (e.g., OFDM waveforms) may experience reduced reliability, reduced communication quality, increased interference between transmissions, or any combination thereof.

[0087] To support asynchronous transmission, UE 115 may transmit uplink communication using CDMA waveform, which may be transmitted without UE 115 being synchronized with network entity 105. UE 115 may transmit CDMA waveform via an uplink channel shared with UE 115 performing OFDM transmission. In some cases, an uplink channel for CDMA transmission may be divided into CDMA subchannels for CDMA transmission. In some cases, uplink transmission using CDMA may cause interference to OFDMA uplink transmission, and network entity 105 may use one or more metrics to monitor the load of the system. If the load of the system (e.g., interference caused by UE 115 using CDMA) exceeds a threshold, network entity 105 may limit CDMA transmission on the uplink channel. The uplink channel may be a RACH and may support RACH transmission, or may be a data channel and support data transmission. In some cases, after establishing a timing adjustment with the network, UE 115 may transition from CDMA to OFDMA transmission.

[0088] Figure 2 An example of a wireless communication system 200 that supports concurrent code division and frequency division signaling via an uplink channel according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 200 may be implemented by one or more aspects of the wireless communication system 100. For example, UE 115-a and UE 115-b may each be a wireless communication system as described in reference Figure 1 Additionally or alternatively, the network entity 105 - a (eg, a non-terrestrial network entity 105 , another type of network entity 105 ) may be as described in reference Figure 1 2. An example of a network entity 105 is shown. UE 115-a may communicate with network entity 105-a over an uplink communication link 205-a and a downlink communication link 210-a using an OFDM waveform. Similarly, UE 115-b may communicate with network entity 105-a over an uplink communication link 205-b using a CDMA waveform and a downlink communication link 210-b using an OFDM waveform. Network entity 105-a may send downlink messages 220 to UE 115-a and UE 115-b using OFDM waveforms.

[0089] In some examples, UE 115-a may operate with GNSS and UE 115-b may operate without GNSS, such that UE 115-b cannot be synchronized with network entity 105-a. Therefore, UE 115-a may perform uplink communications via an uplink channel using a single carrier or other OFDM waveform (e.g., including DFT-s-OFDM), while UE 115-b may perform uplink communications via an uplink channel using a CDMA waveform because the CDMA waveform may be multiplexed without synchronization (e.g., with incomplete or perfect synchronization). The uplink channel may be configured for one or more CDMA transmissions from a first set of UEs 115 (e.g., including UE 115-b) and one or more OFDMA transmissions from a second set of UEs 115 (e.g., including UE 115-a). For example, UE 115-a and UE 115-b may share the same channel, and UE 115-a and UE 115-b may communicate concurrently (e.g., at least partially concurrently) with network entity 105-a. For example, an uplink message 230 sent by UE 115-b using a CDMA waveform may not affect, or may have a relatively small impact on, an uplink message 215 sent by UE 115-a via the same channel using an OFDM waveform.

[0090] UE 115-a may establish a connection with network entity 105-a by sending an uplink message 215 using an OFDM waveform. Network entity 105-a may synchronize with UE 115-a based on uplink message 215 and send a downlink message 220-a on the OFDM waveform.

[0091] Prior to communicating using CDMA signals, the UE 115-b may send a capabilities message 235 to the network entity 105-a using OFDMA signals. The capabilities message 235 may indicate that the UE 115-b supports CDMA transmissions using an uplink channel shared with OFDMA transmissions. In some cases, the network entity 105-a may respond to the received capabilities message 235 by sending one or more parameters (e.g., CDMA code or channel allocation) for CDMA transmissions using the uplink channel, such as via a downlink message 220-b. Additionally or alternatively, the UE 115-b may receive the one or more parameters as part of system information prior to sending the capabilities message 235 (e.g., from the network entity 105-a or another network entity 105). Based on sending the capabilities message 235 indicating that the UE 115-b supports CDMA uplink transmissions using the uplink channel (e.g., after sending the capabilities message 235), the UE 115-b may send a CDMA uplink message 230 via the uplink channel using the one or more parameters.

[0092] In some cases, sharing an uplink channel between CDMA transmissions and OFDM transmissions (e.g., OFDMA transmissions) may cause an uplink message 230 sent by UE 115-b using a CDMA waveform to interfere with an uplink message 215 sent by UE 115-a using an OFDM waveform (e.g., or interfere with another OFDM-based uplink message from another UE 15). To mitigate or reduce such interference, the network entity 105-a may monitor the load (e.g., traffic, received power) of the uplink channel and may determine whether the uplink channel supports CDMA transmissions (e.g., in addition to OFDMA transmissions). Based on such a determination, the network entity 105-a may indicate to the UE 115-b via a load indication 225 to transmit or refrain from transmitting using the CDMA waveform. In some implementations, the UE 115-b may receive a load indication 225 from the network entity 105-a indicating that the uplink channel supports CDMA transmissions. In such cases, the UE 115-b may send the uplink message 230 based on receiving the load indication 225. In other specific implementations, the UE 115-b may receive a load indication 225 from the network entity 105-a via an uplink channel that limits CDMA transmissions (e.g., the load indication may be set). In such cases, the UE 115-b may refrain from sending CDMA signals via the uplink channel based on the load indication 225.

[0093] In some cases, the uplink message 230 may include a RACH preamble identifying the UE 115-b, and may also include data associated with the preamble (e.g., a capsule). In some cases, the UE 115-b may send the preamble and data together (e.g., with a short interval between the transmission of the preamble and the data) as part of the first message of the RACH process. The network entity 105-a may determine a search window size based on the received preamble and send a downlink message 220-b in response to the UE 115-b. In some cases, the UE 115-b may additionally or alternatively use a data channel to send data via the uplink message 230. For example, the UE 115-b may send data during a time period based on a propagation delay of transmissions between the UE 115-b and the network entity 105-a.

[0094] In some cases, the network entity 105-a may determine a timing adjustment for the UE 115-b and send the timing adjustment to the UE 115-b via the downlink communication link 210-b. For example, based on detection of use of a CDMA waveform via a data channel or based on the capability message 235, the network entity 105-a may communicate with one or more UEs 115 using a CDMA waveform and may determine a round-trip delay for each UE 115 communicating using the CDMA waveform. In some cases, the timing adjustment may include an absolute adjustment (e.g., for achieving a fast but coarse timing adjustment), a relative adjustment (e.g., for achieving a slow but fine timing adjustment), or both. The network entity 105-a may send an indication of the timing adjustment to a UE 115, such as the UE 115-b.

[0095] UE 115-b may use the received timing adjustment to establish accurate timing with network entity 105-a, thereby supporting synchronization with network entity 105-a. Thus, in some cases, UE 115-b may establish synchronization with network entity 105-a and send uplink messages to network entity 105-a using an OFDM waveform instead of a CDMA waveform (e.g., UE 115-b may determine to transmit the OFDM waveform after synchronization). In some cases, network entity 105-b may send a closed-loop command (e.g., an indication of the timing adjustment) to UE 115-b after a connection has been established (e.g., after a signal exchange), which may instruct UE 115-b to transition from transmission using the CDMA waveform to transmission using the OFDM waveform. In some examples, UE 115-b may use the CDMA waveform to send a small payload, or other relatively small or short messaging, before transitioning to the OFDM waveform (e.g., after synchronization with the network). Such transitions may support the network entity 105 - a in managing load and interference on the uplink channel (eg, by transitioning UEs 115 to an OFDM waveform so that a relatively low number of UEs 115 use a CDMA waveform).

[0096] In some cases, the network entity 105-a may include a receiver for processing a hybrid waveform. For example, the network entity 105-a may concurrently or sequentially process an OFDM waveform received from the UE 115-a using the receiver and a CDMA waveform received from the UE 115-b using the receiver. In one specific implementation, the receiver may remove the cyclic prefix of the OFDM waveform and perform a fast Fourier transform (FFT) on the entire bandwidth of the waveform. The receiver may select a subband for forming an M-ary vector based on the FFT, and may perform an inverse discrete Fourier transform (IDFT) on the M-ary vector and decode data from the resulting transform. Separately or concurrently, the receiver may filter the CDMA waveform using a low-pass filter. The receiver may process the filtered waveform in the time domain (e.g., remove pulse shaping) and decode data from the resulting waveform.

[0097] Figure 3A and Figure 3B Examples of channel configurations 300 and 350 that support concurrent code division and frequency division signaling via an uplink channel according to one or more aspects of the present disclosure are illustrated. In some examples, the channel configurations 300 and / or 350 may implement or be implemented by one or more aspects of the wireless communication system 100 or 200. For example, the channel configurations 300 and / or 350 may be used for an uplink channel shared by different UEs 115 using an OFDM waveform and a CDMA waveform, respectively, as described in reference to Figure 1 and Figure 2The uplink channels may include an OFDM uplink channel 305 and a CDMA uplink channel 310 . Figure 3A and Figure 3B A corresponding OFDM uplink channel 305 and a CDMA uplink channel 310 are shown as functions of frequency and power. The OFDM uplink channel 305 may use more power than the CDMA uplink channel 310 because a UE 115 using an OFDM waveform may have a higher data throughput and may use more power (e.g., based on the higher data throughput, based on one or more other parameters). A UE 115 using a CDMA waveform may transmit at a lower data rate and may therefore use less power than a UE operating with OFDM.

[0098] In channel configuration 300, CDMA uplink channel 310-a and OFDM uplink channel 305-a may each span the bandwidth of the uplink channel. In channel configuration 350 (e.g., based on the total channel bandwidth), CDMA uplink channel 310-b may be divided into multiple subchannels 330 (e.g., within the bandwidth of the uplink channel), while OFDM uplink channel 305-b may span the bandwidth of the uplink channel.

[0099] In some cases, the network entity 105 may serve the UE 115 using an OFDM waveform for uplink transmissions and serve the UE 115 using a CDMA waveform for uplink transmissions. The UE 115 using CDMA may share the same uplink channel with the UE 115 using OFDM. In some cases, the shared uplink channel may cause interference in the uplink transmissions (e.g., the CDMA transmissions may cause interference to the OFDM transmissions). Therefore, the network entity 105 may monitor the total load of the CDMA uplink channel 310 or subchannel 330, where the load may refer to the received power of the CDMA uplink channel 310 (e.g., at the network entity 105).

[0100] For example, the network entity 105 may analyze interference to a CDMA uplink channel 310-a or 310-b, or to a frequency band of an OFDM uplink channel 305 in which a single OFDM user may be active. In some cases, the network entity 105 may use a rise-over-thermal (RoT) metric to monitor the load and / or interference of the CDMA uplink channel 310. RoT may be defined as the total power in a receiver of the network entity 105 (e.g., received by the receiver) divided by the thermal noise power (e.g., the noise power in the receiver). The thermal level may depend on the temperature, and the temperature of a non-terrestrial network entity 105 (e.g., a satellite) may vary by a relatively high amount based on the received power. Thus, the open loop power control may inform the network entity 105 of the thermal noise (e.g., the varying thermal noise). Thus, in some cases, the network entity 105 may observe the RoT more reliably than the load of the uplink channel, because the load may be caused by a variety of factors, but the network entity 105 may not be able to identify some of these factors. Thus, RoT may be associated with or indicative of stability of an uplink channel or load of an uplink channel. If an uplink channel exceeds a load threshold (e.g., a RoT threshold), the system may become unstable and / or interference (e.g., interference generated by CDMA) may become unmanageable (e.g., relatively difficult to manage by the network entity 105).

[0101] For example, if an uplink channel experiences a relatively high level of interference (e.g., from CDMA transmissions), the transmitting UE 115 may attempt to transmit at a higher power so that the uplink signaling can be successfully received by the network entity 105. However, interference may also increase as each UE 115 increases transmit power. Therefore, in order to take action to reduce or manage interference levels, the network entity 105 may monitor the RoT to attempt to maintain the power level of the channel below a threshold (e.g., to ensure that the power level does not exceed the threshold).

[0102] In some cases, the link budget may constrain the RoT threshold and affect potential incoming users. Additionally or alternatively, the target signal to interference and noise ratio (SINR) for CDMA users may fluctuate due to imperfect power control, which may cause the RoT to also fluctuate. Such fluctuations may be amplified with high RoT. However, for a single CDMA or OFDM UE 115 (e.g., a single UE 115 transmitting within the bandwidth), a high RoT may be allowed. Therefore, if a single UE 115 (e.g., CDMA or OFDM) exists (e.g., transmits) within the bandwidth (e.g., a subchannel 330 or a portion of an uplink channel), the network entity 105 may allow a high RoT.

[0103] As described herein, the network entity 105 may monitor the RoT to determine if the RoT exceeds a threshold for the system (e.g., an uplink channel). In some cases, if the RoT is above a threshold (e.g., meets a threshold) for the CDMA uplink channel 310-a or one or more subchannels 330 of the CDMA uplink channel 310-b, the network entity 105 may broadcast an overload indication to each UE 115 (e.g., to each UE 115 associated with the uplink channel, to each UE 115 transmitting using CDMA). In some examples, UEs 115 using CDMA waveforms may monitor for overload indications from the network entity 105. If an overload indication is not set (e.g., not sent by the network entity 105), these UEs 115 may transmit using the CDMA waveform on the CDMA uplink channel 310.

[0104] In some cases, the network entity 105 may periodically broadcast a RoT indication message on a downlink communication channel, which may indicate whether the corresponding CDMA uplink channel 310 is available for CDMA transmission. For example, the network entity 105 may broadcast an indication message indicating that the CDMA uplink channel 310 is not available for CDMA transmission. In such a case, the UE 115 using the CDMA waveform may refrain from using the CDMA uplink channel 310 for transmission and may wait to transmit until the RoT is below a threshold. In some cases, the network entity may broadcast an indication message indicating that the CDMA uplink channel 310 is available for CDMA transmission (e.g., after previously indicating that the CDMA uplink channel 310 is not available). In such a case, the UE 115 using the CDMA waveform may transmit via the CDMA uplink channel 310 based on the indication message.

[0105] In some cases, for example, a UE 115 using an OFDM waveform may have a higher priority than a UE 115 using a CDMA waveform because a UE 115 using OFDM in a frequency band may have a relatively higher transmit power (e.g., and may also have a higher data throughput) than a UE 115 using CDMA. In some cases, the network entity 105 may be equipped with an advanced receiver, such as a receiver that supports interference cancellation and may therefore support removing interference from CDMA transmissions to OFDM transmissions. Such a receiver may support improved performance, for example, by supporting removal of CDMA interference (e.g., it may support a higher RoT threshold for an uplink channel). Because OFDM waveforms may be associated with higher receive powers, the network entity 105 may first decode the received OFDM waveforms and cancel these waveforms from the received signal (e.g., using interference cancellation capabilities). After removing the OFDM waveform from the signal, the CDMA waveform of the signal may be processed by the receiver (e.g., after the OFDM interference is canceled by the receiver).

[0106] In one specific implementation, the CDMA uplink channel 310 may be used for RACH transmissions from one or more UEs 115 to the network entity 105. The CDMA uplink channel 310 may, for example, support RACH channel transmissions because the CDMA uplink channel 310 may support asynchronous transmissions. If the CDMA uplink channel 310 is used for RACH transmissions, the UE 115 may transmit a RACH preamble 320 and data 325 as part of a first message 315 (e.g., which may be similar to message A (msgA)) of a two-step RACH process via the CDMA uplink channel 310. In some cases, the length of the RACH preamble 320 may be configured to accommodate the longest delay (e.g., longest propagation delay, worst-case delay) of a serving link between the UE 115 and the network entity 105. For example, over a series of uplink transmissions, the longest delay may be the longest time delay between the UE 115 and the network entity 105 for the series of transmissions, or may be the longest time delay for the series of transmissions plus an offset or buffer. Additionally or alternatively, each UE 115 served by the network entity 105 and using the CDMA waveform may experience delays in uplink transmissions, and the longest delay of the serving link may be the longest time delay among all UEs 115 using the CDMA waveform.

[0107] Multiple preamble formats (e.g., preamble bandwidth, duration) may be defined to accommodate various service link delays (e.g., delays within non-terrestrial networks), and in some cases, the network entity 105 may select one of the multiple preamble formats based on the longest delay. In some cases, the propagation delay may be estimated by reference signal received power (RSRP) measurements, and the length of the RACH preamble 320 may be based on the propagation delay. Based on the estimated propagation delay, the network entity 105 may adjust one or more timings to reduce the reception time difference between uplink signals from the UE 115 using the CDMA waveform.

[0108] The UE may send data 325 associated with the RACH preamble 320 in the capsule of the first message 315. In some cases, the data 325 may be sent entirely within the capsule of the first message 315. In some other cases, for example, if the data 325 exceeds the capsule size, the UE 115 may send a first portion of the data 325 via the capsule and a second portion of the data 325 via an advanced data channel.

[0109] A variety of capsule formats (e.g., capsule modulation and coding scheme (MCS), duration) may be configured to accommodate various data rates of the capsule. In addition, the UE 115 may include a UE identifier in the capsule (e.g., within the data 325). In some cases, the UE 115 may scramble the RACH preamble 320 and the data 325 using the same pseudo-random code (e.g., CDMA code). The mask of the pseudo-random code may be a function of a cell identifier, a time slot number, or other values. After sending the first message 315, the UE 115 may monitor for a random access response from the network entity 105. Therefore, the network entity may receive the first message 315 and determine a search window for monitoring the data 325 based on the received RACH preamble 320. The search window for the random access response may be based on the longest delay of the serving link (e.g., the search window duration may be longer than the longest round trip delay), and the UE 115 may monitor for a random access response message from the network entity 105 via an OFDM downlink channel.

[0110] In another specific implementation, the CDMA uplink channel 310 may be used for a data channel (e.g., the UE 115 may send an uplink message 315 via the data channel). The UE 115 may send the message 315 via the data channel with a fixed time offset (e.g., defined as a system-level parameter) from the transmission of the RACH channel. In such cases, the fixed offset may accommodate the longest round-trip delay of the service link as described herein. If the UE 115 receives an acknowledgment message (e.g., a random access response) for the transmission of the RACH channel, the UE 115 may send the message 315 via the data channel. In some cases, the UE may send a relatively small preamble 320 before (e.g., immediately before) the start of the data channel (e.g., the transmission of the data 325), wherein the preamble 320 may support a receiver at the network entity 105 to resynchronize the uplink timing of the UE 115. The resynchronization may reduce or mitigate timing delays that may occur during gaps between transmissions due to environmental factors (e.g., service link Doppler).

[0111] Figure 4 An example of a process flow 400 for supporting concurrent code division and frequency division signaling via an uplink channel according to one or more aspects of the present disclosure is illustrated. In some examples, the process flow 400 may be implemented as described in reference to Figure 1 and Figure 2 The wireless communication systems 100 and 200 described or referenced Figure 3A and Figure 3B One or more aspects of the channel configurations 300 and 350 described herein, or as described with reference to Figure 1 and Figure 2 The wireless communication systems 100 and 200 described or referenced Figure 3A and Figure 3B For example, UE 115-c may be an example of UE 115, and network entity 105-b may be an example of network entity 105, as described in reference to Figures 1 to 3B In the following description of process flow 400, operations between UE 115-c and network entity 105-b may be sent in an order different from the example order shown, or the operations performed may be performed in a different order or at a different time. Some operations may also be omitted from process flow 400, and other operations may be added to process flow 400.

[0112] At 405, UE 115-c may send an indication to network entity 105-b using an OFDMA signal that UE 115-c supports CDMA transmissions using an uplink channel. In some cases, the uplink channel may be configured for one or more CDMA transmissions from a set of UEs 115 including UE 115-c, and may also be configured for one or more OFDM transmissions from another set of UEs 115. In some cases, a CDMA transmission in one or more CDMA transmissions may be partially concurrent with an OFDM transmission in one or more OFDM transmissions. As described herein, the CDMA transmission may be at least partially concurrent with the OFDM transmission based on the CDMA transmission and the OFDM transmission at least partially overlapping in time. Additionally or alternatively, the CDMA transmission may be at least partially concurrent with the OFDM transmission based on the time period (e.g., TTI) in which the CDMA transmission is performed at least partially overlapping with the time period (e.g., TTI) in which the OFDM transmission is performed.

[0113] At 410, the UE 115-c may receive an indication of one or more parameters sent using CDMA of the uplink channel. In some cases, the parameters may be received as part of system information prior to 405. In some cases, the parameters may be received in response to the indication sent at 405.

[0114] The network entity 105-b may determine whether the received power level of the uplink channel satisfies a threshold power level at 415. The network entity 105-b may determine whether the threshold is satisfied based on the RoT of the uplink channel.

[0115] At 420, the network entity 105-b may send an indication that the uplink channel supports CDMA transmissions (e.g., an overload indication) based on determining that the received power level fails to meet the threshold power level. In some cases, the network entity 105-b may send an indication that the uplink channel does not support CDMA transmissions (e.g., an overload indication) based on determining that the received power level meets the threshold power level. The UE 115-c may determine whether to send a CDMA waveform via the uplink channel based on the overload indication. For example, the UE 115-c may use one or more parameters to send a CDMA signal via the uplink channel.

[0116] In some cases, at 425, the UE 115-c may send a first RACH message (e.g., MsgA) via the CDMA signal. The first message may include a RACH preamble and a capsule, which may include data transmission associated with the RACH preamble. The UE 115-c may send the RACH preamble, the capsule, or both during a time period based on a propagation delay of transmissions between the UE 115-c and the network entity 105-b.

[0117] At 430, in some cases, the network entity 105-b may receive a CDMA signal via an uplink channel. The network entity 105-b may process the signal, including detecting a RACH preamble. For example, the network entity 105-b may use the RACH preamble to receive an associated capsule.

[0118] In some cases, at 435, the network entity 105-b may send a second RACH message (e.g., MsgB) to the UE 115-c in response to the first RACH message. In some cases, at 440, the UE 115-c may send a CDMA signal carrying data via an uplink channel using the one or more parameters received at 410, where the CDMA signal may be a data signal sent via a data channel. In some cases, the UE 115-c may send the data at a time offset 445 from receiving the second RACH message (e.g., MsgB).

[0119] Figure 5 A block diagram 500 of a device 505 supporting concurrent code and frequency division signaling via an uplink channel according to one or more aspects of the present disclosure is shown. The device 505 may be an example of aspects of a UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0120] Receiver 510 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels associated with concurrent code and frequency division signaling via uplink channels), user data, control information, or any combination thereof. The information may be communicated to other components of device 505. Receiver 510 may utilize a single antenna or a collection of multiple antennas.

[0121] The transmitter 515 may provide means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels associated with concurrent code division and frequency division signaling via uplink channels), user data, control information, or any combination thereof. In some examples, the transmitter 515 may be co-located with the receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0122] The communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of concurrent code and frequency division signaling via uplink channels as described herein. For example, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may support methods for performing one or more of the functions described herein.

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

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

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

[0126] According to examples as disclosed herein, the communication manager 520 may support wireless communications at a UE. For example, the communication manager 520 may be configured to or otherwise support a component for sending a first indication to a network entity and using an OFDMA signal that the UE supports CDMA transmission using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, and the CDMA transmissions in the one or more CDMA transmissions are at least partially concurrent with the OFDMA transmissions in the one or more OFDMA transmissions. The communication manager 520 may be configured to or otherwise support a component for receiving a second indication of one or more parameters for CDMA transmission using an uplink channel. The communication manager 520 may be configured to or otherwise support a component for sending a CDMA signal via an uplink channel using the one or more parameters based on sending the first indication that the UE supports CDMA transmission using the uplink channel.

[0127] By including or configuring a communication manager 520 according to examples as described herein, a device 505 (eg, a processor controlling or otherwise coupled with a receiver 510, a transmitter 515, a communication manager 520, or a combination thereof) may support techniques for reduced power consumption.

[0128] Figure 6 A block diagram 600 of a device 605 supporting concurrent code division and frequency division signaling via an uplink channel according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of the device 505 or UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0129] The receiver 610 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels associated with concurrent code and frequency division signaling via uplink channels), user data, control information, or any combination thereof. The information may be communicated to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0130] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels associated with concurrent code division and frequency division signaling via uplink channels), user data, control information, or any combination thereof. In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0131] The device 605 or its various components may be examples of components for performing various aspects of concurrent code division and frequency division signaling via uplink channels as described herein. For example, the communication manager 620 may include a CDMA indication transmitter component 625, a parameter receiver component 630, a CDMA signal transmitter component 635, or any combination thereof. The communication manager 620 may be an example of various aspects of the communication manager 520 as described herein. In some examples, the communication manager 620 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the receiver 610, the transmitter 615, or both. For example, the communication manager 620 may receive information from the receiver 610, transmit information to the transmitter 615, or be integrated with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0132] According to examples as disclosed herein, the communication manager 620 may support wireless communications at a UE. The CDMA indication transmitter component 625 may be configured to or otherwise support a component for sending a first indication to a network entity and using an OFDMA signal that the UE supports CDMA transmission using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, and the CDMA transmissions in the one or more CDMA transmissions are at least partially concurrent with the OFDMA transmissions in the one or more OFDMA transmissions. The parameter receiver component 630 may be configured to or otherwise support a component for receiving a second indication of one or more parameters for CDMA transmission using an uplink channel. The CDMA signal transmitter component 635 may be configured to or otherwise support a component for sending a CDMA signal via an uplink channel using the one or more parameters based on sending the first indication that the UE supports CDMA transmission using the uplink channel.

[0133] Figure 7A block diagram 700 of a communication manager 720 supporting concurrent code division and frequency division signaling via an uplink channel in accordance with one or more aspects of the present disclosure is shown. The communication manager 720 may be an example of aspects of the communication manager 520, the communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of components for performing various aspects of concurrent code division and frequency division signaling via an uplink channel as described herein. For example, the communication manager 720 may include a CDMA indication transmitter component 725, a parameter receiver component 730, a CDMA signal transmitter component 735, a CDMA indication receiver component 740, a random access preamble transmitter component 745, a package transmitter component 750, a timing adjustment indication receiver component 755, a waveform transition component 760, a preamble transmitter component 765, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0134] According to examples as disclosed herein, the communication manager 720 may support wireless communications at a UE. The CDMA indication transmitter component 725 may be configured to or otherwise support a component for sending a first indication to a network entity and using an OFDMA signal that the UE supports CDMA transmission using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, and the CDMA transmissions in the one or more CDMA transmissions are at least partially concurrent with the OFDMA transmissions in the one or more OFDMA transmissions. The parameter receiver component 730 may be configured to or otherwise support a component for receiving a second indication of one or more parameters for CDMA transmission using an uplink channel. The CDMA signal transmitter component 735 may be configured to or otherwise support a component for sending a CDMA signal via an uplink channel using the one or more parameters based on sending the first indication that the UE supports CDMA transmission using the uplink channel.

[0135] In some examples, CDMA indication receiver component 740 may be configured or otherwise support means for receiving a third indication from a network entity that an uplink channel supports CDMA transmission, wherein transmitting the CDMA signal is based on receiving the third indication.

[0136] In some examples, CDMA indication receiver component 740 may be configured or otherwise support means for receiving a third indication from a network entity via an uplink channel to restrict CDMA transmission. In some examples, CDMA signal transmitter component 735 may be configured or otherwise support means for refraining from transmitting a second CDMA signal based on the third indication, wherein transmitting the CDMA signal is based on transmitting the CDMA signal that occurred prior to receiving the third indication.

[0137] In some examples, to support sending CDMA signals, random access preamble transmitter component 745 may be configured or otherwise support components for sending a random access preamble via a RACH. In some examples, to support sending CDMA signals, capsule transmitter component 750 may be configured or otherwise support components for sending a capsule including data transmission associated with the random access preamble via a RACH, wherein the UE sends the capsule during a time period based on a propagation delay of the transmission between the UE and a network entity.

[0138] In some examples, the propagation delay is based on RSRP measurements.

[0139] In some examples, the length of the random access preamble is based on the propagation delay.

[0140] In some examples, to support transmitting CDMA signals, the CDMA signal transmitter component 735 may be configured or otherwise support components for transmitting data via a data channel at a time offset from a RACH transmission, where the time offset is based on a propagation delay of the transmission between the UE and the network entity.

[0141] In some examples, the preamble transmitter component 765 may be configured as or otherwise support components for transmitting a preamble associated with data via a data channel and prior to transmission of the data, wherein the preamble is used to resynchronize uplink transmissions from the UE to a network entity.

[0142] In some examples, timing adjustment indication receiver component 755 may be configured or otherwise support means for receiving a third indication of a timing adjustment from a network entity. In some examples, waveform transition component 760 may be configured or otherwise support means for transitioning from transmitting a CDMA waveform via an uplink channel to transmitting an OFDM waveform via an uplink channel based on receiving the third indication.

[0143] In some examples, uplink transmissions from the UE to the network entity are asynchronous transmissions.

[0144] In some examples, the uplink channel includes a set of multiple CDMA subchannels based on one or more parameters of a CDMA transmission.

[0145] In some examples, the UE and the network entity communicate via the NTN.

[0146] Figure 8 A diagram of a system 800 including a device 805 supporting concurrent code division and frequency division signaling via an uplink channel according to one or more aspects of the present disclosure is shown. The device 805 may be an example of a device 505, a device 605, or a UE 115 as described herein or include a component of these devices or UEs. The device 805 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). The device 805 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, a code 835, and a processor 840. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 845).

[0147] The I / O controller 810 can manage the input and output signals of the device 805. The I / O controller 810 can also manage peripheral devices that are not integrated into the device 805. In some cases, the I / O controller 810 can represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 810 can utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX® or another known operating system. Additionally or alternatively, the I / O controller 810 can represent a modem, keyboard, mouse, touch screen or similar device or interact with these devices. In some cases, the I / O controller 810 can be implemented as a part of a processor (such as a processor 840). In some cases, a user can interact with the device 805 via the I / O controller 810 or via the hardware components controlled by the I / O controller 810.

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

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

[0150] The processor 840 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 840. The processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 830) to enable the device 805 to perform various functions (e.g., functions or tasks that support concurrent code division and frequency division signaling via an uplink channel). For example, the device 805 or a component of the device 805 may include a processor 840 and a memory 830 coupled to or coupled to the processor 840, and the processor 840 and the memory 830 are configured to perform the various functions described herein.

[0151] According to examples as disclosed herein, the communication manager 820 may support wireless communications at a UE. For example, the communication manager 820 may be configured to or otherwise support a component for sending a first indication to a network entity and using an OFDMA signal that the UE supports CDMA transmission using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, and the CDMA transmissions in the one or more CDMA transmissions are at least partially concurrent with the OFDMA transmissions in the one or more OFDMA transmissions. The communication manager 820 may be configured to or otherwise support a component for receiving a second indication of one or more parameters for CDMA transmission using an uplink channel. The communication manager 820 may be configured to or otherwise support a component for sending a CDMA signal via an uplink channel using the one or more parameters based on sending the first indication that the UE supports CDMA transmission using the uplink channel.

[0152] By including or configuring a communication manager 820 according to examples as described herein, the device 805 can support techniques for improving communication reliability, reducing latency, improving user experience related to reduced processing, reducing power consumption, and improving coordination between devices.

[0153] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 815, one or more antennas 825, or any combination thereof. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported or performed by the processor 840, the memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions executable by the processor 840 to cause the device 805 to perform various aspects of concurrent code division and frequency division signaling via an uplink channel as described herein, or the processor 840 and the memory 830 may be otherwise configured to perform or support such operations.

[0154] Fig. 9 A block diagram 900 of a device 905 supporting concurrent code division and frequency division signaling via an uplink channel according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0157] The communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of concurrent code and frequency division signaling via uplink channels as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may support methods for performing one or more of the functions described herein.

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

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

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

[0161] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a network entity. For example, the communication manager 920 may be configured to or otherwise support a component for receiving, via an OFDMA signal, a first indication that the UE supports CDMA transmission using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, and the CDMA transmissions in the one or more CDMA transmissions are at least partially concurrent with the OFDMA transmissions in the one or more OFDMA transmissions. The communication manager 920 may be configured to or otherwise support a component for sending a second indication of one or more parameters for the CDMA transmission using the uplink channel. The communication manager 920 may be configured to or otherwise support a component for receiving a CDMA signal via an uplink channel using the one or more parameters based on receiving the first indication that the UE supports CDMA transmission using the uplink channel.

[0162] By including or configuring a communication manager 920 according to examples as described herein, a device 905 (eg, a processor controlling or otherwise coupled with a receiver 910, a transmitter 915, a communication manager 920, or a combination thereof) may support techniques for reduced power consumption.

[0163] Fig.10A block diagram 1000 of a device 1005 supporting concurrent code division and frequency division signaling via an uplink channel according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the device 905 or network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0166] The device 1005 or its various components may be examples of components for performing various aspects of concurrent code division and frequency division signaling via an uplink channel as described herein. For example, the communication manager 1020 may include a CDMA indication receiver component 1025, a parameter transmitter component 1030, a signal receiver component 1035, or any combination thereof. The communication manager 1020 may be an example of various aspects of the communication manager 920 as described herein. In some examples, the communication manager 1020 or its various components may be configured to use or otherwise cooperate with the receiver 1010, the transmitter 1015, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 1020 may receive information from the receiver 1010, transmit information to the transmitter 1015, or be integrated with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0167] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a network entity. The CDMA indication receiver component 1025 may be configured to or otherwise support a component for receiving, via an OFDMA signal, a first indication that the UE supports CDMA transmission using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, and the CDMA transmissions in the one or more CDMA transmissions are at least partially concurrent with the OFDMA transmissions in the one or more OFDMA transmissions. The parameter transmitter component 1030 may be configured to or otherwise support a component for sending a second indication of one or more parameters for CDMA transmission using the uplink channel. The signal receiver component 1035 may be configured to or otherwise support a component for receiving a CDMA signal via an uplink channel using the one or more parameters based on receiving the first indication that the UE supports CDMA transmission using the uplink channel.

[0168] Fig.11A block diagram 1100 of a communication manager 1120 supporting concurrent code division and frequency division signaling via an uplink channel in accordance with one or more aspects of the present disclosure is shown. The communication manager 1120 may be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of means for performing various aspects of concurrent code division and frequency division signaling via an uplink channel as described herein. For example, the communication manager 1120 may include a CDMA indication receiver component 1125, a parameter transmitter component 1130, a signal receiver component 1135, a power level determination component 1140, a CDMA indication transmitter component 1145, a received power level determination component 1150, a random access preamble receiver component 1155, a capsule receiver component 1160, a timing adjustment indication receiver component 1165, a preamble receiver component 1170, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0169] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity. The CDMA indication receiver component 1125 may be configured to or otherwise support a component for receiving, via an OFDMA signal, a first indication that the UE supports CDMA transmission using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, and the CDMA transmissions in the one or more CDMA transmissions are at least partially concurrent with the OFDMA transmissions in the one or more OFDMA transmissions. The parameter transmitter component 1130 may be configured to or otherwise support a component for sending a second indication of one or more parameters for CDMA transmission using the uplink channel. The signal receiver component 1135 may be configured to or otherwise support a component for receiving a CDMA signal via an uplink channel using the one or more parameters based on receiving the first indication that the UE supports CDMA transmission using the uplink channel.

[0170] In some examples, power level determination component 1140 can be configured to or otherwise support means for determining whether a received power level of an uplink channel satisfies a threshold power level. In some examples, CDMA indication transmitter component 1145 can be configured to or otherwise support means for transmitting a third indication that the uplink channel supports CDMA transmission based on determining that the received power level fails to satisfy the threshold power level, wherein receiving the CDMA signal is based on transmitting the third indication.

[0171] In some examples, received power level determining component 1150 may be configured to or otherwise support means for determining whether a received power level of an uplink channel satisfies a threshold power level. In some examples, CDMA indication receiver component 1125 may be configured to or otherwise support means for sending a third indication to the UE via the uplink channel to restrict CDMA transmissions based on determining that the received power level of the uplink channel satisfies the threshold power level.

[0172] In some examples, power level determination component 1140 may be configured as or otherwise support components for determining whether a received power level of an uplink channel satisfies a threshold power level based on the ability of the network entity's receiver to detect and cancel interference, where the threshold power level is based on the capabilities of the network entity's receiver.

[0173] In some examples, to support receiving CDMA signals, random access preamble receiver component 1155 may be configured or otherwise support components for receiving a random access preamble associated with the UE via a RACH. In some examples, to support receiving CDMA signals, capsule receiver component 1160 may be configured or otherwise support components for receiving a capsule including a data transmission associated with the random access preamble via a RACH, wherein the network entity receives the capsule during a time period based on a propagation delay of the transmission between the UE and the network entity.

[0174] In some examples, the propagation delay is based on RSRP measurements.

[0175] In some examples, the length of the random access preamble is based on the propagation delay.

[0176] In some examples, signal receiver component 1135 may be configured or otherwise support components for receiving data via a data channel at a time offset from a RACH transmission, where the time offset is based on a propagation delay of transmissions between the UE and a network entity.

[0177] In some examples, preamble receiver component 1170 may be configured or otherwise support components for receiving a preamble associated with data via a data channel and prior to receipt of the data, wherein the preamble is used to resynchronize uplink transmissions from the UE to a network entity.

[0178] In some examples, timing adjustment indication receiver component 1165 may be configured or otherwise support means for sending a third indication of a timing adjustment to the UE. In some examples, signal receiver component 1135 may be configured or otherwise support means for receiving a signal associated with the UE via an uplink channel, the signal comprising an OFDM waveform based on the third indication of the timing adjustment.

[0179] In some examples, signal receiver component 1135 may be configured or otherwise support components for receiving signaling including a CDMA signal and an OFDM signal via an uplink channel, wherein receiving the CDMA signal is based on processing the signaling.

[0180] In some examples, the uplink channel includes a set of multiple CDMA subchannels based on one or more parameters of a CDMA transmission.

[0181] In some examples, uplink transmissions from the UE to the network entity are asynchronous transmissions, and downlink transmissions from the network entity to the UE are synchronous transmissions.

[0182] In some examples, the UE and the network entity communicate via the NTN.

[0183] Fig.12 A diagram of a system 1200 including a device 1205 supporting concurrent code division and frequency division signaling via an uplink channel according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of a device 905, a device 1005, or a network entity 105 as described herein or include a component of these devices or network entities. The device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1205 may include components that support output and acquisition of communications, such as a communication manager 1220, a transceiver 1210, an antenna 1215, a memory 1225, a code 1230, and a processor 1235. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1240).

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

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

[0186] The processor 1235 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1235. The processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1225) to enable the device 1205 to perform various functions (e.g., functions or tasks that support concurrent code division and frequency division signaling via an uplink channel). For example, the device 1205 or a component of the device 1205 may include a processor 1235 and a memory 1225 coupled to the processor 1235, and the processor 1235 and the memory 1225 are configured to perform various functions described herein. Processor 1235 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 may host functionality (e.g., by executing code 1230 ) to perform the functionality of device 1205 .

[0187] In some examples, bus 1240 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1240 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1205, or communications performed between different components of device 1205 that may be co-located or located in different locations (e.g., where device 1205 may refer to a system in which one or more of communication manager 1220, transceiver 1210, memory 1225, code 1230, and processor 1235 may be located in one component of different components or divided between different components).

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

[0189] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network entity. For example, the communication manager 1220 may be configured to or otherwise support a component for receiving, via an OFDMA signal, a first indication that the UE supports CDMA transmission using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, and the CDMA transmissions in the one or more CDMA transmissions are at least partially concurrent with the OFDMA transmissions in the one or more OFDMA transmissions. The communication manager 1220 may be configured to or otherwise support a component for sending a second indication of one or more parameters for the CDMA transmission using the uplink channel. The communication manager 1220 may be configured to or otherwise support a component for receiving a CDMA signal via an uplink channel using the one or more parameters based on receiving the first indication that the UE supports CDMA transmission using the uplink channel.

[0190] By including or configuring a communication manager 1220 according to examples as described herein, the device 1205 can support techniques for improving communication reliability, reducing latency, improving user experience associated with reduced processing, reducing power consumption, and improving coordination between devices.

[0191] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the processor 1235, the memory 1225, the code 1230, the transceiver 1210, or any combination thereof. For example, the code 1230 may include instructions executable by the processor 1235 to cause the device 1205 to perform various aspects of concurrent code division and frequency division signaling via an uplink channel as described herein, or the processor 1235 and the memory 1225 may be otherwise configured to perform or support such operations.

[0192] Fig.13 A flow chart illustrating a method 1300 for supporting concurrent code division and frequency division signaling via an uplink channel according to one or more aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE 115 as described in reference to Figures 1 to 8In some examples, the UE may execute instruction sets to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0193] At 1305, the method may include: sending a first indication to a network entity and using an OFDMA signal that the UE supports CDMA transmissions using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, the CDMA transmissions in the one or more CDMA transmissions being at least partially concurrent with the OFDMA transmissions in the one or more OFDMA transmissions. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Figure 7 The CDMA indication transmitter component 725 is executed.

[0194] At 1310, the method may include receiving a second indication of one or more parameters for a CDMA transmission using an uplink channel. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference to Figure 7 The parameter receiver component 730 is used to execute.

[0195] At 1315, the method may include: sending a CDMA signal via the uplink channel using one or more parameters based on sending a first indication that the UE supports CDMA transmission using the uplink channel. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed as described in reference to Figure 7 The CDMA signal transmitter component 735 is used to perform.

[0196] Fig.14 A flow chart illustrating a method 1400 for supporting concurrent code division and frequency division signaling via an uplink channel according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE 115 as described in reference to Figures 1 to 8 In some examples, the UE may execute instruction sets to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0197] At 1405, the method may include: sending a first indication to a network entity and using an OFDMA signal that the UE supports CDMA transmissions using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, the CDMA transmissions in the one or more CDMA transmissions being at least partially concurrent with the OFDMA transmissions in the one or more OFDMA transmissions. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 7 The CDMA indication transmitter component 725 is executed.

[0198] At 1410, the method may include: receiving a third indication from a network entity that the uplink channel supports CDMA transmission, wherein transmitting the CDMA signal is based on receiving the third indication. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference Figure 7 The CDMA instructions receiver component 740 is executed.

[0199] At 1415, the method may include receiving a second indication of one or more parameters for CDMA transmission using an uplink channel. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Figure 7 The parameter receiver component 730 is used to execute.

[0200] At 1420, the method may include: sending a CDMA signal via the uplink channel using one or more parameters based on sending a first indication that the UE supports CDMA transmission using the uplink channel. The operations of 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed as described in reference to Figure 7 The CDMA signal transmitter component 735 is used to perform.

[0201] Fig.15 A flow chart illustrating a method 1500 for supporting concurrent code division and frequency division signaling via an uplink channel according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 4 as well as Figures 9 to 12 The network entity described herein may be executed by the network entity described herein. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0202] At 1505, the method may include: receiving, via an OFDMA signal, a first indication that the UE supports CDMA transmissions using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, the CDMA transmissions in the one or more CDMA transmissions being at least partially concurrent with the OFDMA transmissions in the one or more OFDMA transmissions. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig.11 The CDMA indication receiver component 1125 is implemented.

[0203] At 1510, the method may include sending a second indication of one or more parameters for a CDMA transmission using an uplink channel. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig.11 The parameter transmitter component 1130 is used to perform.

[0204] At 1515, the method may include: receiving a CDMA signal via an uplink channel using one or more parameters based on receiving a first indication that the UE supports CDMA transmission using the uplink channel. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Fig.11 The signal receiver component 1135 is used to perform the above operation.

[0205] Fig.16 A flow chart illustrating a method 1600 for supporting concurrent code division and frequency division signaling via an uplink channel according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 4 as well as Figures 9 to 12 The network entity described herein may be executed by the network entity described herein. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0206] At 1605, the method may include: receiving, via an OFDMA signal, a first indication that the UE supports CDMA transmissions using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, the CDMA transmissions in the one or more CDMA transmissions being at least partially concurrent with the OFDMA transmissions in the one or more OFDMA transmissions. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.11 The CDMA indication receiver component 1125 is implemented.

[0207] At 1610, the method may include sending a second indication of one or more parameters for a CDMA transmission using an uplink channel. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig.11 The parameter transmitter component 1130 is used to perform.

[0208] At 1615, the method may include determining whether the received power level of the uplink channel satisfies a threshold power level. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig.11 The power level determination component 1140 described above is performed.

[0209] At 1620, the method may include: sending a third indication that the uplink channel supports CDMA transmission based on determining that the received power level fails to meet the threshold power level, wherein receiving the CDMA signal is based on sending the third indication. The operations of 1620 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Fig.11 The CDMA indication transmitter component 1145 is executed.

[0210] At 1625, the method may include: receiving a CDMA signal via an uplink channel using one or more parameters based on receiving a first indication that the UE supports CDMA transmission using the uplink channel. The operations of 1625 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1625 may be performed as described in reference to Fig.11 The signal receiver component 1135 is used to perform the above operation.

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

[0212] Aspect 1: A method for performing wireless communications at a UE, the method comprising: sending a first indication to a network entity and using an OFDMA signal that the UE supports CDMA transmission using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, and a CDMA transmission in the one or more CDMA transmissions is at least partially concurrent with an OFDMA transmission in the one or more OFDMA transmissions; receiving a second indication of one or more parameters for the CDMA transmission using the uplink channel; and sending a CDMA signal via the uplink channel using the one or more parameters based at least in part on sending the first indication that the UE supports the CDMA transmission using the uplink channel.

[0213] Aspect 2: According to the method of aspect 1, the method also includes: receiving a third indication from the network entity that the uplink channel supports the CDMA transmission, wherein sending the CDMA signal is at least partially based on receiving the third indication.

[0214] Aspect 3: According to the method described in any one of Aspects 1 to 2, the method further includes: receiving a third indication to limit the CDMA transmission from the network entity via the uplink channel; and suppressing the transmission of a second CDMA signal based at least in part on the third indication, wherein the transmission of the CDMA signal is at least in part based on the transmission of the CDMA signal occurring before receiving the third indication.

[0215] Aspect 4: A method according to any one of Aspects 1 to 3, wherein sending the CDMA signal further comprises: sending a random access preamble via a RACH; and sending a capsule including data associated with the random access preamble via the RACH, wherein the UE sends the capsule during a time period based at least in part on a propagation delay of the transmission between the UE and the network entity.

[0216] Aspect 5: The method according to aspect 4, wherein the propagation delay is based at least in part on RSRP measurement.

[0217] Aspect 6: The method according to any one of aspects 4 to 5, wherein the length of the random access preamble is based at least in part on the propagation delay.

[0218] Aspect 7: A method according to any one of Aspects 1 to 6, wherein sending the CDMA signal further comprises: sending data via a data channel at a time offset from the RACH transmission, wherein the time offset is at least partially based on a propagation delay of the transmission between the UE and the network entity.

[0219] Aspect 8: According to the method according to Aspect 7, the method also includes: sending a preamble associated with the data via the data channel and before sending the data, wherein the preamble is used to resynchronize uplink transmission from the UE to the network entity.

[0220] Aspect 9: According to the method described in any one of Aspects 1 to 8, the method also includes: receiving a third indication of timing adjustment from the network entity; and transitioning from sending a CDMA waveform via the uplink channel to sending an OFDM waveform via the uplink channel based at least in part on receiving the third indication.

[0221] Aspect 10: The method according to any one of aspects 1 to 9, wherein the uplink transmission from the UE to the network entity is asynchronous transmission.

[0222] Aspect 11: The method according to any one of aspects 1 to 10, wherein the uplink channel includes multiple CDMA sub-channels, and the multiple CDMA sub-channels are based at least in part on the one or more parameters of the CDMA transmission.

[0223] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the first UE and the network entity communicate via an NTN.

[0224] Aspect 13: A method for performing wireless communications at a network entity, the method comprising: receiving a first indication via an OFDMA signal that the UE supports CDMA transmissions using an uplink channel, wherein the uplink channel is configured for one or more CDMA transmissions from a first set of UEs and one or more OFDMA transmissions from a second set of UEs, and a CDMA transmission in the one or more CDMA transmissions is at least partially concurrent with an OFDMA transmission in the one or more OFDMA transmissions; sending a second indication of one or more parameters for the CDMA transmission using the uplink channel; and receiving a CDMA signal via the uplink channel using the one or more parameters based at least in part on receiving the first indication that the UE supports the CDMA transmission using the uplink channel.

[0225] Aspect 14: According to the method described in Aspect 13, the method also includes: determining whether the received power level of the uplink channel meets the threshold power level; and sending a third indication that the uplink channel supports the CDMA transmission based at least in part on determining that the received power level fails to meet the threshold power level, wherein receiving the CDMA signal is at least in part based on sending the third indication.

[0226] Aspect 15: According to the method described in any one of Aspects 13 to 14, the method further includes: determining whether the received power level of the uplink channel meets a threshold power level; and sending a third indication to the UE via the uplink channel to limit the CDMA transmission based at least in part on determining that the received power level of the uplink channel meets the threshold power level.

[0227] Aspect 16: According to the method of Aspect 15, the method also includes: determining whether the received power level of the uplink channel meets the threshold power level based at least in part on the ability of the receiver of the network entity to detect and eliminate interference, wherein the threshold power level is based at least in part on the ability of the receiver of the network entity.

[0228] Aspect 17: A method according to any one of Aspects 13 to 16, wherein receiving the CDMA signal includes: receiving a random access preamble associated with the UE via a RACH; and receiving a capsule including a data transmission associated with the random access preamble via the RACH, wherein the network entity receives the capsule during a time period based at least in part on a propagation delay of the transmission between the UE and the network entity.

[0229] Aspect 18: The method of aspect 17, wherein the propagation delay is based at least in part on RSRP measurements.

[0230] Aspect 19: The method according to any one of aspects 17 to 18, wherein the length of the random access preamble is based at least in part on the propagation delay.

[0231] Aspect 20: The method according to any one of aspects 13 to 19, the method further comprising: receiving data via a data channel at a time offset from the RACH transmission, wherein the time offset is at least partially based on a propagation delay of the transmission between the UE and the network entity.

[0232] Aspect 21: The method according to aspect 20 further comprises: receiving a preamble associated with the data via the data channel and before receiving the data, wherein the preamble is used to resynchronize uplink transmission from the UE to the network entity.

[0233] Aspect 22: According to the method described in any one of Aspects 13 to 21, the method further includes: sending a third indication of a timing adjustment to the UE; and receiving a signal associated with the UE via the uplink channel, the signal comprising an OFDM waveform based at least in part on the third indication of the timing adjustment.

[0234] Aspect 23: According to any one of aspects 13 to 22, the method further includes: receiving signaling including the CDMA signal and the OFDM signal via the uplink channel, wherein receiving the CDMA signal is at least partially based on processing the signaling.

[0235] Aspect 24: The method according to any one of aspects 13 to 23, wherein the uplink channel includes multiple CDMA sub-channels, and the multiple CDMA sub-channels are based at least in part on the one or more parameters of the CDMA transmission.

[0236] Aspect 25: The method according to any one of aspects 13 to 24, wherein uplink transmission from the UE to the network entity is asynchronous transmission, and downlink transmission from the network entity to the UE is synchronous transmission.

[0237] Aspect 26: The method according to any one of aspects 13 to 25, wherein the second UE and the network entity communicate via an NTN.

[0238] Aspect 27: An apparatus for performing wireless communications at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 12.

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

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

[0241] Aspect 30: An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 13 to 26.

[0242] Aspect 31: An apparatus for wireless communication at a network entity, the apparatus comprising: at least one component for performing the method according to any one of aspects 13 to 26.

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

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

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

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

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

[0248] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using one or more instructions or codes of 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 may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the functions are implemented at different physical locations.

[0249] Computer-readable media include both non-transient computer storage media and communication media, and the communication media include any media that facilitates the transfer of computer programs from one location to another.Non-transient storage media can be any available media that can be accessed by a general or special computer.By way of example and not limitation, non-transient computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage devices, disk storage devices or other magnetic storage devices, or can be used to carry or store desired program code components in the form of instructions or data structures and any other non-transient media that can be accessed by a general or special computer, or a general or special processor.Moreover, any connection is appropriately referred to as a computer-readable medium.For example, if software is sent 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 microwaves, coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwaves are included in the definition of computer-readable media. As used herein, disks and optical disks include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks can reproduce data magnetically, and optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

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

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

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

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

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

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: transmitting, to a network entity and using an orthogonal frequency division multiple access signal, a first indication that the UE supports code division multiple access transmissions using an uplink channel, wherein the uplink channel is configured for one or more code division multiple access transmissions from a first set of one or more UEs and one or more orthogonal frequency division multiple access transmissions from a second set of one or more UEs, a code division multiple access transmission of the one or more code division multiple access transmissions being at least partially concurrent with an orthogonal frequency division multiple access transmission of the one or more orthogonal frequency division multiple access transmissions; receiving a second indication of one or more parameters for the code division multiple access transmission using the uplink channel; as well as A code division multiple access signal is transmitted via the uplink channel using the one or more parameters based at least in part on transmitting the first indication that the UE supports the code division multiple access transmission using the uplink channel.

2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: A third indication is received from the network entity that the uplink channel supports the code division multiple access transmission, wherein sending the code division multiple access signal is based at least in part on receiving the third indication.

3. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: receiving, from the network entity via the uplink channel, a third indication to restrict the code division multiple access transmission; and Transmitting a second code division multiple access signal is refrained from based at least in part on the third indication, wherein transmitting the code division multiple access signal is based at least in part on transmitting the code division multiple access signal occurring prior to receiving the third indication.

4. The apparatus of claim 1, wherein the instructions for transmitting the code division multiple access signal are further executable by the processor to cause the apparatus to: transmitting a random access preamble via a random access channel; and A capsule including a data transmission associated with the random access preamble is transmitted via the random access channel, wherein the UE transmits the capsule during a time period based at least in part on a propagation delay of transmissions between the UE and the network entity.

5. The apparatus of claim 4, wherein the propagation delay is based at least in part on a reference signal received power measurement.

6. The apparatus of claim 4, wherein a length of the random access preamble is based at least in part on the propagation delay.

7. The apparatus of claim 1, wherein the instructions for transmitting the code division multiple access signal are further executable by the processor to cause the apparatus to: Data is transmitted via a data channel at a time offset from a random access channel transmission, wherein the time offset is based at least in part on a propagation delay of transmissions between the UE and the network entity.

8. The apparatus of claim 7, wherein the instructions are further executable by the processor to cause the apparatus to: A preamble associated with the data is transmitted via the data channel and prior to the transmission of the data, wherein the preamble is used to resynchronize uplink transmission from the UE to the network entity.

9. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: receiving a third indication of a timing adjustment from the network entity; and Based at least in part on receiving the third indication, transitioning from transmitting a code division multiple access waveform via the uplink channel to transmitting an orthogonal frequency division multiplexing waveform via the uplink channel.

10. The apparatus of claim 1, wherein the uplink transmission from the UE to the network entity is an asynchronous transmission.

11. The apparatus of claim 1, wherein the uplink channel comprises a plurality of code division multiple access subchannels, the plurality of code division multiple access subchannels being based at least in part on the one or more parameters of the code division multiple access transmission.

12. The apparatus of claim 1, wherein the UE and the network entity communicate via a non-terrestrial network.

13. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving, via an orthogonal frequency division multiple access signal, a first indication that a user equipment (UE) supports code division multiple access transmissions using an uplink channel, wherein the uplink channel is configured for one or more code division multiple access transmissions from a first set of one or more UEs and one or more orthogonal frequency division multiple access transmissions from a second set of one or more UEs, a code division multiple access transmission of the one or more code division multiple access transmissions being at least partially concurrent with an orthogonal frequency division multiple access transmission of the one or more orthogonal frequency division multiple access transmissions; sending a second indication of one or more parameters of the code division multiple access transmission using the uplink channel; as well as A code division multiple access signal is received via the uplink channel using the one or more parameters based at least in part on receiving the first indication that the UE supports the code division multiple access transmission using the uplink channel.

14. The apparatus of claim 13, wherein the instructions are further executable by the processor to cause the apparatus to: determining whether a received power level of the uplink channel satisfies a threshold power level; and Based at least in part on determining that the received power level fails to satisfy the threshold power level, a third indication is sent that the uplink channel supports the code division multiple access transmission, wherein receiving the code division multiple access signal is based at least in part on sending the third indication.

15. The apparatus of claim 13, wherein the instructions are further executable by the processor to cause the apparatus to: determining whether a received power level of the uplink channel satisfies a threshold power level; and A third indication is sent to the UE via the uplink channel to restrict the code division multiple access transmission based at least in part on determining that the received power level of the uplink channel satisfies the threshold power level.

16. The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to: Determining whether the received power level of the uplink channel satisfies the threshold power level based at least in part on an ability of a receiver of the network entity to detect and cancel interference, wherein the threshold power level is based at least in part on the ability of the receiver of the network entity.

17. The apparatus of claim 13, wherein the instructions for receiving the code division multiple access signal are executable by the processor to cause the apparatus to: receiving a random access preamble associated with the UE via a random access channel; and A capsule including a data transmission associated with the random access preamble is received via the random access channel, wherein the network entity receives the capsule during a time period based at least in part on a propagation delay of transmissions between the UE and the network entity.

18. The apparatus of claim 17, wherein the propagation delay is based at least in part on a reference signal received power measurement.

19. The apparatus of claim 17, wherein a length of the random access preamble is based at least in part on the propagation delay.

20. The apparatus of claim 13, wherein the instructions are further executable by the processor to cause the apparatus to: Data is received via a data channel at a time offset from a random access channel transmission, wherein the time offset is based at least in part on a propagation delay of transmissions between the UE and the network entity.

21. The apparatus of claim 20, wherein the instructions are further executable by the processor to cause the apparatus to: A preamble associated with the data is received via the data channel and prior to receipt of the data, wherein the preamble is used to resynchronize uplink transmissions from the UE to the network entity.

22. The apparatus of claim 13, wherein the instructions are further executable by the processor to cause the apparatus to: sending a third indication of a timing adjustment to the UE; and A signal associated with the UE is received via the uplink channel, the signal comprising an orthogonal frequency division multiplexing waveform based at least in part on the third indication of the timing adjustment.

23. The apparatus of claim 13, wherein the instructions are further executable by the processor to cause the apparatus to: Signaling including the code division multiple access signal and an orthogonal frequency division multiplexing signal is received via the uplink channel, wherein receiving the code division multiple access signal is based at least in part on processing the signaling.

24. The apparatus of claim 13, wherein the uplink channel comprises a plurality of code division multiple access subchannels based at least in part on the one or more parameters of the code division multiple access transmission.

25. The apparatus of claim 13, wherein uplink transmission from the UE to the network entity is asynchronous transmission, and downlink transmission from the network entity to the UE is synchronous transmission.

26. The apparatus of claim 13, wherein the UE and the network entity communicate via a non-terrestrial network.

27. A method for wireless communication at a user equipment (UE), the method comprising: transmitting, to a network entity and using an orthogonal frequency division multiple access signal, a first indication that the UE supports code division multiple access transmissions using an uplink channel, wherein the uplink channel is configured for one or more code division multiple access transmissions from a first set of one or more UEs and one or more orthogonal frequency division multiple access transmissions from a second set of one or more UEs, a code division multiple access transmission of the one or more code division multiple access transmissions being at least partially concurrent with an orthogonal frequency division multiple access transmission of the one or more orthogonal frequency division multiple access transmissions; receiving a second indication of one or more parameters for the code division multiple access transmission using the uplink channel; as well as A code division multiple access signal is transmitted via the uplink channel using the one or more parameters based at least in part on transmitting the first indication that the UE supports the code division multiple access transmission using the uplink channel.

28. The method according to claim 27, further comprising: A third indication is received from the network entity that the uplink channel supports the code division multiple access transmission, wherein sending the code division multiple access signal is based at least in part on receiving the third indication.

29. A method for wireless communication at a network entity, the method comprising: receiving, via an orthogonal frequency division multiple access signal, a first indication that a user equipment (UE) supports code division multiple access transmissions using an uplink channel, wherein the uplink channel is configured for one or more code division multiple access transmissions from a first set of one or more UEs and one or more orthogonal frequency division multiple access transmissions from a second set of one or more UEs, a code division multiple access transmission of the one or more code division multiple access transmissions being at least partially concurrent with an orthogonal frequency division multiple access transmission of the one or more orthogonal frequency division multiple access transmissions; sending a second indication of one or more parameters of the code division multiple access transmission using the uplink channel; as well as A code division multiple access signal is received via the uplink channel using the one or more parameters based at least in part on receiving the first indication that the UE supports the code division multiple access transmission using the uplink channel.

30. The method according to claim 29, further comprising: determining whether a received power level of the uplink channel satisfies a threshold power level; as well as Based at least in part on determining that the received power level fails to satisfy the threshold power level, a third indication is sent that the uplink channel supports the code division multiple access transmission, wherein receiving the code division multiple access signal is based at least in part on sending the third indication.

Images