Uplink shared channel multiplexing based on frequency domain orthogonal cover codes

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a configuration associated with an orthogonal cover code (OCC) sequence, where the OCC sequence is associated with a physical uplink shared channel (PUSCH) multiplexing based on frequency domain OCC. The UE may transmit a PUSCH transmission based at least in part on the configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission. Numerous other aspects are described.

Description

Cross-reference to related applications

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 366,444, filed August 7, 2023, entitled “FREQUENCY DOMAIN ORTHOGONALCOVER CODE BASED UPLINK SHARED CHANNEL MULTIPLEXING”, assigned to the assignee of this application. The disclosure of the earlier application is considered part of this patent application and is incorporated herein by reference. Technical Field

[0002] All aspects of this disclosure relate to wireless communication in general, and to techniques and apparatus for physical uplink shared channel (PUSCH) multiplexing based on frequency domain orthogonal cover code (OCC). Background Technology

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0004] A wireless network may include one or more network nodes that support communication for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with network nodes via downlink and uplink communication. A "downlink" (or "DL") refers to the communication link from the network node to the UE, and an "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via local links (e.g., sidelinks (SL), wireless local area network (WLAN) links, and / or wireless personal area network (WPAN) links, etc.).

[0005] The aforementioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, country, region, and / or global levels. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard issued by 3GPP. NR is designed to better support mobile broadband internet access by: improving spectrum efficiency; reducing costs; improving service; utilizing new spectrum; and better integrating with other open standards by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (CP-OFDM), and CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink; and supporting beamforming, Multiple-Input Multiple-Output (MIMO) antenna technologies and carrier aggregation. Further improvements to LTE, NR, and other radio access technologies remain useful as the demand for mobile broadband access continues to increase. Summary of the Invention

[0006] In some specific implementations, an apparatus for wireless communication at a user equipment (UE) includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to: receive a configuration associated with an orthogonal coverage code (OCC) sequence, wherein the OCC sequence is associated with frequency-domain OCC-based physical uplink shared channel (PUSCH) multiplexing; and transmit PUSCH transmissions at least in part based on the configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission.

[0007] In some specific implementations, an apparatus for wireless communication at a network node includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to: transmit a configuration associated with an OCC sequence, wherein the OCC sequence is associated with PUSCH multiplexing based on frequency domain OCC; and receive PUSCH transmissions at least in part based on the configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission.

[0008] In some specific implementations, a method of wireless communication performed by a UE includes: receiving a configuration associated with an OCC sequence, wherein the OCC sequence is associated with PUSCH multiplexing based on frequency domain OCC; and transmitting a PUSCH transmission based at least in part on the configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission.

[0009] In some specific implementations, a wireless communication method performed by a network node includes: transmitting a configuration associated with an OCC sequence, wherein the OCC sequence is associated with PUSCH multiplexing based on frequency domain OCC; and receiving PUSCH transmissions at least in part based on the configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission.

[0010] In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: receive a configuration associated with an OCC sequence, wherein the OCC sequence is associated with PUSCH multiplexing based on frequency domain OCC; and transmit a PUSCH transmission at least in part based on the configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission.

[0011] In some implementations, a non-transitory computer-readable medium stores a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a network node, cause the network node to: transmit a configuration associated with an OCC sequence, wherein the OCC sequence is associated with PUSCH multiplexing based on frequency domain OCC; and receive PUSCH transmissions at least in part based on the configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission.

[0012] In some specific implementations, an apparatus for wireless communication includes: a component for receiving a configuration associated with an OCC sequence, wherein the OCC sequence is associated with PUSCH multiplexing based on frequency domain OCC; and a component for transmitting PUSCH transmissions at least in part based on the configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission.

[0013] In some specific implementations, an apparatus for wireless communication includes: a component for transmitting a configuration associated with an OCC sequence, wherein the OCC sequence is associated with a PUSCH multiplexing based on frequency domain OCC; and a component for receiving a PUSCH transmission at least in part based on the configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission.

[0014] The entirety of the terms includes methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the accompanying drawings and description and illustrated as illustrated in the drawings and description.

[0015] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to provide a better understanding of the detailed description that follows. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose of this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, in both their organization and manner of operation, and the associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the drawings provided is for illustrative and descriptive purposes and not as a definition of limitation of the claims.

[0016] While aspects are described herein by way of example, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or package arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user equipment of various sizes, shapes, and configurations. Attached Figure Description

[0017] To gain a full understanding of the foregoing features of this disclosure, a more specific description of the brief overview can be obtained by referring to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered as limiting its scope, as other equally valid aspects may be acknowledged in this description. The same reference numerals in different drawings may identify the same or similar elements.

[0018] Figure 1 This is a diagram illustrating an example of a wireless network according to the present disclosure.

[0019] Figure 2 This is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0020] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0021] Figure 4 This is a diagram illustrating an example of frequency domain orthogonal coverage code (OCC) multiplexing for two UEs according to this disclosure.

[0022] Figures 5 to 9 This is a diagram illustrating an example of physical uplink shared channel (PUSCH) multiplexing associated with frequency domain OCC according to this disclosure.

[0023] Figures 10 to 11 This is a diagram illustrating an example process associated with frequency domain OCC-based PUSCH multiplexing according to this disclosure.

[0024] Figures 12 to 13 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0025] In non-terrestrial networks (NTNs), the uplink signal-to-noise ratio (SNR) may be relatively low, and to compensate for the relatively low coverage, Physical Uplink Shared Channel (PUSCH) transmissions by User Equipment (UEs) may need to be repeated multiple times. These repetitions can be used to multiplex multiple UEs with Orthogonal Coverage Codes (OCCs), which can increase overall system capacity. By multiplexing multiple UEs with OCCs, the same number of resources can support a larger number of UEs. However, a UE may not be configured with an OCC sequence to support PUSCH multiplexing with OCCs. As a result, the UE may not be able to apply OCCs that allow PUSCH multiplexing, which may prevent the use of these repetitions to support multiplexing of multiple UEs and thus may prevent an increase in overall system capacity.

[0026] The various aspects generally involve frequency-domain OCC-based PUSCH multiplexing. Some aspects more specifically involve configuring OCC sequences associated with frequency-domain OCC-based PUSCH multiplexing. In some examples, a UE may receive configuration associated with an OCC sequence from a network node associated with an NTN. This OCC sequence may be associated with frequency-domain OCC-based PUSCH multiplexing. This OCC sequence may be associated with resource mapping to frequency-domain subcarriers. Frequency-domain OCC-based PUSCH multiplexing may involve multiple PUSCH transmissions from multiple UEs respectively. This configuration may indicate to the UE which OCC sequence the UE should apply. The UE may transmit PUSCH to the network node based at least in part on this configuration. The OCC sequence may be applied to one or more symbols associated with the PUSCH transmission.

[0027] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to implement frequency-domain OCC-based PUSCH multiplexing by configuring an OCC sequence associated with frequency-domain OCC-based PUSCH multiplexing, which compensates for relatively low NTN coverage. In some aspects, the UE can be configured to support PUSCH multiplexing with OCC, at least in part based on the configuration associated with the OCC sequence. The UE can be able to apply OCCs that allow PUSCH multiplexing, which can allow multiplexing of multiple UEs to be supported by repetition, and thus increase overall system capacity.

[0028] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art will appreciate that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Furthermore, the scope of this disclosure is intended to cover such apparatuses or methods practiced using structures, functionalities, or structures and functionalities other than or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims.

[0029] Various devices and techniques will now be used to illustrate several aspects of a telecommunications system. These devices and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0030] Although terms generally associated with 5G or New Radio (NR) Radio Access Technology (RAT) may be used herein to describe aspects, aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or 5G and later (e.g., 6G) RATs.

[0031] Figure 1This is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., LTE) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., LTE) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), one or more UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. Network node 110 is a network node that communicates with UE 120. As shown, network node 110 may include one or more network nodes. For example, network node 110 can be an aggregated network node, meaning that an aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0032] In some examples, network node 110 is or includes network nodes (such as RUs) that communicate with UE 120 via a radio access link. In some examples, network node 110 is or includes network nodes (such as DUs) that communicate with other network nodes 110 via a fronthaul or midhaul link. In some examples, network node 110 is or includes network nodes (such as CUs) that communicate with other network nodes 110 via a midhaul link or with the core network via a backhaul link. In some examples, network node 110 (such as aggregated network node 110 or decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. Network node 110 may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, Transmit / Receive Points (TRPs), DUs, RUs, CUs, network mobility elements, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some examples, network nodes 110 can interconnect with each other or to one or more other network nodes 110 in the wireless network 100 using any suitable transport network through various types of fronthaul, midhaul, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

[0033] In some examples, network node 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), depending on the context of terminology use, the term "cell" may refer to the coverage area of ​​network node 110 and / or the network node subsystem serving that coverage area. Network node 110 may provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell may cover a relatively large geographic area (e.g., with a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UE 120 associated with the femtocell (e.g., UE 120 in a Closed Subscriber Group (CSG)). Network node 110 used for macrocells may be referred to as a macro network node. Network node 110 used for picocells may be referred to as a pico network node. The network node 110 used for femtocells can be referred to as a femtocell network node or a home network node. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 102a, network node 110b can be a pico network node for pico cell 102b, and network node 110c can be a femto network node for femto cell 102c. Network nodes can support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographical area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

[0034] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, "base station" or "network node" may refer to a CU, DU, RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of that function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions can be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one base station function rather than another. In this way, a single device may include more than one base station.

[0035] Wireless network 100 may include one or more relay stations. A relay station is a network node that can receive data transmissions from upstream nodes (e.g., network node 110 or UE 120) and transmit data to downstream nodes (e.g., UE 120 or network node 110). A relay station may be a UE 120 that can relay transmissions for other UE 120s. Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. The network node 110 for relay communication may be referred to as a relay station, relay base station, relay network node, relay node, repeater, etc.

[0036] Wireless network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different effects on interference in wireless network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0037] Network controller 130 may be coupled to or communicate with a group of network nodes 110, and may provide coordination and control for these network nodes 110. Network controller 130 may communicate with network nodes 110 via a backhaul or midhaul communication link. Network nodes 110 may also communicate directly with each other, or indirectly via a wireless or wired backhaul communication link. In some aspects, network controller 130 may be a CU or a core network device, or may include a CU or a core network device.

[0038] UE 120 may be distributed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, a UE function of a network node, and / or any other suitable device configured to communicate via wireless or wired media.

[0039] Some UEs 120 may be considered Machine-Type Communication (MTC) or Evolved or Enhanced Machine-Type Communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags that can communicate with network nodes, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (Narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. UEs 120 may be contained within a housing that houses components of the UE 120, such as processor components and / or memory components. In some examples, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0040] Generally, any number of wireless networks 100 can be deployed in a given geographical area. Each wireless network 100 can support a specific RAT and can operate on one or more frequencies. A RAT may be referred to as a radio technology, air interface, etc. A frequency may be referred to as a carrier, frequency channel, etc. Each frequency in a given geographical area can support a single RAT to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0041] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary device to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols) and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0042] Devices in Wireless Network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices in Wireless Network 100 can communicate using one or more operating frequency bands. In 5G NR, two initial operating frequency bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, FR1 is generally (interchangeably) referred to as the “sub-6GHz” band in various documents and articles. Similar naming issues sometimes occur with FR2, which is generally (interchangeably) referred to as the “millimeter wave” band in documents and articles, although this is different from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0043] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating frequency bands have been identified as the frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0044] Considering the examples above, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" is used herein, it can broadly refer to frequencies below 6 GHz, within FR1, or including intermediate frequency bands. Furthermore, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" is used herein, it can broadly refer to frequencies that can include intermediate frequency bands, within FR2, FR4, FR4-a, or FR4-1 and / or FR5, or within the EHF band. Modifications to frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) are contemplated, and the techniques described herein are applicable to those modified frequency ranges.

[0045] In some aspects, the UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive a configuration associated with an OCC sequence, wherein the OCC sequence is associated with frequency-domain OCC-based PUSCH multiplexing; and transmit PUSCH transmissions at least in part based on the configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0046] In some aspects, a network node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may transmit a configuration associated with an OCC sequence, wherein the OCC sequence is associated with PUSCH multiplexing based on frequency-domain OCC; and receive PUSCH transmissions at least in part based on this configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0047] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0048] Figure 2 This is a diagram illustrating example 200 of communication between network node 110 and UE 120 in a wireless network 100 according to this disclosure. Network node 110 may be equipped with a set of antennas 234a to 234t, such as... T One antenna ( T ≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R One antenna ( R ≥1). Network node 110 of Example 200 includes one or more radio frequency components, such as antenna 234 and modem 232. In some examples, network node 110 may include an interface, communication components, or another component that facilitates communication with UE 120 or another network node. Some network node 110 may not include radio frequency components that facilitate direct communication with UE 120, such as one or more CUs or one or more DUs.

[0049] At network node 110, transmitting processor 220 can receive data from data source 212 intended for use by UE 120 (or a group of UEs 120). Transmitting processor 220 can select one or more modulation and decoding schemes (MCS) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 can process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120 and can provide data symbols for UE 120. Transmitting processor 220 can process system information (e.g., semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and control symbols. Transmitting processor 220 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can transmit a set of output symbol streams (e.g., T Each output symbol stream is provided to a corresponding set of modems 232 (e.g., ...). TEach modem 232a to 232t may be used to process a corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. For example, each output symbol stream may be provided to a modulator component (MOD) of modem 232. Each modem 232 may use a corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may also use a corresponding modulator component to process the output sample stream (e.g., convert to analog, amplify, filter, and / or up-convert) to obtain a downlink signal. Modems 232a to 232t may be used via a corresponding set of antennas 234 (e.g., T Each antenna (shown as antennas 234a to 234t) is used to transmit a set of downlink signals (e.g., ...). T (One downlink signal).

[0050] At UE 120, a set of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from network node 110 and / or other network nodes 110 and can transmit a set of received signals (e.g., R The received signals are provided to a group of modems 254 (e.g., R Each modem 254 (shown as modems 254a to 254r) may receive a signal. For example, each received signal may be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may use a demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from modem 254, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. Receiver processor 258 may process (e.g., demodulate and decode) the detected symbols, provide the decoded data for UE 120 to data sink 260, and provide the decoded control information and system information to controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine parameters such as the Reference Signal Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Signal Received Quality (RSRQ), and / or CQI. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0051] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, for example, in a core network. Network controller 130 may communicate with network node 110 via communication unit 294.

[0052] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements and / or one or more antenna arrays, etc., or may be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements and / or coupled to one or more transmitting and / or receiving components (such as...). Figure 2 One or more antenna elements (one or more components in a )

[0053] On the uplink, at UE 120, the transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reporting including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 can generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 can be pre-decoded by the TX MIMO processor 266 where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to network node 110. In some examples, the modem 254 of UE 120 may include a modulator and demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to execute this document (e.g., reference). Figures 5 to 13 ( ) any aspect of the methods described in the method.

[0054] At network node 110, uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232 (shown as DEMOD)), detected by MIMO detector 236, and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communication. In some examples, modem 232 of network node 110 may include modulator and demodulator. In some examples, network node 110 includes transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute this document (e.g., reference). Figures 5 to 13 ( ) any aspect of the methods described in the method.

[0055] The controller / processor 240 of network node 110, the controller / processor 280 of UE 120 and / or Figure 2 Any other component may perform one or more techniques associated with frequency-domain OCC-based PUSCH multiplexing, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component that can execute or direct, for example Figure 10 Process 1000 Figure 11 The operation of process 1100 and / or other processes as described herein. Memory 242 and memory 282 may store data and program code for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions may cause the one or more processors, UE 120 and / or network node 110 to perform or direct, for example, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, transformation and / or interpretation). Figure 10 Process 1000 Figure 11The operation of process 1100 and / or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions and / or interpret instructions, etc.

[0056] In some aspects, the UE (e.g., UE 120) includes components for receiving a configuration associated with an OCC sequence, wherein the OCC sequence is associated with frequency-domain OCC-based PUSCH multiplexing (e.g., using antenna 252, modem 254, MIMO detector 256, receive processor 258, controller / processor 280, memory 282, etc.); and / or components for transmitting PUSCH transmissions at least in part based on the configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission (e.g., using controller / processor 280, transmit processor 264, TX MIMO processor 266, modem 254, antenna 252, memory 282, etc.). Components for the UE to perform the operations described herein may include, for example, one or more of the following: communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0057] In some aspects, a network node (e.g., network node 110) includes components for transmitting a configuration associated with an OCC sequence, wherein the OCC sequence is associated with frequency-domain OCC-based PUSCH multiplexing (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, memory 242, etc.); and / or components for receiving PUSCH transmissions at least in part based on this configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission (e.g., using antenna 234, modem 232, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, etc.). Components for the network node to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0058] In some respects, a single processor can perform all the functions described as being performed by that one or more processors. In other respects, the one or more processors can jointly perform a set of functions. For example, a first group(s) of the one or more processors can perform a first function described as being performed by that one or more processors, and a second group(s) of the one or more processors can perform a second function described as being performed by that one or more processors. The first group and the second group of processors can be the same group of processors or can be different groups of processors. The reference to "one or more processors" should be understood as referring to a combination of functions. Figure 2 Any one or more processors described. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as those in conjunction with... Figure 2 The memory described. For example, a function described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0059] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0060] As indicated above, Figure 2 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 2 The examples described are different.

[0061] Communication systems (such as 5G NR systems) can be deployed in various ways with a variety of components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in either a converged or decomposed architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), TRP, or cell, etc.) or one or more units (or components) performing base station functionality can be implemented as a converged base station (also known as a standalone base station or monolithic base station) or a decomposed base station. A "network entity" or "network node" can refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or combinations thereof).

[0062] Aggregated base stations (e.g., aggregated network nodes) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or cell). Decomposed base stations (e.g., decomposed network nodes) can be configured to utilize a protocol stack that is physically or logically distributed across two or more cells (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual cell, such as a Virtual Central Unit (VCU), a Virtual Distributed Unit (VDU), or a Virtual Radio Unit (VRU), etc.

[0063] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in IAB networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)) to facilitate the scaling of communication systems by separating base station functionality into one or more units that can be deployed independently. Decomposed base stations can include functionality implemented across two or more units at various physical locations, as well as functionality virtually implemented for at least one unit, which enables flexibility in network design. Each unit of a decomposed base station can be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0064] Figure 3 This is an illustration of an example disaggregated base station architecture 300 according to this disclosure. The disaggregated base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more disaggregated control units (such as near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a Service Management and Orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RUs 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UEs 120 via a corresponding radio frequency (RF) access link. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0065] Each unit in the cells (including CU 310, DU 330, RU 340), as well as the near-RT RIC 325, non-RT RIC 315, and SMO frame 305, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit in the cell, or an associated processor or controller providing instructions to one or more communication interfaces of the corresponding unit, may be configured to communicate with one or more units in other cells via transmission media. In some examples, each unit in the cell may include a wired interface and a wireless interface configured to receive signals via a wired transmission media or transmit signals to one or more units in other cells, and the wireless interface may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals via a wireless transmission media or transmit signals to one or more units in other cells, or both.

[0066] In some aspects, the CU 310 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, or Service Data Adaptation Protocol (SDAP) functions, etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 310. The CU 310 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP) functions), control plane functions (e.g., Central Unit-Control Plane (CU-CP) functions), or combinations thereof. In some implementations, the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be implemented to communicate with the DU 330 for network control and signaling purposes, as needed.

[0067] Each DU 330 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 340s. In some aspects, the DU 330 may, at least in part, host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers, depending on functional splits (such as those defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as those implemented by one or more modules for Fast Fourier Transform (FFT), Inverse FFT (iFFT), Digital Beamforming, or Physical Random Access Channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0068] Each RU 340 can implement lower-layer functionality. In some deployments, an RU 340 controlled by a DU 330 can correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, based on function splitting (e.g., function splitting defined by 3GPP) (such as lower-layer function splitting). In such architectures, each RU 340 can be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration allows each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0069] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 305 can be configured to interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 can communicate with the hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0070] The non-RT RIC 315 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325, such as via an A1 interface. The near-RT RIC 325 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as via an E2 interface, connecting one or more CU 310s, one or more DU 330s, or both, and O-eNBs to the near-RT RIC 325.

[0071] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the creation of the SMO framework 305 (such as reconfiguration via the O1 interface) or via RAN management policies (such as A1 interface policies).

[0072] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0073] In NTN, uplink SNR can be relatively low. For example, at an orbital altitude of 600 km, the SNR (in dB) can vary from approximately -13.2 dB to approximately -3.1 dB as the elevation angle changes from 10 degrees to 90 degrees. At an orbital altitude of 800 km, the SNR can vary from approximately -15.0 dB to approximately -5.6 dB as the elevation angle changes from 10 degrees to 90 degrees. As a more specific example, at an elevation angle of 30 degrees, the SNR can be approximately -8.2 dB at an orbital altitude of 600 km, and approximately -10.4 dB at an orbital altitude of 800 km.

[0074] In NTN, to compensate for relatively low coverage, PUSCH may need to be repeated multiple times (e.g., repeated over 20 time slots). The decoding rate can be less than 1 / 5, which can be the minimum decoding rate for low-density parity-check (LDPC) codes without repetition. For example, for a 184-bit voice frame per 20 ms, a resource block (RB) frequency domain resource allocation (FDRA), 12 OFDM symbols per ms, and a transport block on multiple time slots (TBoMS), the decoding rate can be 0.035, and the output bits of the channel encoder can be associated with six repetitions (e.g., identical copies) of the entire cyclic buffer. These repetitions can be used to multiplex multiple UEs with the OCC, which increases the overall system capacity because the same amount of resources can support a larger number of UEs.

[0075] Figure 4 This is an example 400 illustrating frequency domain OCC multiplexing of two UEs according to this disclosure.

[0076] like Figure 4 As shown, for frequency domain OCC multiplexing of two UEs, the first UE (e.g., UE1 Tx) can pass through the first channel ( H1 The second UE (e.g., UE2 Tx) can transmit to the network node (e.g., gNB Rx) via the second channel ( H2 The first UE sends a symbol to the network node, and the network node can receive it from both the first UE and the second UE. The first UE can send symbols to the network node with a repetition factor of 2. For example, the first UE can send a first symbol (s1) twice, a second symbol (s2) twice, and so on, where, due to the application of positive OCC, both the first and second symbols can be positive symbols (e.g., +s1, +s1, +s2, +s2, and so on). The second UE can also send symbols with positive and negative signs to the network node with a repetition factor of 2. For example, the second UE can send a first symbol (t1) twice, a second symbol (t2) twice, and so on, where, due to the application of both positive and negative OCC, the first and second symbols can be associated with both positive and negative symbols (e.g., +t1, -t1, +t2, -t2, and so on).

[0077] A network node can receive +s1H1 and +t1H2 at the first resource element (or first tone). A network node can receive +s1H1 and -t1H2 at the second resource element (or second tone), and so on. The network node can add symbols for the first and second resource elements. The network node can perform (s1H1+t1H2)+(s1H1-t1H2), which yields 2s1H1. The network node can obtain 2s1H1 from the first UE (e.g., 2 multiplied by s1 multiplied by H1). (e.g., via DMRS signal) Using the estimation of H1, the network node can estimate s1. The network node can also subtract symbols for the first and second resource elements. The network node can perform s1H1+t1H2-(s1H1-t1H2), which yields 2t1H2. The network node can obtain 2t1H2 from the second UE (e.g., 2 multiplied by t1). (For example, via DMRS signals) Using the estimation of H2, network nodes can estimate t1.

[0078] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0079] In an analog configuration involving two UEs, an OCC length of 2, an NTN tapped delay line (TDL) rural channel with a 30-degree elevation angle, a transport block size (TBS) of 184, 20 repetitions, one RB FDRA, quadrature phase shift keying (QPSK), 5 Hz Doppler spread, and DMRS bundled, frequency domain OCC multiplexing can double the number of supported UEs without sacrificing the performance of each individual UE.

[0080] In NTN, uplink SNR may be relatively low, and to compensate for the relatively low coverage, PUSCH transmissions by the UE may need to be repeated multiple times. These repetitions can be used to multiplex multiple UEs with an OCC, which can increase overall system capacity. By multiplexing multiple UEs with an OCC, the same number of resources can support a larger number of UEs. However, a UE may not be configured with an OCC sequence to support PUSCH multiplexing with an OCC. As a result, the UE may not be able to apply an OCC that allows PUSCH multiplexing, which may prevent the use of these repetitions to support multiplexing of multiple UEs, and therefore may prevent an increase in overall system capacity.

[0081] In various aspects of the techniques and apparatus described herein, a UE can receive a configuration associated with an OCC sequence for supporting PUSCH multiplexing from a network node associated with an NTN. This OCC sequence can be associated with frequency-domain OCC-based PUSCH multiplexing. This OCC sequence can be associated with resource mapping to frequency-domain subcarriers. Frequency-domain OCC-based PUSCH multiplexing can involve multiple PUSCH transmissions from multiple UEs respectively. This configuration can be associated with CP-OFDM waveforms or DFT-s-OFDM waveforms. The UE can receive this configuration from the network node via a MAC control element (MAC-CE), RRC signaling, or downlink control information (DCI). This configuration can instruct the UE which OCC sequence the UE should apply. The UE can transmit PUSCH to the network node at least in part based on this configuration. The OCC sequence can be applied to one or more symbols associated with the PUSCH transmission. Frequency-domain OCC-based PUSCH multiplexing can compensate for relatively low NTN coverage. In some respects, at least in part based on the configuration associated with the OCC sequence, the UE can be configured to support PUSCH multiplexing with the OCC. The UE may be able to apply the OCC that allows PUSCH multiplexing, which may allow multiplexing of multiple UEs to be supported by repetition, and thus increase the overall system capacity.

[0082] Figure 5 This is a diagram illustrating example 500 associated with frequency-domain OCC-based PUSCH multiplexing according to this disclosure. Figure 5As shown, Example 500 includes communication between a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the UE and the network node may be included in a wireless network (such as wireless network 100).

[0083] As shown by reference numeral 502 in the attached figure, the UE can receive a configuration associated with an OCC sequence from a network node. The UE can receive this configuration from the network node via MAC-CE, RRC signaling, or DCI. This configuration can be associated with a CP-OFDM waveform or a DFT-s-OFDM waveform. This configuration can indicate a randomization mode for selecting the OCC sequence over a period of time. This configuration can be associated with an OCC configuration for DMRS, and the same OCC multiplexing mode or the same OCC sequence associated with that DMRS can be applied to PUSCH transmissions performed by the UE. This configuration can be associated with PUSCH multiplexing based on frequency-domain OCC. The OCC sequence can be a Hadamard sequence. The OCC sequence can be associated with a vector of a Discrete Fourier Transform (DFT) matrix. The OCC sequence can be a Zadoff-Chu sequence. The OCC sequence can be a computer-generated sequence or a cyclically shifted version of that computer-generated sequence.

[0084] In some respects, frequency-domain OCC-based PUSCH multiplexing can compensate for low NTN coverage. The UE can determine which OCC sequences will be applied to PUSCH transmission. The selection of OCC sequences for frequency-domain OCC-based PUSCH multiplexing can be based at least in part on this configuration from the network node. In some respects, the OCC sequence can be selected from a Hadamard sequence. For example, for a spread factor of 2, the Hadamard sequence can be [1 1], [1 -1], or for a spread sequence of 4, the Hadamard sequence can be [1 1 1 1], [1 1-1 -1], [1 -1 1 -1], [-1 1 1 -1]. In some respects, the OCC sequence can be selected from a vector of the DFT matrix. For example, for a spread factor of 3, the vector of the DFT matrix can be [1 1 1], [1... ... ]、[1 Alternatively, for an expansion factor of 4, the vector of the DFT matrix can be [1 1 1 1], [1 -j -1 j], [1 -1 1 -1], [1 j -1 -j]. In some aspects, the OCC sequence may be selected from a Zadeov-Zhu sequence, which may be used for odd lengths. The Zadeov-Zhu sequence may include Zadeov-Zhu sequences with different cyclic shifts, Zadeov-Zhu sequences with different roots, cyclically expanded Zadeov-Zhu sequences, and / or truncated Zadeov-Zhu sequences. In some aspects, the OCC sequence may be selected from a computer-generated sequence (e.g., sequences of length 6 and 12) and / or a cyclically shifted version of the computer-generated sequence.

[0085] In some respects, this configuration of the OCC sequence can be applied to both CP-OFDM and DFT-s-OFDM. In other respects, this configuration of the OCC sequence can follow the new configuration of OCC for PUSCH. The OCC sequence can be listed in a table in specifications such as 3GPP Technical Specification (TS) 38.211. The network node can send an indication to the UE indicating which OCC sequence the UE should use for frequency-domain OCC-based PUSCH multiplexing. This indication can include a row index of the table to indicate the OCC sequence. The network node can send this indication via MAC-CE, RRC signaling, or DCI. The network node can indicate a randomization mode when selecting the OCC sequence over time. For example, the index of the OCC sequence in a slot (or OFDM symbol) can change according to the randomization mode over time. The randomization mode can define a modular index offset relative to a first index (for a slot or OFDM symbol). In some respects, this configuration of the OCC sequence can follow the OCC configuration for DMRS. The same OCC multiplexing mode (e.g., frequency division multiplexing (FDM) and OCC sequence) or the same OCC sequence can be applied to frequency-domain OCC-based PUSCH multiplexing. Furthermore, reserved values ​​in the antenna port field of the DCI (which can be associated with DMRS code division multiplexing (CDM) groups) can be used to indicate new antenna ports that identify new DMRS modes.

[0086] In some aspects, resource mapping for the OCC sequence can be tone-based resource mapping. The new sequence can be generated for a given symbol sequence, where each symbol can be repeated consecutively a certain number of times, which may correspond to the OCC length, and the new sequence can be mapped to time-frequency resources. In some aspects, resource mapping for the OCC sequence can be block-based resource mapping. The new sequence can be generated for a given symbol sequence, where symbol blocks (e.g., symbol groups, such as symbols s0, s1, s2, s3, s4, and s5) can be repeated consecutively a first number of times, which may be at least partially based on a second number associated with the number of subcarriers in the frequency domain resource allocation and a third number associated with the OCC length, and the new sequence can be mapped to time-frequency resources.

[0087] In some aspects, resource mappings for OCC sequences utilizing CP-OFDM can be defined. In some aspects, resource mappings for OCC sequences utilizing CP-OFDM can be tone-based resource mappings (e.g., such as...). Figure 6 As shown, this tone-based resource mapping provides improved orthogonality. The resource mapping can be to frequency domain subcarriers. For a given symbol sequence, a new sequence can be generated, where each symbol can be repeated consecutively. L Second, and among them L This is the length of the OCC. The new sequence can be mapped to a time-frequency grid.

[0088] For example, a first UE can be configured to transmit symbols s0, s1, s2, s3, s4, and s5, and the OCC length can be 2. A new sequence can be generated, in which each of the symbols s0, s1, s2, s3, s4, and s5 can be repeated twice. Similarly, a second UE can be configured to transmit symbols t0, t1, t2, t3, t4, and t5, and the OCC length can be 2. A new sequence can be generated, in which each of the symbols t0, t1, t2, t3, t4, and t5 can be repeated twice.

[0089] In some respects, resource mapping for OCC sequences utilizing CP-OFDM can be chunk-based resource mapping (e.g., ... Figure 7 (As shown). Resource mapping can be to frequency domain subcarriers. For a given symbol sequence, a new sequence can be generated, where symbol blocks can be repeated consecutively. M Second-rate, M = floor( N / L ), N L is the number of subcarriers in the frequency domain resource allocation, and L is the length of the OCC. The new sequence can be mapped to a time-frequency grid.

[0090] For example, a first UE can be configured to transmit symbols s0, s1, s2, s3, s4, and s5, and the OCC length can be 2. A new sequence can be generated in which symbol blocks (e.g., symbols s0, s1, s2, s3, s4, and s5) can be repeated consecutively twice. Similarly, a second UE can be configured to transmit symbols t0, t1, t2, t3, t4, and t5, and the OCC length can be 2. A new sequence can be generated in which symbol blocks (e.g., symbols t0, t1, t2, t3, t4, and t5) can be repeated consecutively twice.

[0091] For example, in a simulation involving two UEs, an OCC length of 2 (e.g., the number of tones equals the OCC length), and an RB FDRA, tone-based resource mapping and block-based resource mapping can produce relatively similar peak-to-average power ratios (PAPRs). The simulation can indicate the PAPR associated with the block-based OCC for the first UE, the PAPR associated with the block-based OCC for the second UE, the PAPR associated with the tone-based OCC for the first UE, and the PAPR associated with the tone-based OCC for the second UE.

[0092] In some aspects, resource mapping for OCC sequences can be based at least in part on block-based expansion, where the new sequence can be generated for a given symbol sequence, wherein symbol blocks can be repeated consecutively a first number of times, the first number being at least in part based on a second number associated with the size of the DFT of the DFT expander (which is sometimes also referred to as a transform pre-decoder) and a third number associated with the OCC length, and the new sequence can be input into the DFT expander. In some aspects, resource mapping for OCC sequences can be based at least in part on sample-based expansion, where the new sequence can be generated for a given symbol sequence, wherein each symbol can be repeated consecutively a certain number of times, the number corresponding to the OCC length, and the new sequence can be input into a discrete DFT expander.

[0093] In some aspects, resource mappings for OCC sequences utilizing DFT-s-OFDM can be defined. In some aspects, resource mappings for OCC sequences utilizing DFT-s-OFDM can be based at least in part on chunk-based extensions (e.g., such as...). Figure 8 (As shown). Resource mapping can be to frequency domain subcarriers. For a given symbol sequence, a new sequence can be generated, where symbol blocks can be repeated consecutively. M Second-rate, M = floor( N / L ), N It is the size of the DFT of the DFT extension block. L This is the length of the OCC. The new sequence can be fed into the DFT expansion block.

[0094] For example, a first UE can be configured to transmit symbols x0, x1, x2, x3, x4, and x5. A new sequence can be generated in which symbol blocks (e.g., symbols x0, x1, x2, x3, x4, and x5) can be repeated consecutively twice. Similarly, a second UE can be configured to transmit symbols z0, z1, z2, z3, z4, and z5. A new sequence can be generated in which symbol blocks (e.g., symbols z0, z1, z2, z3, z4, and z5) can be repeated consecutively twice. Furthermore, for both the first and second UEs, OCC can be applied before the DFT extension block. For example, OCC extension can occur before DFT extension.

[0095] In some respects, resource mapping for OCC sequences utilizing DFT-s-OFDM can be at least partially based on sample-based extensions (e.g., such as...). Figure 9 (As shown). For a given sequence of symbols, a new sequence can be generated, where each symbol can be repeated consecutively. L Next, and L This is the length of the OCC. The new sequence can be fed into the DFT extension block. Resource mapping can be to frequency domain subcarriers.

[0096] For example, a first UE can be configured to transmit symbols x0, x1, x2, x3, x4, and x5. A new sequence can be generated in which each of the symbols x0, x1, x2, x3, x4, and x5 can be repeated consecutively twice. Similarly, a second UE can be configured to transmit symbols z0, z1, z2, z3, z4, and z5. A new sequence can be generated in which each of the symbols z0, z1, z2, z3, z4, and z5 can be repeated consecutively twice.

[0097] For example, in a simulation involving two UEs, an OCC length of 2, and an RB FDRA, block-based expansion can be associated with more predictable PAPR behavior compared to sample-based expansion. Therefore, block-based expansion can be associated with better performance compared to sample-based expansion. The simulation can indicate the PAPR associated with the block-based OCC for the first UE, the block-based OCC for the second UE, the sample-based OCC for the first UE, and the sample-based OCC for the second UE.

[0098] As shown by reference numeral 504 in the attached figure, the UE can transmit PUSCH transmissions to the network node based at least in part on this configuration. The OCC sequence can be applied to one or more symbols associated with the PUSCH transmission. The UE can use the OCC sequence indicated by the configuration for PUSCH transmissions. This configuration allows PUSCH transmissions to be multiplexed with another PUSCH transmission performed by another UE. For example, the UE can be a first UE, and the PUSCH transmission can be a first PUSCH transmission. Based at least in part on this configuration, a second UE can transmit a second PUSCH transmission to the network node, wherein the first PUSCH transmission and the second PUSCH transmission can be multiplexed PUSCH transmissions. Multiplexed PUSCH transmissions can allow multiple UEs to repeat the Physical Uplink Control Channel (PUCCH) multiplexed with OCC, which can increase system capacity because more UEs can be supported using the same resources.

[0099] In some respects, the UE may send a PRACH transmission to the network node indicating the UE's OCC capabilities. The UE may receive this configuration via message 2 (Msg2) at least in part based on the OCC capabilities. The PUSCH transmission may be an initial message 3 (Msg3) transmission or a retransmission of Msg3.

[0100] In some respects, Msg3 repetition (where Msg3 may be part of a four-step random access channel (RACH) procedure) may not be associated with TBoMS. When the UE is not connected, it may send Msg3, thus the UE may not receive an OCC sequence prior to sending Msg3. Msg3 repetition signaling may be based at least in part on the UE sending an indication request and / or capability via PRACH. Msg3 repetition signaling may be based at least in part on the network node indicating the number of repetitions. The network node may indicate the number of repetitions by reinterpreting the MCS bit in the random access response (RAR) uplink grant or DCI (e.g., DCI 0_0). Regarding the feasibility of frequency-domain OCC for Msg3, in the case of an RB FDRA, the decoding rate is approximately 0.2 (e.g., 56 / 288), and in the case of an OCC length of 2, the decoding rate is approximately 0.4 < 1.

[0101] In some aspects, to support frequency-domain OCC for Msg3 (e.g., the initial Msg3 transmission for Msg3 retransmission), the UE may indicate its OCC capability to the network node via PRACH transmission. The UE may indicate its OCC capability at least in part based on an indication to select a PRACH sequence from a subset of PRACH sequences or a RACH timing from a subset of RACH timings. The network node may configure and signal the PRACH sequence subset or RACH timing subset in the System Information Block (SIB). The network node may indicate the configuration (e.g., the configuration associated with the OCC sequence) to the UE at least in part based on the UE's OCC capability. The UE may indicate the configuration for the initial Msg3 transmission in Msg2 of a four-step RACH procedure, or in the DCI (e.g., DCI 0_0). This configuration may be indicated in Msg2 or in the DCI via a new field for the OCC length and assigned OCC. Alternatively, this configuration may be indicated in Msg2 or in the DCI based at least in part on the link between the Msg3 repetition factor (e.g., 1, 2, 3, 4, 7, 8, 12, or 16) and the OCC length. The UE may randomly determine the OCC based at least in part on the link between the Msg3 repetition factor and the OCC length. In other words, the UE may randomly determine the OCC based at least in part on the OCC length, wherein the OCC length is at least in part based on the Msg3 repetition factor.

[0102] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0103] Figure 6 This is a diagram illustrating example 600 associated with frequency domain OCC-based PUSCH multiplexing according to this disclosure.

[0104] like Figure 6As shown, in tone-based resource mapping (e.g., OCC with CP-OFDM), a first UE can be configured to transmit symbols s0, s1, s2, s3, s4, and s5, and the OCC length can be 2. A new sequence can be generated, where each of the symbols s0, s1, s2, s3, s4, and s5 can be repeated twice. For the first UE, a positive OCC can be applied to the two repetitions of a given symbol (e.g., +s0, +s0, +s1, +s1, and so on). A second UE can be configured to transmit symbols t0, t1, t2, t3, t4, and t5, and the OCC length can be 2. A new sequence can be generated, where each of the symbols t0, t1, t2, t3, t4, and t5 can be repeated twice. For the second UE, both positive and negative OCCs can be applied to the repetition of a given symbol (e.g., +t0, -t0, +t1, -t1, and so on).

[0105] As indicated above, Figure 6 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 6 The examples described are different.

[0106] Figure 7 This is a diagram illustrating example 700 associated with frequency domain OCC-based PUSCH multiplexing according to this disclosure.

[0107] like Figure 7 As shown, in block-based resource mapping (e.g., OCC with CP-OFDM), a first UE can be configured to transmit symbols s0, s1, s2, s3, s4, and s5, and the OCC length can be 2. A new sequence can be generated where symbol blocks (e.g., symbols s0, s1, s2, s3, s4, and s5) can be repeated consecutively twice. For the first UE, a positive OCC can be applied to two blocks (e.g., a positive OCC can be applied to the first block of symbols s0 to s5, and a positive OCC can be applied to the second block of symbols s0 to s5). A second UE can be configured to transmit symbols t0, t1, t2, t3, t4, and t5, and the OCC length can be 2. A new sequence can be generated where symbol blocks (e.g., symbols t0, t1, t2, t3, t4, and t5) can be repeated consecutively twice. For the second UE, both positive OCC and negative OCC can be applied to two blocks respectively (for example, positive OCC can be applied to the first block of symbols t0 to t5, and negative OCC can be applied to the second block of symbols t0 to t5).

[0108] As indicated above, Figure 7 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 7 The examples described are different.

[0109] Figure 8This is a diagram illustrating an example 800 associated with frequency domain OCC-based PUSCH multiplexing according to this disclosure.

[0110] like Figure 8 As shown, in a resource mapping associated with block-based expansion (e.g., OCC utilizing DFT-s-OFDM), a first UE can be configured to transmit symbols x0, x1, x2, x3, x4, and x5. A new sequence can be generated where symbol blocks (e.g., symbols x0, x1, x2, x3, x4, and x5) can be repeated consecutively twice. For the first UE, a positive OCC can be applied to two blocks (e.g., a positive OCC can be applied to the first block of symbols x0 to x5, and a positive OCC can be applied to the second block of symbols x0 to x5). For the first UE, the OCC can be applied before the DFT expansion block. For example, the OCC expansion can occur before the DFT expansion and the inverse fast Fourier transform (IFFT). A second UE can be configured to transmit symbols z0, z1, z2, z3, z4, and z5. A new sequence can be generated where symbol blocks (e.g., symbols z0, z1, z2, z3, z4, and z5) can be repeated consecutively twice. For the second UE, both positive and negative OCC can be applied to two separate blocks (e.g., positive OCC can be applied to the first block of symbols z0 to z5, and negative OCC can be applied to the second block of symbols z0 to z5). For the second UE, OCC can be applied before the DFT extension block. For example, OCC extension can occur before DFT extension and IFFT.

[0111] As indicated above, Figure 8 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 8 The examples described are different.

[0112] Figure 9 This is a diagram illustrating example 900 associated with frequency domain OCC-based PUSCH multiplexing according to this disclosure.

[0113] like Figure 9As shown, in the resource mapping associated with sample-based extensions (e.g., OCC utilizing DFT-s-OFDM), a first UE can be configured to transmit symbols x0, x1, x2, x3, x4, and x5. A new sequence can be generated where each of the symbols x0, x1, x2, x3, x4, and x5 can be repeated consecutively twice. For the first UE, a positive OCC can be applied to the two repetitions of a given symbol (e.g., +x0, +x0, +x1, +x1, and so on). A second UE can be configured to transmit symbols z0, z1, z2, z3, z4, and z5. A new sequence can be generated where each of the symbols z0, z1, z2, z3, z4, and z5 can be repeated consecutively twice. For the second UE, both positive and negative OCC can be applied to the repetition of a given symbol (e.g., +z0, -z0, +z1, -z1, and so on).

[0114] As indicated above, Figure 9 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 9 The examples described are different.

[0115] Figure 10 This is a diagram illustrating an example procedure 1000 performed by a UE according to this disclosure. Example procedure 1000 is an example in which a UE (e.g., UE 120) performs operations associated with frequency domain OCC-based PUSCH multiplexing.

[0116] like Figure 10 As shown, in some aspects, process 1000 may include receiving a configuration associated with an OCC sequence, wherein the OCC sequence is associated with PUSCH multiplexing based on frequency domain OCC (block 1010). For example, the UE (e.g., using...) Figure 12 The depicted receiving component 1202 and / or communication manager 1206 can receive configurations associated with an OCC sequence, wherein the OCC sequence is associated with PUSCH multiplexing based on frequency domain OCC, as described above.

[0117] like Figure 10 Further shown, in some aspects, process 1000 may include sending a PUSCH transmission at least in part based on this configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission (box 1020). For example, the UE (e.g., using...) Figure 12 The transmitting component 1204 and / or communication manager 1206 described herein may transmit PUSCH transmissions at least in part based on this configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission, as described above.

[0118] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0119] In the first aspect, the OCC sequence is a Hadamard sequence, the OCC sequence is associated with a vector of a DFT matrix, the OCC sequence is a Zadeh-Zhu sequence, or the OCC sequence is a computer-generated sequence or a cyclically shifted version of the computer-generated sequence.

[0120] In the second aspect, either alone or in combination with the first aspect, the configuration is associated with a CP-OFDM waveform or a DFT-s-OFDM waveform, or the configuration indicates a randomization mode for selecting an OCC sequence over a time period.

[0121] In the third aspect, either alone or in combination with one or more of the first and second aspects, the configuration is associated with the OCC configuration for the DMRS, and the same OCC multiplexing mode or the same OCC sequence associated with the DMRS is applied to the PUSCH transmission.

[0122] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the resource mapping for the OCC sequence is a tone-based resource mapping, the new sequence is generated for a given symbol sequence, wherein each symbol is repeated consecutively a certain number of times, the number corresponding to the OCC length, and the new sequence is mapped to a time-frequency resource.

[0123] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the resource mapping for the OCC sequence is a block-based resource mapping, the new sequence being generated for a given symbol sequence, wherein symbol blocks are repeated consecutively a first number of times, the first number being at least partially based on a second number associated with the number of subcarriers in the frequency domain resource allocation and a third number associated with the OCC length, and the new sequence is mapped to time-frequency resources.

[0124] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the resource mapping for the OCC sequence is based at least in part on chunk-based expansion, the new sequence being generated for a given symbol sequence, wherein symbol chunks are repeated consecutively a first number of times, the first number being based at least in part on a second number associated with the size of the DFT of the DFT expander and a third number associated with the OCC length, and the new sequence is input to the DFT expander.

[0125] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the resource mapping for the OCC sequence is at least partially based on sample-based expansion, the new sequence being generated for a given symbol sequence, wherein each symbol is repeated consecutively a certain number of times, the number corresponding to the OCC length, and the new sequence is input into a DFT expander.

[0126] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, process 1000 includes sending a PRACH transmission indicating the OCC capability of the UE, wherein the configuration is received via Msg2 based at least in part on the OCC capability, and the PRACH transmission is an initial Msg3 transmission or a Msg3 retransmission.

[0127] although Figure 10 An example box for process 1000 is shown, but in some respects, it differs from... Figure 10 Compared to the boxes depicted, process 1000 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in process 1000 may be executed in parallel.

[0128] Figure 11 This is a diagram illustrating an example process 1100 performed by a network node, for example, according to this disclosure. Example process 1100 is an example in which a network node (e.g., network node 110) performs operations associated with frequency domain OCC-based PUSCH multiplexing.

[0129] like Figure 11 As shown, in some aspects, process 1100 may include sending a configuration associated with an OCC sequence, wherein the OCC sequence is associated with PUSCH multiplexing based on frequency domain OCC (box 1110). For example, network nodes (e.g., using...) Figure 13 The transmitting component 1304 and / or the communication manager 1306 depicted herein can transmit configurations associated with an OCC sequence, wherein the OCC sequence is associated with a PUSCH multiplexing based on frequency domain OCC, as described above.

[0130] like Figure 11 Further shown, in some aspects, process 1100 may include receiving PUSCH transmissions at least in part based on this configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission (box 1120). For example, network nodes (e.g., using...) Figure 13 The receiving component 1302 and / or communication manager 1306 described herein may receive PUSCH transmissions at least in part based on this configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission, as described above.

[0131] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0132] In the first aspect, the configuration is associated with a CP-OFDM waveform or a DFT-s-OFDM waveform, or the configuration indicates a randomization mode for selecting an OCC sequence over a time period.

[0133] In the second aspect, either alone or in combination with the first aspect, the configuration is associated with the OCC configuration for the DMRS, and the same OCC multiplexing mode or the same OCC sequence associated with the DMRS is applied to the PUSCH transmission.

[0134] In a third aspect, either alone or in combination with one or more of the first and second aspects, the resource mapping for the OCC sequence is a tone-based resource mapping, wherein the new sequence is generated for a given symbol sequence, wherein each symbol is repeated consecutively a certain number of times, the number corresponding to the OCC length, and the new sequence is mapped to time-frequency resources; or the resource mapping for the OCC sequence is a block-based resource mapping, wherein the new sequence is generated for the given symbol sequence, wherein symbol blocks are repeated consecutively a first number of times, the first number being at least partially based on a second number associated with the number of subcarriers in the frequency domain resource allocation and a third number associated with the OCC length, and the new sequence is mapped to time-frequency resources.

[0135] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the resource mapping for the OCC sequence is at least partially based on chunk-based expansion, the new sequence being generated for a given symbol sequence, wherein symbol chunks are repeated consecutively a first number of times, the first number being at least partially based on a second number associated with the size of the DFT of the DFT expander and a third number associated with the OCC length, and the new sequence is input to the DFT expander; or the resource mapping for the OCC sequence is at least partially based on sample-based expansion, the new sequence being generated for the given symbol sequence, wherein each symbol is repeated consecutively a certain number of times, the number corresponding to the OCC length, and the new sequence is input to the DFT expander.

[0136] In the fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 1100 includes receiving a PRACH transmission indicating the UE's OCC capability, wherein the configuration is received via Msg2 based at least in part on the OCC capability, and the PRACH transmission is an initial Msg3 transmission or a Msg3 retransmission.

[0137] although Figure 11 An example box for process 1100 is shown, but in some respects, it differs from... Figure 11 Compared to the boxes depicted, process 1100 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in process 1100 may be executed in parallel.

[0138] Figure 12 This is a diagram of an example device 1200 for wireless communication according to the present disclosure. Device 1200 may be a UE, or a UE may include device 1200. In some aspects, device 1200 includes a receiving component 1202, a transmitting component 1204, and / or a communication manager 1206 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1206 is combined with... Figure 1 The described communication manager 140. As shown, device 1200 can communicate with another device 1208 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1202 and transmitting component 1204.

[0139] In some respects, device 1200 can be configured to perform the functions described herein. Figures 5 to 9 One or more operations described herein. Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Figure 10 The process 1000. In some aspects, the apparatus 1200 and / or Figure 12 One or more components shown may include combinations Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 12 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more of the components in a set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0140] Receiver 1202 may receive communications from device 1208, such as reference signals, control information, data communications, or combinations thereof. Receiver 1202 may provide the received communications to one or more other components of device 1200. In some aspects, receiver 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of device 1200. In some aspects, receiver 1202 may include combinations of... Figure 2 The described UE includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0141] Transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1208. In some aspects, one or more other components of device 1200 may generate communications and provide the generated communications to transmitting component 1204 for transmission to device 1208. In some aspects, transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1208. In some aspects, transmitting component 1204 may include combinations of... Figure 2 The described UE includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, transmit component 1204 may be co-located with receive component 1202 in a transceiver.

[0142] The communication manager 1206 may support the operation of the receiving component 1202 and / or the transmitting component 1204. For example, the communication manager 1206 may receive information associated with configuring the reception of communications by the receiving component 1202 and / or the transmission of communications by the transmitting component 1204. Additionally or alternatively, the communication manager 1206 may generate control information and / or provide control information to the receiving component 1202 and / or the transmitting component 1204 to control the reception and / or transmission of communications.

[0143] The receiving component 1202 can receive a configuration associated with an OCC sequence, wherein the OCC sequence is associated with frequency-domain OCC-based PUSCH multiplexing. The transmitting component 1204 can transmit a PUSCH transmission at least in part based on this configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission. The transmitting component 1204 can transmit a PRACH transmission indicating the UE's OCC capability, wherein the configuration is received via Msg2 at least in part based on the OCC capability, and the PUSCH transmission is an initial Msg3 transmission or a Msg3 retransmission.

[0144] Figure 12 The number and arrangement of components shown are provided as an example. In reality, with... Figure 12 Compared to the components shown, there may be additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 12 The two or more components shown can be implemented within a single component, or Figure 12 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 12 The set (one or more) components shown are executable and described as being composed of Figure 12 The other set of components shown performs one or more functions.

[0145] Figure 13 This is a diagram of an example device 1300 for wireless communication according to the present disclosure. Device 1300 may be a network node, or a network node may include device 1300. In some aspects, device 1300 includes a receiving component 1302, a transmitting component 1304, and / or a communication manager 1306 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1306 is combined with... Figure 1 The described communication manager 150. As shown, device 1300 can communicate with another device 1308 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1302 and transmitting component 1304.

[0146] In some respects, device 1300 can be configured to perform the functions described herein. Figures 5 to 9 One or more operations described herein. Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as Figure 11 The process 1100. In some respects, Figure 13 The illustrated device 1300 and / or one or more components may include a combination Figure 2 One or more components of the described network node. Additionally or alternatively, Figure 13 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more of the components in a set of components may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0147] Receiver 1302 may receive communications from device 1308, such as reference signals, control information, data communications, or combinations thereof. Receiver 1302 may provide the received communications to one or more other components of device 1300. In some aspects, receiver 1302 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of device 1300. In some aspects, receiver 1302 may include combinations of... Figure 2 The described network node includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof. In some aspects, receiver component 1302 and / or transmitter component 1304 may include or be included in a network interface. The network interface may be configured to acquire and / or output signals for device 1300 via one or more communication links, such as backhaul links, midhaul links, and / or fronthaul links.

[0148] Transmitting component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1308. In some aspects, one or more other components of device 1300 may generate communications and provide the generated communications to transmitting component 1304 for transmission to device 1308. In some aspects, transmitting component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1308. In some aspects, transmitting component 1304 may include combinations of... Figure 2 The described network node includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 1304 may be co-located with the receive component 1302 in a transceiver.

[0149] The communication manager 1306 may support the operation of the receiving component 1302 and / or the transmitting component 1304. For example, the communication manager 1306 may receive information associated with configuring the reception of communications by the receiving component 1302 and / or the transmission of communications by the transmitting component 1304. Additionally or alternatively, the communication manager 1306 may generate control information and / or provide control information to the receiving component 1302 and / or the transmitting component 1304 to control the reception and / or transmission of communications.

[0150] Transmitting component 1304 can transmit a configuration associated with an OCC sequence, wherein the OCC sequence is associated with frequency-domain OCC-based PUSCH multiplexing. Receiving component 1302 can receive PUSCH transmissions at least in part based on this configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission. Receiving component 1302 can receive PRACH transmissions indicating the UE's OCC capability, wherein the configuration is received via Msg2 at least in part based on the OCC capability, and the PUSCH transmission is an initial Msg3 transmission or a Msg3 retransmission.

[0151] Figure 13 The number and arrangement of components shown are provided as an example. In reality, with... Figure 13 Compared to the components shown, there may be additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 13 The two or more components shown can be implemented within a single component, or Figure 13 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 13 The set (one or more) components shown are executable and described as being composed of Figure 13 The other set of components shown performs one or more functions.

[0152] The following provides an overview of some aspects of this disclosure.

[0153] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a configuration associated with an orthogonal coverage code (OCC) sequence, wherein the OCC sequence is associated with frequency domain OCC-based physical uplink shared channel (PUSCH) multiplexing; and transmitting a PUSCH transmission at least in part based on the configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission.

[0154] Aspect 2: According to the method of aspect 1, wherein: the OCC sequence is a Hadamard sequence; the OCC sequence is associated with a vector of a discrete Fourier transform (DFT) matrix; the OCC sequence is a Zadeoff-Zhu sequence; or the OCC sequence is a computer-generated sequence or a cyclically shifted version of the computer-generated sequence.

[0155] Aspect 3: The method according to any one of Aspects 1 to 2, wherein: the configuration is associated with a Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) waveform or a Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveform; or the configuration indicates a randomization mode for selecting an OCC sequence over a time period.

[0156] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the configuration is associated with an OCC configuration for demodulation reference signal (DMRS), wherein the same OCC multiplexing mode or the same OCC sequence associated with the DMRS is applied to the PUSCH transmission.

[0157] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the resource mapping for the OCC sequence is a tone-based resource mapping, the new sequence is generated for a given symbol sequence, wherein each symbol is repeated continuously a certain number of times, the number corresponding to the OCC length, and the new sequence is mapped to a time-frequency resource.

[0158] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the resource mapping for the OCC sequence is based on block-based resource mapping, the new sequence is generated for a given symbol sequence, wherein the symbol blocks are repeated continuously a first number of times, the first number being at least in part based on a second number associated with the number of subcarriers in the frequency domain resource assignment and a third number associated with the OCC length, and the new sequence is mapped to time-frequency resources.

[0159] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the resource mapping for the OCC sequence is based at least in part on a chunk-based expansion, the new sequence being generated for a given symbol sequence, wherein symbol chunks are repeated consecutively a first number of times, the first number being based at least in part on a second number associated with the size of the Discrete Fourier Transform (DFT) expander and a third number associated with the OCC length, and the new sequence is input to the DFT expander.

[0160] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the resource mapping for the OCC sequence is at least partially based on a sample-based extension, the new sequence being generated for a given symbol sequence, wherein each symbol is repeated consecutively a certain number of times, the number corresponding to the OCC length, and the new sequence is input to a Discrete Fourier Transform (DFT) extension.

[0161] Aspect 9: The method according to any one of Aspects 1 to 8, the method further comprising: transmitting a Physical Random Access Channel (PRACH) transmission indicating the OCC capability of the UE, wherein the configuration is received via message 2 (Msg2) based at least in part on the OCC capability, and the PUSCH transmission is an initial message 3 (Msg3) transmission or a retransmission of Msg3.

[0162] Aspect 10: A method of wireless communication performed by a network node, the method comprising: transmitting a configuration associated with an orthogonal cover code (OCC) sequence, wherein the OCC sequence is associated with frequency-domain OCC-based physical uplink shared channel (PUSCH) multiplexing; and receiving PUSCH transmissions at least in part based on the configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmissions.

[0163] Aspect 11: The method according to aspect 10, wherein: the configuration is associated with a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform or a discrete Fourier transform extended orthogonal frequency division multiplexing (DFT-s-OFDM) waveform; or the configuration indicates a randomization mode for selecting an OCC sequence over a time period.

[0164] Aspect 12: The method according to any one of Aspects 10 to 11, wherein the configuration is associated with an OCC configuration for demodulation reference signal (DMRS), wherein the same OCC multiplexing mode or the same OCC sequence associated with the DMRS is applied to the PUSCH transmission.

[0165] Aspect 13: The method according to any one of Aspects 10 to 12, wherein: the resource mapping for the OCC sequence is a tone-based resource mapping, the new sequence is generated for a given symbol sequence, wherein each symbol is repeated consecutively a certain number of times, the number corresponding to the OCC length, and the new sequence is mapped to time-frequency resources; or the resource mapping for the OCC sequence is a block-based resource mapping, the new sequence is generated for the given symbol sequence, wherein symbol blocks are repeated consecutively a first number of times, the first number being at least partially based on a second number associated with the number of subcarriers in the frequency domain resource allocation and a third number associated with the OCC length, and the new sequence is mapped to time-frequency resources.

[0166] Aspect 14: The method according to any one of Aspects 10 to 13, wherein: the resource mapping for the OCC sequence is at least partially based on a block-based expansion, the new sequence being generated for a given symbol sequence, wherein symbol blocks are repeated consecutively a first number of times, the first number being at least partially based on a second number associated with the size of the Discrete Fourier Transform (DFT) expander and a third number associated with the OCC length, and the new sequence is input to the DFT expander; or the resource mapping for the OCC sequence is at least partially based on a sample-based expansion, the new sequence being generated for the given symbol sequence, wherein each symbol is repeated consecutively a certain number of times, the number corresponding to the OCC length, and the new sequence is input to the DFT expander.

[0167] Aspect 15: The method according to any one of Aspects 10 to 14, the method further comprising: receiving a Physical Random Access Channel (PRACH) transmission indicating the OCC capability of a User Equipment (UE), wherein the configuration is received via message 2 (Msg2) based at least in part on the OCC capability, and the PUSCH transmission is an initial message 3 (Msg3) transmission or a retransmission of Msg3.

[0168] Aspect 16: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 1 to 9.

[0169] Aspect 17: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors being configured to perform the method according to one or more of aspects 1 to 9.

[0170] Aspect 18: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 9.

[0171] Aspect 19: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to one or more of aspects 1 to 9.

[0172] Aspect 20: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 9.

[0173] Aspect 21: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 10 to 15.

[0174] Aspect 22: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors being configured to perform the method according to one or more of aspects 10 to 15.

[0175] Aspect 23: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 10 to 15.

[0176] Aspect 24: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to one or more of aspects 10 to 15.

[0177] Aspect 25: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 10 to 15.

[0178] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit aspects to the precise form disclosed. Modifications and variations can be made based on the foregoing disclosure, or from various aspects of practice.

[0179] As used herein, the term "component" is intended to be interpreted broadly as hardware and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, "software" should be interpreted broadly as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, etc. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent to those skilled in the art that the systems and / or methods described herein can be implemented in various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limiting in any way. Therefore, no specific software code is referenced in this document to describe the operation and behavior of the systems and / or methods, as those skilled in the art will understand that the software and hardware can be designed, at least in part, based on the descriptions herein, to implement the systems and / or methods.

[0180] Hardware and data processing means for implementing the various exemplary logic, logic blocks, modules, and circuits described herein can be implemented or executed using general-purpose single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some aspects, specific processes and methods can be performed by circuitry dedicated to a given function.

[0181] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0182] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically set forth in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with each other claim in the set of claims. As used herein, the phrase “at least one of” in the list of items refers to any combination of these items, including a single member. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination having multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0183] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are used interchangeably with “one or more.” Furthermore, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Furthermore, as used herein, the terms “have,” “possess,” “have,” etc., are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used in a series and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., in combination with “any” or “only one”).

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being individually or collectively configured to: Receive configuration associated with an orthogonal coverage code (OCC) sequence, wherein the OCC sequence is associated with frequency-domain OCC-based physical uplink shared channel (PUSCH) multiplexing; and The PUSCH transmission is sent at least in part based on the configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission.

2. The apparatus according to claim 1, wherein: The OCC sequence is a Hadama sequence; The OCC sequence is associated with a vector of the Discrete Fourier Transform (DFT) matrix; The OCC sequence is a Zadeh-Zhu sequence; or The OCC sequence is a computer-generated sequence or a cyclically shifted version of the computer-generated sequence.

3. The apparatus according to claim 1, wherein: The configuration is associated with a Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) waveform or a Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveform; or The configuration instruction is used to select the randomization mode of the OCC sequence within a time period.

4. The apparatus of claim 1, wherein the configuration is associated with an OCC configuration for demodulation reference signal (DMRS), and the same OCC multiplexing mode or the same OCC sequence associated with the DMRS is applied to the PUSCH transmission.

5. The apparatus of claim 1, wherein the resource mapping for the OCC sequence is a tone-based resource mapping, the new sequence is generated for a given symbol sequence, wherein each symbol is repeated consecutively a certain number of times, the number corresponding to the OCC length, and the new sequence is mapped to a time-frequency resource.

6. The apparatus of claim 1, wherein the resource mapping for the OCC sequence is a block-based resource mapping, the new sequence is generated for a given symbol sequence, wherein the symbol block is repeated continuously a first number of times, the first number being at least in part based on a second number associated with the number of subcarriers in the frequency domain resource allocation and a third number associated with the OCC length, and the new sequence is mapped to time-frequency resources.

7. The apparatus of claim 1, wherein the resource mapping for the OCC sequence is based at least in part on a chunk-based expansion, the new sequence being generated for a given symbol sequence, wherein symbol chunks are repeated consecutively a first number of times, the first number being based at least in part on a second number associated with the size of the Discrete Fourier Transform (DFT) expander and a third number associated with the OCC length, and the new sequence is input to the DFT expander.

8. The apparatus of claim 1, wherein the resource mapping for the OCC sequence is at least partially based on sample-based expansion, the new sequence being generated for a given symbol sequence, wherein each symbol is repeated consecutively a certain number of times, the number corresponding to the OCC length, and the new sequence is input to a Discrete Fourier Transform (DFT) expander.

9. The apparatus of claim 1, wherein the one or more processors are individually or jointly configured to: A Physical Random Access Channel (PRACH) transmission indicating the UE's OCC capability is sent, wherein the configuration is received via message 2 (Msg2) based at least in part on the OCC capability, and the PUSCH transmission is either an initial message 3 (Msg3) transmission or a retransmission of Msg3.

10. An apparatus for wireless communication at a network node, the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being individually or collectively configured to: Sending configurations associated with orthogonal coverage code (OCC) sequences, wherein the OCC sequences are associated with frequency-domain OCC-based physical uplink shared channel (PUSCH) multiplexing; and The PUSCH transmission is received at least in part based on the configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission.

11. The apparatus according to claim 10, wherein: The configuration is associated with a Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) waveform or a Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveform; or The configuration instruction is used to select the randomization mode of the OCC sequence within a time period.

12. The apparatus of claim 10, wherein the configuration is associated with an OCC configuration for demodulation reference signal (DMRS), and the same OCC multiplexing mode or the same OCC sequence associated with the DMRS is applied to the PUSCH transmission.

13. The apparatus according to claim 10, wherein: The resource mapping for the OCC sequence is a tone-based resource mapping. The new sequence is generated for a given symbol sequence, wherein each symbol is repeated continuously a certain number of times, the number corresponding to the OCC length, and the new sequence is mapped to time-frequency resources. or The resource mapping for the OCC sequence is a block-based resource mapping, the new sequence being generated for the given symbol sequence, wherein symbol blocks are repeated consecutively a first number of times, the first number being at least in part based on a second number associated with the number of subcarriers in the frequency domain resource allocation and a third number associated with the OCC length, and the new sequence is mapped to time-frequency resources.

14. The apparatus of claim 10, wherein: The resource mapping for the OCC sequence is based at least in part on a chunk-based expansion, the new sequence being generated for a given symbol sequence, wherein the symbol chunks are repeated consecutively a first number of times, the first number being based at least in part on a second number associated with the size of the Discrete Fourier Transform (DFT) expander and a third number associated with the OCC length, and the new sequence is input to the DFT expander; or The resource mapping for the OCC sequence is at least partially based on sample-based expansion, the new sequence being generated for the given symbol sequence, wherein each symbol is repeated consecutively a certain number of times, the number corresponding to the OCC length, and the new sequence is input into the DFT expander.

15. The apparatus of claim 10, wherein the one or more processors are individually or jointly configured to: The Physical Random Access Channel (PRACH) transmission indicating the OCC capability of the User Equipment (UE) is received, wherein the configuration is received via message 2 (Msg2) based at least in part on the OCC capability, and the PUSCH transmission is either an initial message 3 (Msg3) transmission or a retransmission of Msg3.

16. A method for wireless communication performed by a user equipment (UE), the method comprising: Receive configuration associated with an orthogonal coverage code (OCC) sequence, wherein the OCC sequence is associated with frequency domain OCC-based physical uplink shared channel (PUSCH) multiplexing; as well as The PUSCH transmission is sent at least in part based on the configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission.

17. The method of claim 16, wherein: The OCC sequence is a Hadama sequence; The OCC sequence is associated with a vector of the Discrete Fourier Transform (DFT) matrix; The OCC sequence is a Zadeh-Zhu sequence; or The OCC sequence is a computer-generated sequence or a cyclically shifted version of the computer-generated sequence.

18. The method of claim 16, wherein: The configuration is associated with a Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) waveform or a Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveform; or The configuration instruction is used to select the randomization mode of the OCC sequence within a time period.

19. The method of claim 16, wherein the configuration is associated with an OCC configuration for demodulation reference signal (DMRS), and the same OCC multiplexing mode or the same OCC sequence associated with the DMRS is applied to the PUSCH transmission.

20. The method of claim 16, wherein the resource mapping for the OCC sequence is a tone-based resource mapping, the new sequence is generated for a given symbol sequence, wherein each symbol is repeated consecutively a certain number of times, the number corresponding to the OCC length, and the new sequence is mapped to a time-frequency resource.

21. The method of claim 16, wherein the resource mapping for the OCC sequence is a block-based resource mapping, the new sequence is generated for a given symbol sequence, wherein the symbol blocks are repeated consecutively a first number of times, the first number being at least in part based on a second number associated with the number of subcarriers in the frequency domain resource assignment and a third number associated with the OCC length, and the new sequence is mapped to time-frequency resources.

22. The method of claim 16, wherein the resource mapping for the OCC sequence is based at least in part on a chunk-based expansion, the new sequence being generated for a given symbol sequence, wherein symbol chunks are repeated consecutively a first number of times, the first number being based at least in part on a second number associated with the size of the Discrete Fourier Transform (DFT) expander and a third number associated with the OCC length, and the new sequence is input to the DFT expander.

23. The method of claim 16, wherein the resource mapping for the OCC sequence is at least partially based on sample-based expansion, the new sequence being generated for a given symbol sequence, wherein each symbol is repeated consecutively a certain number of times, the number corresponding to the OCC length, and the new sequence is input to a Discrete Fourier Transform (DFT) expander.

24. The method of claim 16, further comprising: A Physical Random Access Channel (PRACH) transmission indicating the UE's OCC capability is sent, wherein the configuration is received via message 2 (Msg2) based at least in part on the OCC capability, and the PUSCH transmission is either an initial message 3 (Msg3) transmission or a retransmission of Msg3.

25. A method for wireless communication performed by a network node, the method comprising: Send configurations associated with orthogonal coverage code (OCC) sequences, wherein the OCC sequences are associated with frequency-domain OCC-based physical uplink shared channel (PUSCH) multiplexing; as well as The PUSCH transmission is received at least in part based on the configuration, wherein the OCC sequence is applied to one or more symbols associated with the PUSCH transmission.

26. The method of claim 25, wherein: The configuration is associated with a Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) waveform or a Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveform; or The configuration instruction is used to select the randomization mode of the OCC sequence within a time period.

27. The method of claim 25, wherein the configuration is associated with an OCC configuration for demodulation reference signal (DMRS), and the same OCC multiplexing mode or the same OCC sequence associated with the DMRS is applied to the PUSCH transmission.

28. The method of claim 25, wherein: The resource mapping for the OCC sequence is a tone-based resource mapping. The new sequence is generated for a given symbol sequence, wherein each symbol is repeated continuously a certain number of times, the number corresponding to the OCC length, and the new sequence is mapped to time-frequency resources. or The resource mapping for the OCC sequence is a block-based resource mapping, the new sequence being generated for the given symbol sequence, wherein symbol blocks are repeated consecutively a first number of times, the first number being at least in part based on a second number associated with the number of subcarriers in the frequency domain resource allocation and a third number associated with the OCC length, and the new sequence is mapped to time-frequency resources.

29. The method of claim 25, wherein: The resource mapping for the OCC sequence is based at least in part on a chunk-based expansion, the new sequence being generated for a given symbol sequence, wherein the symbol chunks are repeated consecutively a first number of times, the first number being based at least in part on a second number associated with the size of the Discrete Fourier Transform (DFT) expander and a third number associated with the OCC length, and the new sequence is input to the DFT expander; or The resource mapping for the OCC sequence is at least partially based on sample-based expansion, the new sequence being generated for the given symbol sequence, wherein each symbol is repeated consecutively a certain number of times, the number corresponding to the OCC length, and the new sequence is input into the DFT expander.

30. The method of claim 25, further comprising: The Physical Random Access Channel (PRACH) transmission indicating the OCC capability of the User Equipment (UE) is received, wherein the configuration is received via message 2 (Msg2) based at least in part on the OCC capability, and the PUSCH transmission is either an initial message 3 (Msg3) transmission or a retransmission of Msg3.

Images