Orthogonal cover codes for multiplexing transmissions by multiple user equipments

Abstract

Methods, systems, and devices for wireless communication are described herein. Techniques described herein relate to multiplexing transmissions from multiple user equipments (UEs) on the same time-frequency resource. The UE may receive control signaling from a network entity indicating a multiplexing order, a repetition configuration, and an orthogonal coverage coding (OCC) configuration to be applied to an uplink grant. The repetition configuration may indicate a set of redundancy versions (RVs), a number of resource elements (REs) for each RV, and a number of repetitions for each RV. The UE may generate a transport block (TB) using the OCC configuration, and an instance of the RV of the TB may be mapped to the RE of the TB based on the multiplexing order and the OCC configuration.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 186,772, filed March 20, 2023, entitled “ORTHOGONALCOVER CODE FOR MULTIPLEXING TRANSMISSIONS BY MULTIPLE USER EQUIPMENTS”, which has been assigned to the assignee of this application and whose entire contents are expressly incorporated herein by reference. Technical Field

[0003] The following discussion relates to wireless communications, including orthogonal overlay codes for multiplexing transmissions carried out by multiple user equipment. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, and broadcasting. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, improved LTE (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices (which may be referred to as User Equipment (UE)). Summary of the Invention

[0005] The described technology relates to improved methods, systems, devices, and apparatuses for supporting orthogonal coverage codes (OCCs) for multiplexing transmissions performed by multiple user equipments (UEs). Two or more UEs can use orthogonal coverage decoding configurations to simultaneously transmit uplink transmissions scheduled for repetition to a network entity using the same time-frequency resources. For example, transmitting UEs can use orthogonal coverage codes to achieve orthogonal M-order UE multiplexing without complex scrambling and / or complex receiver designs at the network entity, where M refers to the multiplexing order (e.g., the number of UEs transmitting on the same time-frequency resources). For example, the network entity can indicate to the UEs the multiplexing order M, repetition configuration, and orthogonal coverage decoding configuration to be applied to the uplink permission. The repetition configuration can indicate a set of redundant versions (RVs) (e.g., the number of RVs associated with uplink transmissions for each UE in the UE set), the number of resource elements (REs) associated with each repetition of each RV in the RV set, and the number of repetitions associated with each RV in the RV set (e.g., the number of times each RV in the RV set is repeated). Each UE performs a repetitive mapping of RVs across time based on an orthogonal coverage code and multiplexing order M, for example, by using indicated rows or columns of a Hadamard matrix or Discrete Fourier Transform (DFT) matrix whose size is set based on the size of M, and thus the transmissions performed by M UEs are orthogonal. If the total number or repetitions is greater than 2M, the UE can apply an OCC-based mapping of repetitive RVs across time without increasing the amount of time-frequency resources used for uplink transmissions. Accordingly, from a network perspective, uplink capacity is increased.

[0006] A method for wireless communication at a user equipment (UE) is described. The method may include: receiving from a network entity control signaling an indication of a multiplexing order, a repeat configuration, and an orthogonal coverage decoding configuration to be applied to uplink permission, wherein the repeat configuration indicates a set of redundant versions, a first number of REs associated with each repeat of each redundant version in the set of redundant versions, and a number of repeats associated with each redundant version in the set of redundant versions, and wherein the orthogonal coverage decoding configuration is based on the multiplexing order; generating a transport block comprising one or more instances of the set of redundant versions, the one or more instances of the set of redundant versions being mapped to a set of REs of the transport block over time based on the multiplexing order and the orthogonal coverage decoding configuration; and transmitting an uplink transmission comprising the transport block to the network entity according to the uplink permission.

[0007] An apparatus for wireless communication at a UE is described. The apparatus may include: a processor; a memory coupled to the processor; and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive from a network entity control signaling indicating a multiplexing order, repeat configuration, and orthogonal coverage decoding configuration to be applied to uplink permission, wherein the repeat configuration indicates a set of RVs, a first number of REs associated with each repeat of each RV in the RV set, and a number of repeats associated with each RV in the RV set, and wherein the orthogonal coverage decoding configuration is based on the multiplexing order; generate a transport block comprising one or more instances of the RV set, the one or more instances of the RV set being mapped to a set of REs of the transport block over time based on the multiplexing order and the orthogonal coverage decoding configuration; and transmit an uplink transmission comprising the transport block to the network entity according to the uplink permission.

[0008] Another apparatus for wireless communication at a UE is described. The apparatus may include: unit for receiving from a network entity control signaling indicating a multiplexing order, repeat configuration, and orthogonal coverage decoding configuration to be applied to uplink permission, wherein the repeat configuration indicates a set of RVs, a first number of REs associated with each repeat of each RV in the RV set, and a number of repeats associated with each RV in the RV set, and wherein the orthogonal coverage decoding configuration is based on the multiplexing order; unit for generating a transport block comprising one or more instances of the RV set, the one or more instances of the RV set being mapped to a set of REs of the transport block across time based on the multiplexing order and the orthogonal coverage decoding configuration; and unit for transmitting an uplink transmission comprising the transport block to the network entity according to the uplink permission.

[0009] A non-transitory computer-readable medium is described, storing code for wireless communication at a UE. The code may include instructions executable by a processor to: receive from a network entity control signaling indicating a multiplexing order, repeat configuration, and orthogonal coverage decoding configuration to be applied to uplink permission, wherein the repeat configuration indicates a set of RVs, a first number of REs associated with each repeat of each RV in the RV set, and a number of repeats associated with each RV in the RV set, and wherein the orthogonal coverage decoding configuration is based on the multiplexing order; generate a transport block comprising one or more instances of the RV set, the one or more instances of the RV set being mapped to a set of REs of the transport block over time based on the multiplexing order and the orthogonal coverage decoding configuration; and transmit an uplink transmission comprising the transport block to the network entity according to the uplink permission.

[0010] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for the following steps: receiving from the network entity an indication that the RE set may be associated with the uplink permission; and mapping each instance of each RV in the RV set to a subset of REs in the RE set, wherein a second number of REs in each subset is the first number multiplied by the multiplexing order.

[0011] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for the following steps: receiving a second uplink permission associated with a second set of REs from the network entity, wherein the second set of REs includes the same number of REs as the set of REs, and wherein a second multiplexing order associated with the second uplink permission may be one; generating a second transport block according to the repeat configuration; and sending a second uplink transmission including the second transport block to the network entity according to the second uplink permission, wherein a first data capacity of the transport block is equal to a second data capacity of the second transport block.

[0012] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, generating the transport block includes operations, features, units, or instructions for the following steps: generating the RV set from a data buffer; mapping a set of repetitions of the RV set across time to a corresponding consecutive subset of REs in the RE set, wherein the number of repetitions in each set of repetitions may be based on the multiplexing order; and applying the orthogonal overlay decoding configuration to the set of repetitions of the RV set across time to the corresponding consecutive subset of REs to generate the transport block.

[0013] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, applying the orthogonal overlay decoding configuration may include operations, features, units, or instructions for applying the orthogonal overlay decoding configuration on a per-symbol, per-slot, per-resource-unit, or per-redundancy-version basis.

[0014] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the control signaling may include operations, features, units, or instructions for the following steps: receiving the control signaling indicating that the orthogonal overlay decoding configuration includes rows or columns associated with a Hadamard matrix or a discrete Fourier transform matrix, and wherein the control signaling indicates which rows or columns of the Hadamard matrix or the discrete Fourier transform matrix may be associated with the UE.

[0015] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the size of the Hadamard matrix or the discrete Fourier transform matrix may be associated with the multiplexing order.

[0016] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the control signaling may include operations, features, units, or instructions for the following steps: receiving a first control message indicating the repeat configuration; and receiving a second control message indicating the uplink permission, the multiplexing order, and the orthogonal overlay decoding configuration.

[0017] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the total number of repetitions may be at least twice the reuse order, and the total number of repetitions may be the number of repetitions associated with each RV multiplied by the number of RVs in the set of RVs.

[0018] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the network entity may be a non-terrestrial network entity.

[0019] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the control signaling may include operations, features, elements, or instructions for the following steps: receiving the control signaling via radio resource control signaling, media access control (MAC) control elements, or a combination thereof.

[0020] A method for wireless communication at a network entity is described. The method may include: sending control signaling to a set of user equipment (UEs) indicating a multiplexing order, repeat configuration, and corresponding orthogonal coverage decoding configuration to be applied to a corresponding uplink permission for the set of UEs, wherein the repeat configuration indicates a set of RVs, a first number of REs associated with each repeat of each RV in the set of RVs, and a number of repeats associated with each RV in the set of RVs, and wherein the corresponding orthogonal coverage decoding configuration is based on the multiplexing order; receiving from the set of UEs a multiplexed set of uplink transmissions, the multiplexed set of uplink transmissions including corresponding transport blocks encoded using the corresponding orthogonal coverage decoding configuration, wherein the corresponding transport blocks include one or more corresponding instances of a corresponding RV set, the one or more instances of the corresponding RV set being mapped to a set of REs associated with the corresponding uplink permission based on the multiplexing order and the corresponding orthogonal coverage decoding configuration; and decoding the corresponding transport blocks based on the corresponding orthogonal coverage decoding configuration associated with the set of UEs.

[0021] An apparatus for wireless communication at a network entity is described. The apparatus may include: a processor; a memory coupled to the processor; and instructions stored in the memory. The instructions may be executable by the processor to cause the device to perform the following operations: sending control signaling to a set of user equipment (UEs) indicating a multiplexing order, repeat configuration, and corresponding orthogonal coverage decoding configuration to be applied to a corresponding uplink permission for the set of UEs, wherein the repeat configuration indicates a set of RVs, a first number of REs associated with each repeat of each RV in the set of RVs, and a number of repeats associated with each RV in the set of RVs, and wherein the corresponding orthogonal coverage decoding configuration is based on the multiplexing order; receiving a multiplexed set of uplink transports from the set of UEs, the multiplexed set of uplink transports including corresponding transport blocks encoded using the corresponding orthogonal coverage decoding configuration, wherein the corresponding transport blocks include one or more corresponding instances of a corresponding set of RVs, the one or more corresponding instances of the corresponding set of RVs being mapped to a set of REs associated with the corresponding uplink permission based on the multiplexing order and the corresponding orthogonal coverage decoding configuration; and decoding the corresponding transport blocks based on the corresponding orthogonal coverage decoding configuration associated with the set of UEs.

[0022] Another apparatus for wireless communication at a network entity is described. The apparatus may include: a unit for transmitting control signaling to a set of user equipment (UEs) indicating a multiplexing order, repetition configuration, and corresponding orthogonal coverage decoding configuration to be applied to a corresponding uplink permission for the set of UEs, wherein the repetition configuration indicates a set of RVs, a first number of REs associated with each repetition of each RV in the set of RVs, and a number of repetitions associated with each RV in the set of RVs, and wherein the corresponding orthogonal coverage decoding configuration is based on the multiplexing order; a unit for receiving a multiplexed set of uplink transmissions from the set of UEs, the multiplexed set of uplink transmissions including corresponding transport blocks encoded using the corresponding orthogonal coverage decoding configuration, wherein the corresponding transport blocks include one or more corresponding instances of a corresponding RV set, the one or more instances of the corresponding RV set being mapped to a set of REs associated with the corresponding uplink permission based on the multiplexing order and the corresponding orthogonal coverage decoding configuration; and a unit for decoding the corresponding transport blocks based on the corresponding orthogonal coverage decoding configuration associated with the set of UEs.

[0023] A non-transitory computer-readable medium is described, which stores code for wireless communication at network entities. The code may include instructions executable by a processor to perform the following operations: sending control signaling to a set of user equipment (UEs) indicating a multiplexing order, repeat configuration, and corresponding orthogonal coverage decoding configuration to be applied to a corresponding uplink permission for the set of UEs, wherein the repeat configuration indicates a set of RVs, a first number of REs associated with each repeat of each RV in the set of RVs, and a number of repeats associated with each RV in the set of RVs, and wherein the corresponding orthogonal coverage decoding configuration is based on the multiplexing order; receiving a set of multiplexed uplink transports from the set of UEs, the set of multiplexed uplink transports including corresponding transport blocks encoded using the corresponding orthogonal coverage decoding configuration, wherein the corresponding transport blocks include one or more corresponding instances of a corresponding RV set, the one or more instances of the corresponding RV set being mapped to a set of REs associated with the corresponding uplink permission based on the multiplexing order and the corresponding orthogonal coverage decoding configuration; and decoding the corresponding transport blocks based on the corresponding orthogonal coverage decoding configuration associated with the set of UEs.

[0024] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, elements, or instructions for the following steps: sending an indication to the set of UEs to the set of REs associated with the corresponding uplink permission, wherein the multiplexed uplink transmission set may be received via the set of REs.

[0025] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for the following steps: sending a second uplink permission associated with a second set of REs to a UE in the set of UEs, wherein the second set of REs includes the same number of REs as the set of REs, and wherein a second multiplexing order associated with the second uplink permission may be one; and receiving a second uplink transmission including a second transport block from the UE according to the second uplink permission, wherein a first data capacity of the corresponding transport block associated with the UE may be equal to a second data capacity of the second transport block.

[0026] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, decoding a corresponding transport block based on the corresponding orthogonal overlay decoding configuration associated with the set of UEs may include operations, features, elements, or instructions for decoding the corresponding transport block based on the corresponding orthogonal overlay decoding configuration on a per-symbol, per-slot, per-resource-element, or per-RV basis.

[0027] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, sending the control signaling may include operations, features, units, or instructions for the following steps: sending the control signaling indicating that the corresponding orthogonal overlay decoding configuration includes rows or columns associated with a Hadamard matrix or a discrete Fourier transform matrix, and wherein the control signaling indicates which rows or columns of the Hadamard matrix or the discrete Fourier transform matrix may be associated with each UE in the UE set.

[0028] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the size of the Hadamard matrix or the discrete Fourier transform matrix may be associated with the multiplexing order.

[0029] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting the control signaling may include operations, features, elements, or instructions for the following steps: transmitting a first control message indicating the repeat configuration; and transmitting a corresponding second control message to the set of UEs indicating the corresponding uplink permission, the multiplexing order, and the corresponding orthogonal coverage decoding configuration.

[0030] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the total number of repetitions may be at least twice the reuse order, and the total number of repetitions may be the number of repetitions associated with each RV multiplied by the number of RVs in the set of RVs.

[0031] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the network entity may be a non-terrestrial network entity.

[0032] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, transmitting the control signaling may include operations, features, elements, or instructions for the following steps: transmitting the control signaling via radio resource control signaling, MAC control elements, or a combination thereof. Attached Figure Description

[0033] Figure 1 An example of a wireless communication system that supports orthogonal coverage codes (OCCs) for multiplexing transmissions performed by multiple user equipments (UEs) is shown, according to one or more aspects of this disclosure.

[0034] Figure 2 Another example of a wireless communication system that supports one or more aspects of this disclosure for multiplexing OCCs of transmissions performed by multiple UEs is shown.

[0035] Figure 3 An example of resource configuration for each UE is shown that supports one or more aspects of this disclosure for multiplexing OCCs performed by multiple UEs.

[0036] Figure 4 Examples of resource configurations for nonorthogonal multiple access uplink transmissions are shown, according to one or more aspects of this disclosure.

[0037] Figure 5 Resource configurations supporting OCC for multiplexing transmissions performed by multiple UEs are shown, according to one or more aspects of this disclosure.

[0038] Figure 6 An example of resource configuration for multiplexing OCCs performed by multiple UEs is shown, according to one or more aspects of this disclosure.

[0039] Figure 7 An example of resource configuration for multiplexing OCCs performed by multiple UEs is shown, according to one or more aspects of this disclosure.

[0040] Figure 8An example of an encoding configuration that supports one or more aspects of this disclosure for multiplexing OCC transmissions performed by multiple UEs is shown.

[0041] Figure 9 An example of a process flow for multiplexing OCC transmissions performed by multiple UEs is shown, according to one or more aspects of this disclosure.

[0042] Figure 10 and Figure 11 A block diagram of an apparatus for multiplexing OCCs performed by multiple UEs is shown, according to one or more aspects of this disclosure.

[0043] Figure 12 A block diagram is shown of a communication manager that supports OCC for multiplexing transmissions performed by multiple UEs, according to one or more aspects of this disclosure.

[0044] Figure 13 A schematic diagram of a system including an apparatus for supporting OCC for multiplexing transmissions performed by multiple UEs, according to one or more aspects of this disclosure, is shown.

[0045] Figure 14 and Figure 15 A block diagram of an apparatus for multiplexing OCCs performed by multiple UEs is shown, according to one or more aspects of this disclosure.

[0046] Figure 16 A block diagram is shown of a communication manager that supports OCC for multiplexing transmissions performed by multiple UEs, according to one or more aspects of this disclosure.

[0047] Figure 17 A schematic diagram of a system including an apparatus for supporting OCC for multiplexing transmissions performed by multiple UEs, according to one or more aspects of this disclosure, is shown.

[0048] Figure 18 and Figure 19 A flowchart is shown depicting a method for supporting OCC for multiplexing transmissions performed by multiple UEs, according to one or more aspects of this disclosure. Detailed Implementation

[0049] In some wireless communication systems (such as narrowband Internet of Things (NB-IoT) systems), user equipment (UEs) can transmit (e.g., uplink communication) multiple decoded copies of data (e.g., data duplication). In some examples, duplication may include a redundant version (RV) of the uplink Hybrid Automatic Repeat Request (HARQ). To increase uplink capacity, multiple UEs can use non-orthogonal multiple access (NOMA) to access resources simultaneously, where data from multiple UEs is identified at the network entity. In NOMA scenarios, simultaneous transmission from multiple UEs can lead to uplink interference at the network entity. Furthermore, identifying data as originating from a specific UE at the network entity can be complex and time-consuming. For example, identifying data from a particular UE may involve UEs employing complex and robust scrambling schemes and complex receiver designs (e.g., at the base station).

[0050] Accordingly, as disclosed herein, the transmitting UE can use orthogonal overlay codes (OCC) to achieve orthogonal M-order UE multiplexing without robust scrambling and / or complex receiver design at the network entity. If the total number or repetitions is greater than 2M, the UE applies M-factor overlay decoding without increasing the amount of time-frequency resources used for uplink transmission. Accordingly, from the network perspective, uplink capacity is increased (in terms of the number of UEs that can be scheduled in a given time-frequency resource, where there is almost no interference between UEs).

[0051] Network entities can send control signaling to UEs indicating the multiplexing order, repetition configuration, and orthogonal coverage decoding configuration to be applied to the uplink. The multiplexing order M indicates the number (e.g., number) of uplink transmissions from different UEs that will be multiplexed on the same time-frequency resources. Network entities can instruct the repetition configuration and orthogonal coverage decoding configuration to the M UEs that will transmit multiplexed uplink transmissions. The repetition configuration can indicate the number of RVs associated with the uplink transmission for each UE, the number of resource elements (REs) associated with each RV (e.g., each repetition of each RV), and the number of repetitions associated with each RV. For example, the first RV (RV 0) can be repeated 4 times, and the second RV (RV 2) can be repeated 4 times. Each UE uses orthogonal coverage codes to perform M-factor coverage decoding, and accordingly, the transmissions performed by the M UEs will be orthogonal. For example, each UE can use indicated rows of a Hadamard matrix to perform M-factor coverage decoding, where the size of the Hadamard matrix is ​​set based on the size of M. M-factor coverage decoding can be performed on a symbol-by-symbol, slot-by-slot, resource-by-resource-unit, or RV-by-RV basis.

[0052] Various aspects of this disclosure are first described in the context of a wireless communication system. Further aspects of this disclosure are illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to orthogonal coverage codes for multiplexing transmissions performed by multiple user equipment.

[0053] Figure 1 Examples of a wireless communication system 100 supporting orthogonal coverage codes for multiplexing transmissions performed by multiple user equipments, according to one or more aspects of this disclosure, are shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an improved LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not expressly mentioned herein.

[0054] Network entity 105 may be distributed throughout a geographic area to form wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network device, among other terms. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographic area where network entity 105 and UE 115 may support signal transmission according to one or more radio access technologies (RATs).

[0055] UE 115 can be distributed throughout the entire coverage area 110 of the wireless communication system 100, and each UE 115 can be stationary, mobile, or both at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are shown in the document. The UE 115 described herein may be able to support communication with various types of devices, such as other UE 115s or network entities 105, such as Figure 1 As shown.

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

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

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

[0059] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105 (such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration initiated by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. RU 170 may also be referred to as a radio headend, an intelligent radio headend, a remote radio headend (RRH), a remote radio unit (RRU), or a transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0060] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layer (such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer)) functionality and signaling, and can each be at least partially controlled by CU 160. Alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some protocol layer functions can be performed by one of CU 160, DU 165, or RU 170, while other protocol layer functions can be performed by a different one of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165s via midrange communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170s via frontend communication link 168 (e.g., open frontend (FH) interface). In some examples, a mid-range communication link 162 or a front-end communication link 168 may be implemented based on an interface (e.g., a channel) between layers of the protocol stack, which is supported by a corresponding network entity 105 communicating via such a communication link.

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

[0062] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and an RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Alternatively, CU 160 may communicate with the core network via an interface (which may be part of a backhaul link) and with other CU 160s (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be part of a backhaul link).

[0063] IAB node 104 can refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability). DU 165 can act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT can act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor can be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor can relay UE transmissions through one or more other IAB nodes 104). Alternatively or additionally, depending on the AN's relay chain or configuration, IAB node 104 can also be referred to as a parent node or child node of other IAB nodes 104. Therefore, the IAB-MT entity of IAB node 104 can provide a Uu interface to child IAB node 104 to receive signaling from parent IAB node 104, and a DU interface (e.g., DU 165) can provide a Uu interface to parent IAB node 104 to signal to child IAB node 104 or UE 115.

[0064] For example, IAB node 104 may be referred to as a parent node supporting communication for child IAB nodes, or a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, the IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may directly signal transmissions to UE 115, or both. The IAB donor's CU 160 may establish a signaled communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions via DU 165 (e.g., transmissions relayed from the IAB donor to UE 115). That is, data may be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104. Communication between IAB node 104 and IAB node 104 can be scheduled by DU 165 of IAB donor, and communication between IAB node 104 and IAB node 104 can also be scheduled by DU 165 of IAB node 104.

[0065] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support orthogonal coverage codes for multiplexing transmissions performed by multiple user equipments, as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) can be additionally or alternatively performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

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

[0067] The UE 115 described in this document may be able to communicate with various types of devices, such as other UEs 115 that can sometimes act as repeaters, as well as network entities 105 and network devices (including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, and other examples). Figure 1 As shown.

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

[0069] In some examples (such as in carrier aggregation configurations), carriers may also have acquisition signaling or control signaling to coordinate operations against other carriers. Carriers may be associated with frequency channels (e.g., Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and can be identified according to the channel grid for discovery by UE115. Carriers can operate in standalone mode, in which case UE115 can perform initial acquisition and connection via a carrier, or carriers can operate in non-standalone mode, in which case different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0070] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from network entity 105 to UE 115, uplink transmissions (e.g., reverse link transmissions) from UE 115 to network entity 105, or both, and other transmission configurations. A carrier may carry downlink or uplink communication (e.g., in FDD mode) or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0071] A carrier can be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth can be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth can be one bandwidth in a set of bandwidths for a specific radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) can have a hardware configuration that supports communication using a specific carrier bandwidth, or can be configured to support communication using one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 can include a network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 can be configured to operate on a portion (e.g., a subband, BWP) or all of the carrier bandwidth.

[0072] The signal waveform transmitted via a carrier can be composed of multiple subcarriers (e.g., using multicarrier modulation (MCM) techniques such as Orthogonal Frequency Division Multiplexing (OFDM) or Discrete Fourier Transform Extended OFDM (DFT-S-OFDM). In a system employing MCM, an RE can refer to a symbol period (e.g., the duration of a modulation symbol) and a subcarrier resource, in which case the symbol period and subcarrier spacing can be inversely related. The number of bits carried through each RE can depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of REs and a relatively high-order modulation scheme can correspond to a relatively high communication rate. Wireless communication resources can refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources can increase the data rate or data integrity used for communication with UE 115.

[0073] One or more digital schemes (numerologies) can be supported for a carrier, and the digital scheme can include subcarrier spacing (Δf) and a cyclic prefix. A carrier can be divided into one or more BWPs with the same or different digital schemes. In some examples, UE 115 can be configured with multiple BWPs. In some examples, a single BWP for a carrier can be active at a given time, and communication for UE 115 can be restricted to one or more active BWPs.

[0074] It can be expressed in a basic unit of time (which can be, for example, T). s =1 / (Δf) max ·N f For a sampling period of ) seconds, Δf max This can represent the supported subcarrier spacing, and N f The time interval for network entity 105 or UE 115 can be represented as a multiple of the supported Discrete Fourier Transform (DFT) size. The time interval for communication resources can be organized based on radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0075] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., this depends on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N) symbols. f The symbol period is associated with a number of sampling periods. The duration of the symbol period can depend on the subcarrier spacing or the operating frequency band.

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

[0077] Physical channels can be multiplexed using various techniques for communication using carriers. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels for signaling via a downlink carrier. A control region (e.g., a control resource set (CORESET)) for physical control channels can be defined by a set of symbol periods and can extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) can be configured for a set of UEs 115. For example, one or more UEs 115 can monitor or search for control regions for control information based on one or more search space sets, and each search space set can include one or more control channel candidates arranged in a cascaded manner at one or more aggregation levels. The aggregation level for control channel candidates can refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a common search space set configured to send control information to multiple UEs 115 and a UE-specific search space set used to send control information to a specific UE 115.

[0078] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the extent of such cells can range from small areas (e.g., structures, subsets of structures) to large areas. For example, a cell may be or include buildings, subsets of buildings, or external space between or overlapping coverage areas 110, and other examples.

[0079] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

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

[0081] Some UE 115 devices (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC can include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents it to humans interacting with the application. Some UE 115 devices can be designed to collect information or automate the behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based billing.

[0082] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception, but not concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115 include: entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

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

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

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

[0086] Wireless communication system 100 can operate using one or more frequency bands (which can range from 300 MHz to 300 GHz). Typically, the region from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) region or decimeter band because the wavelength range extends from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but the waves can be sufficiently penetrating structures to provide service to UE 115 located indoors via macrocells. Compared to communication using smaller frequencies and longer waves in the lower HF or VHF portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter distances (e.g., less than 100 km).

[0087] Wireless communication system 100 can utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 can employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating using unlicensed RF spectrum bands, devices (such as network entity 105 and UE 115) can employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands can be based on carrier aggregation configurations that combine component carriers operating using licensed frequency bands (e.g., LAA). Operation in the unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and other examples.

[0088] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels (which may support MIMO operation or transmit or receive beamforming). For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located in different geographical locations. Network entity 105 may include an antenna array having a set of rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Alternatively or additionally, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0089] Network entity 105 or UE 115 can use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such a technique can be called spatial multiplexing. For example, a transmitting device can transmit multiple signals via different antennas or different combinations of antennas. Similarly, a receiving device can receive multiple signals via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) (where multiple spatial layers are transmitted to the same receiving device) and multi-user MIMO (MU-MIMO) (where multiple spatial layers are transmitted to multiple devices).

[0090] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to form or guide an antenna beam (e.g., transmit beam, receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements can include applying amplitude offset, phase offset, or both to the signals carried via the antenna elements associated with the transmitting or receiving device. The adjustments associated with each antenna element can be defined by a set of beamforming weights associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device, or relative to some other orientation).

[0091] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Network entity 105 may transmit some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) multiple times along different directions. For example, network entity 105 may transmit signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) to identify the beam direction for subsequent transmissions or receptions by network entity 105.

[0092] A transmitting device (e.g., transmitting network entity 105, transmitting UE 115) may transmit signals (such as data signals associated with that receiving device) along a single beam direction (e.g., a direction associated with a specific receiving device, such as receiving network entity 105 or receiving UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on signals transmitted along one or more beam directions. For example, UE 115 may receive one or more signals transmitted by network entity 105 along different directions and may report to network entity 105 an indication of the signal received by UE 115 that has the highest signal quality or otherwise acceptable signal quality.

[0093] In some examples, multiple beam directions can be used to perform transmissions by a device (e.g., network entity 105 or UE 115), and the device can use a combination of digital precoding or beamforming to generate a combined beam for (e.g., from network entity 105 to UE 115) transmissions. UE 115 can report feedback indicating precoding weights for one or more beam directions, and this feedback can correspond to a configured set of beams spanning the system bandwidth or one or more subbands. Network entity 105 can transmit reference signals that can be precoded or unprecoded (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)). UE 115 can provide feedback on beam selection, which can be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel type codebook, linear combination type codebook, port selection type codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) along one or more directions, UE 115 may employ similar techniques to transmit signals multiple times along different directions (e.g., to identify beam directions for subsequent transmissions or receptions by UE 115) or to transmit signals along a single direction (e.g., to transmit data to a receiving device).

[0094] When receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105), the receiving device (e.g., UE 115) can perform reception operations according to multiple reception configurations (e.g., directional listening). For example, the receiving device can perform reception via different antenna subarrays, by processing the received signals according to different antenna subarrays, by performing reception according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array (e.g., different sets of directional listening weights), or by processing the received signals according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array (any of the above operations can be referred to as "listening" according to different reception configurations or reception directions), thereby performing reception according to multiple reception directions. In some examples, the receiving device can use a single reception configuration to receive along a single beam direction (e.g., when receiving data signals). A single receiver configuration can be aligned along a beam direction determined based on listening in different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening in multiple beam directions).

[0095] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. HARQ feedback is a technique used to increase the likelihood of data being correctly received via communication links (e.g., communication link 125, D2D communication link 135). HARQ can include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal and noise conditions). In some examples, the device can support same-slot HARQ feedback, in which case the device can provide HARQ feedback for data received via previous symbols in a specific time slot. In some other examples, the device can provide HARQ feedback in subsequent time slots or according to some other time interval.

[0096] In some examples, network entity 105 can use the same time-frequency resources to schedule uplink transmissions from multiple UEs 115 (e.g., M UEs). The transmitting UE 115 can use orthogonal coverage codes (e.g., OCC) to perform M-factor coverage decoding on the transmission to achieve orthogonal M-order UE multiplexing without robust scrambling and / or complex receiver design at the network entity. If the total number or repetitions is greater than 2M, UE 115 applies M-factor coverage decoding without increasing the amount of time-frequency resources used for uplink transmissions. Accordingly, from a network perspective, uplink capacity can be increased.

[0097] Network entity 105 may send control signaling to UE 115 indicating the multiplexing order, repetition configuration, and orthogonal coverage decoding configuration to be applied to the uplink. The multiplexing order M indicates the number of uplink transmissions from different UEs 115 that will be multiplexed on the same time-frequency resources. The network entity may indicate the repetition configuration and orthogonal coverage decoding configuration to the M UEs 115 that will transmit the multiplexed uplink transmissions. The repetition configuration may indicate the number of RVs associated with or included in the uplink transmissions for each UE in UE 115, the number of REs associated with or included in each RV (e.g., the number of REs for each repetition of each RV), and the number of repetitions associated with each RV (e.g., the number of times each RV is scheduled to be repeated). For example, the first RV (RV 0) may be repeated 4 times, and the second RV (RV 2) may be repeated 4 times. Each UE 115 uses OCC to perform M-factor coverage decoding, and accordingly, the transmissions performed by the M UEs will be orthogonal. For example, each UE can perform M-factor coverage decoding using indicated rows or columns of a Hadamard matrix or DFT matrix, where the size of the Hadamard matrix or DFT matrix is ​​based on the size of M. M-factor coverage decoding can be performed on a symbol-by-symbol, slot-by-slot, resource-element-by-resource-unit, or RV-by-RV basis.

[0098] Figure 2 An example of a wireless communication system 200 supporting OCC for multiplexing transmissions performed by multiple UEs 115, according to one or more aspects of this disclosure, is shown. The wireless communication system 200 may implement aspects of the wireless communication system 100, or may be implemented by aspects of the wireless communication system 100. For example, the wireless communication system 200 may include UEs 115-a and UEs 115-b, which may be related to... Figure 1 An example of UE 115 is described. The wireless communication system 200 also includes a first network entity 105-a, which may be as described above. Figure 1 An example of network entity 105 described.

[0099] In some examples, UE 115-a and / or UE 115-b may be NB-IoT devices. To ensure reliable communication where UE 115-a and / or UE 115-b are NB-IoT devices, UE 115-a and / or UE 115-b may transmit multiple decoded copies of data (e.g., data duplication may be transmitted). In some examples, duplication may include HARQ RV. Duplication can be used as a method or dimension for multiplexing multiple uplink transmissions from UE 115-a and UE 115-b to facilitate increased uplink capacity (e.g., packaging transmissions from multiple UE 115s into the same time-frequency resource). Multiple UE 115s may transmit RVs in the same time-frequency resource. However, multiplexing multiple UE 115s may cause interference at network entity 105-a. As discussed herein, orthogonal overlay decoding configurations can mitigate potential interference. Specifically, data from UE 115s can be overlaid and decoded orthogonally across RVs. In some cases, multiple UE 115s (e.g., UE 115-a and / or UE 115-b) may also use quadrature demodulation reference signals (DMRS), which use their own OCC.

[0100] UE 115-a can use communication link 125-a to communicate with network entity 105-a, and UE 115-b can use communication link 125-b to communicate with network entity 105-a. Communication link 125-a can be an example of an NR or LTE link between UE 115-a and network entity 105-a. Communication link 125-b can be an example of an NR or LTE link between UE 115-b and network entity 105-b. In some examples, communication link 125-a and / or communication link 125-b can be examples of a non-terrestrial network (NTN) link. Communication link 125-a and communication link 125-b can include bidirectional links that implement both uplink and downlink communication. For example, UE 115-a can use communication link 125-a to send uplink signal 205-a (e.g., uplink transmission) (such as uplink control signal or uplink data signal) to network entity 105-a, and network entity 105-a can use communication link 125-a to send downlink signal 210-a (e.g., downlink transmission) (such as downlink control signal or downlink data signal) to UE 115-a. UE 115-b can use communication link 125-b to send uplink signal 205-b (e.g., uplink transmission) (such as uplink control signal or uplink data signal) to network entity 105-a, and network entity 105-a can use communication link 125-b to send downlink signal 210-b (e.g., downlink transmission) (such as downlink control signal or downlink data signal) to UE 115-b.

[0101] To mitigate interference caused by uplink transmissions from UE 115 on the same time-frequency resources, network entity 105-a may send control signaling 230 to UE 115. Control signaling 230 indicates the M-factor orthogonal coverage decoding configuration to be applied to uplink permissions for UEs that will be multiplexed on the same time-frequency resources. For example, network entity 105-a may send a second control signaling 235 including uplink permission scheduling 250 for uplink transmissions 250 for UEs 115-a and UE 115-b on the same time-frequency resources. Control signaling 230 may indicate the multiplexing order, repetition configuration, and corresponding orthogonal coverage decoding configuration to be applied to the uplink permissions for the respective UE 115. The repetition configuration may indicate the RV set, the number of REs associated with each RV in the RV set, and the number of RVs associated with each RV in the RV set. In some cases, duplicate configuration can be applied to all uplink transmissions for a given UE 115 (e.g., it can be configured via RRC for uplink transmissions for a given UE 115). In some cases, duplicate configuration can be applied to a given indicated uplink permission.

[0102] UE 115 can organize data into RVs (Real Transport Units) based on control signaling received from network entity 105 for transmission in uplink transmission 250 according to uplink permission. Specifically, UE 115 can generate a transport block set using an orthogonal overlay decoding configuration. The number of REs associated with each transport block in the transport block set is based on the multiplexing order and the number of REs associated with each RV. Each transport block in the transport block set can be associated with an RV in the RV set. Generating transport blocks may involve: generating a second transport block set from a data buffer according to a repetition configuration; and applying the orthogonal overlay decoding configuration to the second transport block set to generate the transport block set. After generating the transport blocks, UE 115 can transmit the transport blocks in uplink transmission 250 according to uplink permission.

[0103] Network entity 105-a can receive transport blocks in the corresponding uplink transmission 250 from each UE in UE 115 in the same time-frequency resources. Network entity 105-a can decode the corresponding transport block set based on the corresponding orthogonal coverage decoding configuration associated with a given UE 115.

[0104] Figure 3 An example of resource configuration 300 for each UE 115 is shown, supporting OCC for multiplexing transmissions performed by multiple UEs 115, according to one or more aspects of this disclosure. Figure 3 The UE 115-c shown may be about Figure 1An example of UE 115 is described. The resource configuration illustrates the configuration of resources (e.g., REs) for uplink permission for UE 115-c. Resource configuration 300 may include multiple repetitions organized according to RVs 305 (such as first RV 305-a, second RV 305-b, third RV 305-c, fourth RV 305-d, up to N RVs 305, where N can be an integer). Each RV may have a duration of 307T. RV For example, each RV may include several REs. Individual RVs 305 may be cyclically used for transmission in an alternating or interleaved manner. For example, first RV 305-a and third RV 305-c correspond to RV 0, while second RV 305-b and fourth RV 305-d correspond to RV 2, and these RVs 0 and RV 2 are transmitted cyclically in an alternating pattern using first RV 305-a to fourth RV 305-d within the corresponding time slot duration 307.

[0105] Resource configuration 300 may include the total RE set, which includes There are N REs, of which N RU N indicates the number of resource units (RUs) to which a transport block can be mapped. rep Indicates the number of repetitions of each transport block within a transport block. This can indicate the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols within a resource cell (e.g., the number of REs within the resource cell). For example, uplink permission can be... Uplink transmissions are scheduled within each RE. RV repetition may include RV cycling, where each RV 305 includes Each (RE). RV 305 may include multiple resource units 320, each resource unit 320 may include multiple time slots 315, and each time slot 315 may include multiple symbols 310.

[0106] Figure 4 An example of resource configuration 400 for NOMA uplink transmission according to one or more aspects of this disclosure is shown. Resource configuration 400 may include UE 115-d and UE 115-e, which may be as described in relation to Figure 1 An example of UE115 is described. In some cases, to increase capacity, M UEs 115 can simultaneously access the same time-frequency resources (such as...). (Each RE or resource unit), where M can refer to a set of UE 115. As shown in the diagram... Figure 4In this context, M is 2. For transmissions from M UEs on the same time-frequency resources, network entity 105 can use a specific receiver design to separate and identify data from the M UEs 115 as belonging to a specific UE 115. The RV 405 depicted... (i) n can correspond to the RV index n at the UE's identifier i. RV It can indicate the duration of a non-OCC RV duration 407.

[0107] In resource configuration 400, each UE in UE 115 can transmit uplink transmissions on the same time-frequency resources, for example, including a first RV 405-a and a second RV 405-b, up to N RV 405s (e.g., where N is an integer). Transmissions to RV 405 by each UE in UE 115 can be alternately cyclical (e.g., RV 0, RV 2, RV0, RV 2, etc. for each UE in UE 115). In resource configuration 400, the network entity 105 receiving uplink transmissions from UE 115-d and UE 115-e can perform robust scrambling, or it can be associated with a complex receiver design to reduce interference from multiple UE 115s. Thus, in some examples, an OCC-based scheme can be implemented for UE 115s transmitting simultaneously to efficiently transmit data between UE 115 and network entity 105 with reduced interference.

[0108] As will be discussed herein, the OCC scheme can be implemented across OFDM symbols or time slots. Typically, UE 115 (e.g., a transmitter) can receive all data symbols from the modulator output, select the OCC corresponding to UE 115 (e.g., a row of the Hadamard matrix) (which may be indicated in control signaling received from network entity 105), use the OCC to perform M-factor overlay decoding of the symbols, and transmit data configured with the OCC. The network entity can receive the data symbols configured with the OCC, decode the OCC corresponding to UE 115 (e.g., using the corresponding Hadamard matrix), and send the decoded sequence to the demodulator for computation (e.g., log-likelihood ratio (LLR) calculation). OCC can be performed on a symbol-by-symbol or time-slot-by-slot basis (e.g., symbol-by-symbol or time-slot-by-slot).

[0109] Figure 5 An example of resource configuration 500 supporting OCC for multiplexing transmissions performed by multiple UEs, according to one or more aspects of this disclosure, is shown. Resource configuration 500 may include UE 115-f and UE 115-g, which may be as described in relation to Figure 1An example of UE 115 is described. Resource configuration 500 shows the configuration of uplink-permitted resources (e.g., REs) for UE 115-f and UE 115-g.

[0110] In resource configuration 500, UE 115-f can transmit a first RV 505-a and a second RV 505-b, where the first RV 505-a can be an overlaid decoded RV 0 (e.g., RV 505-b). (1) 0), the second RV 505-b can be an overlaid decoded RV 2 (e.g., RV 0). (1) 2). In some examples, RV 505 in the resource configuration can be cycled. Overlay decoding can be based on an orthogonal overlay decoding configuration (e.g., an orthogonal overlay decoding configuration that can be indicated by network entity 105 via control signaling, as described herein, for example regarding...). Figure 2 (As described). The repetition configuration indicated by network entity 105 in the control signaling can indicate the set of RVs 505 (e.g., the number of RVs (e.g., RV0 and RV2)), the number of REs within each RV 505, and the number of repetitions associated with each RV 505 (e.g., how many times each RV 505 is repeated). RVs can be decoded according to the indicated orthogonal overlay decoding configuration, and in some examples, RVs can be decoded in such a way that instead of sending RV0 and RV2 alternately, RV1 can be grouped, and the number of RV1s in the RV1 set is indicated in the control signaling. Therefore, RVs grouped by RV type (e.g., RV1 or RV2) are sent efficiently in groups compared to individually or in a cyclic manner, as will be the case regarding... Figure 7 As discussed, since this configuration is requested from network entity 105 via control signaling in downlink transmission, network entity 105 can quickly and efficiently decode the transport block associated with the received RV 505 based on a known specific configuration indicating the following: the set of RV 505, the number of repetitions associated with each RV 505 in a plurality of RV 505s (e.g., 8 RV1s to be sent and 8 RV2s to be sent subsequently), etc.

[0111] In order to apply OCC in resource configuration 500, the total number of RV 505 for UE 115 will be greater than or equal to twice the number of multiplexed UEs (e.g., N). rep ≥2M, where N rep M is the total number of RVs 505 used for UE 115, and M is the number of multiplexed UE 115s (e.g., UE 115-f and UE 115-g, or 2 UE 115s). When the total number of RVs used for a UE is equal to 2M (e.g., N...), M is the number of multiplexed UE 115s (e.g., N...). repWhen the frequency is 2M, the orthogonal coverage decoding configuration may not involve looping through RV 505. By applying the orthogonal coverage decoding configuration, the uplink capacity at network entity 105 (e.g., base station) can be increased. Specifically, the number of UEs 115 using the same time and frequency resources for uplink transmission increases compared to uplink transmissions without utilizing the orthogonal coverage decoding configuration. Typically, resource configuration 500 may include... The number of REs calculated, N' rep It is N rep Divide by M (e.g., N') rep =N rep / M).

[0112] Typically, when implementing a resource configuration of 500, additional REs are not required. The total number of REs used for non-OCC implementations can include... Each RE (e.g., the total in non-OCC) The total number of REs used for the OCC implementation can include It can be equivalent to It can be equivalent to (For example, the total with OCC) A single OCC RV 505 in resource configuration 500 can be applied across the time period of M non-OCC RV 505s, where a single OCC RV 505 or 1 OCC RV 505 is equivalent to M non-OCC RV 505s. (For example, 1 OCC repetition = M non-OCC repetitions). Thus, the time used to send at least M non-OCC RV 505s (e.g., a group of RV 505s or a set of RV 505s or a "super RV") can be used for OCC. A single OCC RV 505 comprising multiple RV 505s can be referred to as a "super RV," and a super RV 505 can have a transmission duration of MTRV. Where M is the number of UE 115, and T RV This is the time slot duration used for transmitting RV 505. For RV 505 cycles conforming to general standards (such as non-OCC transmissions or OCC uplink transmissions), N' rep It can be greater than or equal to twice the quantity M (e.g., N). rep ≥2M). However, when N' rep Equal to the quantity M (e.g., N) rep When =M), RV loop can be avoided in uplink transmission.

[0113] Compared to non-OCC technologies, OCC technologies can better reduce or eliminate interference (e.g., interference cancellation) due to orthogonal transmission, such as regarding... Figure 9This is discussed in detail. Generally, compared to non-OCC implementations, the configuration of UE115 (e.g., transmitter) and network entity 105 (e.g., receiver or base station) in OCC implementations can be less complex (e.g., more user-friendly). In addition to performing OCC uplink transmissions at the RV 505 level or on an RV basis, OCC transmissions can also be performed at or on a sub-RV level, such as at the resource unit level (RU level or RU basis), time slot unit level (time slot level or time slot basis), or symbol level (symbol level or symbol basis).

[0114] Figure 6 An example of a resource configuration 600 supporting OCC for multiplexing transmissions performed by multiple UEs 115, according to one or more aspects of this disclosure, is shown. In resource configuration 600, UE 115-h and UE 115-i can be as follows: Figure 1 An example of UE 115 is described. Although the following discussion describes data duplication as resource element 605 (RU) (which represents a particular embodiment), the techniques described herein can be applied alternatively or in lieu of other levels of data duplication, such as RV, symbols, or time slots. In some examples, UE 115-h and UE 115-i may each transmit a first resource element 605-a and a second resource element 605-b in a set of resource elements 605 (e.g., a super resource element (super RU)). In some examples, another OCC application may be implemented within the super RU, resulting in the Kronecker product of the elements of the first resource element 605-a in the super RU with an OCC of length M to create a super RU of length M. Resource configuration 600 illustrates the configuration of uplink-permitted resources (e.g., REs) for UE 115-h and UE 115-i.

[0115] In some examples, the format of uplink transmissions (e.g., uplink shared channel (PUSCH) transmissions) can be equal to 1, and the number of resource units N can be N. RU SC It can be equal to 1 (e.g., N) RU SC =1), the number of time slots N slots UL It can be equal to 16 (e.g., N). slots UL =16), and the number of symbols N symb UL It can be equal to 7 (e.g., N). symb UL =7). Δf (which is the frequency) can be equal to 3.75 kHz (e.g., Δf = 3.75 kHz), and the time slot duration T is... slot607 can be equal to 2 milliseconds (ms) (for example, T slot =2ms). A single non-OCC RV (e.g., non-OCC RV) includes N RU There are RUs, therefore the RV set (e.g., 1 super RV) can include MN. RU Resource unit 605 (e.g., one or a single RU) may include a number of time slots and symbols. (N REs), where N RU It can include There are REs, and therefore, MN RU A RU can include One RE.

[0116] Resource unit duration T RU It can include a number of time slots and the duration of the time slots. (For example, A number of resource units 605 and the duration of the resource units (N). RU RU duration) can include a number of resource units, a number of time slots, and time slot duration (e.g., A number of UEs 115, a number of resource elements 605, and a resource element duration may include a number of UEs 115, a number of resource elements 605, a number of time slots, and a resource element time slot duration (e.g., M resource units can be grouped to form large resource unit sets (e.g., super RUs). Thus, a large group of RV sets can include a number of units from the super resource units (e.g., 1 super RV = N). RU (A super RU). This can indicate the resource unit index l at UE i. Typically, and as will be regarding... Figure 8 The grouping discussed can be performed by applying a matrix to the symbols, resource units, or RVs of a time slot.

[0117] Figure 7 An example of resource configuration 700 supporting OCC for multiplexing transmissions performed by multiple UEs 115, according to one or more aspects of this disclosure, is shown. Resource configuration 700 may be performed at the resource unit level or on a per-resource unit basis. Resource configuration 700 may include UEs 115-j and UE 115-k, which may be as described regarding... Figure 1An example of UE 115 is described. Although the following description describes an OCC implementation at the slot level (which represents a particular embodiment), this implementation can be performed at the symbol level or slot level for resource elements or RVs. For example, a slot-level OCC implementation can result in a superslot for each slot, and the superslot can be generated by the Kronecker product of the slot element and the OCC. The superslot can eventually be mapped to a super RV. Each granularity of the RV (e.g., RV, RU, slot, or symbol) can include mapping the corresponding element to the maximum element or super RV (which can be the size of M RVs). Resource configuration 700 illustrates the configuration of uplink-permitted resources (e.g., REs) for UE 115-j and UE 115-k. In some examples, for the OCC implementation, slot-level OCC utilizing rows of a 2x2 Hadamard matrix can be applied to both UE 115s.

[0118] In some examples, resource configuration 700 may include a wireless system with an NPUSCH for communication. In this example, the NPUSCH format may be 1 (e.g., NPUSCH format = 1), and the number of resource units N RU SC It can be 1 (e.g., N) RU SC =1), the number of time slots N slots UL It can be 16 (e.g., N) slots UL =16), the number of symbols can be 7 (e.g., N). symb UL =7), and the frequency can be 3.75kHz (e.g., Δf = 3.75kHz), and the time slot duration T slot It can be 2ms (e.g., T) slot =2ms).

[0119] M time slots can be grouped together to form a set of M resource units or one super resource unit, where 1 resource unit = N. symb UL N slots UL One RE. The duration of one super RU is In the illustrated example, UE 115 is transmitting a timeslot that has been configured with OCC. Specifically, UE 115-j can transmit a first timeslot 705-a and a second timeslot 705-b. The notation for timeslot 705 corresponds to... It includes the time slot index k at UE i. Therefore, both the first time slot 705-a and the second time slot 705-b correspond to the time slot index 1 for UE 115-j (e.g., UE 1 or S). 1 In other words, time slot 705 is grouped into sets by index, so that transmission does not cycle through time slots with different indices.

[0120] A matrix can be used to implement OCC decoding of time slot 705, as shown in the following example. Figure 2 As described herein, and as will be described in this document, the time slots of UE 115-j can be assigned a [1,1] vector of a matrix to the time slot set and index. However, as part of OCC decoding, UE 115-k can be assigned a [1,-1] vector to the time slot sequence. For UE 115-k, the first time slot 705-e and the second time slot 705-f have indices for time slot 0 of UE 115-k (e.g., UE2 or S). 2 The second time slot 705-e is formatted as a negative time slot, in which -1 is applied.

[0121] Figure 8 An example of an encoding configuration 800 for multiplexing transmissions performed by multiple UEs 115, according to one or more aspects of this disclosure, is shown. UEs 115-1 and UEs 115-m can be as follows: Figure 1 An example of UE 115 is described. Encoding configuration 800 can be used to perform overlay decoding on RE / time slot / resource element / RV according to orthogonal overlay decoding configuration to generate orthogonal transmissions for UE 115-l and UE 115-m, as described herein.

[0122] In the encoding configuration, UE 115-l can input data time slot 805-a into Hadamard matrix 810, and UE 115-m can input the second data time slot 805-d into Hadamard matrix 810. Hadamard matrix 810 can be a 2x2 matrix (e.g., two rows and two columns). The first row can correspond to the vector [1,1], and the first row outputs, given data time slot 805-a as input, the product of the third time slot 805-c and the fourth time slot 805-d. The third time slot 805-c and the fourth time slot 805-d can have the same values ​​as the input to the first time slot 805-a, since the vector is [1,1].

[0123] The second row of the matrix can correspond to the vector [1, -1]. Given data time slot 805-b as input, the second row output includes the product of the fifth time slot 805-e and the sixth time slot 805-f. The sixth time slot 805-f is the negative output of the input because a negative integer is applied to this vector in the matrix. Applying the matrix to the input time slots (e.g., or other levels of data such as symbols, resource units, or RVs) in this way produces orthogonal outputs, and accordingly, the transmissions from UE 115-l and UE 115-m are orthogonal and therefore do not interfere with each other. The encoding using Hadamard matrix 810 can be applied to the set of time slots for each UE (e.g., time slots). Wherein, the data time slot is k at UE i). In some examples, each time slot can have 6 data symbols and 1 DMRS, and the number of symbols per time slot can be 7 (e.g., NsymbUL = 7 [1]). The input to the coding matrix can include In some examples involving symbol-level transmissions, the input to the encoding matrix can be symbols, rather than time slots, such as... The data symbol at UE I is j, where j = 0...NsymbUL–2.

[0124] In some examples, such as for four UE 115s, the matrix can be a 4×4 Hadamard matrix with four rows and four columns. Similarly, the OCC implementation for four UE 115s can involve RV sets (e.g., super RVs) or repetition levels, and in some cases, it can involve slot-level implementations. In such an example, the matrix can include a first row vector [1,1,1,1], a second row vector [1,-1,1,-1], a third row vector [1,1,-1,-1], and a fourth row vector [1,-1,-1,1].

[0125] Figure 9 An example of a process flow 900 supporting OCC for multiplexing transmissions performed by multiple UEs 115, according to one or more aspects of this disclosure, is shown. Process flow 900 may involve two or more UEs 115, such as UE 115-n and UE 115-o, which can be as described regarding... Figure 1 An example of UE 115 is described. Process flow 900 may also involve network entity 105-b, which may be as described in relation to Figure 1 An example of network entity 105 described.

[0126] In the following description of process flow 900, operations between network entity 105-a and UE 115-a may be sent in a different order than the example order shown, or operations performed by network entity 105-a and UE 115-a may be performed in a different order or at different times. Some operations may also be omitted from process flow 900, while others may be added to process flow 900.

[0127] At 905, UE 115 can receive control signaling from network entity 105-b. This control signaling indicates the permitted multiplexing order, repeatability configuration, and orthogonal coverage decoding configuration to be applied to the uplink. The repeatability configuration indicates the RV set, the first number of resource elements associated with each repeat of each redundant version in the redundant version set, and the number of repeats associated with each redundant version in the redundant version set. The orthogonal coverage decoding configuration is based on the multiplexing order.

[0128] At 910, UE 115 can generate a transport block that includes one or more instances of a redundant version set, the instances of which are mapped to a set of resource elements of the transport block across time based on the multiplexing order and orthogonal overlay decoding configuration. For example, the duration of a super RV (e.g., the number of REs associated with each instance of each RV in the transport block) is equal to the duration of a normal RV (e.g., the number of REs in each RV in a duplicated configuration) multiplied by the multiplexing order.

[0129] At 915, UE 115 can send an uplink transmission, including a set of transport blocks, to network entity 105-b based on uplink permission.

[0130] In some examples, UE 115 can also receive from network entity 105-b an indication of the association of a set of resource elements with an uplink permission, and UE 115 can map each instance of each redundant version in the redundant version set to a subset of resource elements in the resource element set. The number of resource elements in each subset can be equal to a first number (of resource elements associated with each duplicate of each redundant version in the redundant version set) multiplied by the multiplexing order. In some examples, UE 115-n can receive from network entity 105-b a second uplink permission associated with a second set of resource elements, wherein the second set of resource elements includes the same number of resource elements as the resource element set, and the second multiplexing order associated with the second uplink permission is one. UE 115-n can generate a second transport block according to the duplicate configuration, and can send a second uplink transmission including the second transport block to network entity 105-b according to the second uplink permission, wherein the first data capacity of the transport block is equal to the second data capacity of the second transport block.

[0131] In some examples, generating a transport block may include: generating a set of redundant versions from a data buffer; mapping repeated sets of the redundant version set to corresponding consecutive subsets of resource elements in a resource element set over time, wherein the number of repetitions in each repeated set of repeated sets is based on the multiplexing order; and applying an orthogonal overlay decoding configuration to the repeated sets of the corresponding consecutive subsets of resource elements over time to generate the transport block. In some examples, the OCC configuration may be applied on a per-symbol, per-slot, per-resource-unit, or per-redundancy-version basis.

[0132] In some examples, receive control signaling may include instructions for orthogonal overlay decoding configurations that include rows or columns associated with a Hadamard matrix or DFT matrix, and the control signaling may indicate which rows or columns of the Hadamard matrix or DFT matrix are associated with UE 115. In some examples, the control signaling may indicate which rows or columns of the Hadamard matrix or DFT matrix are associated with UE 115 (e.g., which rows or columns of the matrix should be applied to orthogonal overlay decoding for a given UE 115). The size of the Hadamard matrix or DFT matrix may be associated with the multiplexing order. For example, the Hadamard matrix may be as large as the multiplexing order. Thus, a 2-row matrix can be used for multiplexing 2 UEs 115, a 4-row matrix can be used for multiplexing 4 UEs, and so on.

[0133] In some examples, receiving control signaling includes receiving a first control message indicating duplicate configuration and a second control message indicating uplink permission, multiplexing order, and orthogonal coverage decoding configuration. In some examples, the total number of duplicates may be at least twice the multiplexing order, and the total number of duplicates may be the number of duplicates associated with each RV multiplied by the number of RVs in the RV set. In some examples, network entity 105-b may be a non-terrestrial network entity. In some examples, control signaling may be received via RRC or MAC-CE or a combination thereof (e.g., duplicate configuration may be indicated via RRC, and uplink permission, multiplexing order, and orthogonal coverage decoding configuration may be indicated via MAC-CE).

[0134] Figure 10 A block diagram 1000 of an apparatus 1005 supporting orthogonal overlay codes for multiplexing transmissions performed by multiple UEs 115, according to one or more aspects of this disclosure, is shown. Apparatus 1005 may be an example of various aspects of UE 115 as described herein. Apparatus 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. Apparatus 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0135] Receiver 1010 may provide a unit for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, and information channels related to OCC used for multiplexing transmissions performed by multiple UEs). The information may be transmitted to other components of device 1005. Receiver 1010 may utilize a single antenna or a collection of multiple antennas.

[0136] Transmitter 1015 may provide a unit for transmitting signals generated by other components of device 1005. For example, transmitter 1015 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to OCC used for multiplexing transmissions performed by multiple UEs). In some examples, transmitter 1015 may be co-located with receiver 1010 in a transceiver module. Transmitter 1015 may utilize a single antenna or a collection of multiple antennas.

[0137] The communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof, or various components thereof, may be examples of units for performing various aspects of an OCC for multiplexing transmissions performed by multiple UEs as described herein. For example, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0138] In some examples, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic, discrete hardware component, or any combination thereof configured to or otherwise support a unit for performing the functions described herein. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in memory by the processor).

[0139] Alternatively or concurrently, in some examples, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof, may be implemented using code executed by a processor (e.g., as communication management software or firmware). If implemented using processor-executed code, the functionality of the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., units configured or otherwise supported for performing the functions described in this disclosure).

[0140] In some examples, the communication manager 1020 may be configured to use or otherwise cooperate with receiver 1010, transmitter 1015, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1020 may receive information from receiver 1010, send information to transmitter 1015, or integrate with receiver 1010, transmitter 1015, or a combination thereof to acquire information, output information, or perform various other operations as described herein.

[0141] According to the examples disclosed herein, the communication manager 1020 can support wireless communication at the UE. For example, the communication manager 1020 can be configured or otherwise supported to support elements for receiving control signaling from a network entity indicating multiplexing order, repeat configuration, and orthogonal coverage decoding configuration to be applied to uplink permission, wherein the repeat configuration indicates a set of RVs, a first number of REs associated with each repeat of each RV in the RV set, and a number of repeats associated with each RV in the RV set, and wherein the orthogonal coverage decoding configuration is based on the multiplexing order. The communication manager 1020 can be configured or otherwise supported to support elements for generating transport blocks comprising one or more instances of an RV set, the one or more instances of the RV set being mapped to a set of REs of the transport block across time based on the multiplexing order and orthogonal coverage decoding configuration. The communication manager 1020 can be configured or otherwise supported to support elements for transmitting uplink transmissions comprising transport blocks to a network entity according to uplink permission.

[0142] By including or configuring the communication manager 1020 according to the examples described herein, device 1005 (e.g., a processor that controls or is otherwise coupled to receiver 1010, transmitter 1015, communication manager 1020, or a combination thereof) can support techniques for increasing uplink capacity while reducing interference from simultaneous transmissions from UE 115. Specifically, uplink capacity at network entity 105 can be increased by applying an orthogonal coverage decoding configuration. The number of UEs 115 using the same time and frequency resources for uplink transmissions increases compared to uplink transmissions without utilizing the orthogonal coverage decoding configuration. Furthermore, data from different UEs 115 can be efficiently decoded to identify the corresponding UE 115 that is transmitting simultaneously.

[0143] Figure 11 A block diagram 1100 of an apparatus 1105 supporting OCC for multiplexing transmissions performed by multiple UEs 115, according to one or more aspects of this disclosure, is shown. Apparatus 1105 may be an example of apparatus 1005 as described herein or of various aspects of UE 115. Apparatus 1105 may include a receiver 1110, a transmitter 1115, and a communications manager 1120. Apparatus 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0144] Receiver 1110 may provide a unit for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, and information channels associated with OCC used for multiplexing transmissions performed by multiple UEs). The information may be passed to other components of device 1105. Receiver 1110 may utilize a single antenna or a collection of multiple antennas.

[0145] Transmitter 1115 may provide a unit for transmitting signals generated by other components of device 1105. For example, transmitter 1115 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with OCC used for multiplexing transmissions performed by multiple UEs). In some examples, transmitter 1115 may be co-located with receiver 1110 in a transceiver module. Transmitter 1115 may utilize a single antenna or a collection of multiple antennas.

[0146] Device 1105 or its various components may be examples of units for performing aspects of OCC for multiplexing transmissions performed by multiple UEs as described herein. For example, communication manager 1120 may include control signal receiving manager 1125, transport block manager 1130, uplink transport manager 1135, or any combination thereof. Communication manager 1120 may be examples of aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to use receiver 1110, transmitter 1115, or both, or otherwise cooperate with receiver 1110, transmitter 1115, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1120 may receive information from receiver 1110, send information to transmitter 1115, or integrate with receiver 1110, transmitter 1115, or a combination thereof to acquire information, output information, or perform various other operations as described herein.

[0147] According to the examples disclosed herein, the communication manager 1120 can support wireless communication at the UE. The control signal receiving manager 1125 can be configured or otherwise supported to receive from a network entity control signaling indicating the multiplexing order, repeat configuration, and orthogonal coverage decoding configuration to be applied to uplink permission, wherein the repeat configuration indicates a set of RVs, a first number of REs associated with each repeat of each RV in the RV set, and a number of repeats associated with each RV in the RV set, and wherein the orthogonal coverage decoding configuration is based on the multiplexing order. The transport block manager 1130 can be configured or otherwise supported to generate transport blocks comprising one or more instances of an RV set, the one or more instances of the RV set being mapped to a set of REs of the transport block across time based on the multiplexing order and orthogonal coverage decoding configuration. The uplink transport manager 1135 can be configured or otherwise supported to transmit uplink transports comprising transport blocks to a network entity according to uplink permission.

[0148] Figure 12A block diagram 1200 is shown of a communication manager 1220 supporting OCC for multiplexing transmissions performed by multiple UEs 115, according to one or more aspects of this disclosure. The communication manager 1220 may be an example of aspects of the communication manager 1020, communication manager 1120, or both as described herein. The communication manager 1220 or its various components may be examples of units for performing aspects of OCC for multiplexing transmissions performed by multiple UEs, as described herein. For example, the communication manager 1220 may include a control signal receiving manager 1225, a transport block manager 1230, an uplink transport manager 1235, an RE indication manager 1240, an RV mapping manager 1245, a data buffer manager 1250, an OCC manager 1255, an OCC matrix manager 1260, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0149] According to the examples disclosed herein, the communication manager 1220 can support wireless communication at the UE. The control signal receiving manager 1225 can be configured or otherwise supported to receive from a network entity control signaling indicating the multiplexing order, repeat configuration, and orthogonal coverage decoding configuration to be applied to uplink permission, wherein the repeat configuration indicates a set of RVs, a first number of REs associated with each repeat of each RV in the RV set, and a number of repeats associated with each RV in the RV set, and wherein the orthogonal coverage decoding configuration is based on the multiplexing order. The transport block manager 1230 can be configured or otherwise supported to generate transport blocks comprising one or more instances of an RV set, the one or more instances of the RV set being mapped to a set of REs of the transport block across time based on the multiplexing order and orthogonal coverage decoding configuration. The uplink transport manager 1235 can be configured or otherwise supported to transmit uplink transports comprising transport blocks to a network entity according to uplink permission.

[0150] In some examples, the RE indication manager 1240 may be configured or otherwise supported to include units for receiving indications from network entities regarding the association of an RE set with uplink grants. Specifically, uplink grants may be scheduled within a time-frequency RE set. In some examples, the RV mapping manager 1245 may be configured or otherwise supported to include units for mapping each instance of each RV in the RV set to a subset of REs in the RE set, wherein a second number of REs in each subset is a first number multiplied by the multiplexing order.

[0151] In some examples, the control signal receiving manager 1225 may be configured or otherwise supported to receive from a network entity a second uplink permission associated with a second set of REs, wherein the second set of REs comprises the same number of REs as the set of REs, and wherein the second multiplexing order associated with the second uplink permission is one. In some examples, the transport block manager 1230 may be configured or otherwise supported to generate a second transport block according to a repeating configuration. In some examples, the uplink transport manager 1235 may be configured or otherwise supported to send a second uplink transmission including a second transport block to a network entity according to a second uplink permission, wherein the first data capacity of the transport block is equal to the second data capacity of the second transport block.

[0152] In some examples, to support the generation of transport blocks, the data buffer manager 1250 may be configured or otherwise supported to support units for generating RV sets from the data buffer. In some examples, to support the generation of transport blocks, the RV mapping manager 1245 may be configured or otherwise supported to support units for mapping repeating sets of the RV set to corresponding consecutive RE subsets in the RE set across time, wherein the number of repetitions in each repeating set is based on the multiplexing order. In some examples, to support the generation of transport blocks, the OCC manager 1255 may be configured or otherwise supported to support units for applying orthogonal overlay decoding configuration to the time-crossing mapping of the RV set to repeating sets of corresponding consecutive RE subsets to generate transport blocks.

[0153] In some examples, to support the application of orthogonal overlay decoding configurations, the OCC manager 1255 can be configured or otherwise support cells for applying orthogonal overlay decoding configurations on a per-symbol, per-slot, per-resource-cell, or per-RV basis.

[0154] In some examples, to support receiving control signaling, the OCC matrix manager 1260 can be configured or otherwise support units for receiving control signaling that indicates the orthogonal overlay decoding configuration includes rows or columns associated with a Hadamard matrix or a discrete Fourier transform matrix, wherein the control signaling indicates which rows or columns of the Hadamard matrix or discrete Fourier transform matrix are associated with the UE.

[0155] In some examples, the size of the Hadamard matrix or discrete Fourier transform matrix is ​​associated with the multiplexing order.

[0156] In some examples, to support receiving control signaling, the control signal receiving manager 1225 may be configured or otherwise supported as a unit for receiving a first control message indicating a repeat configuration. In some examples, to support receiving control signaling, the control signal receiving manager 1225 may be configured or otherwise supported as a unit for receiving a second control message indicating uplink permission, multiplexing order, and orthogonal overlay decoding configuration.

[0157] In some examples, the total number of repetitions is at least twice the reuse order, and the total number of repetitions is the number of repetitions associated with each RV multiplied by the number of RVs in the RV set.

[0158] In some examples, network entities are non-terrestrial network entities.

[0159] In some examples, to support the reception of control signaling, the control signal reception manager 1225 can be configured or otherwise support units for receiving control signaling via RRC signaling, MAC control element (MAC-CE), or a combination thereof.

[0160] Figure 13 A schematic diagram of a system 1300 including a device 1305 supporting an OCC for multiplexing transmissions performed by multiple UEs 115, according to one or more aspects of this disclosure, is shown. Device 1305 may be an example of device 1005, device 1105, or UE 115 as described herein, or may include components thereof. Device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 1305 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1320, an input / output (I / O) controller 1310, a transceiver 1315, an antenna 1325, a memory 1330, a code 1335, and a processor 1340. These components may communicate electronically or be otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1345).

[0161] I / O controller 1310 can manage input and output signals for device 1305. I / O controller 1310 can also manage peripheral devices not integrated into device 1305. In some cases, I / O controller 1310 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1310 can utilize, for example... This can be an operating system such as I / O controller 1310 or another known operating system. Alternatively, I / O controller 1310 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, I / O controller 1310 may be implemented as part of a processor (such as processor 1340). In some cases, a user may interact with device 1305 via I / O controller 1310 or via hardware components controlled by I / O controller 1310.

[0162] In some cases, device 1305 may include a single antenna 1325. However, in other cases, device 1305 may have more than one antenna 1325, which are capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1315 may communicate bidirectionally via one or more antennas 1325, wired or wireless links as described herein. For example, transceiver 1315 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1315 may also include a modem for modulating packets, providing modulated packets to one or more antennas 1325 for transmission, and demodulating packets received from one or more antennas 1325. Transceiver 1315, or transceiver 1315 and one or more antennas 1325, may be an example of transmitter 1015, transmitter 1115, receiver 1010, receiver 1110, or any combination thereof or components thereof as described herein.

[0163] Memory 1330 may include random access memory (RAM) and read-only memory (ROM). Memory 1330 may store computer-readable, computer-executable code 1335, which includes instructions that, when executed by processor 1340, cause device 1305 to perform the various functions described herein. Code 1335 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1335 may not be directly executable by processor 1340, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some additional cases, memory 1330 may also contain a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0164] Processor 1340 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1340 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1340. Processor 1340 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1330) to cause device 1305 to perform various functions (e.g., functions or tasks supporting OCC for multiplexing transmissions performed by multiple UEs). For example, device 1305 or components of device 1305 may include processor 1340 and memory 1330 coupled to or coupled to processor 1340, processor 1340 and memory 1330 being configured to perform the various functions described herein.

[0165] According to the examples disclosed herein, the communication manager 1320 can support wireless communication at the UE. For example, the communication manager 1320 can be configured or otherwise supported to support elements for receiving control signaling from a network entity indicating a multiplexing order, repeat configuration, and orthogonal coverage decoding configuration to be applied to uplink permission, wherein the repeat configuration indicates a set of RVs, a first number of REs associated with each repeat of each RV in the RV set, and a number of repeats associated with each RV in the RV set, and wherein the orthogonal coverage decoding configuration is based on the multiplexing order. The communication manager 1320 can be configured or otherwise supported to support elements for generating transport blocks comprising one or more instances of an RV set, the one or more instances of the RV set being mapped to a set of REs of the transport block across time based on the multiplexing order and orthogonal coverage decoding configuration. The communication manager 1320 can be configured or otherwise supported to support elements for transmitting uplink transmissions comprising transport blocks to a network entity according to uplink permission.

[0166] By including or configuring the communication manager 1320 according to the examples described herein, device 1305 can support techniques for increasing uplink capacity while reducing interference caused by simultaneous transmissions from UE 115. Specifically, uplink capacity at network entity 105 can be increased by applying orthogonal coverage decoding configuration. The number of UEs 115 using the same time and frequency resources for uplink transmissions increases compared to uplink transmissions without orthogonal coverage decoding configuration. Furthermore, data from different UEs 115 can be efficiently decoded to identify the corresponding UE 1150 that is transmitting simultaneously.

[0167] In some examples, the communication manager 1320 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in cooperation with transceiver 1315, one or more antennas 1325, or any combination thereof. Although the communication manager 1320 is shown as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by processor 1340, memory 1330, code 1335, or any combination thereof. For example, code 1335 may include instructions executable by processor 1340 to cause device 1305 to perform aspects of the OCC for multiplexing transmissions performed by multiple UEs as described herein, or processor 1340 and memory 1330 may be otherwise configured to perform or support such operations.

[0168] Figure 14 A block diagram 1400 of an apparatus 1405 supporting OCC for multiplexing transmissions performed by multiple UEs 115, according to one or more aspects of this disclosure, is shown. Apparatus 1405 may be an example of aspects of network entity 105 as described herein. Apparatus 1405 may include a receiver 1410, a transmitter 1415, and a communications manager 1420. Apparatus 1405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0169] Receiver 1410 may provide units for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q sampling, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1405. In some examples, receiver 1410 may support acquiring information by receiving signals via one or more antennas. Alternatively or concurrently, receiver 1410 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0170] Transmitter 1415 may provide a unit for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1405. For example, transmitter 1415 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q sampling, symbols, packets, protocol data units, service data units). In some examples, transmitter 1415 may support outputting information by transmitting signals via one or more antennas. Alternatively or concurrently, transmitter 1415 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1415 and receiver 1410 may be co-located in a transceiver, which may include or be coupled to a modem.

[0171] Communication manager 1420, receiver 1410, transmitter 1415, or various combinations thereof, or various components thereof, may be examples of units for performing various aspects of multiplexing transmissions performed by multiple UEs as described herein. For example, communication manager 1420, receiver 1410, transmitter 1415, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0172] In some examples, the communication manager 1420, receiver 1410, transmitter 1415, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include processors, DSPs, CPUs, ASICs, FPGAs or other programmable logic devices, microcontrollers, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured to or otherwise support units for performing the functions described herein. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in memory by the processor).

[0173] Alternatively or concurrently, in some examples, the communication manager 1420, receiver 1410, transmitter 1415, or various combinations or components thereof, may be implemented using code executed by a processor (e.g., as communication management software or firmware). If implemented using processor-executed code, the functionality of the communication manager 1420, receiver 1410, transmitter 1415, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., units configured or otherwise supported for performing the functions described in this disclosure).

[0174] In some examples, the communication manager 1420 may be configured to use or otherwise cooperate with the receiver 1410, transmitter 1415, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1420 may receive information from the receiver 1410, send information to the transmitter 1415, or integrate with the receiver 1410, transmitter 1415, or a combination thereof to acquire information, output information, or perform various other operations as described herein.

[0175] According to the examples disclosed herein, the communication manager 1420 can support wireless communication at a network entity. For example, the communication manager 1420 can be configured or otherwise supported for sending control signaling to a set of UEs, the control signaling indicating a multiplexing order, repeat configuration, and corresponding orthogonal coverage decoding configuration to be applied to a corresponding uplink permission for the set of UEs, wherein the repeat configuration indicates a set of RVs, a first number of REs associated with each repeat of each RV in the RV set, and a number of repeats associated with each RV in the RV set, and wherein the corresponding orthogonal coverage decoding configuration is based on the multiplexing order. The communication manager 1420 can be configured or otherwise supported for receiving from the set of UEs a multiplexed set of uplink transports including a corresponding transport block encoded using the corresponding orthogonal coverage decoding configuration, wherein the corresponding transport block includes one or more corresponding instances of a corresponding RV set, the corresponding one or more instances of the corresponding RV set being mapped to a set of REs associated with the corresponding uplink permission based on the multiplexing order and the corresponding orthogonal coverage decoding configuration. The communication manager 1420 can be configured or otherwise support units for decoding corresponding transport blocks based on the corresponding orthogonal overlay decoding configuration associated with the UE set.

[0176] By including or configuring the communication manager 1420 according to the examples described herein, device 1405 (e.g., a processor that controls or is otherwise coupled to receiver 1410, transmitter 1415, communication manager 1420, or a combination thereof) can support techniques for increasing uplink capacity while reducing interference due to simultaneous transmissions from UE 115. Specifically, uplink capacity at network entity 105 can be increased by applying an orthogonal coverage decoding configuration. The number of UEs 115 using the same time and frequency resources for uplink transmissions increases compared to uplink transmissions without utilizing the orthogonal coverage decoding configuration. Furthermore, data from different UEs 115 can be efficiently decoded to identify the corresponding UE 115 transmitting simultaneously.

[0177] Figure 15A block diagram 1500 of an apparatus 1505 supporting OCC for multiplexing transmissions performed by multiple UEs 115, according to one or more aspects of this disclosure, is shown. Apparatus 1505 may be an example of aspects of apparatus 1405 or network entity 105 as described herein. Apparatus 1505 may include a receiver 1510, a transmitter 1515, and a communications manager 1520. Apparatus 1505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0178] Receiver 1510 may provide units for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q sampling, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1505. In some examples, receiver 1510 may support acquiring information by receiving signals via one or more antennas. Alternatively, receiver 1510 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0179] Transmitter 1515 may provide a unit for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1505. For example, transmitter 1515 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q sampling, symbols, packets, protocol data units, service data units). In some examples, transmitter 1515 may support outputting information by transmitting signals via one or more antennas. Alternatively or concurrently, transmitter 1515 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1515 and receiver 1510 may be co-located in a transceiver, which may include or be coupled to a modem.

[0180] Device 1505 or its various components may be examples of units for performing aspects of OCC for multiplexing transmissions performed by multiple UEs as described herein. For example, communication manager 1520 may include control signal transmission manager 1525, uplink receive manager 1530, decoding manager 1535, or any combination thereof. Communication manager 1520 may be examples of aspects of communication manager 1420 as described herein. In some examples, communication manager 1520 or its various components may be configured to use receiver 1510, transmitter 1515, or both, or otherwise cooperate with receiver 1510, transmitter 1515, or both to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, communication manager 1520 may receive information from receiver 1510, send information to transmitter 1515, or integrate with receiver 1510, transmitter 1515, or a combination thereof to acquire information, output information, or perform various other operations as described herein.

[0181] According to the examples disclosed herein, the communication manager 1520 can support wireless communication at a network entity. The control signal transmission manager 1525 can be configured or otherwise supported for sending control signaling to a set of UEs, the control signaling indicating the multiplexing order, repetition configuration, and corresponding orthogonal coverage decoding configuration to be applied to a corresponding uplink permission for the set of UEs, wherein the repetition configuration indicates a set of RVs, a first number of REs associated with each repetition of each RV in the RV set, and a number of repetitions associated with each RV in the RV set, and wherein the corresponding orthogonal coverage decoding configuration is based on the multiplexing order. The uplink receive manager 1530 can be configured or otherwise supported for receiving from the set of UEs a multiplexed set of uplink transmissions including a corresponding transport block encoded using the corresponding orthogonal coverage decoding configuration, wherein the corresponding transport block includes one or more corresponding instances of a corresponding RV set, the corresponding one or more instances of the corresponding RV set being mapped to a set of REs associated with the corresponding uplink permission based on the multiplexing order and the corresponding orthogonal coverage decoding configuration. The decoding manager 1535 can be configured or otherwise support units for decoding corresponding transport blocks based on the corresponding orthogonal overlay decoding configuration associated with the UE set.

[0182] Figure 16A block diagram 1600 is shown of a communication manager 1620 supporting OCC for multiplexing transmissions performed by multiple UEs 115, according to one or more aspects of this disclosure. The communication manager 1620 may be an example of aspects of the communication manager 1420, communication manager 1520, or both as described herein. The communication manager 1620 or its various components may be examples of units for performing aspects of OCC for multiplexing transmissions performed by multiple UEs, as described herein. For example, the communication manager 1620 may include a control signal transmission manager 1625, an uplink receive manager 1630, a decoding manager 1635, an RE indication manager 1640, an OCC matrix manager 1645, an uplink permission manager 1655, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which may include communication within the protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components or virtualization components associated with network entity 105, between devices, components or virtualization components associated with network entity 105), or any combination thereof.

[0183] According to the examples disclosed herein, the communication manager 1620 can support wireless communication at a network entity. The control signal transmission manager 1625 can be configured or otherwise supported for sending control signaling to a set of UEs, the control signaling indicating the multiplexing order, repetition configuration, and corresponding orthogonal coverage decoding configuration to be applied to a corresponding uplink permission for the set of UEs, wherein the repetition configuration indicates a set of RVs, a first number of REs associated with each repetition of each RV in the RV set, and a number of repetitions associated with each RV in the RV set, and wherein the corresponding orthogonal coverage decoding configuration is based on the multiplexing order. The uplink receive manager 1630 can be configured or otherwise supported for receiving from the set of UEs a multiplexed set of uplink transmissions including a corresponding transport block encoded using the corresponding orthogonal coverage decoding configuration, wherein the corresponding transport block includes one or more corresponding instances of a corresponding RV set, the corresponding one or more instances of the corresponding RV set being mapped to a set of REs associated with the corresponding uplink permission based on the multiplexing order and the corresponding orthogonal coverage decoding configuration. The decoding manager 1635 can be configured or otherwise support units for decoding corresponding transport blocks based on the corresponding orthogonal overlay decoding configuration associated with the UE set.

[0184] In some examples, the RE indication manager 1640 may be configured or otherwise supported to send an indication to a set of UEs for a set of REs associated with a corresponding uplink permission, wherein the multiplexed uplink transmission set is received via the RE set.

[0185] In some examples, the uplink grant manager 1655 may be configured or otherwise supported to transmit a second uplink grant associated with a second set of REs to UEs in a set of UEs, wherein the second set of REs includes the same number of REs as the set of REs, and wherein the second multiplexing order associated with the second uplink grant is one. In some examples, the uplink receive manager 1630 may be configured or otherwise supported to receive a second uplink transmission including a second transport block from a UE based on the second uplink grant, wherein the first data capacity of the corresponding transport block associated with the UE is equal to the second data capacity of the second transport block.

[0186] In some examples, in order to support decoding of corresponding transport blocks based on the corresponding orthogonal overlay decoding configuration associated with the UE set, the decoding manager 1635 may be configured or otherwise support units for decoding corresponding transport blocks based on the corresponding orthogonal overlay decoding configuration on a per-symbol, per-slot, per-resource-element, or per-RV basis.

[0187] In some examples, to support the transmission of control signaling, the OCC matrix manager 1645 can be configured or otherwise supported to support units for transmitting control signaling that indicates the corresponding orthogonal overlay decoding configuration includes rows or columns associated with the Hadamard matrix or discrete Fourier transform matrix, and wherein the control signaling indicates which rows or columns of the Hadamard matrix or discrete Fourier transform matrix are associated with each UE in the UE set.

[0188] In some examples, the size of the Hadamard matrix or discrete Fourier transform matrix is ​​associated with the multiplexing order.

[0189] In some examples, to support the transmission of control signaling, the control signaling transmission manager 1625 may be configured or otherwise supported as a unit for transmitting a first control message indicating a repeating configuration. In some examples, to support the transmission of control signaling, the control signaling transmission manager 1625 may be configured or otherwise supported as a unit for transmitting a corresponding second control message to the UE set indicating the corresponding uplink permission, multiplexing order, and corresponding orthogonal coverage decoding configuration.

[0190] In some examples, the total number of repetitions is at least twice the reuse order, and the total number of repetitions is the number of repetitions associated with each RV multiplied by the number of RVs in the RV set.

[0191] In some examples, network entities are non-terrestrial network entities.

[0192] In some examples, to support the transmission of control signaling, the control signaling transmission manager 1625 can be configured or otherwise support units for transmitting control signaling via RRC signaling, Media Access Control MAC-CE, or a combination thereof.

[0193] Figure 17 A schematic diagram of a system 1700 including a device 1705 supporting an OCC for multiplexing transmissions performed by multiple UEs 115, according to one or more aspects of this disclosure, is shown. Device 1705 may be an example of device 1405, device 1505, or network entity 105 as described herein, or include components thereof. Device 1705 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1705 may include components supporting output and acquisition of communication, such as a communication manager 1720, a transceiver 1710, an antenna 1715, a memory 1725, a code 1730, and a processor 1735. These components may communicate electronically via one or more buses (e.g., bus 1740) or be otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0194] Transceiver 1710 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1710 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Alternatively, in some examples, transceiver 1710 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, device 1705 may include one or more antennas 1715, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). Transceiver 1710 may also include a modem for modulating signals, providing modulated signals for transmission (e.g., via one or more antennas 1715, via a wired transmitter), receiving modulated signals (e.g., from one or more antennas 1715, from a wired receiver), and demodulating signals. In some implementations, transceiver 1710 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1715 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1715 configured to support various transmit or output operations, or combinations thereof. In some implementations, transceiver 1710 may include one or more processor or memory components or be configured to couple to one or more processor or memory components operable to perform or support operations based on received or acquired information or signals, or generate information or other signals for transmission or other output, or any combination thereof. In some implementations, transceiver 1710, or transceiver 1710 and one or more antennas 1715, or transceiver 1710 and one or more antennas 1715 and one or more processor or memory components (e.g., processor 1735, or memory 1725, or both) may be included in a chip or chip assembly mounted in device 1705. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and forward communication link 168).

[0195] Memory 1725 may include RAM and ROM. Memory 1725 may store computer-readable, computer-executable code 1730, which includes instructions that, when executed by processor 1735, cause device 1705 to perform the various functions described herein. Code 1730 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1730 may not be directly executable by processor 1735, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, in addition, memory 1725 may also contain a BIOS that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0196] Processor 1735 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, processor 1735 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1735. Processor 1735 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1725) to cause device 1705 to perform various functions (e.g., functions or tasks supporting OCC for multiplexing transmissions performed by multiple UEs). For example, device 1705 or components of device 1705 may include processor 1735 and memory 1725 coupled to processor 1735, processor 1735 and memory 1725 being configured to perform the various functions described herein. Processor 1735 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software, such as an operating system, virtual machine, or container instance) that can host functions (e.g., by executing code 1730) to perform the functions of device 1705. Processor 1735 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1705 (such as in memory 1725). In some implementations, processor 1735 may be a component of a processing system. A processing system can generally refer to a system that receives input and processes input to produce a set of outputs, or a series of machines or components (the set of outputs may be passed to other systems or, for example, components of device 1705). For example, the processing system of device 1705 may refer to a system that includes various other components or sub-components of device 1705 (such as processor 1735, or transceiver 1710, or communication manager 1720, or other components or combinations of components of device 1705). The processing system of device 1705 can interface with other components of device 1705 and can process information (such as inputs or signals) received from other components or output information to other components. For example, the chip or modem of device 1705 may include a processing system and one or more interfaces for outputting information or receiving information, or both. The one or more interfaces may be implemented or otherwise include a first interface configured to output information and a second interface configured to receive information, or the same interface configured to output and receive information, and other implementations. In some implementations, the one or more interfaces may refer to the interface between the processing system of the chip or modem and the transmitter, enabling device 1705 to transmit information output from the chip or modem.Alternatively, in some implementations, one or more interfaces may refer to the interface between the processing system of the chip or modem and the receiver, enabling device 1705 to receive information or signal input, and the information can be transmitted to the processing system. Those skilled in the art will readily recognize that the first interface can also receive information or signal input, and the second interface can also output information or signal output.

[0197] In some examples, bus 1740 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1740 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1705 or communication between different components of device 1705 that may be co-located or located in different locations (e.g., where device 1705 may refer to a system in which one or more of communication manager 1720, transceiver 1710, memory 1725, code 1730, and processor 1735 may be located in one of different components or partitioned between different components).

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

[0199] According to the examples disclosed herein, the communication manager 1720 can support wireless communication at a network entity. For example, the communication manager 1720 can be configured or otherwise supported for sending control signaling to a set of UEs, the control signaling indicating a multiplexing order, repeat configuration, and corresponding orthogonal coverage decoding configuration to be applied to a corresponding uplink permission for the set of UEs, wherein the repeat configuration indicates a set of RVs, a first number of REs associated with each repeat of each RV in the RV set, and a number of repeats associated with each RV in the RV set, and wherein the corresponding orthogonal coverage decoding configuration is based on the multiplexing order. The communication manager 1720 can be configured or otherwise supported for receiving from the set of UEs a multiplexed set of uplink transports including a corresponding transport block encoded using the corresponding orthogonal coverage decoding configuration, wherein the corresponding transport block includes one or more corresponding instances of a corresponding RV set, the corresponding one or more instances of the corresponding RV set being mapped to a set of REs associated with the corresponding uplink permission based on the multiplexing order and the corresponding orthogonal coverage decoding configuration. The communication manager 1720 can be configured or otherwise support units for decoding corresponding transport blocks based on the corresponding orthogonal overlay decoding configuration associated with the UE set.

[0200] By including or configuring the communication manager 1720 according to the examples described herein, device 1705 can support techniques for increasing uplink capacity while reducing interference caused by simultaneous transmissions from UE 115. Specifically, uplink capacity at network entity 105 can be increased by applying orthogonal coverage decoding configuration. The number of UEs 115 using the same time and frequency resources for uplink transmissions increases compared to uplink transmissions without orthogonal coverage decoding configuration. Furthermore, data from different UEs 115 can be efficiently decoded to identify the corresponding UE 1150 transmitting simultaneously.

[0201] In some examples, the communication manager 1720 may be configured to perform various operations (e.g., receive, acquire, monitor, output, transmit) in cooperation with or in conjunction with transceiver 1710, one or more antennas 1715 (e.g., where applicable), or any combination thereof. Although the communication manager 1720 is shown as a separate component, in some examples, one or more functions described with reference to the communication manager 1720 may be supported by or performed by transceiver 1710, processor 1735, memory 1725, code 1730, or any combination thereof. For example, code 1730 may include instructions executable by processor 1735 to cause device 1705 to perform aspects of the OCC for multiplexing transmissions performed by multiple UEs as described herein, or processor 1735 and memory 1725 may be otherwise configured to perform or support such operations.

[0202] Figure 18 A flowchart illustrating a method 1800 for multiplexing OCC transmissions performed by multiple UEs 115, according to one or more aspects of this disclosure, is shown. Operation of method 1800 can be implemented by a UE or its components as described herein. For example, operation of method 1800 can be implemented by, as referred to... Figures 1 to 13 The UE 115 described herein is used to perform this function. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described function. Alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0203] At 1805, the method may include: receiving from a network entity control signaling indicating a multiplexing order, repeat configuration, and orthogonal overlay decoding configuration to be applied to the uplink permission, wherein the repeat configuration indicates a set of RVs, a first number of REs associated with each repeat of each RV in the RV set, and a number of repeats associated with each RV in the RV set, and wherein the orthogonal overlay decoding configuration is based on the multiplexing order. The operation of 1805 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1805 may be determined by reference to... Figure 12 The control signal receiving manager 1225 described herein is used to perform this action.

[0204] At 1810, the method may include: generating a transport block comprising one or more instances of a set of RVs, the instances of which are mapped to a set of REs of the transport block across time based on the multiplexing order and orthogonal overlay decoding configuration. Specifically, the duration of a super RV (e.g., the number of REs associated with each instance of an RV in the transport block) may be equal to the duration of an RV indicated in a repeating configuration (e.g., the number of REs in each RV in the repeating configuration) multiplied by the multiplexing order. The operation of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1810 may be provided by reference to [reference needed]. Figure 12 The transport block manager 1230 described is used for execution.

[0205] At 1815, the method may include: sending an uplink transmission, including a transport block, to a network entity based on uplink permission. The operation at 1815 can be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1815 may be derived from references... Figure 12 The described uplink transmission manager 1235 is used to perform this.

[0206] Figure 19 A flowchart illustrating a method 1900 for multiplexing OCC transmissions performed by multiple UEs 115, according to one or more aspects of this disclosure, is shown. Operation of method 1900 can be implemented by a network entity or its components as described herein. For example, operation of method 1900 can be implemented by, as referred to... Figures 1 to 9 as well as Figures 14 to 17 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0207] At 1905, the method may include: sending control signaling to a set of UEs, the control signaling indicating a corresponding uplink-permitted multiplexing order, repeat configuration, and corresponding orthogonal coverage decoding configuration to be applied to the set of UEs, wherein the repeat configuration indicates a set of RVs, a first number of REs associated with each repeat of each RV in the set of RVs, and a number of repeats associated with each RV in the set of RVs, and wherein the corresponding orthogonal coverage decoding configuration is based on the multiplexing order. The operation at 1905 can be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1905 can be determined by reference to... Figure 16 The control signal transmission manager 1625 described is used to perform this.

[0208] At 1910, the method may include: receiving from a set of UEs a multiplexed set of uplink transports comprising corresponding transport blocks encoded using a corresponding orthogonal overlay decoding configuration, wherein the corresponding transport block comprises one or more corresponding instances of a corresponding RV set, the corresponding one or more instances of the corresponding RV set being mapped to a set of REs associated with a corresponding uplink permission based on the multiplexing order and the corresponding orthogonal overlay decoding configuration. The operation of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1910 may be provided by reference to... Figure 16 The uplink receive manager 1630 described is used to perform this.

[0209] At 1915, the method may include: decoding the corresponding transport block based on the corresponding orthogonal overlay decoding configuration associated with the UE set. The operation at 1915 can be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1915 may be determined by reference to... Figure 16 The described decoding manager 1635 is used to execute this.

[0210] The following provides an overview of some aspects of this disclosure:

[0211] Aspect 1: A method for wireless communication at a UE, comprising: receiving from a network entity control signaling indicating a multiplexing order, repeat configuration, and orthogonal coverage decoding configuration to be applied to uplink permission, wherein the repeat configuration indicates a set of redundant versions, a first number of resource elements associated with each repeat of each redundant version in the set of redundant versions, and a number of repeats associated with each redundant version in the set of redundant versions, and wherein the orthogonal coverage decoding configuration is at least partially based on the multiplexing order; generating a transport block comprising one or more instances of the set of redundant versions, the one or more instances of the set of redundant versions being mapped to a set of resource elements of the transport block over time at least partially based on the multiplexing order and the orthogonal coverage decoding configuration; and transmitting an uplink transmission comprising the transport block to the network entity according to the uplink permission.

[0212] Aspect 2: The method according to aspect 1 further includes: receiving from the network entity an indication that the set of resource elements is associated with the uplink permission; and mapping each instance of each redundant version in the set of redundant versions to a subset of resource elements in the set of resource elements, wherein a second number of resource elements in each subset is the first number multiplied by the multiplexing order.

[0213] Aspect 3: The method according to Aspect 2 further includes: receiving from the network entity a second uplink permission associated with a second set of resource elements, wherein the second set of resource elements includes the same number of resource elements as the set of resource elements, and wherein the second multiplexing order associated with the second uplink permission is one; generating a second transport block according to the repeat configuration; and sending a second uplink transmission including the second transport block to the network entity according to the second uplink permission, wherein a first data capacity of the transport block is equal to a second data capacity of the second transport block.

[0214] Aspect 4: The method according to any one of Aspects 1 to 3, wherein generating the transport block comprises: generating the redundant version set from a data buffer; mapping the repeating sets of the redundant version set to corresponding consecutive subsets of resource elements in the resource element set over time, wherein the number of repeats in each repeating set of the repeating sets is at least partially based on the multiplexing order; and applying the orthogonal overlay decoding configuration to the repeating sets of the corresponding consecutive subsets of resource elements over time to generate the transport block.

[0215] Aspect 5: According to the method of aspect 4, applying the orthogonal overlay decoding configuration includes applying the orthogonal overlay decoding configuration on a per-symbol, per-slot, per-resource-unit, or per-redundancy-version basis.

[0216] Aspect 6: The method according to any one of Aspects 1 to 5, wherein receiving the control signaling comprises: receiving the control signaling indicating that the orthogonal overlay decoding configuration includes rows or columns associated with a Hadamard matrix or a discrete Fourier transform matrix, and wherein the control signaling indicates which rows or columns of the Hadamard matrix or the discrete Fourier transform matrix are associated with the UE.

[0217] Aspect 7: According to the method of aspect 6, the size of the Hadamard matrix or the discrete Fourier transform matrix is ​​associated with the multiplexing order.

[0218] Aspect 8: The method according to any one of Aspects 1 to 7, wherein receiving the control signaling includes: receiving a first control message indicating the repeat configuration; and receiving a second control message indicating the uplink permission, the multiplexing order, and the orthogonal overlay decoding configuration.

[0219] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the total number of repetitions is at least twice the reuse order, and the total number of repetitions is the number of repetitions associated with each redundant version multiplied by the number of redundant versions in the set of redundant versions.

[0220] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the network entity is a non-terrestrial network entity.

[0221] Aspect 11: The method according to any one of Aspects 1 to 10, wherein receiving the control signaling comprises: receiving the control signaling via radio resource control signaling, media access control (MAC) control elements, or a combination thereof.

[0222] Aspect 12: A method for wireless communication at a network entity, comprising: sending control signaling to a set of user equipment (UEs), the control signaling indicating a multiplexing order, a repeatability configuration, and a corresponding orthogonal coverage decoding configuration to be applied to a corresponding uplink permitted for the set of UEs, wherein the repeatability configuration indicates a set of redundant versions, a first number of resource elements associated with each repeat of each redundant version in the set of redundant versions, and a number of repeats associated with each redundant version in the set of redundant versions, and wherein the corresponding orthogonal coverage decoding configuration is at least partially based on the multiplexing order; from the The UE set receives a multiplexed uplink transport set, the multiplexed uplink transport set including corresponding transport blocks encoded using the corresponding orthogonal overlay decoding configuration, wherein the corresponding transport block includes one or more instances of a corresponding redundancy version set, the corresponding one or more instances of the corresponding redundancy version set being mapped at least in part to a set of resource elements associated with the corresponding uplink permission based on the multiplexing order and the corresponding orthogonal overlay decoding configuration; and the corresponding transport block is decoded at least in part based on the corresponding orthogonal overlay decoding configuration associated with the UE set.

[0223] Aspect 13: The method according to aspect 12 further includes: sending an indication to the set of UEs of the set of resource elements associated with the corresponding uplink permission, wherein the multiplexed uplink transmission set is received via the set of resource elements.

[0224] Aspect 14: The method according to aspect 13 further includes: sending a second uplink permission associated with a second resource element set to UEs in the set of UEs, wherein the second resource element set includes the same number of resource elements as the resource element set, and wherein the second multiplexing order associated with the second uplink permission is one; receiving a second uplink transmission including a second transport block from the UE according to the second uplink permission, wherein a first data capacity of the corresponding transport block associated with the UE is equal to a second data capacity of the second transport block.

[0225] Aspect 15: The method according to any one of Aspects 12 to 14, wherein decoding the corresponding transport block based at least in part on the corresponding orthogonal coverage decoding configuration associated with the set of UEs comprises: decoding the corresponding transport block based at least in part on the corresponding orthogonal coverage decoding configuration on a per-symbol, per-slot, per-resource-element, or per-redundancy version basis.

[0226] Aspect 16: The method according to any one of Aspects 12 to 15, wherein sending the control signaling comprises: sending the control signaling indicating that the corresponding orthogonal overlay decoding configuration includes rows or columns associated with a Hadamard matrix or a discrete Fourier transform matrix, and wherein the control signaling indicates which rows or columns of the Hadamard matrix or the discrete Fourier transform matrix are associated with each UE in the UE set.

[0227] Aspect 17: The method according to aspect 16, wherein the size of the Hadamard matrix or the discrete Fourier transform matrix is ​​associated with the multiplexing order.

[0228] Aspect 18: The method according to any one of Aspects 12 to 17, wherein sending the control signaling includes: sending a first control message indicating the repetitive configuration; and sending a corresponding second control message to the UE set indicating the corresponding uplink permission, the multiplexing order, and the corresponding orthogonal coverage decoding configuration.

[0229] Aspect 19: The method according to any one of Aspects 12 to 18, wherein the total number of repetitions is at least twice the reuse order, and the total number of repetitions is the number of repetitions associated with each redundant version multiplied by the number of redundant versions in the set of redundant versions.

[0230] Aspect 20: The method according to any one of Aspects 12 to 19, wherein the network entity is a non-terrestrial network entity.

[0231] Aspect 21: The method according to any one of Aspects 12 to 20, wherein sending the control signaling comprises: sending the control signaling via radio resource control signaling, media access control (MAC) control elements or a combination thereof.

[0232] Aspect 22: An apparatus for wireless communication at a UE, 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 any one of aspects 1 to 11.

[0233] Aspect 23: An apparatus for wireless communication at a UE, comprising: at least one unit for performing the method according to any one of aspects 1 to 11.

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

[0235] Aspect 25: An apparatus for wireless communication at a network entity, 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 any one of aspects 12 to 21.

[0236] Aspect 26: An apparatus for wireless communication at a network entity, comprising at least one unit for performing the method according to any one of aspects 12 to 21.

[0237] Aspect 27: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code including instructions executable by a processor to perform a method according to any one of aspects 12 to 21.

[0238] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods can be combined.

[0239] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in much of the description, the techniques described herein apply beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described can be applied to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

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

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

[0242] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using such instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including being distributed such that different parts of the functions are implemented in different physical locations.

[0243] Computer-readable media includes both non-transitory computer storage media and communication media, with communication media encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose computer or a special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired units of program code in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically copy data, while optical discs can optically copy data using lasers. The combination described above is also included within the scope of computer-readable media.

[0244] As used herein (including in the claims), the word "or" in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such that a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0245] The term "determine" or "determining" encompasses a wide variety of actions, and therefore, "determining" can include calculation, operation, processing, derivation, investigation, searching (e.g., looking in a table, database, or other data structure), ascertaining, etc. Furthermore, "determining" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Additionally, "determining" can include parsing, obtaining, selecting, choosing, creating, and other similar actions.

[0246] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by a dash and a second reference numeral following the reference numeral, the second reference numeral used to differentiate between similar components. If only the first reference numeral is used in the specification, the description applies to any one of the similar components having the same first reference numeral, regardless of the second reference numeral or other subsequent reference numerals.

[0247] This document describes exemplary configurations in conjunction with the accompanying drawings, and does not represent all examples that can be implemented or that are within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," and not "preferred" or "advantageous over other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques can be implemented without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0248] The descriptions provided herein are intended to enable those skilled in the art to implement or use the present disclosure. Various modifications to the present disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of the disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but is to be given the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: The network entity receives control signaling indicating the multiplexing order, repeat configuration, and orthogonal overlay decoding configuration to be applied to the uplink, wherein the repeat configuration indicates a set of redundant versions, a first number of resource elements associated with each repeat of each redundant version in the set of redundant versions, and a number of repeats associated with each redundant version in the set of redundant versions, and wherein the orthogonal overlay decoding configuration is at least partially based on the multiplexing order; Generate a transport block comprising one or more instances of the redundant version set, wherein the one or more instances of the redundant version set are mapped to a set of resource elements of the transport block at least in part based on the multiplexing order and the orthogonal overlay decoding configuration spanning time; and Uplink transmissions, including the transport block, are sent to the network entity based on the uplink permission.

2. The method according to claim 1, further comprising: Receive from the network entity an indication regarding the association of the resource element set with the uplink permission; as well as Each instance of each redundant version in the redundant version set is mapped to a subset of resource elements in the resource element set, wherein the second number of resource elements in each subset is the first number multiplied by the reuse order.

3. The method according to claim 2, further comprising: Receive a second uplink permission associated with a second set of resource elements from the network entity, wherein the second set of resource elements includes the same number of resource elements as the set of resource elements, and wherein the second multiplexing order associated with the second uplink permission is one; A second transport block is generated according to the repeated configuration; and A second uplink transmission, including the second transport block, is sent to the network entity according to the second uplink permission, wherein the first data capacity of the transport block is equal to the second data capacity of the second transport block.

4. The method according to claim 1, wherein, Generating the transport block includes: The redundant version set is generated from the data buffer; Mapping the duplicate sets of the redundant version set to corresponding consecutive subsets of resource elements in the resource element set across time, wherein the number of duplicates in each duplicate set is at least partially based on the reuse order; and The orthogonal overlay decoding configuration is applied to the time-spanning set of the redundant version set and mapped to the repeating set of the corresponding consecutive resource element subset to generate the transport block.

5. The method according to claim 4, wherein, The application of the orthogonal overlay decoding configuration includes: The orthogonal overlay decoding configuration is applied on a per-symbol, per-slot, per-resource-unit, or per-redundancy-version basis.

6. The method according to claim 1, wherein, Receiving the control signaling includes: The control signaling received indicates that the orthogonal overlay decoding configuration includes rows or columns associated with a Hadamard matrix or a discrete Fourier transform matrix, wherein the control signaling indicates which rows or columns of the Hadamard matrix or the discrete Fourier transform matrix are associated with the UE.

7. The method according to claim 6, wherein, The size of the Hadamard matrix or the discrete Fourier transform matrix is ​​related to the multiplexing order.

8. The method according to claim 1, wherein, Receiving the control signaling includes: Receive a first control message indicating the repeated configuration; and Receive a second control message indicating the uplink permission, the multiplexing order, and the orthogonal overlay decoding configuration.

9. The method according to claim 1, wherein: The total number of repetitions is at least twice the reuse order, and The total number of duplicates is the number of duplicates associated with each redundant version multiplied by the number of redundant versions in the set of redundant versions.

10. The method according to claim 1, wherein, The network entity is a non-terrestrial network entity.

11. The method according to claim 1, wherein, Receiving the control signaling includes: The control signaling is received via radio resource control signaling, media access control (MAC) control elements, or a combination thereof.

12. A method for wireless communication at a network entity, comprising: A control signaling is sent to a set of user equipment (UEs) indicating the appropriate uplink permitted multiplexing order, repeatability configuration, and appropriate orthogonal coverage decoding configuration to be applied to the set of UEs, wherein the repeatability configuration indicates a set of redundant versions, a first number of resource elements associated with each repeat of each redundant version in the set of redundant versions, and a number of repeats associated with each redundant version in the set of redundant versions, and wherein the appropriate orthogonal coverage decoding configuration is at least partially based on the multiplexing order; Receive from the UE set a multiplexed uplink transport set, the multiplexed uplink transport set comprising corresponding transport blocks encoded using the corresponding orthogonal overlay decoding configuration, wherein the corresponding transport block comprises one or more instances of a corresponding redundancy version set, the corresponding one or more instances of the corresponding redundancy version set being mapped, at least in part, to a set of resource elements associated with the corresponding uplink permission based on the multiplexing order and the corresponding orthogonal overlay decoding configuration; and The corresponding transport block is decoded at least in part based on the corresponding orthogonal overlay decoding configuration associated with the UE set.

13. The method of claim 12, further comprising: Send an indication to the set of UEs of the set of resource elements associated with the corresponding uplink permission, wherein the multiplexed uplink transmission set is received via the set of resource elements.

14. The method of claim 13, further comprising: Send a second uplink grant associated with a second set of resource elements to UEs in the UE set, wherein the second set of resource elements includes the same number of resource elements as the set of resource elements, and wherein the second multiplexing order associated with the second uplink grant is one; and The second uplink transmission, including a second transport block, is received from the UE according to the second uplink permission, wherein the first data capacity of the corresponding transport block associated with the UE is equal to the second data capacity of the second transport block.

15. The method according to claim 12, wherein, Decoding the corresponding transport block, at least in part, based on the corresponding orthogonal coverage decoding configuration associated with the UE set, includes: The corresponding transport block is decoded at least in part based on the corresponding orthogonal overlay decoding configuration on a per-symbol, per-slot, per-resource-unit, or per-redundancy version basis.

16. The method according to claim 12, wherein, Sending the control signaling includes: The control signaling is sent indicating that the corresponding orthogonal overlay decoding configuration includes rows or columns associated with a Hadamard matrix or a discrete Fourier transform matrix, wherein the control signaling indicates which rows or columns of the Hadamard matrix or the discrete Fourier transform matrix are associated with each UE in the UE set.

17. The method according to claim 16, wherein, The size of the Hadamard matrix or the discrete Fourier transform matrix is ​​related to the multiplexing order.

18. The method according to claim 12, wherein, Sending the control signaling includes: Send a first control message indicating the repeated configuration; and Send a corresponding second control message to the UE set, indicating the corresponding uplink permission, the multiplexing order, and the corresponding orthogonal coverage decoding configuration.

19. The method according to claim 12, wherein: The total number of repetitions is at least twice the reuse order, and The total number of duplicates is the number of duplicates associated with each redundant version multiplied by the number of redundant versions in the set of redundant versions.

20. The method according to claim 12, wherein, The network entity is a non-terrestrial network entity.

21. The method according to claim 12, wherein, Sending the control signaling includes: The control signaling is transmitted via radio resource control signaling, media access control (MAC) control elements, or a combination thereof.

22. An apparatus for wireless communication at a user equipment (UE), comprising: processor; A memory coupled to the processor; as well as Instructions, which are stored in the memory and can be executed by the processor, cause the device to perform the following operations: The network entity receives control signaling indicating the multiplexing order, repeat configuration, and orthogonal overlay decoding configuration to be applied to the uplink, wherein the repeat configuration indicates a set of redundant versions, a first number of resource elements associated with each repeat of each redundant version in the set of redundant versions, and a number of repeats associated with each redundant version in the set of redundant versions, and wherein the orthogonal overlay decoding configuration is at least partially based on the multiplexing order; Generate a transport block comprising one or more instances of the redundant version set, wherein the one or more instances of the redundant version set are mapped to a set of resource elements of the transport block at least in part based on the multiplexing order and the orthogonal overlay decoding configuration spanning time; and Uplink transmissions, including the transport block, are sent to the network entity based on the uplink permission.

23. An apparatus for wireless communication at a network entity, comprising: processor; A memory coupled to the processor; as well as Instructions, which are stored in the memory and can be executed by the processor, cause the device to perform the following operations: A control signaling is sent to a set of user equipment (UEs) indicating the appropriate uplink permitted multiplexing order, repeatability configuration, and appropriate orthogonal coverage decoding configuration to be applied to the set of UEs, wherein the repeatability configuration indicates a set of redundant versions, a first number of resource elements associated with each repeat of each redundant version in the set of redundant versions, and a number of repeats associated with each redundant version in the set of redundant versions, and wherein the appropriate orthogonal coverage decoding configuration is at least partially based on the multiplexing order; Receive from the UE set a multiplexed uplink transport set, the multiplexed uplink transport set comprising corresponding transport blocks encoded using the corresponding orthogonal overlay decoding configuration, wherein the corresponding transport block comprises one or more instances of a corresponding redundancy version set, the corresponding one or more instances of the corresponding redundancy version set being mapped, at least in part, to a set of resource elements associated with the corresponding uplink permission based on the multiplexing order and the corresponding orthogonal overlay decoding configuration; and The corresponding transport block is decoded at least in part based on the corresponding orthogonal overlay decoding configuration associated with the UE set.

Images