Orthogonal cover codes for pusch repetition

Abstract

A user equipment (UE) configured for operation in a 5th Generation New Radio (5G NR) network may decode signaling to configure the UE with one or more orthogonal cover code (OCC) sequences. The UE may apply one of the OCC sequences to physical uplink shared channel (PUSCH) repetition of a PUSCH transmission. For inter-slot OCC PUSCH repetition, values of an OCC sequence are applied across slots of the PUSCH repetition. The UE may apply a first value of an OCC sequence of length two to a first repetition of a PUSCH transmission in a first slot and apply a second value of the OCC sequence of length two to a second repetition of the PUSCH transmission in a second slot.

Description

ORTHOGONAL COVER CODES FOR PUSCH REPETITIONPRIORITY CLAIM

[0001] This application claims the benefit of priority to United States Provisional Patent Application Serial No. 63 / 549,951, filed February 5, 2024 [reference number AF9237-Z], and U.S. Provisional Patent Application Serial No. 63 / 666,596, filed on July 1, 2024 [reference number AG2164-Z], both of which are incorporated herein by reference in their entireties.TECHNICAL FIELD

[0002] Embodiments pertain to wireless communications.BACKGROUND

[0003] Some issues with wireless networks relate to system capacity and maintaining adequate quality of service. These are particularly issues with uplink transmissions due to lower transmit power by user equipment (UE).

[0004] Thus, there are general needs for improving system capacity and maintaining quality of service in wireless networks.BRIEF DESCRIPTION OF THE DRAWINGS

[0005] FIG. 1 A illustrates an architecture of a network, in accordance with some embodiments.

[0006] FIG. IB and FIG. 1C illustrate a non-roaming 5G system architecture in accordance with some embodiments.

[0007] FIG. 2 illustrates symbol level OCC for PUSCH transmission: Option 1, in accordance with some embodiments.

[0008] FIG. 3 illustrates symbol level OCC for PUSCH transmission: Option 2, in accordance with some embodiments.

[0009] FIG. 4 illustrates OCC on Type B PUSCH repetitions: Option 1, in accordance with some embodiments.

[0010] FIG. 5 illustrates OCC on Type B PUSCH repetitions: Option 2, in accordance with some embodiments.

[0011] FIG. 6 illustrates OCC on Type B PUSCH repetitions: Option 3, in accordance with some embodiments.

[0012] FIG. 7 illustrates OCC on TBoMS repetitions, in accordance with some embodiments.

[0013] FIG. 8 illustrates OCC on PUSCH repetition due to collision: Option 1, in accordance with some embodiments.

[0014] FIG. 9 illustrates OCC on PUSCH repetition due to collision: Option 2, in accordance with some embodiments.

[0015] FIG. 10 illustrates OCC on PUSCH repetition due to collision: Option 3, in accordance with some embodiments.

[0016] FIG. 11 illustrates a functional block diagram of a wireless communication device, in accordance with some embodiments.DETAILED DESCRIPTION

[0017] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0018] Embodiments disclosed herein relate to the use of orthogonal cover code (OCC) sequences for physical uplink shared channel (PUSCH) repetition.

[0019] Some embodiments are directed to an apparatus of a user equipment (UE) configured for operation in a 5thGeneration New Radio (5G NR) network. The apparatus may comprise processing circuitry and memory. In these embodiments, the processing circuitry is configured to decode signaling to configure the UE with one or more orthogonal cover code (OCC) sequences. The UE may apply one of the OCC sequences to physical uplink shared channel (PUSCH) repetition of a PUSCH transmission. For inter-slot OCC PUSCH repetition, values of an OCC sequence are applied across slots of the PUSCH repetition. The UE may apply a first value of an OCC sequence of length two to a first repetition of a PUSCH transmission in a first slot and apply a second value of the OCC sequence of length two to a second repetition of the PUSCH transmission in a second slot.

[0020] Some embodiments are directed to an apparatus of a generation Node B (gNB) configured for operation in a fifth-generation new radio (5GNR) network comprising processing circuitry and memory. In these embodiments, the processing circuitry may be configured to decode user equipment (UE) capability information elements (IE) from two or more UEs indicating capabilities for application of orthogonal cover code (OCC) sequences to physical uplink shared channel (PUSCH) transmissions of a PUSCH repetition. In these embodiments, for UEs that have indicated a UE capability for the application of the OCC sequences, the processing circuitry may generate signalling for transmission to the UEs to configure the UEs with or indicate OCC sequences. The gNB may demultiplex PUSCH repetitions received from the UEs using the OCC sequences. These embodiments as well as other are described in more detail herein.

[0021] Orthogonal cover code sequences provide for multiple access allowing multiple users to share the same frequency channel by assigning unique, non-interfering codes to each user. Orthogonal cover code sequences also provide for interference reduction because the orthogonal nature of the codes minimizes cross-talk and interference between different users' signals. Orthogonal cover code sequences also provide for signal separation because at the receiver, these codes enable cleaner separation of different users' transmissions.

[0022] For cellular system, coverage is a principal factor for successful operation. Compared to LTE, NR can be deployed at relatively higher carrier frequency in frequency range 1 (FR1), e.g., at 3.5GHz. In this case, coverage loss is expected due to larger path-loss, which makes it more challenging to maintain an adequate quality of service. Typically, uplink coverage is the bottleneck for system operation considering the low transmit power at UE side. Moreover, 5G NR cellular standard can be used for Non-Terrestrial Networks (NTN), where a UE is served via satellites or High-Altitude Platform Stations. Considering significant distances between satellite and UE, additional coverage enhancements are required for NTN deployment.

[0023] Given that the coverage of NTN satellites is very wide and considering device density, it is expected that a large number of UEs will be within a satellite’s coverage. Especially for LEO, a large number of UEs in coverage must succeed in transmitting desired data during a satellite coverage. In addition, some users will require higher resources than others, depending on their traffic patterns. Therefore, further granularity of resource multiplexing can significantly improve system capacity efficiency.

[0024] In NR, system design is based on waveform choice of cyclic prefix - orthogonal frequency-division multiplexing (CP-OFDM) for DL and UL, and additionally, Discrete Fourier Transform-spread-OFDM (DFT-s- OFDM) for UL. Note that DFT-s-OFDM waveform is realized by enabling transform precoding at the transmitter side. In order to improve the capacity performance on uplink, Orthogonal Cover Codes (OCC) may be applied for the transmission of physical uplink shared channel (PUSCH) with DFT-s-OFDM waveform. In particular, OCC may be applied on PUSCH across OFDM symbols, across slots, and / or within an OFDM symbol. In this case, certain signalling mechanisms may need to be defined for UE to apply the OCC on PUSCH transmissions.

[0025] Embodiments disclosed herein provide for orthogonal cover codes for PUSCH transmission. These embodiments cover:• Signalling mechanism on orthogonal cover codes for PUSCH transmission• Orthogonal cover codes for Type B PUSCH and TBoMS transmission• Collision handling in case of orthogonal cover codes for PUSCH transmission

[0026] FIG. 1 A illustrates an architecture of a network in accordance with some embodiments. The network 140A is shown to include user equipment (UE) 101 and UE 102. The UE 101 and UE 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, drones, or any other computing device including a wired and / or wireless communications interface. The UE 101 and UE 102 can be collectively referred to herein as UE 101, and UE 101 can be used to perform one or more of the techniques disclosed herein.

[0027] Any of the radio links described herein (e.g., as used in the network 140 A or any other illustrated network) may operate according to any exemplary radio communication technology and / or standard.

[0028] LTE and LTE- Advanced are standards for wireless communications of high-speed data for UE such as mobile telephones. In LTE- Advanced and various wireless systems, carrier aggregation is a technology according to which multiple carrier signals operating on different frequencies may be used to carry communications for a single UE, thus increasing the bandwidth available to a single device. In some embodiments, carrier aggregation may be used where one or more component carriers operate on unlicensed frequencies.

[0029] Embodiments described herein can be used in the context of any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and further frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and further frequencies).

[0030] Embodiments described herein can also be applied to different Single Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR(New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[0031] In some embodiments, any of the UE 101 and UE 102 can comprise an Intemet-of-Things (loT) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing short-lived UE connections. In some embodiments, any of the UE 101 and UE 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE). An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or loT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An loT network includes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The loT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the loT network. In some embodiments, any of the UE 101 and UE 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

[0032] The UE 101 and UE 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110. The RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The UE 101 and UE 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to- Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution(LTE) protocol, a fifth-generation (5G) protocol, a New Radio (NR) protocol, and the like.

[0033] In an aspect, the UE 101 and UE 102 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

[0034] The UE 102 is shown to be configured to access an access point (AP) 106 via connection 107. The connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

[0035] The RAN 110 can include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). In some embodiments, the RAN nodes 111 and 112 can be transmission / reception points (TRPs). In instances when the RAN nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeBs. The RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro-RAN node, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node.

[0036] Any of the RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UE 101 and UE 102. In some embodiments, any of the RAN nodes 111 and 112 can fulfillvarious logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In an example, any of the RAN nodes 111 and / or 112 can be a new generation Node-B (gNB), an evolved node-B (eNB), or another type of RAN node.

[0037] The RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an SI interface 113. In embodiments, the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to FIGS. 1B-1C). In this aspect, the SI interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the SI -mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and MMEs 121.

[0038] In this aspect, the CN 120 comprises the MMEs 121, the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 121 may manage mobility embodiments in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc.

[0039] The S-GW 122 may terminate the SI interface 113 towards the RAN 110, and routes data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Otherresponsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.

[0040] The P-GW 123 may terminate an SGi interface toward a PDN. The P-GW 123 may route data packets between the CN 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125. The P-GW 123 can also communicate data to other external networks 131 A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks. Generally, the application server 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125. The application server 184 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UE 101 and UE 102 via the CN 120.

[0041] The P-GW 123 may further be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in some embodiments, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with a local breakout of traffic, there may be two PCRFs associated with a UE's IP- CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P- GW 123.

[0042] In some embodiments, the communication network 140 A can be an loT network or a 5G network, including 5G new radio network using communications in the licensed (5GNR) and the unlicensed (5GNR-U) spectrum. One of the current enablers of loT is the narrowband-IoT (NB-IoT).

[0043] An NG system architecture can include the RAN 110 and a 5G network core (5GC). In these embodiments, the RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs. The CN 120 (e.g., a 5G core network or 5GC) can include an access and mobility function (AMF) and / or a user plane function (UPF). The AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some embodiments, the gNBs and the NG-eNBs can be connected to the AMF by NG- C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via Xn interfaces.

[0044] In some embodiments, the NG system architecture can use reference points between various nodes as provided by 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12). In some embodiments, each of the gNBs and the NG-eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth. In some embodiments, a gNB can be a primary node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.

[0045] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some embodiments. Referring to FIG. IB, there is illustrated a 5G system architecture 140B in a reference point representation. More specifically, UE 102 can be in communication with RAN 110 as well as one or more other 5G core (5GC) network entities. The 5G system architecture MOB includes a plurality of network functions (NFs), such as access and mobility management function (AMF) 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, user plane function (UPF) 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM) / home subscriber server (HSS) 146. The UPF 134 can provide a connection to a data network (DN) 152, which can include, for example, operator services, Internet access, or third-party services. The AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality. The SMF 136 can be configured to set up and manage various sessions according to network policy. The UPF 134 can be deployed in one or moreconfigurations according to the desired service type. The PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system). The UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).

[0046] In some embodiments, the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS 168B includes a CSCF, which can function as a proxy CSCF (P-CSCF) 162B, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B. The S-CSCF 164B can be configured to manage the session states in the network, and the E-CSCF can be configured to handle certain embodiments of emergency sessions such as routing an emergency request to the correct emergency center or PSAP. The I-CSCF 166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area. In some embodiments, the I-CSCF 166B can be connected to another IP multimedia network 170E, e.g., an IMS operated by a different network operator.

[0047] In some embodiments, the UDM / HSS 146 can be coupled to an application server 160E, which can include a telephony application server (TAS) or another application server (AS). The AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.

[0048] A reference point representation shows that interaction can exist between corresponding NF services. For example, FIG. IB illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between the RAN 110 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152),N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM / HSS 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between the UDM / HSS 146 and the SMF 136, not shown), Ni l (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM / HSS 146, not shown), N14 (between two AMFs 132, not shown), N15 (between the PCF 148 and the AMF 132 in case of a non-roaming scenario, or between the PCF 148 and a visited network and AMF 132 in case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Other reference point representations not shown in FIG. IB can also be used.

[0049] FIG. 1C illustrates a 5G system architecture 140C and a servicebased representation. In addition to the network entities illustrated in FIG. IB, system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156. In some embodiments, 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.

[0050] In some embodiments, as illustrated in FIG. 1C, service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services. In this regard, 5G system architecture 140C can include the following service-based interfaces: Namf 158H (a service-based interface exhibited by the AMF 132), Nsmf 1581 (a service-based interface exhibited by the SMF 136), Nnef 158B (a service-based interface exhibited by the NEF 154), Npcf 158D (a service-based interface exhibited by the PCF 148), a Nudm 158E (a service-based interface exhibited by the UDM / HSS 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a service-based interface exhibited by the NRF 156), Nnssf 158A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a service-based interface exhibited by the AUSF 144). Other servicebased interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown in FIG. 1C can also be used.

[0051] In some embodiments, any of the UEs or base stations described in connection with FIGS. 1 A-1C can be configured to perform the functionalities described herein.

[0052] Mobile communication has evolved significantly from early voice systems to today’s highly sophisticated integrated communication platform. The next generation wireless communication system, 5G, or new radio (NR) will provide access to information and sharing of data anywhere, anytime by various users and applications. NR is expected to be a unified network / system that targets to meet vastly different and sometimes conflicting performance dimensions and services. Such diverse multi-dimensional requirements are driven by different services and applications. In general, NR will evolve based on 3 GPP LTE- Advanced with additional potential new Radio Access Technologies (RATs) to enrich people's lives with better, simple, and seamless wireless connectivity solutions. NR will enable everything connected by wireless and deliver fast, rich content and services. Rel-15 NR systems are designed to operate on the licensed spectrum. The NR-unlicensed (NR-U), a short-hand notation of the NR-based access to unlicensed spectrum, is a technology that enables the operation of NR systems on the unlicensed spectrum.

[0053] Signalling mechanism on orthogonal cover codes for PUSCH transmission

[0054] As mentioned above, in NR, system design is based on waveform choice of cyclic prefix - orthogonal frequency-division multiplexing (CP- OFDM) for DL and UL, and additionally, Discrete Fourier Transform-spread- OFDM (DFT-s-OFDM) for UL. Note that DFT-s-OFDM waveform is realized by enabling transform precoding at the transmitter side. In order to improve the capacity performance on uplink, Orthogonal Cover Codes (OCC) may be applied for the transmission of physical uplink shared channel (PUSCH) with DFT-s- OFDM waveform. In particular, OCC may be applied on PUSCH across OFDM symbols, across slots, and / or within an OFDM symbol. In this case, certain signalling mechanisms may need to be defined for UE to apply the OCC onPUSCH transmissions. Embodiments of signalling mechanism on orthogonal cover codes for PUSCH transmission are provided as follows:

[0055] In one embodiment, the length of orthogonal cover code (OCC) may be configured by higher layers via NR remaining minimum system information (RMSI), NR other system information (OSI) or dedicated radio resource control (RRC) signalling, dynamically indicated in the DCI, or a combination thereof. In some aspects, if the length of OCC is not configured, OCC is not applied for PUSCH repetition. In some aspects, the length of OCC can be configured or dynamically indicated as 1, which indicates that OCC is not applied for PUSCH repetition.

[0056] In one embodiment, the OCC sequence used for the PUSCH transmission can be configured by dedicated RRC signalling or dynamically indicated in the DCI, or a combination thereof. In one option, the OCC sequence can be dynamically indicated in the DCI format 0 1, 0 2 and / or 0 3. The field size can be determined in accordance with the length of OCC. In one example, the field size can be determined as nog2( / Vocc)],is the length of OCC. Further, whether OCC is applied for PUSCH transmission can be configured by dedicated RRC signalling, which may be separately configured for each DCI format. In an example of the embodiment, multiple OCC sequences of different lengths are specified and higher layer signalling and / or layer 1 (DCI- based) indication can be used to provide a UE with a sequence of a given length. In another option, for DCI format 0 0, OCC is not applied for PUSCH transmission. In another option, for configured grant PUSCH (CG-PUSCH) including Type 1 and Type 2 CG-PUSCH, OCC sequence can be configured by higher layers via dedicated RRC signalling. For Type 2 CG-PUSCH which is activated by the DCI, the OCC sequence for the transmission of PUSCH can be determined in accordance with the RRC configuration or the indication in the DCI for activation of Type 2 CG-PUSCH. In another option, for DCI format 0 1, 0 2 and / or 0 3, OCC sequence indication may be configured as part of time domain resource allocation (TDRA) table. In particular, OCC sequence indication may be configured together with repetition, starting and length indicator in a row of TDRA table.

[0057] In one embodiment, the length of OCC and the OCC sequence are jointly coded and indicated via single bitfield in DCI or single higher-layer parameter. In other embodiment, the length of OCC, the OCC sequence and the number of repetitions for PUSCH transmission are jointly coded and indicated via single bit field in DCI or single higher-layer parameter. Further, one codepoint of the bitfield for indication of OCC length and / or OCC sequence may include enabled or disabled of transform precoding for PUSCH transmission.

[0058] In another embodiment, when cross symbol and / or cross slot OCC is applied for PUSCH transmission, if the length of OCC is less than or equal to the number of repetitions for PUSCH transmission, the OCC sequence is repeated until it reaches the number of repetitions. In one example, if the length of OCC is 2 and OCC sequence is [+1 -1], and the number of repetitions is 7, the OCC sequence that is applied to the PUSCH repetitions can be [+1 -1 +1 -1 +1 -1 +1], If the length of OCC is greater than the number of repetitions for PUSCH transmission, the OCC sequence that is applied to the PUSCH repetitions is truncated so that the length of OCC sequence is equal to the number of repetitions. In one example, if the length of OCC is 4 and OCC sequence is [+1 -1 +1 -1], and the number of repetitions is 2, the OCC sequence that is applied to the PUSCH repetitions can be [+1 -1], In one option, a combination of OCC within a symbol, cross symbol and / or cross slot can be applied for PUSCH repetitions. For instance, a first OCC can be applied within a symbol and a second OCC can be jointly applied on PUSCH repetitions cross slot.

[0059] In another embodiment, symbol-level OCC may be applied to a single PUSCH transmission for a PUSCH scheduled or configured for transmission with or without repetitions. In an example, symbol-level OCC may be applied to a single PUSCH transmission if the duration of the PUSCH corresponds to one of: 2, 4, 8 symbols including the associated PUSCH DMRS symbols with or without any PUSCH REs. In another example, symbol -level OCC may be applied to a single PUSCH transmission if the duration of the PUSCH corresponds to one of: 2, 4, 8 symbols excluding the associated PUSCH DMRS symbols without PUSCH REs, if any. In this example, the OCC may beapplied to symbols with PUSCH REs, with or without any PUSCH DMRS REs and not to symbols with associated PUSCH DMRS only.

[0060] In another embodiment, for symbol level OCC, a set of symbols within the allocated number of symbols for PUSCH transmission, excluding DMRS symbols, may be grouped for OCC. In some aspects, symbol level OCC or pre-DFT OCC (OCC within a symbol) may apply for PUSCH repetition type A and / or PUSCH repetition type B. In case of PUSCH repetition type A, the symbol level OCC or pre-DFT OCC may be applied for each repetition of PUSCH transmission. Further, in case of PUSCH repetition type B, the symbol level OCC or pre-DFT OCC may be applied for each actual or nominal repetition of PUSCH transmission. In one option, the number of symbols allocated for a PUSCH transmission excluding DMRS symbols is an integer multiple of OCC length. In some aspects, the number symbols in a group are equal to the OCC length. In this case, the indicated or configured OCC sequence is applied on the set of symbols for PUSCH transmission. In another option, the number of symbols allocated for a PUSCH transmission excluding DMRS symbols may not be an integer multiple of OCC length. When the remaining number of symbols in a group is less than the OCC length, the OCC sequence that is applied to the group is truncated so that the length of OCC sequence is equal to the number of symbols in the group. In one option, the set of symbols in a group excluding DMRS symbols where the OCC sequence is applied may be continuous in time domain.

[0061] FIG. 2 illustrates one example of symbol level OCC for PUSCH transmission. In the example, 7 symbols are allocated for PUSCH transmission, where the first symbol 202 is allocated for DMRS. Further, OCC with length of 2 is configured and indicated OCC sequence is [+1 -1], In this case, 3 groups of symbols 204, 206, 208 are used for OCC, where OCC sequence [+1, -1] is applied on each set of symbols in each group transmission. In this example, OCC sequence value +1 is applied to the first symbol group one 204, OCC sequence value -1 is applied to the second symbol group one 204, OCC sequence value +1 is applied to the first symbol group two 206, OCC sequence value -1 is applied to the second symbol group two 206, OCC sequence value +1 is applied to the first symbol group three 208, and OCC sequence value -1 is applied to thesecond symbol group three 208. In this option, the symbols in each group are continuous. In another option, the set of symbols in a group excluding DMRS symbols where the OCC sequence is applied may be non-continuous in time domain.

[0062] FIG. 3 illustrates one example of symbol level OCC for PUSCH transmission. In the example, 7 symbols are allocated for PUSCH transmission, where the first symbol is allocated for DMRS. Further, an OCC sequence with length of 2 is configured and the indicated OCC sequence is [+1 -1], In this case, 3 groups of symbols 304, 306, 308 are used for OCC, where the OCC sequence [+1, -1] is applied on the set of symbols in each group transmission. In this example, OCC sequence value +1 is applied to the first symbol group one 304, OCC sequence value -1 is applied to the second symbol group one 304, OCC sequence value +1 is applied to the first symbol group two 306, OCC sequence value -1 is applied to the second symbol group two 306, OCC sequence value +1 is applied to the first symbol group three 308, and OCC sequence value -1 is applied to the second symbol group three 308. In this option, the symbols in each group are non-continuous.

[0063] In another embodiment, in case when symbol level OCC, slot level OCC and / or pre-DFT OCC (OCC within a symbol) is supported for a UE, whether to support one of the symbol level OCC, slot level OCC and / or pre-DFT OCC (OCC within a symbol) for PUSCH transmission can be configured by higher layers via dedicated RRC signalling.

[0064] In another embodiment, OCC may only be applied for PUSCH with DFT-s-OFDM waveform. For dynamic waveform switching, OCC sequence indication field may be present or reserved in accordance with whether transform precoder indicator field is set to 1, such that DFT-s-OFDM waveform is used for PUSCH transmissions. In particular, OCC sequence indication field may have 0 bit if the higher layer parameter OCC length is not configured, or if transform precoder is disabled by higher layers and the Transform precoder indicator field is not present. Further, OCC sequence indication field may haveif transform precoder is enabled by higher layers and higher layer parameter OCC length is configured, or if the transform precoder indicatorfield is present and higher layer parameter OCC length is configured. If the transform precoder indicator field is present and set to ‘ 1’, the bit is reserved.

[0065] Orthogonal cover codes for Type B PUSCH and TBoMS transmission

[0066] Embodiments of orthogonal cover codes for Type B PUSCH and TBoMS transmission are provided as follows:

[0067] In one embodiment, when cross symbol or cross slot orthogonal cover code (OCC) is applied for Type B PUSCH repetitions, the OCC is applied on the nominal PUSCH repetitions. In other words, same OCC is applied for actual repetitions within a nominal repetition.

[0068] FIG. 4 illustrates one example of applying OCC on Type B PUSCH repetitions. In the example, it is assumed that starting symbol of first nominal PUSCH repetition is 6 and length of PUSCH repetition is 14 symbols 401. Further, 2 repetitions are applied for PUSCH transmission. Based on the PUSCH repetition type B, PUSCH repetition is divided into two segments for each repetition due to across slot boundary. For this option, assuming the length of OCC is 2, based on the indication in the DCI, +1 is applied on the first nominal repetition 402 and -1 is applied on the second nominal repetition 404.

[0069] In another embodiment, when cross symbol or cross slot orthogonal cover code (OCC) is applied for Type B PUSCH repetitions, the OCC is applied on the actual PUSCH repetitions.

[0070] FIG. 5 illustrates one example of applying OCC on Type B PUSCH repetitions. In the example, it is assumed that starting symbol of first nominal PUSCH repetition is 6 and length of PUSCH repetition is 14 symbols. Further, 2 repetitions are applied for this PUSCH transmission. Based on the PUSCH repetition type B, PUSCH repetition is divided into two segments for each repetition due to across slot boundaries 502. For this option, assuming the length of OCC is 4, based on the indication in the DCI, [+1 -1 +1 -1] is applied on the 4 actual repetitions, respectively.

[0071] In another embodiment, when cross symbol or cross slot orthogonal cover code (OCC) is applied for Type B PUSCH repetitions, the OCC is applied on the PUSCH repetition for a slot.

[0072] FIG. 6 illustrates one example of applying OCC on Type B PUSCH repetitions. In the example, it is assumed that starting symbol of first nominal PUSCH repetition is 6 and length of PUSCH repetition is 14 symbols. Further, 2 repetitions are applied for the PUSCH transmission. Based on the PUSCH repetition type B, PUSCH repetition is divided into two segments for each repetition due to across slot boundaries 602. For this option, assuming the length of OCC is 4, based on the indication in the DCI, [+1 -1 +1] is applied on the Type B PUSCH repetitions in three slots, respectively.

[0073] In another embodiment, when cross slot orthogonal cover code (OCC) is applied on transport block over multiple slots (TBoMS), the OCC is applied for each repetition of TBoMS.

[0074] FIG. 7 illustrates one example of applying OCC on TBoMS repetitions. In this example, each TBoMS repetition spans two slots and 2 repetitions are applied for TBoMS transmissions. For this option, for an OCC sequence of length 2 [+1, -1] is applied for the first and second TBoMS repetition, respectively. For example, the value +1 is applied to the first TBoMS repetition in the first slot 702 and the second slot 704, and the value -1 is applied to the second TBoMS repetition in the third slot 706 and the fourth slot 708.

[0075] In another embodiment, when cross slot orthogonal cover code (OCC) is applied on transport block over multiple slots (TBoMS), symbol-level OCC may be applied to a single TBoMS repetition. In an example, symbol-level OCC may be applied to a single TBoMS repetition if the TBoMS repetition spans a duration of 2Ak symbols (where k is a positive integer) including the associated PUSCH DMRS symbols with or without any PUSCH REs. In another example, symbol-level OCC may be applied to a single TBoMS repetition if the TBoMS repetition spans a duration of 2Ak symbols (where k is a positive integer) excluding the associated PUSCH DMRS symbols without PUSCH REs, if any. In this example, the OCC may be applied to symbols with PUSCH REs, with or without any PUSCH DMRS REs and not to symbols with associated PUSCH DMRS only.

[0076] In another embodiment, symbol level OCC or pre-DFT OCC (OCC within a symbol) may be applied for the TBoMS transmission without and / or with repetitions. When TBoMS transmission with repetition is applied forPUSCH transmission, symbol level OCC or pre-DFT OCC may be applied for each repetition of TBoMS transmission.

[0077] Collision handling in case of orthogonal cover codes for PUSCH transmission

[0078] Embodiments of collision handling in case of orthogonal cover codes for PUSCH transmission are provided as follows:

[0079] In one embodiment, when cross-slot OCC is applied for the PUSCH repetitions, if a PUSCH repetition is cancelled or dropped due to collision with high priority uplink transmission or semi-static DL symbols including synchronization signal block (SSB) and / or if UCI is multiplexed on PUSCH when PUSCH overlaps with PUCCH in time, the PUSCH repetitions or transmission occasions after the PUSCH are dropped.

[0080] FIG. 8 illustrates one example of OCC on PUSCH repetition due to collision. In the example, 4 repetitions are assumed for PUSCH transmission, repetition #1 802, repetition #2 804, repetition #3 806 and repetition #4 808.OCC length of 4 and OCC sequence with [+1 -1 +1 -1] is applied for the PUSCH repetition. Further, PUSCH repetition #3 806 is dropped due to collision with SSB symbols. For this option, the PUSCH repetition #4 808 may also be dropped.

[0081] In another embodiment, when cross-slot OCC is applied for the PUSCH repetitions, if a PUSCH repetition is cancelled or dropped due to collision with high priority uplink transmission or DL symbols including synchronization signal block (SSB) and / or if UCI is multiplexed on PUSCH when PUSCH overlaps with PUCCH in time, the OCC is not applied to the PUSCH and the OCC sequence is not postponed to the next available transmission occasion or repetition.

[0082] FIG. 9 illustrates one example of OCC on PUSCH repetition due to collision. In the example, 4 repetitions are assumed for PUSCH transmission, repetition #1 902, repetition #2 904, repetition #3 906 and repetition #4 908.OCC length of 4 and OCC sequence with [+1 -1 +1 -1] is applied for the PUSCH repetition. Further, PUSCH repetition #3 906 is dropped due to collision with SSB symbols. For this option, +1 is applied to the PUSCH repetition #1, -1 isapplied to the PUSCH repetition #2 and -1 is applied to the PUSCH repetition #4, respectively.

[0083] In another embodiment, when cross-slot OCC is applied for the PUSCH repetitions, if a PUSCH repetition is cancelled or dropped due to collision with high priority uplink transmission or DL symbols including synchronization signal block (SSB) and / or if UCI is multiplexed on PUSCH when PUSCH overlaps with PUCCH in time, the OCC is not applied to the PUSCH and the OCC sequence is postponed to the next available transmission occasion or repetition.

[0084] FIG. 10 illustrates one example of OCC on PUSCH repetition due to collision. In the example, 4 repetitions are assumed for PUSCH transmission repetition #1 1002, repetition #2 1004, repetition #3 1006 and repetition #4 1008. OCC length of 4 and OCC sequence with [+1 -1 +1 -1] is applied for the PUSCH repetition. Further, PUSCH repetition #3 is dropped due to collision with SSB symbols. For this option, +1 is applied to the PUSCH repetition #1, -1 is applied to the PUSCH repetition #2 and +1 is applied to the PUSCH repetition #4, respectively.

[0085] Some embodiments are directed to an apparatus of a user equipment (UE) configured for operation in a 5thGeneration New Radio (5G NR) network. The apparatus may comprise processing circuitry and memory. In these embodiments, the processing circuitry may be configured to decode signaling to configure the UE with one or more orthogonal cover code (OCC) sequences. The UE may apply one of the OCC sequences to physical uplink shared channel (PUSCH) repetition of a PUSCH transmission.

[0086] In some embodiments, when the OCC sequence that may be applied to the PUSCH repetition may be an OCC sequence of length two. In these embodiments, when the UE is configured to use inter-slot OCC for the PUSCH repetition, the processing circuitry may be configured to apply a first value of the OCC sequence of length two to a first repetition of a PUSCH transmission in a first slot and apply a second value of the OCC sequence of length two to a second repetition of the PUSCH transmission in a second slot. In these embodiments, the OCC sequence may be applied across slots of thePUSCH repetition. In these embodiments, the gNB may use two OCC sequencesof length two to multiplex PUSCH transmission to be received concurrently from two UEs.

[0087] In some embodiments, the processing circuitry may encode a UE capability information element (IE) for transmission to a gNB indicating a UE capability for an OCC sequence of length two.

[0088] In some embodiments, when the OCC sequence that is applied to the PUSCH repetition may be an OCC sequence of length four, and when the UE is configured to use inter-slot OCC for PUSCH repetition, the processing circuitry may apply a first value of the OCC sequence of length four to a first repetition of a PUSCH transmission in a first slot, apply a second value of the OCC sequence of length four to a second repetition of the PUSCH transmission in a second slot, apply a third value of the OCC sequence of length four to a third repetition of a PUSCH transmission in a third slot, and apply a fourth value of the OCC sequence of length four to a fourth repetition of the PUSCH transmission in a fourth slot. In these embodiments, the gNB may use four OCC sequences of length four to multiplex PUSCH receptions from four UEs. For OCCs of length N, the maximum number of orthogonal sequences is also N because the sequences form an orthogonal basis in an N-dimensional vector space.

[0089] In some embodiments, the processing circuitry may be configured to encode a UE capability IE for transmission to a gNB indicating a UE capability for an OCC sequence of length four.

[0090] In these embodiments, there are separate UE capabilities for OCC length 2 sequences and OCC length 4 sequences. A UE capability for OCC length 2 may be a prerequisite for UE capability for OCC length 4,

[0091] In some embodiments, the UE further comprises transmitter circuitry, and when the UE is configured to use inter-slot OCC for the PUSCH repetition, the transmitter circuitry may be configured or indicated to generate a Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) waveform for transmission of the PUSCH. In these embodiments, the OCC sequence may be applied to the DFT-s-OFDM waveform. In some other embodiments, the transmitter circuitry may generate a cyclic prefix OFDM (CP-OFDM) and apply the OCC sequence to the CP-OFDM waveform.

[0092] In some embodiments, the PUSCH repetition may be a Type A PUSCH repetition, Type B PUSCH repetition or a Transport Block processing over multi-Slot (TBoMS) repetition.

[0093] In some embodiments, for the Type B PUSCH repetition, for across slot boundary application of OCC sequences (see FIG. 4), a nominal repetition of the PUSCH may crosse a slot boundary in which a first segment of a first nominal repetition is to be transmitted in a first slot, a second segment of the first nominal repetition is to be transmitted in a second slot, a first segment of a second nominal repetition is to be transmitted in a third slot and a second segment of the second nominal repetition is to be transmitted in a fourth slot. In these embodiments, the UE may apply a first value of the OCC sequence to both the first segment of the first nominal repetition in the first slot and to the second segment of the first nominal repetition in the second slot, and may apply a second value of the OCC sequence to both the first segment of the second nominal repetition in the third slot and to the second segment of the second nominal repetition in the fourth slot.

[0094] In some embodiments, for within slot boundary application of OCC sequences (see FIG. 5), a nominal repetition of the PUSCH crosses a slot boundary in which a first segment of a first nominal repetition is to be transmitted in a first slot, a second segment of the first nominal repetition is to be transmitted in a second slot, a first segment of a second nominal repetition is to be transmitted in a third slot and a second segment of the second nominal repetition is to be transmitted in a fourth slot. In these embodiments, the UE may be configured to apply a first value of the OCC sequence to the first segment of the first nominal repetition in the first slot, apply a second value of the OCC sequence to the second segment of the first nominal repetition in the second slot, apply a third value of the OCC sequence to the first segment of the second nominal repetition in the third slot, and apply a fourth value of the OCC sequence to the second segment of the second nominal repetition in the fourth slot.

[0095] In some embodiments, for symbol-level application of an OCC sequence, the processing circuitry may be configured to apply each value of the OCC sequence to groups of one or more symbols of a PUSCH transmission,excluding any DMRS symbols. Examples of symbol-level application of OCC sequences are illustrated in FIG. 2 and FIG. 3.

[0096] In some embodiments, for collision handling, when a repetition of the PUSCH is dropped due to a collision with a higher-priority transmission, the UE may refrain from applying a next value of the OCC sequence to the repetition of the PUSCH is dropped and may apply the next value of the OCC sequence to a next repetition of the PUSCH.

[0097] In some embodiments, the UE may apply the OCC sequence to PUSCH repetition for a PUSCH transmission to nodes of a non-terrestrial network (NTN) (i.e., satellite network). In some embodiments, OCC sequences may only be applied to PUSCH repetition for PUSCH transmission to nodes of a NTN and are not applied to PUSCH repetition for a PUSCH transmission to nodes of a terrestrial network, although the scope of the embodiments is not limited in this respect. In some embodiments, the UE may apply the OCC sequence to PUSCH repetition for a PUSCH transmission to nodes of a terrestrial network.

[0098] Some embodiments are directed to a non-transitory computer- readable storage medium that stores instructions for execution by processing circuitry of a user equipment (UE) configured for operation in a 5thGeneration New Radio (5GNR) network. In these embodiments, the processing circuitry configured to decode signaling to configure the UE with one or more orthogonal cover code (OCC) sequences and apply one of the OCC sequences to physical uplink shared channel (PUSCH) repetition of a PUSCH transmission.

[0099] Some embodiments are directed to an apparatus of a generation Node B (gNB) configured for operation in a fifth-generation new radio (5GNR) network comprising processing circuitry and memory. In these embodiments, the processing circuitry may be configured to decode user equipment (UE) capability information elements (IE) from two or more UEs indicating capabilities for application of orthogonal cover code (OCC) sequences to physical uplink shared channel (PUSCH) transmissions of a PUSCH repetition. In these embodiments, for UEs that have indicated a UE capability for the application of the OCC sequences, the processing circuitry may generate signalling for transmission to the UE to configure the UEs with or indicate OCCsequences, and demultiplex PUSCH repetitions received from the UEs using the OCC sequences. In these embodiments, the OCC sequences may comprise OCC sequences of length two and OCC sequences of length four and the UE capability IE indicates whether a UE has a capability for application of at least one of the OCC sequences of length two and the OCC sequences of length four.

[0100] In these embodiments, the gNB may select two UEs for use of two OCCs of length two based on a carrier frequency offset differential of the two UEs although the scope of the embodiments is not limited in this respect. In some embodiments, the gNB may select four UEs for use of four OCCs of length four based on a carrier frequency offset differential of the four UEs, although the scope of the embodiments is not limited in this respect.

[0101] In some NTN embodiments, an NTN node (e.g., a satellite) forwards signal to a gNB on the ground and the demultiplexing and PUSCH reception are done at the gNB on the ground. In some alternate NTN embodiments, referred to as a regenerative architecture, the NTN node may have some gNB functionality onboard and the demultiplexing and PUSCH reception are performed at the satellite.

[0102] FIG. 11 illustrates a functional block diagram of a wireless communication device, in accordance with some embodiments. Wireless communication device 1100 may be suitable for use as a UE or gNB configured for operation in a 5GNR or 6G network. Some embodiments are directed to an apparatus of a UE or gNB comprising processing circuitry and memory configured for operation in a 5GNR or 6G network.

[0103] The wireless communication device 1100 may also be suitable for use as a handheld device, a mobile device, a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a wearable computer device, a femtocell, a high data rate (HDR) subscriber device, an access point, an access terminal, or other personal communication system (PCS) device. In some embodiments, the wireless communication device 1100 may be configured for Ultra-High Reliability (UHR) communications in accordance with an IEEE 802.11 (e.g., WiFi 8). Some embodiments are directed to an apparatus of a STA configured for operation in a WLAN comprising processing circuitry and memory.

[0104] The wireless communication device 1100 may include communications circuitry 1102 and a transceiver 1110 for transmitting and receiving signals to and from other communication devices using one or more antennas 1101. The communications circuitry 1102 may include circuitry that can operate the physical layer (PHY) communications and / or medium access control (MAC) communications for controlling access to the wireless medium, and / or any other communications layers for transmitting and receiving signals. The wireless communication device 1100 may also include processing circuitry 1106 and memory 1108 arranged to perform the operations described herein. In some embodiments, the communications circuitry 1102 and the processing circuitry 1106 may be configured to perform operations detailed in the above figures, diagrams, and flows.

[0105] In accordance with some embodiments, the communications circuitry 1102 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium. The communications circuitry 1102 may be arranged to transmit and receive signals. The communications circuitry 1102 may also include circuitry for modulation / demodulation, upconversion / downconversion, filtering, amplification, etc. In some embodiments, the processing circuitry 1106 of the wireless communication device 1100 may include one or more processors. In other embodiments, two or more antennas 1101 may be coupled to the communications circuitry 1102 arranged for sending and receiving signals. The memory 1108 may store information for configuring the processing circuitry 1106 to perform operations for configuring and transmitting message frames and performing the various operations described herein. The memory 1108 may include any type of memory, including non-transitory memory, for storing information in a form readable by a machine (e.g., a computer). For example, the memory 1108 may include a computer-readable storage device, read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices and other storage devices and media.

[0106] In some embodiments, the wireless communication device 1100 may be part of a portable wireless communication device, such as a personaldigital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and / or transmit information wirelessly.

[0107] In some embodiments, the wireless communication device 1100 may include one or more antennas 1101. The antennas 1101 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals. In some embodiments, instead of two or more antennas, a single antenna with multiple apertures may be used. In these embodiments, each aperture may be considered a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting device.

[0108] In some embodiments, the wireless communication device 1100 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements. The display may be an LCD screen including a touch screen.

[0109] Although the wireless communication device 1100 is illustrated as having several separate functional elements, two or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and / or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radiofrequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements of the wireless communication device1100 may refer to one or more processes operating on one or more processing elements.

[0110] The described examples focus on enhancing cellular communication systems, specifically addressing coverage and capacity challenges in 5G New Radio (NR) networks. The technology addresses coverage limitations that occur when NR is deployed at higher carrier frequencies in frequency range 1 (FR1), such as 3.5GHz. At these frequencies, increased pathloss creates coverage challenges. This is particularly noticeable in uplink transmissions due to limited transmit power from user equipment (UE).

[0111] The examples also target Non-Terrestrial Networks (NTN), where UEs communicate through satellites or High-Altitude Platform Stations. These scenarios require additional coverage enhancements due to the substantial distances between satellites and UEs.

[0112] The base technology uses cyclic prefix-orthogonal frequencydivision multiplexing (CP-OFDM) for both downlink and uplink transmissions. For uplink, an additional waveform called Discrete Fourier Transform-spread- OFDM (DFT-s-OFDM) can be used through transform precoding at the transmitter. To improve uplink capacity performance, the examples introduce Orthogonal Cover Codes (OCC) for physical uplink shared channel (PUSCH) transmissions with DFT-s-OFDM waveform. These codes can be applied in multiple ways:• Across OFDM symbols• Across slots• Within an OFDM symbol

[0113] The examples include several components:

[0114] Signaling mechanisms for OCC:• The length of OCC can be configured through system information or radio resource control signaling• OCC sequences can be indicated dynamically through downlink control information• Multiple OCC sequences of different lengths can be specified

[0115] Symbol-level OCC implementation:• Can be applied to single PUSCH transmission• Supports different symbol durations (2, 4, or 8 symbols)• Can include or exclude DMRS symbols

[0116] Type B PUSCH and Transport Block over Multiple Slots (TBoMS) transmission:• OCC can be applied to nominal PUSCH repetitions• Supports actual repetitions within nominal repetitions• Allows for different OCC applications across slots

[0117] Collision handling mechanisms:• Manages scenarios where PUSCH repetitions conflict with high- priority transmissions• Provides options for handling OCC sequences during collisions• Includes procedures for dropped or cancelled transmissions

[0118] The examples address practical implementation considerations such as:• Handling cases where OCC length differs from repetition numbers• Managing symbol grouping for OCC application• Coordinating OCC with DMRS symbols• Supporting both continuous and non-continuous symbol arrangements

[0119] For satellite communications, these examples become particularly relevant as satellites cover wide areas with numerous UEs, especially in Low Earth Orbit (LEO) scenarios. The technology allows multiple users to successfully transmit data during satellite coverage periods while accommodating different resource requirements based on traffic patterns.

[0120] The described components work together to provide enhanced resource multiplexing capabilities. This helps improve system capacity efficiency, particularly in scenarios with coverage limitations or when serving multiple users simultaneously.• The examples include specific technical implementations for:• Configuring OCC parameters through different signaling layers• Managing OCC sequences across different transmission types• Handling various transmission scenarios and potential conflicts• Supporting different waveform configurations• Accommodating both terrestrial and non-terrestrial network deployments

[0121] Examples:1. The method of example 1, wherein the length of orthogonal cover code (OCC) may be configured by higher layers via NR remaining minimum system information (RMSI), NR other system information (OSI) or dedicated radio resource control (RRC) signalling, dynamically indicated in the DCI, or a combination thereof2. The method of example 1, wherein the length of OCC can be configured or dynamically indicated as 1, which indicates that OCC is not applied for PUSCH repetition3. The method of example 1, wherein OCC sequence used for the PUSCH transmission can be configured by dedicated RRC signalling or dynamically indicated in the DCI, or a combination thereof.4. The method of example 1, wherein multiple OCC sequences of different lengths are specified and higher layer signalling and / or layer 1 (DCI-based) indication can be used to provide a UE with a sequence of a given length5. The method of example 1, wherein when cross symbol and / or cross slot OCC is applied for PUSCH transmission, if the length of OCC is less than or equal to the number of repetitions for PUSCH transmission, the OCC sequence is repeated until it reaches the number of repetitions6. The method of example 1, wherein symbol -level OCC may be applied to a single PUSCH transmission for a PUSCH scheduled or configured for transmission with or without repetitions7. The method of example 1, wherein OCC may only be applied for PUSCH with DFT-s-OFDM waveform, wherein for dynamic waveform switching, OCC sequence indication field may be present or reserved in accordance with whether transform precoder indicator field is set to 1, such thatDFT-s-OFDM waveform is used for PUSCH transmissions8. The method of example 1, wherein when cross symbol or cross slot orthogonal cover code (OCC) is applied for Type B PUSCH repetitions, the OCC is applied on the nominal PUSCH repetitions9. The method of example 1, wherein when cross symbol or cross slot orthogonal cover code (OCC) is applied for Type B PUSCH repetitions, the OCC is applied on the actual PUSCH repetitions10. The method of example 1, wherein when cross symbol or cross slot orthogonal cover code (OCC) is applied for Type B PUSCH repetitions, the OCC is applied on the PUSCH repetition for a slot.11. The method of example 1, wherein when cross slot orthogonal cover code (OCC) is applied on transport block over multiple slots (TBoMS), the OCC is applied for each repetition of TBoMS12. The method of example 1, wherein when cross slot orthogonal cover code (OCC) is applied on transport block over multiple slots (TBoMS), symbollevel OCC may be applied to a single TBoMS repetition13. The method of example 1, wherein when cross-slot OCC is applied for the PUSCH repetitions, if a PUSCH repetition is cancelled or dropped due to collision with high priority uplink transmission or semi-static DL symbols including synchronization signal block (SSB) and / or if UCI is multiplexed on PUSCH when PUSCH overlaps with PUCCH in time, the PUSCH repetitions or transmission occasions after the PUSCH are dropped14. The method of example 1, wherein when cross-slot OCC is applied for the PUSCH repetitions, if a PUSCH repetition is cancelled or dropped due to collision with high priority uplink transmission or DL symbols including synchronization signal block (SSB) and / or if UCI is multiplexed on PUSCH when PUSCH overlaps with PUCCH in time, the OCC is not applied to the PUSCH and the OCC sequence is not postponed to the next available transmission occasion or repetition15. The method of example 1, wherein when cross-slot OCC is applied for the PUSCH repetitions, if a PUSCH repetition is cancelled or dropped due to collision with high priority uplink transmission or DL symbols including synchronization signal block (SSB) and / or if UCI is multiplexed on PUSCH when PUSCH overlaps with PUCCH in time, the OCC is not applied to the PUSCH and the OCC sequence is postponed to the next available transmission occasion or repetition.16. The method of example 1, wherein for symbol level OCC, a set of symbols within the allocated number of symbols for PUSCH transmission, excluding DMRS symbols, may be grouped for OCC.17. The method of example 1, wherein the number of symbols allocated for a PUSCH transmission excluding DMRS symbols is an integer number of OCC length18. The method of example 1, wherein the number symbols in a group is equal to the OCC length19. The method of example 1, wherein when the remaining number of symbols in a group is less than the OCC length, the OCC sequence that is applied to the group is truncated so that the length of OCC sequence is equal to the number of symbols in the group20. The method of example 1, wherein the set of symbols in a group excluding DMRS symbols where the OCC sequence is applied may be continuous or non-continuous in time domain. 21. The method of example 1, wherein symbol level OCC or pre-DFT OCC(OCC within a symbol) may be applied for the TBoMS transmission without and / or with repetitions22. The method of example 1, wherein when TBoMS transmission with repetition is applied for PUSCH transmission, symbol level OCC or pre-DFTOCC may be applied for each repetition of TBoMS transmission

[0122] The Abstract is provided to comply with 37 C.F.R. Section1.72(b) requiring an abstract that will allow the reader to ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it will not be used to limit or interpret the scope or meaning of the claims. The following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.

Claims

CLAIMSWhat is claimed is:

1. An apparatus of a user equipment (UE) configured for operation in a 5thGeneration New Radio (5G NR) network, the apparatus comprising: processing circuitry and memory, wherein the processing circuitry is configured to: decode signaling to configure the UE with one or more orthogonal cover code (OCC) sequences; and apply one of the OCC sequences to physical uplink shared channel (PUSCH) repetition of a PUSCH transmission.

2. The apparatus of claim 1, wherein when the OCC sequence that is applied to the PUSCH repetition is an OCC sequence of length two, and wherein when the UE is configured to use inter-slot OCC for the PUSCH repetition, the processing circuitry is configured to apply a first value of the OCC sequence of length two to a first repetition of a PUSCH transmission in a first slot and apply a second value of the OCC sequence of length two to a second repetition of the PUSCH transmission in a second slot.

3. The apparatus of claim 2, wherein the processing circuitry is configured to encode a UE capability information element (IE) for transmission to a gNB indicating a UE capability for an OCC sequence of length two.

4. The apparatus of claim 2, wherein when the OCC sequence that is applied to the PUSCH repetition is an OCC sequence of length four, and wherein when the UE is configured to use inter-slot OCC for PUSCH repetition, the processing circuitry is configured to: apply a first value of the OCC sequence of length four to a first repetition of a PUSCH transmission in a first slot; apply a second value of the OCC sequence of length four to a second repetition of the PUSCH transmission in a second slot;apply a third value of the OCC sequence of length four to a third repetition of a PUSCH transmission in a third slot; and apply a fourth value of the OCC sequence of length four to a fourth repetition of the PUSCH transmission in a fourth slot.

5. The apparatus of claim 4, wherein the processing circuitry is configured to encode a UE capability IE for transmission to a gNB indicating a UE capability for an OCC sequence of length four.

6. The apparatus of claim 2, wherein the UE further comprises transmitter circuitry, and wherein when the UE is configured to use inter-slot OCC for the PUSCH repetition, the transmitter circuitry is configured to generate a Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) waveform for transmission of the PUSCH, wherein the OCC sequence is applied to the DFT-s-OFDM waveform.

7. The apparatus of claim 2, wherein the PUSCH repetition one of a Type A PUSCH repetition, Type B PUSCH repetition and a Transport Block processing over Multi-Slot (TBoMS) repetition.

8. The apparatus of claim 7, wherein for the Type B PUSCH repetition, for across slot boundary application of OCC sequences when a nominal repetition of the PUSCH crosses a slot boundary in which a first segment of a first nominal repetition is to be transmitted in a first slot, a second segment of the first nominal repetition is to be transmitted in a second slot, a first segment of a second nominal repetition is to be transmitted in a third slot and a second segment of the second nominal repetition is to be transmitted in a fourth slot, the processing circuitry is configured to: apply a first value of the OCC sequence to the first segment of the first nominal repetition in the first slot and to the second segment of the first nominal repetition in the second slot;apply a second value of the OCC sequence to the first segment of the second nominal repetition in the third slot and to the second segment of the second nominal repetition in the fourth slot.

9. The apparatus of claim 1, wherein for within slot boundary application of OCC sequences when a nominal repetition of the PUSCH crosses a slot boundary in which a first segment of a first nominal repetition is to be transmitted in a first slot, a second segment of the first nominal repetition is to be transmitted in a second slot, a first segment of a second nominal repetition is to be transmitted in a third slot and a second segment of the second nominal repetition is to be transmitted in a fourth slot, the processing circuitry is configured to: apply a first value of the OCC sequence to the first segment of the first nominal repetition in the first slot; apply a second value of the OCC sequence to the second segment of the first nominal repetition in the second slot; apply a third value of the OCC sequence to the first segment of the second nominal repetition in the third slot; and apply a fourth value of the OCC sequence to the second segment of the second nominal repetition in the fourth slot.

10. The apparatus of claim 1, wherein for symbol -level application of an OCC sequence, the processing circuitry is configured to: apply each value of the OCC sequence to groups of one or more symbols of a PUSCH transmission, excluding any DMRS symbols.

11. The apparatus of claim 1, wherein for collision handling, when a repetition of the PUSCH is dropped due to a collision, the processing circuitry is configured to refrain from applying a next value of the OCC sequence to the repetition of the PUSCH is dropped and apply the next value of the OCC sequence to a next repetition of the PUSCH.

12. The apparatus of claim 1, wherein the processing circuitry is configured to apply the OCC sequence to PUSCH repetition for a PUSCH transmission to nodes of a non-terrestrial network (NTN).

13. A computer-readable storage medium that stores instructions for execution by processing circuitry of a user equipment (UE) configured for operation in a 5thGeneration New Radio (5G NR) network, the processing circuitry configured to: decode signaling to configure the UE with one or more orthogonal cover code (OCC) sequences; and apply one of the OCC sequences to physical uplink shared channel (PUSCH) repetition of a PUSCH transmission.

14. The computer-readable storage medium of claim 13, wherein when the OCC sequence that is applied to the PUSCH repetition is an OCC sequence of length two, and wherein when the UE is configured to use inter-slot OCC for the PUSCH repetition, the processing circuitry is configured to apply a first value of the OCC sequence of length two to a first repetition of a PUSCH transmission in a first slot and apply a second value of the OCC sequence of length two to a second repetition of the PUSCH transmission in a second slot.

15. The computer-readable storage medium of claim 14, wherein the processing circuitry is configured to encode a UE capability information element (IE) for transmission to a gNB indicating a UE capability for an OCC sequence of length two.

16. The computer-readable storage medium of claim 14, wherein when the OCC sequence that is applied to the PUSCH repetition is an OCC sequence of length four, and wherein when the UE is configured to use inter-slot OCC for PUSCH repetition, the processing circuitry is configured to:apply a first value of the OCC sequence of length four to a first repetition of a PUSCH transmission in a first slot; apply a second value of the OCC sequence of length four to a second repetition of the PUSCH transmission in a second slot; apply a third value of the OCC sequence of length four to a third repetition of a PUSCH transmission in a third slot; and apply a fourth value of the OCC sequence of length four to a fourth repetition of the PUSCH transmission in a fourth slot.

17. The computer-readable storage medium of claim 16, wherein the processing circuitry is configured to encode a UE capability IE for transmission to a gNB indicating a UE capability for an OCC sequence of length four.

18. An apparatus of a generation Node B (gNB) configured for operation in a fifth-generation new radio (5G NR) network, the apparatus comprising: processing circuitry; and memory, wherein the processing circuitry is configured to: decode user equipment (UE) capability information elements (IE) from two or more UEs indicating capabilities for application of orthogonal cover code (OCC) sequences to physical uplink shared channel (PUSCH) transmissions of a PUSCH repetition, wherein for UEs that have indicated a UE capability for the application of the OCC sequences, the processing circuitry is configured to: generate signalling for transmission to the UE to indicate OCC sequences; demultiplex PUSCH repetitions received from the UEs using the OCC sequences.

19. The apparatus of claim 18, wherein the OCC sequences comprise OCC sequences of length two and OCC sequences of length four, wherein the UE capability IE indicated whether a UE has a capability for application of at least one of the OCC sequences of length two and the OCC sequences of length four.

20. The apparatus of claim 19, wherein the processing circuitry is configured to select two UEs for use of two OCCs of length two based on a carrier frequency offset differential of the two UEs.

Images