Methods for physical uplink shared channel enhancement with uplink muting and orthogonal cover code
The integration of orthogonal cover codes with enhanced PUSCH configurations addresses length mismatches, collisions, and interference in 5G NR networks, enhancing uplink performance and reliability in dense deployments.
Patent Information
- Application Number
- PCT/CN2025/093797
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-09
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication systems face undefined behaviors and inefficiencies in handling length mismatches between orthogonal cover codes (OCC) and physical uplink shared channel (PUSCH) repetitions, collisions with high priority signals, power control inconsistencies, and interference management due to uplink muting, particularly in 5G NR networks.
Implementing methods for PUSCH enhancements that include configuring UEs to apply OCC with uplink transmissions, handling collisions through postponement or dropping of repetitions, managing power control configurations, and integrating uplink muting to maintain orthogonality and interference mitigation, while supporting π/2 BPSK modulation and DFT-s-OFDM waveforms.
Enhances uplink performance by improving coverage, managing interference, and ensuring reliable communication in dense deployments through defined UE behaviors and network configurations that maintain orthogonality and power consistency.
Smart Images

Figure CN2025093797_12112026_PF_FP_ABST
Abstract
Description
METHODS FOR PHYSICAL UPLINK SHARED CHANNEL ENHANCEMENT WITH UPLINK MUTING AND ORTHOGONAL COVER CODETECHNICAL FIELD
[0001] The present disclosure relates generally to wireless communication, and more particularly, to an enhanced physical uplink shared channel (PUSCH) with uplink muting and orthogonal cover code (OCC) .BACKGROUND
[0002] The Third Generation Partnership Project (3GPP) specifies a radio interface referred to as fifth generation (5G) new radio (NR) (5G NR) . An architecture for a 5G NR wireless communication system includes a 5G core (5GC) network, a 5G radio access network (5G-RAN) , a user equipment (5G UE) , etc. The 5G NR architecture seeks to provide increased data rates, decreased latency, and / or increased capacity compared to prior generation cellular communication systems.
[0003] Wireless communication systems, in general, provide various telecommunication services (e.g., telephony, video, data, messaging, etc. ) based on multiple-access technologies, such as orthogonal frequency division multiple access (OFDMA) technologies, that support communication with multiple UEs. Improvements in mobile broadband continue the progression of such wireless communication technologies. For example, enhancing PUSCH may provide for robust and efficient uplink performance in wireless communication networks. Integration of OCC with PUSCH transmissions may improve coverage and recover throughput loss. Details pertaining to the integration of OCC with PUSCH transmissions may be undefined. BRIEF SUMMARY
[0004] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor delineates the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
[0005] A network entity, such as a base station or a unit of a base station, may configure a user equipment (UE) to transmit physical uplink shared channel (PUSCH) repetitions with orthogonal cover codes (OCC) . OCC are sequences used in communication systems, which can be applied to multiplex signals in the same radio resources from different sources. OCC can be applied with uplink (UL) repetitions to compensate for throughput loss due to the transmission of the PUSCH repetitions. The UE may apply a distinct OCC sequence in an OCC group to allow the network entity to distinguish individual signals from the multiplexed signals.
[0006] UL resource muting is a technique where the network refrains from scheduling a certain number of symbols within a slot for PUSCH transmissions, creating quiet periods in the uplink. The muted UL resources manage interference between base stations. Specifically, the muted UL resources enable network entities to perform network entity to network entity co-channel inter-subband cross link interference (CLI) measurements and to estimate the network entity to network entity CLI covariance matrix, providing valuable data for optimizing network performance and mitigating interference without disrupting normal user data flow on other symbols.
[0007] In some aspects, to apply the OCC the UE configures an uplink transmission into repetitions, and then applies the OCC to the repetitions. A one-to-one mapping may be applied when a length of the repetition equals to the length of an OCC sequence. However, in some aspects, the length of the repetition and the OCC sequence may not be the same. Thus, details pertaining to the UE behavior when the length of the repetition and the OCC sequence do not match may be undefined. In some aspects, if one repetition of PUSCH repetitions collides with high priority signals / symbols, the repetition may be dropped or postponed, which may impact the orthogonality of an OCC sequence when applied to PUSCH repetitions. Thus, details pertaining to handling collisions between a PUSCH repetition with OCC and other signals may be undefined. In some aspects, for uplink repetition, UEs may perform repetition with slot counting such that UEs may postpone a repetition to a next available uplink resource due to a collision with another signal. However, the interruption of a continuous uplink repetitions transmission may lead to non-continuous transmission phase which may impact the orthogonality of the OCC sequence. Thus, details pertaining to handling collisions between the PUSCH repetition with OCC with slot counting may be undefined. In some aspects, the network entity may configure a UE to transmit uplink transmissions in a set of time domain resources where different uplink configurations are applied for different time domain resources. However, if a repetition transmission with the OCC crosses the different time domain resources, only one power control configuration may be applied. Thus, details pertaining to instances where the repetition transmission with the OCC crosses the different time domain resources may be undefined. In some aspects, PUSCH may support π / 2 binary phase shift keying (BPSK) modulation, particularly with the discrete Fourier transform-spread-orthogonal frequency division multiplexing (DFT-s-OFDM) waveforms, to enhance uplink coverage. However, some instances of UL resource muting may inadvertently compromise the benefits of π / 2 BPSK, such as when transform precoding is enabled for PUSCH. Thus, details pertaining to input symbols that are selected or generated for the π / 2 BPSK modulation may be undefined.
[0008] Aspects of the present disclosure address the above-noted and other deficiencies by implementing methods for PUSCH enhancements with uplink muting and OCC. For example, the present disclosure describes UE procedures for length mismatches between the OCC sequence and the PUSCH repetition, collision handling for PUSCH repetition with the OCC with or without slot counting, or power consistency issues due to separate power control configurations. In some aspects, the present disclosure describes a configuration and indication of applying OCC to uplink transmissions and UE behaviors when configuring the OCC with features such as uplink repetition, uplink repetition with slot counting, multiple power control configurations, DFT-s-OFDM transform precoding, and uplink resource muting.
[0009] According to some aspects, the UE receives, from a network entity, a configuration for uplink transmission including a PUSCH repetition configuration with an OCC configuration. The configuration for the uplink transmission being based on at least an uplink enhancement factor. The UE transmits, to the network entity, PUSCH repetitions with OCC based on the configuration for the uplink transmission.
[0010] According to some aspects, the network entity transmits, to a UE, a configuration for uplink transmission including a PUSCH repetition configuration with an OCC configuration. The configuration for the uplink transmission being based on at least an uplink enhancement factor. The network entity receives, from the UE, PUSCH repetitions with OCC based on the configuration for the uplink transmission.BRIEF DESCRIPTION OF THE DRAWINGS
[0011] FIG. 1 illustrates a diagram of a wireless communications system that includes a plurality of UEs and network entities in communication over one or more cells according to an embodiment.
[0012] FIG. 2 is a diagram illustrating an example of PUSCH repetition with OCC multiplexing according to an embodiment.
[0013] FIG. 3 is a diagram illustrating an example of length-4 OCC sequences in an OCC group according to an embodiment.
[0014] FIG. 4 is a diagram illustrating an example of uplink muting according to an embodiment.
[0015] FIG. 5 is a signaling diagram illustrating communications between a UE and a network entity for PUSCH repetitions with OCC according to an embodiment.
[0016] FIG. 6 is a diagram illustrating an example of an OCC sequence repetition according to an embodiment.
[0017] FIG. 7 is a diagram illustrating an example of an application of OCC pattern cycling according to an embodiment.
[0018] FIG. 8 is a diagram illustrating an example of an application of OCC sequence repetition in orphan repetitions according to an embodiment.
[0019] FIG. 9 is a diagram illustrating an example of dropping orphan repetitions for OCC according to an embodiment.
[0020] FIG. 10 is a diagram illustrating an example of a repetition length being less than an OCC length according to an embodiment.
[0021] FIG. 11 is a flow diagram illustrating an example of PUSCH repetition with slot counting and OCC according to an embodiment.
[0022] FIG. 12 is a flow diagram illustrating an example of a collision of PUSCH repetition with OCC and a transmission with a higher priority according to an embodiment.
[0023] FIG. 13 is a flow diagram illustrating an example of postponement of an OCC bit of collided PUSCH repetition to a subsequent non-collided PUSCH repetition according to an embodiment.
[0024] FIG. 14 is a diagram illustrating an example of postponement of an OCC bit of collided PUSCH repetition to a subsequent non-collided PUSCH repetition according to an embodiment.
[0025] FIG. 15 is a flowchart of a method of wireless communication at a UE according to an embodiment.
[0026] FIG. 16 is a flowchart of a method of wireless communication at a network entity according to an embodiment.
[0027] FIG. 17 is a diagram illustrating a hardware implementation for an example UE apparatus according to some embodiments.
[0028] FIG. 18 is a diagram illustrating a hardware implementation for one or more example network entities according to some embodiments.DETAILED DESCRIPTION
[0029] FIG. 1 illustrates a diagram 100 of a wireless communications system associated with a plurality of cells 190. The wireless communications system includes user equipments (UEs) 102 and base stations / network entities 104. Some base stations may include an aggregated base station architecture and other base stations may include a disaggregated base station architecture. The aggregated base station architecture utilizes a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node. A disaggregated base station architecture utilizes a protocol stack that is physically or logically distributed among two or more units (e.g., radio unit (RU) 106, distributed unit (DU) 108, central unit (CU) 110) . For example, a CU 110 is implemented within a RAN node, and one or more DUs 108 may be co-located with the CU 110, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs 108 may be implemented to communicate with one or more RUs 106. Any of the RU 106, the DU 108 and the CU 110 can be implemented as virtual units, such as a virtual radio unit (VRU) , a virtual distributed unit (VDU) , or a virtual central unit (VCU) . The base station / network entity 104 (e.g., an aggregated base station or disaggregated units of the base station, such as the RU 106 or the DU 108) , may be referred to as a transmission reception point (TRP) .
[0030] Operations of the base station 104 and / or network designs may be based on aggregation characteristics of base station functionality. For example, disaggregated base station architectures are utilized in an integrated access backhaul (IAB) network, an open-radio access network (O-RAN) network, or a virtualized radio access network (vRAN) , which may also be referred to a cloud radio access network (C-RAN) . Disaggregation may include distributing functionality across the two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network designs. The various units of the disaggregated base station architecture, or the disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit. For example, the base stations 104d, 104e and / or the RUs 106a, 106b, 106c, 106d may communicate with the UEs 102a, 102b, 102c, 102d, and / or 102s via one or more radio frequency (RF) access links based on a Uu interface. In examples, multiple RUs 106 and / or base stations 104 may simultaneously serve the UEs 102, such as by intra-cell and / or inter-cell access links between the UEs 102 and the RUs 106 / base stations 104.
[0031] The RU 106, the DU 108, and the CU 110 may include (or may be coupled to) one or more interfaces configured to transmit or receive information / signals via a wired or wireless transmission medium. For example, a wired interface can be configured to transmit or receive the information / signals over a wired transmission medium, such as via the fronthaul link 160 between the RU 106d and the baseband unit (BBU) 112 of the base station 104d associated with the cell 190d. The BBU 112 includes a DU 108 and a CU 110, which may also have a wired interface (e.g., midhaul link) configured between the DU 108 and the CU 110 to transmit or receive the information / signals between the DU 108 and the CU 110. In further examples, a wireless interface, which may include a receiver, a transmitter, or a transceiver, such as an RF transceiver, configured to transmit and / or receive the information / signals via the wireless transmission medium, such as for information communicated between the RU 106a of the cell 190a and the base station 104e of the cell 190e via cross-cell communication beams 136-138 of the RU 106a and the base station 104e.
[0032] The RUs 106 may be configured to implement lower layer functionality. For example, the RU 106 is controlled by the DU 108 and may correspond to a logical node that hosts RF processing functions, or lower layer PHY functionality, such as execution of fast Fourier transform (FFT) , inverse FFT (iFFT) , digital beamforming, physical random access channel (PRACH) extraction and filtering, etc. The functionality of the RU 106 may be based on the functional split, such as a functional split of lower layers.
[0033] The RUs 106 may transmit or receive over-the-air (OTA) communication with one or more UEs 102. For example, the RU 106b of the cell 190b communicates with the UE 102b of the cell 190b via a first set of communication beams 132 of the RU 106b and a second set of communication beams 134b of the UE 102b, which may correspond to inter-cell communication beams or, in some examples, cross-cell communication beams. For instance, the UE 102b of the cell 190b may communicate with the RU 106a of the cell 190a via a third set of communication beams 134a of the UE 102b and a fourth set of communication beams 136 of the RU 106a. DUs 108 can control both real-time and non-real-time features of control plane and user plane communications of the RUs 106.
[0034] Any combination of the RU 106, the DU 108, and the CU 110, or reference thereto individually, may correspond to a base station 104. Thus, the base station 104 may include at least one of the RU 106, the DU 108, or the CU 110. The base stations 104 provide the UEs 102 with access to a core network. The base stations 104 may relay communications between the UEs 102 and the core network (not shown) . The base stations 104 may be associated with macrocells for higher-power cellular base stations and / or small cells for lower-power cellular base stations. For example, the cell 190e may correspond to a macrocell, whereas the cells 190a-190d may correspond to small cells. Small cells include femtocells, picocells, microcells, etc. A network that includes at least one macrocell and at least one small cell may be referred to as a “heterogeneous network. ”
[0035] Transmissions from a UE 102 to a base station 104 / RU 106 are referred to as uplink (UL) transmissions, whereas transmissions from the base station 104 / RU 106 to the UE 102 are referred to as downlink (DL) transmissions. Uplink transmissions may also be referred to as reverse link transmissions and downlink transmissions may also be referred to as forward link transmissions. For example, the RU 106d utilizes antennas of the base station 104d of cell 190d to transmit a downlink / forward link communication to the UE 102d or receive an uplink / reverse link communication from the UE 102d based on the Uu interface associated with the access link between the UE 102d and the base station 104d / RU 106d.
[0036] Communication links between the UEs 102 and the base stations 104 / RUs 106 may be based on multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links may be associated with one or more carriers. The UEs 102 and the base stations 104 / RUs 106 may utilize a spectrum bandwidth of Y MHz (e.g., 5, 10, 15, 20, 100, 400, 800, 1600, 2000, etc. MHz) per carrier allocated in a carrier aggregation of up to a total of Yx MHz, where x component carriers (CCs) are used for communication in each of the uplink and downlink directions. The carriers may or may not be adjacent to each other along a frequency spectrum. In examples, uplink and downlink carriers may be allocated in an asymmetric manner, with more or fewer carriers allocated to either the uplink or the downlink. A primary component carrier and one or more secondary component carriers may be included in the component carriers. The primary component carrier may be associated with a primary cell (PCell) and a secondary component carrier may be associated with a secondary cell (SCell) .
[0037] Some UEs 102, such as the UEs 102a and 102s, may perform device-to-device (D2D) communications over sidelink. For example, a sidelink communication / D2D link utilizes a spectrum for a wireless wide area network (WWAN) associated with uplink and downlink communications. Such sidelink / D2D communication may be performed through various wireless communications systems, such as wireless fidelity (Wi-Fi) systems, Bluetooth systems, Long Term Evolution (LTE) systems, New Radio (NR) systems, etc.
[0038] The UEs 102 and the base stations 104 / RUs 106 may each include a plurality of antennas. The plurality of antennas may correspond to antenna elements, antenna panels, and / or antenna arrays that may facilitate beamforming operations. For example, the RU 106b transmits a downlink beamformed signal based on a first set of communication beams 132 to the UE 102b in one or more transmit directions of the RU 106b. The UE 102b may receive the downlink beamformed signal based on a second set of communication beams 134b from the RU 106b in one or more receive directions of the UE 102b. In a further example, the UE 102b may also transmit an uplink beamformed signal (e.g., sounding reference signal (SRS) ) to the RU 106b based on the second set of communication beams 134b in one or more transmit directions of the UE 102b. The RU 106b may receive the uplink beamformed signal from the UE 102b in one or more receive directions of the RU 106b. The UE 102b may perform beam training to determine the best receive and transmit directions for the beamformed signals. The transmit and receive directions for the UEs 102 and the base stations 104 / RUs 106 may or may not be the same.
[0039] In further examples, beamformed signals may be communicated between a first base station / RU 106a and a second base station 104e. For instance, the base station 104e of the cell 190e may transmit a beamformed signal to the RU 106a based on the communication beams 138 in one or more transmit directions of the base station 104e. The RU 106a may receive the beamformed signal from the base station 104e of the cell 190e based on the RU communication beams 136 in one or more receive directions of the RU 106a. In further examples, the base station 104e transmits a downlink beamformed signal to the UE 102e based on the communication beams 138 in one or more transmit directions of the base station 104e. The UE 102e receives the downlink beamformed signal from the base station 104e based on UE communication beams 130 in one or more receive directions of the UE 102e. The UE 102e may also transmit an uplink beamformed signal to the base station 104e based on the UE communication beams 130 in one or more transmit directions of the UE 102e, such that the base station 104e may receive the uplink beamformed signal from the UE 102e in one or more receive directions of the base station 104e.
[0040] The base station 104 may include and / or be referred to as a network entity. That is, “network entity” may refer to the base station 104 or at least one unit of the base station 104, such as the RU 106, the DU 108, and / or the CU 110. The base station 104 may also include and / or be referred to as a next generation evolved Node B (ng-eNB) , a next generation NB (gNB) , an evolved NB (eNB) , an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a TRP, a network node, network equipment, or other related terminology. The base station 104 or an entity at the base station 104 can be implemented as an IAB node, a relay node, a sidelink node, an aggregated (monolithic) base station, or a disaggregated base station including one or more RUs 106, DUs 108, and / or CUs 110. A set of aggregated or disaggregated base stations may be referred to as a next generation-radio access network (NG-RAN) . In some examples, the UE 102a operates in dual connectivity (DC) with the base station 104e and the base station / RU 106a. In such cases, the base station 104e can be a master node and the base station / RU 106a can be a secondary node.
[0041] Still referring to FIG. 1, in certain aspects, any of the UEs 102 may include a PUSCH repetition component 140 configured to receive, from a network entity, a configuration for a PUSCH including repetition information and OCC information; apply, an OCC sequence associated with the OCC information, to PUSCH repetitions associated with the repetition information; and transmit, to the network entity, the PUSCH repetitions based on at least one of: a length of the OCC sequence different from a length of the PUSCH repetitions, a collision between a PUSCH repetition and another transmission, different power control configurations for the PUSCH repetitions, or UL resource muting.
[0042] In certain aspects, any of the base stations 104 or a network entity of the base stations 104 may include an uplink configuration component 150 configured to transmit, to a UE, a configuration for a PUSCH including repetition information and OCC information, an OCC sequence associated with the OCC information being applied over PUSCH repetitions associated with the repetition information; and receive, from the UE, the PUSCH repetitions based on at least one of: a length of the OCC sequence different from a length of the PUSCH repetitions, a collision between a PUSCH repetition and another transmission, different power control configurations for the PUSCH repetitions, or UL resource muting.
[0043] Accordingly, FIG. 1 describes a wireless communication system that may be implemented in connection with aspects of one or more other figures described herein. Further, although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as 5G-Advanced and future versions, LTE, LTE-advanced (LTE-A) , and other wireless technologies, such as 6G.
[0044] Enhancing PUSCH is critical for robust and efficient uplink (UL) performance in modern wireless communication networks. The integration of OCC with PUSCH transmissions plays a significant role in improving coverage and recovering the throughput loss.
[0045] Simultaneously, addressing UL muting, where a UE temporarily silences its uplink transmission, is crucial for managing interference in sub-band full duplex scenarios.
[0046] Therefore, PUSCH enhancements that effectively incorporate OCC and manage UL muting are vital for boosting uplink capacity, improving spectral efficiency, improving coverage, and ensuring reliable communication, particularly in dense deployments, cell edge scenarios and other diverse scenarios.
[0047] OCC are sequences used in communication systems, which can be applied to multiplex signals in the same radio resources from different sources, such as signals from different layer, UE, and base stations (BS) . OCC can be applied with UL repetitions in the coverage enhancement scenario to make up the throughput loss in the system due to the repetition transmission. For example, plural UEs may be scheduled or configured to send UL repetitions in the same radio resources, where each UE applies a distinct OCC sequence in an OCC group. In accordance with the OCC sequence, the base station can distinguish individual signals from the multiplexed signals.
[0048] FIG. 2 is a diagram 200 illustrating an example of PUSCH repetition with OCC multiplexing according to an embodiment. The diagram 200 of FIG. 2 illustrates an example where UE 1 and UE 2 are scheduled to transmit PUSCH repetitions (e.g., 210, 212) with OCC in an OOC group. PUSCH repetitions (e.g., 210a, 210b, 210c, 210d) of UE 1 and the PUSCH repetitions (e.g., 212a, 212b, 212c, 212d) of UE 2 share the same time and frequency resources.
[0049] FIG. 3 is a diagram 300 illustrating an example of length-4 OCC sequences in an OCC group according to an embodiment. The diagram 300 of FIG. 3 includes an index 314 and an OCC sequence 316 associated with the index 314. According to diagram 300 of FIG. 3, a length-4 OCC sequence list, UE 1 and UE 2 apply the 2nd and 3rd OCC sequences from the OCC group, respectively, where the 1st code bit is applied to the 1st repetition, 2nd code bit is applied to the 2nd repetition, and so on.
[0050] The present disclosure includes a configuration and indication of applying OCC to UL transmission, and UE behaviors when configuring OCC with features such as UL repetition, UL repetition with slot counting, multiple power control configurations (e.g., in sub-band full duplex, SBFD) , DFT-s-OFDM transform precoding, and UL resource muting.
[0051] FIG. 4 is a diagram 400 illustrating an example of uplink muting according to an embodiment. UL resource muting is a technique where the network intentionally refrains from scheduling a certain number of symbols within a slot for PUSCH transmissions (e.g., 422) , effectively creating quiet periods in the uplink. These transparently muted UL resources (e.g., 424) serve a crucial purpose in managing interference between base stations. Specifically, they enable base stations to perform base station (e.g., 104a) to base station (e.g., 104b) co-channel inter-subband cross-link interference (CLI) measurements and to estimate the base station to base station CLI covariance matrix, providing valuable data for optimizing network performance and mitigating interference without disrupting normal user data flow on other symbols. In the diagram 400 of FIG. 4, the base station 104a may be a victim network entity and the base station 104b may be an aggressor network entity, such that downlink transmissions (e.g., physical downlink control channel (PDCCH) 418, physical downlink shared channel (PDSCH) 420) of the base station 104b may interfere with uplink transmissions (e.g., PUSCH 422) intended for the base station 104a.
[0052] To apply OCC, UE has to turn a transmission into repetitions (e.g., transmission occasions) , the UE may then apply OCC to the repetitions. For example, multiplying the first OCC code bit to the first repetition, the second OCC code bit to the second repetition, and so on. In some aspects, the length of repetition equals to the length of the OCC sequence, thus a 1-to-1 mapping may be applied. However, in some aspects, the length of repetition and the length of the OCC sequence are separated configured and / or indicated to the UE. In such instances, the length of the repetition and the length of the OCC sequence may not match to each other, such that the UE behavior may be clarified.
[0053] In some aspects, if one repetition of PUSCH repetitions collides with high priority signals or indicated DL symbols, the repetition will be drop or postponed according to UE capability and base station configuration. However, when OCC is applied to PUSCH repetition, dropping a repetition may break the orthogonality an OCC sequence, thereby increasing the interference to other UEs in the same OCC group. In this regard, the collision handling rule for PUSCH repetition with OCC may be further clarified.
[0054] For UL repetition, some UEs can perform repetition with slot counting. For example, when the UE is not able to send a repetition in transmission repetitions due to collision with cell specific signal and channel or high priority transmission, the UE may postpone the repetition to the next available UL resource. However, the interruption of a continuous UL repetitions transmission may lead to non-continuous transmission phase, which will break the orthogonality of the OCC sequence. Thus, the UE behavior in such scenario may be defined.
[0055] With some feature such as subband full duplex (SBFD) , the base station configures a UE to transmit UL in a set of time domain resource (e.g., a set of slot and symbols indexes) , wherein the UE applies a 1st UL configuration for transmissions in a 1st subset of the set of time domain resource and applies a 2nd UL configuration for transmissions in a 2nd subset of the set of time domain resource. For example, the UE is configured to apply separate power control configurations to transmissions on the 1st and 2nd subset of the set of time domain resource. However, if a repetition transmission with OCC crosses the 1st and 2nd subset of the set of time domain resource, only one power control configuration can be applied, in order to maintain the power consistency of the OCC sequence.
[0056] To suppress interference power level, the base station can configure a UE to avoid mapping UL transmission on some UL resources (e.g., UL resource muting) . For example, the base station may indicate a UE to perform comb-2 UL resource muting for a symbol index in each slot, where the UE will avoid to use every even indexed resource elements (RE) in each resource block (RB) for UL transmission. If the UE is also configured to use DFT-s-OFDM waveform (e.g., transform precoder is enabled) for UL transmission where a DFT precoding should be applied before the resource mapping. With comb-2 UL resource muting, the scheduled UL resource may not fit the DFT size supported by the UE. It may affect how a base station scheduling OCC and repetition to the UE.
[0057] PUSCH supports π / 2-BPSK modulation, particularly with the DFT-s-OFDM waveform, to enhance uplink coverage. A key advantage of π / 2 binary phase shift keying (BPSK) modulation is its ability to offer a lower peak-to-average power ratio (PAPR) compared to BPSK modulation. Standard BPSK modulation can suffer from high PAPR due to the zero crossings in the signal envelope. These zero crossings happen when the bit stream changes from 0 to 1, or 1 to 0 leading to a 180-degree phase shift as the signal transitions between constellation points. Such phase change causes the signal envelope to momentarily pass through or near zero, contributing to an increased PAPR.
[0058] A π / 2-BPSK modulated symbol is generated as: from a BPSK symbol: where i is the complex-valued symbol index.
[0059] The incremental π / 2 phase rotation applied to successive complex-valued symbols ensures that direct 180-degree phase transitions between adjacent symbols are avoided, thereby maintaining a more constant signal envelope and achieving the desired PAPR reduction.
[0060] However, specific handling of UL resource muting may inadvertently compromise these benefits of π / 2-BPSK when transform precoding is enabled for PUSCH.
[0061] In some aspects, the DFT processing effectively operates on modulated symbols, where is the total number of scheduled subcarriers for the PUSCH. This reduction is achieved either by modifying the DFT size to or by employing symbol repetition or zero-padding strategies with a DFT of size followed by selection of specific subcarriers. For example, if transform precoding is enabled for a PUSCH, the DFT size is modified as for symbol (s) with UL resource muting. The modulated symbols are transformed to the frequency domain with a DFT of size and the result is mapped to the unmuted scheduled subcarriers. In another example, the DFT size is for symbol (s) with UL resource muting. The block of modulated symbols is repeated before DFT. After DFT, the non-zero even-indexed subcarriers are extracted and then mapped to the unmuted scheduled subcarriers. The block of modulated symbols is extended to modulated symbols by inserting ‘0’ after every modulated symbol. After DFT, the first subcarriers are extracted and then mapped to the unmuted scheduled subcarriers. is the total number of subcarriers of the PUSCH. Above options are mathematically equivalent.
[0062] While these options are mathematically equivalent concerning the DFT output for the unmuted subcarriers, the manner in which the input symbols are selected or generated can lead to issues with the π / 2-BPSK modulation.
[0063] Other issues addressed in this document related to UL muting include the following issues: how to support UL resource muting in DFT-s-OFDM symbols containing phase tracking reference signal (PT-RS) , and transport block size (TBS) determination when the UL resource muting is applied.
[0064] FIG. 5 is a signaling diagram 500 illustrating communications between a UE 102 and a network entity 104 for PUSCH repetitions with OCC according to an embodiment. The UE 102 optionally transmits 502 and the network entity 104 optionally receives 502 a UE capability message indicating support for at least one of:applying OCC over PUSCH repetitions, a length of an OCC sequence, OCC sequence repetition, OCC sequence cycling, OCC sequence repetition over orphan repetitions, PUSCH types with OCC, DCI formats, or a maximum number of PUSCH repetitions with OCC. In some aspects, the UE capability message may include information on whether the UE supports OCC (e.g., per band, per band combination) , supported OCC length, supported DCI format for scheduling PUSCH with OCC, or supported PUSCH types with OCC (e.g., Type 1 or Type 2 configured grant (CG) PUSCH, or dynamic grant (DG) PUSCH scheduled by DCI format 0_0 / 0_1 / 0_2 / 0_3) . The UE capability can also report the maximum number of repetitions the UE can handle with OCC applied.
[0065] The network entity 104 (e.g., based on the received UE capabilities) transmits 504 and the UE receives 504 a configuration for PUSCH including repetition information and OCC information. In some aspects, the OCC indication is indicated by using legacy fields in the current format (e.g., time-domain resource allocation (TDRA) , demodulation reference signal (DMRS) ports, etc. ) . In some aspects, the network entity may configure the OCC length and / or OCC sequence associated with one or multiple TDRA code-point (e.g., by RRC signaling) and indicate one of the TDRA code-points by the DCI scheduling the PUSCH. In some aspects, the OCC indication is indicated by using a new field in the DCI format (e.g., DCI format 0_0 / 0_1 / 0_2 / 0_3) . In one example, for OCC indication based on DCI format 0_3, the network entity may indicate the common or separate OCC for the scheduled PUSCH from the scheduled serving cells by common or separate DCI field. For example, the network entity may configure a list of available OCC length (s) and / or OCC sequence (s) indexed by the RRC signaling, and then use the DCI to indicate one of the OCC lengths and / or OCC sequences to the UE. In another example, the network entity may indicate the OCC sequence based on the OCC length configured by RRC signaling. In some aspects, the network entity may configure whether the OCC indication is present for DCI format (e.g., DCI format 0_1 / 0_2 / 0_3 by common or separate RRC parameters) . The network entity may provide the RRC parameter (s) per bandwidth part, per serving cell or serving cell group. In some aspects, the network entity may refrain from scheduling the PUSCH with OCC by one or multiple of the DCI format (e.g., DCI format 0_0 / 0_1 / 0_2 / 0_3) . The network entity can activate / deactivate PUSCH repetitions with OCC. The activation / deactivation can be per configured grant, per carrier, or per BWP. In addition, the UE may determine the applied OCC sequence, the resource mapping rules, and collision handling rules, based on at least an uplink enhancement factor or the configuration for uplink transmission.
[0066] The UE 102 applies 505 an OCC sequence associated with the OCC information to PUSCH repetitions associated with the repetition information. In some aspects, the PUSCH repetitions have a first length, and the OCC sequence has a second length. The first length of the PUSCH repetitions indicates at least one of: actual PUSCH repetitions, nominal PUSCH repetitions, or a number of slots scheduled for the PUSCH repetitions. In some aspects, applying the OCC sequence includes OCC sequence repetition or OCC sequence cycling over the PUSCH repetitions, where the first length is greater than the second length, and the first length is an integer multiple of the second length. In some aspects, applying the OCC sequence includes OCC sequence repetition over orphan PUSCH repetitions, where the first length is greater than the second length, and the first length is not an integer multiple of the second length.
[0067] The network entity 104 may optionally transmit 506 and the UE 102 may optionally receive 506 a control signal (e.g., DCI) scheduling the PUSCH repetitions with the OCC.
[0068] The UE 102 transmits 508 and the network entity receives 508 PUSCH repetitions based on at least one of: a length of the OCC sequence different from a length of the PUSCH repetitions, a collision between a PUSCH repetition and another transmission, different power control configurations for the PUSCH repetitions, or UL resource muting. If the UE is indicated (e.g., by a DCI, DCI format 0_0 / 0_1 / 0_2 / 0_3) to transmit PUSCH repetitions with OCC, the UE transmits PUSCH repetition with OCC according to DCI and the PUSCH repetitions and OCC configuration configured by the BS. If the UE is configured to transmit PUSCH repetitions with OCC, the UE transmits PUSCH repetition with OCC according to the PUSCH repetitions and OCC configuration configured by the network entity, and discussed further herein.
[0069] In some aspects, the first length is greater than the second length, and the first length is not an integer multiple of the second length, in such instances, the UE may drop the PUSCH repetitions that exceed a value of the length of the second length and update the first length of the PUSCH repetitions to equal to the second length, where application of the OCC sequence occurs over the updated first length of the PUSCH repetitions. In some aspects, the first length is less than the second length, where the updated first length of the PUSCH repetitions equals the second length, such that the UE may update the updated first length of the PUSCH repetitions to match the second length of the OCC sequence.
[0070] In some aspects, the repetition information includes PUSCH repetition with slot counting, where the transmitting the PUSCH repetitions includes transmitting the PUSCH repetitions based on a determination whether allocated resources for the PUSCH repetitions are available.
[0071] In some aspects, the repetition information includes PUSCH repetition with slot counting and allocated resources for the PUSCH repetitions are unavailable, in such instances, the transmitting the PUSCH repetitions includes transmitting the PUSCH repetitions based on a determination of whether a phase continuity is maintained.
[0072] In some aspects, the UE may stop transmission of the PUSCH repetitions when at least one PUSCH repetition overlaps a downlink or uplink transmission having a higher priority.
[0073] In some aspects, a first length of the PUSCH repetitions is greater than a second length of the OCC sequence, where at least one PUSCH repetition overlaps a downlink or uplink transmission having a higher priority than the PUSCH repetitions. In such instances, the UE may transmit non-overlapping PUSCH repetitions based on a number of the non-overlapping PUSCH repetitions being greater than the second length of the OCC sequence and the at least one PUSCH repetition that overlaps is a last repetition of the PUSCH repetitions.
[0074] In some aspects, different power control configurations may be configured for different subsets of time domain resources. In such instances, the UE may at least one of: transmit the PUSCH repetitions within an OCC group, drop transmission of one or more of the PUSCH repetitions within the OCC group, drop transmission of all the PUSCH repetitions, transmit the PUSCH repetition within the OCC group in a next available slot, or transmit the PUSCH repetition within the OCC group with a consistent power or a consistent phase.
[0075] In some aspects, a power control configuration may be configured for the PUSCH repetitions. In such instances, the UE may transmit or drop a subset of or all the PUSCH repetitions with the OCC when the UE lacks a power consistency or a phase continuity.
[0076] In some aspects, the configuration further configures a DFT-s-OFDM waveform for the PUSCH and the UL resource muting. In some aspects, the configuration configures the DFT-s-OFDM waveform and the UL resource muting with the OCC information.
[0077] In some aspects, the configuration further configures a π / 2 BPSK modulation scheme for the PUSCH. In such instances, the UE may generate first complex-valued modulation symbols associated with the π / 2 BPSK modulation scheme based on DFT samples before applying the UL resource muting, generate second complex-valued modulation symbols associated with the π / 2 BPSK modulation scheme based on the on the DFT samples after applying the UL resource muting, refrain from using the π / 2 BPSK modulation scheme for the PUSCH repetitions with the UL resource muting, or replace an index i, associated with complex-valued modulation symbols of the π / 2 BPSK modulation scheme, with i / 2 for the PUSCH repetitions with the UL resource muting.
[0078] In some aspects, the configuration configures the UL resource muting with the PUSCH repetitions. In such instances, the UE may refrain from applying the UL resource muting on symbols with PT-RS or with a waveform; apply the UL resource muting on symbols with a PT-RS with a DFT-s-OFDM waveform; apply the UL resource muting to at least one PUSCH symbol and refraining from transmitting a PT-RS on the at least one PUSCH symbol, a PUSCH transmission occasion, or an entire PUSCH; or refrain from transmitting a PT-RS on symbols with a DFT-s-OFDM waveform when an OFDM symbol comprises the UL resource muting.
[0079] In some aspects, the UE may determine a TBS for a number of REs allocated for PUSCH based on at least one of: removal of a number of muted REs allocated for the PUSCH within a physical resource block (PRB) , a pre-configured number of muted REs are applied when the UL resource muting is applied on a PUSCH allocation, or removal of the muted REs from a final number of the REs allocated for the PUSCH.
[0080] FIG. 6 is a diagram 600 illustrating an example of an OCC sequence repetition according to an embodiment. Assume a UE is scheduled to transmit a first length of PUSCH repetitions with a second length OCC sequence. The first length of PUSCH repetitions may indicate the actual PUSCH repetitions or nominal PUSCH repetitions (e.g., number of repetitions configured or indicated for the PUSCH) , or the number of slots that scheduled for the PUSCH repetition (e.g., the first length can be different from the number of repetitions) .
[0081] Diagram 600 of FIG. 6 illustrates a method when the first length is larger than the second length, and the first length is an integer multiple of the second length, where the UE applies the indicated OCC sequence repeatedly to the PUSCH repetitions. As shown in diagram 600 of FIG. 6, the UE is scheduled to transmit a length-8 PUSCH repetitions 626 with a length-4 OCC sequence with 2nd OCC sequence as shown in diagram 300 of FIG. 3 (e.g., index 2, OCC sequence {1, -1, 1, -1} ) . The UE applies the 1st OCC sequence to the first 4 (e.g., OCC repetitions 1 628) and last 4 PUSCH repetitions (e.g., OCC repetitions 2 630) , respectively. In some implementations, the network entity combines the first 4 and last 4 PUSCH repetitions, and then resolves the OCC. In other implementations, the network entity resolves the length-8 PUSCH repetitions with OCC directly.
[0082] FIG. 7 is a diagram 700 illustrating an example of an application of OCC pattern cycling according to an embodiment. Diagram 700 of FIG. 7 illustrates a method in a scenario where the first length is larger than the second length, and the first length is an integer multiple of the second length. The UE applies OCC sequence in a configured patterns to the PUSCH repetitions 726. Assume the OCC sequence cycling pattern (e.g., OCC cycling 1 732, OCC cycling 2 734) follows the OCC sequence order in diagram 300 of FIG. 3 (e.g., {1st, 2nd, 3rd, 4th} ) or a configured OCC sequence order (e.g., {2nd, 1st, 4th , 3rd} ) , which can be specified in the standard or configured / indicated by the network entity. Assume the cycling pattern {1st, 2nd, 3rd, 4th} is applied or configured, and a UE is scheduled, by the network entity, to transmit a length-8 PUSCH repetitions with a starting OCC sequence index 2 (e.g., OCC sequence {1, -1, 1, -1} ) . Then the UE applies the 2nd OCC sequence to the first 4 PUSCH repetitions, and applies the 3rd OCC sequence to the following 4 PUSCH repetitions, according to the OCC sequence cycling pattern. Likewise, if the scheduled PUSCH repetition has a length of 16, the UE applies the 2nd, 3rd, 4th, and 1st OCC sequence to each 4 repetitions in the 16 repetitions.
[0083] FIG. 8 is a diagram 800 illustrating an example of an application of OCC sequence repetition in orphan repetitions according to an embodiment. Diagram 800 of FIG. 8 illustrates a method in a scenario where the first length is larger than the second length, and the first length is not an integer multiple of the second length. For example, the network entity schedules a UE to transmit a length-6 PUSCH repetitions 826 with a length-4 OCC. In this case, 6 modulo 4 equals to 2, whereby repetitions 1-4 are within the OCC repetition 1 836 and repetitions 5 and 6, within OCC repetition 2 838, are orphan repetitions for the OCC operation. In such instances, the UE applies the OCC sequence repetition as described in connection with diagram 600 of FIG. 6, except that the UE applies the 1st and 2nd OCC code bits of the same OCC sequence to the orphan repetition 5 and 6, respectively. Likewise, if the length of PUSCH repetition is 7 and the OCC sequence length is 4, the UE applies the 1st, 2nd, and 3rd OCC code bits of the same OCC sequence to the orphan repetition 5, 6, and 7, respectively.
[0084] FIG. 9 is a diagram 900 illustrating an example of dropping orphan repetitions for OCC according to an embodiment. Diagram 900 of FIG. 9 shows a method in a scenario where the first length is larger than the second length, and the first length is not an integer multiple of the second length. For example, the network entity schedules a UE to transmit a length-6 PUSCH repetitions 926 with a length-4 OCC, such that repetitions 1-4 are within OCC repetition 1 940 while repetition 5 and 6 are orphan repetitions, similarly as discussed in connection with diagram 800 of FIG. 8. In such instances, the UE drops the orphan repetitions (e.g., repetition 5 and 6) , thus the actual length of PUSCH repetition becomes an updated first length of 4. The UE then applies the methods discussed in connection with diagram 600 of FIG. 6 (e.g., OCC sequence repetition) and diagram 700 of FIG. 7 (e.g., OCC pattern cycling) . Likewise, if the scheduled PUSCH repetition has a length of 15 and the indicated OCC length is 4. The number of orphan repetition is 3 (15 modulo 4 equals to 3) , then the UE drops the last 3 repetitions to make sure the actual transmitted PUSCH repetition length (e.g., updated first length = 12) is an integer multiple (3) of the second length equals 4.
[0085] In some aspects, when the first length is not an integer multiple of the second length, whether to drop or transmit the orphan PUSCH repetitions as discussed in connection with diagram 800 of FIG. 8 or diagram 900 of FIG. 9 may be pre-defined or configured / indicated by the base station via RRC signaling or MAC-CE or DCI (e.g., DCI scheduling the PUSCH) or reported by the UE (e.g., via UE capability) . In one example, for CG-PUSCH (e.g., Type1 or Type2 CG-PUSCH) , when the first length is not an integer multiple of the second length, the UE may drop the orphan PUSCH repetitions. For DG-PUSCH, the network entity may indicate whether the UE should drop or transmit the orphan PUSCH repetitions by the scheduling DCI when the first length is not an integer multiple of the second length.
[0086] FIG. 10 is a diagram 1000 illustrating an example of a repetition length being less than an OCC length according to an embodiment. Diagram 1000 of FIG. 10 illustrates a scenario where the first length is shorter than the second length. In some aspects, the UE updates the repetition length to an updated first length that equals to the second length (e.g., rounded up to the OCC length) . Then the UE transmits the the updated first length PUSCH repetitions with the second length OCC. As the example shown in diagram 1000 of FIG. 10, the network entity schedules a length-2 PUSCH repetitions 1026 with length-4 OCC to a UE, and the UE applies length-4 PUSCH repetitions (e.g., OCC repetition 1 1042) to match the OCC length.
[0087] In some aspects, for the scenario where the first length is larger than the second length, but the first length is not an integer multiple of the second length. The UE can update the first length to an updated first length equal to the smallest integer multiple of the second length that is larger than the first length (e.g., rounded up to the next multiple of the OCC length) . For example, the base station schedules, to the UE, a length-7 PUSCH repetitions with a length-4 OCC sequence. The number of repetitions is rounded up to 8 instead of 7 to match a multiple of the length-4 OCC sequence. Then the UE transmits the length-8 PUSCH repetitions with OCC.
[0088] In some aspects, the UE drops the entire PUSCH repetitions if the first length is smaller than the second length.
[0089] In some aspects, when the first length is smaller than the second length, whether to drop or transmit the PUSCH repetitions may be pre-defined or configured / indicated by the network entity via RRC signaling or MAC-CE or DCI (e.g., DCI scheduling the PUSCH) or reported by the UE (e.g., via UE capability) . For example, for CG-PUSCH (e.g., Type1 or Type2 CG-PUSCH) , when the first length is smaller than the second length, the UE may drop the orphan PUSCH repetitions. For DG-PUSCH, the network entity may indicate whether the UE should drop or transmit the orphan PUSCH repetitions by the scheduling DCI when the first length is smaller than the second length.
[0090] In some aspects, the network entity may refrain from configuring or indicating the first length of PUSCH repetitions with the second length of OCC, where the first length is not the same as the second length or a multiple of the second length. This may be applicable for Type1 or Type2 CG-PUSCH or DG-PUSCH.
[0091] FIG. 11 is a flow diagram 1100 illustrating an example of PUSCH repetition with slot counting and OCC according to an embodiment. In some aspects, the network entity can configure UE to perform PUSCH repetition with slot counting. If the UE identifies that a repetition of the scheduled PUSCH repetitions is not applicable to transmit due to collision handling, for example, collides with transmissions with higher priority, synchronization signal block and physical broadcast channel (SSB / PBCH) , PDCCH of Type0-common search space (Type0-CSS) , etc., the UE postpones the repetition to the next available resource. To maintain the OCC orthogonality, the network entity may provide common configurations for slot counting for the co-scheduled UEs. Thus, the co-scheduled UEs determine common available slots for uplink transmission.
[0092] Flow diagram 1100 of FIG. 11 shows a UE behavior flow diagram in a scenario where the network entity configures the UE to apply PUSCH repetition with slot counting and OCC. The UE receives 1144 a schedule to transmit PUSCH repetitions with OCC. The UE determines 1146 whether the allocated resource for the PUSCH repetition is available or not. If the allocated resource is available (e.g., Yes branch) , the UE transmits 1154 the PUSCH repetition with OCC. Otherwise, if the allocated resources are not available (e.g., No branch) the UE identifies 1148 available resources for the PUSCH repetitions. The UE determines 1150 whether the phase continuity can be maintained for transmitting the PUSCH repetition with OCC (e.g., based on the gap due to postpone a repetition, and DMRS bundling rules) . If the phase continuity can be maintained for transmitting the PUSCH repetitions with OCC (e.g. Yes branch) , the UE transmits 1154 the PUSCH repetition with OCC. If the phase continuity cannot be maintained for transmitting the PUSCH repetition with OOC (e.g., No branch) , the UE stops 1152 the transmission of the PUSCH repetitions with OCC. In some aspects, UE may stop or drop 1152 the transmission of the PUSCH repetitions that cannot maintain the phase continuity, or the transmission of the PUSCH repetitions within an OCC group including the PUSCH repetition that cannot maintain the phase continuity, or the transmission of all the PUSCH repetitions.
[0093] FIG. 12 is a flow diagram 1200 illustrating an example of a collision of PUSCH repetition with OCC and a transmission / configuration with a higher priority according to an embodiment. For example, a high priority transmission / configuration may refer to a dynamic scheduled DL / UL transmission (e.g., PDSCH, PDCCH, PUSCH, PUCCH, SSB / PBCH, reference signals) , a semi-static configured DL / UL transmission with high priority indication, a non-applicable transmission directions configured by the base station (e.g., symbol types “uplink, downlink, flexible, SBFD, and non-SBFD” from time division duplex (TDD) patterns) or a time duration that the UE is unable to transmit (e.g., antenna switching gap) . Flow diagram 1200 of FIG. 12 shows a UE behavior flow diagram in a collision scenario. The UE receives 1256 a schedule to transmit PUSCH repetitions with OCC. The UE identifies 1258 that at least one repetition of the PUSCH repetition with OCC overlaps with another scheduled or configured DL / UL transmission with a higher priority or a slot / symbol indicated as DL according to TDD patterns configuration. The UE stops 1260 the transmission of the PUSCH repetition with OCC. In some aspects, if the UE is scheduled / configured to receive / transmit the DL / UL transmission with a higher priority, the UE receives / transmits 1262 the DL / UL transmission with a higher priority.
[0094] FIG. 13 is a flow diagram 1300 illustrating an example of postponement of an OCC bit of collided PUSCH repetition to a subsequent non-collided PUSCH repetition according to an embodiment. Flow diagram 1300 of FIG. 13 shows the UE behavior flow diagram in another collision scenario. The UE receives 1364 a schedule to transmit a PUSCH repetition with OCC, where the number of repetitions is larger than the second length of OCC sequence. The UE identifies 1366 that at least one repetition of the PUSCH repetitions with OCC overlaps with a DL / UL transmission which has a higher priority or a slot / symbol indicated as DL according to TDD patterns configuration. The UE determines 1368 whether the number of non-overlapped repetitions of the PUSCH repetitions with OCC is larger than the OCC length. If the number of non-overlapped repetitions is not larger than the OCC length (e.g., No branch) , then the UE stops 1370 the transmission of the PUSCH repetition with the OCC. If the number of non-overlapped repetitions is larger than the OCC length (e.g., Yes branch) , the UE then determines 1372 whether the overlapped repetition is the last repetition of the PUSCH repetitions with the OCC. If the overlapped repetition is the last repetition of the PUSCH repetitions with the OCC (e.g., Yes branch) , then the UE drops 1374 the transmission of the overlapped repetition. If the overlapped repetition is not the last repetition of the PUSCH repetitions with the OCC (e.g., No branch) , the UE applies 1376 the OCC bit of the overlapped repetition to the next non-overlapped repetition and transmits the PUSCH repetition with the OCC. In some aspects, after the UE applies 1376 the OCC bit of the overlapped repetition to the next non-overlapped repetition, the UE may determine whether phase continuity may be maintained, as discussed in connection with diagram 1100 of FIG. 11. For example, after the UE applies 1376 the OCC bit of the overlapped repetition to the next non-overlapped repetition, the UE determines 1150 whether the phase continuity can be maintained for transmitting the PUSCH repetition with OCC (e.g., based on the gap due to postpone a repetition, and DMRS bundling rules) . If the phase continuity can be maintained for transmitting the PUSCH repetitions with OCC (e.g. Yes branch) , the UE transmits 1154 the PUSCH repetition with OCC. If the phase continuity cannot be maintained for transmitting the PUSCH repetition with OOC (e.g., No branch) , the UE stops 1152 the transmission of the PUSCH repetitions with OCC.
[0095] FIG. 14 is a diagram 1400 illustrating an example of postponement of an OCC bit of collided PUSCH repetition to a subsequent non-collided PUSCH repetition according to an embodiment. Diagram 1400 of FIG. 14 shows an example of applying method discussed in connection with flow diagram 1300 of FIG. 13 with the method discussed in connection with diagram 600 of FIG. 6 and diagram 800 of FIG. 8. As shown in diagram 1400 of FIG. 14, the UE is not able to transmit the repetition 4 1478 of the PUSCH repetitions with OCC due to collision handling (e.g., collision 1484) , thus the UE applies the original OCC bit of repetition 4 1478 to the repetition 5 1480, and applies the original OCC bit of repetition 5 1480 to repetition 6 1482.
[0096] In some aspects, the network entity configures a first and a second UL transmission configurations to a first and second subsets of time domain resources, respectively. In some aspects, the network entity indicates to the UE that a transmission can be transmitted in either the first or the second subset of time domain resources. When the base station schedules the UE to transmit a PUSCH repetition with OCC, where the first length of PUSCH repetition is larger than the second length of the OCC, the UE determines the number of repetitions in the first and second subset of time domain resources as K and L, respectively. If K is larger than the second length and L is smaller than the second length, the UE determines to transmit repetitions of PUSCH repetition with OCC in the first subset of time domain resources. In some aspects, if L is larger than the second length and K is smaller than the second length, the UE determines to transmit repetitions of PUSCH repetitions with OCC in the second subset of time domain resources. If both K and L are larger than the second length, the UE determines to transmit repetitions of PUSCH repetition with OCC in a subset of time domain resources with larger number of repetitions (e.g., 1st subset if K>L, and 2nd subset if L>K) . If both K and L are smaller than the second length, the UE stops the transmission of the PUSCH repetition with OCC.
[0097] In some aspects, if the UE determines to drop at least one repetition of the repetitions within an OCC group (e.g., repetition 1 / 2 / 3 / 4 in diagram 1400 of FIG. 14 are in one OCC group) , the UE may transmit all the repetitions in the OCC group from the next available slots (e.g., transmitting the repetition 1 / 2 / 3 / 4 in the resource starting from the repetition 5 in diagram 1400 of FIG. 14) .
[0098] In some aspects (e.g., SBFD) , the network entity may configure separate power control configurations to different subsets of time domain resources (e.g., slot and symbol indexes) . The network entity may indicate to the UE that a transmission can be transmitted in a first subset and a second subset of time domain resources. If the UE is to transmit a PUSCH repetition with OCC crossing slots / symbols with a first power control configuration and a second power configuration, the UE may apply at least one of the following to determine the transmission power for the scheduled PUSCH repetition with OCC: the UE applies the power control configuration of the first available repetition of the PUSCH repetition with OCC, the UE applies the power control configuration which indicates a larger transmission power, or the UE applies the power control configuration which indicates a smaller transmission power.
[0099] In some aspects, the network entity indicates one of the power control configurations from the first and second power control configuration to the UE for the cross transmission case. The UE applies the indicated power control configuration for the PUSCH repetitions with OCC. The indication can be implemented by RRC signaling, downlink control information (DCI) , or MAC control element (MAC CE) .
[0100] In some aspects, the network entity configures a third power control configuration for the cross transmission case or PSUCH repetition with OCC. The UE applies the third power control configuration for the PUSCH repetitions with OCC.
[0101] In some aspects, when UE is unable to maintain the power consistency or phase continuity for PUSCH repetitions within an OCC group, the UE may apply at least one of the following: transmit the PUSCH repetitions within the OCC group, drop the PUSCH repetition (s) within the OCC group, drop all the PUSCH repetitions, transmit the PUSCH repetition (s) within the OCC group in the next available slots, or transmit the PUSCH repetitions within the OCC group with consistent power and / or consistent phase (e.g., drop the remaining repetitions with power consistency or phase continuity issues) . In some aspects, a consistent power may refer to maintaining a transmit power for the PUSCH repetitions. In some aspects, a consistent phase may refer to maintaining phase continuity for the PUSCH repetitions.
[0102] In some aspects, the network entity may configure or indicate one of the above options for the UE determine how to transmit the PUSCH, via RRC signaling or MAC-CE or DCI (e.g., DCI scheduling the PUSCH) . In some aspects, for Type1 or Type2 CG-PUSCH, the UE behavior based on one of the above options may be pre-defined or configured via RRC signaling, and for DG-PUSCH, the UE behavior based on one of the above options may be indicated by the DCI scheduling the PUSCH.
[0103] In some aspects, if the network entity indicates the UE to apply UL muting (e.g., comb-2 muting) on some indicated time domain resources, the scheduled frequency resource for PUSCH transmission may not fit the applicable DFT precoding component of the UE. For example, the DFT size is based on the number of RBs, which should fulfill the condition of MRB= (2a) × (3b) × (5c) , where a, b, and c are non-negative integers, and the MRB is the size of the DFT in number of resource blocks (RB) . To solve the problem, the following solutions can be applied.
[0104] In some implementations, a UE supports a 2nd DFT size with comb-2 UL muting. In one example, the UE may support a DFT size of: Msc= 12× (2a) × (3b) × (5c) where Msc the size of the DFT in number of subcarriers (RE) , and a, b, and c are non- negative integers. In another example, the UE may support a DFT size of multiple of 1.5 and 2.5. Then, the UE indicates / reports, to the network entity, that it supports a DFT size with UL muting (e.g., comb-2) , in the UE capability. Then the network entity can schedule PUSCH transmissions with a size according to current specification. Then the UE transmits the PUSCH in DFT-s-OFDM waveform with UL muting by applying the supported DFT size. In one example, the UE may report the UE capability indicating it supports one of the followings for DFT-s-OFDM based PUSCH with comb-2 UL resource muting: number of scheduled RBs for the PUSCH as the followings: MRB= 2× (2a) × (3b) × (5c) or MRB / 2 = (2a) × (3b) × (5c) , or number of subcarriers for the PUSCH as the followings: Msc= 6× (2a) × (3b) × (5c) .
[0105] In some aspects, the network entity may refrain from scheduling the DFT-s-OFDM based PUSCH with comb-2 UL resource muting with the number of scheduled RBs that does not fulfill at least one of the conditions: MRB= 2× (2a) × (3b) × (5c) or MRB / 2 = (2a) × (3b) × (5c) , or number of subcarriers for the PUSCH as the followings: Msc= 6× (2a) × (3b) × (5c) .
[0106] In some aspects, the UE indicates, to the network entity, that the UE supports DFT-s-OFDM with UL muting with puncturing. The UE will apply a DFT size according to the current specification, with a largest frequency resource that is smaller than the frequency resource scheduled PUSCH. The UE drops the frequency resource of the scheduled PUSCH that exceeds the frequency range after apply resource mapping (RE interlaced comb-type mapping) of the UL resource muting.
[0107] In some aspects, the UE indicates, to the network entity, that the UE supports DFT-s-OFDM with UL muting with DFT outcome cyclic prefix. Similar to the above implementation, instead of mapping 0 to the frequency resource that is larger than the supported DFT size, the UE maps a subset of the DFT precoding output to the exceeded part of the frequency resource of the scheduled PUSCH. For example, the subset of the DFT precoding outcome can be a subset of lowest indexed or highest indexed frequency resource from the DFT precoding outcome.
[0108] In aspects where the UE is configured, by the network entity, to transmit PUSCH with DFT-s-OFDM waveform, UL resource muting, PUSCH repetition with OCC. If the UE identified that at least one repetition of the PUSCH repetition with OCC is allocated in a symbol indicated for UL resource muting, the UE applies the UL resource muting to all the repetitions of the PUSCH repetition with OCC.
[0109] In some aspects, the network entity may configure / indicate the UE to transmit PUSCH with UL muting (e.g., comb-2 muting) and OCC. The network entity may configure / indicate the same UL muting pattern for PUSCH repetitions within an OCC group. The UE may apply the same UL muting pattern for the PUSCH repetitions within an OCC group. For example, if the UE apply UL muting for one PUSCH repetition, it may apply the same UL muting for all the PUSCH repetitions within an OCC group. In some aspects, the UE may drop one or multiple PUSCH repetitions within an OCC group if the UL muting pattern for the PUSCH repetitions are different or if UL muting is applied on some PUSCH repetitions and not applied on some other PUSCH repetitions. In some aspects, the UE may transmit the PUSCH repetitions within an OCC group in the next available slots if the UL muting pattern for the PUSCH repetitions are different.
[0110] It can be specified that the UE is expecting all PUSCH repetitions to have the same UL muting pattern applied or the same number of muted REs. The first PUSCH repetition can be considered as the reference and the following PUSCH repetitions should follow the first PUSCH repetition (e.g., if the UE is scheduled with a first PUSCH repetition with UL muted REs) the UE expects the following PUSCH repetitions to have the same UL muted REs or the same number of UL muted REs.
[0111] In some aspects, a PUSCH with repetitions is not expected to overlap with UL muting symbols. A PUSCH repetition overlapping with UL muting symbols is dropped.
[0112] In some aspects, UL resource muting is not applied to PUSCH transmissions when they are scheduled by a single DCI. For example, a new semi-static signalling (e.g., RRC) or dynamic signaling (e.g., DCI, MAC-CE) configures / activates / de-activates UL resource muting on the multiple PUSCHs scheduled by a single DCI. In another example, in the multiple PUSCHs scheduled by a single DCI, UL resource muting is applied on the subset of PUSCHs in the SBFD symbols / slots and not applied on the subset of PUSCHs on the non-SBFD symbols / slots. In yet another example, the multi-PUSCHs scheduled by a single DCI follow the same rules applied to PUSCH repetitions type A or type B.
[0113] In some aspects, PUSCH repetitions can overlap with UL muting symbols. PUSCH repetitions will have the same number of resource allocations and rate matching is used on PUSCHs with UL muted REs.
[0114] In some aspects, the network entity may refrain from configuring / indicating the UE to transmit PUSCH with UL muting (e.g., comb-2 muting) and OCC. For example, the network entity may refrain from configuring / indicating the UE to transmit PUSCH with OCC and configuring SBFD (e.g., in the same serving cell) .
[0115] In some aspects, such as π / 2-BPSK for PUSCH / PTRS, if complex symbols are selected with even indices, for example like complex symbols with even indices or with odd indices like for example then the π / 2-BPSK complex valued symbol would change into a BPSK complex valued symbol and this is because the index i is even and is equal to (hence i mod 2 is always 0) and there would be no π / 2 phase rotation.
[0116] At least one of the following solutions can be specified to address this issue: (option 1) the index i for PUSCH and position m for PT-RS is based on the DFT samples before muting. For example taking the first complex symbols (e.g., ) ; (option 2) the index i for PUSCH and position m for PT-RS is based on the DFT samples after muting. For example taking the first DFT symbols after the muting (e.g., unmuted positions) ; (option 3) π / 2-BPSK modulation is not used for PUSCH with UL resource muting; or (option 4) index i for π / 2-BPSK complex is replaced with i / 2 when UL resource muting is used with PUSCH / PTRS using pi / 2 BPSK modulation.
[0117] The challenge of applying UL resource muting to DFT-s-OFDM symbols that also carry PT-RS necessitates careful consideration to avoid degrading phase error estimation and tracking performance.
[0118] One approach involves adapting PT-RS insertion for symbols subject to muting by effectively reducing the number of PT-RS groups within the pre-transform precoding block of samples. Another proposal suggests that UL resource muting should not be applied at all to PUSCH symbols containing PT-RS, thereby prioritizing the integrity of phase tracking. This aims to minimize any impact on channel estimation. Further refinements suggest that such a restriction on muting PT-RS symbols might be particularly pertinent for Frequency Range 2 (FR2) operations or could involve mechanisms for dynamically activating or deactivating UL resource muting on these specific symbols as needed. UL resource muting and / or UL resource muting on PT-RS symbols can be configured and / or activated / de-activated per cell, per UE, per carrier, per BWP, per frequency band, per waveform, per numerology, …etc. UL resource muting and / or UL resource muting on PT-RS symbols can be configured separately for DG-PUSCH and for Type 1 / 2 CG-PUSCH (e.g., two different RRC parameters are activating / de-activating the muting on DG PUSCH and CG PUSCH) . Some specific DCI formats can be used to enable / disable the UL resource muting and / or UL resource muting on PT-RS symbols. A new / existing bit-field in DCI 0_1 / 0_2 / 1_0 / 1_2 can be specified to enable / disable the UL resource muting and / or UL resource muting on PT-RS symbols.
[0119] In some aspects, a semi-static signalling (e.g., RRC) or dynamic signalling (e.g., DCI, MAC-CE) can be indicated by the network to the UE to indicate if PT-RS or UL muting should be applied in a specific symbol or a slot with transform precoding. For example, if there is overlapping between PT-RS symbols and UL resource muting, a different PT-RS pattern or a different PT-RS density is applied on symbols with UL resource muting. In another example, if PT-RS is present on a symbol with UL resource muting applied on the symbol, the UL resource muting pattern is specified to occupy REs that do not overlap with the PT-RS samples using additional specified rules / mappings.
[0120] In some aspects, if UL resource muting is not supported on non-SBFD symbols / slots, the UE is not expecting to receive DCI indication or TDRA indication indicating or enabling muting on non-SBFD symbols. If the UE receives such indication, it will ignore it or it will drop the PUSCH transmission.
[0121] In some aspects, if UL resource muting is supported on non-SBFD symbols / slots, it can be configured and / or activated / de-activated per cell, per UE, per carrier, per BWP, per frequency band, per waveform, per numerology, etc. A new semi-static signalling (e.g., RRC) or dynamic signalling (e.g., DCI, MAC-CE, …) can be used to configure and / or activate de-activate the UL resource muting on non-SBFD symbols / slots. Different muting patterns and time / frequency locations can be used for the muting symbols on SBFD symbols / slots and non-SBFD symbols / slots. New UE capabilities can be defined to indicate to the network if muting on SBFD symbols / slots and / or muting on non-SBFD symbols / slots are supported by the UE.
[0122] In some aspects, UL resource muting can be applied in non-SBFD symbols if they meet certain conditions (e.g., they are configured as ‘flexible’s ymbols in the TDD UL / DL patterns) .
[0123] When transform precoding is enabled and an UL muting symbol overlaps a symbol containing PT-RS, for PT-RS insertion in a block of samples prior to transform precoding, and are determined as legacy; PT-RS sample positions are determined as legacy, but only for the first groups; or UL resource muting is not applied in the PUSCH symbol containing PT-RS.
[0124] At least one of the following may be specified to the challenge of applying UL resource muting to DFT-s-OFDM symbols that also carry PT-RS: UL resource muting is not applied on symbols with PT-RS for FR2 with DFT-s-OFDM, UL resource muting on symbols with PT-RS with DFT-s-OFDM is configured by the network and activated / de-activated semi-statically or dynamically (e.g., via RRC, DCI, MAC-CE) , when UL resource muting is applied to at least one of the PUSCH symbol, the UE does not transmit PT-RS on the PUSCH symbol or the PUSCH transmission occasion or the whole PUSCH, or PT-RS are not transmitted on symbols with DFT-s-OFDM when UL resource muting is applied on the OFDM symbol.
[0125] In some aspects, the UE may perform a TBS determination when the UL resource muting is applied. For the determination of the number of REs allocated for PUSCH, the UE may first determine the number of REs (NRE) within the slot: A UE first determines the number of REs allocated for PUSCH within a PRB (N'RE) by where is the number of subcarriers in the frequency domain in a physical resource block, is the number of symbols L of the PUSCH allocation for scheduled PUSCH or for configured PUSCH, is the number of REs for DM-RS per PRB in the allocated duration including the overhead of the DM-RS CDM groups without data, as described for PUSCH with a configured grant or as indicated by DCI format 0_1, 0_2 or 0_3 or as described for DCI format 0_0, and is the overhead configured by higher layer parameter xOverhead in PUSCH-ServingCellConfig. If the is not configured (avalue from 6, 12, or 18) , the is assumed to be 0. For Msg3 or MsgA PUSCH transmission the is always set to 0. In case of PUSCH repetition Type B, is determined assuming a nominal repetition with the duration of L symbols without segmentation.
[0126] A UE determines the total number of REs allocated for PUSCH (NRE) as follows: For TB processing over multiple slots, NRE=N*min (156, N′RE) ·nPRB where nPRB is the total number of allocated PRBs for the UE and N is the number of slots used for TBS determination indicated by numberOfSlotsTBoMS. Otherwise, NRE= min (156, N′RE) ·nPRB.
[0127] To take the muting into consideration the number of muted REs can be taken into consideration as below in the TBS determination formulas. In a first example, remove the number of muted REs allocated for PUSCH within a PRB. In such instances, the UE may first determine the number of REs (NRE) within the slot: A UE first determines the number of REs allocated for PUSCH within a PRB (N'RE) by where is the number of subcarriers in the frequency domain in a physical resource block, is the number of symbols L of the PUSCH allocation for scheduled PUSCH or for configured PUSCH, is the number of muted symbols in the PUSCH allocation is the number of REs for DM-RS per PRB in the allocated duration including the overhead of the DM-RS CDM groups without data, as described for PUSCH with a configured grant or as indicated by DCI format 0_1, 0_2 or 0_3 or as described for DCI format 0_0 in Clause 6.2.2, and is the overhead configured by higher layer parameter xOverhead in PUSCH-ServingCellConfig. If the is not configured (avalue from 6, 12, or 18) , the is assumed to be 0. For Msg3 or MsgA PUSCH transmission the is always set to 0. In case of PUSCH repetition Type B, is determined assuming a nominal repetition with the duration of L symbols without segmentation. A UE determines the total number of REs allocated for PUSCH (NRE) as follows: for TB processing over multiple slots, NRE=N*min (156, N′RE) ·nPRB where nPRB is the total number of allocated PRBs for the UE and N is the number of slots used for TBS determination indicated by numberOfSlotsTBoMS. Otherwise, NRE=min (156, N′RE) ·nPRB.
[0128] In a second example, higher layer fixed number may be applied when UL resource muting is enabled and is applied on the PUSCH allocation. In such instances, the UE shall first determine the number of REs (NRE) within the slot: the UE first determines the number of REs allocated for PUSCH within a PRB (N'RE) by where is the number of subcarriers in the frequency domain in a physical resource block, is the number of symbols L of the PUSCH allocation for scheduled PUSCH or for configured PUSCH, is the number of REs for DM-RS per PRB in the allocated duration including the overhead of the DM-RS CDM groups without data, as described for PUSCH with a configured grant or as indicated by DCI format 0_1, 0_2 or 0_3 or as described for DCI format 0_0, and is the overhead configured by higher layer parameter xOverhead in PUSCH-ServingCellConfig. is configured by higher layer and applied if UL resource muting is enabled and UL resource muting is applied on the PUSCH allocation. If the is not configured (avalue from 6, 12, or 18) , the is assumed to be 0. For Msg3 or MsgA PUSCH transmission the is always set to 0. In case of PUSCH repetition Type B, is determined assuming a nominal repetition with the duration of L symbols without segmentation. A UE determines the total number of REs allocated for PUSCH (NRE) as follows: for TB processing over multiple slots, NRE=N*min (156, N′RE) ·nPRB where nPRB is the total number of allocated PRBs for the UE and N is the number of slots used for TBS determination indicated by numberOfSlotsTBoMS. Otherwise, NRE=min (156, N′RE) ·nPRB.
[0129] In a third example, muted REs may be subtracted from the final number of PUSCH allocated REs. In such instances, the UE shall first determine the number of REs (NRE) within the slot: the UE first determines the number of REs allocated for PUSCH within a PRB (N'RE) by where is the number of subcarriers in the frequency domain in a physical resource block, is the number of symbols L of the PUSCH allocation for scheduled PUSCH or for configured PUSCH, is the number of REs for DM-RS per PRB in the allocated duration including the overhead of the DM-RS CDM groups without data, as described for PUSCH with a configured grant or as indicated by DCI format 0_1, 0_2 or 0_3 or as described for DCI format 0_0, and is the overhead configured by higher layer parameter xOverhead in PUSCH-ServingCellConfig.. If the is not configured (avalue from 6, 12, or 18) , the is assumed to be 0. For Msg3 or MsgA PUSCH transmission the is always set to 0. In case of PUSCH repetition Type B, is determined assuming a nominal repetition with the duration of L symbols without segmentation. A UE determines the total number of REs allocated for PUSCH (NRE) as follows: for TB processing over multiple slots, where nPRB is the total number of allocated PRBs for the UE and N is the number of slots used for TBS determination indicated by numberOfSlotsTBoMS. Otherwise,
[0130] In some aspects, the first, second, or third examples discussed above may be applied if the PUSCH is based on one or multiple of the following conditions, and legacy approach is applied, otherwise: number of scheduled PUSCH symbols (including / excluding DMRS) is below a threshold (e.g., 2-symbol or 4-symbol PUSCH) ; number of PUSCH symbols with muted REs (including / excluding DMRS) is above a threshold (e.g., 2-symbols are muted) ; or the ratio of the PUSCH symbols with muted REs to the total number of scheduled PUSCH symbols (including / excluding DMRS) is above a threshold (e.g., 0.5) .
[0131] For the TBS determination in one of the following cases: initial PUSCH transmission has muted REs and the PUSCH retransmission doesn’ t have muted REs; initial PUSCH transmission doesn’ t have muted REs and the PUSCH retransmission has muted REs; both initial PUSCH transmission and PUSCH retransmission have muted REs; both initial PUSCH transmission and PUSCH retransmission have muted REs but not the same amount of muted REs (e.g., not the same number of muted symbols) ; initial PUSCH transmission has muted REs and the PUSCH repetition doesn’ t have muted REs; initial PUSCH transmission doesn’ t have muted REs and the PUSCH repetition has muted REs; both initial PUSCH transmission and PUSCH repetition have muted REs; or both initial PUSCH transmission and PUSCH repetition have muted REs but not the same amount of muted REs (e.g., not the same number of muted symbols) . The TBS calculation is based on one of the following solutions: use the initial transmission / repetition to determine the TBS, assume no muted REs in the TBS calculation, or use the initial transmission / repetition to determine the TBS or assume no muted REs in the TBS calculation are applied under specific condition (s) (e.g., conditions on the muted REs ratio in PUSCH or number of PUSCH symbols with muted REs) .
[0132] FIG. 15 illustrates a flowchart 1500 of a method of wireless communication at a UE. With reference to FIGs. 1-14, the method may be performed by the UE 102.
[0133] The UE 102 optionally transmits 1502, to a network entity, a UE capability message indicating support for at least one of: applying OCC over the PUSCH repetitions, a length of an OCC sequence, OCC sequence repetition, OCC sequence cycling, OCC sequence repetition over orphan repetitions, PUSCH types with OCC, DCI formats, or a maximum number of PUSCH repetitions with OCC. For example, FIG. 5 shows that the UE 102 optionally transmits 502, to a network entity, a UE capability message indicating support for at least one of: applying OCC over the PUSCH repetitions, a length of an OCC sequence, OCC sequence repetition, OCC sequence cycling, OCC sequence repetition over orphan repetitions, PUSCH types with OCC, DCI formats, or a maximum number of PUSCH repetitions with OCC.
[0134] The UE 102 receives 1504, from the network entity, a configuration for PUSCH including repetition information and OCC information. For example, FIG. 5 shows that the UE 102 receives 504, from the network entity, a configuration for PUSCH including repetition information and OCC information.
[0135] The UE 102 applies 1505 an OCC sequence associated with the OCC information to PUSCH repetitions associated with the repetition information. For example, FIG. 5 shows that the UE 102 applies 505 an OCC sequence associated with the OCC information to PUSCH repetitions associated with the repetition information.
[0136] The UE 102 optionally receives 1506, from the network entity, a control signal scheduling the PUSCH repetitions with the OCC. For example, FIG. 5 shows that the UE 102 optionally receives 506, from the network entity, a control signal scheduling the PUSCH repetitions with the OCC.
[0137] The UE 102 transmits 1508, to the network entity, the PUSCH repetitions based on at least one of: a length of the OCC sequence different from a length of the PUSCH repetitions, a collision between a PUSCH repetition and another transmission, different power control configurations for the PUSCH repetitions, or UL resource muting. For example, FIG. 5 shows that the UE 102 transmits 508, to the network entity, the PUSCH repetitions based on at least one of: a length of the OCC sequence different from a length of the PUSCH repetitions, a collision between a PUSCH repetition and another transmission, different power control configurations for the PUSCH repetitions, or UL resource muting.
[0138] FIG. 16 is a flowchart 1600 of a method of wireless communication at a network entity. With reference to FIGs. 1-14, the method may be performed by one or more network entities 104, which may correspond to a base station or a unit of the base station, such as the RU 106, the DU 108, and / or the CU 110.
[0139] The network entity 104 optionally receives 1602, from a UE, a UE capability message indicating support for at least one of: applying OCC over the PUSCH repetitions, a length of an OCC sequence, OCC sequence repetition, OCC sequence cycling, OCC sequence repetition over orphan repetitions, PUSCH types with OCC, DCI formats, or a maximum number of PUSCH repetitions with OCC. For example, FIG. 5 shows that the network entity 104 optionally receives 502, from a UE, a UE capability message indicating support for at least one of: applying OCC over the PUSCH repetitions, a length of an OCC sequence, OCC sequence repetition, OCC sequence cycling, OCC sequence repetition over orphan repetitions, PUSCH types with OCC, DCI formats, or a maximum number of PUSCH repetitions with OCC.
[0140] The network entity 104 transmits 1604, to the UE, a configuration for PUSCH including repetition information and OCC information. For example, FIG. 5 shows that the network entity 104 transmits 504, to the UE, a configuration for PUSCH including repetition information and OCC information. An OCC sequence associated with the OCC information being applied over PUSCH repetitions associated with the repetition information.
[0141] The network entity 104 optionally transmits 1606, to the UE, a control signal scheduling the PUSCH repetitions with the OCC. For example, FIG. 5 shows that the network entity 104 optionally transmits 506, to the UE, a control signal scheduling the PUSCH repetitions with the OCC.
[0142] The network entity 104 receives 1608, from the UE, the PUSCH repetitions based on at least one of: a length of the OCC sequence different from a length of the PUSCH repetitions, a collision between a PUSCH repetition and another transmission, different power control configurations for the PUSCH repetitions, or UL resource muting. For example, FIG. 5 shows that the network entity 104 receives 508, from the UE, the PUSCH repetitions based on at least one of: a length of the OCC sequence different from a length of the PUSCH repetitions, a collision between a PUSCH repetition and another transmission, different power control configurations for the PUSCH repetitions, or UL resource muting.
[0143] FIG. 17 is a diagram 1700 illustrating an example of a hardware implementation for a UE apparatus 1702. The UE apparatus 1702 may be the UE 102, a component of the UE 102, or may implement UE functionality. The UE apparatus 1702 may include an application processor 1706, which may have on-chip memory 1706’ . In examples, the application processor 1706 may be coupled to a secure digital (SD) card 1708 and / or a display 1710. The application processor 1706 may also be coupled to a sensor (s) module 1712, a power supply 1714, an additional module of memory 1716, a camera 1718, and / or other related components.
[0144] The UE apparatus 1702 may further include a wireless baseband processor 1726, which may be referred to as a modem. The wireless baseband processor 1726 may have on-chip memory 1726'. Along with, and similar to, the application processor 1706, the wireless baseband processor 1726 may also be coupled to the sensor (s) module 1712, the power supply 1714, the additional module of memory 1716, the camera 1718, and / or other related components. The wireless baseband processor 1726 may be additionally coupled to one or more subscriber identity module (SIM) card (s) 1720 and / or one or more transceivers 1730 (e.g., wireless RF transceivers) .
[0145] Within the one or more transceivers 1730, the UE apparatus 1702 may include a Bluetooth module 1732, a WLAN module 1734, an SPS module 1736 (e.g., GNSS module) , and / or a cellular module 1738. The Bluetooth module 1732, the WLAN module 1734, the SPS module 1736, and the cellular module 1738 may each include an on-chip transceiver (TRX) , or in some cases, just a transmitter (TX) or just a receiver (RX) . The Bluetooth module 1732, the WLAN module 1734, the SPS module 1736, and the cellular module 1738 may each include dedicated antennas and / or utilize antennas 1740 for communication with one or more other nodes. For example, the UE apparatus 1702 can communicate through the transceiver (s) 1730 via the antennas 1740 with another UE (e.g., sidelink communication) and / or with a network entity 104 (e.g., uplink / downlink communication) , where the network entity 104 may correspond to a base station or a unit of the base station, such as the RU 106, the DU 108, or the CU 110.
[0146] The wireless baseband processor 1726 and the application processor 1706 may each include a computer-readable medium / memory 1726', 1706', respectively. The additional module of memory 1716 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1726', 1706', 1716 may be non-transitory. The wireless baseband processor 1726 and the application processor 1706 may each be responsible for general processing, including execution of software stored on the computer-readable medium / memory 1726', 1706', 1716. The software, when executed by the wireless baseband processor 1726 / application processor 1706, causes the wireless baseband processor 1726 / application processor 1706 to perform the various functions described herein. The computer-readable medium / memory may also be used for storing data that is manipulated by the wireless baseband processor 1726 / application processor 1706 when executing the software. The wireless baseband processor 1726 / application processor 1706 may be a component of the UE 102. The UE apparatus 1702 may be a processor chip (e.g., modem and / or application) and include just the wireless baseband processor 1726 and / or the application processor 1706. In other examples, the UE apparatus 1702 may be the entire UE 102 and include the additional modules of the apparatus 1702.
[0147] As discussed in FIG. 1 and implemented with respect to FIG. 15, the PUSCH repetition component 140 is configured to receive, from a network entity, a configuration for a PUSCH including repetition information and OCC information. The PUSCH repetition component 140 is configured to apply, an OCC sequence associated with the OCC information, to PUSCH repetitions associated with the repetition information. The PUSCH repetition component 140 is configured to transmit, to the network entity, the PUSCH repetitions based on at least one of: a length of the OCC sequence different from a length of the PUSCH repetitions, a collision between a PUSCH repetition and another transmission, different power control configurations for the PUSCH repetitions, or UL resource muting.
[0148] The PUSCH repetition component 140 may be within the application processor 1706 (e.g., at 140a) , the wireless baseband processor 1726 (e.g., at 140b) , or both the application processor 1706 and the wireless baseband processor 1726. The PUSCH repetition component 140a-140b may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm, stored within a computer-readable medium for implementation by the one or more processors, or a combination thereof.
[0149] FIG. 18 is a diagram 1800 illustrating an example of a hardware implementation for one or more network entities 104. The one or more network entities 104 may be a base station, a component of a base station, or may implement base station functionality. The one or more network entities 104 may include, or may correspond to, at least one of the RU 106, the DU, 108, or the CU 110. The CU 110 may include a CU processor 1846, which may have on-chip memory 1846'. In some aspects, the CU 110 may further include an additional module of memory 1856 and / or a communications interface 1848, both of which may be coupled to the CU processor 1846. The CU 110 can communicate with the DU 108 through a midhaul link 162, such as an F1 interface between the communications interface 1848 of the CU 110 and a communications interface 1828 of the DU 108.
[0150] The DU 108 may include a DU processor 1826, which may have on-chip memory 1826'. In some aspects, the DU 108 may further include an additional module of memory 1836 and / or the communications interface 1828, both of which may be coupled to the DU processor 1826. The DU 108 can communicate with the RU 106 through a fronthaul link 160 between the communications interface 1828 of the DU 108 and a communications interface 1808 of the RU 106.
[0151] The RU 106 may include an RU processor 1806, which may have on-chip memory 1806'. In some aspects, the RU 106 may further include an additional module of memory 1816, the communications interface 1808, and one or more transceivers 1830, all of which may be coupled to the RU processor 1806. The RU 106 may further include antennas 1840, which may be coupled to the one or more transceivers 1830, such that the RU 106 can communicate through the one or more transceivers 1830 via the antennas 1840 with the UE 102.
[0152] The on-chip memory 1806', 1826', 1846'a nd the additional modules of memory 1816, 1836, 1856 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of the processors 1806, 1826, 1846 is responsible for general processing, including execution of software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor (s) 1806, 1826, 1846 causes the processor (s) 1806, 1826, 1846 to perform the various functions described herein. The computer-readable medium / memory may also be used for storing data that is manipulated by the processor (s) 1806, 1826, 1846 when executing the software. In examples, the uplink configuration component 150 may sit at any of the one or more network entities 104, such as at the CU 110; both the CU 110 and the DU 108; each of the CU 110, the DU 108, and the RU 106; the DU 108; both the DU 108 and the RU 106; or the RU 106.
[0153] As discussed in FIG. 1 and implemented with respect to FIG. 16, the uplink configuration component 150 is configured to transmit, to a UE, a configuration for a PUSCH including repetition information and OCC information, an OCC sequence associated with the OCC information being applied over PUSCH repetitions associated with the repetition information. The uplink configuration component 150 is configured to receive, from the UE, the PUSCH repetitions based on at least one of: a length of the OCC sequence different from a length of the PUSCH repetitions, a collision between a PUSCH repetition and another transmission, different power control configurations for the PUSCH repetitions, or UL resource muting.
[0154] The uplink configuration component 150 may be within one or more processors of the one or more network entities 104, such as the RU processor 1806 (e.g., at 150a) , the DU processor 1826 (e.g., at 150b) , and / or the CU processor 1846 (e.g., at 150c) . The uplink configuration component 150a-150c may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors 1806, 1826, 1846 configured to perform the stated processes / algorithm, stored within a computer-readable medium for implementation by the one or more processors 1806, 1826, 1846, or a combination thereof.
[0155] The specific order or hierarchy of blocks in the processes and flowcharts disclosed herein is an illustration of example approaches. Hence, the specific order or hierarchy of blocks in the processes and flowcharts may be rearranged. Some blocks may also be combined or deleted. Dashed lines may indicate optional elements of the diagrams. The accompanying method claims present elements of the various blocks in an example order, and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts.
[0156] The detailed description set forth herein describes various configurations in connection with the drawings and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough explanation of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.
[0157] Aspects of wireless communication systems, such as telecommunication systems, are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and are illustrated in the accompanying drawings by various blocks, components, circuits, processes, call flows, systems, algorithms, etc. (collectively referred to as “elements” ) . These elements may be implemented using electronic hardware, computer software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
[0158] An element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs) , central processing units (CPUs) , application processors, digital signal processors (DSPs) , reduced instruction set computing (RISC) processors, systems-on-chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other similar hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software, which may be referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.
[0159] If the functionality described herein is implemented in software, the functions may be stored on, or encoded as, one or more instructions or code on a computer-readable medium, such as a non-transitory computer-readable storage medium. Computer-readable media includes computer storage media and can include a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer. Storage media may be any available media that can be accessed by a computer.
[0160] Aspects, implementations, and / or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, the aspects, implementations, and / or use cases may come about via integrated chip implementations and other non-module-component based devices, such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI) -enabled devices, machine learning (ML) -enabled devices, etc. The aspects, implementations, and / or use cases may range from chip-level or modular components to non-modular or non-chip-level implementations, and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques described herein.
[0161] Devices incorporating the aspects and features described herein may also include additional components and features for the implementation and practice of the claimed and described aspects and features. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes, such as hardware components, antennas, RF-chains, power amplifiers, modulators, buffers, processor (s) , interleavers, adders / summers, etc. Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., of varying configurations.
[0162] The description herein is provided to enable a person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be interpreted in view of the full scope of the present disclosure consistent with the language of the claims.
[0163] Reference to an element in the singular does not mean “one and only one” unless specifically stated, but rather “one or more. ” Terms such as “if, ” “when, ” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when, ” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The terms “may” , “might” , and “can” , as used in this disclosure, often carry certain connotations. For example, “may” refers to a permissible feature that may or may not occur, “might” refers to a feature that probably occurs, and “can” refers to a capability (e.g., capable of) . The phrase “For example” often carries a similar connotation to “may” and, therefore, “may” is sometimes excluded from sentences that include “for example” or other similar phrases.
[0164] Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C” or “one or more of A, B, or C” include any combination of A, B, and / or C, such as A and B, A and C, B and C, or A and B and C, and may include multiples of A, multiples of B, and / or multiples of C, or may include A only, B only, or C only. Sets should be interpreted as a set of elements where the elements number one or more. Terms or articles such as “a” , “an” , and / or “the” may refer to one of an item, feature, element, etc., that the term or article precedes, or may refer to more than one of said item, feature, element, etc. that the term or article precedes. For example, the recitation “awidget” does not preclude reference to multiples of said widget, as “multiple widgets” necessarily includes “a widget” . Hence, the recitation “awidget” may be interpreted as “at least one widget” or, similarly, interpreted as “one or more widgets” .
[0165] Unless otherwise specifically indicated, ordinal terms such as “first” and “second” do not necessarily imply an order in time, sequence, numerical value, etc., but are used to distinguish between different instances of a term or phrase that follows each ordinal term.
[0166] Reference numbers, as used in the specification and figures, are sometimes cross-referenced among drawings to denote same or similar features. A feature that is exactly the same in multiple drawings may be labeled with the same reference number in the multiple drawings. A feature that is similar among the multiple drawings, but not exactly the same, may be labeled with reference numbers that have different leading numbers but have one or more of the same trailing numbers (e.g., 206, 306, 406, etc., may refer to similar features in the drawings) . Hence, like numbers may refer to like actions.
[0167] Structural and functional equivalents to elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. The words “module, ” “mechanism, ” “element, ” “device, ” and the like may not be a substitute for the word “means. ” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for. ” As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” , where “A” may be information, a condition, a factor, or the like, shall be construed as “based at least on A” unless specifically recited differently.
[0168] The following examples are illustrative only and may be combined with other examples or teachings described herein, without limitation.
[0169] Example 1 is a method of wireless communication at a UE, including: receiving, from a network entity, a configuration for a PUSCH including repetition information and OCC information; applying, an OCC sequence associated with the OCC information, to PUSCH repetitions associated with the repetition information; and transmitting, to the network entity, the PUSCH repetitions based on at least one of: a length of the OCC sequence different from a length of the PUSCH repetitions, a collision between a PUSCH repetition and another transmission, different power control configurations for the PUSCH repetitions, or UL resource muting.
[0170] Example 2 is the method of example 1, further including: transmitting, to the network entity, a UE capability message indicating support for at least one of: applying OCC over the PUSCH repetitions, a length of an OCC sequence, OCC sequence repetition, OCC sequence cycling, OCC sequence repetition over orphan repetitions, PUSCH types with OCC, DCI formats, or a maximum number of PUSCH repetitions with OCC.
[0171] Example 3 is the method of any of examples 1-2, where the PUSCH repetitions have a first length and the OCC sequence has a second length, where the first length of the PUSCH repetitions indicates at least one of: actual PUSCH repetitions, nominal PUSCH repetitions, or a number of slots scheduled for the PUSCH repetitions.
[0172] Example 4 is the method of any of examples 1-3, where the applying the OCC sequence includes OCC sequence repetition or OCC sequence cycling over the PUSCH repetitions, where the first length is greater than the second length, and the first length is an integer multiple of the second length.
[0173] Example 5 is the method of any of examples 1-4, where the applying the OCC sequence includes OCC sequence repetition over orphan PUSCH repetitions, where the first length is greater than the second length, and the first length is not an integer multiple of the second length.
[0174] Example 6 is the method of any of examples 1-5, where the first length is greater than the second length, and the first length is not an integer multiple of the second length, further including: dropping the PUSCH repetitions that exceed a value of the length of the second length; and updating the first length of the PUSCH repetitions to equal to the second length, where application of the OCC sequence occurs over the updated first length of the PUSCH repetitions.
[0175] Example 7 is the method of any of examples 1-6, where the first length is less than the second length, wherein the updated first length of the PUSCH repetitions equals the second length, further including: updating, by the UE, the updated first length of the PUSCH repetitions to match the second length of the OCC sequence.
[0176] Example 8 is the method of any of examples 1-7, where the repetition information includes PUSCH repetition with slot counting; where the transmitting the PUSCH repetitions includes: transmitting the PUSCH repetitions based on a determination whether allocated resources for the PUSCH repetitions are available.
[0177] Example 9 is the method of any of examples 1-8, where the repetition information includes PUSCH repetition with slot counting; where allocated resources for the PUSCH repetitions are unavailable; where the transmitting the PUSCH repetitions includes: transmitting the PUSCH repetitions based on a determination of whether a phase continuity is maintained.
[0178] Example 10 is the method of any of examples 1-9, further including: stopping transmission of the PUSCH repetitions when at least one PUSCH repetition overlaps a downlink or uplink transmission having a higher priority.
[0179] Example 11 is the method of any of examples 1-10, where a first length of the PUSCH repetitions is greater than a second length of the OCC sequence; where at least one PUSCH repetition overlaps a downlink or uplink transmission having a higher priority than the PUSCH repetitions, further including: transmitting non-overlapping PUSCH repetitions based on a number of the non-overlapping PUSCH repetitions being greater than the second length of the OCC sequence and the at least one PUSCH repetition that overlaps is a last repetition of the PUSCH repetitions.
[0180] Example 12 is the method of any of examples 1-11, where the different power control configurations are for different subsets of time domain resources, further including: transmitting the PUSCH repetitions within an OCC group, dropping transmission of one or more of the PUSCH repetitions within the OCC group, dropping transmission of all the PUSCH repetitions, transmitting the PUSCH repetition within the OCC group in a next available slot, or transmitting the PUSCH repetition within the OCC group with a consistent power or a consistent phase.
[0181] Example 13 is the method of any of examples 1-12, where the configuration further configures a DFT-s-OFDM waveform for the PUSCH and the UL resource muting.
[0182] Example 14 is the method of any of examples 1-13, where the configuration configures the DFT-s-OFDM waveform and the UL resource muting with the OCC information.
[0183] Example 15 is the method of any of examples 1-14, wherein the configuration further configures a π / 2 binary phase shift keying, BPSK, modulation scheme for the PUSCH, further including: generating first complex-valued modulation symbols associated with the π / 2 BPSK modulation scheme based on DFT samples before applying the UL resource muting; generating second complex-valued modulation symbols associated with the π / 2 BPSK modulation scheme based on the on the DFT samples after applying the UL resource muting; refraining from using the π / 2 BPSK modulation scheme for the PUSCH repetitions with the UL resource muting; or replacing an index i, associated with complex-valued modulation symbols of the π / 2 BPSK modulation scheme, with i / 2 for the PUSCH repetitions with the UL resource muting.
[0184] Example 16 is the method of any of examples 1-15, where the configuration further configures the UL resource muting with the PUSCH repetitions, further including: refraining from applying the UL resource muting on symbols with, a PT-RS, with a DFT-s-OFDM waveform; applying the UL resource muting on symbols with a PT-RS with a DFT-s-OFDM waveform; applying the UL resource muting to at least one PUSCH symbol and refraining from transmitting a PT-RS on the at least one PUSCH symbol, a PUSCH transmission occasion, or an entire PUSCH; or refraining from transmitting a PT-RS on symbols with a DFT-s-OFDM waveform when an OFDM symbol comprises the UL resource muting.
[0185] Example 17 is the method of any of examples 1-16, further including: determining a TBS for a number of REs allocated for PUSCH, based on at least one of: removal of a number of muted REs allocated for the PUSCH within a PRB, a pre-configured number of muted REs are applied when the UL resource muting is applied on a PUSCH allocation, or removal of the muted REs from a final number of the REs allocated for the PUSCH.
[0186] Example 18 is the method of any of examples 1-17, where the configuration includes a power control configuration for the PUSCH repetitions, further including: transmitting or dropping the PUSCH repetitions with the OCC when the UE lacks a power consistency or a phase continuity.
[0187] Example 19 is the method of any of examples 1-18, further including: receiving, from the network entity, a control signal scheduling the PUSCH repetitions with the OCC
[0188] Example 20 is a method of wireless communication at a network entity, including: transmitting, to a UE, a configuration for a PUSCH including repetition information and OCC information, an OCC sequence associated with the OCC information being applied over PUSCH repetitions associated with the repetition information; and receiving, from the UE, the PUSCH repetitions based on at least one of: a length of the OCC sequence different from a length of the PUSCH repetitions, a collision between a PUSCH repetition and another transmission, different power control configurations for the PUSCH repetitions, or UL resource muting.
[0189] Example 21 is the method of example 20, further including: receiving, from the UE, a UE capability message indicating support for at least one of: applying OCC over the PUSCH repetitions, a length of an OCC sequence, OCC sequence repetition, OCC sequence cycling, OCC sequence repetition over orphan repetitions, PUSCH types with OCC, DCI formats, or a maximum number of PUSCH repetitions with OCC.
[0190] Example 22 is the method of any of examples 20-21, where the PUSCH repetitions have a first length and an OCC sequence has a second length, where the first length of the PUSCH repetitions indicate at least one of: actual PUSCH repetitions, nominal PUSCH repetitions, or a number of slots scheduled for the PUSCH repetitions.
[0191] Example 23 is the method of any of examples 20-22, where the repetition information includes PUSCH repetition with slot counting.
[0192] Example 24 is the method of any of examples 20-23, where the different power control configurations are for different subsets of time domain resources.
[0193] Example 25 is the method of any of examples 20-24, further including: transmitting, to the UE, a control signal scheduling the PUSCH repetitions with the OCC.
[0194] Example 26 is an apparatus for wireless communication for implementing a method as in any of examples 1-25.
[0195] Example 27 is an apparatus for wireless communication including means for implementing a method as in any of examples 1-25.
[0196] Example 28 is a non-transitory computer-readable medium storing computer executable code, the code when executed by a processor causes the processor to implement a method as in any of examples 1-25.
[0197] Example 29 is a computer program product for implementing a method as in any of examples 1-25.
Claims
1.A method of wireless communication at a user equipment, UE, (102) , comprising:receiving (504) , from a network entity (104) , a configuration for a physical uplink shared channel, PUSCH, including repetition information and orthogonal cover code, OCC, information;applying (505) , an OCC sequence associated with the OCC information, to PUSCH repetitions associated with the repetition information; andtransmitting (508) , to the network entity (104) , the PUSCH repetitions based on at least one of:a length of the OCC sequence different from a length of the PUSCH repetitions,a collision between a PUSCH repetition and another transmission, different power control configurations for the PUSCH repetitions, or uplink, UL, resource muting.2.The method of claim 1, further comprising:transmitting (502) , to the network entity (104) , a UE capability message indicating support for at least one of:applying OCC over the PUSCH repetitions,a length of an OCC sequence,OCC sequence repetition,OCC sequence cycling,OCC sequence repetition over orphan repetitions,PUSCH types with OCC,downlink control information, DCI, formats, ora maximum number of PUSCH repetitions with OCC.3.The method of any of claims 1-2, wherein the PUSCH repetitions have a first length and the OCC sequence has a second length, wherein the first length of the PUSCH repetitions indicates at least one of: actual PUSCH repetitions, nominal PUSCH repetitions, or a number of slots scheduled for the PUSCH repetitions.4.The method of claim 3, wherein the applying the OCC sequence includes OCC sequence repetition or OCC sequence cycling over the PUSCH repetitions, wherein the first length is greater than the second length, and the first length is an integer multiple of the second length.5.The method of claim 4, wherein the applying the OCC sequence includes OCC sequence repetition over orphan PUSCH repetitions, wherein the first length is greater than the second length, and the first length is not an integer multiple of the second length.6.The method of claim 4, wherein the first length is greater than the second length, and the first length is not an integer multiple of the second length, the method further comprising:dropping the PUSCH repetitions that exceed a value of the length of the second length; andupdating the first length of the PUSCH repetitions to equal to the second length, wherein application of the OCC sequence occurs over an updated first length of the PUSCH repetitions.7.The method of claim 4, wherein the first length is less than the second length, wherein an updated first length of the PUSCH repetitions equals the second length, further comprising:updating, by the UE, the updated first length of the PUSCH repetitions to match the second length of the OCC sequence.8.The method of any of claims 1-7, wherein the repetition information includes PUSCH repetition with slot counting;wherein the transmitting the PUSCH repetitions includes:transmitting the PUSCH repetitions based on a determination whether allocated resources for the PUSCH repetitions are available.9.The method of any of claims 1-8, wherein the repetition information includes PUSCH repetition with slot counting;wherein allocated resources for the PUSCH repetitions are unavailable;wherein the transmitting the PUSCH repetitions includes:transmitting the PUSCH repetitions based on a determination of whether a phase continuity is maintained.10.The method of any of claims 1-9, further comprising:stopping transmission of the PUSCH repetitions when at least one PUSCH repetition overlaps a downlink or uplink transmission having a higher priority.11.The method of any of claims 1-2, wherein a first length of the PUSCH repetitions is greater than a second length of the OCC sequence;wherein at least one PUSCH repetition overlaps a downlink or uplink transmission having a higher priority than the PUSCH repetitions; the method further comprising:transmitting non-overlapping PUSCH repetitions based on a number of the non-overlapping PUSCH repetitions being greater than the second length of the OCC sequence and the at least one PUSCH repetition that overlaps is a last repetition of the PUSCH repetitions.12.The method of any of claims 1-11, wherein the different power control configurations are for different subsets of time domain resources; the method further comprising at least one of:transmitting the PUSCH repetitions within an OCC group,dropping transmission of one or more of the PUSCH repetitions within the OCC group,dropping transmission of all the PUSCH repetitions,transmitting the PUSCH repetition within the OCC group in a next available slot, ortransmitting the PUSCH repetition within the OCC group with a consistent power or a consistent phase.13.The method of any of claims 1-12, wherein the configuration further configures a discrete Fourier transform spread orthogonal frequency division multiplexing, DFT-s-OFDM, waveform for the PUSCH and the UL resource muting.14.The method of claim 13, wherein the configuration configures the DFT-s-OFDM waveform and the UL resource muting with the OCC information.15.The method of any of claims 1-14, wherein the configuration further configures a π / 2 binary phase shift keying, BPSK, modulation scheme for the PUSCH; the method further comprising at least one of:generating first complex-valued modulation symbols associated with the π / 2 BPSK modulation scheme based on discrete Fourier transform, DFT, samples before applying the UL resource muting,generating second complex-valued modulation symbols associated with the π / 2 BPSK modulation scheme based on the on the DFT samples after applying the UL resource muting,refraining from using the π / 2 BPSK modulation scheme for the PUSCH repetitions with the UL resource muting, orreplacing an index i, associated with complex-valued modulation symbols of the π / 2 BPSK modulation scheme, with i / 2 for the PUSCH repetitions with the UL resource muting.16.The method of any of claims 1-15, wherein the configuration further configures the UL resource muting with the PUSCH repetitions; the method further comprising at least one of:refraining from applying the UL resource muting on symbols with, a phase tracking reference signal, PT-RS, with a discrete Fourier transform spread orthogonal frequency division multiplexing, DFT-s-OFDM, waveform,applying the UL resource muting on symbols with a PT-RS with a DFT-s-OFDM waveform,applying the UL resource muting to at least one PUSCH symbol and refraining from transmitting a PT-RS on the at least one PUSCH symbol, a PUSCH transmission occasion, or an entire PUSCH, orrefraining from transmitting a PT-RS on symbols with a DFT-s-OFDM waveform when an OFDM symbol comprises the UL resource muting.17.The method of any of claims 1-16, further comprising:determining a transport block size, TBS, for a number of resource elements, REs, allocated for PUSCH, based on at least one of:removal of a number of muted REs allocated for the PUSCH within a physical resource block, PRB,a pre-configured number of muted REs are applied when the UL resource muting is applied on a PUSCH allocation, orremoval of the muted REs from a final number of the REs allocated for the PUSCH.18.A method of wireless communication at a network entity (104) , comprising:transmitting (504) , to a user equipment, UE, (102) , a configuration for a physical uplink shared channel, PUSCH, including repetition information and orthogonal cover code, OCC, information, an OCC sequence associated with the OCC information being applied over PUSCH repetitions associated with the repetition information; andreceiving (508) , from the UE (102) , the PUSCH repetitions based on at least one of:a length of an OCC sequence different from a length of the PUSCH repetitions,a collision between a PUSCH repetition and another transmission, different power control configurations for the PUSCH repetitions, or uplink, UL, resource muting.19.An apparatus for wireless communication comprising a memory, a transceiver, and a processor coupled to the memory and the transceiver, the apparatus being configured to implement a method as in any of claims 1-18.
