Uplink capacity enhancement techniques

Abstract

Various aspects of the present disclosure relate to techniques for preventing bidding down attacks. A user equipment (UE) is configured to multiplex uplink (UL) data associated with the UE in one or more of a time domain or a frequency domain according to at least one orthogonal cover code sequence, and transmit, over a physical UL shared channel (PUSCH), a waveform carrying the multiplexed UL data associated with the UE.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more specifically, to uplink (UL) capacity enhancement technologies. Background Technology

[0002] A wireless communication system may include one or more network communication devices, such as base stations, that support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UE) or other suitable terms. The wireless communication system can support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.)). Furthermore, the wireless communication system can support wireless communication across a variety of radio access technologies, including third-generation (3G), fourth-generation (4G), fifth-generation (5G), and other suitable radio access technologies other than 5G (e.g., sixth-generation (6G)). Summary of the Invention

[0003] The article “a” preceding an element is unrestricted and should be understood to refer to “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, the word “or,” as used in a list of items (e.g., a list of items beginning with phrases such as “at least one,” “one or more,” or “one or two”) indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as referring to a closed set of conditions. For example, without departing from the scope of this disclosure, an example step described as “based on condition A” may be based on both condition A and condition B. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, the word “group” may comprise one or more elements.

[0004] A UE for wireless communication is described. The UE can be configured, is capable of, or is operable to multiplex UL data associated with the UE in one or more of the time or frequency domains according to at least one orthogonal code sequence, and to transmit waveforms carrying the multiplexed UL data associated with the UE via a Physical UL Shared Channel (PUSCH).

[0005] A method for wireless communication performed by a UE is described. The method is configured, capable of, or operable to multiplex UL data associated with the UE in one or more time or frequency domains according to at least one orthogonal code sequence, and to transmit a waveform carrying the multiplexed UL data associated with the UE via a PUSCH.

[0006] A processor for wireless communication is described. The processor is configured, capable, or operable to multiplex UL data associated with a UE in one or more of the time or frequency domains according to at least one or more orthogonal code sequences, and to transmit waveforms carrying the multiplexed UL data associated with the UE via a PUSCH.

[0007] A network apparatus (NE) for wireless communication is described. The NE is configured, capable, or operable to multiplex UL data of a plurality of UEs in one or more of the time or frequency domains according to at least one orthogonal code sequence, and to transmit waveforms carrying the multiplexed UL data of the plurality of UEs via a PUSCH.

[0008] A method for wireless communication performed by an NE is described. The method is configurable, capable, or operable to multiplex UL data of a plurality of UEs in one or more time or frequency domains according to at least one or more orthogonal code sequences, and to transmit waveforms carrying the multiplexed UL data of the plurality of UEs via a PUSCH.

[0009] A processor for wireless communication is described. The processor is configured, capable, or operable to multiplex UL data of a plurality of UEs in one or more of the time or frequency domains according to at least one or more orthogonal code sequences, and to transmit waveforms carrying the multiplexed UL data of the plurality of UEs via a PUSCH. Attached Figure Description

[0010] Figure 1 Examples of wireless communication systems according to aspects of this disclosure are described.

[0011] Figure 2A This document describes an example of Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) employing Orthogonal Cover Code (OCC) in the time domain, according to aspects of this disclosure.

[0012] Figure 2B This describes an example of applying OCC to UL data prior to DFT, based on aspects of this disclosure.

[0013] Figure 3A This describes an instance of OCC applied in the frequency domain to each resource block (RB) according to aspects of this disclosure.

[0014] Figure 3B This describes an example of a continuous mapping of resource elements (REs) of length 2 and 4 codes applied to a PUSCH according to aspects of this disclosure.

[0015] Figure 3C Examples of continuous and discontinuous scheduling of REs for application length 6-code OCCs are described according to aspects of this disclosure.

[0016] Figure 4 Examples of the application of the time and frequency of OCC sequences according to aspects of this disclosure are provided.

[0017] Figure 5 Examples of UEs based on aspects of this disclosure are described.

[0018] Figure 6 Examples of processors according to aspects of this disclosure are described.

[0019] Figure 7 Examples of NEs based on aspects of this disclosure are described.

[0020] Figure 8 A flowchart illustrating a method performed by a UE according to aspects of this disclosure.

[0021] Figure 9 A flowchart illustrating the method performed by NE according to aspects of this disclosure. Detailed Implementation

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

[0023] As an example, in an NTN, satellites can be configured with extensive geographic coverage areas, potentially resulting in numerous UEs located within these coverage areas. In some cases, such as wireless communication via Low Earth Orbit (LEO) satellites, several UEs within the geographic coverage area of ​​an LEO satellite may need to quickly coordinate with the LEO satellite (e.g., gaining access to the LEO satellite, obtaining resource allocation from the LEO satellite, etc.) to perform wireless communication (e.g., transmission) while within the LEO satellite's geographic coverage area. The limitations of the total available spectrum resources in an NTN may further necessitate significant improvements in system capacity efficiency. For example, depending on service patterns, some UEs may require more resources than others, thus potentially requiring further granular resource multiplexing.

[0024] Various aspects of this disclosure relate to enabling one or more UEs to support UL communication using orthogonal overlay codes (OCC), which may result in an increase in the UL capacity of one or more UEs, as described herein. Further aspects of this disclosure relate to one or more configurations for applying OCC to time-domain UL data channels while employing Discrete Fourier Transform to extend orthogonal frequency division multiplexing (DFT-s-OFDM) waveforms.

[0025] Aspects of this disclosure are described in the context of wireless communication systems.

[0026] Figure 1 This section describes an example of a wireless communication system 100 according to aspects of this disclosure. The wireless communication system 100 may include one or more NEs 102, one or more UEs 104, and a core network (CN) 106. The wireless communication system 100 may support various radio access technologies. In some embodiments, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-A network. In some other embodiments, the wireless communication system 100 may be an NR network, such as a 5G network, a 5G-A network, or a 5G Ultra Wideband (5G-UWB) network. In other embodiments, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies other than 5G, such as 6G. In addition, the wireless communication system 100 can support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0027] One or more NEs 102 may be distributed across a geographical area to form a wireless communication system 100. One or more of the NEs 102 described herein may be, include, or be referred to as a network node, base station, network element, network function, network entity, radio access network (RAN), NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. NEs 102 and UEs 104 may communicate via a communication link, which may be a wireless or wired connection. For example, NEs 102 and UEs 104 may perform wireless communication (e.g., receive signaling, transmit signaling) via a Uu interface.

[0028] NE 102 can provide a geographic coverage area that supports services for one or more UEs 104 within that geographic coverage area. For example, NE 102 and UE 104 can support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some embodiments, UE 102 can be mobile, such as a satellite associated with a non-terrestrial network (NTN). In some embodiments, different geographic coverage areas 112 associated with the same or different radio access technologies can overlap, but different geographic coverage areas can be associated with different NEs 102.

[0029] One or more UEs 104 may be distributed across a geographical area of ​​the wireless communication system 100. UE 104 may include or be referred to as a remote unit, mobile device, wireless device, remote device, subscriber device, transmitter device, receiver device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, and other instances thereof. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, and other instances thereof.

[0030] UE 104 may be able to support direct wireless communication with other UE 104 via a communication link. For example, UE 104 may support direct wireless communication with another UE 104 via 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, communication link 114 may be referred to as a side link. For example, UE 104 may support direct wireless communication with another UE 104 via a PC5 interface.

[0031] NE 102 may support communication with CN 106 or with another NE 102, or both. For example, NE 102 may interface with other NE 102 or CN 106 via one or more backhaul links (e.g., S1, N2, N2, or network interfaces). In some embodiments, NE 102 may communicate directly with each other. In some other embodiments, NE 102 may communicate with each other indirectly (e.g., via CN 106). In some embodiments, one or more NE 102 may include sub-components, such as access network entities, which may be instances of Access Node Controllers (ANCs). The ANC may communicate with one or more UE 104s via one or more other access network transmitting entities (which may be referred to as radio heads, smart radio heads, or TRPs).

[0032] CN 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. CN 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities (e.g., Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) that manage access and mobility, and user plane entities (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) that route packets or interconnect to external networks. In some implementations, the control plane entities may manage non-access stratum (NAS) functions of one or more UEs 104 served by one or more NEs 102 associated with CN 106, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.).

[0033] CN 106 can communicate with the packet data network via one or more backhaul links (e.g., via S1, N2, N2, or another network interface). The packet data network may contain an application server. In some implementations, one or more UEs 104 can communicate with the application server. UE 104 can establish a session (e.g., a Protocol Data Unit (PDU) session, etc.) with CN 106 via NE 102. CN 106 can use the established session (e.g., an established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and the application server. A PDU session may be an instance of a logical connection between UE 104 and CN 106 (e.g., one or more network functions of CN 106).

[0034] In the wireless communication system 100, NE 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some embodiments, NE 102 and UE 104 may support different resource structures. For example, NE 102 and UE 104 may support different frame structures. In some embodiments, such as in 4G, NE 102 and UE 104 may support a single frame structure. In some other embodiments, such as in 5G and other suitable radio access technologies, NE 102 and UE 104 may support various frame structures (i.e., multiple frame structures). NE 102 and UE 104 may support various frame structures based on one or more parameter sets.

[0035] The wireless communication system 100 may support one or more parameter sets, and the parameter sets may include subcarrier spacing and cyclic prefixes. A first parameter set (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a regular cyclic prefix. In some embodiments, the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one time slot per subframe. A second parameter set (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a regular cyclic prefix. A third parameter set (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a regular cyclic prefix or an extended cyclic prefix. A fourth parameter set (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a regular cyclic prefix. A fifth parameter set (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a regular cyclic prefix.

[0036] Time intervals for resources (e.g., communication resources) can be organized according to frames (also known as radio frames). Each frame may have a duration, for example, 10 milliseconds (ms). In some embodiments, each frame may contain multiple subframes. For example, each frame may contain 10 subframes, and each subframe may have a duration, for example, 1 ms. In some embodiments, each frame may have the same duration. In some embodiments, each subframe of a frame may have the same duration.

[0037] Alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may contain a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth parameter sets (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe, respectively. Each time slot may contain a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some embodiments, the number (e.g., quantity) of time slots in a subframe may depend on the parameter set. For a conventional cyclic prefix, a time slot may contain 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60 kHz subcarrier spacing), a time slot may contain 12 symbols. The relationship between the number of symbols per time slot for the regular cyclic prefix and the extended cyclic prefix, the number of time slots per subframe, and the number of time slots per frame may depend on the parameter set. It should be understood that references to the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and time slots.

[0038] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 may support one or more operating frequency bands, such as frequency range names FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some embodiments, NE 102 and UE 104 may perform wireless communication on one or more of the operating frequency bands. In some embodiments, FR1 may be used by NE 102 and UE 104, as well as other equipment or devices, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by NE 102 and UE 104, as well as other equipment or devices, for short-range, high data rate capabilities.

[0039] FR1 may be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 may be associated with a first parameter set containing a 15 kHz subcarrier spacing (e.g., μ=0); a second parameter set containing a 30 kHz subcarrier spacing (e.g., μ=1); and a third parameter set containing a 60 kHz subcarrier spacing (e.g., μ=2). FR2 may be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 may be associated with a third parameter set containing a 60 kHz subcarrier spacing (e.g., μ=2); and a fourth parameter set containing a 120 kHz subcarrier spacing (e.g., μ=3).

[0040] The solution discussed in this paper involves UL capacity enhancement techniques. According to TS 38.300 (incorporated herein by reference), the downlink transmit waveform is conventional orthogonal frequency division multiplexing (OFDM) using a cyclic prefix (CP). The UL transmit waveform is conventional OFDM using CP with transform precoding capabilities that perform Discrete Fourier Transform (DFT) extensions, which can be disabled or enabled. For operations accessed in FR1 using a shared spectrum channel, the UL transmit waveform subcarrier mapping can be mapped to subcarriers interleaved in one or more Physical Resource Blocks (PRBs).

[0041] In one embodiment, two transmission schemes are supported for the 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 the Wideband Probe Reference Signal (SRS) Resource Indicator (SRI) field from the DCI.

[0042] For PUSCH, spatial multiplexing based on closed-loop DMRS is supported. Up to 4 layers of transmission are supported for a given UE. The number of codewords is 1. When using transform precoding, only a single multiple-input multiple-output (MIMO) layer transmission is supported. Transmission durations of 1 to 14 symbols per time slot are supported, and multiple time slots can be repeatedly aggregated using transport blocks (TBs).

[0043] In one embodiment, two types of frequency hopping are supported: intra-slot frequency hopping and inter-slot frequency hopping in the case of time slot aggregation. Intra-slot and inter-slot frequency hopping are not supported when using PRB interleaved UL transmit waveforms.

[0044] In one embodiment, the PUSCH can be scheduled using DCI on the Physical Downlink Control Channel (PDCCH) or authorized via semi-static configuration through Radio Resource Control (RRC), supporting two types of operation: the first PUSCH is triggered by DCI, and subsequent PUSCH transmissions follow the RRC configuration and the scheduling received on the DCI; or the PUSCH is triggered by data arriving at the UE's transmit buffer, and the PUSCH transmissions follow the RRC configuration.

[0045] In one embodiment, the UL physical layer processing of the transport channel consists of the following steps: transport block CRC appending; code block segmentation and code block CRC appending; 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 precoding; mapping to assigned resources and antenna ports.

[0046] In one embodiment, the UE transmits at least one symbol with a demodulation reference signal on each layer of each frequency hopping frequency of the transmit PUSCH, and up to three additional DMRSs can be configured by higher layers. Phase tracking RSs can be transmitted on the additional symbols to assist receiver phase tracking. The UL-SCH physical layer model is described in TS 38.202, which is incorporated herein by reference.

[0047] For the configured authorized operation with shared spectrum channel access as described in Clause 10.3, the configured authorized UL control information (CG-UCI) may be transmitted in the PUSCH scheduled by the configured UL authorized operator.

[0048] In one embodiment, according to 3GPP TS 38.211, up to two codewords can be transmitted. In the case of single codeword transmission, .

[0049] For each codeword, bit block (in The number of bits in the codeword q transmitted over the physical channel should be scrambled before modulation to generate a scrambled bit block according to the following pseudocode.

[0050]

[0051] Where x and y are labels defined, for example, in TS 38.212 (incorporated herein by reference), and where the scrambling sequence As given in Clause 5.2.1, the scrambling sequence generator should be initialized using the following.

[0052]

[0053] in It is equal to the higher-level parameter data dataScramblingIdentityPUSCH (if configured), and RNTI is equal to C-RNTI, MCS-C-RNT1, SP-CSI-RNTI or CS-RNTI, and DCI format 0_0 is not used to schedule the launch in the common search space; The PUSCH transmission is equal to the higher-level parameter msgA-DataScramblingIndex (if configured), and is triggered by a Type 2 random access procedure as described in Clause 8.1A of TS 38.213 (incorporated herein by reference); otherwise ; It is the index of the random access preamble for the msgA transmission as described in Clause 5.1.3A of TS38.321 (incorporated herein by reference), and in which The RA-RNTI is equal to msgA, or otherwise corresponds to the RNTI associated with a 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).

[0054] For each codeword q, one of the modulation schemes in Table 6.3.1.2-1 should be used to modulate the scrambled bit block, as described in Clause 5.1. Modulation is performed to generate complex-valued modulation symbol blocks. .

[0055] In one embodiment, according to Table 7.3.1.3-1, the complex-valued modulation symbols of each of the codewords to be transmitted should be mapped to at most four layers. The complex-valued modulation symbols of codeword q It should be mapped to a layer , ,in It is the number of layers, and It is the number of modulation symbols in each layer.

[0056] In one embodiment, if transform precoding is not enabled according to TS 38.214 6.1.3, then for each layer , .

[0057] If transform precoding is enabled according to TS38.214 6.1.3 (in...), and It depends on the configuration of the phase tracking reference signal.

[0058] If the program instruction in TS 38.214 does not use a phase-tracking reference signal, then the complex-valued symbol block used for a single layer λ=0 is... It should be classified as Groups, each corresponding to an OFDM symbol and .

[0059] If the program in TS 38.214 indicates that a phase tracking reference signal is being used, then the complex value symbol block... It should be divided into several groups, each corresponding to an OFDM symbol, and among them, group contain Each symbol is mapped to the corresponding OFDM symbol before transform precoding. Complex value symbol ,in and .Group The index m of the PT-RS samples and the number of samples in each PT-RS group. and the number of PT-RS groups Defined in Clause 6.4.1.2.2.2. When OFDM symbol When there are one or more PT-RS samples, the number ,otherwise .

[0060] The precoding should be transformed according to the following applications.

[0061]

[0062] Obtain complex value symbol block .variable ,in This represents the bandwidth of PUSCH in terms of resource blocks, and should satisfy:

[0063]

[0064] in It is a set of non-negative integers.

[0065] In one embodiment, the vector block should be configured according to the following: Perform precoding

[0066]

[0067] in , Antenna port group It should be determined according to the procedure in [6,TS 38.214].

[0068] For non-codebook-based transmissions, the precoding matrix W is equal to the identity matrix.

[0069] For codebook-based transmission, the precoding matrix W depends on the number of antenna ports used for transmission—for single-layer transmission on a single antenna port, W=1; for transmission using 2 or 4 antenna ports, W is given in Tables 6.3.1.5-1 to 6.3.1.5-7; for transmission using 8 antenna ports, W is determined by… The matrix is ​​given, where the subscripts i and f(i) represent the rows of the corresponding matrices; f(i) is given in Table 6.3.1.5-8; the intermediate precoding matrix is ​​given. The details are given in 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, where... Represents a matrix with m rows and n columns, all zeros; submatrix The details are given in Tables 6.3.1.5-25 to 6.3.1.5-28 and 6.3.1.5-37 to 6.3.1.5-38.

[0070] The TPMI index used in the table above is obtained from the DCI or higher-layer parameters of the scheduled UL transmission according to the procedure in TS 38.214. When higher-layer parameters are not configured... At that time, the precoding matrix W=1.

[0071] Generally, this paper describes the use of orthogonal codes, such as OCC, to improve UL data channel capacity, while employing DFT-s-OFDM waveforms to allocate higher per-UE resources; that is, substantially the same time and / or frequency resources are allocated to different orthogonal UEs in the code domain. This capacity improvement may be necessary in NTNs because NTNs have large cell sizes and may require the simultaneous scheduling of many UEs. This disclosure describes how OCC can be used / selected to multiplex PUSCH transmissions of multiple UEs, where we describe the application of OCC sequences in the time domain, frequency domain, or both. Different mappings of applying OCC sequences in time and frequency are discussed. Furthermore, OCC sequences of different lengths that can be used for PUSCH transmissions are described.

[0072] According to the first embodiment, UL data for multiple users is multiplexed by multiplying with an orthogonal code specific to the UE, wherein the same time resources are used for different users, but the data is separated by using the orthogonal code.

[0073] In one embodiment, when using a DFT-s-OFDM waveform, the UL data is code-multiplexed in the time domain, such as... Figure 2A As shown in the image. Figure 2AThis section describes an example of DFT-s-OFDM employing OCC in the time domain according to aspects of this disclosure. In one example, UL data may be code-multiplexed 202 before the application of DFT 204, i.e., with transform precoding enabled (note: if transform precoding is disabled, the UE may not expect the application of orthogonal codes).

[0074] For example, after scrambling and modulation, UL data undergoes layer mapping. With transform precoding enabled, complex-valued symbol blocks (e.g., for each layer) are... of ) can be divided into Groups, each corresponding to an OFDM symbol, where It is the number of modulation symbols in each layer, and This is the number of subcarriers in each OFDM symbol of the UL data. Layered data is precoded using orthogonal sequences.

[0075]

[0076] in 220 corresponds to the first time slot in time slot 224. 222 OFDM symbol orthogonal codes, such as Figure 2B As shown in the image. Figure 2B This describes an example of applying OCC to UL data prior to DFT, based on aspects of this disclosure.

[0077] In one embodiment, when the Phase Tracking Reference Symbol (PTRS) is also used with transform precoding, orthogonal codes are applied to the UL data and also to the PTRS. In this case, complex-valued symbol blocks, for example, each layer of It can be divided into several groups, each group corresponding to an OFDM symbol, and the group... contain 1 symbol, and mapped to the corresponding OFDM symbol before applying orthogonal codes. Complex value symbol ,in ,in It is the number of samples in each PT-RS group, and Define the number of PT-RS groups. When OFDM symbols... When there are one or more PT-RS samples, the number ,otherwise In one implementation, the UL data is first multiplied by an orthogonal code, such as... Figure 2B As shown in the diagram, PTRS is then added in the time domain before applying the transform precoding (DFT), as described above.

[0078] In one embodiment, an orthogonal overlay code is applied after the inverse DFT (IDFT) 206 operation and before the insertion of the cyclic prefix 208. In this case, the reference signal is also pre-coded using orthogonal codes, while on the receiver side, the received signal is first decoded using orthogonal codes after the cyclic prefix is ​​removed.

[0079] In one embodiment, the length of the orthogonal code can be at most the time slot length, such as Figure 2B As shown, different combinations of codes can be defined as the maximum length of a maximum time slot. Defining the OCC as the maximum time slot length and defining the combination as the maximum time slot length provides the network with the flexibility to multiplex the same time resources for a maximum number of users (e.g., 14 users) with a maximum time slot length. When the number of time-domain resources allocated to a UE is small (e.g., less than the time slot length), the network can select a code corresponding to the allocated length of the time-domain symbols in the time slot; however, this also limits the number of UEs to be multiplexed with time-domain codes, i.e., the maximum number of users is at most the length of the number of time-domain symbols allocated in the time slot.

[0080] In one embodiment, to achieve full flexibility in multiplexing UEs up to multiple slot lengths, a table can be specified that specifies orthogonal codes, wherein different code combinations for all symbol lengths can be defined in table form to provide flexibility in allocating any number of resources to UEs, and also to select the number of UEs to be multiplexed. The table may include an index corresponding to the length of the code to be used, while another index may be used to indicate a specific code to be used from a code list, as shown in Table 1.

[0081] In one implementation, the type of orthogonal overlay code used for code multiplexing of data in the time domain is based on the Discrete Fourier Transform (as used for NR UL control channels), as shown in Table 1. However, unlike UL control channels, the code length can be further extended to at most the time slot length. Note that in Table 1... Defines the number of UL time-domain data symbols that the network can use to schedule data in a time slot when using OCC, where the maximum number can be the time slot length.

[0082] Table 1: Orthogonal sequences of PUSCH

[0083]

[0084] The selection of orthogonal codes plays a crucial role in the performance of an OCC system. Codes need to be carefully designed to ensure orthogonality and minimize cross-correlation between codes assigned to different users. Therefore, in one implementation, the type of orthogonal overlay code used for code multiplexing of data in the time domain is based on Golay orthogonal sequences, because Golay codes have good autocorrelation properties and minimal cross-correlation. Similar to DFT-based OCC, slot-length OCCs based on Golay codes can be generated and specified in a table, where the network can select appropriate codes for resource scheduling.

[0085] In another implementation, an OCC based on Walsh-Hadamard codes can be used for code multiplexing of PUSCH data in the time domain. For example, multiple tables are specified for OCCs used in UL, where each table defines the OCC for a specific code length, and an index defines the number of available codes for that length. (PUSCH symbol length) Examples of Walsh-Adama-based OCCs are shown in Table 2. Similarly, different tables with lengths of 2, 4, and 12 can be generated.

[0086] Table 2: PUSCH symbol length Furthermore, the Walsh-Adama-based OCC is used for data code multiplexing of up to 8 UEs in the time domain.

[0087]

[0088] According to the second embodiment, orthogonal codes (e.g., OCC) can be applied to UL data in the frequency domain, where multiple users will use the same frequency resources, but the data is separated in the frequency domain using orthogonal codes. In the case of DFT-s-OFDM waveforms, OCC can be applied after transform precoding (DFT) in the frequency domain, for example, once virtual resource blocks have been mapped to physical resource blocks. For example, for each antenna port used for PUSCH transmission, complex-valued symbol blocks are... (Derived from one of the configured modulation schemes (e.g., BPSK, QAM), and precoded after applying transform precoding (if enabled) multiplied by an amplitude scaling factor. To align with the transmission power.

[0089] Then press from The initial sequence maps the resulting symbols to resource elements in the virtual resource block assigned to the PUSCH emission. The mapping will not be performed on the corresponding physical resource block that is to be used to transmit associated reference signals (e.g., DMRS intended for use with other co-scheduled UEs). Within the assigned virtual resource block, it is performed by index. The resource elements allocated to PUSCH are implemented in ascending order. The mapping, where (Subcarrier index)=0 means the first subcarrier in the lowest-numbered virtual resource block, followed by the index. (Symbol Index), where the starting position is given by TS 38.214. Based on the mapping type, i.e., interleaved or non-interleaved mapping, complex-valued symbols are mapped from virtual resource blocks to physical resource blocks. After data symbols have been mapped to physical resource blocks, OCC is applied.

[0090]

[0091] In one implementation, when PTRS is enabled together with transform precoding and OCC is also configured in the frequency domain, UL data and PTRS will be code-multiplexed in the frequency domain because PTRS has been added in the time domain before DFT is applied. In one implementation, OCC can be applied once the frequency-domain precoded data is mapped to a virtual resource block, i.e., before interleaving or non-interleaving mapping is applied.

[0092] In one implementation, when code multiplexing in the frequency domain and transform precoding are enabled for PUSCH, this means that only PUSCH data will be multiplexed with OCC. However, other reference signals, such as DMRS and CSI-RS, may not be code multiplexed with the PUSCH data.

[0093] In one embodiment, orthogonal codes of varying lengths can be implemented to apply OCC in the frequency domain, thereby achieving lower PAPR or providing greater flexibility in scheduling frequency domain resources. For example, code lengths that are multiples of 2 can be defined and specified in tabular form, where codes of lengths 2, 4, 6, and 12 can be used. For this purpose, any of Walsh-Hadamard codes, DFT-based codes, or Gore codes (or combinations thereof) can be used as OCCs. Different implementations of OCCs with lengths of 2, 4, and 12 are shown in Tables 3, 4, 5, and 6.

[0094] Table 3: Orthogonal sequences of length 2 based on Walsh-Adama or DFT for FD-OCC-based PUSCH

[0095]

[0096] Table 4: Orthogonal sequences of length 4 based on Walsh-Adama used for FD-OCC-based PUSCH

[0097]

[0098] Table 5: DFT-based orthogonal sequences of length 4 used for FD-OCC-based PUSCH

[0099]

[0100] Table 6: DFT-based orthogonal sequences of length 12 used for FD-OCC-based PUSCH

[0101]

[0102] Depending on the maximum number of UEs to be multiplexed, and also based on the acceptable peak-to-average power ratio (PAPR) requirement for the coverage area, different types of RE mappings can be implemented for applying OCC to PUSCH.

[0103] In one implementation, a maximum of one RB length OCC can be used to code multiplex UL data from different UEs, where the number of codes can be specified in a table-like manner depending on the number of UEs whose UL data is to be multiplexed in the frequency domain. UEs can be scheduled to use one of the codes from the table, where the UE applies the selected code to all elements of the RB, such as... Figure 3A As shown in the image. Figure 3A This describes the instance OCC applied in the frequency domain to each RB according to aspects of this disclosure. Note that the resource block length can provide frequency domain code multiplexing for up to 12 UEs. In one implementation, when a UE is scheduled for multiple RBs 302 and also for a frequency domain OCC 304, the UE applies the selected code sequence to all RBs 302. Alternatively, the UE can be scheduled with different RB length code sequences for different RBs 302.

[0104] In one embodiment, consecutive RE scheduling is used to apply OCC in the frequency domain, where a comb structure may be employed. For example, when scheduling this mapping, consecutive REs within an RB are then used to apply OCC in the frequency domain, and gaps of the same length within the RB can be used to apply OCC again. For example, as... Figure 3B As shown in the image, Figure 3B This illustration describes an example of a continuous mapping of REs for applying 2- and 4-code OCCs to a PUSCH according to aspects of this disclosure. Two consecutive REs 306 are used for the 2-code application, with the next OCC applied after a gap between the two REs. In this case, a total of 6 REs within the RB are scheduled for the 2-code. Similarly, in the same figure, an example of applying a 4-code with 4 consecutive REs 308 is shown.

[0105] In one embodiment, discontinuous RE scheduling is used to apply OCC in the frequency domain, where the UE can be scheduled to apply OCC in RBs with some RE gaps in between. For example, as Figure 3C As shown in the image, Figure 3C This section describes an example of continuous and discontinuous scheduling of REs for applying a 6-code OCC according to aspects of this disclosure. The 6-code OCC 310 will be applied with a discontinuous mapping 312, where every other / alternating RE is used to apply the OCC. This gap and code can be configured for the UE.

[0106] In one implementation, the number of frequency resources to be scheduled can be limited to the length of the OCC to be applied. For example, if a 4-code length will be used, then the UE can be scheduled to use a maximum of 4 REs within an RB. Therefore, the RB can be divided into 3 groups of 4 REs, where a 4-code length can be used in each group of REs within the RB. This means that when this frequency domain OCC application is configured, the UE will only be allocated a fixed group of REs corresponding to the code length within one RB.

[0107] According to the third embodiment, the OCC sequence is applied to PUSCH transmissions in both the frequency 402 and time 404 domains, such as... Figure 4 As shown in the image, Figure 4 Examples of time and frequency applications of the OCC sequences according to aspects of this disclosure are provided to increase UL capacity because they offer greater flexibility to accommodate the number of users while reducing signaling workload. For example, an index 4 OCC (defining four orthogonal codes) defined for both the frequency and time domains can multiplex up to 16 UEs, thus increasing capacity by 16 times. Defining fewer codes requires fewer bits to indicate the corresponding OCC sequence to be used for PUSCH. For example, a 4-index code would require two bits to indicate to the UE to select the OCC sequence.

[0108] Figure 5 An example of a UE 500 according to aspects of this disclosure is described. UE 500 may include a processor 502, a memory 504, a controller 506, and a transceiver 508. The processor 502, memory 504, controller 506, or transceiver 508, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure as described herein. These components may be coupled via one or more interfaces (e.g., operatively, communicatively, functionally, electronically, electrically).

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

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

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

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

[0113] UE 500 may be configured to support a component for receiving an indication of the UE’s network access restriction enforcement capability, receiving a handover request from the UE, determining the UE’s network access restriction information, transmitting the network access restriction information to network entities associated with different networks, and transmitting a handover command including the network access restriction information to a base station associated with the UE for processing the handover request based on the network access restriction information.

[0114] In one embodiment, the UE 500 may be configured to support a component for multiplexing UL data associated with the UE in one or more of the time or frequency domains according to at least one orthogonal code sequence, and for transmitting waveforms carrying the multiplexed UL data associated with the UE via the PUSCH.

[0115] In one embodiment, the UE 500 may be configured to support a component for receiving from a network entity a configuration comprising a set of one or more orthogonal code sequences, the set of one or more orthogonal code sequences including the at least one orthogonal code sequence.

[0116] In one embodiment, the UE 500 may be configured to support a component for selecting at least one or more orthogonal code sequences from the set of one or more orthogonal code sequences.

[0117] In one embodiment, at least one orthogonal code sequence is orthogonal in multiple different UEs.

[0118] In one embodiment, UE 500 may be configured to support a component for applying at least one orthogonal code sequence to UL data of multiple UEs and a set of one or more phase tracking reference symbols.

[0119] In one embodiment, UE 500 may be configured to support a component for applying at least one orthogonal code sequence to the UL data of multiple UEs after applying IDFT.

[0120] In one embodiment, the length of at least one orthogonal code sequence is less than or equal to the length of a time slot. In one embodiment, the UE 500 may be configured to support a component for generating at least one orthogonal code sequence based at least in part on an applied Discrete Fourier Transform.

[0121] In one embodiment, the UE 500 may be configured to support a component for generating at least one orthogonal code sequence based at least in part on the application of the Walsh-Adama transform.

[0122] In one embodiment, the UE 500 may be configured to support a component for generating at least one orthogonal code sequence based at least in part on the Gore orthogonal sequence.

[0123] In one embodiment, the UE 500 may be configured to support a component for applying orthogonal code sequences of different lengths in the frequency domain.

[0124] In one embodiment, at least one orthogonal code sequence has a resource block length.

[0125] In one embodiment, the UE 500 may be configured to support a component for applying at least one orthogonal code sequence in the frequency domain using a continuous type resource element mapping.

[0126] In one embodiment, at least one orthogonal sequence of the same length is applied over consecutive resource elements of a resource block in such a way that there are no gaps between them.

[0127] In one embodiment, the UE 500 may be configured to support a component for applying at least one orthogonal code sequence in the frequency domain using a non-contiguous type resource element mapping.

[0128] In one embodiment, at least one orthogonal sequence of the same length is applied such that there are gaps between resource elements within a resource block. In one embodiment, the number of resources to be scheduled is limited to the length of the at least one orthogonal code sequence. In one embodiment, the at least one orthogonal code sequence includes at least one orthogonal overlay code sequence. In one embodiment, the waveform includes a DFT-s-OFDM waveform.

[0129] Controller 506 manages the input and output signals of UE 500. Controller 506 can also manage peripheral devices not integrated into UE 500. In some embodiments, controller 506 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some embodiments, controller 506 may be implemented as part of processor 502.

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

[0131] Receiver chain 510 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, receiver chain 510 may include one or more antennas for receiving signals over the air or over a wireless medium. Receiver chain 510 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. 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 signal transmission. Receiver chain 510 may include at least one decoder for decoding and processing the demodulated signal to receive the transmitted data.

[0132] Transmitter chain 512 can be configured to generate and transmit signals (e.g., control information, data, packets). 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). 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 a wireless medium. Transmitter chain 512 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0133] Figure 6An example of a processor 600 according to aspects of this disclosure is described. Processor 600 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 600 may include a controller 602 configured to perform various operations according to the examples described herein. Processor 600 may optionally include at least one memory 604, which may be, for example, an L1 / L2 / L3 cache. Additionally or alternatively, processor 600 may optionally include one or more arithmetic logic units (ALUs) 606. One or more of these components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0134] Processor 600 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, transmit, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to the processor chipset (e.g., processor 600) or contained within the processor chipset (e.g., 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).

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

[0136] Controller 602 may be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 604 and determine subsequent instructions to be executed to enable processor 600 to support various operations according to examples described herein. Controller 602 may be configured to track the memory addresses of instructions associated with memory 604. Controller 602 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 602 may be configured to interpret instructions and determine control signals to be output to other components of processor 600 to enable processor 600 to support various operations according to examples described herein. Additionally or alternatively, controller 602 may be configured to manage data flow within processor 600. Controller 602 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 600.

[0137] Memory 604 may include one or more caches (e.g., memory local to processor 600 or included in processor 600) or other memories, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some embodiments, memory 604 may reside within or on the processor chipset (e.g., local to processor 600). In some other embodiments, memory 604 may reside outside the processor chipset (e.g., remote from processor 600).

[0138] Memory 604 may store computer-readable, computer-executable code containing instructions that, when executed by processor 600, cause processor 600 to perform the 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. Controller 602 and / or processor 600 may be configured to execute computer-readable instructions stored in memory 604 to cause processor 600 to perform various functions. For example, processor 600 and / or controller 602 may be coupled to or coupled to memory 604, and processor 600, controller 602, and memory 604 may be configured to perform the various functions described herein. In some instances, processor 600 may include multiple processors, and memory 604 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be individually or collectively configured to perform the various functions described herein.

[0139] One or more ALUs 606 may be configured to support various operations according to the examples described herein. In some embodiments, one or more ALUs 606 may reside within or on a processor chipset (e.g., processor 600). In some other embodiments, one or more ALUs 606 may reside outside the processor chipset (e.g., processor 600). One or more ALUs 606 may perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALUs 606 may receive input operands and opcodes, the opcodes determining the operation to be performed. One or more ALUs 606 may be configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Alternatively, one or more ALU 606s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 606s to handle conditional operations, comparisons, and bitwise operations.

[0140] Processor 600 may support wireless communication according to examples disclosed herein. In one embodiment, processor 600 may be configured or operable to support a component for multiplexing UL data associated with the UE in one or more of the time or frequency domains according to at least one orthogonal code sequence, and for transmitting waveforms carrying the multiplexed UL data associated with the UE via PUSCH.

[0141] In one embodiment, processor 600 may be configured or operable to support a component for receiving from a network entity a configuration comprising a set of one or more orthogonal code sequences, the set of one or more orthogonal code sequences including the at least one orthogonal code sequence.

[0142] In one embodiment, processor 600 may be configured or operable to support a component for selecting at least one or more orthogonal code sequences from the set of one or more orthogonal code sequences.

[0143] In one embodiment, at least one orthogonal code sequence is orthogonal in multiple different UEs.

[0144] In one embodiment, processor 600 may be configured or operable to support a component for applying at least one orthogonal code sequence to UL data of multiple UEs and a set of one or more phase tracking reference symbols.

[0145] In one embodiment, processor 600 may be configured or operable to support a component for applying at least one orthogonal code sequence to UL data of multiple UEs after IDFT application.

[0146] In one embodiment, the length of at least one orthogonal code sequence is less than or equal to the length of a time slot. In one embodiment, processor 600 may be configured or operable to support a component for generating at least one orthogonal code sequence based at least in part on an applied discrete Fourier transform.

[0147] In one embodiment, processor 600 may be configured or operable to support a component for generating at least one orthogonal code sequence based at least in part on the application of Walsh-Adama transform.

[0148] In one embodiment, processor 600 may be configured or operable to support a component for generating at least one orthogonal code sequence based at least in part on Gore orthogonal sequences.

[0149] In one embodiment, processor 600 may be configured or operable to support a component for applying orthogonal code sequences of different lengths in the frequency domain.

[0150] In one embodiment, at least one orthogonal code sequence has a resource block length.

[0151] In one embodiment, processor 600 may be configured or operable to support a component for applying at least one orthogonal code sequence in the frequency domain using a continuous type resource element mapping.

[0152] In one embodiment, at least one orthogonal sequence of the same length is applied over consecutive resource elements of a resource block in such a way that there are no gaps between them.

[0153] In one embodiment, processor 600 may be configured or operable to support a component for applying at least one orthogonal code sequence in the frequency domain using a non-contiguous type resource element mapping.

[0154] In one embodiment, at least one orthogonal sequence of the same length is applied such that there are gaps between resource elements within a resource block. In one embodiment, the number of resources to be scheduled is limited to the length of the at least one orthogonal code sequence. In one embodiment, the at least one orthogonal code sequence includes at least one orthogonal overlay code sequence. In one embodiment, the waveform includes a DFT-s-OFDM waveform.

[0155] Figure 7An example of NE 700 according to aspects of this disclosure is described. NE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, memory 704, controller 706, or transceiver 708, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure as described herein. These components may be coupled via one or more interfaces (e.g., operatively ground, communicatively ground, functional ground, electronic ground, electrical ground).

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

[0157] The NE 700 can be configured to support a component for multiplexing UL data of multiple UEs in one or more of the time or frequency domains according to at least one orthogonal code sequence, and transmitting waveforms carrying multiplexed UL data of multiple UEs via PUSCH.

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

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

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

[0161] Controller 706 manages the input and output signals of NE 700. Controller 706 can also manage peripheral devices not integrated into NE 700. In some embodiments, controller 706 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some embodiments, controller 706 may be implemented as part of processor 702.

[0162] In some embodiments, the NE 700 may include at least one transceiver 708. In other embodiments, 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.

[0163] Receiver chain 710 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, receiver chain 710 may include one or more antennas for receiving signals over the air or over a wireless medium. Receiver chain 710 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. 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 signal transmission. Receiver chain 710 may include at least one decoder for decoding and processing the demodulated signal to receive the transmitted data.

[0164] Transmitter chain 712 can be configured to generate and transmit signals (e.g., control information, data, packets). 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). 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 a wireless medium. Transmitter chain 712 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0165] Figure 8A flowchart illustrating a method according to an aspect of this disclosure is provided. The operation of the method can be implemented by a UE, as described herein. In some embodiments, the UE can execute a set of instructions to control functional elements of the UE to perform the described functions.

[0166] At 802, the method can multiplex UL data associated with the UE in one or more of the time or frequency domains according to at least one orthogonal code sequence. Operation 802 can be performed according to the examples described herein. In some embodiments, aspects of operation 802 may be referenced from... Figure 5 The UE execution described.

[0167] At 804, the method can transmit a waveform carrying multiplexed UL data associated with the UE via the PUSCH. Operation 804 can be performed according to the examples described herein. In some embodiments, aspects of operation 804 may be described by reference to Figure 5 The UE execution described.

[0168] Figure 9 A flowchart illustrating a method according to an aspect of this disclosure is provided. The operation of the method may be implemented by the NE, as described herein. In some embodiments, the NE may execute a set of instructions to control the functional elements of the NE to perform the described functions.

[0169] At 902, the method can multiplex UL data of multiple UEs in one or more of the time or frequency domains based on at least one orthogonal code sequence. Operation 902 can be performed according to the examples described herein. In some embodiments, aspects of operation 902 may be referenced from... Figure 7 The described NE execution.

[0170] At 904, the method can transmit a waveform carrying multiplexed UL data of multiple UEs via the PUSCH. Operation 904 can be performed according to the examples described herein. In some embodiments, aspects of operation 904 may be described by reference to Figure 7 The described NE execution.

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

[0172] The description herein is provided to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE) for wireless communication, comprising: At least one memory; and At least one processor, coupled to and configured to enable the UE to: Multiplexing uplink UL data associated with the UE in one or more of the time or frequency domains based on at least one or more orthogonal code sequences; and Waveforms carrying the multiplexed UL data associated with the UE are transmitted via the 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 configuration from a network entity including a set of one or more orthogonal code sequences, the set of one or more orthogonal code sequences comprising the at least one orthogonal code sequence; and Select at least one or more orthogonal code sequences from the set of one or more orthogonal code sequences.

3. The UE according to claim 1, wherein the at least one orthogonal code sequence is orthogonal among a plurality of different UEs.

4. The UE of claim 1, wherein the at least one processor is configured to apply the at least one orthogonal code sequence to the UL data of a plurality of UEs and a set of one or more phase tracking reference symbols.

5. The UE of claim 1, wherein the at least one processor is configured to apply the at least one orthogonal code sequence to the UL data of a plurality of UEs after applying the inverse discrete Fourier transform (IDFT).

6. The UE according to claim 1, wherein the length of the at least one orthogonal code sequence is less than or equal to the length of the time slot.

7. The UE of claim 1, wherein the at least one processor is configured such that the UE generates the at least one orthogonal code sequence at least in part based on the application of a discrete Fourier transform.

8. The UE of claim 1, wherein the at least one processor is configured to generate the at least one orthogonal code sequence based at least in part on the application of the Walsh-Adama transform.

9. The UE of claim 1, wherein the at least one processor is configured to generate the at least one orthogonal code sequence based at least in part on the Gore-Ley orthogonal sequence.

10. The UE of claim 1, wherein the at least one processor is configured to apply orthogonal code sequences of different lengths in the frequency domain.

11. The UE of claim 1, wherein the at least one orthogonal code sequence has a resource block length.

12. The UE of claim 1, wherein the at least one processor is configured to enable the UE to apply the at least one orthogonal code sequence in the frequency domain using a continuous type resource element mapping.

13. The UE of claim 12, wherein at least one orthogonal code sequence of the same length is applied on consecutive resource elements of a resource block in such a manner that there are no gaps between them.

14. The UE of claim 1, wherein the at least one processor is configured to enable the UE to apply the at least one orthogonal code sequence in the frequency domain using non-contiguous type resource element mapping.

15. The UE of claim 14, wherein at least one orthogonal sequence of the same length is applied in such a manner that there are gaps between resource elements within a resource block.

16. The UE of claim 1, wherein the number of resources to be scheduled is limited to the length of the at least one orthogonal code sequence.

17. The UE according to claim 1, wherein the at least one orthogonal code sequence comprises at least one orthogonal overlay code sequence.

18. A processor for wireless communication, comprising: At least one controller, coupled to at least one memory and configured to enable the processor to: Multiplexing uplink UL data associated with the User Equipment (UE) in one or more of the time or frequency domains based on at least one orthogonal code sequence; and Waveforms carrying the multiplexed UL data associated with the UE are transmitted via the Physical UL Shared Channel (PUSCH).

19. A method performed by a user equipment (UE), the method comprising: Multiplexing uplink UL data associated with the UE in one or more of the time or frequency domains based on at least one or more orthogonal code sequences; and Waveforms carrying the multiplexed UL data associated with the UE are transmitted via the Physical UL Shared Channel (PUSCH).

20. A network device NE for wireless communication, comprising: At least one memory; and At least one processor, coupled to the at least one memory and configured to enable the NE: Multiplexing uplink UL data of multiple User Equipments (UEs) in one or more of the time or frequency domains based on at least one or more orthogonal code sequences; and Waveforms carrying the multiplexed UL data of the multiple UEs are transmitted via the Physical UL Shared Channel (PUSCH).

Images