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 time domain orthogonal code sequences, each time domain orthogonal code sequence of the set of time domain orthogonal code sequences comprising a sequence length different than sequence lengths of other time domain orthogonal code sequences of the set of time domain orthogonal code sequences, select at least one time domain orthogonal code sequence from the set of time domain orthogonal code sequences, multiplex uplink (UL) data associated with the UE according to the selected at least one time domain orthogonal code sequence, transmit a waveform carrying the multiplexed uplink data associated with the UE over a physical UL shared channel (PUS CH).

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 time domain orthogonal code sequences, each time domain orthogonal code sequence of the set of time domain orthogonal code sequences comprising a sequence length different than sequence lengths of other time domain orthogonal code sequences of the set of time domain orthogonal code sequences, select at least one time domain orthogonal code sequence from the set of time domain orthogonal code sequences, multiplex UL data associated with the UE according to the selected at least one time domain orthogonal code sequence, 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 time domain orthogonal code sequences, each time domain orthogonal code sequence of the set of time domain orthogonal code sequences comprising a sequence length different than sequence lengths of other time domain orthogonal code sequences of the set of time domain orthogonal code sequences, select at least one time domain orthogonal code sequence from the set of time domain orthogonal code sequences, multiplex UL data associated with the UE according to the selected at least one time domain orthogonal code sequence, 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 NE may be configured to, capable of, or operable to transmit, to a UE, an indication to apply orthogonal code sequences in a time domain, receive a PUSCH transmission with a selected at least one orthogonal code sequence applied to a waveform in the time domain, and multiplex PUSCH transmissions for a plurality of UEs based on the orthogonal code sequences in the time domain.

[0007] A method for wireless communication performed by an NE is described. The method may be configured to, capable of, or operable to transmit, to a UE, an indication to apply orthogonal code sequences in a time domain, receive a PUSCH transmission with a selected at least one orthogonal code sequence applied to a waveform in the timedomain, and multiplex PUSCH transmissions for a plurality of UEs based on the orthogonal code sequences in the time 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 2A illustrates an example of a PUSCH-Config radio resource control (RRC) message in accordance with aspects of the present disclosure.

[0010] Figure 2B illustrates an example of a ConfiguredGrantConfig information element in accordance with aspects of the present disclosure.

[0011] Figure 3 illustrates an example of time domain orthogonal cover code (OCC) configuration for multi-slot PUSCH transmission in accordance with aspects of the present disclosure.

[0012] Figure 4 illustrates an example of OCC application with slot aggregation enabled, in accordance with aspects of the present disclosure.

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

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

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

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

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

[0018] 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, solely applying repetitions to wireless communication (e.g., UL transmission, downlinktransmission) 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, solely 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.

[0019] 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.

[0020] 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.

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

[0022] 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 maybe 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 a 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.

[0023] 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.

[0024] 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 the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0025] 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 subscriberdevice, 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.

[0026] 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.

[0027] 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.

[0028] 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), an access 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.

[0029] 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).

[0030] 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.

[0031] 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) may utilize 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 cyclicprefix. A fifth numerology (e.g., ^=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0032] 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.

[0033] 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.

[0034] 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.

[0035] 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.

[0036] 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.

[0037] In one embodiment, two transmission schemes are supported for physical UL shared channel (PUSCH): codebook-based transmission and non-codebook based transmission. For codebook-based transmission, the gNB provides the UE with a transmit precoding matrix indication 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.

[0038] 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.

[0039] 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.

[0040] 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.

[0041] 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.

[0042] 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 three 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.

[0043] 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.

[0044] 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.

[0045] For each codeword, the block of bits b^^^^0^, … , b^^^^M^^^bit − 1^, whereM ^^^ bit is the number of bits in codeword q transmitted on 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 bits b~( q )(i) ^ 1else ifb( q)(i) ^ y / / UCI placeholder bits ~end if i = i + 1 end while

[0046] 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

[0047] c n I ∙ 2^^ + nRAPID ∙ 2^^RNT + nID for msgA on PUSCHinit = ^nRNTI ∙ 2^^ + 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 TS 38.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 of the modulation schemes in Table 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 theshall 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 ofof per layer.

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

[0052] Ifis enabled according to 6.1.3 of TS38.214 (in, υ = 1(0) andx% ( i )depends on the configuration of phase-tracking reference signals. 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 layersymb+ MPUSCHsc sets,(0) (0)to one OFDM symbol andx% ( i )^ x ( i ).

[0054] If theindicates that phase-tracking reference signalsare being used, the block of complex-valued symbols x^^^^0^, … , x^^^ ^Mlayersymb − 1^ shallbe divided into sets, each set corresponding to one OFDM symbol,set lcontainsMPUSCH group PTRSsc ^^l N samp N groupsymbols and is mapped to the complex-valued symbolsx, ^^^^lMto OFDM symbol l prior to transformwith i′ ∈ ^0,1, … , MPUSCHsc − 1^ and i^ ^ m . The index m of PT-RS samples in set l , thenumber of samples per PT-RS group Nsgarmoupp, and the number of PT-RS groups NgPrTo-uRpSare 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 shall be applied according to M PUSCH sc^1 ^ j2^ ik(0) ( l ^ M PUSCH ^ k ) ^1^ x % (0) ( l ^ M PUSCH ^ i ) eM PUSCH sc^he variableMPUSCH ^ M PUSCH ^ N RB, where M PUSCH1 . T sc RB sc RB represents the bandwidth of thePUSCH in terms of resource blocks, and shall fulfill: MRPUBSCH^2^2^3^3^ 5^ 5where^2,^3 , ^ 5is a set ofembodiment, the block % ^^^ ^&'^^ (Tof vectors y ^i^ … y ^i^ shall beprecoded according to z^34^^i^y^^^^i^1⋮ 9 = W 1⋮ 9 z^3678^^i^ y^&'^^^i^

[0058] where i = 0,1, … , M ap − 1, M ap =layer symb symbMsymb . The set of antenna ports;p^ , … , p='^> shall be determined according to the procedure in [6, TS 38.214].

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

[0060] 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.

[0061] 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.

[0062] In general, the subject matter herein describes configuration aspects for the time domain application of OCC for UL data channel capacity improvement while employing DFT-s-OFDM waveform. The time domain allocation of resources for PUSCH is flexible where different symbols within a slot may be allocated to the UE. Moreover, the time domain scheduling may be dynamic or based on RRC signaling. Therefore, selection of an OCC look-up table from different length tables would depend on number of time domain symbols allocation. Moreover, the allocated time domain symbols may be more than available OCC sequence length, that would in return require indication of mapping pattern for the applicability of multiple lengths OCC. Therefore, the following features are disclosed herein – an indication for enabling / disabling the time-domain application of OCC to PUSCH transmission along with capability indication, configuration of OCC parameters including DCI based solution with dynamic scheduling and RRC signaling based solution for semi-persistent scheduling, OCC parameters for multi-slot scheduling, and configuration for OCC parameters for PUSCH repetitions.

[0063] According to a first embodiment, the network indicates to the UE to apply OCC in the time domain for the multiplexing of PUSCH transmission of multiple users, when transform precoding is enabled. 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 be explicitly or implicitly indicated along with PUSCH resource allocation. For example, new fields 202, 204 in PUSCH-Config RRC message may be used to indicates whether time or frequency domain OCCs are to be used or not, as illustrated in Figure 2A. Figure 2A illustrates an example of a PUSCH-Config RRC message in accordance with aspects of the present disclosure.

[0064] 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 alsobe 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, a field may be used to indicate which type of tables to be used for the selection of OCC sequence, for example using field timeDomainOCCType = ENUMERATED (DFT, Walsh-Hadamard) 204. The OCC length and index for the selection OCC sequence may either be separately indicated or in the same configuration.

[0065] In one implementation, time domain OCC are only 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.

[0066] In one embodiment, UE indicates to the network about its capabilities to support time-domain application of 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.

[0067] According to a second embodiment, the network explicitly or implicitly indicates to the UE about the OCC parameters that may be helpful in selection of the OCC sequence to be used in the time domain, once the network indicates about enabling of OCC application to PUSCH data (e.g., as described in the first embodiment). Depending on the type of PUSCH scheduling, e.g., dynamic scheduling or configured scheduling, this may be indicated explicitly or implicitly in the DCI, or through system information block (SIB) or through dedicated RRC signaling.

[0068] In one embodiment, when PUSCH resource allocation for time domain is dynamically configured, the OCC index (i.e., that selects an OCC sequence from a OCC look-up table) may be explicitly indicated in the UL scheduling DCI formats such as DCI 0_0 and 0_1 by using a field, for example namely OCC-index, whereas thelength of the code (i.e., that defines the selection of look-up table from multiple OCC look-up tables of various lengths) may either be explicitly indicated by a field in the same configuration or implicitly indicated.

[0069] In one implementation, the length of OCC is implicitly indicated using the Start and Length Indicator Value (SLIV), where OCC sequence may be of the same length as of the value L in SLIV. Here L indicates the allocated length of PUSCH symbols in the time domain. Basically, the UE would need to select a row index, where this row index corresponds to the time domain resource assignment value in the DCI 0_0 or 0_1.

[0070] For instance, when TimeDomainAllocationList is not configured by either IEs pusch-ConfigCommon or pusch-ConfigDepending, the UE would use the default PUSCH time domain allocation table A that specifies up to 16 rows indicating parameters such as slots offset, PUSCH mapping type, start value and length of allocated symbols. Depending on the received four bit value of the time domain resource assignment value in the DCI 0_0 or 0_1, the corresponding row from the look up table would be selected by the UE.

[0071] Alternatively, when TimeDomainAllocationList is configured, the UE would decode the start value and length value from SLIV value indicated in the time domain allocation list. Note that the maximum value of the parameter L (indicating the length of the allocated symbols in time domain) in SLIV is 14. Moreover, the length is always allocated in multiples of 2 starting from minimum of 4 up to maximum of 14 symbols in the time domain. Therefore, in one implementation, multiple OCC look-up tables corresponding to these lengths may be defined, e.g., length 2, 4, 6, 8, 10, 12, and 14. Once the UE knows the allocated length of time domain PUSCH symbols, the UE would choose one of the OCC look-up tables corresponding to the L value from SLIV, where the index, that may be explicitly configured via DCI, would help in choosing the corresponding OCC sequence from the look-up table.

[0072] In one implementation, when the DMRS carrying symbols are not OCC multiplexed along with the UL data, the UE would deduct the DMRS carrying symbols from the allocated length through SLIV and choose the corresponding table for the application of OCC. For example, if the indicated length through SLIV is L=8 and thereare two DMRS carrying symbols (FGKHLJIMJN^, then the UE would choose OCC look-uptable of length 6 (O − FKLJMNGHIJ ).

[0073] In one implementation, when there are no separate look-up tables for each length, rather a single OCC look-up table is used that defines multiple OCC lengths and corresponding sequences, then the UE would select the row corresponding to the value of L, while the network may indicate in the DCI the index to be used for the selection of sequence from the row. For example, a DFT based OCC look up table for PUSCH is illustrated in Table 1, where each row corresponds to one length OCC codes, while each column defines the different available sequences for that length. In this case, the UE may select the row corresponding the value L in SLIV, while the sequence value (P) may be configured through DCI. VWXY^S^Table 1: Orthogonal sequences dQ ^S^ = U ZR for PUSCHIndex(FeKfLBJ,MgN) i^ 0 i^ 1 i^ 2i^ 4 i^ 5 i^ 61 [0] - - - - - - 2

[0000]

[0001] - - - - - 3

[0000]

[0012]

[0021] - - - - 4

[0000]

[0202]

[0022]

[0220] - - - 5

[0000]

[1234]

[2413]

[3142]

[4321] - - 6 [000000] [012345] [024024] [030303] [042042] [05432 - 1] [05316 [0654 7 [0000000] [0123456] [0246135] [0362514] [0415263] 42] 321]

[0074] In one implementation, whenever the UE would receive new PDCCH carrying information about change of resource allocation in the time domain, e.g., change of L value in SLIV or index is changed, the UE would update the OCC look-up table or selection of OCC sequence correspondingly.

[0075] In one embodiment, when the length of the allocated time domain symbols is more than the length of available OCC sequences, then the UE may additionally be indicated for which symbols, which length codes would be used. For instance, OCC may be defined / specified up to 4 length sequences, e.g., there are at the most 3 look-up table for OCC of length 2, 3, and 4. However, the allocated length of the time domain symbols may be more than longest sequence available, e.g., L >4. In such case, the network may need to additionally indicate that on which symbols in a slot what length sequence need to apply. For example, if a UE is indicated a SLIV value where L = 6,and the maximum length of available OCC sequence is 4, then UE would require additional information about which code table to be applied along with the OCC sequence index.

[0076] In one implementation, a mapping table may be specified, where this table defines the different combination of OCC lengths and the order of their application, e.g., which length should be applied first. Such table helps in choosing an OCC look-up table in an order of applying a specific code when the number of allocated symbols are more than the available OCC lengths. For example, if length 2, 3, 4, 5, and 6 OCC tables are available and the maximum number of symbols that may be allocated are 12, then the table may include all the possible combinations of lengths greater than 6 and up to 12. An illustration of such table is provided in Table 2.

[0077] For instance, if allocated length is 7 and available OCC sequence maximum length is 6, then either index 1 or 2 are configured to the UE in the DCI for dynamic scheduling or through RRC in case of configured scheduling of time domain resources, where the UE would first select the OCC look-up table of length corresponding to the first length, e.g., 2 length OCC look-up table when configured with index 1, and then the next length e.g., length 5 look-up table. The indices for selection of a specific OCC sequence within these OCC length look-up tables may separately be configured. Table 2: A mapping table example when OCC length is less than allocated symbols Indices combinations 1 {2,5} 2 {5,2} 3 {3,4} 4 {3,5} 6 {2,6} 7 {4,5} 8 {2,3,4} … …

[0078] In one implementation, the index and length are indicated by RRC signaling, e.g., in PUSCH config IE, whereas DCI or MAC-CE is used to indicate whether the configured values are valid or not. If not, then the DCI or MAC-CE signaling is used to overwrite those configured values.

[0079] In one embodiment, when PUSCH time domain resource allocation is semi- persistently scheduled (SPS), the OCC sequence index (in order to select a sequence from a OCC look-up table) may be explicitly indicated through RRC signaling orthrough DCI, whereas the OCC length (in order to select a OCC look-up table) may be implicitly indicated through RRC signaling.

[0080] In one implementation, when a UE is configured UL time resources through RRC signaling for configuration grant type 1or type 2 using IE ConfiguredGrantConfig, the network may additionally indicate explicitly in the same IE about the activation of OCC for PUSCH for time domain, selection of an OCC table (length), and the selection of OCC sequence from the look-up table (index) 206. For this purpose, new fields may be used to indicate these OCC parameters, as shown below. Figure 2B illustrates an example of a ConfiguredGrantConfig IE in accordance with aspects of the present disclosure.

[0081] In one implementation, the length of the OCC sequence may be implicitly indicated through RRC message, e.g., derived from the parameter “timeDomainAllocation” in IE ConfiguredGrantConfig, where this parameter indicates a combination of start symbol and length and PUSCH mapping type. Once the UE knows the length of allocated time domain symbols, the UE can use the same length for the selection of OCC look-up table, where other parameters such as index to select the sequence from the table may be indicated separately by a field in the same IE.

[0082] In one implementation, when the resource allocation is configured through configured grant type 2, the OCC index and length may be configured through DCI, where OCC index may be explicitly indicated by a field, while the OCC length may be implicitly indicated through time domain allocated symbol length.

[0083] According to a third embodiment, when the UL transmission is configured to be transmitted on multiple slots, the network may either provide an implicit or an explicit indication to apply time domain OCC on PUSCH transmission for multiple slots. For instance, if PUSCH transmission for either of configured grant type 1 or configured grant type 2 is periodically configured through IE ConfiguredGrantConfig with field “periodicity”, where the same allocation of time and frequency resources are utilized, the network may either configure to use same OCC index (i.e., same OCC sequence) or configure different OCC indices for each periodic interval.

[0084] For example, if multiple OCC indices are not configured and periodicity for UL transmission is configured, then the UE may use the same OCC sequence for all periodic intervals. The network may configure any new sequence at any time usingPDCCH. Alternatively, the network may configure a different OCC index for each periodic interval in the same configuration or set a pattern for selection of next OCC index with reference to first configured OCC index.

[0085] In one realization, a relative index with reference to configured index may be indicated in the configuration. The UE would choose the next index by adding relative index to the configured index. For example, a UE receives an OCC index of 2302 and a relative index of 1 field in the IE ConfiguredGrantConfig. The UE would choose the OCC sequence corresponding to the index 2302 and apply it for a first PUSCH transmission. During the next periodic PUSCH transmission, the UE would choose the OCC sequence corresponding to the index 3304, since relative index value is 1, as illustrated in Figure 3, which illustrates an example of time domain OCC configuration for multi-slot PUSCH transmission in accordance with aspects of the present disclosure. The UE keeps on repeating this, until it receives PDCCH or new RRC configuration.

[0086] Figure 4 illustrates an example of OCC application with slot aggregation enabled, in accordance with aspects of the present disclosure. According to a fourth embodiment, when the UL transmission is configured with repetition to increase the PUSCH coverage (i.e., same transport block (TB) is repeated on multiple slots) either by dynamic scheduling or by configured grant, the same OCC index may be applied to all repetitions. For example, if pusch-AggregationFactor within PUSCH-Config IE for dynamic scheduling or repK within ConfiguredGrantConfig IE for the case of configured grant is used with value greater than 1 for repetitions and a UE is scheduled with one OCC index 402, the UE would apply the same the OCC sequence 404 to all repetitions, as shown in Figure 4, which illustrates an example of OCC application with slot aggregation enabled with PUSCH - AggregationFactor = 4, in accordance with aspects of the present disclosure.

[0087] 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.

[0088] 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.

[0089] 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.

[0090] 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.

[0091] 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.

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

[0093] 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 time domain orthogonal code sequences.

[0094] 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.

[0095] In one embodiment, application of orthogonal code sequences is performed in the time domain in response to transform precoding being enabled.

[0096] In one embodiment, the 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 time domain for physical UL transmissions.

[0097] In one embodiment, the UE 500 may be configured to support a means to receive, from the network entity, at least one parameter for selection of the at least one orthogonal code sequence.

[0098] In one embodiment, the at least one parameter is indicated in a downlink control information format in response to resource allocation of the PUSCH transmission being dynamically configured.

[0099] In one embodiment, the at least one parameter comprises an orthogonal code sequence length, the orthogonal code sequence length indicated using a start and length indicator in the time domain.

[0100] In one embodiment, the at least one parameter comprises at least one symbol to be used based on the orthogonal code sequence length in response to a length of an allocated time domain symbol being greater than the orthogonal code sequence length.

[0101] In one embodiment, the at least one processor is configured to cause the UE to reference a lookup table that defines different combinations of orthogonal code sequence lengths and an order of their application.

[0102] In one embodiment, the at least one parameter is indicated in a downlink control information format or radio resource control signaling in response to resource allocation of the PUSCH transmission being semi-persistently scheduled and the orthogonal code sequence length is implicitly indicated via radio resource control signaling.

[0103] In one embodiment, the at least one parameter is indicated via a configured grant information element through radio resource control signaling.

[0104] In one embodiment, the at least one parameter comprises an orthogonal code sequence length that is implicitly provided via radio resource control signaling and is indicated by a start symbol and length and a physical UL transmission mapping type.

[0105] In one embodiment, in response to the resource allocation being configured through configured grant type 2, the orthogonal code sequence length is implicitly indicated by a time domain allocated symbol length.

[0106] In one embodiment, the UE 500 may be configured to support a means to apply the at least one orthogonal code sequence in the time domain on a plurality of slots in response to the physical UL transmission being configured for transmission on the plurality of slots.

[0107] In one embodiment, the UE 500 may be configured to support a means to apply the at least one orthogonal code sequence in the time domain on each of a plurality of slots with repetition in response to the physical UL transmission being configured for transmission with repetition on the plurality of slots.

[0108] In one embodiment, the at least one orthogonal code sequence comprises at least one orthogonal cover code sequence. In one embodiment, the indication to apply orthogonal code sequences in a time domain is received via radio resource control signaling.

[0109] 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.

[0110] 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.

[0111] 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.

[0112] 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.

[0113] 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 processor configured 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 mayoptionally 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).

[0114] 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).

[0115] 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.

[0116] 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 be configured 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 theprocessor 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.

[0117] 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).

[0118] 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.

[0119] 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 or more 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 configuredwith 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.

[0120] 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 time domain orthogonal code sequences, each time domain orthogonal code sequence of the set of time domain orthogonal code sequences comprising a sequence length different than sequence lengths of other time domain orthogonal code sequences of the set of time domain orthogonal code sequences, select at least one time domain orthogonal code sequence from the set of time domain orthogonal code sequences, multiplex UL data associated with the UE according to the selected at least one time domain orthogonal code sequence, transmit a waveform carrying the multiplexed UL data associated with the UE over a PUSCH.

[0121] 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 time domain orthogonal code sequences.

[0122] 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.

[0123] In one embodiment, application of orthogonal code sequences is performed in the time domain in response to transform precoding being enabled.

[0124] 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 time domain for physical UL transmissions.

[0125] In one embodiment, the processor 600 may be configured to or operable to support a means to receive, from the network entity, at least one parameter for selection of the at least one orthogonal code sequence.

[0126] In one embodiment, the at least one parameter is indicated in a downlink control information format in response to resource allocation of the PUSCH transmission being dynamically configured.

[0127] In one embodiment, the at least one parameter comprises an orthogonal code sequence length, the orthogonal code sequence length indicated using a start and length indicator in the time domain.

[0128] In one embodiment, the at least one parameter comprises at least one symbol to be used based on the orthogonal code sequence length in response to a length of an allocated time domain symbol being greater than the orthogonal code sequence length.

[0129] In one embodiment, the at least one processor is configured to cause the UE to reference a lookup table that defines different combinations of orthogonal code sequence lengths and an order of their application.

[0130] In one embodiment, the at least one parameter is indicated in a downlink control information format or radio resource control signaling in response to resource allocation of the PUSCH transmission being semi-persistently scheduled and the orthogonal code sequence length is implicitly indicated via radio resource control signaling.

[0131] In one embodiment, the at least one parameter is indicated via a configured grant information element through radio resource control signaling.

[0132] In one embodiment, the at least one parameter comprises an orthogonal code sequence length that is implicitly provided via radio resource control signaling and is indicated by a start symbol and length and a physical UL transmission mapping type.

[0133] In one embodiment, in response to the resource allocation being configured through configured grant type 2, the orthogonal code sequence length is implicitly indicated by a time domain allocated symbol length.

[0134] 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 in the time domainon a plurality of slots in response to the physical UL transmission being configured for transmission on the plurality of slots.

[0135] 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 in the time domain on each of a plurality of slots with repetition in response to the physical UL transmission being configured for transmission with repetition on the plurality of slots.

[0136] In one embodiment, the at least one orthogonal code sequence comprises at least one orthogonal cover code sequence. In one embodiment, the indication to apply orthogonal code sequences in a time domain is received via radio resource control signaling.

[0137] 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.

[0138] 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.

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

[0140] 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 combinationthereof). 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.

[0141] 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.

[0142] 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.

[0143] 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.

[0144] 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.

[0145] 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 wirelessmedium. 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.

[0146] 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.

[0147] 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.

[0148] At 802, the method may receive, from a network entity, a configuration comprising a set of time 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.

[0149] At 804, the method may select at least one time domain orthogonal code sequence from the set of time 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.

[0150] At 806, the method may multiplex UL data associated with the UE according to the selected at least one time 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.

[0151] 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.

[0152] 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.

[0153] At 902, the method may transmit, to a UE, an indication to apply orthogonal code sequences in a time 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.

[0154] At 904, the method may receive a PUSCH transmission with a selected at least one orthogonal code sequence applied to a waveform in the time 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.

[0155] At 906, the method may multiplex PUSCH transmissions for a plurality of UEs based on the orthogonal code sequences in the time 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.

[0156] 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.

[0157] 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 time domain orthogonal code sequences, each time domain orthogonal code sequence of the set of time domain orthogonal code sequences comprising a sequence length different than sequence lengths of other time domain orthogonal code sequences of the set of time domain orthogonal code sequences; select at least one time domain orthogonal code sequence from the set of time domain orthogonal code sequences; multiplex uplink (UL) data associated with the UE according to the at least one time 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 time domain orthogonal code sequence from the set of time domain orthogonal code sequences.

3. The UE of claim 2, 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.

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

5. The UE of claim 1, wherein the at least one processor is configured to cause the UE to indicate one or more capabilities for supporting application of orthogonal code sequences in a time domain for physical UL transmissions.

6. The UE of claim 1, wherein the at least one processor is configured to cause the UE to receive, from the network entity, at least one parameter for selection of the at least one time domain orthogonal code sequence.

7. The UE of claim 6, wherein the at least one parameter is indicated in a downlink control information format in response to resource allocation of the PUSCH being dynamically configured.

8. The UE of claim 6, wherein the at least one parameter comprises an orthogonal code sequence length, the orthogonal code sequence length indicated using a start and length indicator in a time domain.

9. The UE of claim 8, wherein the at least one parameter comprises at least one symbol to be used based on the orthogonal code sequence length in response to a length of an allocated time domain symbol being greater than the orthogonal code sequence length.

10. The UE of claim 9, wherein the at least one processor is configured to cause the UE to reference a lookup table that defines different combinations of orthogonal code sequence lengths and an order of their application and wherein the at least one parameter is indicated in a downlink control information format or radio resource control signaling in response to resource allocation of the PUSCH being semi-persistently scheduled and the orthogonal code sequence length is implicitly indicated via radio resource control signaling.

11. The UE of claim 7, wherein the at least one parameter is indicated via a configured grant information element through radio resource control signaling.

12. The UE of claim 7, wherein the at least one parameter comprises an orthogonal code sequence length that is implicitly provided via radio resource control signaling and is indicated by a start symbol and length and a physical UL transmission mapping type.

13. The UE of claim 12, wherein, in response to the resource allocation being configured through configured grant type 2, the orthogonal code sequence length is implicitly indicated by a time domain allocated symbol length.

14. The UE of claim 1, wherein the at least one processor is configured to cause the UE to apply the at least one time domain orthogonal code sequence in a time domain on a plurality of slots in response to a physical UL transmission being configured for transmission on the plurality of slots.

15. The UE of claim 1, wherein the at least one processor is configured to cause the UE to apply the at least one time domain orthogonal code sequence in a time domain on each of a plurality of slots with repetition in response to a physical UL transmission being configured for transmission with repetition on the plurality of slots.

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

17. 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 time 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 time domain; and multiplex PUSCH transmissions for a plurality of UEs based on the orthogonal code sequences in the time domain.

18. The NE of claim 17, wherein the at least one processor is configured to cause the NE to transmit, to the UE, a configuration comprising a set of time domain orthogonal code sequences, each time domain orthogonal code sequence of the set of time domain orthogonal code sequences comprising a sequence length different than sequence lengths of other time domain orthogonal code sequences of the set of time domain orthogonal code sequences.

19. The NE of claim 18, wherein the at least one processor is configured to cause the NE to transmit a configuration for selecting and applying at least one orthogonal code sequence from the set of time domain orthogonal code sequences.

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 time 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 time domain; and multiplexing PUSCH transmissions for a plurality of UEs based on the orthogonal code sequences in the time domain.

Images