Techniques for uplink capacity enhancements

Abstract

Various aspects of the present disclosure relate to techniques for preventing bidding down attacks. A user equipment (UE) is configured to receive, from a network entity, a configuration comprising a set of frequency domain orthogonal code sequences, each frequency domain orthogonal code sequence of the set of frequency domain orthogonal code sequences comprising a sequence length different than sequence lengths of other frequency domain orthogonal code sequences of the set of frequency domain orthogonal code sequences, select at least one frequency domain orthogonal code sequence from the set of frequency domain orthogonal code sequences, multiplex uplink (UL) data associated with the UE according to the selected at least one frequency domain orthogonal code sequence, transmit a waveform carrying the multiplexed UL data associated with the UE over a physical UL shared channel (PUSCH).

Description

TECHNIQUES FOR UPLINK CAPACITY ENHANCEMENTS TECHNICAL FIELD

[0001] The present disclosure relates to wireless communications, and more specifically to techniques for uplink (UL) capacity enhancements. BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, such as base stations, which may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)). SUMMARY

[0003] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” or “one or both of”) indicates an inclusive list such 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). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall beconstrued in the same manner as the phrase “based at least in part on.” Further, as used herein, including in the claims, a “set” may include one or more elements.

[0004] A UE for wireless communication is described. The UE may be configured to, capable of, or operable to receive, from a network entity, a configuration comprising a set of frequency domain orthogonal code sequences, each frequency domain orthogonal code sequence of the set of frequency domain orthogonal code sequences comprising a sequence length different than sequence lengths of other frequency domain orthogonal code sequences of the set of frequency domain orthogonal code sequences, select at least one frequency domain orthogonal code sequence from the set of frequency domain orthogonal code sequences, multiplex UL data associated with the UE according to the selected at least one frequency domain orthogonal code sequence, and transmit a waveform carrying the multiplexed UL data associated with the UE over a physical UL shared channel (PUSCH).

[0005] A method for wireless communication performed by a UE is described. The method may be configured to, capable of, or operable to receive, from a network entity, a configuration comprising a set of frequency domain orthogonal code sequences, each frequency domain orthogonal code sequence of the set of frequency domain orthogonal code sequences comprising a sequence length different than sequence lengths of other frequency domain orthogonal code sequences of the set of frequency domain orthogonal code sequences, select at least one frequency domain orthogonal code sequence from the set of frequency domain orthogonal code sequences, multiplex UL data associated with the UE according to the selected at least one frequency domain orthogonal code sequence, and transmit a waveform carrying the multiplexed UL data associated with the UE over a PUSCH.

[0006] A network equipment (NE) for wireless communication is described. The UE may be configured to, capable of, or operable to transmit, to a UE, an indication to apply orthogonal code sequences in a frequency domain, receive a PUSCH transmission with a selected at least one orthogonal code sequence applied to a waveform in the frequency domain, and multiplex PUSCH transmissions for a plurality of UEs based on the orthogonal code sequences in the frequency domain.

[0007] A method for wireless communication performed by a NE is described. The method may be configured to, capable of, or operable to transmit, to a UE, an indicationto apply orthogonal code sequences in a frequency domain, receive a PUSCH transmission with a selected at least one orthogonal code sequence applied to a waveform in the frequency domain, and multiplex PUSCH transmissions for a plurality of UEs based on the orthogonal code sequences in the frequency domain. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0009] Figure 2 illustrates an example of a PUSCH-Config RRC message in accordance with aspects of the present disclosure.

[0010] Figure 3A illustrates an example application of same orthogonal cover codes (OCC) sequence across multiple allocated resource blocks (RBs) for different UEs, in accordance with aspects of the present disclosure.

[0011] Figure 3B illustrates an example of application of the same OCC sequence across multiple allocated resource block groups (RBGs) for different UEs, in accordance with aspects of the present disclosure.

[0012] Figure 4A illustrates an example of application of OCC less than RB length across multiple scheduled RBs in accordance with aspects of the present disclosure.

[0013] Figure 4B illustrates an example of resource element (RE)-based scheduling when OCC is applied in accordance with aspects of the present disclosure.

[0014] Figure 5 illustrates an example of a UE in accordance with aspects of the present disclosure.

[0015] Figure 6 illustrates an example of a processor in accordance with aspects of the present disclosure.

[0016] Figure 7 illustrates an example of a NE in accordance with aspects of the present disclosure.

[0017] Figure 8 illustrates a flowchart of a method performed by a UE in accordance with aspects of the present disclosure.

[0018] Figure 9 illustrates a flowchart of a method performed by an NE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0019] A wireless communication system (e.g., a non-terrestrial network (NTN)), including one or more of UEs and NEs may support improved UL coverage, such as repetitions and demodulation reference signal (DMRS) bundling. In some cases, applying repetitions to wireless communication (e.g., UL transmission, downlink transmission) may significantly reduce a capacity of the wireless communication system, including throughput of the one or more UEs, by reducing resources available for data both for the one or more UEs, as well as for the entire wireless communication system (e.g., other UEs or NEs). Additionally, applying repetitions to wireless communication may increase latency of the wireless communication and, as a result, the one or more UEs may experience higher utilization of UL resources in a time domain before these resource can be released to other UEs.

[0020] As an example, in an NTN, a satellite may be configured with a broad geographic coverage area, which may result in numerous UEs being located within the geographic coverage area of the satellite. In some cases, such as wireless communication via a low earth orbit (LEO) satellite, several UEs within a geographic coverage area of the LEO satellite may have to coordinate with the LEO satellite (e.g., obtain access to the LEO satellite, obtain an allocation of resources from the LEO satellite, etc.) promptly to perform wireless communication (e.g., transmissions) while in the geographic coverage area of the LEO satellite. The limitation of total spectrum resources available to the NTN may further require significant system capacity efficiency improvements. For instance, some UEs may require higher resources than others, depending on traffic patterns, thus further granularity of resource multiplexing may be needed.

[0021] Various aspects of the present disclosure relate to enabling one or more UEs to support use of orthogonal cover codes (OCCs) for UL communication, which may result in increased UL capacity for the one or more UEs as described herein. Further aspects of the present disclosure relate to one or more configurations for applying OCC to a time domain UL data channel while employing Discrete Fourier Transform-Spread- Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveform.

[0022] Aspects of the present disclosure are described in the context of a wireless communications system.

[0023] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be an NR network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0024] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0025] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas 112 associated with thesame or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0026] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (IoT) device, an Internet-of-Everything (IoE) device, or machine-type communication (MTC) device, among other examples.

[0027] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0028] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., S1, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or TRPs.

[0029] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), anaccess and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0030] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an S1, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0031] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0032] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., ^=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., ^=0) associated with the first subcarrier spacing (e.g., 15 kHz) mayutilize one slot per subframe. A second numerology (e.g., ^=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., ^=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., ^=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., ^=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0033] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0034] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., ^=0, ^=1, ^=2, ^=3, ^=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., ^=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0035] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz – 7.125 GHz), FR2 (24.25 GHz – 52.6 GHz), FR3 (7.125 GHz – 24.25 GHz), FR4 (52.6 GHz – 114.25 GHz), FR4a or FR4-1 (52.6 GHz – 71 GHz), and FR5 (114.25 GHz – 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0036] FR1 may be associated with one or multiple numerologies (e.g., at least threenumerologies). For example, FR1 may be associated with a first numerology (e.g.,^=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., ^=1),which includes 30 kHz subcarrier spacing; and a third numerology (e.g., ^=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., ^=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., ^=3), which includes 120 kHz subcarrier spacing.

[0037] The solutions discussed herein relate to techniques for UL capacity enhancements. According to TS 38.300 (incorporated herein by reference), the downlink transmission waveform is a conventional orthogonal frequency division multiplexing (OFDM) using a Cyclic Prefix (CP). The UL transmission waveform is conventional OFDM using a CP with a transform precoding function performing discrete Fourier transform (DFT) spreading that can be disabled or enabled. For operation with shared spectrum channel access in FR1, the UL transmission waveform subcarrier mapping can map to subcarriers in one or more physical resource block (PRB) interlaces.

[0038] In one embodiment, two transmission schemes are supported for PUSCH: codebook-based transmission and non-codebook based transmission. For codebook- based transmission, the gNB provides the UE with a transmit precoding matrixindication in the downlink control information (DCI). The UE uses the indication to select the PUSCH transmit precoder from the codebook. For non-codebook-based transmission, the UE determines its PUSCH precoder based on wideband sounding reference signal (SRS) resource indicator (SRI) field from the DCI.

[0039] A closed loop DMRS based spatial multiplexing is supported for PUSCH. For a given UE, up to 4 layer transmissions are supported. The number of code words is one. When transform precoding is used, only a single multiple input- multiple output (MIMO) layer transmission is supported. Transmission durations from 1 to 14 symbols in a slot is supported and aggregation of multiple slots with transport block (TB) repetition is supported.

[0040] In one embodiment, two types of frequency hopping are supported, intra-slot frequency hopping, and in case of slot aggregation, inter-slot frequency hopping. Intra- slot and inter-slot frequency hopping are not supported when PRB interlace UL transmission waveform is used.

[0041] In one embodiment, PUSCH may be scheduled with DCI on physical downlink control channel (PDCCH), or a semi-static configured grant may be provided over radio resource control (RRC), where two types of operation are supported - the first PUSCH is triggered with a DCI, with subsequent PUSCH transmissions following the RRC configuration and scheduling received on the DCI, or the PUSCH is triggered by data arrival to the UE’s transmit buffer and the PUSCH transmissions follow the RRC configuration.

[0042] In one embodiment, the UL physical-layer processing of transport channels consists of the following steps - Transport Block CRC attachment; Code block segmentation and Code Block CRC attachment; Channel coding: LDPC coding; Physical-layer hybrid-ARQ processing; Rate matching; Scrambling; Modulation: π / 2 BPSK (with transform precoding only), QPSK, 16QAM, 64QAM and 256QAM; Layer mapping, transform precoding (enabled / disabled by configuration), and pre- coding; Mapping to assigned resources and antenna ports.

[0043] In one embodiment, the UE transmits at least one symbol with demodulation reference signal on each layer on each frequency hop in which the PUSCH is transmitted, and up to 3 additional DMRS can be configured by higher layers. Phase Tracking RS may be transmitted on additional symbols to aid receiver phase tracking. The UL-SCH physical layer model is described in TS 38.202, incorporated herein by reference.

[0044] For configured grants operation with shared spectrum channel access, described in clause 10.3, a Configured Grant UL Control Information (CG-UCI) can be transmitted in PUSCH scheduled by configured UL grant.

[0045] In one embodiment, according to 3GPP TS 38.211, up to two codewords q ∈^0,1^ can be transmitted. In case of single-codeword transmission, q = 0.

[0046] For each codeword, the block of bits b^^^^0^, … , b^^^^M^^^bit − 1^, whereM ^^^ bit is the number of bits in codeword qon the physical channel, shall be prior to modulation, resulting in a block of scrambled bits …, b^ ^^^^M^^^bit − 1^ according to the following pseudo code / / UCI placeholder bitselse if b( q)(i)^y / / UCI placeholder bitsb ~(q)~ (i)^b( q )(i ^1 )else b~(q)(i)^^b(q)(i)^c( q )( i)^mod 2end if end if i = i + 1 end while

[0047] where x and y are tags defined, e.g., in TS 38.212 (incorporated herein by reference) and where the scrambling sequence c^^^^i^ is given by clause 5.2.1. The scrambling sequence generator shall be initialized with cnRNTI ∙ 2^^ + nRAPID ∙ 2^^ + nID for msgA on PUSCHinit = ^n ∙ 2^^ + ^RNTI q ∙ 2 + nID otherwise

[0048] where nID ∈ ^0,1, … ,1023^ equals the higher-layer parameterdataScramblingIdentityPUSCH if configured and the RNTI equals the C-RNTI, MCS- C-RNTI, SP-CSI-RNTI or CS-RNTI, and the transmission is not scheduled using DCI format 0_0 in a common search space; nID ∈ ^0,1, … ,1023^ equals the higher-layerparameter msgA-DataScramblingIndex if configured and the PUSCH transmission is triggered by a Type-2 random access procedure as described in clause 8.1A of TS38.213 (incorporated herein by reference); n cellID = NID otherwise; nRAPID is the index ofthe random-access preamble transmitted for msgA as described in clause 5.1.3A of TS 38.321 (incorporated herein by reference) and where nRNTIequals the RA-RNTI for msgA and otherwise corresponds to the RNTI associated with the PUSCH transmission as described in clause 6.1 of TS 38.214 (incorporated herein by reference) and clause 8.3 of TS 38.213 (incorporated herein by reference).

[0049] For each codeword q, the block of scrambled bits b^ ^^^^0^, … , b^ ^^^^M^^^bit −1^shall be modulated as described in clause 5.1 using one inTable 6.3.1.2-1, resulting in a block of complex-valued modulation symbolsd^^^^0^, … , d^^^ ^M^^^symb − 1^.the complex-valued modulation symbols for each of thecodewords to be transmitted shall be mapped onto up to four layers according to Table7.3.1.3-1. Complex-valued modulation symbols d^^^^0^, … , d^^^ ^M^^^symb − 1^ forcodeword q shall be mapped onto the layers x^i^ =(T, i =0,1, … , M layersymb− 1 where υ is the number ofofper layer.

[0051] In one embodiment, if transform precoding is not enabled according to 6.1.3of TS 38.214, y(^)(i)^ x( ^ )(i)for each layer ^ ^0,1,..., ^ ^ 1.

[0052] If transform precoding isto 6.1.3 of TS38.214 (in, υ = 1andx% (0) ( i )depends on the configuration of phase-tracking reference signals.

[0053] If the procedure in TS 38.214 indicates that phase-tracking reference signalsare not being used, the block of complex-valued symbols x^^^^0^, … , x^^^ ^Mlayersymb − 1^for the single layer λ = 0 shall be divided into M layer PUSCHsymb+ Msc sets,to one OFDM symbol andx% (0)( i ) ^ x (0) ( i ).

[0054] If theindicates that phase-tracking reference signalsare being used, the block of complex-valued symbols x^^^^0^, … , x^^^ ^Mlayer − 1^ shallbe divided into sets, each set corresponding to one OFDM symbol,set lnsMPUSCH^^ Ngroup PTRScontaisc l samp N groupsymbols and is mapped to the complex-valued symbols to OFDM symbol l prior to transform precoding,1^ and i^ ^ m . The index m of PT-RS samples in set l , theperarmoup, and the number of PT-RS groups NgPrTo-uRpSpare defined in clause 6.4.1.2.2.2. The quantity ^l ^ 1 when OFDM symbol l contains oneor more PT-RS samples, otherwise^l ^ 0.

[0055] Transform precoding shallapplied according to M PUSCH^1 ^2^ iky (0) ( l ^ M PUSCH ^ k ) ^1 scj% (0) PUSCHM PUSCH sc sc ^ x ( l ^ M sc ^ i ) esymb −MPUSCH PUSCH RB PUSCH1^. The variable sc ^MRB ^ Nsc , where MRB represents theof thePUSCH in terms of resource blocks, and shall fulfill:

[0057] MRPUBSCH^2^^3^^ 5^

[0058] where^2,^3 , ^ 5is a set of non-negative integers.

[0059] the b % ^^^ ^&'^^ (Tlock of vectors y ^i^ … y ^i^ shall beprecoded according to z^34^^i^y^^^^i^9

[0060] where i =. The set of antenna ports;p , … , p='^> shall bein [6, TS 38.214]

[0061] For non-codebook-based transmission, the precoding matrix W equals the identity matrix.

[0062] For codebook-based transmission, the precoding matrix W depends on the number of antenna ports used for the transmission - for single-layer transmission on asingle antenna port, W = 1; for transmissions using 2, or 4 antenna ports, W is given byTables 6.3.1.5-1 to 6.3.1.5-7; for transmissions using 8 antenna ports, W is given byW?^@^ = W′@ where the subscripts i and f^i^ denote the row of the respective matrix; f^i^is given by Table 6.3.1.5-8; the intermediate precoding matrix W′ is given by Tables 6.3.1.5-9 to 6.3.1.5-24, 6.3.1.5-29 to 6.3.1.5-36, and 6.3.1.5-39 to 6.3.1.5-47 with 0B×Drepresenting the all-zero matrix with m rows and n columns; the submatrices WEB,Dare given by Tables 6.3.1.5-25 to 6.3.1.5-28 and 6.3.1.5-37 to 6.3.1.5-38.

[0063] The TPMI index used in the tables above is obtained from the DCI scheduling the UL transmission or the higher layer parameters according to the procedure in TS 38.214. When the higher-layer parameter txConfig is not configured,the precoding matrix W = 1.

[0064] In general, the subject matter herein describes configuration aspects for the frequency domain application of OCC for UL data channel capacity improvement while employing DFT-s-OFDM waveform. The resource allocation in the frequency domain is RB based, where a single RB or group of RBs are scheduled for the UE when transform precoding is enabled. The OCC sequences may be of variable length; however, the higher length codes may result in high power requirements or higher signaling overhead. One solution may be to have at least an RB length codes, where these codes need to be applied on multiple scheduled RBs. This may require additional signaling for the selection of codes and mapping of these codes to multiple scheduled RBs. Another scenario may be to have the OCC codes with length less than the RB length, but this may require mapping of these codes to resource elements (REs), whereas the scheduling is based on RBs. Therefore, this may require additional configuration aspects to correctly apply the codes. In this disclosure, we discuss the methods and corresponding configuration aspects to correctly apply the OCC in the frequency domain for OCC sequences of variable lengths.

[0065] According to a first embodiment, the network indicates to the UE to apply OCC in the frequency domain or not for the multiplexing of PUSCH transmission of multiple users, when transform precoding is enabled. According to the embodiment, the OCC on PUSCH transmission in the frequency domain is applied when the UL resource allocation schemes such as resource allocation type 1 or type 2 are enabled, e.g., enabled through RRC signaling using IE PUSCH-Config, as frequency resource allocation is only applied when transform precoding is disabled.

[0066] In one implementation, application of OCC for PUSCH transmission may be indicated through RRC signaling, while the selection of the sequence to be used may beexplicitly or implicitly indicated along with PUSCH resource allocation. For example, new fields in PUSCH-Config RRC message may be used to indicate whether frequency domain OCCs are to be used or not, as shown in Figure 2. Figure 2 illustrates an example of a PUSCH-Config RRC message in accordance with aspects of the present disclosure.

[0067] In one implementation, when multiple types of OCC sequences are defined as look-up tables, then the type of OCC to be applied for PUSCH transmission may also be indicated in the configuration. For example, two sets of OCC may be used in the time or frequency domain for PUSCH transmission, e.g., OCC based on DFT and OCC based on Walsh-Hadamard. Then alongside the information about the enabling / disabling of OCC 202, a field may be used to indicate which type of tables to be used for the selection of OCC sequence 204, for example using field frequncyDomainOCCType = ENUMERATED (DFT, Walsh-Hadamard). The OCC length and index for the selection OCC sequence may either be separately indicated or in the same configuration.

[0068] In one implementation, frequency domain OCC are applicable when transform precoding is enabled. Therefore, if transformPrecoder field is disabled in PUSCH-Config IE, then the information regarding OCC may not be considered. In case, ttransformPrecoder field is absent, then UE would look for msg3-transformPrecoder field and if that is enabled then only use the OCC fields in the PUSCH configuration.

[0069] In one embodiment, UE indicates to the network about its capabilities to support application of frequency domain OCC for PUSCH transmission, where this may be indicated by a specific field in IE Phy-Parameters (that is used to convey physical layer capabilities) during capability exchange messages through RRC signaling. Only if network knows that the UE has the capability to apply an OCC, then the network may configure OCC sequence to the UE. In one implementation, the UE also indicates about the maximum length of the code, it supports along with its capability to support the application of OCC in the frequency domain.

[0070] According to the length of frequency domain OCC codes, different methods of OCC applicability and corresponding configurations may be realized since the frequency resource allocation for PUSCH is based on allocation of one or multiple resource blocks (and is not based on configuring resource elements). In oneembodiment, when there are multiple length codes available, the OCC codes could be grouped based on their lengths, e.g., OCC codes less than RB length (e.g., namely OCC Type 1), RB length (e.g., namely OCC Type 2), and OCC codes greater than RB lengths (e.g., namely OCC Type 3), whereas the type of length codes that would be applied may be signaled either through DCI or through RCC signaling along with frequency domain resource allocation, e.g., in IE PUSCH-Config by a field.

[0071] According to a second embodiment, when the OCC length is at least equal to one RB, the network may configure the application of OCC in the frequency domain by implicit or explicit indication, where this indication includes at least a sequence index from the OCC look-up table, and the application pattern (i.e., if more than one RB is allocated, then how the OCC sequence is applied on multiple RBs). For example, only one OCC table of RB length is specified (or is configured) as shown in Table 1, and the network indicates one of the indices from the table that would be applied to at least one RB or on multiple RBs that are allocated as part of frequency domain resource allocation.Table 1: DFT based length 12 orthogonal sequences FG^H^ for FD-OCC based PUSCHIJI^K^0 %+1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1 +1(1 %+1 −M −1 +M +1 −M −1 +M +1 −M −1 +M(2 %+1 −1 +1 −1 +1 −1 +1 −1 +1 −1 +1 −1(3 %+1 +M −1 −M +1 +M −1 −M +1 +M −1 −M(

[0072] In one implementation, the network indicates the OCC sequence index from RB length OCC look-up table in the UL resource scheduling DCIs, e.g., in DCI 0_0, DCI 0_1, DCI 0_2 especially in case of dynamic scheduling, along with the resource vale indicator (RIV) to indicate the number of RBs allocation. In one implementation, the OCC sequence index from RB length OCC look-up table is indicated through RRC signaling, by using a field in IE PUSCH-Config or in IE ConfiguredGrantConfig.

[0073] In one embodiment, when the resource allocation is based on RB allocation (e.g., as is scheduled by DCI 0_1 for resource allocation type 1) and allocated frequency resources are more than one RB, whereas the OCC look-up table is also of RB length, then an application pattern for the use of one RB length OCC sequence on multiple RBsmay also be indicated, where this pattern may either be implicitly indicated or explicitly indicated by using a field in DCI or in RRC signaling.

[0074] In one implementation, when there is no indication that how an RB length OCC sequence is applied on multiple allocated RBs, then the UE would apply the same sequence on all of the RBs. For example, if a UE is configured with 10 RBs within from an UL BWP using allocation type 1 and one sequence index from the RB length table (e.g., as in Table 3), and no additional indication is present either in DCI or in RRC signaling, then the UE applies the same OCC sequence to all of the allocated RBs. In one implementation, a field may be used to indicate to the UE whether the same OCC sequence is to be applied to all allocated RBs or not. An example illustration of such application of OCC sequence is shown in Figure 3A. Figure 3A illustrates an example application of same OCC sequence across multiple allocated RBs for different UEs, in accordance with aspects of the present disclosure. In Figure 3A, the same frequency domain resources 302 are allocated to two UEs 304, 306, but are signalled to use different OCC sequences 308, 310 across the allocated RBs 302.

[0075] In one implementation, the applicability pattern of applying same or different OCC sequences of RB length to multiple allocated RBs is defined with the help of a mapping table, where the mapping table defines different pattern (pattern defining the selection of a sequence for each RB) that can be used for the application of OCC sequences from the table. The network may indicate to UE an index from the mapping table instead of an index from the OCC look-up table and UE would one the use the OCC sequence index according to defined applicability pattern.

[0076] In one implementation, the mapping table indicates the applicability pattern of different OCC sequences to the scheduled RBs may contain the combinations according to number of OCC sequences defined for RB length OCC. For example, if 12 OCC sequences are defined, then the mapping table would contain at least 12 combinations of applicability of OCC i.e., order of selection of a sequence. An example of such mapping table is shown in Table 2, where the combinations are based on number of OCC sequences in Table 1.

[0077] The combinations may be selected in way that the sequences are also orthogonal across RBs. In one example, when such OCC applicability on PUSCH frequency domain resources is configured, the maximum number of RB resourceallocation may correspond to the maximum number of sequences defined in a combination, e.g., 12 RBs in case 12 combinations are there in a sequence. In the event that less or fewer number of RBs are allocated, then UE may select the select the number of sequences according to the length starting from the first in the list. For example, if 3 RBs are schedules and index 1 from the reference look-up Table 2 is configured, then UE would apply sequence corresponding to index 1 from Table 1 to the first RB, the sequence corresponding to index 0 to the second RB, and the sequence corresponding to index 3 to the third RB. Table 2: Mapping table for RB based selection of orthogonal sequences corresponding to OCC in Table 1 Index Combinations 0 0,1,2,3 1 1,0,3,2 2 2,3,0,1 3 3,2,1,0

[0078] In one embodiment, when resource allocation is either based on RBs or based on resource block groups (RBG), the applicability of OCC sequences may be based on grouping of RBs. In case the resource allocation is based on RBs, the network may additionally indicate to the UE the number of RBs to be grouped for the purpose of applicability of OCC. Such applicability may provide network more flexibility to allocate different number of resources with reduced number of OCC sequence.

[0079] In this case, an OCC index (used to select an OCC sequence of RB length) may be applicable to a group of RBs which comprises of contiguous RBs and then the same or different sequences may be applicable to next group of RBs (still comprising of contiguous RBs but may or may not be contiguous to previous groups). Therefore, the applicability pattern (the pattern to apply OCC sequence) may be defined based on allocation of multiple RBGs instead of RBs. Basically, when such RBGs based OCC application pattern is scheduled then at least the same OCC sequence would be applied to all of the allocated RBs within the RBGs. An example of such scheduling is shown in Figure 3B. Figure 3B illustrates an example of application of the same OCC sequence across multiple allocated RBGs for different UEs, in accordance with aspects of the present disclosure. In the depicted embodiment, UEs 304, 306, 312 are grouped 314 for 4 RBs 302 and one sequence 316 is applied across the RBs 302 within the RBG 314.

[0080] In one implementation, the applicability pattern may be defined with the help of a mapping table and only index that selects a row from the table may be configured to UE either as part of DCI signaling or RRC signaling, where the entries in the row select the OCC sequence index in the order of applicability to the RBG. The mapping table may be formulated by having all the possible combinations of available number of OCC sequences to provide more flexibility to the network to apply OCC sequences to variable size frequency domain resource allocation.

[0081] An illustration of such a mapping table is shown in Table 3. In one implementation, the UE may not need to use all the sequence indices when configured from such mapping table rather the UE would use the number of sequence index corresponding to the number of allocated RBGs. Taking the example illustrated in Figure 3B, the first UE may be configured with 3 RBGs (or configured 12 RBs whereas additional indication is also included to group these RBs with consecutive 4 RBs) along with index 5 from Table 3, the UE would choose OCC sequences from Table 1 as 2,3,0 and apply those across 3 RBGs, whereas the UE would discard sequence index 1 as there are only 3 RBGs. The UE 2 is allocated with two RBGs and index 2. Similarly, the UE 2 would only select the sequences corresponding to index 0 and 2 from Table 1. Lastly, UE 3 is allocated with 3 RGBs and index 4 from Table 3. Note that all the overlapping frequency resources are orthogonal as different OCC sequences are used. Table 3: Mapping table for RBG based selection of orthogonal sequences corresponding to OCC in Table 1 Index Combinations 0 0,1,2,3 1 0,1,3,2 2 0,2,1,3 3 0,2,3,1 4 0,3,2,1 5 2,3,0,1 …. …..

[0082] In one implementation, the network may additionally indicate to the UE by DCI or RRC signaling or through MAC-CE that the application of OCC sequence is based on RBs or RBGs. The network has the flexibility to allocate frequency domain resources based either of RBs or RBGs using Type 1 or Type 2 allocation type and by employing either dynamic scheduling or by RRC signaling. Additionally, it may also be specified or indicated through signaling whether the configured pattern is applicableonly if contiguous RBGs are allocated RBGs or for both contiguous and non-contiguous allocated RBGs.

[0083] In one implementation, the applicability pattern is based of RBs within a RBG, whereas different RBGs may use the same pattern if the allocated length of RBs within RBG is same across different RBGs. Basically, a mapping table may be defined that indicates the applicability of multiple sequences within an RBG, e.g., similar to the mapping table defined for RBs as in Table 2 or Table 3. For this purpose, either one or different mapping tables may be defined according to the granularity of the allocated RBG size. In case, one table of maximum length of RBG is defined, then the UE may choose the sequences according to allocated number of RBs from the maximum length combinations for the configured index. Alternatively, the network may define the applicability mapping tables for RBG group size of 2, 4, 8, 16 (e.g., as is the size of RBG that is provided by RRC parameter ResourceAllocationType1-granularity- ForDCIFormat0_2 within PUSCH-Config IE). The network may only indicate the index from the table indicating which sequence may need to be applied, the UE may choose the corresponding table based on the RBG size.

[0084] In one implementation, different mapping types for the application of OCC sequence on one or multiple RBs may be signaled through RRC (e.g., in PUSCH-Config IE), where these mapping type indicates how the OCC would be applied, e.g., RB based (OCC Mapping Type 1), RBG based (OCC Mapping Type 2), or the like.

[0085] In one embodiment, when the OCC look-up tables (or when it is possible any length OCC sequence e.g., through DFT) of the scheduled RBs are available, then the network configures only the sequence selection index either through DCI or through RC signaling, whereas the corresponding table may be selected by the UE based on the number of elements in the configured RBs, e.g., if 2 RBs are configured, then 24 length table for OCC may be selected.

[0086] According to a third embodiment, when OCC lengths in the frequency domain are less than RB length (e.g., the OCC look-up tables corresponding to OCC sequences of less than length 12 are available), whereas the frequency domain resource allocation is RB (or RBG) based, then either a mapping strategy to apply the OCC sequences in an RB may be defined and configured (how less lengths OCC are applied if one or multiple RBs are configured) or a new scheduling scheme that is based onresource elements (RE) (e.g., may only be applicable when OCCs are applied in frequency domain) may be defined and configured.

[0087] In one embodiment, when there are multiple OCC look-up tables of variable lengths but less than RB length, then a mapping strategy to apply these lengths to at least an RB may be defined, where the same or different mapping strategies may be applied to multiple RBs that are configured as part of scheduling signaling through DCI or RRC signaling.

[0088] In one implementation, when OCC look-up tables of length 2, 4, and 6 are used, then same length OCC sequence may be repeated over the RB. The network may configure the OCC length to be used and also the index from the table to select the sequence in the PUSCH scheduling DCI or RRC configuration. Once the UE receives such configuration, the UE selects the OCC sequence and apply the same sequence over contiguous REs starting from the first RE within the RB and then same is applied across multiple RBs. For example, as shown in Figure 4A, which illustrates an example of application of OCC less than RB length across multiple scheduled RBs in accordance with aspects of the present disclosure, a UE 402 is scheduled with 10 RBs 404 starting from RB 14. Additionally, the UE 402 may also be configured to apply OCC with length 4 table 408 and sequence index of 2410. The UE 402 would apply the OCC sequence corresponding to the index 2 by grouping the REs of an RB 404 into set of four 406. The same may be repeated across all the scheduled RBs 404.

[0089] In one implementation, different mapping strategies to apply OCC to an RB may be defined as a look-up table, whereas an index is configured to select one of the mapping strategies and apply it one or multiple scheduled RBs (or RBGs). For example, if length 2,4, and 6 OCC sequences are employed, then the look-up table for such implementation would contain combinations such as (2,4,6), (2,2,4,4), (6,4,2), (6,6), and (4,6,2) corresponding to indices 0,1,2,3, and 4.

[0090] When a UE is configured with an index for such table, the UE would also receive indices to select the sequence from such tables. For example, if index 0 is received, then the UE would also receive the indices to select the sequences from look- up table of 2,4, and 6. The UE would apply those sequence in an order, e.g., apply on first 2 REs, the length 2 sequence, then on the next 4 REs the length 4 sequence is applied and finally on the next 6 REs the length 6 sequence is applied. The UE mayapply the same mapping strategy to all of the scheduled RBs, if otherwise configured by the network to apply different combinations of sequences to other RBs.

[0091] In one embodiment, the UE may be scheduled resources per RB, but when an OCC is to be applied, the UE may not use all of the REs of an RB. Basically, the scheduling is still RBs, but the UE is actually configured resource based on REs. For example, if a UE is configured with length 2 sequence, then the UE may not apply the length 2 to all of the REs of an RB, rather, the UE may additionally be configured with a mapping technique to apply the same OCC sequence to the next REs as non- contiguous.

[0092] For instance, the UE may additionally be configured the start location within an RB to apply the OCC, the UE may either be additionally configured about the RE gap to apply the OCC sequence second time or UE would by default leave the length RE gap to apply the same sequence next time. For example, as shown in Figure 4B, which illustrates an example of RE-based scheduling when OCC is applied in accordance with aspects of the present disclosure, the UE is configured with length 2 412 (left figure) and length 4414 (right figure) OCC sequences with start symbol as 0. The UE applies sequences of these lengths to the same number of REs starting from first RE, then does not map data on the next REs of same length as of OCC and so on. In one implementation, such mapping may be RB specific. In another implementation, such mapping is specific to all scheduled REs, i.e., the UE continues this gap until the end of contiguous scheduled RBs.

[0093] Figure 5 illustrates an example of a UE 500 in accordance with aspects of the present disclosure. The UE 500 may include a processor 502, a memory 504, a controller 506, and a transceiver 508. The processor 502, the memory 504, the controller 506, or the transceiver 508, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0094] The processor 502, the memory 504, the controller 506, or the transceiver 508, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP),an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0095] The processor 502 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 502 may be configured to operate the memory 504. In some other implementations, the memory 504 may be integrated into the processor 502. The processor 502 may be configured to execute computer-readable instructions stored in the memory 504 to cause the UE 500 to perform various functions of the present disclosure.

[0096] The memory 504 may include volatile or non-volatile memory. The memory 504 may store computer-readable, computer-executable code including instructions when executed by the processor 502 cause the UE 500 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 504 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0097] In some implementations, the processor 502 and the memory 504 coupled with the processor 502 may be configured to cause the UE 500 to perform one or more of the functions described herein (e.g., executing, by the processor 502, instructions stored in the memory 504). For example, the processor 502 may support wireless communication at the UE 500 in accordance with examples as disclosed herein.

[0098] The UE 500 may be configured to support a means to receive, from a network entity, a configuration comprising a set of frequency domain orthogonal code sequences, each frequency domain orthogonal code sequence of the set of frequency domain orthogonal code sequences comprising a sequence length different than sequence lengths of other frequency domain orthogonal code sequences of the set of frequency domain orthogonal code sequences, select at least one frequency domain orthogonal code sequence from the set of frequency domain orthogonal code sequences, multiplex UL data associated with the UE according to the selected at least onefrequency domain orthogonal code sequence, and transmit a waveform carrying the multiplexed UL data associated with the UE over a PUSCH.

[0099] In one embodiment, the UE 500 may be configured to support a means to receive a configuration for selecting and applying the at least one orthogonal code sequence from the plurality of frequency domain orthogonal code sequences. In one embodiment, the configuration comprises a type of orthogonal code sequence to be applied. In one embodiment, the type of orthogonal code sequence to be applied comprises a discrete Fourier transform type or a Walsh-Hadamard type.

[0100] In one embodiment, application of orthogonal code sequences is performed in the frequency domain in response to transform precoding being enabled. In one embodiment, UE 500 may be configured to support a means to indicate to the network entity its capabilities for supporting application of orthogonal code sequences in the frequency domain for PUSCH transmissions.

[0101] In one embodiment, the indication to apply the orthogonal code sequences in the frequency domain comprises a sequence index associated with a look-up table and an application pattern. In one embodiment, the sequence index associated with the look- up table is indicated in an UL resource scheduling downlink control information, along with a number of resource blocks to be allocated.

[0102] In one embodiment, in response to allocated frequency resources being more than one resource block and the sequences in the look-up table are one resource block in length, the application pattern may indicate that a plurality of resource blocks may be used for the at least one orthogonal code sequence.

[0103] In one embodiment, the UE 500 may be configured to support a means to apply the at least one orthogonal code sequence to each of the plurality of resource blocks.

[0104] In one embodiment, the UE 500 may be configured to support a means to reference a mapping table to define the application pattern for applying the at least one orthogonal code sequence to the plurality of resource blocks.

[0105] In one embodiment, the mapping table comprises combinations of orthogonal code sequences to resource blocks according to a number of orthogonal code sequence defined for an orthogonal code sequence that has a length of a resource block.

[0106] In one embodiment, the application pattern for the orthogonal code sequences is based on a resource block grouping. In one embodiment, the application pattern for the orthogonal code sequences comprises an index into the look-up table for a resource block group.

[0107] In one embodiment, different resource block groupings use the same application pattern in response to an allocated length of resource blocks within a resource block grouping being the same across different resource block groupings.

[0108] In one embodiment, different mapping types for application of the at least one orthogonal code sequence on one or more resource blocks is signaled through radio resource control.

[0109] In one embodiment, the UE 500 may be configured to support a means to select the look-up table based on a number of elements in a resource block.

[0110] In one embodiment, the UE 500 may be configured to support a means to receive an indication of whether the application pattern is based on resource blocks, resource block grouping, or a combination thereof.

[0111] In one embodiment, in response to the orthogonal code sequences having lengths that are less than a length of a resource block, the UE 500 may be configured to support a means to use a mapping strategy for applying orthogonal code sequences to a resource block or a scheduling scheme that is based on resource elements.

[0112] In one embodiment, the UE 500 may be configured to support a means to repeat same orthogonal code sequences over the resource block. In one embodiment, different mapping strategies to apply orthogonal code sequences to a resource block are defined as a look-up table and an index is used to select a mapping strategy to apply to one or more scheduled resource blocks.

[0113] In one embodiment, the UE 500 may be configured to support a means to use less than a scheduled amount of resource elements of a resource block to apply orthogonal code sequences.

[0114] In one embodiment, the at least one orthogonal code sequence comprises at least one orthogonal cover code sequence. In one embodiment, the waveform comprises a discrete Fourier transform-spread-orthogonal frequency division multiplexing waveform.

[0115] The controller 506 may manage input and output signals for the UE 500. The controller 506 may also manage peripherals not integrated into the UE 500. In some implementations, the controller 506 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 506 may be implemented as part of the processor 502.

[0116] In some implementations, the UE 500 may include at least one transceiver 508. In some other implementations, the UE 500 may have more than one transceiver 508. The transceiver 508 may represent a wireless transceiver. The transceiver 508 may include one or more receiver chains 510, one or more transmitter chains 512, or a combination thereof.

[0117] A receiver chain 510 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 510 may include one or more antennas for receiving the signal over the air or wireless medium. The receiver chain 510 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 510 may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 510 may include at least one decoder for decoding and processing the demodulated signal to receive the transmitted data.

[0118] A transmitter chain 512 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 512 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 512 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 512 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0119] Figure 6 illustrates an example of a processor 600 in accordance with aspects of the present disclosure. The processor 600 may be an example of a processorconfigured to perform various operations in accordance with examples as described herein. The processor 600 may include a controller 602 configured to perform various operations in accordance with examples as described herein. The processor 600 may optionally include at least one memory 604, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 600 may optionally include one or more arithmetic-logic units (ALUs) 606. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0120] The processor 600 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 600) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0121] The controller 602 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 600 to cause the processor 600 to support various operations in accordance with examples as described herein. For example, the controller 602 may operate as a control unit of the processor 600, generating control signals that manage the operation of various components of the processor 600. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0122] The controller 602 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 604 and determine subsequent instruction(s) to be executed to cause the processor 600 to support various operations in accordance with examples as described herein. The controller 602 may be configured to track memory address of instructions associated with the memory 604. The controller 602 may beconfigured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 602 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 600 to cause the processor 600 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 602 may be configured to manage flow of data within the processor 600. The controller 602 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 600.

[0123] The memory 604 may include one or more caches (e.g., memory local to or included in the processor 600 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 604 may reside within or on a processor chipset (e.g., local to the processor 600). In some other implementations, the memory 604 may reside external to the processor chipset (e.g., remote to the processor 600).

[0124] The memory 604 may store computer-readable, computer-executable code including instructions that, when executed by the processor 600, cause the processor 600 to perform various functions described herein. The code may be stored in a non- transitory computer-readable medium such as system memory or another type of memory. The controller 602 and / or the processor 600 may be configured to execute computer-readable instructions stored in the memory 604 to cause the processor 600 to perform various functions. For example, the processor 600 and / or the controller 602 may be coupled with or to the memory 604, the processor 600, the controller 602, and the memory 604 may be configured to perform various functions described herein. In some examples, the processor 600 may include multiple processors and the memory 604 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

[0125] The one or more ALUs 606 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 606 may reside within or on a processor chipset (e.g., the processor 600). In some other implementations, the one or more ALUs 606 may reside external to the processor chipset (e.g., the processor 600). One or more ALUs 606 may perform one ormore computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 606 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 606 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 606 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 606 to handle conditional operations, comparisons, and bitwise operations.

[0126] The processor 600 may support wireless communication in accordance with examples as disclosed herein. In one embodiment, the processor 600 may be configured to or operable to support a means to receive, from a network entity, a configuration comprising a set of frequency domain orthogonal code sequences, each frequency domain orthogonal code sequence of the set of frequency domain orthogonal code sequences comprising a sequence length different than sequence lengths of other frequency domain orthogonal code sequences of the set of frequency domain orthogonal code sequences, select at least one frequency domain orthogonal code sequence from the set of frequency domain orthogonal code sequences, multiplex UL data associated with the UE according to the selected at least one frequency domain orthogonal code sequence, and transmit a waveform carrying the multiplexed UL data associated with the UE over a PUSCH.

[0127] In one embodiment, the processor 600 may be configured to or operable to support a means to receive a configuration for selecting and applying the at least one orthogonal code sequence from the plurality of frequency domain orthogonal code sequences. In one embodiment, the configuration comprises a type of orthogonal code sequence to be applied. In one embodiment, the type of orthogonal code sequence to be applied comprises a discrete Fourier transform type or a Walsh-Hadamard type.

[0128] In one embodiment, application of orthogonal code sequences is performed in the frequency domain in response to transform precoding being enabled. In one embodiment, the processor 600 may be configured to or operable to support a means to indicate to the network entity its capabilities for supporting application of orthogonal code sequences in the frequency domain for PUSCH transmissions.

[0129] In one embodiment, the indication to apply the orthogonal code sequences in the frequency domain comprises a sequence index associated with a look-up table and an application pattern. In one embodiment, the sequence index associated with the look- up table is indicated in an UL resource scheduling downlink control information, along with a number of resource blocks to be allocated.

[0130] In one embodiment, in response to allocated frequency resources being more than one resource block and the sequences in the look-up table are one resource block in length, the application pattern may indicate that a plurality of resource blocks may be used for the at least one orthogonal code sequence.

[0131] In one embodiment, the processor 600 may be configured to or operable to support a means to apply the at least one orthogonal code sequence to each of the plurality of resource blocks.

[0132] In one embodiment, the processor 600 may be configured to or operable to support a means to reference a mapping table to define the application pattern for applying the at least one orthogonal code sequence to the plurality of resource blocks.

[0133] In one embodiment, the mapping table comprises combinations of orthogonal code sequences to resource blocks according to a number of orthogonal code sequence defined for an orthogonal code sequence that has a length of a resource block.

[0134] In one embodiment, the application pattern for the orthogonal code sequences is based on a resource block grouping. In one embodiment, the application pattern for the orthogonal code sequences comprises an index into the look-up table for a resource block group.

[0135] In one embodiment, different resource block groupings use the same application pattern in response to an allocated length of resource blocks within a resource block grouping being the same across different resource block groupings.

[0136] In one embodiment, different mapping types for application of the at least one orthogonal code sequence on one or more resource blocks is signaled through radio resource control.

[0137] In one embodiment, the processor 600 may be configured to or operable to support a means to select the look-up table based on a number of elements in a resource block.

[0138] In one embodiment, the processor 600 may be configured to or operable to support a means to receive an indication of whether the application pattern is based on resource blocks, resource block grouping, or a combination thereof.

[0139] In one embodiment, in response to the orthogonal code sequences having lengths that are less than a length of a resource block, the processor 600 may be configured to or operable to support a means to use a mapping strategy for applying orthogonal code sequences to a resource block or a scheduling scheme that is based on resource elements.

[0140] In one embodiment, the processor 600 may be configured to or operable to support a means to repeat same orthogonal code sequences over the resource block. In one embodiment, different mapping strategies to apply orthogonal code sequences to a resource block are defined as a look-up table and an index is used to select a mapping strategy to apply to one or more scheduled resource blocks.

[0141] In one embodiment, the processor 600 may be configured to or operable to support a means to use less than a scheduled amount of resource elements of a resource block to apply orthogonal code sequences.

[0142] In one embodiment, the at least one orthogonal code sequence comprises at least one orthogonal cover code sequence. In one embodiment, the waveform comprises a discrete Fourier transform-spread-orthogonal frequency division multiplexing waveform.

[0143] Figure 7 illustrates an example of a NE 700 in accordance with aspects of the present disclosure. The NE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0144] The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP),an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0145] The NE 700 may be configured to support a means to transmit, to a UE, an indication to apply orthogonal code sequences in a frequency domain, receive a PUSCH transmission with a selected at least one orthogonal code sequence applied to a waveform in the frequency domain, and multiplex PUSCH transmissions for a plurality of UEs based on the orthogonal code sequences in the frequency domain.

[0146] The processor 702 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 702 may be configured to operate the memory 704. In some other implementations, the memory 704 may be integrated into the processor 702. The processor 702 may be configured to execute computer-readable instructions stored in the memory 704 to cause the NE 700 to perform various functions of the present disclosure.

[0147] The memory 704 may include volatile or non-volatile memory. The memory 704 may store computer-readable, computer-executable code including instructions when executed by the processor 702 causes the NE 700 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 704 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0148] In some implementations, the processor 702 and the memory 704 coupled with the processor 702 may be configured to cause the NE 700 to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704). For example, the processor 702 may support wireless communication at the NE 700 in accordance with examples as disclosed herein.

[0149] The controller 706 may manage input and output signals for the NE 700. The controller 706 may also manage peripherals not integrated into the NE 700. In some implementations, the controller 706 may utilize an operating system such as iOS®,ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 706 may be implemented as part of the processor 702.

[0150] In some implementations, the NE 700 may include at least one transceiver 708. In some other implementations, the NE 700 may have more than one transceiver 708. The transceiver 708 may represent a wireless transceiver. The transceiver 708 may include one or more receiver chains 710, one or more transmitter chains 712, or a combination thereof.

[0151] A receiver chain 710 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 710 may include one or more antennas for receiving the signal over the air or wireless medium. The receiver chain 710 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 710 may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 710 may include at least one decoder for decoding and processing the demodulated signal to receive the transmitted data.

[0152] A transmitter chain 712 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 712 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 712 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 712 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0153] Figure 8 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions.

[0154] At 802, the method may receive, from a network entity, a configuration comprising a set of frequency domain orthogonal code sequences. The operations of 802 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 802 may be performed by a UE as described with reference to Figure 5.

[0155] At 804, the method may select at least one frequency domain orthogonal code sequence from the set of frequency domain orthogonal code sequences. The operations of 804 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 804 may be performed by a UE as described with reference to Figure 5.

[0156] At 806, the method may multiplex UL data associated with the UE according to the selected at least one frequency domain orthogonal code sequence. The operations of 806 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 806 may be performed by a UE as described with reference to Figure 5.

[0157] At 808, the method may transmit a waveform carrying the multiplexed UL data associated with the UE over a PUSCH. The operations of 808 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 808 may be performed by a UE as described with reference to Figure 5.

[0158] Figure 9 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by an NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0159] At 902, the method may transmit, to a UE, an indication to apply orthogonal code sequences in a frequency domain. The operations of 902 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 902 may be performed by an NE as described with reference to Figure 7.

[0160] At 904, the method may receive a PUSCH transmission with a selected at least one orthogonal code sequence applied to a waveform in the frequency domain. The operations of 904 may be performed in accordance with examples as described herein.In some implementations, aspects of the operations of 904 may be performed by an NE as described with reference to Figure 7.

[0161] At 906, the method may multiplex PUSCH transmissions for a plurality of UEs based on the orthogonal code sequences in the frequency domain. The operations of 906 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 906 may be performed by an NE as described with reference to Figure 7.

[0162] It should be noted that the method described herein describes A possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0163] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

CLAIMS What is claimed is:

1. A user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive, from a network entity, a configuration comprising a set of frequency domain orthogonal code sequences, each frequency domain orthogonal code sequence of the set of frequency domain orthogonal code sequences comprising a sequence length different than sequence lengths of other frequency domain orthogonal code sequences of the set of frequency domain orthogonal code sequences; select at least one frequency domain orthogonal code sequence from the set of frequency domain orthogonal code sequences; multiplex uplink (UL) data associated with the UE according to the at least one frequency domain orthogonal code sequence; and transmit a waveform carrying the multiplexed UL data associated with the UE over a physical UL shared channel (PUSCH).

2. The UE of claim 1, wherein the at least one processor is configured to cause the UE to receive a configuration for selecting and applying the at least one frequency domain orthogonal code sequence from the set of frequency domain orthogonal code sequences, and wherein the configuration comprises a type of orthogonal code sequence to be applied, and wherein the type of orthogonal code sequence to be applied comprises a discrete Fourier transform type or a Walsh-Hadamard type.

3. The UE of claim 1, wherein application of orthogonal code sequences is performed in a frequency domain in response to transform precoding being enabled.

4. The UE of claim 1, wherein the at least one processor is configured to cause the UE to indicate to the network entity one or more capabilities for supportingapplication of orthogonal code sequences in a frequency domain for PUSCH transmissions.

5. The UE of claim 1, wherein an indication to apply the frequency domain orthogonal code sequences in the frequency domain comprises a sequence index associated with a look-up table and an application pattern.

6. The UE of claim 5, wherein the sequence index associated with the look-up table is indicated in an UL resource scheduling downlink control information, along with a number of resource blocks to be allocated.

7. The UE of claim 5, wherein, in response to allocated frequency resources being more than one resource block and sequences in the look-up table are one resource block in length, the application pattern may indicate that a plurality of resource blocks may be used for the at least one frequency domain orthogonal code sequence.

8. The UE of claim 7, wherein the at least one processor is configured to cause the UE to apply the at least one frequency domain orthogonal code sequence to each of the plurality of resource blocks.

9. The UE of claim 7, wherein the at least one processor is configured to cause the UE to reference a mapping table to define the application pattern for applying the at least one frequency domain orthogonal code sequence to the plurality of resource blocks, and wherein the mapping table comprises combinations of frequency domain orthogonal code sequences to resource blocks according to a number of orthogonal code sequence defined for an orthogonal code sequence that has a length of a resource block.

10. The UE of claim 5, wherein the application pattern for the frequency domain orthogonal code sequences is based on resource blocks within a resource block grouping and comprises an index into the look-up table for a resource block group, and wherein different resource block groupings use a same application pattern in response to an allocated length of resource blocks within a resource block grouping being same across different resource block groupings.

11. The UE of claim 5, wherein different mapping types for application of the at least one frequency domain orthogonal code sequence on one or more resource blocks is signaled through radio resource control.

12. The UE of claim 5, wherein the at least one processor is configured to cause the UE to select the look-up table based on a number of elements in a resource block.

13. The UE of claim 5, wherein the at least one processor is configured to cause the UE to receive an indication of whether the application pattern is based on resource blocks, resource block grouping, or a combination thereof.

14. The UE of claim 1, wherein, in response to the frequency domain orthogonal code sequences having lengths that are less than a length of a resource block, the at least one processor is configured to cause the UE to use a mapping strategy for applying frequency domain orthogonal code sequences to a resource block or a scheduling scheme that is based on resource elements.

15. The UE of claim 14, wherein the at least one processor is configured to cause the UE to repeat same frequency domain orthogonal code sequences over the resource block.

16. The UE of claim 14, wherein different mapping strategies to apply frequency domain orthogonal code sequences to a resource block are defined as a look-up table and an index is used to select a mapping strategy to apply to one or more scheduled resource blocks.

17. The UE of claim 14, wherein the at least one processor is configured to cause the UE to use less than a scheduled amount of resource elements of a resource block to apply frequency domain orthogonal code sequences.

18. A method performed by a user equipment (UE), the method comprising: receiving, from a network entity, a configuration comprising a set of frequency domain orthogonal code sequences, each frequency domain orthogonal code sequence of the set of frequency domain orthogonal code sequences comprising a sequence length different than sequence lengths of otherfrequency domain orthogonal code sequences of the set of frequency domain orthogonal code sequences; selecting at least one frequency domain orthogonal code sequence from the set of frequency domain orthogonal code sequences; multiplexing uplink (UL) data associated with the UE according to the at least one frequency domain orthogonal code sequence; and transmitting a waveform carrying the multiplexed UL data associated with the UE over a physical UL shared channel (PUSCH).

19. A network equipment (NE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the NE to: transmit, to a user equipment (UE), an indication to apply orthogonal code sequences in a frequency domain; receive a physical uplink (UL) shared channel (PUSCH) transmission with a selected at least one orthogonal code sequence applied to a waveform in the frequency domain; and multiplex PUSCH transmissions for a plurality of UEs based on the orthogonal code sequences in the frequency domain.

20. A method performed by a network equipment (NE), the method comprising: transmitting, to a user equipment (UE), an indication to apply orthogonal code sequences in a frequency domain; receiving a physical uplink (UL) shared channel (PUSCH) transmission with a selected at least one orthogonal code sequence applied to a waveform in the frequency domain; and multiplexing PUSCH transmissions for a plurality of UEs based on the orthogonal code sequences in the frequency domain.

Images